Start of Content Area

Background documentation Recommendations for Defining Field Status  Locate the document in its SAP Library structure

To define the field status, you must decide where you want to make these specifications.

For postings to G/L accounts, make your specifications in the master records. In the standard system, there are only two posting keys used for G/L account postings. This means that only the master records enable you to differentiate the layout of screens. The field status definitions for posting keys 40 (G/L account debit) and 50 (G/L account credit) are all defined as optional fields in the standard system.

Example

In the status bar for a cost element account, you specify that the cost center and order fields are displayed. These fields are not required for bank accounts and they are therefore suppressed. Bank accounts, however, require the value date group and this field is therefore assigned the required entry status.

In the standard system, there are a number of different posting keys for posting to customer or vendor accounts. The field status is therefore differentiated via posting keys.

Example

The field status specifications for posting key 01 (customer invoice) and posting key 15 (customer payment) are different in the standard system. The fields to be displayed and which require an entry are determined based on the transaction. The text and assignment number fields are always required. Payment terms are required when you enter an invoice, but not when you enter a payment. These fields have therefore been suppressed in the specifications for posting key 15.

In the field status definition for reconciliation account master records, you suppress only those fields which are not transaction-specific and which are not required in posting to a customer or vendor account. You define all other fields as optional. Controlling the screen layout using a reconciliation account is advisable only in special G/L transactions such as down payments and bills of exchange. Each of these transactions automatically post to a separate reconciliation account. You can use these separate accounts to differentiate fields specifically for the transaction involved.

Example

Using the reconciliation accounts for investment payment and for down payments on current assets, you determine the screens for posting as follows: For investment payments, you include the fields for assets. These fields are not needed for down payments on current assets and can be suppressed using the status bar in the reconciliation accounts.

Note

The posting keys are defined at client level. They therefore apply to all company codes. If you suppress fields using the specifications for the posting key, you should make sure that they are not needed in a company code.

 

 

 

 

End of Content Area