SAP How-To Guide: Extend the. MDG Business Partner - Overview. Applies to: Summary

Transcription

1 SAP Hw-T Guide: Extend the MDG Business Partner - Overview Applies t: Supplier Gvernance (MDG-S) and Custmer Gvernance (MDG-C) running n SAP ECC 6 EhP 6 Master Data Gvernance and newer. Fr mre infrmatin, visit the Master Data Management hmepage. ( Summary SAP Master Data Gvernance prvides ut-f-the bx slutins fr the central management f master data bjects. Dmain-specific slutins include supplier gvernance (MDG-S), material gvernance (MDG-M), and financials gvernance (MDG-F). If yur dmain-specific slutin des nt fully meet requirements, yu can custmize and extend it. This guide prvides yu with the fundatin knwledge yu need t extend business partner data and its related gvernance slutins: custmer gvernance (MDG-C) and supplier gvernance (MDG-S). Authrs: Michael Theis, Lars Rueter Cmpany: SAP AG Created n: September 2013 Versin: SAP AG 1

2 Table f Cntents Intrductin... 4 Business Partners, Custmers and Suppliers... 4 Business Partner Gvernance (MDG-BP)... 4 Custmer Gvernance (MDG-C)... 5 Supplier Gvernance (MDG-S)... 5 Custmer Vendr Integratin (CVI)... 6 Multiple Assignments... 8 MDG Data Mdel and Access/Handler class cncept... 9 Sftware Layers... 9 Data Derivatin... 9 Access Classes Generic Handler Classes Handler Class fr Business Partner Gvernance (MDG-BP) Handler Class fr Multiple Assignments Handler Class fr Custmer Gvernance (MDG-C) Handler Class fr Supplier Gvernance (MDG-S) Mdeling and Implementatin fr the Generic Interactin Layer (genil) MDG-BP Multiple Assignments MDG-C Supplier Gvernance (MDG-S) User Interfaces Cntext Based Adaptatins MDG-BP Overview ABAP Object List Multiple Assignments Overview ABAP Object List Custmer Gvernance (MDG-C) Overview SAP AG 2

3 ABAP Object List: Generic Cmpnents ABAP Object List: Enterprise Search ABAP Object List: General Data ABAP Object List: Cmpany Cdes ABAP Object List: Dunning Areas ABAP Object List: Extended Withhlding Tax Types ABAP Object List: Sales Areas ABAP Object List: Partner Functins ABAP Object List: Tax Indicatrs ABAP Object List: Custmer-like UI ABAP Object List: Lean Vendr Creatin UI Supplier Gvernance (MDG-S) Overview ABAP Object List: Generic Cmpnents ABAP Object List: Enterprise Search ABAP Object List: General Data ABAP Object List: Cmpany Cdes ABAP Object List: Dunning Areas ABAP Object List: Extended Withhlding Tax Types ABAP Object List: Purchasing Organizatin ABAP Object List: Different Purchasing Data ABAP Object List: Partner Functins ABAP Object List: Sub-Ranges ABAP Object List: Vendr-like UI ABAP Object List: Lean Vendr Creatin UI Additinal Infrmatin Links 36 Hw-t Guides SAP Ntes Cpyright SAP AG 3

4 Intrductin This dcument prvides the basic infrmatin yu need t extend the SAP-delivered slutin fr business partner within MDG. The slutin fr business partner incrprates custmer gvernance (MDG-C) and supplier gvernance (MDG-S). In additin t explaining the key cncepts and implementatin details, this dcument links t guides that prvide real-life examples. The dcument is valid fr MDG in the area f Business Partner starting with enhancement package 6. Sme chapters cntain specific infrmatin being available nly in the MDG 6.1 release. Business Partners, Custmers and Suppliers MDG ffers different slutins in the business partner area. Business Partner Gvernance (MDG-BP) MDG-BP is the fundatin fr MDG-C and MDG-S. Each custmer and supplier is based upn a business partner. It reflects the cmmn SAP Business Partner (the ne yu can maintain in SAPGUI with transactin BP). The scpe f develpments fr business partner gvernance in EHP6 is as fllws: General Data (table BUT000) Only Organizatin Data Addresses Internatinal Address Versins Address Usages Cmmunicatin Data Only address dependent cmmunicatin data Telephne Numbers Mbile Numbers Fax Numbers Addresses Web Sites Rles Bank Accunts Identificatin Numbers Tax Numbers Industries The scpe f develpments fr business partner gvernance in MDG 6.1 is as fllws: Extended General Data (table BUT000) Persn Data 2013 SAP AG 4

5 Grup Data Relatinships Cmmn Relatinships Cntact Persn Relatinships including details and wrkplace address Custmer Gvernance (MDG-C) Custmer gvernance is an extensin f business partner gvernance. It adds the SAP ERP specific parts f custmer master data (the nes that are maintained in SAPGUI with transactins XD01/2/3) t business partner gvernance. EhP6 Scpe: General Data (table KNA1) MDG 6.1 Scpe: Cmpany Cdes (table KNB1) Dunning Areas (table KNB5) Extended Withhlding Tax Types (table KNBW) Sales Areas (table KNVV) Partner Functins (table KNVP) Tax Indicatrs (table KNVI) Cntact persns (table KNVK) via Business Partner Relatinships Supplier Gvernance (MDG-S) Supplier gvernance is an extensin f business partner gvernance. It adds the SAP ERP specific parts f vendr master data (the nes that are maintained in SAPGUI with transactins XK01/2/3) t business partner gvernance. It enables the maintenance f vendr's general data and thers like cmpany cde data, purchasing rganizatins, and s n. The scpe f develpments fr business partner gvernance in EHP6 is as fllws: General Data (table LFA1) Cmpany Cdes (table LFB1) Purchasing Organizatins (LFM1) The scpe f develpments fr business partner gvernance in MDG 6.1 is as fllws: Sub-Ranges (tables WYT1 & WYT1T) Dunning Areas (table LFB5) Extended Withhlding Tax Types (table LFBW) Different Purchasing Data (table LFM2) Partner Functins (table WYT3) 2013 SAP AG 5

6 Custmer Vendr Integratin (CVI) Custmer gvernance and supplier gvernance are bth based n business partner gvernance. In MDG the business partner is the leading entity. Using the MDG UIs a business partner is always created. Depending n the Custmer Vendr Integratin (CVI) cnfiguratin and the entered data, a custmer and/r vendr recrds is created in additin. Taking a detailed lk at the related database tables it is bvius, that sme fields are mre r less identical in the different entity types. CVI is a generic tl that is able t synchrnize parts f the business partner master data with the related ERP custmer and vendr master data and vice versa. MDG UI: Maintain Name 1 Activate Change Request SRM BUT000 SOA BUT000 LFA1 & KNA1 CVI Synchrnizatin ALE R/3 4.6C LFA1 & KNA1 The figure abve shws the flw f the field Name 1 as example. The data is maintained in the business partner part f the user interface fr either custmer gvernance r fr supplier gvernance. As sn as the related change request is apprved, data activatin stres the field in the business partner table BUT000. This triggers CVI, which creates an additinal entry in the related tables fr custmer master data (table KNA1) and vendr master data (table LFA1).One benefit f this behavir is the simplified data replicatin. If the newly created MDG recrds are sent t an SRM system, the system uses the business partner data. SRM neither knws the custmer nr the vendr since this is ERP specific data. If an (lder) ERP system is the target receiver, it is pssible t replicate either the custmer data, r the vendr data, r a cmbinatin f bth, in a direct way (fr example, using the cmmn DEBMAS r CREMAS IDcs). All recrds in all systems have the same value fr Name 1. CVI synchrnizes the fllwing segments and fields: General Data Names Search Terms Trading Partner Business Partner Categry 2013 SAP AG 6

7 ERP custmer and vendr d nt differentiate between rganizatins, persns and grups. Therefre all business partners are treated as rganizatins. Address Data The business partner can handle multiple addresses. This feature is nt available fr ERP s custmer and vendr. Therefre, nly the standard address is synchrnized. Cmmunicatin Data Only address dependent cmmunicatin data is synchrnized. Bank Accunts Industry Sectrs The business partner can handle multiple industry systems and sectrs. This feature is nt available fr ERP s custmer and vendr. Therefre, nly the standard industry sectr f the standard industry system is synchrnized. Tax Numbers The business partner stres tax numbers in a table frmat. ERP custmer and vendr use simple fields cmbined with a table fr Eurpean VAT Numbers. CVI takes care f the crrect synchrnizatin f the business partner table with the fields and tables fr custmer r vendr. When yu cnsider an extensin f MDG, yu can chse frm several ptins t add tables and fields. Yur chice strngly depends upn the fllwing questin: Which entity receives the additinal infrmatin? The fllwing scenaris are pssible: The new field r table is available nly in the business partner. The new field r table is available nly in the custmer r nly in the vendr. The new field r table is available in bth the business partner and in either the custmer r in the vendr. Each extensin requires a specific sequence f steps that must be implemented crrectly. Detailed hw-t guides explain each extensin ptin. CVI is used by MDG. It is neither develped nr maintained by MDG. The synchrnizatin happens during the activatin f master data, and always in the fllwing directin: frm the business partner t the custmer r the vendr. During the setup phase f Custmer Gvernance (MDG-C) and/r Supplier Gvernance (MDG-S) it is pssible t use the CVI Synchrnizatin Cckpit t create business partners frm existing custmers r vendrs. The abve mentined use cases require a valid cnfiguratin f the CVI custmizing. Yu can apply settings in Custmizing under Crss-Applicatin Cmpnents Master Data Synchrnizatin Custmer Vendr Integratin. MDG s cre scenari f central master data gvernance requires that yu set up Custmizing t enable the synchrnizatin directin BP t Custmer/Vendr. This invlves the fllwing tasks: 2013 SAP AG 7

8 Defining at least ne business partner rle that triggers the creatin f a custmer/vendr. It is pssible t define multiple rles. If yu d this, yu must assign the crrect rle when maintaining the user interface. If yu define nly ne rle, the system uses the rle autmatically when it stres the business partner in the active area. If yu use either the Custmer Like UI r the Vendr Like UI, yu must define a unique rle in custmizing. Neither f these user interfaces can use the rles list. As a result, it is nt pssible t add a rle manually t the current custmer/vendr. Defining a mapping f the business partner gruping t its related custmer/vendr accunt grup. The MDG UIs d nt enfrce the maintenance f the BP gruping. If a user des nt select any BP gruping, the system chses a default gruping based n the business partner ID in use. If a business partner ID is maintained, the default gruping fr external numbering is used. If n business partner ID is maintained, the default gruping fr internal numbering is used. Yu must crrectly cnfigure the related BP grupings when applying Custmizing settings fr Custmer Vendr Integratin. The grup mapping defines the key mapping implicitly since each Business Partner /Custmer/Vendr grup is assigned t a specific number range. Ensure that the respective number ranges match, especially if yu use the same numbers fr the BP and fr the custmer/vendr. The first custmer/vendr that is added t a BP is the standard assignment. This assignment derives its accunt grup accrding t cnfiguratin specified in Custmizing settings fr Custmer Vendr Integratin. The accunt grup cannt be changed manually in the MDG UIs. Only additinal assignments allw the manual selectin f the accunt grup. If yu use either the Custmer Like UI r the Vendr Like UI, nly the fllwing numbering cmbinatins fr Business Partners t custmers/vendrs are allwed: BP internal and C/S internal (results in different IDs) BP internal and C/S external with same number (results in identical IDs) BP external and C/S external with same number (results in identical IDs) Other cmbinatins wuld cause a deadlck in the UI. Making sure yu check if further mapping n segment level (e.g. industry sectrs) is required. MDG prcesses d nt require that yu set up the synchrnizatin directin Custmer/Vendr t BP. This directin is nly useful if yu want t transfer existing custmers r vendrs t BPs. Techniques fr ding this include using the MDS Lad Cckpit functinality f CVI. A detailed descriptin f the CVI is available in the SAP Help. Multiple Assignments The Multiple Assignment is a new sub-bject used by MDG-C and MDG-S. It was intrduced in release EhP6. In EhP5, MDG-S was nly able t link a single business partner with a single vendr. This restrictin existed due t the reuse f the Custmer Vendr Integratin (CVI) by MDG SAP AG 8

9 Starting with EhP6, Multiple Assignments allw yu t link ne r mre custmers r ne r mre vendrs t a single business partner. As this is MDG-specific functinality it is nly available n the MDG hub and is nt available in the MDG client systems. MDG Data Mdel and Access/Handler class cncept The MDG data mdel fr business partners, custmers and suppliers is mdel BP. The entity types f the mdel are reuse entity types. The actual data f the mdel is nly stred in MDG (staging) tables as lng as the current recrd is within a gvernance prcess. As sn as the recrd is activated, its data is stred in existing database tables f the SAP system (fr example the business partner is stred in table BUT000, the custmer is stred in table KNA1, the vendr is stred in LFA1, and s n). This requires the implementatin f access classes that read and stre the data in the reuse area. Frm EhP6, a different implementatin cncept fr the access class is used. In EhP6, there is a single access class that distributes all calls t different, bject-specific handler classes. This allws an extensin f the access class simply by creating and registering a custm handler class. The access class is nly respnsible fr cntrlling the calls. The actual executin f the calls, which invlves, fr example reading data r saving data, is implemented within the handler classes. Fllwing the segregatin f duty principle there is a handler fr each bject (in ther wrds ne fr business partner, ne fr multiple assignment, ne fr custmer, and ne fr supplier). This handler alne is fully respnsible fr the related bject (in ther wrds, the supplier handler must never change the custmer bject). Sftware Layers Frm a technical perspective, the MDG data mdel BP, its access classes, and its handler classes are develped in tw different sftware layers. The general business partner cmpnents are built in the MDG fundatin layer whereas the custmer and supplier cmpnents belng t the MDG applicatin layer. This is imprtant fr the further intrductin f access and handler classes. Data Derivatin The data derivatin is part f the SAP handler classes. Yu can use data derivatin t create, change, r delete data based upn either user actins in the UI r data inbund r bth. An example is the autmated creatin f default partner functins as sn as a sales area is created in the custmer UI. Frm the UI perspective, a derivatin is triggered during the start f the UI applicatin as well as during each UI rund-trip triggered by the user. During data inbund derivatins are executed, t. The SAP handlers implement the derivatin in tw phases. 1. The handlers analyze the current changes applied in the User Interface r in inbund prcessing. The applicatin f these changes cmes via the framewrk t the handler class. The data is buffered within the handlers. If any actins are required due t the new data, related tasks are being buffered, t. Related cding is available in the methd BUFFER_DERIVED_DATA f the handler classes SAP AG 9

10 2. The handlers perfrm the derivatin accrding t the given tasks and buffered data. Related cding is available in the methd DERIVE_DATA f the handler classes. There is anther special derivatin ptin that is triggered by a change f the business partner key. In that case the MDG framewrk calls the handler methd DERIVE_DATA_ON_KEY_CHANGE. Access Classes Access classes are required t rute the calls by the MDG framewrk t the specific handler implementatins. Since MDG-BP, MDG-C and MDG-S cnsist f multiple sftware layers, a single access class wuld nt be sufficient fr this need. Therefre, the implementatin cnsists f three classes in a hierarchy with inheritance: 1. CL_MDG_BS_BP_ACCESS_MASTER The master class is the ne being called by the MDG framewrk. Its bject instance actually depends n the current sftware layer it is running in. In the MDG fundatin layer, it is a reference f class CL_MDG_BS_FND_ACCESS whereas in the MDG applicatin layer it is a reference f class CL_MDG_ECC_ACCESS. The class implements the MDG framewrk's access interface and prvides sme generic functinality. 2. CL_MDG_BS_FND_ACCESS This class is the MDG fundatin layer implementatin. It cntains bth generic implementatins usable fr all entity types f MDG-BP Custmer Gvernance (MDG-C) and Supplier Gvernance (MDG-S) as well specific cding fr all entity types f MDG-BP. 3. CL_MDG_BS_ECC_ACCESS This class is the MDG applicatin layer implementatin. It cntains nly cding fr all entity types f Custmer Gvernance (MDG-C) and Supplier Gvernance (MDG-S). If yu want t create an extensin f MDG, yu d nt have t enhance existing access classes respectively t create an access class f yur wn. We recmmend that yu implement a specific handler class instead. All calls frm the access t the handler classes are triggered by the access class. Therefre the access class cllects a list f registered handlers cnsisting f bth predefined SAP handlers as well as custm handlers first. Then the access class calls each handler within a lp. It is nt guaranteed that the handler class prvides a fixed sequence fr the calls f the access class t the different handler classes Generic Handler Classes The link between an access class and a handler class is the handler interface IF_MDG_BS_BP_ACCESS_HANDLER. A handler class must implement this interface. Since majr parts f the applicatin lgic needed fr MDG-BP, Custmer Gvernance (MDG-C) and Supplier Gvernance (MDG-S) is mre r less the same fr each bject, tw abstract classes (again in a hierarchy with inheritance t supprt the needs f the different sftware layers) prvide this cmmn implementatin: 2013 SAP AG 10

11 1. CL_MDG_BS_FND_HANDLER This class is the MDG fundatin layer implementatin. It cntains generic and reusable cding fr all entity types f MDG-BP, Custmer Gvernance (MDG-C) and Supplier Gvernance (MDG-S). It intrduces several attributes and cnstants used fr the data derivatin (e.g. the MDG-BP specific buffer GS_BP_EXTERN_DERIVED_DATA). 2. CL_MDG_BS_ECC_HANDLER This class is the MDG applicatin layer implementatin. It cntains nly reusable cding fr multiple assignments, Custmer Gvernance (MDG-C) and Supplier Gvernance (MDG-S). It intrduces several attributes and cnstants used fr the data derivatin, such as the buffer fr MDG-C and MDG-S (GS_MLT_AS_DERIVED_DATA) and task buffers (GV_BP_ROOT_TASK r GT_MLTAS_TASK). The abve-mentined classes are abstract. A few public classes that frm the abstract classes and prvide further bject-specific lgic. The classes fllw the segregatin f duty principle. A single handler is respnsible fr a single bject nly. The fllwing chapters intrduce the classes in detail. If yu want t extend MDG by creating yur wn handler classes, there are several pssibilities. A general recmmendatin fr the creatin f a custm handler class is that yur new class inherits frm either the abstract fundatin handler r frm the applicatin handler. Deciding which parent t chse frm the available SAP handlers depends n the actual use case f the extensin. In sme cases, it might even make sense t chse ne f the SAP predefined bject handlers as a parent. Handler Class fr Business Partner Gvernance (MDG-BP) The MDG-BP specific handler class is CL_MDG_BS_BP_HANDLER. It inherits frm class CL_MDG_BS_FND_HANDLER. It prvides the business partner-specific implementatin f the handler interface. This class is a valid parent fr a custm handler class if the use case is a mdificatin r enhancement f the existing applicatin lgic f the business partner. Handler Class fr Multiple Assignments The multiple assignment specific handler class is CL_MDG_BS_MLT_ASSGNMNT_HANDLER. It inherits frm class CL_MDG_BS_ECC_HANDLER. It prvides the multiple assignment-specific implementatin f the handler interface. This class is valid parent fr a custm handler class if the use case is a mdificatin r enhancement f the existing applicatin lgic f the multiple assignments. Handler Class fr Custmer Gvernance (MDG-C) The MDG-C specific handler class is CL_MDG_BS_CUST_HANDLER. It inherits frm class CL_MDG_BS_ECC_HANDLER. It prvides the custmer specific implementatin f the handler interface SAP AG 11

12 This class is valid parent fr a custm handler class if the use case is a mdificatin r enhancement f the existing applicatin lgic f the custmer. Handler Class fr Supplier Gvernance (MDG-S) The MDGS specific handler class is CL_MDG_BS_SUPPL_HANDLER. It inherits frm class CL_MDG_BS_ECC_HANDLER. It prvides the supplier (vendr) specific implementatin f the handler interface. This class is valid parent fr a custm handler class if the use case is a mdificatin r enhancement f the existing applicatin lgic f the supplier (vendr). Mdeling and Implementatin fr the Generic Interactin Layer (genil) Since the MDG BP UIs are built using Flrplan Manager (FPM) and its Business Object Layer (BOL) / Generic Integratin Layer (genil) integratin, the genil mdel builds the fundatin f the UI. The genil layer cnsists f a genil mdel and ne r mre genil implementatin classes fr the specific mdel. genil mdels are defined and maintained in the SAP backend with transactin GENIL_MODEL_BROWSER. genil implementatin classes are built within the cmmn transactins SE24 and/r SE80. The genil mdel f MDG-BP, MDG-C and Supplier Gvernance (MDG-S) reflects the intrduced separatin f bjects, t. The basis is the business partner genil mdel cmpnent BUPA which is extended by custmer and supplier in the genil mdel enhancement BUPA_CUSP. A genil mdel basically cnsists f bjects and relatins. Objects cnsist f attributes. Each attribute reflects a usable field fr the user interface. Relatins cnnect ne bject t anther. They define the cardinality f bjects in a relatin, t. Relatins are reflected in the user interface by the wires (cnnectins) frm ne UIBB t anther. It is mandatry that the UIBB hierarchy in the verview page is cnsistent t the genil bject hierarchy as defined by the relatins. The imprtant parts f an bject are the key structure and the attribute structure. Bth must be existing ABAP DDIC structures. The key structure is used internally by genil. The sub-bject s key structure must always cntain the key fields f its parent. The attribute structure is used by FPM during the UI creatin. It defines the field catalgue that is available fr creating a list r frm UIBB. If a key field shall be visible respectively maintainable in the UI, it must be part f the attribute structure, t. Each genil mdel cmpnent respectively enhancement requires exactly ne implementatin class. With regards t the cmplexity f the MDG-BP, MDG-C and Supplier Gvernance (MDG-S) slutin this might be cnsidered as a "limitatin" since the MDG slutins wuld need implementatin classes fr each specific bject. T vercme this "limitatin" the MDG-BP, MDG-C and MSG-S genil implementatin cnsists f a class hierarchy where each class inherits frm its parent class: 2013 SAP AG 12

13 1. CL_MDG_BS_GENIL: the generic genil implementatin fr all MDG slutins 2. CL_BS_GENIL_BUPA: the genil implementatin fr MDGBP 3. CL_BS_GENIL_MLT_ASSIGNMENTS: the genil implementatin fr multiple assignments 4. CL_BS_GENIL_SUPPLIER: the genil implementatin fr MDGS 5. CL_BS_GENIL_CUSTOMER: the genil implementatin fr all MDGC The last class CL_BS_GENIL_CUSTOMER is the ne that is defined in the genil mdel enhancement BUPA_CUSP. The class hierarchy ensures that always all classes are executed during design and runtime f the UI. It is abslutely mandatry that each custm enhancement f the genil mdel which needs t use an wn implementatin class inherits frm CL_BS_GENIL_CUSTOMER. Otherwise it might cme t unfreseen errrs during design and runtime f the UI. The generic implementatin in class CL_MDG_BS_GENIL cntains a type based mapping frm the UI data structures int the MDG entity data structures and vice versa. This mapping wrks fine if the used data type f the surce and target field is identical. If this is nt the case, r if multiple fields are using the same data type, the generic mapping fails which might lead t disappearing values in the UI. T reslve this issue, it is pssible t re-define ne f the fllwing methds: IF_BS_TYPECASTED_MAP_ASSISTANT~TARGET_FIELD_NAME The methd allws defining a strict field mapping based upn the surce structure and field name t the target structure and field name. IF_BS_TYPECASTED_MAP_ASSISTANT~TYPE_ALTERNATIVE The methd allws defining an alternative data type fr the generic type based mapping based upn the surce structure and field type t the target structure and field type. Example implementatins are pre-defined by SAP in the abve mentined bject-specific classes (items 2 t 4). MDG-BP The fllwing genil bjects are mdeled. 1. BP_Rt representing the rt business partner bject. 2. BP_Grup being a sub-bject f BP_Rt representing the Grup specific business partner data. 3. BP_Organizatin being a sub-bject f BP_Rt representing the Organizatin specific business partner data. 4. BP_Persn being a sub-bject f BP_Rt representing the Persn specific business partner data. 5. ADDR_Rt representing the address. 6. ADDR_CmmPhne representing the phne cmmunicatin data f an address. 7. BP_Relatin representing the business partner relatinships. 8. BP_Cntact_Persn being a sub-bject f BP_Relatin representing the special cntact persn relatin relatinship. 9. BP_Address being a sub-bject f ADDR_Rt representing the business partner address SAP AG 13

14 10. BP_AddressUsage representing the usage f an address. 11. BP_AddressVersin_Organizatin representing the internatinal address versins fr business partners f type Organizatin. 12. BP_AddressVersin_Persn representing the internatinal address versins fr business partners f type Persn. 13. BP_BankAccunt representing the bank accunt resp. bank details. 14. BP_Cmm representing the address. 15. BP_CmmFax representing the fax data. 16. BP_CmmMbile representing the mbile phne data. 17. BP_CmmPhne representing the cmmn phne data. 18. BP_CmmURI representing the web page data. 19. BP_IdentificatinNumber representing the identificatin number data. 20. BP_Industry representing the industry sectrs. 21. BP_PersnVersin representing persn data fr internatinal address versins. 22. BP_Rle representing business partner rles. 23. BP_TaxNumbers representing tax infrmatin data. 24. BP_WrkplaceAddress representing the wrkplace address f a cntact persn. 25. BP_Cmm representing the wrkplace address f a cntact persn. 26. BP_CmmFax representing the wrkplace fax data f a cntact persn. 27. BP_CmmMbile representing the wrkplace mbile phne data f a cntact persn. 28. BP_CmmPhne representing the wrkplace cmmn phne data f a cntact persn. 29. BP_CmmURI representing the wrkplace web page data f a cntact persn. 30. BP_QueryRt representing a static query bject usable fr searching business partners. 31. BP_DynamicQueryMDGPrviderRt representing a dynamic query bject usable fr searching business partners. Multiple Assignments The fllwing genil bjects are mdeled. 1. BP_MultipleAssignment representing the multiple assignments. The fllwing genil relatins are mdeled. All relatins link the business partner rt bject (BP_Rt) with the multiple assignment bject (BP_MultipleAssignment). Name BP_MultipleAssignmentRel Descriptin This is a generic 0:n relatin. It is nt used by the SAP standard. It prepares a custm multiple assignment categry. CU_MultipleAssignmentsRel This is a custmer specific 0:n relatin. It is used by MDG-C. Using filter mechanisms it ensures that during MDG-C usage nly custmers are visible in the UI SAP AG 14

15 Name CU_StandardAssignmentRel Descriptin This is a custmer specific 0:1 relatin. It is used by MDG-C. Using filter mechanisms it ensures that during MDG-C usage nly the standard assignment fr custmers is visible in the UI. SP_MultipleAssignmentsRel This is a supplier specific 0:n relatin. It is used by Supplier Gvernance (MDG-S). Using filter mechanisms it ensures that during MDG-S usage nly vendrs are visible in the UI. SP_StandardAssignmentRel This is a supplier specific 0:1 relatin. It is used by Supplier Gvernance (MDG-S). Using filter mechanisms it ensures that during MDG-S usage nly the standard assignment fr vendrs is visible in the UI. All genil specific ABAP bjects referring t multiple assignments are available in package MDG_BS_ECC_BP_MLT_ASSGMNT. The implementatin class is CL_BS_GENIL_MLT_ASSIGNMENTS. The nly key structure is BSS_BPIL_MLT_ASSGMNT_KEY. It is used by several bjects. It is the key fr multiple assignments (BP_MultipleAssignment) as well as custmer and vendr general data (CU_GeneralData and SP_GeneralData). The latter ne is pssible due t the fact that the multiple assignments key already uniquely identifies a custmer and vendr general data bject. The nly attribute structure is BSS_BPIL_MLT_ASSGMNT_ATTR fr bject BP_MultipleAssignment. MDG-C The fllwing genil bjects are mdeled. 1. CU_GeneralData representing the general data. 2. CU_CmpanyCde representing the cmpany cdes. 3. CU_DunningArea representing the dunning areas. 4. CU_WithhldingTaxType representing the extended withhlding tax types. 5. CU_SalesArea representing the sales areas. 6. CU_PartnerFunctin representing the partner functins. 7. CU_TaxIndicatr representing the tax indicatrs. The fllwing genil relatins are mdeled. Name CU_AssignedCustmerRel Descriptin This is a custmer specific 0:1 relatin. It links the custmer multiple assignment (BP_MultipleAssignment) with its general data (CU_GeneralData) SAP AG 15

16 Name CU_AssignedCmpanyCdesRel Descriptin This is a custmer specific 0:n relatin. It links the custmer multiple assignment (BP_MultipleAssignment) with its cmpany cdes (CU_CmpanyCde). CU_CmpDunningAreasRel This is a custmer specific 0:n relatin. It links the custmer cmpany cde (CU_CmpanyCde) with its dunning areas (CU_DunningArea). CU_CmpWithhldingTaxesRel This is a custmer specific 0:n relatin. It links the custmer cmpany cde (CU_CmpanyCde) with its extended withhlding tax types (CU_WithhldingTaxType). CU_AssignedSalesAreasRel This is a custmer specific 0:n relatin. It links the custmer multiple assignment (BP_MultipleAssignment) with its sales areas (CU_SalesArea). CU_SalesPartnerFunctinsRel This is a custmer specific 0:n relatin. It links the custmer sales area (CU_SalesArea) with its partner functins (CU_PartnerFunctin). CU_AssignedTaxIndicatrsRel This is a custmer specific 0:n relatin. It links the custmer multiple assignment (BP_MultipleAssignment) with its tax indicatrs (CU_TaxIndicatr). This relatin is used fr displaying all tax indicatrs f a custmer. CU_SalesTaxIndicatrsRel This is a custmer specific 0:n relatin. It links the custmer sales area (CU_SalesArea) with its tax indicatrs (CU_TaxIndicatr). This relatin is used fr displaying the tax indicatrs per sales area in the UI. All genil specific ABAP bjects referring t custmers are available in package MDG_BS_ECC_CUSTOMER_GENIL. The implementatin class is CL_BS_GENIL_CUSTOMER. Key Structure BSS_CUIL_COMPANY_CODE_KEY Descriptin Used fr bject CU_CmpanyCde. It includes the multiple assignment keys and adds the cmpany cde key. BSS_CUIL_DUNNING_KEY Used fr bject CU_DunningArea. It includes the cmpany cde keys and adds the dunning area key. BSS_CUIL_WHTAX_KEY Used fr bject CU_WithhldingTaxType. It includes the cmpany cde keys and adds the withhlding tax keys. The cuntry is required due t MDG mdeling. BSS_CUIL_SALES_AREA_KEY Used fr bject CU_SalesArea. It includes the multiple assignment keys and adds the sales areas keys SAP AG 16

17 Key Structure BSS_CUIL_FUNCTION_KEY Descriptin Used fr bject CU_PartnerFunctin. It includes the sales area keys and adds the partner functin keys. BSS_CUIL_TAXINDICATOR_KEY Used fr bject CU_TaxIndicatr. It includes the multiple assignment keys and adds the tax indicatr keys. Althugh tax indicatrs are nly calculated if a sales area is maintained, they d nt depend n the sales area keys. Attribute Structure BSS_CUIL_GENERAL Descriptin Used fr bject CU_GeneralData. The custmer ID is treated as a cmmn attribute. BSS_CUIL_COMPANY_CODE Used fr bject CU_CmpanyCde. It includes the cmpany cde key as attribute t enable its maintenance in the UI. BSS_CUIL_DUNNING Used fr bject CU_DunningArea. It includes the cmpany cde key as attribute t enable its maintenance in the UI. BSS_CUIL_WHTAX Used fr bject CU_WithhldingTaxType. It includes nly the withhlding tax type as attribute t enable its maintenance in the UI. The cuntry is nt displayed. BSS_CUIL_SALES_AREA Used fr bject CU_SalesArea. It includes the sales area keys as attributes t enable their maintenance in the UI. BSS_CUIL_FUNCTION Used fr bject CU_PartnerFunctin. It includes the partner functin keys as attributes t enable their maintenance in the UI. The partner cunter is nt displayed in the UI. BSS_CUIL_TAXINDICATORS Used fr bject CU_TaxIndicatr. It includes the tax indicatr keys as attributes t enable their display in the UI. Supplier Gvernance (MDG-S) The fllwing genil bjects are mdeled. 1. SP_GeneralData representing the general data. 2. SP_CmpanyCde representing the cmpany cdes. 3. SP_DunningArea representing the dunning areas. 4. SP_WithhldingTaxType representing the extended withhlding tax types. 5. SP_PurchasingOrg representing the purchasing rganizatin. 6. SP_PurchasingOrg2 representing the different purchasing data SAP AG 17

18 7. SP_PartnerFunctin representing the partner functins. 8. SP_Subrange representing the vendr sub-ranges. The fllwing genil relatins are mdeled. Name SP_AssignedSupplierRel Descriptin This is a supplier specific 0:1 relatin. It links the supplier multiple assignment (BP_MultipleAssignment) with its general data (SP_GeneralData). SP_AssignedCmpanyCdesRel This is a supplier specific 0:n relatin. It links the supplier multiple assignment (BP_MultipleAssignment) with its cmpany cdes (SP_CmpanyCde). SP_SingleCmpanyCdeRel This is a supplier specific 0:1 relatin. It links the supplier multiple assignment (BP_MultipleAssignment) with a single cmpany cde (SP_CmpanyCde). It is used by the lean creatin UI. SP_CmpDunningAreasRel This is a supplier specific 0:n relatin. It links the supplier cmpany cde (SP_CmpanyCde) with its dunning areas (SP_DunningArea). SP_CmpWithhldingTaxesRel This is a supplier specific 0:n relatin. It links the supplier cmpany cde (SP_CmpanyCde) with its extended withhlding tax types (SP_WithhldingTaxType). SP_AssignedPurchasingOrgsRel This is a supplier specific 0:n relatin. It links the supplier multiple assignment (BP_MultipleAssignment) with its purchasing rganizatins (SP_PurchasingOrg). SP_SinglePurchasingOrgRel This is a supplier specific 0:1 relatin. It links the supplier multiple assignment (BP_MultipleAssignment) with a single purchasing rganizatin (SP_PurchasingOrg). It is used by the lean creatin UI. SP_PurchOrgPurchasingOrg2Rel This is a supplier specific 0:n relatin. It links the supplier purchasing rganizatin (SP_PurchasingOrg) with its different purchasing data (SP_PurchasingOrg2). SP_PurchOrgPartnerFunctinsRel This is a supplier specific 0:n relatin. It links the supplier purchasing rganizatin (SP_PurchasingOrg) with its partner functins (SP_PartnerFunctin). SP_AssignedSubrangesRel This is a supplier specific 0:n relatin. It links the supplier multiple assignment (BP_MultipleAssignment) with its sub-ranges (SP_Subrange) SAP AG 18

19 All genil specific ABAP bjects referring t suppliers are available in package MDG_BS_ECC_SUPPLIER_GENIL. The implementatin class is CL_BS_GENIL_SUPPLIER. Key Structure BSS_SPIL_COMPANY_CODE_KEY Descriptin Used fr bject SP_CmpanyCde. It includes the multiple assignment keys and adds the cmpany cde key. BSS_SPIL_DUNNING_KEY Used fr bject SP_DunningArea. It includes the cmpany cde keys and adds the dunning area key. BSS_SPIL_WHTAX_KEY Used fr bject SP_WithhldingTaxType. It includes the cmpany cde keys and adds the withhlding tax keys. The cuntry is required due t MDG mdeling. BSS_SPIL_PURCHASING_ORG_KEY Used fr bject SP_PurchasingOrg. It includes the multiple assignment keys and adds the purchasing rganizatin key. BSS_SPIL_PURCHASING_ORG2_KEY Used fr bject SP_PurchasingOrg2. It includes the purchasing rganizatin key and adds the different purchasing data keys. BSS_SPIL_FUNCTION_KEY Used fr bject SP_PartnerFunctin. It includes the purchasing rganizatin key and adds the partner functin keys. BSS_SPIL_SUBRANGE_KEY Used fr bject SP_Subrange. It includes the multiple assignment keys and adds the sub-range keys. Attribute Structure BSS_SPIL_GENERAL Descriptin Used fr bject SP_GeneralData. The vendr ID is treated as a cmmn attribute. BSS_SPIL_COMPANY_CODE Used fr bject SP_CmpanyCde. It includes the cmpany cde key as attribute t enable its maintenance in the UI. BSS_SPIL_DUNNING Used fr bject SP_DunningArea. It includes the cmpany cde key as attribute t enable its maintenance in the UI. BSS_SPIL_WHTAX Used fr bject SP_WithhldingTaxType. It includes nly the withhlding tax type as attribute t enable its maintenance in the UI. The cuntry is nt displayed. BSS_SPIL_PURCHASING_ORG Used fr bject SP_PurchasingOrg. It includes the purchasing rganizatin key as attribute t enable its maintenance in the UI SAP AG 19

20 Attribute Structure BSS_SPIL_PURCHASING_ORG2 Descriptin Used fr bject SP_PurchasingOrg2. It includes the different purchasing data keys as attributes t enable their maintenance in the UI. BSS_SPIL_FUNCTION Used fr bject SP_PartnerFunctin. It includes the partner functin keys as attributes t enable their maintenance in the UI. The partner cunter is nt displayed in the UI. BSS_SPIL_SUBRANGE Used fr bject SP_Subrange. It includes the sub-range keys as attributes t enable their display in the UI. User Interfaces The MDG UIs are built with the flr plan manager (FPM) using the Business Object Layer (BOL) / Generic Integratin Layer (genil) technlgy. The UI uses a specific genil mdel that differs frm the actual MDG BP mdel used fr data gvernance. Sme advantages t be mentined are: Lse cupling f the UIs t the MDG specific prcesses High flexibility fr the creatin f the UIs. The huge amunt f fields t be displayed is split int small UI Building Blcks (UIBBs). UIBBs supprt lists, frms and special kinds like pp-ups, search input and search results. Pssibility t create bject specific UIs t create a cmmn lk and feel and/r a similarity f the MDG UI cmpared t the SAPGUI maintenance transactins Reuse f existing tables, structures and fields (including naming) during the UI creatin General infrmatin abut FPM and its functinality is available in the FPM Ckbk n SDN. Cntext Based Adaptatins A cntext based adaptatin (CBA) is a FPM cncept that allws changing the UI in a flexible way based upn given values (e.g. applicatin parameters, user input, and thers). A CBA cnsists f an Adaptatin Schema that cnsists f ne r mre Adaptatin Dimensins. Using bth it is pssible t create varius adaptatins f the UI (e.g. a different layut f an verview page (OVP), r additinal/remved rw actins within a list UIBB, and s n). It is pssible t cmbine several dimensins t create a very specific adaptatin. The CBA cncept is based n the cmmn FPM event handling. It is pssible t trigger ne r mre CBA events that are handled by FPM's event lp prcessing. Refer t chapter Cntext Based Adaptatins (CBA) in the FPM Ckbk n SDN fr mre details SAP AG 20

21 The layut f an OVP can nly be changed with a CBA during the startup f the applicatin. It is nt pssible t change the OVP (e.g. the sequence f UIBBs) using a CBA during UI rund-trips. CBAs can nly change the layut f single UIBBs fr each rund-trip. FPM's event handling cncept allws triggering multiple CBA events during ne UI rund-trip. But FPM des nt cumulate the dimensin infrmatin given within each event. Cnsider a scenari with the fllwing sequence f events: 1. A first event triggers a CBA fr dimensin ACTION (fr example by defining the value DELETE t trigger the Mark fr Deletin UI), 2. A secnd CBA event cntains nly sme infrmatin fr a different dimensin withut the dimensin ACTION. In this scenari, the CBA fr the ACTION will nt be NOT prcessed since its value is reset t initial Still, there is a pssibility t trigger cmplex CBAs described in the related use case Trigger my wn CBA Event. The SAP delivered UIs supprt and use CBAs. There is a predefined schema BP_ADAPTS having several dimensins that are actively used within the UIs. The actual UI that is being displayed t a user in the web brwser is determined frm varius cmpnents f the UI cnfiguratin: Persnalizatin Enhancements Cntext Based Adaptatins Base Cnfiguratin The general rule is that the persnalizatin is the strngest cmpnent. This is best explained with an example. The base cnfiguratin defines the verview page as a list f UIBBs. Since a user des nt want t scrll, he r she creates a persnalizatin f the page intrducing a stacking f the UIBBs in tab-strips. A UI designer decides t create a cntext based adaptatin that sets a single UIBB t hidden and excluded frm event lp. All users nt having a persnalizatin will nt see this UIBB anymre. The user with the persnalizatin set is unaffected by this change. This is because the UIBBs that are hidden and excluded frm event lp still belng t the OVP. They can be added t the OVP using persnalizatin. Since the user has created a persnalizatin that shws the UIBB (the persnalizatin was created befre the CBA), the UIBB is still visible. T exclude the UIBB yu must either reset persnalizatin r delete the UIBB in the CBA SAP AG 21

22 MDG-BP Overview ABAP Object List Multiple Assignments Overview The multiple assignment UI cnsists f re-usable cmpnents nly. There is n specific OVP. There are several lists available fr the different assignment categries f business partner, custmer and supplier. This simplifies the creatin f bject specific OVPs. It allws the usage f several multiple assignment lists n a single OVP. Additinally there is a single frm fr maintaining the multiple assignment data. All UI specific ABAP bjects fr the multiple assignments are available in package MDG_BS_ECC_BP_MLT_ASSGMNT. ABAP Object List The genil bject defining the field catalgue is BP_MultipleAssignment. Class CL_BS_BP_GUIBB_MLT_ASSIGNMENTS is the respnsible feeder class fr the belw mentined list UIBBs. List UIBB BS_BP_MLT_ASSIGNMENTS Descriptin A cmmn list fr assignments that is nt used by the SAP delivered UI cnfiguratins. The list can be used t add custm assignment categries t the UI. BS_CU_MLT_ASSIGNMENTS The custmer specific list that links the business partner with ne r mre SAP ERP custmers. BS_SP_MLT_ASSIGNMENTS The supplier specific list that links the business partner with ne r mre SAP ERP vendrs. Class CL_BS_BP_GUIBB_MLT_ASSIGNMENT is the respnsible feeder class fr the frm UIBB BS_BP_MLT_ASSIGNMENT. This is a cmmn frm fr assignments that is nt used by the SAP delivered UI cnfiguratins. It can be used t maintain custm assignment categries in details SAP AG 22

23 Custmer Gvernance (MDG-C) Overview The Custmer Gvernance (MDG-S) UI prvides several independent UI applicatins fr maintaining supplier master data. All applicatins re-use the business partner UI and either change r extend it specifically fr the supplier. User Interface BS_OVP_CU Descriptin Main UI fr custmer gvernance. Reuses the verview page fr the business partner UI. Extends this page with the custmer multiple assignments list. This list is the starting pint fr the maintenance f ERP custmer master data. The UI cnsists f several edit pages with frms and list User Interface Building Blcks (UIBB). BS_OVP_CU_VL Referred t as the custmer-like user interface. Des nt use multiple assignments. Layut is synchrnized, as far as pssible, with the SAP GUI transactins used t maintain custmers. All UI specific ABAP bjects fr the custmer are available in package MDG_BS_ECC_CUSTOMER_BOLUI. ABAP Object List: Generic Cmpnents The main applicatin cnfiguratin is BS_OVP_CU. Starting this applicatin the verview page BS_CU_OVP is called with the applicatin specific cmmunicatr setting as defined in BS_OVP_CU. Any custmer UI specific messages are stred within message class MDG_BS_CUST_BOLUI. ABAP Object List: Enterprise Search The enterprise search template includes custmer attributes like the custmer ID. T reflect this within the search UIBB, a custmer specific search UIBB BS_CU_DQUERY_ES is prvided. Its feeder class is CL_BS_CU_GUIBB_DQUERY. ABAP Object List: General Data The genil bject defining the field catalgue is CU_GeneralData SAP AG 23

24 Class CL_BS_CU_GUIBB_GENERAL_DATA is the respnsible feeder class fr the belw mentined frm UIBBs. The class is a jin feeder since it handles bth the multiple assignments and custmer general data attributes. List UIBB BS_CU_GEN_ADDITIONAL Descriptin A frm fr the "additinal data" segment f the custmer's general data. BS_CU_GEN_ALL A frm cnsisting f all segments f the custmer's general data. This frm is currently nt used by the SAP delivered UI cnfiguratins. It culd be used t replace the multiple single frm UIBBs, e.g. in case f perfrmance issues. BS_CU_GEN_BLOCK_DEL A frm fr the "blcking and deletin flag" segments f the custmer's general data. BS_CU_GEN_CONTROL A frm fr the "cntrl data" segment f the custmer's general data and the multiple assignment attributes. BS_CU_GEN_EXPORT BS_CU_GEN_MARKETING BS_CU_GEN_PAYMENT A frm fr the "exprt data" segment f the custmer's general data. A frm fr the "marketing" segment f the custmer's general data. A frm fr the "payment transactins" segment f the custmer's general data. BS_CU_GEN_TAXINFORMATION A frm fr the "tax infrmatin" segment f the custmer's general data. ABAP Object List: Cmpany Cdes The genil bject defining the field catalgue is CU_CmpanyCde. Class CL_BS_CU_COMPANY_CODES is the respnsible feeder class fr the list UIBB BS_CU_COMPANY_CODES. In the standard UI the list is part f the custmer s general data edit page. It shws the cmpany cde key and descriptin nly. It is read-nly since the actual data is maintained by frms n a specific edit page. Class CL_BS_CU_COMPANY_CODE is the respnsible feeder class fr the belw mentined frm UIBBs. Frm UIBB BS_CU_COMPANY_CODE Descriptin A frm fr displaying the key fields f custmer s cmpany cde SAP AG 24

25 Frm UIBB BS_CU_ COMPANY_CODE_ALL Descriptin A frm cnsisting f all segments f the custmer's cmpany cde. This frm is currently nt used by the SAP delivered UI cnfiguratins. It culd be used t replace the multiple single frm UIBBs, e.g. in case f perfrmance issues. BS_CU_COMPANY_CODE_BLOCK_DEL A frm fr the "blcking and deletin flag" segments f the custmer's cmpany cde. BS_CU_COMPANY_CODE_ACCOUNTING A frm fr displaying the accunting infrmatin segment f the custmer s cmpany cde. BS_CU_COMPANY_CODE_INTEREST A frm fr displaying the interest calculatin data segment f the custmer s cmpany cde. BS_CU_COMPANY_CODE_REFERENCE A frm fr displaying the reference data segment f the custmer s cmpany cde. BS_CU_COMPANY_CODE_PAYM_DATA A frm fr displaying the payment data segment f the custmer s cmpany cde. BS_CU_COMPANY_CODE_AUTO_PAY A frm fr displaying the autmatic payment transactins segment f the custmer s cmpany cde. BS_CU_COMPANY_CODE_PAYM_ADVICE A frm fr displaying the payment advice ntes segment f the custmer s cmpany cde. BS_CU_COMPANY_CODE_EXP_INSURANCE A frm fr displaying the exprt credit insurance segment f the custmer s cmpany cde. BS_CU_COMPANY_CODE_DUNNING A frm fr displaying the dunning data segment f the custmer s cmpany cde. ABAP Object List: Dunning Areas The genil bject defining the field catalgue is CU_DunningArea. Class CL_BS_CU_DUNNING_AREAS is the respnsible feeder class fr the list UIBB BS_CU_DUNNING_AREAS. In the standard UI the list is part f the custmer s cmpany cde edit page. It shws the dunning area key and descriptin nly. It is read-nly since the actual data is maintained by a frm n a specific edit page. Class CL_BS_CU_DUNNING_AREA is the respnsible feeder class fr the frm UIBB BS_CU_DUNNING_AREA SAP AG 25

26 ABAP Object List: Extended Withhlding Tax Types The genil bject defining the field catalgue is CU_WithhldingTaxType. Class CL_BS_CU_WHTAXES is the respnsible feeder class fr the list UIBB BS_CU_WITHHOLDING_TAXES. In the standard UI the list is part f the custmer s cmpany cde edit page. It shws the extended withhlding tax type key and descriptin nly. It is read-nly since the actual data is maintained by a frm n a specific edit page. Maintenance in general is nly allwed if the parent cmpany cde uses the extended withhlding tax functinality. Class CL_BS_CU_WHTAX is the respnsible feeder class fr the frm UIBB BS_CU_WITHHOLDING_TAX. ABAP Object List: Sales Areas The genil bject defining the field catalgue is CU_SalesArea. Class CL_BS_CU_SALES_AREAS is the respnsible feeder class fr the list UIBB BS_CU_SALES_AREAS. In the standard UI the list is part f the custmer s general data edit page. It shws the sales area keys and descriptin nly. It is read-nly since the actual data is maintained by frms n a specific edit page. Class CL_BS_CU_SALES_AREA is the respnsible feeder class fr the belw mentined frm UIBBs. Frm UIBB BS_CU_SALES_AREA Descriptin A frm fr displaying the key fields f the custmer s sales area. BS_CU_SALES_AREA_ALL A frm cnsisting f all segments f the custmer's sales area. This frm is currently nt used by the SAP delivered UI cnfiguratins. It culd be used t replace the multiple single frm UIBBs, e.g. in case f perfrmance issues. BS_CU_SALES_AREA_BLOCK_DEL A frm fr displaying the blcking and deletin flags f the custmer s sales area. This UIBB is visible nly in blcking mde. BS_CU_SALES_AREA_ORDER A frm fr displaying the sales rders segment f the custmer s sales area. BS_CU_SALES_AREA_PRICING_STATS A frm fr displaying the pricing and statistics segment f the custmer s sales area. BS_CU_SALES_AREA_AGENCY_BUSINESS A frm fr displaying the agency business segment f the custmer s sales area. BS_CU_SALES_AREA_SHIPPING A frm fr displaying the shipping segment f the custmer s sales area SAP AG 26

27 Frm UIBB BS_CU_SALES_AREA_PART_DELIVER Descriptin A frm fr displaying the partial deliveries segment f the custmer s sales area. BS_CU_SALES_AREA_BILLING_DOC A frm fr displaying the billing dcuments segment f the custmer s sales area. BS_CU_SALES_AREA_DELIVER_PAYM A frm fr displaying the delivery and payment terms segment f the custmer s sales area. BS_CU_SALES_AREA_ACCOUTING A frm fr displaying the accunting segment f the custmer s sales area. BS_CU_SALES_AREA_CUSTOMER_GROUPS A frm fr displaying the custmer grups segment f the custmer s sales area. ABAP Object List: Partner Functins The genil bject defining the field catalgue is CU_PartnerFunctin. Class CL_BS_CU_FUNCTIONS is the respnsible feeder class fr the list UIBB BS_CU_FUNCTIONS. In the standard UI the list is part f the custmer s sales area edit page. It shws the cmplete partner functin data. The data is maintained within the list. There s n specific edit page. ABAP Object List: Tax Indicatrs The genil bject defining the field catalgue is CU_TaxIndicatr. Class CL_BS_CU_TAX_INDICATORS is the respnsible feeder class fr tw list UIBBs. List BS_CU_TAX_INDICATORS is part f the custmer s general data edit page. It shws all tax indicatrs f the custmer. BS_CU_SALES_TAX_INDICATORS is part f the custmer s sales area edit page. It shws all tax indicatrs fr the current sales area f the custmer. Fr bth the data is maintained within the list. There s n specific edit page. ABAP Object List: Custmer-like UI The Custmer-like UI re-uses mst f the Custmer Gvernance (MDG-C) custmer UI frms and lists. Still, it is necessary t prvide additinal UIBBs where the cmmn nes cannt be used. The fllwing are UIBBs that replace the cmmn nes: Frm UIBB BS_CU_CL_GEN_ADMIN is used additinally fr administrative data f the Custmer Like UI. This frm has a specific feeder class CL_BS_CU_GUIBB_Custmer SAP AG 27

28 Cmpsite UIBB BS_CU_CL_DETAILS_CU is used instead f the cmmn cmpsite UIBB f the custmer. Frm UIBB BS_CU_CL_GEN_BLOCK is used instead f the cmmn frm UIBB fr the blcking flags f the custmer. Frm UIBB BS_CU_CL_GEN_CONTROL is used instead f the cmmn frm UIBB fr the cntrl data segment f the custmer. Frm UIBB BS_CU_CL_GEN_DELETE is used instead f the cmmn frm UIBB fr the deletin flags f the custmer. List UIBB BS_CU_CL_QUERY_RESULT is used instead f the cmmn list UIBB fr custmer search results. Frm UIBB BS_CU_CL_RELATION is used instead f the cmmn frm UIBB fr business partner relatinships. List UIBB BS_CU_CL_RELATIONS is used instead f the cmmn list UIBB fr business partner relatinships. ABAP Object List: Lean Vendr Creatin UI The Lean Vendr Creatin UI re-uses mst f the Supplier Gvernance (MDG-S) supplier UI frms and lists (the majr part f the UIBBs are hidden). Still, it is necessary t prvide additinal UIBBs where the cmmn nes cannt be used. The fllwing are UIBBs that replace the cmmn nes: Cmpsite UIBB BS_SP_LVC_DETAILS_CU is used instead f the cmmn cmpsite UIBB f the supplier. Frm UIBB BS_SP_LVC_ORG_UNITS is an additinal frm UIBB t allw the request fr a cmpany cde and purchasing rganizatin. It cnsists f the key fields nly. This frm has a specific feeder class CL_BS_SP_GUIBB_LVC_ORG_UNITS. List UIBB BS_SP_LVC_QUERY_RESULT is used instead f the cmmn list UIBB fr supplier search results. Supplier Gvernance (MDG-S) Overview The MDGS UI prvides an independent UI applicatin fr maintaining custmer master data. Therefre it reuses the verview page f the business partner UI. It extends it with the supplier multiple assignments list. This list is the starting pint fr the maintenance f ERP supplier master data. The UI cnsists f several edit pages with frm and list UIBBs. All UI specific ABAP bjects fr the supplier are available in package MDG_BS_ECC_SUPPLIER_BOLUI SAP AG 28

29 The Supplier Gvernance (MDG-S) UI prvides several independent UI applicatins fr maintaining supplier master data. All applicatins re-use the business partner UI and either change r extend it specifically fr the supplier. User Interface BS_OVP_SP Descriptin Main UI fr supplier gvernance. Reuses the verview page fr the business partner UI. Extends this page with the vendr multiple assignments list. This list is the starting pint fr the maintenance f ERP vendr master data. The UI cnsists f several edit pages with frms and list User Interface Building Blcks (UIBB). BS_OVP_SP_VL Referred t as the vendr-like user interface. Des nt use multiple assignments. Layut is synchrnized, as far as pssible, with the SAP GUI transactins used t maintain vendrs. BS_OVP_SP_LVC Referred t as the Lean Vendr Creatin UI. Prvides a single request frm t trigger the creatin f a supplier with ERP vendr master data. The main Supplier Gvernance (MDG-S) UI BS_OVP_SP fr suppliers it re-uses the verview page f the business partner UI. It extends it with the vendr multiple assignments list. This list is the starting pint fr the maintenance f ERP vendr master data. The UI cnsists f several edit pages with frm and list UIBBs. The Supplier Gvernance (MDG-S) UI BS_OVP_SP_VL (s called Vendr Like UI) des nt use multiple assignments. The layut f this UI is synchrnized (as far as pssible) with the SAGUI transactins fr ERP vendr maintenance. The Supplier Gvernance (MDG-S) UI BS_OVP_SP_LVC (s called Lean Vendr Creatin UI) prvides a single request frm t trigger the creatin f a supplier with ERP vendr master data. All UI specific ABAP bjects fr the supplier are available in package MDG_BS_ECC_SUPPLIER_BOLUI SAP AG 29

30 ABAP Object List: Generic Cmpnents There are three applicatin cnfiguratins t start the different UIs. BS_OVP_SP starts the verview page BS_SP_OVP with the applicatin specific cmmunicatr setting as defined in BS_OVP_SP. BS_OVP_SP_VL starts the verview page BS_SP_VL_OVP with the applicatin specific cmmunicatr setting as defined in BS_OVP_SP_VL. BS_OVP_SP_LVC starts the verview page BS_SP_LVC_OVP with the applicatin specific cmmunicatr setting as defined in BS_OVP_SP_LVC. Any supplier UI specific messages are stred within message class MDG_BS_SUPP_BOLUI. ABAP Object List: Enterprise Search The enterprise search template includes vendr attributes like the vendr ID, cmpany cdes, and s n. T reflect this within the search UIBB, a vendr specific search UIBB BS_SP_DQUERY_ES is prvided. Its feeder class is CL_BS_SP_GUIBB_DQUERY. ABAP Object List: General Data The genil bject defining the field catalgue is SP_GeneralData. Class CL_BS_SP_GUIBB_GENERAL_DATA is the respnsible feeder class fr the belw mentined frm UIBBs. The class is a jin feeder since it handles bth the multiple assignments and vendr general data attributes. List UIBB BS_SP_GEN_CONTROL Descriptin A frm UIBB fr displaying the segment cntrl data f the vendr's general data and multiple assignments attributes. BS_SP_GEN_ALL A frm cnsisting f all segments f the vendr's general data. This frm is currently nt used by the SAP delivered UI cnfiguratins. It culd be used t replace the multiple single frm UIBBs, e.g. in case f perfrmance issues. BS_SP_GEN_REFERENCE A frm UIBB fr displaying the segment reference data f the vendr s general data. BS_SP_GEN_TAXINFORMATION A frm UIBB fr displaying the segment tax infrmatin f the vendr s general data. BS_SP_GEN_PAYMENT A frm UIBB fr displaying the segment payment transactin data f the vendr s general data SAP AG 30

31 List UIBB BS_SP_GEN_ADD_PORG Descriptin A frm UIBB fr displaying the segment additinal purchasing rganizatin data f the vendr s general data. ABAP Object List: Cmpany Cdes The genil bject defining the field catalgue is SP_CmpanyCde. Class CL_BS_SP_COMPANY_CODES is the respnsible feeder class fr the list UIBB. BS_SP_COMPANY_CODES. In the standard UI the list is part f the vendr s general data edit page. It shws the cmpany cde key and descriptin nly. It is read-nly since the actual data is maintained by frms n a specific edit page. Class CL_BS_SP_COMPANY_CODE is the respnsible feeder class fr the belw mentined frm UIBBs. Frm UIBB BS_SP_COMPANY_CODE BS_SP_COMPANY_CODE_ALL Descriptin A frm fr displaying the key fields f vendr s cmpany cde. A frm cnsisting f all segments f the vendr s cmpany cde. This frm is currently nt used by the SAP delivered UI cnfiguratins. It culd be used t replace the multiple single frm UIBBs, e.g. in case f perfrmance issues. BS_SP_COMPANY_CODE_ACCOUNTIN G BS_SP_COMPANY_CODE_AUTO_PAY A frm fr displaying the accunting infrmatin segment f the vendr s cmpany cde. A frm fr displaying the autmatic payment transactins segment f the vendr s cmpany cde. BS_SP_COMPANY_CODE_BLOCK_DEL A frm fr the "blcking and deletin flag" segments f the vendr s cmpany cde. BS_SP_COMPANY_CODE_CORRESP A frm fr the "crrespndence" segment f the vendr's cmpany cde data. BS_SP_COMPANY_CODE _DUNNING A frm fr the "dunning data" segment f the vendr's cmpany cde data. BS_SP_COMPANY_CODE_INTEREST A frm fr displaying the interest calculatin data segment f the vendr s cmpany cde. BS_SP_COMPANY_CODE _INVOICE A frm fr the "invice verificatin" segment f the vendr's cmpany cde data. BS_SP_COMPANY_CODE _PAYMENT A frm fr the "payment transactins" segment f the vendr's cmpany cde data SAP AG 31

32 Frm UIBB BS_SP_COMPANY_CODE _REFERENCE BS_SP_COMPANY_CODE _WITHHOLDING Descriptin A frm fr the "reference data" segment f the vendr's cmpany cde data. A frm fr the "withhlding tax" segment f the vendr's cmpany cde data. ABAP Object List: Dunning Areas The genil bject defining the field catalgue is SP_DunningArea. Class CL_BS_SP_DUNNING_AREAS is the respnsible feeder class fr the list UIBB BS_SP_DUNNING_AREAS. In the standard UI the list is part f the vendr s cmpany cde edit page. It shws the dunning area key and descriptin nly. It is read-nly since the actual data is maintained by a frm n a specific edit page. Class CL_BS_SP_DUNNING_AREA is the respnsible feeder class fr the frm UIBB BS_SP_DUNNING_AREA. ABAP Object List: Extended Withhlding Tax Types The genil bject defining the field catalgue is SP_WithhldingTaxType. Class CL_BS_SP_WHTAXES is the respnsible feeder class fr the list UIBB BS_SP_WITHHOLDING_TAXES. In the standard UI the list is part f the vendr s cmpany cde edit page. It shws the extended withhlding tax type key and descriptin nly. It is read-nly since the actual data is maintained by a frm n a specific edit page. Maintenance in general is nly allwed if the parent cmpany cde uses the extended withhlding tax functinality. Class CL_BS_SP_WHTAX is the respnsible feeder class fr the frm UIBB BS_SP_WITHHOLDING_TAX. ABAP Object List: Purchasing Organizatin The genil bject defining the field catalgue is SP_PurchasingOrg. Class CL_BS_SP_PURCH_ORGS is the respnsible feeder class fr the list UIBB BS_CU_PURCH_ORGS. In the standard UI the list is part f the vendr s general data edit page. It shws the purchasing rganizatin key and descriptin nly. It is read-nly since the actual data is maintained by frms n a specific edit page. Class CL_BS_SP_PURCH_ORG is the respnsible feeder class fr the belw mentined frm UIBBs. Frm UIBB BS_SP_PURCH_ORG Descriptin A frm fr displaying the key field f the vendr s purchasing rganizatin SAP AG 32

33 Frm UIBB BS_SP_ PURCH_ORG_ALL Descriptin A frm cnsisting f all segments f the vendr's purchasing rganizatin. This frm is currently nt used by the SAP delivered UI cnfiguratins. It culd be used t replace the multiple single frm UIBBs, e.g. in case f perfrmance issues. BS_SP_ PURCH_ORG_BLOCK_DEL A frm fr the "blcking and deletin flag" segment f the vendr's purchasing rganizatin. BS_SP_ PURCH_ORG_CONDITIONS A frm fr the "cnditins" segment f the vendr's purchasing rganizatin. BS_SP_ PURCH_ORG_CONTROL A frm fr the "cntrl data" segment f the vendr's purchasing rganizatin. BS_SP_ PURCH_ORG_MATERIAL A frm fr the "default data material" segment f the vendr's purchasing rganizatin. BS_SP_ PURCH_ORG_SALES A frm fr the "sales data" segment f the vendr's purchasing rganizatin. BS_SP_ PURCH_ORG_SERVICE A frm fr the "service data" segment f the vendr's purchasing rganizatin. ABAP Object List: Different Purchasing Data The genil bject defining the field catalgue is SP_PurchasingOrg2. Class CL_BS_SP_PURCH_ORGS2 is the respnsible feeder class fr the list UIBB BS_CU_PURCH_ORGS2. In the standard UI, the list is part f the vendr s purchasing rganizatin edit page. It shws the different purchasing data keys and descriptin nly. It is read-nly since the actual data is maintained by frms n a specific edit page. Class CL_BS_SP_PURCH_ORG2 is the respnsible feeder class fr the belw mentined frm UIBBs. Frm UIBB BS_SP_PURCH2_ORG Descriptin A frm fr displaying the key fields f the vendr s different purchasing data. BS_SP_PURCH2_ORG_ALL A frm cnsisting f all segments f the vendr's different purchasing data. This frm is currently nt used by the SAP delivered UI cnfiguratins. It culd be used t replace the multiple single frm UIBBs, e.g. in case f perfrmance issues SAP AG 33

34 Frm UIBB BS_SP_PURCH2_ORG_CONDITION Descriptin A frm fr the "cnditins" segment f the vendr's different purchasing data. BS_SP_PURCH2_ORG_CONTROL A frm fr the "cntrl data" segment f the vendr's different purchasing data. BS_SP_PURCH2_ORG_MATERIAL A frm fr the "default data material" segment f the vendr's different purchasing data. BS_SP_PURCH2_ORG_SALES A frm fr the "sales data" segment f the vendr's different purchasing data. BS_SP_PURCH2_ORG_SERVICE A frm fr the "service data" segment f the vendr's different purchasing data. ABAP Object List: Partner Functins The genil bject defining the field catalgue is SP_PartnerFunctin. Class CL_BS_SP_FUNCTIONS is the respnsible feeder class fr the list UIBB BS_SP_FUNCTIONS. In the standard UI the list is part f the vendr s purchasing rganizatin edit page. It shws the cmplete partner functin data. The data is maintained within the list. There s n specific edit page. Class CL_BS_SP_FUNCTIONS_DIA is the respnsible feeder class fr the frm UIBB BS_SP_FUNCTIONS_DIA. This frm is used n a pp-up fr the maintenance f partner functins fr different purchasing data. It cnsists f the related additinal key fields. ABAP Object List: Sub-Ranges The genil bject defining the field catalgue is SP_Subrange. Class CL_BS_SP_SUBRANGES is the respnsible feeder class fr the list UIBB BS_SP_SUBRANGES. In the standard UI the list is part f the vendr s general data edit page. The data is maintained within the list. There s n specific edit page. ABAP Object List: Vendr-like UI The Vendr-like UI re-uses mst f the Supplier Gvernance (MDG-S) supplier UI frms and lists. Still, it is necessary t prvide additinal UIBBs where the cmmn nes cannt be used. The fllwing are UIBBs that replace the cmmn nes: Frm UIBB BS_SP_GEN_ADMIN is used additinally fr administrative data f the Vendr Like UI. This frm has a specific feeder class CL_BS_SP_GUIBB_VENDOR. Cmpsite UIBB BS_SP_DETAILS_CU is used instead f the cmmn cmpsite UIBB f the supplier SAP AG 34

35 Frm UIBB BS_SP_GEN_CONTROL_VL is used instead f the cmmn frm UIBB fr the cntrl data segment f the supplier. Frm UIBB BS_SP_GEN_DELETE_VL is used instead f the cmmn frm UIBB fr the blcking and deletin flags f the supplier. List UIBB BS_SP_VL_QUERY_RESULT is used instead f the cmmn list UIBB fr supplier search results. ABAP Object List: Lean Vendr Creatin UI The Lean Vendr Creatin UI re-uses mst f the Supplier Gvernance (MDG-S) supplier UI frms and lists (the majr part f the UIBBs are hidden). Still, it is necessary t prvide additinal UIBBs where the cmmn nes cannt be used. The fllwing are UIBBs that replace the cmmn nes: Cmpsite UIBB BS_SP_LVC_DETAILS_CU is used instead f the cmmn cmpsite UIBB f the supplier. Frm UIBB BS_SP_LVC_ORG_UNITS is an additinal frm UIBB t allw the request fr a cmpany cde and purchasing rganizatin. It cnsists f the key fields nly. This frm has a specific feeder class CL_BS_SP_GUIBB_LVC_ORG_UNITS. List UIBB BS_SP_LVC_QUERY_RESULT is used instead f the cmmn list UIBB fr supplier search results SAP AG 35

36 Additinal Infrmatin Links Custmer Vendr Integratin n SAP Help FPM Ckbk n SDN MDG Guides fr EhP 6 n Service Market Place MDG Extensibility Optins n SDN Extensibility Optins fr SAP Master Data Gvernance -> Custmer / Supplier Data -> Data Mdel Metadata Hw-t Guides Extensibility Optins fr SAP Master Data Gvernance -> Custmer / Supplier Data Hw-t Guide: Create and Register a Custm Handler Class Hw-t Guide: Create r Redefine a UI Feeder Class Hw-t Guide: Extend MDG-S / MDG-C Data Mdel by a New Entity Type (Flex Optin) Hw-t Guide: Extend MDG-S / MDG-C Data Mdel by a New Entity Type (Reuse Optin) Hw-t Guide: Extend MDG-S / MDG-C Data Mdel by a New Field (Reuse Optin) Hw-t Guide: Default the ERP Vendr Creatin with MDG-S Hw-t Guide: Filter an Input Help fr a Business System SAP Ntes specifying required infrmatin fr OSS supprt 2013 SAP AG 36

37 Cpyright Cpyright 2013 SAP AG. All rights reserved. N part f this publicatin may be reprduced r transmitted in any frm r fr any purpse withut the express permissin f SAP AG. The infrmatin cntained herein may be changed withut prir ntice. Sme sftware prducts marketed by SAP AG and its distributrs cntain prprietary sftware cmpnents f ther sftware vendrs. Micrsft, Windws, Excel, Outlk, and PwerPint are registered trademarks f Micrsft Crpratin. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PwerVM, Pwer Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPwer, PwerPC, BatchPipes, BladeCenter, System Strage, GPFS, HACMP, RETAIN, DB2 Cnnect, RACF, Redbks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivli and Infrmix are trademarks r registered trademarks f IBM Crpratin. Linux is the registered trademark f Linus Trvalds in the U.S. and ther cuntries. Adbe, the Adbe lg, Acrbat, PstScript, and Reader are either trademarks r registered trademarks f Adbe Systems Incrprated in the United States and/r ther cuntries. Oracle is a registered trademark f Oracle Crpratin. UNIX, X/Open, OSF/1, and Mtif are registered trademarks f the Open Grup. Citrix, ICA, Prgram Neighbrhd, MetaFrame, WinFrame, VideFrame, and MultiWin are trademarks r registered trademarks f Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks r registered trademarks f W3C, Wrld Wide Web Cnsrtium, Massachusetts Institute f Technlgy. Java is a registered trademark f Oracle Crpratin. JavaScript is a registered trademark f Oracle Crpratin, used under license fr technlgy invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and ther SAP prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f SAP AG in Germany and ther cuntries. Business Objects and the Business Objects lg, BusinessObjects, Crystal Reprts, Crystal Decisins, Web Intelligence, Xcelsius, and ther Business Objects prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f Business Objects S.A. in the United States and in ther cuntries. Business Objects is an SAP cmpany. All ther prduct and service names mentined are the trademarks f their respective cmpanies. Data cntained in this dcument serves infrmatinal purpses nly. Natinal prduct specificatins may vary. These materials are subject t change withut ntice. These materials are prvided by SAP AG and its affiliated cmpanies ("SAP Grup") fr infrmatinal purpses nly, withut representatin r warranty f any kind, and SAP Grup shall nt be liable fr errrs r missins with respect t the materials. The nly warranties fr SAP Grup prducts and services are thse that are set frth in the express warranty statements accmpanying such prducts and services, if any. Nthing herein shuld be cnstrued as cnstituting an additinal warranty SAP AG 37