PO versioning in CIG component

Since 2024 we are utilizing CIG constituent successful our SAP backend strategy to make acquisition orders and nonstop them via our interface to Ariba Business Network. We had immoderate months to summation acquisition with CIG but besides collected immoderate issues that we’re present trying to solve.

In CIG constituent a PO versioning seems to beryllium foreseen. That means that whenever a PO is created, it is marked with mentation fig 1 successful the respective SAP table. Whenever a alteration connected that PO is done, mentation numbers summation successful the respective SAP table. Those mentation numbers are portion of the PO Idoc and besides transmitted successful PO cxml to Ariba Business Network.

According to our backend logic, we bash not privation to nonstop each azygous PO alteration to the supplier. There mightiness ever beryllium immoderate interior changes similar accounting information, interior texts etc. which are not relevant/interesting for the suppliers. Therefore specified changes bash not pb to a palmy PO output message. Nevertheless, according to CIG modular logic, it leads to an summation of PO mentation fig successful the respective SAP table.

Whenever specified a PO is cancelled astatine a aboriginal constituent of time, PO cancellation connection is sent with a higher mentation fig than the existent progressive connection successful Ariba Business Network. As Ariba Business Network expects a cancellation ever to person the aforesaid mentation fig than the PO connection which should beryllium cancelled, this leads to an mistake connection successful CIG and PO cancellation not reaching Ariba Business Network.

We would admit to person immoderate champion practices, akin experiences oregon suggested solutions however we could grip those issues successful future.

Thanks a batch successful advance.