Skip to Content
Technical Articles

Syncing custom attribute data from SAP MDG 9.1 to S/4 HANA 1709.

Syncing custom attribute data from SAP MDG 9.1 to S/4 HANA 1709.

Introduction : This blog gives some insight of synching custom attribute data from SAP MDG 9.1 to S/4 HANA 1709 theoretically. Note this blog covers MDG data modeling/UI Modeling/Process Modeling/Data Replication framework insight including Validations and Derivation with MDG BRF+ plug in.

Mainpart : This blog content outlines the steps to replicate the data from MDG 9.1 to S/4 HANA 1709. e.g. New field ZZ_TESTvis being added in MDG 9.1 and need to replicate the same to S/4 HANA . The steps below gives some theoretical insight to sync custom attribute data from MDG 9.1 to S/4 HANA 1709.

Step 1: Data Modeling : Add field in relevant tables(LFM1 etc..) table in MDG 9.1 and S/4 HANA systems. Find out staging and active area structure names with data element name with path MDGIMG/Data Modeling/Edit Data Model/Entity Type/Attribute. Add same custom attribute in these structures and activate . Then pick staging and active structure names with the path MDGIMG/Data Modeling/Generate Data Model-Specific structures/Data Model/Structure/Mapping. Then do the mapping/transformation from source to target structures with path MDGIMG/Data Modeling/Extend mappings. Same custom attribute needs to be created ins/4 HANA system and syncs data with data replication framework( DRF+).

Step 2 UI Modeling: Enable created custom attribute by creating configuration or adaptations with FPM framework. Use feeder class GET_DATA method to tweak logic(hiding data/enabling/disabling) if required as per use case. Use context based adaptation if field needs to be controlled based on configuration field type. Feeder class can be enhanced with exit points or standard feeder class can be replaced for custom code development. SAP MDG USMD_ACC_FLD_PROP_CUST_DEP_SET BADI can be used to control attribute as per use case.

Step 3: Validations and Derivations : BADI /BRF+ MDG Plugin: Validations can be placed in badi’s(USMD_RULE_SERVICE_CROSS_ET and USMD_RULE_SERVICE) or MDG BRF+ plug in BRF+ application FMDM_MODEL_AR with check and derive methods.If validation is associated with multiple cross entities, write custom code for validations/derivations in BADI.

Step 4: Process Modeling: Process modeling is the heart of SAP MDG to control the CR process flow. As part of this, Create CR with data model(BP etc..), Main entity(BP_HEADER etc..), workflow template(WS60800086), entity types, business activities and service level agreement(SLA) by using the standard CR reference.Then CR Steps needs to be configured along with entity/auth check/duplicate check,BADI validations/User Interface for each CR.Then configure rule based workflow with decision table steps/actions that can be changed as per use case and assign custom service(USMD201C_SSW) at service name column that can be used as a filter at badl level(ExUSMD_SSW_SYSTEM_METHOD_CALLER/USMD_SSW_DYNAMIC_AGENT_SELECT) to write custom code as per use case. If new custom attribute has scenario of tweaking logic during workflow process, put custom code in these badis.

Step 5: Data Replication : Create business systems and replicate model for synching data from MDG to S/4 , Enhance web service structure(BPSUITERplctReqSuplr/BPSUITERplctReqProcmtArrgmt) with new custom field in MDG and S/4 HANA and write custom code to populate data in MDG/S/4 HANA BADI implementations(Enhancement spot : MDG_SE_SPOT_BPBUPA MDG_BP_BPSUITERPLRQ_PROCMT_ARR/MDG_BP_BPSUITERPLCT_REQ_SUPLR), then custom data gets stored in associated table(Note: Table structure needs to be enhanced as well as mentioned in step1 for MDG table ).

 

Conclusion: Hope this blog gives some useful SAP MDG process theoretical insight to sync data to S/4 HANA.

 

 

Thanks,

Mani Kothapalli(SAP  Technical Architect)

3 Comments
You must be Logged on to comment or reply to a post.