If processing is not real time via service and works based on batch job of Pull program (/ARBA/SM_BUSINESS_PARTNER_PULL) then place additional breakpoint in this program to check if the process is pulling payload data from Ariba or not.įor all scenarios, below methods help a lot to gather error message: We have observed error logging during creation process is not readable, and we need to debug it’s API related methods and below are the places where setting a breakpoint during replication process would get us error message in general. Supplier getting replicated from Ariba SLP but CR or BP is not created in SAP-MDG? Read Key mapping data to get Supplier Id via below APIsįill Supplier Id in OUT-BUSINESS_PARTNER-RECEIVER_INTERNAL_ID & OUT-BUSINESS_PARTNER-SUPPLIER-RECEIVER_INTERNAL_ID Get current Business Partner Id from OUT-BUSINESS_PARTNER-INTERNAL_ID or OUT-BUSINESS_PARTNER-SUPPLIER-INTERNAL_ID.Įnsure both Internal Ids are same (i.e. Implement BADI MDG_SE_BP_BULK_REPLRQ_OUT, in method IF_MDG_BP_BULK_REPLRQ_OUT~OUTBOUND_PROCESSING Once we enable DRF to Ariba from MDG, how does the Business Partner number flow back to SLP post BP is created in MDG to enable Bi-Sync? – Call method: CL_MDG_BP_BUPA_SI_IN=>IF_MDG_UPLOAD_PROXY~SETUP_FOR_FILE_UPLOAD ( Exporting IV_INSTANCE = 1 IT_USER_SETTING = ) – Define internal table with type MDG_USER_PROXY_SETTING_T. Implement BADI MDG_SE_BP_BULK_REPLRQ_IN, in method INBOUND_PROCESSING write below code: ![]() How do we create a Change Requests (diff for create/change) from the payload incoming from Ariba SLP? If we observe more scenarios will create a version 2.īelow are the frequent and important scenarios faced while working with Ariba SLP MDG. We have penned down general areas where all SAP-MDG projects struggle with Ariba Integration. ![]() This blog post would help you save time and effort and not reinvent the wheel.
0 Comments
Leave a Reply. |