on 2018 Sep 27 2:34 PM
1. General data will be sent from ariba to SAP MDG. To accept the temporary vendor id(ACN) do we need to perform any badi work here?
2. When general data is sent from Ariba to sap mdg, will it create Change request automatically or do we need to use 'API' to create change request in badi during inbound of MDG
3.if we plan to send the replication back to ariba system, will drf setting is enough or do we need to do any other approach to send the vendor data to Ariba after activation of change request.
Please share your comments on sap mdg - ariba integration
Request clarification before answering.
Hi Guys,
I am trying to integrate Ariba with MDG. I am using the standard inbound BP SOA service (BusinessPartnerSUITEBulkReplicateRequest_In) but it is not creating any record in BP. Could you guys please let me know the steps to integrate Ariba with MDG. Below are the steps I followed,
1. In Ariba SLP - SM Admin - ERP Sync - CIG - system ID
2. Created project in CIG
3. Enabled Web service in SPRO
4. In ariba SLP I tried to sync it ERP, the status in SRT_MONI is "Delivered" but I don't see any BP got created.
Am I missing any steps here?
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
1. If you are using the standard inbound BP SOA service (BusinessPartnerSUITEBulkReplicateRequest_In), then yes you will need to use the BADI MDG_SE_BP_BULK_REPLRQ_IN to create the CR.
2. See above answer. More infor can be found here: https://blogs.sap.com/2017/02/09/sap-businesspartner-enterpriseservice-businesspartnersuitebulkrepli...
3. Ariba supports both direct via SOA message or mediated integration to SAP MDG. The last integration I did with Ariba and MDG (where MDG version < 9.0) was to push files out for Ariba to pick up, however I understand the newer versions of Ariba and MDG have better integration capabilities.
Hope that helps
Luqman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @ajay.mahajan (AJ),
Thanks for detail explanation.
I have question on point no.6.
Once CR is approved/rejected in MDG which webservice it triggers?
Is it BP*Request_out or confirmation_out?
Regards,
RJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello All,
1. If you enable consolidation process or Change request configuration in replication model upon arrival of a web service message in MDG system, MDG will not send any confirmation message.
2. You can also create a change request by implementing Inbound BADI MDG_SE_BP_BULK_REPLRQ_IN
3. Even though you are looking to set up an integration with Ariba a similar principle applies to when integrating MDG with C4C. A very helpful guide can be found at this link: https://help.sap.com/viewer/6d52de87aa0d4fb6a90924720a5b0549/1809.002/en-US/130b87be0523466dbeadf263...
4. When creating a business partner the inbound handling of the web service in MDG should trigger a consolidation process. If the record is not a duplicate a new BP will be created in MDG with a generated ID and the key mapping will be updated. The business partner will then be sent to the source system together with the key mapping. If the records was a duplicate then the key mapping will be enhanced and the updated records sent to the source system.
5. When updating an existing Business partner you can use the BADI to enable change request upon receiving the message. Because during creation the source system was informed of the MDG ID, the message will be send with the MDG ID and the inbound processing will not start a consolidation process but rather a change request will be created. The updated record after activation will be sent to the source system.
6. Sending the confirmation message when capturing the message in MDG makes no sense, because the ID will only be generated and known once the record is activated in MDG. From what I know you have enabled automatic activation of CR, which is not a supported process by MDG. Every CR should go through an approval process. Once the changes are approved and the record activated MDG will send the business partner web service to your original system and that system will then send a confirmation message back to MDG.
7. If you follow the standard processes then the key mapping will be created properly in MDG and also replicated to all target systems.
8. For Key mapping more details you can find here https://launchpad.support.sap.com/#/notes/2926463%E2%80%8B
we have done the ARIBA Integration with MDG via webservices using BP EXTERNAL Number Field in BP Model which automatically creates the key mapping between ARIBA and MDG.
Hope these details will help you, kindly vote if it answer your queries.
Thanks!
AJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
I am also trying to sync it to ERP but Change request are not getting created the stutus in SRT_MONI is "Delivered" but i dont see any vendors created.
Please let me know any pointers i am missing..
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guys,
i have integrated Ariba and MDG , change requests are getting created for Success records, wherein Change request are not created for failed one, my requirement is to have change request created in SAP MDG for all Vendor data coming in SAP MDG.
I am using Staging option and in BADI Persistence value = 1.
Do please let me know if any one of you have any idea or solution.
Thanks,
Waseem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
please be aware that the given link is not correct. Following the blog can lead to severe issues with data consistency and key mapping. You should rather follow the implementation & configuration guides offered by SAP.
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.