Order confirmation is failing with error: allDetail is not a valid confirmation status for header level

	English	
Deutsch - Machine Translation Español - Machine Translation Français (France) - Machine Translation Italiano - Machine Translation 日本語 - Machine Translation 한국어 - Machine Translation Português (Brasil) - Machine Translation Русский - Machine Translation 简体中文 - Machine Translation

Support Note KB0400770

Symptom

Order Confirmation is failing with the error allDetail is not a valid confirmation status for header level.

Cause

There are two possible causes for this issue:

Entitlement Enhanced order confirmation integration capabilities is enabled on the buyer's account.
Entitlement Enhanced order confirmation integration capabilities for hosted and integrated suppliers is enabled on the buyer's account as well as feature CSC-23050.

Type="allDetail" is required when the above entitlements are enabled. The entitlement also requires that the confirmation contain ConfirmationItem elements with line item information from the order.

Feature CSC-23050 adds extrinsic allDetailOC to POs originating from SAP Ariba Buying and Invoicing as it does not support allDetail order confirmations.

Resolution

This is a two-step process which covers enabling feature CSC-23050 in SAP Business Network and carrying out customization in SAP Ariba Procurement.

In SAP Business Network, the buyer needs to enable entitlement Enhanced order confirmation integration capabilities for hosted and integrated suppliers.

If this entitlement is already enabled and feature CSC-23050 is enabled as well, the supplier needs to send an order confirmation with type="accept", type="reject" or type="detail" at the header level whenever the Purchase Order (PO) is originating from SAP Ariba Procurement.

In SAP Ariba Procurement : (Only applicable if SAP Ariba Procurement sends orders to the SAP Business Network)

Create a custom-derived field cus_allDetailOC of type text at PurchaseOrder level in SAP Ariba Buying and Invoicing through the Field Configuration section under Customization Manager.
Set the expression to "notAllowed".
Don't click on any other box to ensure it does not show up on the UI.
Mark it as an External field and publish the customization.

POs created after customization can be identified by extrinsic allDetailOC in the Payload.

<Extrinsic name="allDetailOC">notAllowed</Extrinsic>

This field will need to be created/exported from the ERP if the PO is sent to the SAP Business Network from the ERP.

See Also

The Business Network recognises the <Extrinsic name="allDetailOC">notAllowed</Extrinsic> tag and sends the type as Detail instead of allDetail in the OC CXML when an Order Confirmation is done by the supplier and send to SAP Ariba Buying and Invoicing. Ariba B&I is hence able to recognise the OC thus resolving the problem.

Applies To

Purchasing > Purchase Orders > Order Confirmation
SAP Integration Suite Managed Gateway > Managed Gateway for Business Network SCC > Managed Gateway for Buyer Business Network SCC