Start of Content Area

Background documentation Screen Layout  Locate the document in its SAP Library structure

You can customize the screens for entering master data and transaction data such that they are specific to the account or to the transaction.

For master data, you select the required fields using the account groups.

When you enter a document, the relevant field status definitions are those in the G/L account master records and those for the posting keys.

Note

In certain circumstances, special screens that differ from the standard screen sequence are called up. This is the case, for example, if the bank master data for a set of bank details has not been created. The system then branches to the screen for creating the bank master data. If you post to a one-time account or to an account with an alternative payee, the system displays a screen on which you can enter the address data. These particular screens are also called up during batch input. The prerequisite for this is that the data for these screens is transferred.

Example

The following figures show a screen for entering payment differences: The first screen is unchanged, the second has been adapted.

This graphic is explained in the accompanying text

This graphic is explained in the accompanying text

A question mark has been added to the Text field on the second screen. This means that it must be filled (required field) since you must enter an explanation in the line item when you enter a payment difference. All other fields are optional; you can fill them, but do not have to. The Collective.no. field has been suppressed.

In the example, fields for posting documents are shown with different statuses. This is also possible for master data. In particular, address data fields are suppressed when you enter one-time account master data, since this data is entered in the line item.

Caution

You must make sure that all the fields for which you transfer data are ready for input. In addition, you must make an entry in all fields that require an entry (required fields). If you do not do this and then transfer your legacy data using, for example, batch input, the incorrect records are not updated when processing the session with the missing data.

For more information about account groups and field status definitions, see Screen Layout for Posting: Field Status