s4h24 opensap: unit 06: cvi preparation: mapping / badis
TRANSCRIPT
s4h24 – Unit 6 Exercise 1
s4h24 openSAP: Unit 06: CVI preparation: mapping / BAdIs
Exercise 1: Activating BAdI Implementation to derive BP category
PUBLIC
s4h24 – Unit 6 Exercise 1
2
TABLE OF CONTENTS
Contents BEFORE YOU START ...................................................................................................... 3
Prerequisites for this exercise ........................................................................................ 3
Logon Data ...................................................................... Error! Bookmark not defined.
Logon to system (SAP ERP) ............................................. Error! Bookmark not defined.
Used Master data: ............................................................ Error! Bookmark not defined.
Additional information: ...................................................... Error! Bookmark not defined.
Exercise 1: Activating BAdI Implementation to derive BP category ...................................... 4
Overview ....................................................................................................................... 4
Objective ................................................................................................................... 4
Exercise Description ................................................................................................... 4
Activate BAdI implementation and perform tests ............................................................. 5
s4h24 – Unit 6 Exercise 1
3
BEFORE YOU START
Prerequisites for this exercise
Please make sure that activities from unit 5 are completed in your system before starting unit 6 activities provided in this document.
The following Cloud Appliance Library solution must be used for this exercise:
“1: SAP ERP source system” - https://cal.sap.com/subscription?sguid=1a3556c0-0ee1-4a4c-8a5a-db08173df293
Logon Data
User ID Password Client number
10steps2s4 <your CAL master password> 100
Logon to system (SAP ERP)
Please log on to SAP CAL solution instance which you created from CAL solution “1: SAP ERP source system” in unit 1 exercise 2.
Used Master data:
N/A
Additional information:
N/A
s4h24 – Unit 6 Exercise 1
4
Exercise 1: Activating BAdI Implementation to
derive BP category
Overview
Estimated time: 45 mins
Objective
The objective is to activate a BAdI implementation so that the Business Partner category will be derived base on the address title.
Exercise Description
In this exercise, you will activate a BAdI implementation. You will also look into the coding of this implementation and you will test the implementation by creating
a new vendor master record.
s4h24 – Unit 6 Exercise 1
5
Activate BAdI implementation and perform tests
Activate your instance of CAL solution 1 and logon to your Cloud Appliance solution “SAP ERP source system” - https://cal.sap.com/subscription?sguid=1a3556c0-0ee1-4a4c-8a5a-
db08173df293 . What to Do What You Will See
1. Look up available BAdIs for CVI IMG -> Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Business Add-Ins (BAdIs)
2. Select IMG activity for BAdI CVI_MAP_TITLE -> Select BAdI: Data Assignment of Form of Address from Customer/vendor to BP
3. Deactivate implementation CVI_MAP_TITLE_DIRECT and activate the BADI implementation to derive the Business Partner Category based on the form of address Create a Workbench request
s4h24 – Unit 6 Exercise 1
6
4. Look up BADI CVI_MAP_TITLE using transaction SE18
5. Double click on Implementations
6. The three implementations will be listed. Implementation CVI_MAP_BP_CATEGORY is now active based on the customizing setting Double click on Implementation CVI_MAP_BP_CATEGORY
s4h24 – Unit 6 Exercise 1
7
7. Double click on Implementing Class. 4 methods will be shown. Double click on method MAP_VENDOR_TITLE_BP_CREATE
8. The coding of this method will be shown. You can use push button ‘Signature’ to display the parameters of this method. The coding derives the Business Partner Category based on the settings of customizing table TSAD3. If only column ‘Person’ is selected for a certain address title, BP category ‘Person’ will be set. If only column ‘Group’ is selected for a certain address title, BP category ‘Group’ will be set. Otherwise, BP category will keep the standard value and the resulting Business Partner will end up with BP category ‘Organization’.
s4h24 – Unit 6 Exercise 1
8
9. Look up customizing table TSAD3 IMG -> Cross-Application Components -> SAP Business Partner -> Basic Settings -> Forms of Address -> Maintain Forms of Address
10. The customizing entries will be displayed. Based on the activated BAdI implementation, a customer or vendor with title ‘Ms.’ or ‘Mr.’ will become a Business Partner with category ‘Person’. If no title will be used, a BP of category ‘Organization’ will be created.
11. Test these scenarios: Create a Vendor with title ‘Ms.’ and check if the BP will be created with category ‘Person’. Create a Vendor with no title and check if the BP will be created with category ‘Organization’. Transaction XK01 -> use account group ‘YB01’, remove any organizational elements and enter a vendor number within the number
Example for a person:
s4h24 – Unit 6 Exercise 1
9
interval.
s4h24 – Unit 6 Exercise 1
10
12. Check the Business Partner category with transaction BP
13. Either continue directly with the exercise of unit 7 or suspend your instance of CAL solution 1. Re-activate it once you continue with unit 7. This is important to save cost.
s4h24 – Unit 6 Exercise 1
11
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. 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 SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distr ibutors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and serv ices 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.
Coding Samples Any software coding or code lines/strings (“Code”) provided in this documentation are only examples and are not intended for use in a production system environment. The Code is only intended to bett er explain and visualize the syntax and phrasing rules for certain SAP coding. SAP does not warrant the correctness or completen ess of the Code provided herein and SAP shall not be liable for errors or damages cause by use of the Code, except where such damages were caused by SAP with intent or with gross negligence.