CIG-why document type ContractRequestServices is triggering in CIG ?

[former_member761922]

Hi Team,

Background : Created RFQ (material)-> from sorucing request we created RFP sourcing project-->at award stage we created new contract and completed all contract workspace task and published contract line document and sent to external system.

issue : in CIG wrong document Contract service document is triggering in transaction tracker ( even thoughcontract-cxml.png we have given only material) due to this in SAP SRT_MONI wrong interface "QuoteMessagePurchasingContract_Async_In_V1 is triggered with error " CX_FEH_CONSISTENCY_ERROR:An exception with the type CX_FEH_CONSISTENCY_ERROR was raised, but was not handled locally or declared"

Expectation :

According to Note : https://connectsupport.ariba.com/sites?Recommendation=AC#item-view&/191402

For contract created from quote should have QuoteMessageContract and interface called will be QuoteMsgPurchasingContract_Async_In

In our case Interface is "QuoteMessagePurchasingContract_Async_In_V1" getting triggered for material which is wrong.

Could you please give your input on this issue please refer screenshots of CXML .contract-transaction-tracker.pngcontract-cross-reference.png

[former_member651171]

Hi Shivakumar,

There are 2 flows

1. If you start with RFQ -> sourcing project-->Bidding -> award it as contract -> send quotes to external system then, Based on the line items in your payload doc type will be determined.

That is if your payload only has material items ,it will be shown as Quote message Contract .

At least one service item then its shown as Quote message contract services.

Having said that there is another cross reference parameter we have given recently which is "Service Interface" , if you enable this then even if you are sending a quote that has only material line items it will still show as Quote message contract services..

2. i assume this is what you are testing

If you start with RFQ -> sourcing project-->Bidding - > award it as contract-> Add the contents to a new contract work space, -> Send CLID to external system

Doc type on CIG will be purely based on the your CIG basic data version.

If you have AddonInfo2 value maintained along with AddOnInfo1 in your basic data then irrespective you send only material line items in the contract it will be still show as Contract Request Services.(This will support both services and material contracts)

If AddOninfo2 is not maintained then when you send a contract that will be shown as contract request on CIG tracker.(This will only support material contract)

Hope this is clear.

Regards,

Sunitha V S

[former_member761922]

Hi Sunitha,

Thanks a lot for explaining the process, in our CIG we have maintained only Addon (please refer screenshot) is this right place to check ?

[former_member651171]

Hi Shivakumar,

Please look into below, this might help you

On the CIG tracker, right side top corner click on your profile name and then basic data

Then validate the details against the system ID you are using. Also please note once you have maintained the addon version you cannot downgrade or remove the same. Also these details are auto populated when you run initial data sync from your backend SAP system. That is when you run Synchronise SAP Information with SAP Ariba Cloud Integration Gateway from SPRO.

Regards,

Sunitha V S

[pboucquiaux]

Hi dears,

I have exactly the same issue on my SAP backend system (EHP8 package 16 and ARBCI10014 & ARBCI20010).

I removed the second component from the system definition in basic data and resend one message from Ariba Contract.

I was expecting to have the old message, "contractRequest", but unfortunately the message "ContractRequestServices" was still determined by CIG.

Anyone has any suggestion?

I will raise a SR for invetsigation because during a previous test, the first message was used and after few days, the second one appears and I don't remember to implement a significant change which explains this switch.

Thanks in advance

Regards

[pboucquiaux]

Finally to resolve the error message with this document type, Ariba provided a content item:

185232 - CIG ERP Error: "CX_FEH_CONSISTENCY_ERROR:An exception with the type CX_FEH_CONSISTENCY_ERROR was raised" for ContractRequestServices messages

https://connectsupport.ariba.com/sites#item-view&/185232

By maintaining this customizing point, the contract is processed by the system:

Go to SPRO > SAP Customizing Implementation Guide > Cross-Application Components > Process and tools for Enterprise Application > Enterprise Services > Error and Conflict Handler > Assign Caller to a Business Process.

Add the following entries in "Mapping from API and API Method to Business Process" screen.

API Name: II_ARBCIG_QUOTE_PURCH_CONTRACT

API Component: QUOTE_MESSAGE_PURCH_CONTRACT

Call Type: Inbound Service

Component: CA-SOA-ESM-ERP-MISC

Business Process: PURCONT001

Hope this will help other people 😉

Regards

Pascal Boucquiaux

[former_member651171]

Hi Pascal,

CIG doesn't allow you to downgrade or remove the SP version thats already maintained in Basic data. Can you please check again if ABRCI2 component is really removed from your project's basic data.

Regards,

Sunitha V S

[pboucquiaux]

Hi Sunitha,

thanks for your comment. for the downgrading, I had to delete the entry and recreate it manually with a lower version.

But this didn't resolve the issue. It seems that this message type is now the default one.

regards