cancel
Showing results for 
Search instead for 
Did you mean: 

SourcingMasterDataImport not triggering in CIG

10-11-2021 7:33 AM
3185 views 7 comments Go to solution
0 Likes
SAP Managed Tags
Subscribe

We executed ARBCIG_MASTER_DATA_EXPORT in S4hana full mode and when we checked in SRT_MONI it is delivered please check attachment fo r reference . issue is SourcingMasterDataImport not triggering in CIG due to which master data is not transmitted to sourcing realm.

0 Likes

Accepted Solutions (1)

Accepted Solutions (1)

former_member651171
Participant

Hi Shivakumar,

Please confirm if you are seeing the message in SRT_UTIL? If you are not seeing the msg then please check SOMANAGER port configuration.

If you have completed above configuration , and seeing msg in SRT-UTIL but not only seeing in CIG tracker the Please confirm if you are still in testing phase or in Production already ? If your CIG project is still in testing then the URL you should be using is testacig.ariba.com.

acig.ariba.com is the URL for Production phase, this URL is based on the option you select while running interface setup program in SPRO.

Regards,

Sunitha V S

0 Likes

Hi Sunitha,

you are correct in soamanager SOAP URL for sourcing: Master data was poitning to production CIG , we changed to Test instance: https://testacig.ariba.com/cxf/receiveERPMD.

Now its working .

Thanks a lot for your response:)

Answers (4)

Answers (4)

YayatiEkbote
Contributor
0 Likes

Yes. It looks like proxy/firewall settings are not allowing to send the message outside.

  1. When doing the initial setup, how the SOAMANAGER interface was activated? Through the utility program which comes as a part of CIG addon? Or manually through SOAMANAGER transaction? In both cases, there is an option to fill the proxy server details. If your IT security policy is to allow sending messages through proxy only, then you need to have proxy details filled in the interface settings.
  2. Check if realm ID, variant and partition, CIG P-User ID and password is correctly configured. Ideally if it is a mismatch, then you must at least see pre-processing message failed in CIG. But just check once.

Regards,

Yayati

rdemchuk
Active Participant
0 Likes

also don’t run them all at once you should have a sequence of loading to parent then child realms. All at once could cause a dump. Think of it like building an organization. Company code, plant, pgrp and etc.

rdemchuk
Active Participant
0 Likes

Sunitha is correct. Look into your proxy settings in the soamanager. Make sure you are active (also part of spro config to initiate this sourcing master data process. If you see it in cig but not in Ariba it’s the proxy. Look for any arbcig1 or master proxy and validate they are working. Some folks use a certificate Authenticator but I like the P-user for this process. If you need a quick fix just export the al11 file and load it manually (csv style) into the realm you need it.

YayatiEkbote
Contributor
0 Likes

I cannot see attachment.

Also please explain in detail and confirm if following activities are done -

1. Add CIG certificate in Ariba realm integration toolkit security

2. For sourcing , you need to add ERP system ID in Administration -> Master Data Manager -> External System Configuration

3. Even if your ERP system id S/4 HANA, the type of ERP should always be kept as SAPECC.

If all above is done, then check in AL11 in SAP ERP if the CSV files are generated properly. Check in Administration -> Master Data Manager -> Manage Payload requests if the payload got logged in there in scheduled/in process status.

If payload is logged and has error, check what is the error.

Follow latest Ariba CIG configuration guide for each and every step.

Regards,

Yayati Ekbote

0 Likes

1. Add CIG certificate in Ariba realm integration toolkit security : Completed

Screenshots :

1. Executing CIG master data extract

Screenshot of Al11 : attached in main question

SRT_Moni Screenshot :attached in main question

2.Issue is in CIG we do not see any document, attached in main question

3.External system config maintained as per document : attached in main question