Latest version of contract does not getting linked to changed requisition despite the contract being chosen in the initial version of the requisition.

This can happen due to any one or more of the following reasons:

1. Previous version of requisition has been received or serviced (even partially) .
2. Previous version of requisition has invoices that have been reconciled.
3. Parameter Application.Contract.MasterAgreement.EnableAutoSelect is disabled.
4. Parameter Application.Contract.MasterAgreement.EnableAutoSelect is enabled and Application.Procure.RestrictAutoAttachingContractsOnChangeOrders is enabled.
5. Shop By Contract option (available only in standard P2P and not Guided Buying) was used to create the Requisition. In this case, the latest changed version of the contract will not get linked to the requisition change.
6. If the contract is imported as part of the Requisition import file or web service payload, then the latest version of the contract will not attach to the requisition on change.

Parameter Application.Contract.MasterAgreement.EnableAutoSelect is available in the Intelligent Configuration Manager(ICM) and therefore can be managed by customer administrators. Please create a case for SAP Ariba Support in case you need parameter Application.Procure.RestrictAutoAttachingContractsOnChangeOrders to be updated.

Purchasing > Contract Compliance > Contract-Based Requisitions