Customize Business Partner Screens S4H [PDF]

Zitiervorschau

HOW TO CUSTOMIZE BUSINESS PARTNER SCREENS AND FIELDS ON SAP S/4HANA TUTORIAL

JAN DURINDA - Solution Center Lead ERP Consulting -

A publication of

TABLE OF CONTENTS • Introduction • Description of the issue • Solution • Result

INTRODUCTION

Due to the integration of Customer and Vendor SAP objects into one main object called Business Partner on SAP S/4HANA, Business Partner is ­ becoming ­ ­ unconditionally one of the most important objects across SAP. Each project, either greenfield (new implementation) or brownfield (upgrade of ­existing ­systems to S/4HANA), related SAP S/4HANA implementation will ­definitely contain phase where Business Partners are customized for business purposes. In this tutorial, I will explain how to customize Business Partners with focus on hiding only single field from the screen. As you might know, hiding fields and creating your own tabs for customers and vendors on SAP S/4HANA is now different on the old ECC. Visual Configuration Tool (VCT) – ­transaction “BUCO” feature for doing screen change that was originally designed for Business Partners on ECC, will be used on SAP S/4HANA as the main tool for doing screen adjustments also for customers and vendors, due to the already mentioned merge into one object. I must admit that in some ways using VCT for customers and vendors is much more comfortable than before. However, in many cases, especially when I wanted to remove single fields from the screen, I was struggling a lot. This is because you can easily remove only complete sections or as SAP calls it “Views”, but not a single field from the section. Therefore, I prepared a ­step-by-step guide on how to hide single field out of the screen section, which worked for me.

1 DESCRIPTION OF THE ISSUE

Chapter 1: DESCRIPTION OF THE ISSUE

DESCRIPTION OF THE ISSUE It is required to hide the “Pmt meth. Supplement” field. But, this field belongs to a section containing other fields which need to be kept and therefore the whole section cannot be removed.

Field which needs to be hidden

As you can see, the field belongs to a section containing other fields, therefore it is not possible to remove whole section.

2 SOLUTION

Chapter 1: DESCRIPTION OF THE ISSUE

SOLUTION Below you can find solution split into steps: 1. Finding SAP view (section) which contains all fields from block 1.1. Using F1 keyboard on field which we want to hide we will get “Field name” (in our case UZAWE)

1.2. Using transaction SE16 and table TBZ3R we will find all possible “Field Groups” in column FLDGR

Chapter 1: DESCRIPTION OF THE ISSUE

1.3. Once we have “Field Group” using table TBZ3S and obtained field group ­value (in our case 1871) you need to find “View”.

1.4. Based on the results, it is possible to find “View” (in our case CVIV42) that ­contains field group referring to the field which needs to be hidden. 2. Creation of Z* enhanced view 2.1. Using transaction BUS3 we open found view and after clicking option “View->Field Groups” you can see all “Field Groups” which that view contains.

Chapter 1: DESCRIPTION OF THE ISSUE

2.2. It is highly recommended to check all fields which are assigned to field group which is planned to be removed. In our case it was field group “1871”- field UZAWE. Using transaction BUS2 you can easily achieve it.

2.3. Once we know View (section which contains the field) and all the field group(which is actually representing field) which we want to remove we need to create Z* view without these field group. However before creation of Z* view we need to prepare “Data Set”. 2.4. In order to create “Data Set” you can use transaction BUS23, where you create new Z* Data Set by using “copy as option” based on data set field which is located in the original view (in our case data set value was CVIC04)

Chapter 1: DESCRIPTION OF THE ISSUE

2.5. Once Z*Data Set prepared it is necessary to open once again transaction BUS3 and using functionality “copy as option” it is necessary to create your own Z* view based on default view (in our case CVIC40 -> ZCVI40), and inside Data Set field insert just created Z* data set from previous step 2.4. (In our case CVIC04 -> ZCVIC04).

> 2.3. Once we know View(section which contains field) and all field group(which is actually representing field) which we want to remove we need to create Z* view without these field group. However before creation of Z* view we need to prepare so called “Data Set”. 2.4. In order to create “Data Set” you can use transaction BUS23, where you create new Z* Data Set by using “copy as option” based on data set field which is located in original view (in our case data set value was CVIC04)

Chapter 1: DESCRIPTION OF THE ISSUE

2.6. Once copying is done go into “View -> Field Groups” option and delete all obsolete field groups which are related to obsolete fields (in our case 1871) and save View.

2.7. The enhanced view which represents part of the screen containing only fields you want to keep needs to be assigned to a section now. To do it, find the ­section where the original view was assigned (in our case CVIC24) by using table TBZ3H (or you can use the “where used” feature).

2.8. Out of results we can see that “Section”, to which original view is assigned is “CVIC35” – Column ABSNR

Chapter 1: DESCRIPTION OF THE ISSUE

3. Creation of Z* Section 3.1. Once we found related Section we need to create our own Z* Section using transaction BUS4.

3.2. After confirmation of relation between screen and section proceed with ­creation of Z* section using copy as functionality. 3.3. Once creation of new Z* section is created, it is necessary to enhance it with already created Z*view from previous step 2.5 (In our case view – ZVIC42)

>

Chapter 1: DESCRIPTION OF THE ISSUE

3.4. For now we have prepared Z*View with only fields which we want to keep, Z*Section where Z*View belongs, however now we need to find the Screen to which the original section belongs. In order to the original Screen you can use either table TBZ3I based on the original section or the “where used” ­option (in our case CVIC35)

3.5. Based on the results you can take “Screen” from column DYNID (In our case CVIC31)

Chapter 1: DESCRIPTION OF THE ISSUE

4. Creation of Z* Screen 4.1. Once related screen is found it is necessary again to create our own Z*Screen using transaction BUS5 4.2. Again proceed with creation of Z*Screen using copy as option button, however screen consists of multiple sections and it is necessary to replace original section with newly created Z*Section from previous step 3.

> 4.3. After this step there is done we have prepared Z*Dataset, Z*View, Z*Section, Z*Screen and last step in this structure is to find Screen Sequences. Screen Sequence consist of multiple screens and it is necessary to replace original screen with newly created one (in our case ZVIC31)

Chapter 1: DESCRIPTION OF THE ISSUE

5. Replacing screen within Screen sequences 5.1. In order to find Screen sequence use table TBZ3K using original view based on which we created Z* view

5.2. Based on the results you can take Screen sequence from column VARNR (In our case FS0001) 5.3. Using value of Screen sequence and transaction BUS6 it is necessary to ­replace original screen with newly created one (in our case CVIC31 -> ZVIC31)

>

Chapter 1: DESCRIPTION OF THE ISSUE

6. Setup correct Data Sets for Business partner views 6.1. Once screen sequence is prepared it is necessary to execute last setup related to BP Views which is assigned to your main BP Role. In order to find BP View assigned to BP Role use customizing “Cross-Application Components”-> ”SAP Business Partner” -> “Business Partner” -> “Business Partner Roles” -> ­”Define BP Roles” and find your BP Role under which is used during creation of ­business partner.

Chapter 1: DESCRIPTION OF THE ISSUE

6.2. After obtaining information about BP View (in our case ZFLCU0) it is n ­ ecessary to assign important “Data Set” which we created in step 2.4 to BP View (In our case ZFLCU0) using transaction BUSD.

Note: I recommend to double check within transaction BUSD if following items are correctly assigned: Subheader ID: which represents additional tabs within business partners (e.g. Company Code data for BP) Screen Sequence: Represents screen sequence of main general data of ­business partner Calling Application: Are used mainly for differentiation type of views. H ­ owever for all views which are supposed to be displayed must all related ­application be assigned to BP View.

Chapter 1: DESCRIPTION OF THE ISSUE

7. Replacing screen within Screen sequences 7.1. As last step you must ensure that original data set which is still assigned to BP View (in our case CVIC04) is not anymore linked with original view (in our case CVIC42), otherwise on your screen still would appear original setup of fields. In order to break this link again use transaction BUS3 and open original view from step and delete Data Set from this View

7.2. By terminating link only new Z* view will be used and all setup which view contains 7.3. After all is done I recommend also to check transaction BUCO. It might ­happen you need to again activate view – section

3 RESULT

Chapter 1: DESCRIPTION OF THE ISSUE

RESULT

vs.

Hint: Below you can find some additional HINT to guide related to BUCO transaction

“

Thank you for reading this e-book. Don´t hesitate to contact me if you want to learn more. Jan Durinda [email protected]

Appendix

Copyright: Datavard AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of Datavard AG. The information contained herein may be changed without prior notice. Datavard, OutBoard, ERNA, CanaryCode, BW Fitness Test and ERP Fitness Test are trademarks or registered trademarks of Datavard AG and its affiliated companies. SAP, R/3, SAP NetWeaver, SAP BusinessObjects, SAP MaxDB, SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are provided by Datavard AG and its affiliated companies (“­Datavard”) for informational purposes only, without representation or warranty of any kind, and Datavard shall not be liable for errors or omissions with respect to the materials. The only warranties for Datavard products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.