The above segregation is done to ensure the granular level control over fields appearing while vendor master data creation/change/display.

We will see how all of the above options work:

Screen Layout at Account Groups LevelIn this step, we assign field status to various fields based on the Vendor Account Groups. This means, for e.g. field Mobile Number can be made mandatory for Account Group of One Time Vendors and at the same time can be kept optional for other account groups.

Field Status at Company Code LevelIn this step, we assign field status to various fields based on the Company Codes. This means, for e.g. field Alternate Payee can be made suppressed for Company Code "A" and at the same time can be kept optional for Company Code "B". This will help to control the master data at company code level.

Field Status at Activity TypeIn this step, we assign field status to various fields based on activities i.e. Creation, Change and Display. This means, for e.g. field Reconciliation Account can be made Mandatory while creation of master data and at the same time can be kept in display mode for change of master data. This will help to ensure the reconciliation between Sub Ledger and General Ledger.

After we configure all the above levels, whenever we create or change the vendor master, system works as below:

Verifies field status at all the above three levels

Based on all the three decides the final status to be applied for the field (Based on the logic explained below)

After system analyses the field status, system presents the user with the final fields as per the final status.

Before I explain you the logic how system identifies the final status, we need to first understand the ranking of every status

Suppress : FirstMandatory : SecondDisplay : ThirdOptional : Last

Now we will show you some examples how system finds final status:

Field: XStatus at Account Group: OptionalStatus at Company Code: OptionalStatus at Activity: Suppressed

In above case, system will suppress the field as suppress has precedence over optional status.

But we also need to consider certain field status combinations which are not allowed by SAP

Mandatory and SuppressedMandatory and DisplaySuppressed and Display

In case any field has any of above combination, the system throws error while creating/changing master data and the field status has to be corrected in order to complete the master data.

SAP provides standard field statuses in the system, but they can be changed as per our requirement. But please use care and caution while doing the same as any incorrect combination it may cause error.