Ansicht
Dokumentation

ISISFICA_INSO0018 - Configure Field Attributes per Activity

Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Dependent on the activity, in this activity you define which fields

,,,,o require input (required entry)

,,,,o are ready for input (optional entry)

,,,,o are displayed (display)

,,,,o are hidden (hide)

during master data maintenance.

For each field, this definition is linked to the field status for the other criteria. The link is used to determine the status that the field takes in the input screen for master data.

Link Rules

1. Linking the same criteria

The same criteria can be two or more roles, for example, that a business partner can have, or several roles that can be grouped together into a role grouping.

The field statuses for two identical criteria are linked, and then the result is linked with the third criterion and so on. Required entry has the highest priority here, followed by optional entry, display, hide, and the non-specified entry.

In this way, the field status is reduced to a single status.

Examples of linking:

Criterion 1         Hide        Op.Entry    Op.Entry

Criterion 2         Op.Entry    Display     Req.Entry


Interim Result      Op.Entry    Op.Entry    Req.Entry

1. Linking all remaining different criteria (apart from the activity)

Different criteria can be, for example, role(s) and BP type (application object business partner) or relationship category and client (application object relationships).

The field statuses for two different criteria are linked, and then the result is linked with the third criterion and so on. Hide has the highest priority here, followed by display, required entry, optional entry, and the non-specified entry.

Examples of linking:

Criterion 1         Hide        Op.Entry    Op.Entry

Criterion 2         Op.Entry    Display     Req.Entry


Interim Result      Hide    Display    Req.Entry

1. Linking the result with the activity

The result from above is linked with the field status for the activity. In principle, the same rules apply as above. In addition, the activity displaymeans that all the fields are no longer ready for input.

Examples of linking:

Interim Result       Req.Entry    Req.Entry   Op.Entry

Field Status Act. Op.Entry     Non-spec.   Display

Data Maint. Act. Create       Display     Change


Result               Req.Entry    Display     Display

Example

In exceptional cases it can be necessary to control the field status using the activity. This can be the case, for example, if a field is filled when created, and is then not to be changed at a later date.

Check the delivered attribute assignments and change them where necessary.

ROGBILLS - Synchronize billing plans   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4593 Date: 20240420 Time: 120107     sap01-206 ( 51 ms )