Populating Transaction Type during Order Settlement 

You have an internal order that you want to settle to a balance sheet account. This accounts field status makes the transaction type (BSEG-BEWAR) required. During settlement you receive error message F5 808 stating that this field is status initial but the field is required.   This field is not available to you in the settlement rule definition.   Is it possible that this field is suppressed?   You could not locate a means to display or require it if so.   You attempted to resolve this using a substitution that would popluate the transaction type field.  However, during execution you did not hit the breakpoint you put into the user exit.   How to overcome this issue? 

You can change the requirement of the field in the "Field Status" of the account (Financial Accounting -> General Ledger Accounting -> Business Transaction -> G/L Account Posting -> Carry Out and Check Documents Settings -> Maintain Field Status Variants) 

or 

In transaction OB41 where you define posting keys and its "Field status". Both "Field Status" are maybe differents, but if in one of them the field is like "required entry" you have to change it.   But if you are posting a fixed asset account, you will need this field completed because it defines the movement you are making. 

See Also
SAP FI FAQ

Get help for your SAP FI/CO problems
SAP FICO Forum - Do you have a SAP FI/CO Question?

SAP Books
SAP FICO Books  - Certification, Interview Questions and Configuration

SAP FICO Tips
SAP FI/CO Tips and Financial Accounting/Controlling Discussion Forum

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.