
If you would like to use Import ERP Push Error on a document stuck in Ordering and move it to Composing status, PurchaseOrderErrorImport.csv needs be used in the above mentioned tasks without having data in PurchaseOrderItemImport.csv.įor more details, please refer to the Data Dictionary from Core Admin Section. Similarly for change orders stuck in Ordering, the Import Change Purchase Order Status task can be used. As a system admin created users accounts and gave required roles to the users’ profiles and ensured the number of user licenses purchased does not exceed Experience in configuring Ariba. PO_ITEM is the Line Item number and ERP_PO_ITEM is the SAPPOLineNumber PO_ITEM,ERP_PO_ITEM,PACKAGE_INFO,SRVMAPKEY,ERPORDERID This causes integration issues during change order/receipt/invoice/payment with ERP.ĮRPORDERID is the Ariba Order ID and EBELN is the ERP Order ID Even though the system allows you to load the Order ID using only PurchaseOrderHeaderImport.csv file, SAPPOLineNumber is not updated in the POs if the PurchaseOrderItemImport.csv is not used.


You may keep the Header Status and error files empty, but make sure that there are values in the last two files. PurchaseOrderERPHeaderStatusFileImport.csv

To import the Order ID, please use the Import Purchase Order Status task using the Full Load operation. However, it is possible to import the Order ID manually via Core Administration > Data Import/Export. It is not possible to rerun the web service to import the Order ID again, since Ariba Procure-to-Pay waits for the web service answer only for a certain amount of time.
