Technical Articles
SAP S/4HANA Business Partner Field Status Analysis
With Business Partner implementation at SAP S/4HANA you notice that a field is unexpected set to required/hidden and you wonder where field status has been set.
In this blog you will get to know how to analyze field status in BP transaction.
This blog is in addition to blog post Tips and Tricks on Field Modifications in Transaction BP, CVI in S/4HANA.
Introduction
Purpose and Target
The purpose of this blog is to describe how to analyze field status in BP transaction.
Target audience: Functional Experts, Key Users
Version: SAP S/4HANA On premise 1610 and higher
If you work with below SAP S/4HANA 2020 please have a look at SAP Note2848273 – CVI_BDT: Find reason for field status (required, hidden etc.) of fields in transaction BP (CVI_CHECK_VISIBILITY).
At BP transaction you notice a field which is unexpected set to required. Transaction CVI_CHECK_VISIBILITY will help to find the cause.
At this example field ‘Customer Pricing Procedure’ is set as required and you want to find the source of field status.
Sources of Field Status setting
There are many of sources to set field status. This picture shows main Field Status criteria categorized in source object.
At BP Transaction all of these field criteria are considered and a merged into one field status per field group based on priority (from highest to lowest):
- hidden
- display
- required
- optional
Find corresponding Field Group with BDT Analyzer
A description how to use BDT Analyzer can be found at my blog
SAP S/4HANA Business Partner BDT Analyzer usage
At BP Transaction mark the field in question and enter bdt_analyzer into OK code field.
The following Pop-Up appears.
You may notice that some Field Groups are marked with plus or minus at column FldStatus. As you can see Field Group 1910 is set to required.
Analyze Field Status
To analyze Field Status open an additional SAP GUI session and run transaction CVI_CHECK_VISIBILITY.
At selection screen choose option ‘All Statuses’ enter following data based on BP transaction and BDT-Analyzer.
and press <EXECUTE>.
Reading result screen
After executing you will get the result screen.
The report is running through all Field Status criteria and analyzes Field Status setting As you can see at our example field ‘Customer Pricing Procedure’ is set as required at Account Group level.
Changing Field Status at each criterion
At this chapter you will find IMG path for all Field Status criterion. To set Field Status use given Field Group number.
Business Partner settings
Client setting
Cross-Application Components ->
Role setting
Activity setting
BP category (BP Type) setting
Customer settings
Account Group setting
Activity setting
Sales Organisation setting
Vendor/Supplier settings
Screenshots below are just example to show you where to find field status setting in IMG.
Account Group setting
Activity setting
Purchasing Organisation setting
Site BP for retail (RE-FX) settings
Conclusion
With this guide you are able now to do your own field status analysis for field (group) of your choice.
A good explanation
VERY useful utility that enabled us to trace the elusive source of the setting of the vendor's GR-IR flag (dynpro field GS_LFM1-WEBRE) as "Mandatory" in the maze of apparently contradictory settings, especially when the field is assigned to Field Group 343 which has the unencouraging description "Obsolete: Payment Advice by EDI!"