Previously, Ariba Procurement solutions did not allow customers to specify a contract ID during requisition import. Contracts were auto-selected by the system for use with imported requisitions.

Now, Ariba Procurement solutions have been enhanced to allow customers to specify a contract ID during requisition import. The contract with the specified contract ID is imported along with the requisition and will be associated with it.

Action Required / Change Impact:

The contract ID must be specified in the new ContractId column, for file channel import. It must be specified using the new ContractIdStaging tag for each line item, for the web services channel.

Workflow for importing contract during requisition import:

The contract import with the requisition import has the following workflow:

1. The user specifies a contract ID and initiates requisition import using either file channel import or web services.
2. The system checks if the specified contract ID is valid. If the contract ID is valid, the requisition import moves to the next step. If the ID is invalid, an appropriate error is generated, and the requisition import is reverted.
3. The system retrieves the corresponding contract checks if the contract is active. If it is active, the requisition import moves to the next step. If it is not, an appropriate error is generated, and the requisition import is reverted.
4. The system checks if the contract matches the requisition line item. If it matches the line item, the requisition import moves to the next step. If it does not, an appropriate error is generated, and the requisition import is reverted.
5. The retrieved contract is associated with the imported requisition. This step overrides the auto-selection of contracts by the system.

Data migration:

In order for a customer site to use the contract ID import functionality introduced with this enhancement, customer administrators belonging to the Integration Admin group must review and accept the data definition changes for this feature.

Note: If a customer does not need this functionality, they can defer accepting the data definition changes. This ensures that requisition import will continue the legacy behavior.

After the data migration, the data import configurations must be similar to the samples in the following sections.

File channel import:

Specify the contract ID in the RequisitionDetail.csv file used for requisition import, in the ContractId column, as shown in the following sample.

Cp1252
Requisition_Number,Line_Number,ParentLineNumber,OriginatingSystemLineNumber,Supplier,Supplier_Location,Contact_Id,DeliverTo,Need_By_Date,CommonCommodity_Code,Domain,Commodity_Code,Quantity,Unit_Price,Unit_Of_Measure,Currency,Item_Description,ManPartNo,ItemPartNo,SplitAccountingType,Region,BuyerPartNumber,Facility,UnitConversion,PriceUnitQuantity,PriceUnit,PricingDescription,Account_Type,TaxCode,DiscountAmount,ChargeType,ChargeAmount,ContractId
"5302",1,1,1,,,,"Sample DeliverTo","02/10/2020","51",unspsc,"","500","200","EA","USD","VGA Cables",SampleManPartNo,SampleItemPartNo,,SE10,"EOEGeneral","Pittsburgh","1","2","EA","Price for 2 boxes","Expense","TC_US_ITEquipment",-10,"Handling",50,C14

In this sample CSV file, the contract ID specified is C14.

Web services import:

Specify the contract ID in the requisition import web services export XML file, in the <urn:ContractIdStaging></urn:ContractIdStaging> tag within the <urn:LineItems></urn:LineItems> section, as shown in the following sample:

<urn:ContractIdStaging>C14</urn:ContractIdStaging>

In this example, C14 is the unique name of the contract.

Purchasing