Create Requisitions from XML-Based Punchouts with Purchase Agreement References

Create requisitions from XML-based punchouts with contract purchase agreement or blanket purchase agreement references in the Redwood Self Service Procurement application. You can create requisition lines using XML-based punchouts that will now honor the agreement referenced in the payload. You must pass an agreement reference for a contract purchase agreement and both agreement and line details for a blanket purchase agreement.

Here's an illustration of a blanket agreement reference in the payload.

<contract>
    <buyerContract>
         <contractNumber>1007144</contractNumber>
         </buyerContractLineNumber>1</buyerContractLineNumber>
    </buyerContract>
</contract>

Before this release, for an XML-based punchout process, an agreement would be automatically sourced. With this update, an agreement returned with the punchout payload will be used to source the requisition line.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Procurement

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Procurement

If you want to use the Create Requisitions from XML-Based Punchouts with Purchase Agreement References feature, then you must opt in to one or both of these features:

• Enable the Redwood Version as the Default Self Service Procurement Application: Makes the Purchase Requisitions (New) work area available to all your users, and hides the Purchase Requisitions work area from all your users.
• Procure Goods and Services Using the Redwood Self Service Procurement Application: Keeps the Purchase Requisitions work area available to all your users, and makes the Purchase Requisitions (New) work area available to the users who are assigned this privilege: Manage Requisition with the Redwood Self Service Procurement Application (POR_MANAGE_REQ_WITH_PWA_PRIV).

If you’ve already opted in, then you don’t have to opt in again.

Tips And Considerations

If the agreement provided in the payload is invalid or inactive, the requisition will then follow the autosourcing process to source a valid contract purchase agreement. 

Key Resources

• To know how to provide the required privileges to your requesters to use your own configured role instead of the Requisition Self Service User role, refer to the Privileges Required for a Predefined Role for a Requisition Self Service User topic.
• For more information on how to enable a guided journey for Redwood pages, refer to the Enable a Guided Journey for Redwood Pages topic.
• For information about using Oracle Visual Builder Studio to extend your Redwood application pages, see Oracle Fusion Cloud HCM and SCM: Extending Redwood Applications for HCM and SCM Using Visual Builder Studio.

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

• Manage Requisition with the Redwood Self Service Procurement Application (POR_MANAGE_REQ_WITH_PWA_PRIV) to access the Redwood Self Service Procurement application. 

NOTE: This privilege isn’t required if you have opted in to the Enable the Redwood Version as the Default Self Service Procurement Application feature to access the Redwood Self Service Procurement application.

This privilege was available prior to this update.