Recommendations for Defining Field Status 

To define the field status, you must decide where you want to make these specifications. SAP recommends the following procedure:

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.

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 are therefore suppressed in the field status group for bank accounts. Bank accounts, however, require the value date group, which you display.

The field statuses for postings to customer or vendor accounts are handled in a different manner. In the standard system, there are a number of different posting keys used for these postings. The field status is therefore differentiated via posting keys.

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. The payment terms 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 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.

Using the reconciliation accounts for investment payment and for down payments on current assets, you determine the screens for posting as follows: Because you require the fixed asset fields for investment payments, you display them. These fields are not needed for down payments on current assets and can be hidden with the status bar in the reconciliation accounts.

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