Skip to Content

Search

Technical Articles

Nallasivam Balagurusamy

Posted on September 11, 2020 3 minute read

SAP MDG-S Integration with Ariba-SLP

Follow RSS feed Like

8 Likes 1,520 View 3 Comments

Steps to Integrate SAP MDG-S with SLP – Ariba via Web Services via Replication Model

Steps to be followed in SAP MDG & SAP PI

Landscape & Architecture
Business Function activation
List of Services to be used
Service activation in SOAMANAGER
DRF Model Creation
Badi Enhancements

Integration Landscape & Architecture

Business Function activation

The below business functions related to MDG-S Data replication framework for the SLP-MDG Integration

T.Code : SFW5

Business Functions	Status
CA_BP_SOA	To be activated
CA_SUPPLIER_SOA	To be activated
DRF_FOUNDATION	To be activated

List of Services to be used

Type	Scenario	Source System	Target System	Services
Inbound to MDG Outbound from Ariba	Supplier Creation in Ariba	Ariba	MDG	BusinessPartnerSUITEBulkReplicateRequest_In
Outbound from MDG/ECC Inbound to Ariba	Data replication back to Ariba after CR activation in MDG	MDG/ECC	Ariba	BusinessPartnerSUITEBulkReplicateRequest_Out
Inbound to Ariba Outbound from MDG/ECC	Send validation error/success message about the Supplier data CR validation	MDG/ECC	Ariba	BusinessPartnerSUITEBulkReplicateConfirmation_Out
Inbound to MDG/ECC Outbound from Ariba	Send successful data received acknowledgement message from Ariba to MDG/ECC	Ariba	MDG/ECC	BusinessPartnerSUITEBulkReplicateConfirmation_In

BP Relationship related Services

BusinessPartnerRelationshipSUITEBulkReplicateRequest_In

BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out

BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out

Service activation in SOAMANAGER

T.Code: SOAMANAGER

Web Service Activation with logical port definition to point to the respective Target system to be done

Request_Out

Confirmation_Out

DRF Replication Model Creation

Create the Replication Model for Ariba Target system

Assign Outbound Implementation

Assign Target system

Assign Outbound Parameters

Define Technical Settings for Business Target System

Create Business Target system

Assign Logical system

Assign necessary RFC Destination to reach the Target system

Define Business Object Type for the Target system

Define the BO Communication Type for the Target system

BAdi Enhancements

Inbound Data processing: This can be used to process the data sent in the RequestIn in the IN parameter and fill in the necessary data in the OUT Parameter

Enhancement Spot: MDG_SE_SPOT_BPBUPA

BAdI Definition: MDG_SE_BP_BULK_REPLRQ_IN

Interface: IF_MDG_SE_BP_BULK_REPLRQ_IN

Outbound Data processing: This can be used to process the data which needs to be sent in the RequestOut in the IN parameter and fill in the necessary data in the OUT Parameter

Enhancement Spot: MDG_SE_SPOT_BPBUPA

BAdI Definition: MDG_SE_BP_BULK_REPLRQ_OUT

Interface: IF_MDG_SE_BP_BULK_REPLRQ_OUT

Thanks,

Nalla B.

Alert Moderator

3 Comments

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

ashish bansal

September 17, 2020 at 2:03 am
Thank you for such a detailed blog. i had few queries, can you please help me with those.
1. Do we need to install CIG add -on, on the S4 HANA system where MDG is installed.
2. How to add custom fields in the SLP -MDG integration.
3. I don’t see this business partner documents in the mapping tool. What can be the reason for that?
Request you to please help me with the above queries as soon as possible, it would be really helpful.
- Like(0)
- Ashish Bansal
  
  September 18, 2020 at 10:08 am
  
  Nallasivam Balagurusamy Can you please help me with the above queries.
  - Like(0)
  - Nallasivam Balagurusamy Post author
    
    October 28, 2020 at 4:53 pm
    Hi Bansal,
    
    We had a co-deployed system so we installed CIG on the same system.
    
    Custom fields can be added by enhancing the proxy structures and the values can be passed with FIELD_NAME = ‘ZZXXXX’ and FIELD_VALUE = ‘YYYY’ and it can be retrieved in BAdi and added to the CR
    
    Am not sure about this, may need to check with SAP on this via support incident. But by standard documents are not supported as part of SOA.
    
    Hope this helps.
    
    Thanks,
    
    Nalla B,
    Like(0)