Hello colleagues,(Required solution on URGENT basis)customer have already existing PI/PO (On Premise) and build our own mapping in the PI/PO.We are faced with the challenge that we want to connect CIG with the SAP PI/PO (On Prem).When we enable integ...
Hello Experts,
I am getting below mentioned error in the CIG while sending the master data from ERP TO ARIBA.
The solution that we are using is Ariba Sourcing Integration.
Also, we are sending one custom field i.e., Vendor Master CSV file in th...
Hello Experts,
I am trying to integrate the Vendor Master into the Ariba Sourcing via a custom development.
I have developed a code in which I am sending one custom .csv file for the vendor master data into the directory (AL11) and then it will...
Hello experts,
We need suggestion on below Scenario which is related to SLP Solution :
We have number of supplier in Ariba portal as well as s/4 hana , but we are going to change the number range of these supplier in S/4 hana .
Now we want to ...
Hi All,
Our client is planning to migrate from SAP ECC (Oracle DB) to SAP S/4 HANA (Latest Version).
They are using Ariba B&I for the complete PR to Invoice Process.
We need to know what are the prerequisites, and activities to be performed for...
Hello,Also, can you please let me know if any possibility is there of integrating vendor master through the websservice or by sending the file into the Master data program.Thanks & Regards,
Hello Ramprasad,I have created it without the custom and it is getting created successfully. Also, I am not sending any schema file for the custom CSV.s I am sending the vendor Master through the ARBCIG_MASTER_DATA_EXPORT program do we need to send t...
Thanks for the information.Yes, we are using CIGJust to verify, we need to clear/ Pay the invoice documents as well before switching the ECC to HANA?Ariba will start the process with new, documents and newly integrated master data from the sap s/4 ha...
Hi Prem,Thanks for the response.The Issue was due to the Info Record that was created for the Supplier the Pricing conditions of PO & Info Record were not matching which caused this issue.
