Confirmation Types That Require Descriptive Flexfield Setup

You need to configure descriptive flexfields on the PO header and PO line if you want your users to be aware of some changes from suppliers that can't be processed by Oracle Fusion Purchasing.

The XSL file for this predefined message definition, OBN-cXML-1-2-011-ConfirmationRequest-In, maps descriptive flexfields with the following API names to convey information about specific confirmation types acknowledgment codes. You can configure descriptive flexfields with the same API names or modify the XSL and replace them with your descriptive flexfield API names.

Flexfield API Name	When Used
Header Level Descriptive Flexfields (60 characters)
b2bAckReviewRequired	This field displays the following text when an acknowledgment code is received that can't be updated by a change order: One or more lines have acknowledgment comments. You can change the text by modifying the variable HeaderFlexfield in the XSL file.
Line Level Descriptive Flexfields (50 characters)
b2bProvidedDateNote	When a confirmation that includes a date is received in the message, this field will be updated to describe the type of date that was provided.
b2bProvidedDate	This field is populated if a date is provided in the confirmation message, and it doesn’t match what is expected based on the Buyer Managed Transport setting selection on the PO or in the case of a partial backorder this field is always populated with the date received.
b2bPartNumberCorrection	When a confirmation type value is in the lineChange type list and a SupplierPartID is received in the confirmation, the SupplierPartID is mapped to this flexfield if the feature Correct the Supplier Item Number on Purchase Orders isn't enabled.
b2bUOMChange	When a confirmation has a confirmation type value in the lineChange type list and a UnitOfMeasure, this flexfield is populated with the new UOM.