Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Andi_M
Product and Topic Expert
Product and Topic Expert
208

Introduction

In SAP S/4HANA, the Business Partner serves as the primary entity for managing both customer and vendor information. Within the Business Partner General Data section, you can maintain all essential cross-application master data, including addresses, communication details, tax numbers, and identification numbers.

 

Missing Information in Customer and Vendor Roles

You may have noticed that tax numbers, industry information, and identification numbers are not visible on the customer and vendor role screens (specifically roles FLCU01 and FLVN01). To view or modify tax numbers, you must switch to the Business Partner role "000000 Business Partner (Gen.)." This blog outlines simple steps to add the missing information to customer and vendor roles, focusing on tax numbers in the BP role FLCU01. You can apply these steps to other BP roles as well.

01-BP 000000.jpg

 

Screen Analysis

To gain more insights into the BDT Analyzer, refer to the blog post titled SAP S/4HANA Business Partner BDT Analyzer Usage.
To identify which screen objects are affected, you can perform a screen analysis using the transaction code BDT_ANALYZER.

02-BDT_ANALYZER.jpg

At first glance, everything appears to be in order. However, there must be another reason why certain sections are not displayed. Take note of the following details regarding the missing sections:

  • Section: BUTX01 - Tax Numbers
  • Dataset: BUTX01
  • Field Group: 0114

 

Field Status Analysis

For further information on Field Status Analysis, please check the blog post titled SAP S/4HANA Business Partner Field Status Analysis.
To analyze field status, execute the transaction code CVI_CHECK_VISIBILITY and input the relevant information.

03-Field Status.jpg

You will see the following results screen.

04-Analysis.jpg

Now, let's review each of these check results.

 

CVI Field Mapping

If you encounter the two lines mentioned, open the specified customizing views in transaction SM30 and adjust the settings for client 000.

05-field mapping views.jpg

 

Check Dataset Field Group BP View Assignment

06-dataset.jpg

Open the Business Data Toolset (BDT) configuration in a new session by entering the transaction code BUPT. Navigate to the BP Views option.

07-BP Views.jpg

Display the BP View Dataset assignment for BP View FLCU01 (which is linked to BP role FLCU01).

08-FLCU01 dataset.jpg

Here, you will notice that Dataset BUTX01 is not assigned to BP View FLCU01.

09-missing dataset.jpg

Assign Dataset BUTX01 to BP View FLCU01.

10-add dataset.jpg

 

Check Application BP View Assignment

Tax numbers are managed by their own BDT application. Therefore, the application BUTX must be assigned to BP View FLCU01.

11-add application.jpg

12-new application.jpg

 

Check Changes

Field Status Analysis

To verify the changes you have made so far, run the transaction CVI_CHECK_VISIBILITY again using the data from your initial run.
From this perspective, everything appears to be correct. As you can see, the last line of the field status check has disappeared due to the customization adjustments.

13-field Status.jpg

 

Check BP Transaction

Finally, execute the BP transaction to confirm that tax data is now available in BP role FLCU01.

14-bp transaction.jpg

 

Conclusion

Following these steps you are able to apply missing sections to your roles in usage.

1 Comment