This article goes over how to automatically create a purchase requisition (PR) in SAP Ariba when a contract is completed in Ironclad. Once configured, completing a workflow with contract line items in Ironclad triggers the contract sync job to create the matching purchase requisition in SAP Ariba, with line items, quantities, units of measure, and pricing carried over.
Use Case
Use this feature for contract-first purchasing. When your team negotiates and signs the agreement in Ironclad before any purchase exists in SAP, procurement still needs a requisition in SAP Ariba to act on it. Rather than re-typing line items into SAP Ariba after signature, configure purchase requisition creation so that executing the contract in Ironclad automatically generates the PR in SAP.
Prerequisites
| Features | Integrations, APIs, Workflows |
| Connected Systems | SAP Ariba |
| Packages |
SAP Procurement Automation |
| Permissions |
|
Configuring Purchase Requisition Creation
Purchase requisition creation is triggered by the contract sync job. When a workflow completes in Ironclad, the contract sync picks up the executed contract and, if PR creation is enabled for that configuration, creates a purchase requisition in SAP Ariba using the contract’s line items.
For this to work, there are three requirements:
- The contract sync job is set up and functioning. Learn more in Sync Contracts Between Ironclad and SAP Ariba.
- Enforced Terms is enabled at the item level, with your line items table attribute set as the source.
- The Generate PR from Contract toggle under Purchase Requisition is turned on. This toggle controls whether a PR is created when the contract syncs.
Step 1: Configure the BTP Integration Suite Connection
This feature uses an SAP BTP Integration Suite connection to communicate with SAP. Configure the BTP connection setting with credentials from your BTP service key:
| Field | Description |
|---|---|
| Instance URL | The URL of your BTP Integration Suite instance. |
| Token URL | The OAuth token endpoint for your BTP instance. |
| Client ID | The OAuth client ID from your BTP service key. |
| Client Secret | The OAuth client secret from your BTP service key. Store this securely. |
To access the BTP connection setting:
- In Ironclad, click your profile picture in the top right corner and select Company Settings.
- Click the Integrations page in the left sidebar menu.
- Under Procurement, click SAP Ariba.
- Click the Connection Settings tab and scroll down to the Connect to BTP Integration Suite section.
- This is where you’ll find the Instance URL, Token URL, SAP STP Client ID, and SAP STP Client Secret that comes from Atlassian.
Step 2: Configure Workflow Field Mappings
Under the Workflow Sync tab set up a workflow sync configuration with field mappings so launch forms can be pre-filled and line items flow through to the purchase requisition. The essential mapping for this feature is the Line Items section.
This makes it easier to prefill the Line Items Workflow Table Attribute with line items from an existing purchase requisition. That table attribute is what the integration reads when it builds the purchase requisition.
Once you’ve set up your workflow configuration, you can enable purchase requisition creation under the Contract Sync tab.
Step 3: Enable Purchase Requisition Creation in Contract Sync
To enable purchase requisition creation:
- Click the Contract Sync tab.
- Under Operational Compliance, check the box next to Enforce terms during purchasing.
- Under Line Item Document, select Table Attribute as the source.
- Under Purchase Requisition, check the box next to Generate PR from contract.
- Map any remaining attributes.
Beyond the line items table, the configuration only needs the basic required attributes for the contact workspace.
Launch a Workflow to Create a Purchase Requisition
Once configuration is complete, PR creation happens automatically when a contract is executed. To launch a workflow:
- In Ironclad, navigate to your Dashboard.
- Click New in the top right corner and select Start a workflow.
- Select a workflow and click Use this workflow.
- Click the Pull from SAP Ariba button.
- When prompted, choose an object (like an existing PR) to fill data in the launch form.
- Click Fill Launch Form.
- Review the line items table to make sure it’s accurate. Each line item needs a:
- Name
- Unit of Measure
- Quantity
- Price
Note:
SAP’s proper value for a unit of measure if the UoM code (for example, EA for “each”). Ironclad includes mapping logic that converts friendly values like “each” or “dozen” to the correct SAP code automatically, so either format works.
- Click Save to preserve your changes, or Submit to launch the workflow.
- Complete the workflow’s approval and signature steps.
Once the contract is executed and archived, the next contract sync run creates the purchase requisition in SAP Ariba. When you click the workflow to open the overview panel, you’ll be able to tell the contract sync went through under the External links section. If there’s an option to View in SAP Ariba, your contract sync was successful.
Note:
If you pre-fill the launch form from an existing requisition, Ariba may include sales tax line items in the table. Remove these before submitting. The purchase requisition should only contain the raw items being purchased.
Verify the Purchase Requisition in SAP Ariba
To view the purchase requisition that was created:
- In Ironclad, confirm the workflow appears in the contract sync history by clicking the overview panel for your workflow and checking the External links section. If there’s an option to View in SAP Ariba, your contract sync was successful.
- Log in to SAP Ariba and make sure you’re in your child realm. The child realm is where purchase requisitions are created.
- Search for Requisitions.
- Open the requisition created for your contract. You should see the contract’s line items with the correct quantities, units of measure, and pricing.
Resources
Explore articles, courses, and support options to get the most out of Ironclad.
Support