Procurement - Integration Tracker - SAP Variant

File Name Task
PurchasingUnit.csv Import Purchasing Units
Import Currency Conversion

CurrencyConversionRate.csv Rates
POConditions.csv Import PO Conditions
AccountType.csv Import Account Types
ItemCategory.csv Import Item Categories
AccountCategory.csv Import Account Categories

Common/Accountng
CompanyCode.csv Import Company Codes
GeneralLedger.csv Import General Ledgers
Import Account Category Field

AccCategoryFieldStatusCombo.csv Status Combinations
CostCenter.csv Import Cost Centers
InternalOrder.csv Import Internal Order Codes
Import Company Code Internal

CompanyCodeIOCombo.csv Order Mapping
WBSElement.csv Import WBS Elements

Import Company Code WBS
CompanyCodeWBSCombo.csv Mapping
Asset.csv Import Assets
Network.csv Import Networks
ActivityNumber.csv Import Activity Numbers
PurchaseOrg.csv
Plant.csv Import Plants Data
Import Plant to Purchase

PlantPurchaseOrgCombo.csv Organization Mapping
PurchaseGroup.csv Import Purchase Groups
IncoTerms.csv Import Incoterms
Import Supplier Data

SupplierConsolidated.csv (Consolidated File)
Import Supplier Location Data
SupplierLocationConsolidated.csv (Consolidated File)
Suppliers
Import Remittance Location Data

RemittanceLocationConsolidated.csv (Consolidated File)
Import Purchase Organization to

PurchaseOrgSupplierCombo.csv Supplier Mapping
Import Preferred Supplier

PreferredSupplierMap.csv Mappings
PunchinGroup.csv Import Punchin Groups

Custom groups
CustomGroup.csv Import Custom Groups
Import Group To Child Group

GroupParentGroup.csv Mapping
Custom
GroupChildGroupMap.csv
Import User Data (Consolidated

Users and
UserConsolidated.csv File)
Groups
Import User to Group Mapping

GroupConsolidated.csv Data (Consolidated File)
Import Payment Terms Data

PaymentTermsConsolidated.csv
Payment
(Consolidated File)
Details
PaymentMethodType.csv Import Payment Method Types
Import Commodity Code/Import

CommodityCode.csv Commodity Code Hierarchy
Import Classification Code

ClassificationCodeMap.csv Relationships
Commodites / UOM
ERPCommodityCode.csv Import ERP Commodity Codes
Import ERP Commodity to

ERPCommodityCodeMap.csv Commodity Mapping
UnitsOfMeasure.csv Import Units Of Measure
UnitsOfMeasureMap.csv Import Unit Of Measure Mapping
TaxType.csv Import Tax Types (New)

TaxTypeMap.csv Import Tax Type Mappings (Both)
ChargeType.csv Import Charge Types (New)
TaxComponent.csv Import Tax Components (New)

Taxes
TaxCodeHeader.csv Import Tax Codes (New)
TaxCodeDetails.csv Import Tax Codes (New)
TaxCodeLookup.csv Import Tax Code Lookups (Both)
Import Tax Code Lookup Field

TaxCodeLookupFieldMapping.csv Map (New)
Import Tax Code Lookup Field

WHTLookupFieldMapping.csv Map for Withholding Taxes (New)
BudgetHeader.csv Import Budgets in ZIP File Format

BudgetPeriods.csv
BudgetLineItems.csv
Budget
BudgetAllocation.csv
BudgetAdjustments.csv Import Budget Adjustments
Import Flex Master Data Budget

BudgetPeriod.csv Period
Import Flex Master Data

CommitmentItem.csv Commitment Item
EarmarkedFundsDocument.csv Earmarked Funds Document

EarmarkedFundsLineItem.csv Earmarked Funds Line Item #
Funds Management
FMArea.csv Import Flex Master Data FM Area

FunctionalArea.csv Functional Area
Fund.csv Import Flex Master Data Fund
Import Flex Master Data Funded

FundedProgram.csv Program
Import Flex Master Data Funds

FundsCenter.csv Center
Grant.csv Import Flex Master Data Grant
Import Document Types for

DocumentType.csv Advance Payment
Import GL Indicators for Advance

GLIndicator.csv Payment
ments
Import Advance Payment
AdvancePaymentCancelReasonCodesImport.csv Cancellation Reasons
Advance Payments
AdvancePaymentIDImport.csv
Import Advance Payment Status
AdvancePaymentErrorImport.csv
CancelAdvancePaymentIDImport.csv
Import Cancel Advance Payment

Status
CancelAdvancePaymentErrorImport.csv
RelationType.csv Import Relations

Custom
RelatonEntry.csv Import Relation Entries
Import Flex Master Data To Be

FlexMasterData_ToBeDetermined.csv Determined
Import Account Category

AccountCategoryLang.csv Translation
AccountTypeLang.csv Import Account Type Translations
Import Commodity Code

CommodityCodeLang.csv Translation
CostCenterLang.csv Import Cost Center Translations

Import Custom Group
CustomGroupLang.csv Translations
Import General Ledger

GeneralLedgerLang.csv Translations
Translatons
Import ERP Commodity Code

ERPCommodityCode.csv Translations
IncoTerms.csv Import Incoterms Translations
Import Invoice Exception Type

InvoiceExceptonTypeLang.csv Translations
Import Item Category

ItemCategoryLang.csv Translations
Import Payment Method Type

PaymentMethodTypeLang.csv Translations
Import Payment Term

PaymentTermsLang.csv Translations
Import Tax Code Translations

TaxCodeLang.csv
NetworkLang.csv Import Network Translations
Approval Lookup Tables:

Customization Manager >
CostCenterOwners.csv Approval Rules Files > Supporting
Files
CommodityApprovers.csv
val Lookup Tables
NBidsPolicy.csv
Approval Lookup Tables
ContractApprovers.csv
ReceivingLookup.csv
InvoiceLimit.csv
InvoiceNonPOLimit.csv
InvoiceReconciliatonSupplierApprovers.csv
PurchOrdHeaderDetails.csv
PurchOrdLineDetails.csv
PurchOrdAcctDetails.csv
Export Purchase Order to ERP
PurchOrdLineAddDetails.csv
PurchOrdScheduleDetails.csv
PurchOrdLineText.csv
ChangePurchOrdHeaderDet.csv
ChangePurchOrdLineDet.csv
ChangePurchOrdAcctDet.csv
ChangePurchOrdSchdlDet.csv Export Change Purchase Order
ChangePurchOrdDelAcct.csv
ChangePurchOrdDelItems.csv
ChangePurchOrdLineText.csv
CancelPurchOrdHeader.csv Export Cancel Purchase Order
Export Purchase Order Close

ClosePurchOrdLineDetails.csv Status
Purchase Orders
PurchaseOrderIDImport.csv
Import Purchase Order Status
PurchaseOrderErrorImport.csv
PurchaseOrderChangeIDImport.csv
Import Change Purchase Order
Status
PurchaseOrderChangeErrorImport.csv
PurchaseOrderCancelIDImport.csv
Import Cancel Purchase Order
Status
Import Cancel Purchase Order
Status
PurchaseOrderCancelErrorImport.csv
PurchaseOrderCloseErrorImport.csv
PurchaseOrderCloseStatusHeaderImport.csv Import Purchase Order Close

Status
PurchaseOrderCloseStatusItemImport.csv
No file (this feature is available only via web-

service) Fetch Purchase Order Details
ReceiptHeaderDetails.csv
Export Receipts to ERP
ReceiptLineDetails.csv
ReceiptHeaderExport.csv
Receipts
ReceiptDetailExport.csv Export Receipts

ReceiptAssetExport.csv
ReceiptIDImport.csv
Import Receipt Status
ReceiptErrorImport.csv
ReceiptImport.csv Import Receipts
RequisitionHeader.csv
Reqs
RequisitionDetail.csv
Import Requisitions in 3 CSV Files
RequisitionSplitAccounting.csv
PaymentHeaderExport.csv
Payments
PaymentLineItemDet.csv
PaymentAccountDet.csv Export Payment Requests
PaymentDetailExport.csv
PaymentTaxExport.csv
PaymentHeaderExport.csv
ents including
nce payments
PaymentLineItemDet.csv
Export Payment Requests with

Advance Payments
Payments including
Advance payments
PaymentDetailExport.csv
Export Payment Requests with
Advance Payments
PaymentTaxExport.csv
EnhancedPaymentAccountDet.csv
AdvancePaymentDetailExport.csv
InvoiceIDImport.csv
Invoice
Import Invoice Status

InvoiceErrorImport.csv
Remittance
Remittance.csv
Advice
Import Remittance
RemittanceDetails.csv
Remitance Advice
Advance Payment
AdvancePaymentRemittance.csv
Import advance payment
remittance
AdvancePaymentRemittanceDetails.csv
Import Demand Holding Rules

Aggregaton
DemandHoldingRule.csv
Demand
Import Assignment Rules for

DemandAssignmentRule.csv Demand Aggregation
Import Demand Aggregation

DemandAggregationRule.csv Rules
Export Service
Entry Sheets
File Descripton
Declares the entities that are used by Ariba to enforce data segregation and visibility
controls. Transactional documents (Requisitions, Invoices, etc) are assigned to a Purchasing
Unit. Users are also assigned to one or more purchasing units for one or more roles, and
therefore granted access to the transactional documents that reside in those Purchasing
Units. Master data such as suppliers can be assigned to a Purchasing Unit, limiting their
visibility to users. Purchasing units also allow for more granular control of other
configurations/mappings like receiving types, commodity code maps, terms and
conditions, PO logos, etc. They can also be used to partition approval routing/notifications.
Customer-defined conversion rates between currencies.
Contains the Terms and Conditions that will be included on Purchase Orders to suppliers.
In addition to commodity code, the Account Type is used as a "helper", or another

element of criteria, to determine what default accounting elements to code an item to.
Common Account Types are "Expense" and "Capital". In ERPCommodityCodeMap.csv
(below) if there are two mappings to default accounting for a given commodity code with
two different Account Types, then the Account Type the user has selected will determine
which accounting values will be defaulted.
Defines SAP item categories.
Defines account categories.
The SAP accounting entity company code. A company code represents an independent
accounting unit within a client. Each company code has its own balance sheet and its own
profit and loss statement.
Defines the SAP accounting entity general ledger (G/L).
The combinations of SAP account category and field status codes. This information is used
to simulate the accounting combinations used in your SAP system. It is used to filter the list
of general ledgers based on valid combinations of account category, company code field
status variant, and general ledger field status group.
Define cost centers. A cost center is typically an organizational unit within a controlling
area that represents a clearly defined location where costs occur.
The SAP accounting entity internal order (IO). Typically internal orders are used to plan,
collect, and settle the costs of internal jobs and tasks.
The combinations of SAP company codes and internal orders.
The WBS elements. All projects created in SAP must contain a project definition, and at
least one work breakdown structure (WBS) element. WBS elements represent a part of the
project and track financial information.
The combinations of SAP company codes and WBS elements.
Defines the SAP accounting entity asset.
The SAP purchasing organizations. A purchasing organization is an organizational unit

responsible for procuring materials or services for one or more plants and for negotiating
general conditions of purchase with vendors.
Contains the Ship To and Bill To addresses that are referenced by other master data
elements like users and on transactional data like purchase orders. All Ship To and Bill To
addresses must be defined in this file.
Defines combinations of SAP plants and purchasing organizations. A plant is assigned to
one or more purchasing organizations.
The SAP purchasing groups. Purchasing groups are responsible for the day-to-day buying
activities of purchasing organizations. A purchasing group can act for several purchasing
organizations.
This file defines the first layer of the Ariba supplier hierarchy, the top-level vendor
information.
This file defines the second layer of the Ariba supplier hierarchy, the supplier ordering
locations.
This file defines the third and final layer of the Ariba supplier hierarchy, the remittance
locations. Remittance locations are where a buyer sends their payment to a supplier.
This file defines combinations of SAP purchasing organizations and suppliers.
This file defines the preferred suppliers for Non-Catalog Purchases
This file is used to define a customer's Punchin groups. Punchin groups are generally used
by customers to associate the kind of catalog views the users should be able to see.
This file is used to define a customer's custom groups. Custom groups are used by
customers to:
1. Consolidate several Ariba system groups (which include privledges or permissions that
are inherited) to a single group.
2. Route approval requests.
These files are used to map Ariba system groups to customer defined custom groups in a
parent/child relationship. When a custom group is made a child of an Ariba system group,
the custom group inherits all of the permissions/abilities that intrinsically belong to the
parent Ariba system group.
These files are used to map Ariba system groups to customer defined custom groups in a
parent/child relationship. When a custom group is made a child of an Ariba system group,
the custom group inherits all of the permissions/abilities that intrinsically belong to the
parent Ariba system group.
This file is used to define users and various attributes associated with the user in Ariba.
This file is used to map users to groups and, optionally, purchasing unit responsibilities for
those groups.
This file define's a customer's payment terms. Payment terms define the date when the
net amount of an invoice is due to a supplier, as well as any discounts for early payment.
This file defines the payment methods of a customer's ERP. Each customer payment
method must be mapped to an Ariba-native payment method, and no two customer
payment methods can map to the same Ariba-native payment method.
This file is used to define commodity codes and their hiearchy. Ariba's default commodity
code set is based off of the UNSPSC standard.
This file is used to map the commodity codes that suppliers may use on their catalogs to
commodity codes that are recognized by Ariba.
This file is used to define the commodity codes used by the customers ERP or procurement
system. The commodity codes defined in this file will be returned to the ERP on
transactional documents outbound from Ariba. These typically represent SAP material
groups.
This file is used to:

1. Map the Ariba system commodity codes to the ERP commodity codes that are specific to
the customer. Many Ariba system commodity codes can be mapped to a single ERP
commodity code, but a single system commodity cannot be mapped to mulitple ERP
commodity codes (unless AccountType is a differentiator).
2. Map the Ariba system commodity codes to default accounting information (typically
Account and SubAccount). Based on the commodity code of items in a Requisition or
Invoice, Ariba will default the accounting elements according to the information provided
in this file.
Defines units of measure. Units of measure are terms that describe how items are
packages, such as by the box, by the unit, or by the pound.
Defines mappings for UNCEFACT (also called UNUOM) units of measure. In Ariba Buyer,
this data import task translates between canonical units of measure and the units of
measure in a partition.
Defines tax types to create tax components or to add taxes to invoices

This file maps tax types that a supplier may use on their electronic invoices to Ariba-native
tax types.
Defines charge types to apply charges on requisitions and invoices.
Defines Tax Components that can be assigned to Tax Codes.
Defines details about the tax codes
Defines components and sequence for the tax codes specified in TaxCodeHeader.csv.
This file is used to determine what Tax Code a tax charge on an invoice should be applied
to. Out-of-the-box, Ariba makes this determination based on the ShipTo juristiction, the
Ship From juristiction, and an item's commodity code.
Defines tax code look up field mappings based on line item fields on the approvables
(Req/Inv/IR) to apply taxes.
Defines tax code look up field mappings based on line item fields on the approvables
(Inv/IR) to apply withholding taxes.
This file defines the title of the budget.

This file defines the budget periods.
This file defines the budget codes and accounting strings that make up the budget.
This file defines allocation and/or available amounts for the budget codes and periods
defined in BudgetPeriods.csv and BudgetLineItems.csv.
This file allows for loading adjustments to previously-loaded budgets.
Defines budget period.
Defines commitment item.

Defines Earmarked Funds Document
Defines Earmarked Funds Line Items
Defines FM Area
Defines Functional Area
Defines Fund
Defines Funded Program
Defines Funds Center
Defines Grant
Defines document type for Advance payments
Defines GL Indicators
Defines the payment cancellation reasons in Ariba.
These files are used to import the Advance Payment Ids and/or error details for Advance
Payment exported via the "Export Advance Payment" task.
Payment exported via the "Export Advance Payment" task.
Payment exported via the "Export Cancel Advance Payment" task.
Payment exported via the "Export Cancel Advance Payment" task.
This file is used to declare relationships between two data elements. It is only used in
conjunction with Ariba customizations.
This file is used to declare relationships between two data elements. It is only used in
conjunction with Ariba customizations.
Customer requirements may result in the need for Ariba to perform a customization to
create a new data element. This placeholder is for a file where the customer would define
the instances of such a custom data element.
This file is used to load the translation for the Account assignments that gets used on the
transactions
This file is used to load the translation of the account types that are used on the
transactions. This is usually a one time file load.
This file is used to load the translation of commodity codes. One has to worry about this
only if you introduce some new codes that were missing OOTB, for all OOTB there is a
translation available.
This file is used to load the translation of the account types that are used on the
transactions. This is usually a one time file load.
This rule helper file defines and adds as an approver the manager(s) of the cost center(s)
on the Requisition and/or Invoice Reconciliation document(s).
This rule helper file adds an approver of the customer's choice if the Requisition contains
any items that are assigned to a specified commodity code.
This rule helper file defines your "N Bids and a Buy" policy (i.e., which commodites/dollar
amounts require multiple suppliers bids before purchasing).
This rule helper file adds an approver of the customer's choice if the Contract Request Max
Amount is within a range of the customer's choice.
This rule helper file adds a receiver of the customer's choice if the receipt is against a PO
that contains any items that are assigned to a specified commodity code.
This rule helper file adds an approver of the customer's choice if the invoice total is within
a range of the customer's choice. It applies only to PO-based invoices.
This rule helper file adds an approver of the customer's choice if the invoice total is within
a range of the customer's choice. It applies only to non-PO-based invoices.
This rule helper file adds an approver of the customer's choice if the invoice is for a
supplier of the customer's choice.
These files contain details about purchase orders created in Ariba.

These files contain details about change purchase orders created in Ariba.
This file contains information about purchase orders that have been cancelled in Ariba.
This file contains close status information of the orders that have been closed in Ariba.
These files are used to import the purchase order numbers and/or error details for
purchase orders exported via the "Export Purchase Order to ERP" task.
purchase orders exported via the "Export Purchase Order to ERP" task.
These files are used to import the purchase order numbers and/or error details for change
purchase orders exported via the "Export Change Purchase Order" task.
These files are used to import the purchase order numbers and/or error details for change
purchase orders exported via the "Export Change Purchase Order" task.
cancelled purchase orders exported via the "Export Cancel Purchase Order" task.
cancelled purchase orders exported via the "Export Cancel Purchase Order" task.
This file is used to update the status of the PO close error from the external system
This file is used to update the status of the PO close ID at the header level
This file is used to update the status of the PO close ID at the line item level. This file needs
to go along with the header PO close status file indicating which line item is acknowledged
to be closed from ERP.
This task allows any web-service caller to invoke a web-service in Ariba that would return
the attachment and comments associated with a PO number.
The caller must send the PO# for which they are expecting to receive the attachmenta and
comments for.
These files contain details about receipts created in Ariba.

These files are used to import the receipt numbers and/or error details for receipts
exported via the "Export Receipts to ERP" task.
These files are used to import the receipt numbers and/or error details for receipts
exported via the "Export Receipts to ERP" task.
This file is used to import receipts into Ariba.
These files are used to import requisitions into Ariba.
These files contain details about payment requests (i.e., fully reconciled invoices)
generated in Ariba
generated in Ariba
generated in Ariba
generated in Ariba
generated in Ariba
These files contain details about payment requests (invoices and advance payments)
These files are used to import the ERP invoice numbers and/or error details for payment
requests exported via the "Export Payment Requests" task.
These files are used to import the ERP invoice numbers and/or error details for payment
requests exported via the "Export Payment Requests" task.
These files are used to import remittance details into Ariba.
These files are used to import remittance details into Ariba.
These files are used to import remittance details that includes

advance payments into Ariba.
These files are used to import remittance details that include

advance payments into Ariba.
Associates demand holding rule with commodity codes. If you have to define Line Type it
should be Catalog or Non Catalog along with commodity code and additional configuration
rules.
Associates demand assignment rule with commodity codes. If you have to define Line Type
it should be Catalog or Non Catalog along with commodity code and additional
configuration rules.
Associates demand aggregation rule. If you have to define CompanyCode along with ShipTo
and DeliverTo configuration rules.
Fil
File Dependencies (optional and Ariba B&I

When Is This Task Needed? required) (P2P)
When implementing purchasing unit functionality Y
When transacting in multiple currencies Y
When you want to include "terms and conditions"

language on PO's PurchasingUnit.csv Y
Always Y
P2X:Always
Invoice Pro: When you want to identify the item Y
category on copy orders
Always Y
Always PurchasingUnit.csv Y
When using general ledgers in Ariba CompanyCode.csv Y
GeneralLedger.csv, CompanyCode.csv,
When using general ledgers in Ariba AccountCategory.csv Y
When using cost centers in Ariba CompanyCode.csv, PurchasingUnit.csv Y
When using internal orders in Ariba CompanyCode.csv Y
When using internal orders in Ariba CompanyCode.csv, InternalOrder.csv Y
When using WBS elements in Ariba Y

When using WBS elements in Ariba CompanyCode.csv, WBSElement.csv Y
When using assets in Ariba CompanyCode.csv Y
Always CompanyCode.csv, PurchasingUnit.csv Y
Always CompanyCode.csv Y
Always Plant.csv, PurchaseOrg.csv Y
Always PurchasingUnit.csv Y
When using Inco terms in Ariba Y
When maintaining suppliers via file instead of or in

addition to via UI PurchasingUnit.csv Y
When maintaining suppliers via file instead of or in

addition to via UI SupplierConsolidated.csv, Pcard.csv Y
When validating remittance locations on invoices and SupplierLocationConsolidated.csv,

maintaining via file instead of via UI PaymentMethodType.csv Y
SupplierConsolidated.csv,
When maintaining suppliers via file instead of via UI PurchaseOrg.csv, Y
PaymentTermsConsolidated.csv
SupplierLocationConsolidated.csv
ERPCommodityCode.csv
,
When maintaining Preferred Suppliers. Plant.csv Y
, Supplier.csv
When using punchin groups that needs to be sent

across to APC sites during Punch Out setup request. N
When using custom groups and maintaining via file

instead of or in addition to via UI (e.g., large volume Y
of custom groups)
When creating parent-child group references and

maintaining via file instead of or in addition to via UI CustomGroup.csv Y
Y
Plant.csv, CompanyCode.csv,
When maintaining users via file load instead of or in GeneralLedger.csv, PurchasingUnit.csv,
addition to via UI (or organic growth in APC) CostCenter.csv, PurchaseOrg.csv, Y
PurchaseGroup.csv
When maintaining user/group assignments and/or CustomGroup.csv,

responsible user assignments via file load instead of UserConsolidated.csv,
or in addition to via UI or via self-service user profile PurchasingUnit.csv Y
maintenance
When you want to print payment terms on a PO

and/or validate payment terms during invoice Y
reconciliation.
When maintaining payment methods via file instead

of via UI Y
When updating or replacing pre-loaded UNSPSC

codes and maintaining via file instead of or in Y
addition to via UI
When replacing UNSPSC with a custom taxonomy

and/or using ASCC codes as part of Ariba Services
Procurement module, and maintaining these CommodityCode.csv Y
mappings via file instead of or in addition to via UI.
When maintaining ERP Commodity Codes via file

instead of or in addition to via UI Y
P2X/Invoice Pro: When maintaining ERP Commodity CommodityCode.csv, Plant.csv,

CompanyCode.csv, CostCenter.csv,
Mapping via file instead of or in addition to via UI GeneralLedger.csv, Asset.csv,
APC: When there is a need to map UNSPSC to
WBSElement.csv, AccountCategory.csv, Y
ItemCategory.csv, AccountType.csv,
material groups, and maintaining the mapping via file ERPCommodityCode.csv,
instead of or in addition to via UI PurchasingUnit.csv
When updating pre-loaded UNUOM units of measure UnitsOfMeasureMap.csv Y
When updating or adding new mappings between

system UOMs and ERP or catalog UOMs and Y
maintaining via file instead of or in addition to via UI
When using tax calculation in Ariba Y

Always Y
When using Charges in Ariba Y
GeneralLedger.csv,
Plant.csv,
When multiple tax type scenarios are applicable. AccountCategory.csv, Y
CostCenter.csv,
CompanyCode.csv
TaxCode.csv, ERPCommodityCode.csv,
When validating taxes on invoices in Ariba PurchasingUnit.csv Y
When validating taxes in Ariba Y
When validating withholding taxes in Ariba Y

CompanyCode.csv, Asset.csv,
CostCenter.csv, GeneralLedger.csv,
When using budget check functionality InternalOrder.csv, WBSElement.csv, Y
PurchaseGroup.csv, PurchaseOrg.csv, Y
PurchasingUnit.csv
Y
When using budget check functionality and there is a

need to account for spend that occurred outside of BudgetHeader.csv, BudgetPeriods.cdsv,
the PO in Ariba against budgets, and doing it via BudgetLineItems.csv, Y
adjustment loads versus Available Amount in budget BudgetAllocation.csv
definition files
When using Funds Management Y

When using Advance Payments Y

When using Advance Payments
When using Advance Payments
When using customizations that leverage relation

entries Y
Dependency will vary - Ariba to
When using customizations that leverage relation
entries determine if file needed and the Y
dependencies
When using customizations that leverage Flex Master Dependency will vary - Ariba to
Data determine if file needed and the Y
dependencies
Y
Y

When using the "Cost Center Owners" rule on the
Requisition workflow determine if file needed and the Y
dependencies
When using the "Commodity Approvers" rule on the Dependency will vary - Ariba to
Requisition workflow determine if file needed and the Y
dependencies
When using "N Bids and a Buy" functionality determine if file needed and the Y
dependencies
When using the "Financial Contract Approval" rule on Dependency will vary - Ariba to
the Contract Request workflow determine if file needed and the Y
dependencies
When using the "Main Receiving Rule - Central Dependency will vary - Ariba to
Receiving by Commodity and Desktop Receiving" on determine if file needed and the Y
the Receipt workflow dependencies
When using the "PO Invoice Cap Rule" on the Invoice Dependency will vary - Ariba to
Reconciliation workflow determine if file needed and the Y
dependencies
When using the "Non-PO Invoice Cap Rule" on the
Invoice Reconciliation workflow determine if file needed and the Y
dependencies
When using the "Supplier Approvers" rule on the
Invoice Reconciliation workflow determine if file needed and the Y
dependencies
When exporting purchase orders to ERP or other
backend system and using the "ERP PO Export" Y
instead of the "Standard PO Export". Y
Y
Y
Y
When exporting change purchase orders to ERP or Y
other backend system and using the "ERP PO Export" Y
instead of the "Standard PO Export". Y
Y
Y
Y
Y
Y
When exporting cancel purchase orders to ERP or

other backend system and using the "ERP PO Export" Y
instead of the "Standard PO Export".
When using the ERP order method with

acknowledgements. Y

acknowledgements. Y
Y
acknowledgements.
acknowledgements.
Y
When using close PO with acknowledgements Y
When using PO integration that requires Y

attachment and comments
When exporting receipts to ERP or other backend

system and using the ERP receipt export instead of or Y
in addition to the standard receipt export.
Y
When exporting receipts to ERP or other backend
system and using the standard receipt export instead Y
of or in addition to the ERP receipt export
Y
Y
When there is a need to notify Ariba of errors
creating the exported receipts in ERP. Y
Y
When there is a need to import receipts from an
external system into Ariba. Y
When there is a need to load requisitions/PO's from
an external system into Ariba Y
Y
When exporting payment requests (i.e., fully
reconciled invoices) to ERP or other backend system Y

reconciled invoices) to ERP or other backend system
Y
reconciled invoices) to ERP or other backend system
Y
When there is a need to notify Ariba of errors

creating the payment request/invoice in ERP. Y
When there is a need to load remittance

advice into Ariba to provide visibility into
Y
payment details to suppliers and certain
end users
When there is a need to load

remittance advice into Ariba to provide
visibility into payment details to Y
suppliers and certain end users
When using Demand Aggregation Y

Filter by solution
Ariba Ariba-
Ariba Buying (P2O) Ariba(APC)
Catalogs Ariba Invoice Mgmt Contract UI Alternative provided
(Invoice Pro) Invoicing SAP Code
Y N Y Y N N
Y Y Y Y N Y
Y N N N N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N Y
Y N Y Y N N
Y Y Y Y Y Y
Y N Y Y Y Y
N N Y Y Y Y
Y N Y Y Y Y
Y Y Y Y N ?
N Y N N N N
Y Y Y Y Y N
Y Y Y Y Y N
Y Y Y Y Y N
Y Y Y Y Y Y
Y Y Y Y Y Y
Y N Y Y N Y
N N Y Y Y N
Y Y Y Y Y N
Y Y Y Y Y N
Y Y Y Y Y Y
Y Y Y Y Y N
Y Y Y Y N N
Y Y Y Y Y N
Y N Y Y N N
N N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N N N N N
Y N N N N N
Y N N N N N
Y N N N N N
Y N N N N N
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N Y
Y N N N N N
Y N N N N N
Y N N N N N
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N
Y N Y Y N
Y Y Y Y N
Y N Y Y N
Y Y Y Y N
Y N Y Y N
Y Y Y Y N
Y N Y Y N
N N Y Y N
Y N Y Y N
Y N Y Y N
Y N Y Y N
Y N Y Y N
Y N Y Y N
Y N Y y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
Y N Y Y N N
N N Y N N N
N N Y N N N
N N Y N N N
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A N
Y N N N N/A N
Y N N N N/A N
Y N N N N/A Y
Y N N N N/A Y
Y N N N N/A N
Y N N N N/A N
Y N N N N/A N
Y N N N N/A N
N N N N N/A Y
N N N N N/A Y
N N N N N/A Y
N N N N N/A Y
N N N N N/A Y
N N N N N/A
N N N N N/A
N N N N N/A
N N N N N/A
N N N N N/A
N N N N N/A
N N N N N/A Y
N N N N N/A Y
N N N N N/A Y
N N N N N/A Y
N N N N N/A Y
N N N N N/A Y
Y N N No Yes N
Y N N No Yes N
Y N N No Yes N
WebService Option Required for
Where to load in Multi-ERP (FPC) Owner
available (Y/N) <Customer>
Parent or child* NO TBD <Customer>
Parent NO TBD <Customer>
Child NO TBD <Customer>
Parent or child NO TBD <Customer>
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
Both NO TBD <Customer>
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child

Both NO TBD <Customer>
Parent - if no PU is used.
Both - if PU and responsible PU NO TBD <Customer>
functionality is leveraged
NO TBD <Customer>
Child
Parent or child NO TBD <Customer>
Parent NO TBD Ariba
Parent NO TBD Ariba
NO TBD <Customer>
Child
NO TBD <Customer>
Child
Parent NO TBD Ariba
Child NO TBD Ariba

Parent NO TBD Ariba
Child NO TBD Ariba
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD <Customer>
Child
NO TBD Ariba
Child
NO TBD Ariba
Child
Child No TBD <Customer>

Child TBD <Customer>


No
No
Parent or child TBD Ariba
Parent or child TBD <Customer>
Parent or child TBD <Customer>
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Child No
Parent or child* No TBD <Customer>


Yes
Child Yes TBD <Customer>

Yes
(Sychronized Responses)

Yes

Yes
Yes
Yes
Yes (only WS option

exists)

No
Yes

Yes
Yes
Yes
No
Yes

Source
Maint. Method Frequency Due Date Completion Date
System
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
ERP
ERP
ERP
ERP
ERP
ERP
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
Ariba
ERP
ERP
ERP
ERP
ERP
ERP
Status
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Comments
FPC Consideration:
For customer admins and catalog admins you need to load the ImportCtrl = Both for parent
site
Back to homepage
SupplierOrganizations.csv (Import Supplier Organizations)
One record for every common supplier.

Column Header
SystemID
Name
PreferredLanguage.UniqueName
CorporateEmailAddress
AnnualRevenueMinimum.Amount
IsCustomer
StateOfIncorporaton
CorporatePhone
NumberOfEmployees
CorporateFax
CorporateAddress.UniqueName
AnnualRevenueMinimum.Currency.UniqueName
CorporateAddress.PostalAddress.City
IsSupplier
CorporateAddress.PostalAddress.State
AnnualRevenueMaximum.Amount
CorporateURL
HasTradingRelatonship
YearFounded
CorporateAddress.PostalAddress.Country.UniqueName
IsOrgApproved
OrganizatonType
HasSyncRelatonship
PreferredCurrency.UniqueName
CorporateAddress.PostalAddress.Lines
AnnualRevenueMaximum.Currency.UniqueName
CorporateAddress.PostalAddress.PostalCode
port Supplier Organizations)
n supplier.
Field Descripton
A unique identifier for the common supplier.
• If you are suite-integrated and the supplier was created in Ariba Upstream prior
to being interfaced into P2P, you will send the Ariba System ID in this field.
• If you are not suite-integrated or the supplier is “net new” in Ariba, you can store
the ERP Supplier Id or some other unique common supplier identifier in this field.
This field is case-sensitive.
Common Supplier Name - this is visible in the supplier admin UI

Does not drive any functionality in P2X/Invoice Pro/APC

When is this field required? Restrictons
Always <= 64 char.
Always <=255 char.

Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Customer mapping
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Back to homepage
SupplierIDs.csv (Import Supplier Organizations)

Between two and four records per common supplier, depending on fa
defined in "Domain" field description below.
Column Header
Parent.SystemID
Domain
Value
ier Organizations)
s per common supplier, depending on factors
cription below.
Field Descripton
References SystemID in SupplierOrganization.csv. This links the records in this file
to the supplier records defined in SupplierOrganizations.csv.
• buyersystemid - For P2X deployments, there should always be a record with

"buyersystemid" domain. For Invoice Pro deployments this domain is not required.
• networkid - Use the "networkid" domain for Ariba Network-enabled suppliers
only. The Ariba Network ID defined here is used for punchout catalogs and
Network catalog sync.
• sap - Always use the "sap" domain in SAP variant
• privateid - For Invoice Pro deployments, there should be a record with
"privateid" domain always. For P2P deployments this domain is not required
except when ICS is involved.
These values are not case-sensitive.
• When Domain is "buyersystemid", this field should contain the Parent.SystemID

value.
• When Domain is "networkid", this field should contain the supplier Ariba
Network ID.
• When Domain is "sap", this field should contain the SAP vendor id.
• When Domain is "privateid" this field should contain the SAP vendor id
Always See description
Always <=50 char.
Always <=128 char.

Customer mapping
Back to homepage
Supplier.csv (Import Suppliers)

One record for every supplier.
Column Header
LIFNR
NAME1
SupplierIDDomain
PurchasingUnits
t Suppliers)
y supplier.
Field Descripton
This is the unique identifier for the partitioned supplier (typically SAP vendor id), and together
with SupplierIDDomain, references a Domain/Value pair for a previously defined supplier in
SupplierIDs.csv. This supplier id is visible in multiple places in the user interface and is also
available on transactional exports.
Supplier name that is visible in supplier choosers in the UI.
Together with LIFNR, references a Domain/Value pair for a previously defined supplier in
SupplierIDs.csv. The default if left blank is "sap"; typically this is the Domain/Value pair used
for this purpose, since the Value associated with the "sap" Domain will be the SAP vendor ID.
References UniqueName of previously-defined purchasing unit(s) in PurchasingUnit.csv. This

field defines the purchasing unit(s) that a supplier belongs to. Can contain multiple, comma-
separated values.
Always <=128 char.
Only if linking this file to SupplierIDs using a

Domain/Value pair other than "sap" (not See description
common)
When using the PU functionality to filter See description

suppliers
Customer mapping
Back to homepage
SupplierLocation.csv (Import Suppliers)

Column Header
LIFNR
ORT01
REGIO
LAND1
STRAS
PSTLZ
VERKF
SMTP_ADDR
TELF1
TELFX
csv (Import Suppliers)
ery supplier.
Field Descripton
References LIFNR of supplier previously defined in Supplier.csv.
The city for the supplier. Visible in the Supplier Admin UI, on the printed PO, and when
viewing supplier location details elsewhere in the UI.
The state for the supplier. Visible in the Supplier Admin UI, on the printed PO, and when
The two-letter abbreviation of the country where the supplier is located. The Country field
determines the locale for this supplier location, which is used to determine the language for
communicating with the supplier location. Visible in the Supplier Admin UI, on the printed
PO, and when viewing supplier location details elsewhere in the UI.
The street address for the supplier. If there are multiple lines they should be separated by line
feed characters. Visible in the Supplier Admin UI, on the printed PO, and when viewing
supplier location details elsewhere in the UI.
The postal code for the supplier. Visible in the Supplier Admin UI, on the printed PO, and
when viewing supplier location details elsewhere in the UI.
The name of a contact person at the supplier location. Visible in the Supplier Admin UI and
The email address for the supplier. Visible in the Supplier Admin UI and when viewing
The phone number of the supplier. Visible in the Supplier Admin UI and when viewing
The fax number for the supplier. Visible in the Supplier Admin UI and when viewing supplier
location details elsewhere in the UI. It is also used to route quick-enablement fax orders.
Always <=50 char.
Always <=50 char.
Must be a valid two-letter

Always country code
Always <=1024 char.
Always <=50 char.
If you need this information displayed in the UI <=100 char.
Always when using quick enablement via email

for a supplier; otherwise only if you need this <=100 char.
information displayed in the UI
If you need this information displayed in the UI <=70 char.
• <=70 char.
• If using quick enablement via
Always when using quick enablement via fax fax, format must be as follows:
for a supplier; otherwise only if you need this +<Country
information displayed in the UI Code><Area_Code><Telephon
e_Number> (e.g.,
+49(711)8707286)
Customer mapping
Back to homepage
SupplierLocationSupplement.csv (Import Supplier Location Contacts)

Column Header
UniqueName
ContactID
Locale
PreferredOrderingMethod
PCardAcceptanceLevel
GhostPCardNumber
ChangeOrderRestrictons
AribaNetworkId
SplitOrderOnShipTo
PaymentModel
Supplement.csv (Import Supplier Location Contacts)
ery supplier.
Field Descripton
Locale that is used to determine the language in which the PO must be printed. If left blank,
the PO will be printed in the language associated with the supplier location country.
The preferred ordering method for sending orders to the supplier location. The valid values
are:
• URL: Use this for suppliers with which you have established a relationship on the Ariba
Network.
• Email: Use this only when using “quick enablement” functionality via email for a supplier.
• Fax: Use this only when using “quick enablement” functionality via fax for a supplier.
• Print: Use this for suppliers with which you have not established a relationship on the Ariba
Network and with which you are not using “quick enablement” functionality.
These values are case-sensitive.
The default if left blank is “Print”.
A number that indicates whether the supplier location accepts purchasing cards.
The value must be one of the following: 0 (The supplier location does not accept purchasing
cards), 1 (The supplier location accepts purchasing cards). The default if left blank is 0.
References cardNumber of previously defined p-card in Pcard.csv. This is the ghosted p-card
number for the supplier locaton.
A number that indicates whether the supplier location accepts change orders.
The value must be one of the following: 0 (The supplier accepts change orders), 1 (The
supplier does not accept change orders). The default if left blank is 0.
The AN ID for the supplier location. P2P uses this field as a unique ID to identify the supplier
on the Ariba Network and to route purchase orders to the suppliers. For manual suppliers,
leave this field blank.
A Boolean value that indicates whether the supplier location can handle line items
aggregated onto an order if those line items have different shipping addresses. The default is
false, which indicates the supplier can accept multiple shipping addresses on an order. If you
set this field to true, P2X creates separate orders for each shipping address.
Vestige of legacy functionality--no longer used. Specifies the payment model for the supplier
location. The payment model defines how payment transactions are handled. If you want to
send payment requests to Ariba SN, set this value to ANPay. If you want payment requests to
be processed in an external system, such as an ERP system, set this value to ExternalPay. If
you leave this value blank, the supplier location uses the payment model for the supplier. If a
payment model is not specified for the supplier, the supplier location uses the payment
model configured for your site. Valid values are: -1 = Default 0 = ExternalPay 1 = LocalPay 2 =
AribaNetworkPay
If there is a need to specify a locale (which

drives language used on printed PO) other
than your realm default or the locale Must be a valid Ariba locale ID
associated with the supplier location country,
and you want to do so via this file (instead of
manually, on a one-off basis, in the UI)
If you have any URL/Email/Fax suppliers;

otherwise, you can leave blank and let the See description
system default to "Print"
If you need to set the value to 1 (indicating the

supplier accepts p-cards) for some or all of
your suppliers, and want to do so via this file See description
(instead of manually, on a one-off basis, in the
UI). Leave blank if not using p-card
functionality.
If you are using ghosted p-cards and want to

map them to suppliers in this file (instead of
manually in the UI). Leave blank if not using p- See description
card functionality.
If you need to set the value to 1 (indicating the

supplier does not accept change orders) for
some or all of your suppliers, and want to do See description
so via this file (instead of manually, on a one-
off basis, in the UI)
If the PreferredOrderingMethod is set to <=255 char.

"URL"; otherwise, leave blank
If you need to set the value to TRUE for some
or all of your suppliers, and want to do so via Valid values are TRUE/FALSE
this file (instead of manually, on a one-off (case-insensitive)
basis, in the UI)
Never See description

Customer mapping
N/A
Back to homepage
PurchaseOrgSupplierCombo.csv (Import Purchase Organization to

Supplier Mapping)
One record for every valid purchase organization/supplier
combination.
Column Header
EKORG
LIFNR
XERSY
ZTERM
lierCombo.csv (Import Purchase Organization to
)
ery valid purchase organization/supplier
Field Descripton
References EKORG of purchase organization previously defined in PurchaseOrg.csv.
This field indicates whether this is an Evaluated Receipt Settlement (ERS) vendor. In P2X, if a
vendor is identified as ERS, the tax code field becomes visible and required on the requisition
(otherwise is remains hidden). The valid values are "X", which indicates this is an ERS vendor,
and null, which indicates this is not an ERS vendor. (Note that the tax code field is purely
informational within P2X out-of-the-box, but can be added to the purchase order export or
used to drive workflow/validations/etc.)
References UniqueName of previously defined payment term in PaymentTerms.csv. This

defines the payment term used for the supplier/purchase org combo. The payment term on a
PO can be set at the realm-level if there is a global default, or can be overriden by a payment
term set on a contract for contract-based release orders.
If you need to identify any vendors as ERS; See description

otherwise, you can leave blank for all records.
If there is a need to set default payment terms

at the supplier/purchase org level, versus at See description
the realm-level.
Customer mapping
Back to homepage
SharedUser.csv (Import Enterprise Users)

One record for every active user.
Column Header
UniqueName
PasswordAdapter
Name
EmailAddress
Organizaton.SystemID
DefaultCurrency.UniqueName
TimeZoneID
LocaleID.UniqueName
Phone
Fax
v (Import Enterprise Users)
every active user.
Field Descripton
A unique identifier for the user. This is the user id the user enters when logging on to the Ariba site
if using application authentication. If remote authentication (SSO) is turned on, this will typically be
a user's corporate network ID.
Note that user IDs are case-sensitive when logging in or exchanging SSO messages.
This field in conjunction with UniqueName is used to uniquely define a user in Ariba and defines
the user's authentication mechanism.
If remote authentication is out of scope, this value should be "PasswordAdapter1" for all users. If
remote authentication is in scope, use "PasswordAdapter1" for users who will authenticate via
remote authentication and "ThirdPartyUser" for users who need to authenticate via the application
(e.g., contractors, etc., who don't have access to your network).
The full name (first and last) of the user. This is the name that appears in various places in the user
interface in Ariba.
The user email address.This email address is used by Ariba for sending notification messages for
approvals, escalations etc.
Use "no-reply@ansmtp.ariba.com" or "nobody@ansmtp.ariba.com" on your test site if you have to

use a dummy email address to prevent users from getting Ariba email notifications.
Vestige of legacy functionality--should be set to "[Buyer]" (including the brackets) for all user
records.
Default currency for the user when creating requisitions and invoices in Ariba. If this field is left
blank it defaults to the default currency configured in your site.
The time zone of the user, designated with a standard abbreviation such as PST. If the field is left
blank, the system defaults to the Ariba server time zone which is PST. This field actually drives very
little functionality in the system, with one exception being certain exports that contain date fields
without corresponding timestamps rely on this field to determine whether the date should render
pre- or post-midnight.
When a user logs in, the preferred locale determines the language, currency formats, date formats,
etc. for the user interface.
Users can change their preferred locale by modifying their user preferences.
The user's phone number. Visible in User Admin UI and on Network purchase orders when the
ship-to address record does not have a phone number.
The user's fax number. Visible in User Admin UI and on Network purchase orders when the ship-to
address record does not have a fax number.
• <=255 char.
• No special characters except hyphen(-),
Always underscore (_), period (.) and @
• No spaces allowed
Always <= 50 char.
Has to be a valid email format

Always <= 255 char.
If you have a user population with different

default currencies and want to set defaults
via file load versus having the user set it Must be a valid currency code
him/herself
If your user population spans multiple time

zones and you are using exports from Ariba Must be a valid Ariba time zone ID
that contain date fields without
corresponding timestamps
Multi-language/country deployments where

you want this to be set for the user Must be a valid Ariba locale ID
automatically versus having the user set it
him/herself
If you need this information in the system <=70 char.

Customer mapping
Back to homepage
User.csv (Import Users)

Column Header
UniqueName
PasswordAdapter
VanillaDeliverTo
SAPCompanyCode
SAPCostCenter
SAPGeneralLedger
SAPPurchaseGroup
SAPPurchaseOrg
PurchasingUnit
SAPEmployeeSupplierID
ManagementLevel
port Users)
or every active user.
Field Descripton
References UniqueName of user previously defined in SharedUser.csv.
References PasswordAdapter of user previously defined in SharedUser.csv.
The user's preferred delivery information. Typically this is the user's full name. This is
available on the Ariba generated Purchase Order, essentially as an "attention line" in
the ship-to section.
P2X only supports one deliver to field--there is no separate mailstop field. You may
need to account for first name, last name and mailstop in the same deliver to field if
you have a need to include the mailstop as part of the delivery information.
References BUKRS of company code previously defined in CompanyCode.csv. Sets a

default company code for the user.
References KOSTL of cost center previously defined in CostCenter.csv. Sets a default cost
center for the user.
References SAKNR of general ledger previously defined in GeneralLedger.csv. Sets a

default general ledger for the user. The GL would typically be based on the commodity,
not the user, so is often not populated on this file.
References EKGRP of purchase group previously defined in PurchaseGroup.csv. Sets a

default purchase group for the user.
References EKORG of purchase org previously defined in PurchaseOrg.csv. Sets a default

purchase org for the user.
References UniqueName of purchasing unit previously defined in PurchasingUnit.csv.

Sets the user's home purchasing unit. In the SAP variant of P2X, the purchasing unit
can be mapped to the company code instead of the user.
Placeholder for SAP Employee Supplier ID. However, this field does not drive any
functionality and is not visible in the P2X UI.
Placeholder for user's management level. However, this field does not drive any
functionality and is not visible in the P2X UI.
Always <=100 char.
If you want to default the company code field on a req

or invoice based on user, and you want to load the
default via file instead of via self-service user profile See description
maintenance
If you want to default the cost center field on a req or

invoice based on user, and you want to load the default See description
via file instead of via self-service user profile
maintenance
If you want to default the general ledger field on a req or

invoice based on user (versus based on commodity or no See description
default at all), and you want to load the default via file
instead of via self-service user profile maintenance
If you want to default the purchase group field on a req

or invoice based on user (versus based on commodity or See description
no default at all), and you want to load the default via
file instead of via self-service user profile maintenance
If you want to default the purchase org field on a req or

invoice based on user, and you want to load the default See description
via file instead of via self-service user profile
maintenance
If you are using purchasing unit functionality and

mapping purchasing units to users instead of company See description
codes
Never <=100 char.
Never Integer
Customer mapping
N/A
N/A
Back to homepage
UserPCardMap.csv (Import Users)
If mapping users to personal purchasing cards, one record for

every active user that has a p-card. If not mapping users to
personal
Columnpurchasing
Header cards, you do not need any records in this
file----just load a file with the UniqueName and CardNumber
UniqueName
column headers.
CardNumber
ap.csv (Import Users)
sers to personal purchasing cards, one record for

user that has a p-card. If not mapping users to
chasing cards, you do not need
Field Descriptonany records in this
ad a fileReferences
with the UniqueName and CardNumber
UniqueName of user previously defined in SharedUser.csv.
References cardNumber of p-card previously defined in Pcard.csv. This is the user's
ders. personal purchasing card number.
Customer mapping
Back to homepage
User.csv (Import Responsible Users)
One record for every user to which you are assigning or

removing purchasing unit responsibility.
Column Header
UniqueName
PasswordAdapter
See ResponsibleUser.csv
port Responsible Users)
or every user to which you are assigning or

rchasing unit responsibility.
Field Descripton
References UniqueName of user previously defined in User.csv.
References PasswordAdapter of user previously defined in User.csv
Customer mapping
Back to homepage
ResponsibleUser.csv (Import Responsible Users)
One record for every user/group/purchasing unit assignment.

Column Header
UniqueName
PasswordAdapter
Group
PurchasingUnit
See User.csv
User.csv (Import Responsible Users)
or every user/group/purchasing unit assignment.

Field Descripton
References UniqueName of user referenced in User.csv. This is the ID of the user to
whom you are assigning purchasing unit responsibility.
References PasswordAdapter of user referenced in User.csv. This is the password

adapter of the user to whom you are assigning purchasing unit responsibility.
References UniqueName of an out-of-the-box group or of a custom group previously

defined in CustomGroup.csv. This is the group for which the user will have purchasing
unit responsibility.
References UniqueName of a purchasing unit previously defined in PurchasingUnit.csv.

This is the purchasing unit for which the user's group assignment will be effective.

Customer mapping
Back to homepage
SharedUserSupervisor.csv (Import Enterprise User/Supervisor

Relationships)
Column Header
UniqueName
PasswordAdapter
Supervisor.UniqueName
Supervisor.PasswordAdapter
ervisor.csv (Import Enterprise User/Supervisor
every active user.

Field Descripton
References UniqueName of user previously defined in SharedUser.csv. This is the ID of the user
to whom you are assigning a supervisor.
References PasswordAdapter of user previously defined in SharedUser.csv. This is the password
adapter of the user to whom you are assigning a supervisor.
References UniqueName of user previously defined in SharedUser.csv. This is the ID of the
supervisor.
adapter of the supervisor.
If there is an active supervisor defined for

the user. See description
If there is an active supervisor defined for See description

the user.
Customer mapping
Back to homepage
UserApprovalLimit.csv (Import User Approval Limits)

Column Header
UniqueName
PasswordAdapter
ApprovalLimit
ExpenseApprovalLimit
mit.csv (Import User Approval Limits)
every active user.
Field Descripton
to whom you are assigning a supervisor.
adapter of the user to whom you are assigning a supervisor.
The procurement approval limit for the user in the default currency for your site. This limit does
not apply to expense reports and travel authorizations.
The expense report or travel authorization approval limit for the user in the default currency for
your site.
If defining user approval limits for

requisitions and/or invoices. Integer
If defining an approval limit for travel or

expenses submitted in the Ariba Travel and Integer
Expense module.
Customer mapping
Back to homepage
PaymentTerms.csv (Import Payment Terms)
One record for every payment term code.

Column Header
UniqueName
Name
Descripton
ms.csv (Import Payment Terms)
or every payment term code.

Field Descripton
A unique identifier for the payment term. This value is referenced in the supplier
master data files and in transactional data exports, so is typically the code your ERP
uses (e.g., "N30" for Net 30 terms). This ID is displayed in the P2X UI under the
payment terms section of a PO/invoice/etc.
A descriptive name or title for the payment term (e.g., "Net 30"). This name is
displayed in the P2X UI when viewing the details of the payment terms on a
PO/invoice/etc. If your ERP does not contain three separate fields to store the ID, a
name, as well as a description, a common approach is to use the ID in this field as well.
A user-readable description of the payment terms (e.g., "Due in 30 days"). This

description is displayed in the P2X UI when viewing details of the payment terms on a
PO/invoice/etc and visible on the print version of PO's printed directly out of P2X.
Always <=50 char.
Always <=255 char.
Always <=255 char.

Customer mapping
Back to homepage
PaymentTermSteps.csv (Import Payment Terms)
One record for every payment term code. (The Ariba Network
does not allow for multiple installments per payment term--
whichColumnwasHeader
the original intent of this file--so there should only
be one record per term.)
Parent.UniqueName
StepJoinToken
InstallmentPercent
mSteps.csv (Import Payment Terms)
or every payment term code. (The Ariba Network

ow for multiple installments per payment term--
Field Descripton
he original intent of this file--so there should only
References UniqueName defined in PaymentTerms.csv. This field links the records in
d per term.)
this file to the records defined in PaymentTerms.csv.
This field serves as a temporary link between PaymentTermsStep.csv and
PaymentTermsStepDetails.csv during import. The value for StepJoinToken is not
retained. For the sake of simplicity, this can be the same value as the
Parent.UniqueName.
This field should always be set to "1", indicating 100%. (Since the Ariba Network does
not allow for multiple installments per payment term, each "step" in this file should be
set to 100%.)
Always <=100 char.

Customer mapping
Back to homepage
PaymentTermStepDetails.csv (Import Payment Terms)
One record for every discount level per payment term,

including the 0% discount level, if applicable. As examples, a
simple "Net 30" term would contain one record in this file,
Column Header
while a "2% 20, Net 30" term would contain two records--one
Parent.StepJoinToken
to represent the 2% discount if paid in 20 days, and a second
to represent the net due date of 30 days.
PayInDays
DiscountType
Discount
mStepDetails.csv (Import Payment Terms)
or every discount level per payment term,

e 0% discount level, if applicable. As examples, a
30" term would contain one record in this file,
Field Descripton
20, NetReferences
30" term would contain two records--one
StepJoinToken defined in PaymentTermSteps.csv. This field links the records
the 2%in discount if paid
this file to the records defined inin 20 days, and a second
PaymentTermSteps.csv.
the netpayment
duemust date ofin order
be made 30 todays.
A value that specifies the number of days. This is the number of days in which the
qualify for the discounted specified in the
DiscountType/Discount fields.
The type of discount for the payment term, which can be either "percent" or "amount"
(case-insensitive).
A number that specifies the payment discount for early payment. This value is
interpreted as either a percentage or amount, depending on the value in the
DiscountType field. If using percentage discount, do not convert to decimal (e.g., use
"2", not ".02", to represent 2%).
Always Integer
Always Decimal number

Customer mapping
Back to homepage
PurchasingUnit.csv (Import Purchasing Units)
One record for every purchasing unit.
Column Header
UniqueName
Name
Descripton
LogoFileName
Parent
Level
nit.csv (Import Purchasing Units)
or every purchasing unit.
Field Descripton
A unique identifier for the purchasing unit. This field is labeled as the "ID" when
viewing the details of a purchasing unit in the UI.
A user-visible name for the purchasing unit. This field is labeled as the "Purchasing
Unit" on requisition/PO/invoice/etc. screens and when viewing the details of a
purchasing unit in the UI. This field appears in the purchasing unit chooser as well (e.g.,
on non-PO invoice entry screen).
A user-visible description for the purchasing unit. This field is labeled as the
"Description" when viewing the details of a purchasing unit in the UI. This field appears
in the purchasing unit chooser as well (e.g., on non-PO invoice entry screen).
This field references the file name of the purchasing-unit-specific PO brand image. You
must specify the exact file name with the file extension in lower case (for example,
foo.gif or foo.jpeg), but without the location (path) details. This field is case sensitive,
so the letter case of the file name (minus the extension) should match what was loaded
in Ariba.
The unique internal identifier of another purchasing unit. You use this field to establish
hierarchical relationships between purchasing units.
Vestige of legacy functionality.
Always <= 50 char.
Always <=255 char.
Always <=510 char.
When using purchasing-unit-specific PO branding <=100 char.
When creating PU hierarchies and loading a child record See description

Never <=100 char.
Customer mapping
N/A
Back to homepage
AccountType.csv (Import Account Types)
One record for every account type.
Column Header
UniqueName
Name
Descripton
.csv (Import Account Types)
or every account type.
Field Descripton
A unique identifier for the accounting type. This field is not visible in the UI, but is
referenced in ERPCommodityCodeMap.csv. When mapping multiple account types to a
given commodity code, the default account type is set either using the "Preferred" flag
in ERPCommodityCodeMap.csv, or using the alphabetical order of the account type
UniqueNames if the Preferred flag is set to the same value for all records.
A user-visible name for the accounting type. This value is visible in account type drop-
down and when viewing account type details in the UI.
A user-visible description for the accounting type. This value is visible when viewing
account type details in the UI.
Always <= 50 char.
Always <=255 char.
If you want to see a description for the account type <=255 char.
when viewing the account type details
Customer mapping
Back to homepage
ItemCategory.csv (Import Item Categories)
One record for every item category.
Column Header
UniqueName
Name
ExpectedValue
OverallLimit
y.csv (Import Item Categories)
or every item category.
Field Descripton
A unique identifier for the item category. This value is visible when viewing item
category details in the UI.
A user-visible name for the item category. This value is visible in the item category
drop-down and when viewing item category details in the UI.
A Boolean value that indicates whether the "Expected Value" field is displayed for
optional entry on a requisition line (setting this value to TRUE makes the field visible;
setting this value to FALSE or null keeps the field hidden). The "Expected Value" field on
a req/PO is currently purely informational within P2X--it is not available for export or in
reports, and cannot be used to drive any workflow/validations/etc.
A Boolean value that indicates whether the "Overall Limit" field is displayed for
optional entry on a requisition line (setting this value to TRUE makes the field visible;
setting this value to FALSE or null keeps the field hidden). The "Overall Limit" field on a
req/PO is currently purely informational within P2X--it is not available for export or in
reports, and cannot be used to drive any workflow/validations/etc.
Always <=50 char.
Always <=255 char.
If you want the "Expected Value" field to be visible on Valid values are TRUE/FALSE (case-
the req/PO for an item category; otherwise leaving the insensitive)
field null or sending FALSE will have the same effect
If you want the "Overall Limit" field to be visible on the Valid values are TRUE/FALSE (case-
req/PO for an item category; otherwise leaving the field insensitive)
null or sending FALSE will have the sam effect
Customer mapping
Back to homepage
AccountCategory.csv (Import Account Categories)
One record for every account assignment category.
Column Header
KNTTP
KNTTX
FAUS1
gory.csv (Import Account Categories)
or every account assignment category.
Field Descripton
A unique identifier for the account category. This value is visible in the account
assignment drop-down and when viewing account assignment details in the UI.
A user-visible name for the account category. This value is visible in the account
category drop-down and when viewing account category details in the UI.
The field status group string. Each string consists of a series of four characters or
spaces. Each of the four characters corresponds to the four settings that SAP allows for
accounting fields for a given account category. The position of each character within
the string determines the accounting field to which it applies. Refer to the
"Understanding Field Status Group Strings" section in the "Procurement Solutions
Integration Guide for SAP" PDF for more information.
Always <=50 char.
Always <=255 char.
Always <=70 char.

Customer mapping
Back to homepage
CompanyCode.csv (Import Company Codes)
One record for every company code.
Column Header
BUKRS
BUTXT
FSTVA
PurchasingUnit
de.csv (Import Company Codes)
or every company code.
Field Descripton
A unique identifier for the company code. This value is visible in the company code
chooser and when viewing company code details in the UI.
The name of the company. This value is visible in the company code chooser and when
viewing company code details in the UI.
The field status variant. This value is visible when viewing company code details in the
UI. It is also referenced in AccCategoryFieldStatusCombo.csv, where valid combinations
of account categories, company code field status variants, and general ledger field
status groups are defined for purposes of filtering the general ledger chooser. This
replicates cross-validation functionality in SAP, but if you don't require it, you can hard-
code this field and populate AccCategoryFieldStatusCombo.csv accordingly.
In the SAP variant of P2X, the purchasing unit can be mapped to the company code
instead of the user, which would set the purchasing unit of the document to the
purchasing unit defined for the company code (allowing for changing the purchasing
unit by changing the company code). Note that this field does not filter the company
code chooser based on the user's purchasing unit, unlike purchasing unit functionality
related to accounting elements in other variants.
Always <=50 char.
Always <=255 char.
Always <=4 char.
If you are using purchasing unit functionality and

mapping purchasing units to company codes instead of See description
or in addition to users
Customer mapping
Back to homepage
PurchaseOrg.csv (Import Purchase Organizations)
One record for every purchase organization.
Column Header
BUKRS
EKORG
EKOTX
PurchasingUnit
.csv (Import Purchase Organizations)
or every purchase organization.
Field Descripton
References BUKRS of a company code previously defined in CompanyCode.csv. This
field is used to filter the purchase org choices based on the company code selected on
the requisition. If this field is left blank, the purchase org is valid across all company
codes.
A unique identifier for the purchasing organization. This value is visible in the purchase
org chooser and when viewing purchase org details in the UI.
The name of the purchasing organization. This value is visible in the purchase org
chooser and when viewing purchase org details in the UI.
This field does not drive any functionality as purchase org is not filtered by purchasing
unit.
If mapping a purchase org to a company code. If the

purchase org should be valid across all company codes, See description
leave this field blank.
Always <=50 char.
Always <=255 char.

Customer mapping
N/A
Back to homepage
CostCenter.csv (Import Cost Centers)
One record for every cost center, as defined by a unique

BUKRS/KOSTL combination.
Column Header
BUKRS
KOSTL
KTEXT
PurchasingUnit
sv (Import Cost Centers)
or every cost center, as defined by a unique

L combination.
Field Descripton
field is used to filter the cost center chooser based on the company code selected on
the requisition. If this field is left blank, the cost center is not valid for any company
codes.
A unique identifier for the cost center. This value is visible in the cost center chooser
and when viewing cost center details in the UI.
The name of the cost center. This value is visible in the cost center chooser and when
viewing cost center details in the UI.
This field does not drive any functionality as cost center is not filtered by purchasing
unit.
Always <=50 char.
Always <=255 char.

Customer mapping
N/A
Back to homepage
PurchaseGroup.csv (Import Purchase Groups)
One record for every purchase group.
Column Header
EKGRP
EKNAM
PurchasingUnit
up.csv (Import Purchase Groups)
or every purchase group.
Field Descripton
A unique identifier for the purchasing group. This value is visible in the purchasing
group chooser and when viewing purchasing group details in the UI.
The name of the purchasing group. This value is visible in the purchasing group chooser
and when viewing purchasing group details in the UI.
This field does not drive any functionality as purchase group is not filtered by
purchasing unit.
Always <=50 char.
Always <=255 char.

Customer mapping
N/A
Back to homepage
InternalOrder.csv (Import Internal Orders)
One record for every internal order.
Column Header
AUFNR
KTEXT
r.csv (Import Internal Orders)
or every internal order.
Field Descripton
A unique identifier for the internal order. This value is visible in the internal order
chooser and when viewing internal order details in the UI.
The name of the internal order. This value is visible in the internal order chooser and
when viewing internal order details in the UI.
Always <=50 char.
Always <=255 char.

Customer mapping
Back to homepage
CompanyCodeIOCombo.csv (Import Company Code Internal Order

Mapping)
One record for every company code/internal order combination.
Column Header
BUKRS
AUFNR
OCombo.csv (Import Company Code Internal Order
every company code/internal order combination.

Field Descripton
References BUKRS of a company code previously defined in CompanyCode.csv.
References AUFNR of an internal order previously defined in InternalOrder.csv.
Customer mapping
Back to homepage
PlantPurchaseOrgCombo.csv (Import Plant to Purchase Organization

Mapping)
One record for every plant/purchase org combination.
Column Header
WERKS
EKORG
OrgCombo.csv (Import Plant to Purchase Organization
every plant/purchase org combination.

Field Descripton
References WERKS of a plant previously defined in Plant.csv.
References EKORG of a purchase org previously defined in PurchaseOrg.csv.
Customer mapping
Back to homepage
GeneralLedger.csv (Import General Ledgers)
One record for every general ledger, as defined by a unique

BUKRS/SAKNR combination.
Column Header
BUKRS
SAKNR
TXT50
FSTAG
er.csv (Import General Ledgers)
or every general ledger, as defined by a unique

NR combination.
Field Descripton
field is used to filter the general ledger chooser based on the company code selected
on the requisition. If this field is left blank, the general ledger is not valid for any
company codes.
A unique identifier for the general ledger. This value is visible in the general ledger
chooser and when viewing general ledger details in the UI.
A description of the general ledger. This value is visible in the general ledger chooser
and when viewing general ledger details in the UI.
The field status group. This field is referenced in AccCategoryFieldStatusCombo.csv,

where valid combinations of account categories, company code field status variants,
and general ledger field status groups are defined for purposes of filtering the general
ledger chooser (in addition to the company code-based filtering).This replicates cross-
validation functionality in SAP, but if you don't require it, you can hard-code this field
and populate AccCategoryFieldStatusCombo.csv accordingly.
Always <=50 char.
Always <=255 char.
Always <=4 char.

Customer mapping
Back to homepage
CompanyCodeWBSCombo.csv (Import Company Code WBS Mapping)

One record for every company code/WBS Element combination.
Column Header
PBUKR
POSID
WBSCombo.csv (Import Company Code WBS Mapping)
every company code/WBS Element combination.
Field Descripton
References BUKRS of a company code previously defined in CompanyCode.csv.
References POSID of a WBS element previously defined in WBSElement.csv.
Customer mapping
Back to homepage
WBSElement.csv (Import WBS Elements)
One record for every WBS element.
Column Header
POSID
POST1
PSPHI
t.csv (Import WBS Elements)
or every WBS element.
Field Descripton
A unique identifier for the WBS element. This value is visible in the WBS element
chooser and when viewing WBS element details in the UI.
A description of the WBS element. This value is visible in the WBS element chooser and
when viewing WBS element details in the UI.
The project number associated with the WBS element. The value is visible as the
"Project Number" when viewing WBS element details.
Always <=50 char.
Always <=255 char.
If you want to see a project number when viewing the

<=255 char.
WBS element details
Customer mapping
Back to homepage
Asset.csv (Import Assets)

One record for every asset, as defined by a unique
BUKRS/ANLN1/ANLN2 combination.
Column Header
BUKRS
ANLN1
ANLN2
TXT50
TXA50
mport Assets)
or every asset, as defined by a unique
N1/ANLN2 combination.
Field Descripton

field is used to filter the asset chooser based on the company code selected on the
requisition. If this field is left blank, the asset is not valid for any company codes.
The asset number. This value is visible in the asset chooser and when viewing asset
details in the UI.
The asset sub-number. This value is visible in the asset chooser and when viewing asset
details in the UI.
This field and the TXA50 are concatenated (with a space in between) to form the
description of the asset, which is visible in the asset chooser and when viewing asset
details in the UI.
This field and the TXT50 are concatenated (with a space in between) to form the
description of the asset, which is visible in the asset chooser and when viewing asset
details in the UI.
Always <=50 char.
Always <=50 char.
If the asset contains a sub-number (should be the case if <=4 char.

sourced from SAP)
Combined with TXA50 should be <= 127

Always char.
If sourcing from SAP this should be populated with the

corresponding field in the asset table; if populating Combined with TXTA50 should be <= 127
manually or sourcing from another ERP, you can leave char.
blank and put the entirety of the asset description in
TXT50
Customer mapping
Back to homepage
Network.csv (Import Networks)
One record for every Network defined per company code
Column Header
NTWC
NTWK
NTWD
(Import Networks)
or every Network defined per company code
Field Descripton

field is used to filter the network chooser based on the company code selected on the
requisition.
The network number. This value is visible in the network chooser and when viewing
network details in the UI.
The network description. This value is visible in the network chooser and when viewing
network details in the UI.
Always <=50 char.
Always <=50 char.
Always <=255 char.

Customer mapping
Back to homepage
ActivityNumber.csv (Import Activity Numbers)

Activity Number is an organizational unit within a controlling area tha
One record for every Activity Number, as defined by a unique compan
Column Header
ACTC
ACTN
ACTY
ACTD
ber.csv (Import Activity Numbers)
ber is an organizational unit within a controlling area that represents a clearl
or every Activity Number, as defined by a unique company code-NetworkID c
Field Descripton

field is used to filter the network activity chooser based on the company code selected
on the requisition.
The associated network-id.
The activity number id. This value is visible in the activity number chooser and when
viewing activity number details in the UI.
The activity number description. This value is visible in the network chooser and when
viewing network details in the UI.
ling area that represents a clearly defined location where costs occur.
ique company code-NetworkID combination.
Always <=50 char.
Always <=50 char.
If the asset contains a sub-number (should be the case if <=50 char.

sourced from SAP)
Always <=255 char.

n where costs occur.
Customer mapping
Back to homepage
AccCategoryFieldStatusCombo.csv (Import Account Category

Field Status Combinations)
One record for every account category/field status group/field
status variant combination.
Column Header
KNTTP
FSTAG
BUKRS
FieldStatusCombo.csv (Import Account Category
Combinations)
or every account category/field status group/field
t combination.
Field Descripton
References KNTTP of an account category previously defined in AccountCategory.csv.
This field determines the group of general ledger codes that are valid for the given
account category/company code field status variant combination. It should match an
FSTAG value for one or more general ledger codes previously defined in
GeneralLedger.csv.
This field should match an FSTVA value (not a BUKRS value, despite the field name in
this file) for one or more company codes previously defined in CompanyCode.csv.
Always <=4 char.
Always <=4 char.

Customer mapping
Back to homepage
CurrencyConversionRate.csv (Import Currency Conversion

Rates)
One record for every effective-dated currency conversion rate.
Column Header
FCURR
TCURR
EXTRATE
EXTDATE
versionRate.csv (Import Currency Conversion
or every effective-dated currency conversion rate.
Field Descripton
The currency code of the currency from which the monetary value is converted.
The currency code of the currency to which the monetary value is converted.
The currency conversion rate, which is a decimal value.
The date the conversion rate goes into effect.
Always Must be valid currency code
Always YYYYMMDD format
Customer mapping
Back to homepage
ERPCommodityCode.csv (Import ERP Commodity Codes)
One record for every ERP commodity code.
Column Header
MATKL
WGBEZ
dityCode.csv (Import ERP Commodity Codes)
or every ERP commodity code.
Field Descripton
A unique identifier for the ERP commodity code. This value is visible in the material
group chooser and when viewing material group details in the UI.
A description of the ERP commodity code. This value is visible in the material group
chooser and when viewing material group details in the UI.
Always <=50 char.
Always <=255 char.

Customer mapping
Back to homepage
UnitsOfMeasureMap.csv (Import Unit of Measure Mapping)
One record for every unit of measure mapping. An Ariba UOM

can be mapped to multiple external keys, but one external key
cannot be mapped to multiple Ariba UOMs (1:n).
Column Header
Key
Value
Preferred
Comment
sureMap.csv (Import Unit of Measure Mapping)
or every unit of measure mapping. An Ariba UOM

ed to multiple external keys, but one external key
apped to multiple Ariba Field
UOMs (1:n).
Descripton
The external ERP system-specific unit of measure name.
The UniqueName of the Ariba UOM being mapped.
A Boolean that indicates which mapping to use (i.e., which external value to use in
transactional data exports out of Ariba) when there are multiple external keys mapped
to one Ariba UOM. The default if left blank is FALSE.
An optional comment to describe the mapping. These comments are only visible within
the file and in the Unit of Measure Map UI.
Always <=64 char.
Always <=64 char.
If you have multiple mappings for a given Ariba UOM
and want to identify one as the "preferred" value for use Valid values are TRUE/FALSE (case-
insensitive)
in transactional data exports
If you want to load a comment for the mapping record <=64 char.
Customer mapping
Back to homepage
UnitsOfMeasure.csv (Import Units of Measure)
One record for every unit of measure.
Column Header
UniqueName
Name
Descripton
AllowNonWhole
Category
sure.csv (Import Units of Measure)
or every unit of measure.
Field Descripton
A unique identifier for the unit of measure. This value is visible in the unit of measure
chooser and when viewing UOM details in the UI.
A user-visible name for the unit of measure. This value is visible in the unit of measure
chooser and when viewing UOM details in the UI.
A user-visible description for the unit of measure. This description is displayed in the
P2X UI when viewing details of the unit of measure in the UI.
A Boolean value that indicates whether the unit of measure supports non-whole
quantities. For example, a centimeter supports non-whole quantities, while a micron or
an atom does not. The default if left null is FALSE.
Indicates whether the unit of measure is time related. A value of 1 means the unit of
measure is time related. A value of 0 means the unit of measure is not time related.
The default if left null is 0. Certain screens (e.g., timesheet entry) only allow for
selection of time-related units of measure.
Always <=50 char.
Always <=255 char.
If you care to see a description for the unit of measure

<=255 char.
when viewing the account type details
If you are adding a unit of measure that allows for non- Valid values are TRUE/FALSE (case-
whole quantities; otherwise, you can leave null and insensitive)
allow the system to default to FALSE
If you are adding a time-related unit of measure;

otherwise, you can leave null and allow the system to Integer
default to 0
Customer mapping
Back to homepage
POConditions.csv (Import Purchase Order Conditions)

One record for each set of terms and conditions text. If segregating terms and
conditions text by purchasing unit, this file should contain one record per
purchasing unit; otherwise, this file should only contain one record.
Column Header
Title
Text
InvoicingText
LegalText
ProcurementUnit
TAndCVersion
s.csv (Import Purchase Order Conditions)
each set of terms and conditions text. If segregating terms and
by purchasing unit, this file should contain one record per
otherwise, this file should only contain one record.
Field Descripton
A user-visible title for the terms and conditions text. This value is visible as a clickable
link (to view the full terms and condtions text) on the purchase order UI.
The purchase terms and conditions text. This text appears on the purchase order print
view under the heading "Terms And Conditions of Purchase" and is visible on Ariba
Network purchase orders as well. Use line feed characters to add spaces between
paragraphs/sections.
You can opt to load the full text of your terms and conditions or simply a URL pointing
suppliers to a website that contains the full text.
The invoicing terms and conditions text. This text appears on the purchase order print
view under the heading "Invoicing Terms and Conditions of Purchase" and is visible on
Ariba Network purchase orders as well. (If this field is left blank, the "Invoicing Terms
and Conditions of Purchase" heading does not appear at all on the purchase order.)
The legal terms and conditions text. This text appears on the purchase order print view
under the heading "Legal Terms and Conditions of Purchase" and is visible on Ariba
Network purchase orders as well. (If this field is left blank, the "Legal Terms and
Conditions of Purchase" heading does not appear at all on the purchase order.)

This defines the purchasing unit the Terms and Conditions are valid for--if left blank,
the T&C's apply to all purchasing units.
The version number of the terms and conditions text. Leave this column blank. The
system will set it to the correct value.
Always <=100 char.
Always
If you want to include text as the "Invoicing Terms and

Conditions of Purchase" on a purchase order.
If you want to include text as the "Legal Terms and

Conditions of Purchase" on a purchase order.
If you are using purchasing unit functionality and See description

segregating Terms and Conditions by purchasing unit
Never Integer
Customer mapping
N/A
Back to homepage
Plant.csv (Import Plants)

One record for each bill-to and ship-to address. Note that every addre
record must be associated with one and only one company code. If yo
have a requirement to have one address mapped to multiple company
codes, you need one record for every address/company code
combination, and each record should have a unique WERKS value. On
Column Header
common approach in this scenario is to use a concatenation of compa
code and address id as the WERKS.
WERKS
BUKRS
NAME1
STRAS
ORT01
REGIO
LAND1
PSTLZ
TEL_NUMBER
FAX_NUMBER
Line2
Line3
PFACH
lants)
h bill-to and ship-to address. Note that every address
ociated with one and only one company code. If you
t to have one address mapped to multiple company
ne record for every address/company code
each record should have a unique Field DescriptonWERKS value. One
in this scenario is to use a concatenation of company
d as the WERKS.
A unique identifier for the plant (address) record. This value is visible in address choosers and
when viewing address details in the UI.
The Ariba Network expects address IDs to be at least two characters long so this should be a
consideration for addresses that will be used on orders routed to the Ariba Network. Also,
electronically-integrated Network suppliers often key off of the address id, so you should
coordinate with this subset of your suppliers to make sure they can handle your address ids,
especially if they are particularly long or contain non-alpha-numeric characers (e.g., dash or
tilde).
References BUKRS of a company code previously defined in CompanyCode.csv. This field is used
to filter the ship-to and bill-to address choosers based on the company code selected on the
requisition. If this field is left blank, the plant is not valid for any company codes.
A name or description of the address. This value is visible in address choosers and when viewing
address details in the UI.
This value is visible as part of the address on Ariba Network purchase orders. It is visible on
purchase orders printed out of P2X only when the "Company Name" realm-level parameter is
null.
The street address of the plant. If there are multiple lines they should be merged into this field
and separated by line feed characters. Note that while there are separate fields available for
"Line 2" and "Line 3" in this file, the values in those fields are only visible on Ariba Network
purchase orders and not on purchase orders printed out of P2X. As such, the recommendation is
to include all address lines in this field.
The city where the address is located.
The state/province where the address is located.
The two-letter abbreviation of the country where the address is located.
The postal code of the address.
The telephone number of the address.
The fax number of the address.
This field can store a second line for the street address, but is not visible on purchase orders
printed out of P2X, only on Ariba Network purchase orders. As such the recommendation is to
include all address lines in the STRAS field and leave this field blank, unless you will not be
printing orders out of P2X.
This field can store a third line for the street address, but is not visible on purchase orders printed
out of P2X, only on Ariba Network purchase orders. As such the recommendation is to include all
address lines in the STRAS field and leave this field blank, unless you will not be printing orders
out of P2X.
A placeholder for the post office box of the plant. However, this field is not visible in the UI or on
purchase orders.
Always <=50 char.
Always <=128 char.
Always <=1024 char.
Always <=50 char.

If there is a state/province for the address <=50 char.
Always Must be a valid two-letter country code
If there is a postal code for the address <=50 char.
If there is a phone number for the address <=70 char.
If there is a fax number for the address <=70 char.
If you have multi-line addresses, will not be printing

purchase orders directly out of P2X, and cannot merge <=100 char.
address lines into one field (STRAS)
If if you have multi-line addresses, will not be printing

purchase orders directly out of P2X, and cannot merge <=100 char.
address lines into one field (STRAS)
Never <=50 char.

Customer mapping
N/A
Back to homepage
UserParentGroup.csv (Import User Group Mapping)
One record for every group to which you are assigning users to (i.e.,
one record for every unique group referenced in
GroupSharedUserMap.csv).
Column Header
UniqueName
See GroupSharedUserMap.csv
csv (Import User Group Mapping)
ry group to which you are assigning users to (i.e.,

ry unique group referenced in
Map.csv). Field Descripton
defined in CustomGroup.csv.

Customer mapping
Back to homepage
GroupSharedUserMap.csv (Import User Group Mapping)
One record for every user-to-group assignment. If a user needs to be

assigned to multiple groups, there will be multiple records for that
user in this file.
Column Header
Parent.UniqueName
UniqueName
PasswordAdapter
See UserParentGroup.csv
Map.csv (Import User Group Mapping)
ry user-to-group assignment. If a user needs to be

le groups, there will be multiple records for that
Field Descripton
References UniqueName of a group referenced in UserParentGroup.csv. This is the
group to which you are assigning the user.
References UniqueName of user previously defined in SharedUser.csv. This is the ID of
the user you are assigning to the group.
References PasswordAdapter of user previously defined in SharedUser.csv. This is the
password adapter of the user you are assigning to the group.

Customer mapping
Back to homepage
GroupParentGroup.csv (Import Group to Child Group Mapping)
One record for every group to which you are assigning child groups.
Column Header
UniqueName
See GroupChildGroupMap.csv
p.csv (Import Group to Child Group Mapping)
ry group to which you are assigning child groups.
Field Descripton
defined in CustomGroup.csv.

Customer mapping
Back to homepage
GroupChildGroupMap.csv (Import Group to Child Group Mapping)
One record for every child group-to-parent group assignment.
Column Header
Parent.UniqueName
UniqueName
See GroupParentGroup.csv
Map.csv (Import Group to Child Group Mapping)
ry child group-to-parent group assignment.
Field Descripton
References UniqueName of a group referenced in GroupParentGroup.csv. This is the
parent group to which you are assigning the child group (i.e., the group whose
permissions will be inherited by the child group).
References UniqueName of group previously defined in CustomGroup.csv. This is the
child group that you are assigning to the parent (i.e., the group that will be inherting
the permissions associated with the parent group).

Customer mapping
Back to homepage
CustomGroup.csv (Import Custom Groups)

One record for every custom group.
Column Header
UniqueName
Name
User Can Request Responsibility

(Import Custom Groups)
ry custom group.
Field Descripton
A unique identifier for the custom group. This value is visible in group choosers and
when viewing group details in the UI.
A name for the custom group. This value is visible in the UI wherever groups are
referenced.
This is a boolean field which determines whether users can request purchasing unit
responsibility from their User Profile for the group. This field is applicable only when
the parameter Org Visibility is turned on. If left blank, users will not be able to request
purchasing unit responsibility for the group.
Always <=255 char.
Always <=255 char.
If you are using purchasing unit functionality with Org Valid values are TRUE/FALSE (case-
Visibility turned on, and you want users to be able to insensitive)
request purchasing unit responsibility
Customer mapping
Back to homepage
SharedUserSingleBillingAddressMap.csv (Import User/Billing Address

Relationships)
One record for every active user to whom you are assigning a default
billing address.
Column Header
UniqueName
PasswordAdapter
SAPBillingAddress
gleBillingAddressMap.csv (Import User/Billing Address
every active user to whom you are assigning a default

Field Descripton
to whom you are assigning a default billing address.
adapter of the user to whom you are assigning a default billing address.
References WERKS of plant previously defined in Plant.csv. This is the ID of the plant you are
assigning as a default billing address to the user.

Customer mapping
Back to homepage
SharedUserSingleShipToAddressMap.csv (Import User/Ship To

Address Relationships)
One record for every active user to whom you are assigning a default
shipping address.
Column Header
UniqueName
PasswordAdapter
SAPPlant
gleShipToAddressMap.csv (Import User/Ship To
nships)
every active user to whom you are assigning a default
ss.
Field Descripton
to whom you are assigning a default shipping address.
adapter of the user to whom you are assigning a default shipping address.
assigning as a default shipping address to the user.

Customer mapping
Back to homepage
CommodityCode.csv (Import Commodity Codes/Import Commodity

Code Hiearchy)
One record for every system commodity code.
Column Header
UniqueName
Domain
Name
Enabled
ParentUniqueName
sv (Import Commodity Codes/Import Commodity
ry system commodity code.
Field Descripton
A unique identifier for the commodity code. This value is visible in commodity code
choosers and when viewing commodity code details in the UI.
The domain of the commodity code. In most cases this should be "unspsc", but can be
"ascc" if you are defining services commodity codes for use with the Services
Procurement module, or a custom-defined value if you are replacing the out-of-the-box
UNSPSC codes with a custom taxonomy (e.g., "custom").
A name for the commodity code. This value is visible in the UI wherever commodity
codes are found.
A Boolean value that enables or disables the commodity code. You can use this field to
hide or show branches or individual codes. The default if left null is TRUE.
References UniqueName of another active system commodity code. This is the

commodity code's parent in the commodity code hierarchy.
Always <=100 char.
Always <=50 char.
Always <=255 char.
Valid values are TRUE/FALSE (case-

If you are disabling one or more commodity codes insensitive)

Customer mapping
Back to homepage
ClassificationCodeMap.csv (Import Classification Code Relationships)
One record for every commodity-to-commodity mapping. You can

use hierarchical wild-carding in this file, meaning you can define
mappings for parent system commodity codes, and those mappings
will takeColumn
effect when a child commodity code is referenced on a
Header
catalog.
DomainFrom
ValueFrom
DomainTo
ValueTo
Map.csv (Import Classification Code Relationships)
ry commodity-to-commodity mapping. You can

ld-carding in this file, meaning you can define
nt system commodity codes, and those mappings
en a child commodity code is referenced on a
Field Descripton
References Domain of a commodity code previously defined in CommodityCode.csv.
This is the domain of the commodity code you are mapping to a UNSPSC code (e.g.,
"ascc" or "custom").
References UniqueName of a commodity code previously defined in
CommodityCode.csv. This is the ID of the commodity code you are mapping to a
UNSPSC code.
References Domain of a previously defined system commodity code. This is typically

"unspsc" as you will be mapping from a custom or services taxonomy to UNSPSC.

CommodityCode.csv. This is the ID of the UNSPSC code you are mapping the custom or
services code to.

Customer mapping
Back to homepage
ERPCommodityCodeMap.csv (Import ERP Commodity to Commodity

Mapping)
One record for every commodity mapping, as defined by a unique
Company Code/System Commodity Code/Account Type/ERP
Commodity Code combination. You can use hierarchical wild-carding
in this file, meaning you can define mappings for parent system
commodity Columncodes,
Header and those mappings will take effect when a child
commodity code is selected on the requisition or invoice.
CompanyCode
CommonId
CommonIdDomain
AccountType
MaterialGroup
MaxAmt
MinAmt
CurrForMinAndMaxAmt
Preferred
AccountCategory
BillTo
GeneralLedger
InternalOrder
ItemCategory
SAPPurchaseGroup
ShipTo
WBSElement
Asset
SubAsset
DeliverTo
deMap.csv (Import ERP Commodity to Commodity
ry commodity mapping, as defined by a unique

stem Commodity Code/Account Type/ERP
combination. You can use hierarchical wild-carding
g you can define mappings for parent system
and those mappings willField take effect when a child
Descripton
s selected on the requisition or invoice.

References BUKRS of a company code previously defined in CompanyCode.csv. This is
the company code for which the commodity mapping is valid.
Note that leaving this field blank will not make it so that the mapping is picked up for
all company codes--it will make it so that the mapping is only picked up when the
company code is null, which should only be the case in APC scenarios. Thus, this field
should always be populated in P2X/Invoice Pro scenarios.

CommodityCode.csv. This is the ID of the system commodity code you are mapping.

This is the domain of the system commodity code you are mapping.
References UniqueName of an account type previously defined in AccountType.csv.

This is the account type that, in conjunction with the company and commodity, will
determine the default accounting/shipping/billing information.
References MATKL of a material group code (i.e., ERP commodity code) previously
defined in ERPCommodityCode.csv. This is the material group that will be set when the
given company/commodity/account type is selected.
Indicates the upper limit value for a line item or unit price amount range (the lower
limit value is represented by MinAmt). Whenever the line item or unit price amount
falls within the specified range, the account type from the corresponding row in
ERPCommodityCodeMap.csv is selected. You can populate MinAmt and leave this field
blank to represent an open-ended range.
Indicates the lower limit value for a line item amount or unit price range (the upper
limit value is represented by MaxAmt). Whenever the line item or unit price amount
falls within the specified range, the account type from the corresponding row in
ERPCommodityCodeMap.csv is selected.
The currency for the amount in the MinAmt/MaxAmt columns.
Whether this entry is preferred if there are multiple entries available

References KNTTP of an account category previously defined in AccountCategory.csv.
This is the account category you want to default for the given
company/commodity/account type.
This is the only mechanism available for defaulting the account category on a
requisition, so this field can be populated with the same value on all records to serve as
a "realm level" default if there is no need to have different defaults based on
References WERKS of a plant previously defined in Plant.csv. This is the bill-to address
you want to default for the given company/commodity/account type.
This field is often populated to serve as a company-level default for the bill-to address,
by populating the same value on all records for a given company code.
References SAKNR of a general ledger previously defined in GeneralLedger.csv. This is

the general ledger you want to default for the given company/commodity/account
type.
References AUFNR of an internal order previously defined in InternalOrder.csv. This is
the internal order you want to default for the given company/commodity/account
type.
References UniqueName of an item category previously defined in ItemCategory.csv.

This is the item category you want to default for the given
This is the only mechanism available for defaulting the item category on a requisition,
so this field can be populated with the same value on all records to serve as a "realm
level" default if there is no need to have different defaults based on
References EKGRP of a purchase group previously defined in PurchaseGroup.csv. This is

the purchase group you want to default for the given company/commodity/account
type.
Purchase group is a required field on the requisition in P2X, but drives no downstream
functionality within P2X out-of-the-box, so a common approach is to load one
"dummy" purchase group in PurchaseGroup.csv and to apply a "realm-level" default by
referencing the dummy value on all records in this file.
References WERKS of a plant previously defined in Plant.csv. This is the ship-to address
you want to default for the given company/commodity/account type.
References POSID of a WBS element previously defined in WBSElement.csv. This is the

WBS element you want to default for the given company/commodity/account type.
References ANLN1 of an asset previously defined in Asset.csv. This is the asset you want
to default for the given company/commodity/account type.
References ANLN2 of an asset previously defined in Asset.csv. This is the asset you want
to default for the given company/commodity/account type.
The deliver-to value you want to default for the given company/commodity/account
type.
The deliver-to value is usually defaulted from the user profile and thus rarely populated
in this file.
• Always for P2X/Invoice Pro

• For APC this should only be populated if there will be a See description
company code on the shopping cart (i.e., if you are
loading users with default company codes)
If you want to use dollar amount ranges to set the Decimal number
account type and corresponding defaults
If you want to use dollar amount ranges to set the

account type and corresponding defaults Decimal number
If you want to use dollar amount ranges to set the Must be valid currency code
account type and corresponding defaults
If you have multiple account types mapped to a given
commodity code and want to identify the default using Valid values are TRUE/FALSE (case-
this flag, as opposed to based on alphabetical order of insensitive)
the account type UniqueName
If you want to default the account assignment category See description
for a given company/commodity/account type
If you want to default the bill-to address for a given See description
company/commodity/account type
If you want to default a general ledger for a given

See description
If you want to default an internal order for a given See description

If you want to default the item category for a given See description
If you want to default the purchase group for a given See description
If you want to default the ship-to address for a given

company/commodity/account type See description
If you want to default a WBS element for a given See description

If you want to default an asset value for a given See description

If you want to default an asset value for a given
company/commodity/account type, and the asset has a See description
sub-number
If you want to default the deliver-to field for a given <=100 char.
Customer mapping
Back to homepage
TaxCode.csv (Import Tax Codes)

One record for every tax code, as defined by a unique MWSKZ/LAND1
combination.
Column Header
LAND1
MWSKZ
TEXT1
Name
ort Tax Codes)
ery tax code, as defined by a unique MWSKZ/LAND1
Field Descripton
The two-letter abbreviation of the country where the tax code is located. This field is used to
filter tax code choosers based on the country of the ship-to country.
The unique identifier of the tax code. This value is visible in the tax code chooser and when
viewing tax code details in the UI.
A description of the tax code. This value is visible in the tax code chooser and when viewing
tax code details in the UI.
A placeholder for the name of the tax code.
Always country code
Always <=50 char.
Always <=255 char.

Never <=255 char.
Customer mapping
N/A
Back to homepage
PaymentMethodType.csv (Import Payment Method Types)
One record for every payment method type.

Column Header
UniqueName
Name
Descripton
CanonicalName
ClearancePeriod
Rank
Electronic
Type.csv (Import Payment Method Types)
ery payment method type.

Field Descripton
A unique identifier (code) for the payment method type.
A user-visible name for the payment method. If no value is provided, UniqueName is used
instead.
A description for the payment method.

A standard canonical payment method type supported by the Ariba Network--this mapping is
use to translate payment methods on transactions between P2X/Invoice Pro and the Ariba
Network. You can map multiple ERP payment method types to one canonical payment
method type. Null or empty values are not allowed.
The number of days after which a payment made with the payment method is considered
cleared. When remittance advice is loaded against an invoice, the status remains "Paying"
until the clearance period of the payment method type used elapses, at which point the
status changes to "Paid". The default if left blank is 0.
A numeric rank that is used to select a preferred payment method when several are available.
Lower numbers have higher precedence. The default if left blank is 0.
A Boolean value that indicates whether the payment method is electronic. The default if left
blank is FALSE.
Always <=50 char.
If you want the Name to be different than the <=255 char.

UniqueName of the payment method type
Always <=255 char.

Valid values are ach, cash,
check, creditCard,
Always debitCard, draft, wire,
other (case-sensitive)
If you want to set the clearance period to Integer

something other than 0 days
If you want to set the rank to something other Integer

than 0
Valid values are TRUE/FALSE
If you want to set the value to TRUE (case-insensitive)
Customer mapping
Back to homepage
RequisitionHeader.csv (Import Requisitions)

One record for every requisition.
Column Header
Requisiton_Number
Preparer
PreparerPasswordAdapter
Requester
RequesterPasswordAdapter
Title
CompanyCode
DeliverTo
OriginatngSystem
OriginatngSystemReferenceID
Need_By_Date
Delay_Purchase_Untl
Comment
ExternalComment
Operaton
See RequisitionDetail.csv
See RequisitionSplitAccounting.csv
*The information provided in this column assumes you want to import a requisition and have it go into a Submitted status imm
(as is the typical use case), versus loading a "shell" requisition with the intent of having the preparer enter additional details in
and submit manually. If taking the latter approach, some of the information in this column may not be applicable, because in t
you just need to pass a small subset of validations to load the requisition and have it go into a Composing status.
eader.csv (Import Requisitions)
r every requisition.
Field Descripton
A unique internal identifier for the requisition. This field is not displayed in the P2X UI but is required to link
this file with the RequisitionDetail and RequsitionSplitAccounting files. It should be unique across all
requisitions included in a batch, but can be re-used in future batches if needed, as this value does not get
stored. For the sake of simplicity, this is often the same value as the OriginatingSystemReferenceID (see
below for details).
References UniqueName of user previsouly defined in User.csv. This user appears as the preparer on the
requisition, and will be notified and have access to edit the requisition if it is imported into P2X but fails to
pass all of the validations required to make it into a Submitted status.
References PasswordAdapter of user previsouly defined in User.csv. This user appears as the preparer on the
requisition, and will be notified and have access to edit the requisition if it is imported into P2X but fails to
pass all of the validations required to make it into a Submitted status.
References UniqueName of user previsouly defined in User.csv. This user appears as the requester on the
requisition.
References PasswordAdapter of user previsouly defined in User.csv. This user appears as the requester on
the requisition.
A title or description for the requisition. This is a required field on the requisition.
References BUKRS of company code previously defined in CompanyCode.csv. This is the company code
associated with the transaction. This is a required field on the requisition, but if left blank on the import,
will be set to the requester's default value.
The "Deliver To" field is printed on the purchase order under the ship-to address section, essentially as an
attention line. This is typically the requester's full name, sometimes with a mail stop included. This is a
required field on the requisition. If left blank, or if the system is configured to respect system defaults, this
field will be set to the requester's default value or the commodity-based default (via
ERPCommodityCodeMap file).
An identifier for the external system from which the requisition is imported (e.g., 'SAP'). This field is visible
in the P2X UI and can optionally be used to trigger custom logic (e.g., bypass certain approvals depending
on the source system). The default if left blank is 'Imported'.
If you are sending updates or cancellations to previously-imported requisitions, you must reference the
OriginatingSystem/OriginatingSystemReferenceID of the previously-imported requisitions.
An identifier for the source document from which the requisition is imported (e.g., the requisition ID, PO
Number, re-stock number, etc., from the source system). This field can be made visible in the P2X UI as a
reference for users.
If you are sending updates or cancellations to previously-imported requisitions, you must reference the
OriginatingSystem/OriginatingSystemReferenceID of the previously-imported requisitions.
A "Need By" date for the requisition. This is an optional field on the requisition, and is printed on the
purchase order if a value is sent. The need-by date is also present in RequisitionDetail.csv, and is actually a
line-level field on the purchase order--if the value is set here in the header file, the date propogates to each
of the lines in the requisition, except for any lines where the value is set on the line itself, in which case the
line-level value takes precedence.
The date on which the purchasing process (e.g., transmission of the order to the Ariba Network for
Network-enabled suppliers) starts for fully approved requisitions. This process does not start until the
specified Hold Until Date is reached.
A header-level comment that appears on the requisition and optionally the purchase order.
A flag that indicates whether the comment sent in the "Comment" field will be visible to supplier on the
purchase order. The default if left blank is FALSE, which means the supplier would not see the comment.
Specifies whether this is a new requisition (New), a change to a previously-imported requisition (Update), or
a cancellation of a previously-imported requisition (Cancel). This field is case-sensitive and thus letter-case
should exactly match these values. The default if left blank is 'New'.
ed in this column assumes you want to import a requisition and have it go into a Submitted status immediately
), versus loading a "shell" requisition with the intent of having the preparer enter additional details in the UI
aking the latter approach, some of the information in this column may not be applicable, because in that case
mall subset of validations to load the requisition and have it go into a Composing status.
When is this field required?* Restrictons
Always <= 50 char.

Always <= 128 char.
If you want to override the requester's default company
code or account for users who may not have a default set See description
in P2X (Recommended)
If you want to override the requisition's default "deliver

to" information, or account for scenarios where there may <= 100 char.
not be a default.
If you want to capture a reference to the source system of

the requisition, other than the default of 'Imported'. <=50 char.
(Recommended)
If you want to capture a reference to the ID of the source

document of the requisition and/or if you plan to send
changes/cancellations to previously-imported requisitions. <=50 char.
(Recommended)
If there is a need to communicate a date by which you
need the goods/services to the supplier, and this date is M/D/YYYY format,
captured at the header (vs line) level in your source Cannot be in the past
system.
If there is a need to delay the actual transmission of the M/D/YYYY format,

order until a certain date. Cannot be in the past
If you want to import header-level comments. None

If you are importing header-level comments and want
those comments to sometimes or always be visible to Valid values are TRUE/FALSE
suppliers. If you are not sending comments or intend for (case-insensitive)
comments to always be internal-only, you can let the
system default to FALSE.
If you are sending changes and/or cancellations to

previously-imported requisitions via the requisition See description
import. If you are only sending new requisitions, you can
let the system default to 'New'.
Customer mapping
Back to homepage
RequisitionDetail.csv (Import Requisitions)

One record for every requisition line.
Column Header
Requisiton_Number
Line_Number
Supplier
Supplier_Locaton
Contact_Id
Item_Descripton
Quantty
BillTo
Commodity_Code
CommonCommodity_Code
Domain
Currency
Unit_Of_Measure
Account_Assignment
SplitAccountngType
Item_Category
Purchase_Group
Purch_Org
ShipTo
ItemPartNo
ItemAuxPartId
ManPartNo
BuyerPartNumber
Facility
UnitConversion
Unit_Price
PriceUnit
PriceUnitQuantty
PricingDescripton
Account_Type
DeliverTo
Comment
ExternalComment
Need_By_Date
OriginatngSystemLineNumber
See RequisitionHeader.csv
See RequisitionSplitAccounting.csv
(as is the typical use case), versus loading a "shell" or incomplete requisition with the intent of having the preparer enter additi
details in the UI and submit manually. If taking the latter approach, some of the information in this column may not be applicab
because in that case you just need to pass a small subset of validations to load the requisition and have it go into a Composing
tail.csv (Import Requisitions)
r every requisition line.
Field Descripton
References Requisition_Number in RequisitionHeader.csv. This field ties the detail records to the header
records defined in RequisitionHeader.csv.
The line number for this detail line relative to the requisition. This field is required and is used to tie the
records in this file to the records in the RequisitionSplitAccounting file.
For a given requisition, the values in this field do not have to be consecutive or even sequential (e.g., if you
have three lines in a requisition, sending 2, 7, 4 is just as acceptable as sending 1,2,3). This field does NOT,
however, actually impact the ordering or numbering of the lines on the requisition created in P2X. In above
example, the lines on the requisition would be ordered based on the order in which they appear in this file,
and not based on the sequential values in this field, and the line numbers would be 1, 2, and 3.
For the sake of simplicity, two common approaches to populating this field are: 1. Sequential numbering
(e.g., if there is only one detail line for a given requisition, the value would be 1; if there are two lines, the
value for the first line would be 1 and the value for the second would be 2), and 2. using the same value as
the OriginatingSystemLineNumber (see below for details).
References LIFNR of supplier previously defined in Supplier.csv. This is the ID of the supplier on the
requisition line.
References LocationID of supplier location previously defined in SupplierLocationConsolidated.csv. This is

the ID of the supplier location on the requisition line. If left blank, the supplier location is defaulted to the
first supplier location for the supplier identified in the Supplier field.
References ContactID of supplier location previously defined in SupplierLocationConsolidated.csv. This is the

ID of the supplier location on the requisition line. If left blank, the supplier location is defaulted to the first
supplier location for the supplier identified in the Supplier field.
A description of the item. This is a required field on the requisition. If the imported requisition line matches
to an existing catalog item, this field will be set to the description for the item on the catalog. If using item
master matching functionality, this field will have a different impact based on whether or not the system is
configured to respect system defaults--if the system is configured to respect system defaults, this field will
be set to the description for the mapped item; if the system is configured NOT to respect system defaults,
the item master matching will not work properly.
The quantity of the item. The default if left blank is 1.

References WERKS of previously defined plant in Plant.csv. This is the ID of the bill-to address. If left blank,
or if the system is configured to respect system defaults, this field will be set to the requisition default value,
which could be based on the requester, a system parameter, the commodity (via ERPCommodityCodeMap
file).
References UniqueName of previously defined partitioned commodity code in ERPCommodityCode.csv. This

is the ERP commodity code for the item. For non-catalog items, you must specify either a system
commodity code (CommonCommodity_Code field) or an ERP commodity code. If matching to a kit/catalog
item or using item master matching, the system and ERP commodity codes are set based on the system
commodity code associated with the matched item.
References UniqueName of previously defined system commodity code in CommodityCode.csv. This is the
ID of the system commodity code for the item. For non-catalog items, you must specify either a system
commodity code (CommonCommodity_Code field) or an ERP commodity code. If matching to a kit/catalog
item or using item master matching, the system and ERP commodity codes are set based on the system
commodity code associated with the matched item.
References Domain of previously defined system commodity code in CommodityCode.csv. This is the
domain of the system commodity code for the item. This value is required if you specify a system
commodity code in the CommonCommodity_Code field. Typically this value will be "unspsc", though
depending on how your realm is configured, it may be something else (e.g., "custom").
The currency of the unit price. This field is defaulted to your realm's default currency if left blank.
References the Key of a previously-defined Unit of Measure mapping in UnitOfMeasureMap.csv. This is the
unit of measure used for the item. It is one of the keys used to match an imported requisition line to a
catalog item. The default if left blank is Each.
References KNTTP of previously-defined account assignment category in AccountCategory.csv. This is the ID
of the account assignment category for the requisition line. If left blank, or if the system is configured to
respect system defaults, this field will default to the commodity-based default account assignment category
(via ERPCommodityCodeMap file).
The type of split accounting for the item. Valid values are _Percentage, _Quantity, and _Amount. This field is
case-sensitive and thus letter-case should exactly match these values. The default if left blank is
_Percentage.
References UniqueName of a previously defined item category in ItemCategory.csv. This is the ID of the item
category for the requisition line. If left blank, or if the system is configured to respect system defaults, this
field will default to the commodity-based default item category (via ERPCommodityCodeMap file).
References EKGRP of a previously defined purchase group in PurchaseGroup.csv. This is the ID of the
purchase group for the requisition line. If left blank, or if the system is configured to respect system
defaults, this field will be set to the requester's default value or the commodity-based default (via
ERPCommodityCodeMap file).
References EKORG of a previously defined purchasing organization in PurchaseOrg.csv. This is the ID of the
purchase org for the requisition line. If left blank, or if the system is configured to respect system defaults,
this field will be set to the requester's default value.
References WERKS of a previously defined plant in Plant.csv. This is the ID of address to which the goods
should be shipped. If left blank, or if the system is configured to respect system defaults, this field will be set
to the requester's default value or the commodity-based default (via ERPCommodityCodeMap file).
The supplier part number of the item. This is one of the keys used to match an imported requisition line to
a kit (must match the Kit Part ID defined for the kit), or to a catalog item (must match the supplier part
number defined for the catalog item).
The supplier auxiliary part id of the item. This is an optional key used to match an imported requisition to a
kit (must match the Kit Aux. Part ID if one is defined for the kit), or to a catalog item (must match the
Supplier Aux. Part ID if one is defined for the catalog item).
The manufacturer part number of the item.

This is the part number used to look up the item if using item master mapping functionality. This
corresponds to the BuyerPartNumber field in BuyerItemMaster.csv.
This is the facility used to look up the item if using item master mapping functionality. This corresponds to
the Facility field in BuyerItemMaster.csv.
Ratio used to convert the ordered unit to the price unit. The unit price is based on the price unit quantity
and the price unit.
The unit price of the item. For non-catalog items this value is required for the requisition to move to the
Submitted status.
References the Key of a previously-defined Unit of Measure mapping in UnitOfMeasureMap.csv. This is the
unit of measure for the unit price.
The quantity corresponding to the unit price of the item specified by the supplier. The unit price is based on
the price unit quantity of the item.
Any information for quantity-based pricing. Buyers can use the field to store any information on the unit
conversion calculation.
References UniqueName of a previously defined account type in AccountType.csv. This is the ID of the
account type on the requisition line, which can drive different accounting defaults for a given commodity
code. If left blank, the system will set the value to the default account type defined for the commodity in
ERPCommodityCodeMap.
The name of the user to whom this line item must be delivered (essentially an attention line in the ship-to
section of the purchase order) . If left blank, or if the system is configured to respect system defaults, this
field will be set to the requester's default value.
A line-level comment that appears on the requisition and optionally the purchase order.
A flag that indicates whether the comment sent in the "Comment" field will be visible to supplier on the
purchase order. The default if left blank is FALSE, which means the supplier would not see the comment.
Need By date for line item. This is an optional field on the requisition, and is printed on the purchase order
if a value is sent.
The number of the corresponding line on the source document from which the requisition is imported. This
field can be made visible in the P2X UI as a reference for users, and can be used for receipt matching if
importing receipts (requires a configuration change made by Ariba personnel).
If you are sending updates to previously-imported requisitions, you must reference the
OriginatingSystemLineNumbers of the previously-imported requisition lines.
), versus loading a "shell" or incomplete requisition with the intent of having the preparer enter additional
mit manually. If taking the latter approach, some of the information in this column may not be applicable,
just need to pass a small subset of validations to load the requisition and have it go into a Composing status.
Always Integer
• Always if not using item master matching

• If using item master matching, send only if supplier See description
should be one of the criteria used in the match
If you have multiple supplier locations associated with the

supplier and want to specify which supplier location the See description
requisition is for, versus letting the system pick a default
If you have multiple supplier locations associated with the

supplier and want to specify which supplier location the See description
requisition is for, versus letting the system pick a default
• Always for non-catalog items

• If you are directly matching to a catalog item, completely
optional as it will have no impact either way
• If you are using item master matching functionality and
the system is configured to respect system defaults, <=2000 char.
completely optional as it will have no impact either way
• If you are using item master matching functionality and
the system is configured to respect the imported values
over the system default, do not send
If you will be importing requisitions lines with quantities > Decimal number
1. (Recommended)
If you want to override the requisition's default bill-to
address, or account for scenarios where there may not be See description
a default.
If the line item is non-catalog and you are identifying the

commodity using ERP commodity codes instead of System See description
Commodity Codes--i.e., send this field if you are not
sending CommonCommodity_Code.
If the line item is non-catalog and you are identifying the

commodity using system commodity codes instead of ERP See description
Commodity Codes--i.e., send this field if you are not
sending Commodity_Code.
If you are identifying the commodity using system

commodity codes instead of ERP Commodity Codes--i.e., See description
send this field if you are sending
CommonCommodity_Code..
If transacting in currencies other than the default currency Must be valid currency code
configured in your realm.
If creating requisition line items with a unit of measure See description

other than each.
If you want to override the requisition's default account

assignment category, or account for scenarios where there See description
may not be a default.
If you are using split accounting in your imported

requisitions and are splitting the accounting by Quantity or
Amount in some or all requisitions. Otherwise, you can See description
leave blank and allow the system to default to
_Percentage.
If you want to override the requisition's default item

category, or account for scenarios where there may not be See description
a default.
If you want to override the requisition's default purchase

group, or account for scenarios where there may not be a See description
default.
If you want to override the requester's default purchase

org or account for scenarios where there may not be a See description
default.
If you want to override the requisition's default ship-to

address, or account for scenarios where there may not be See description
a default. (Recommended)
If you are matching an imported requisition line to a kit or

catalog item, or if you want to communicate the part <=255 char.
number to the supplier on non-catalog line items.
(Recommended)
If you are matching an imported requisition line to a kit
that contains a Kit Aux. Part ID or a catalog item that
contains a Supplier Aux. Part ID, or if you want to <=255 char.
communicate an auxilliary part number to the supplier on
non-catalog line items.
<=255 char.
If using item master mapping functionality. <=50 char.
If using item master mapping functionality. <=50 char.
If using quantity-based/unit conversion pricing. Decimal number
Decimal number
If using quantity-based/unit conversion pricing. See description
If using quantity-based/unit conversion pricing. Decimal number
If using quantity-based/unit conversion pricing and you <=2000 char.

want users to see a description of the pricing details.
If you have multiple account types defined in the system,

and there is a need to override the commodity-based See description
default.
If you want to override the requester's default "deliver to"

information or account for users who may not have a <=100 char.
default set in P2X (Recommended)
If you want to import line-level comments. None
If you are importing line-level comments and want those
comments to sometimes or always be visible to suppliers. Valid values are TRUE/FALSE
If you are not sending comments or intend for comments (case-insensitive)
to always be internal-only, you can let the system default
to FALSE.
If there is a need to communicate a date by which you

need the goods/services to the supplier and this date is
captured at the line (vs header) level in your source M/D/YYYY format
system.
If you want to capture a reference to the line number of

the corresponding line on the source document of the Integer
requisition and/or if you plan to send changes to
previously-imported requisitions. (Recommended)
Customer mapping
Back to homepage
RequisitionSplitAccounting.csv (Import Requisitions)

If loading accounting information via the requisition import, one recor
for every requisition line accounting split. (If you are loading accountin
information but not actually splitting the accounting, the record count
would be the same as in RequisitionDetail.csv; if you are splitting the
accounting in some or all cases the record count would be greater tha
equalColumn
to the record count in RequisitionDetail.csv).
Header
If not loading accounting information via the requisition import (i.e.,
allowing the system defaults to be set), you do not need any records i
Requisiton_Number
this file--just load a file with the Requisition_Number and Line_Numb

Line_Number
column headers.
NumberInCollecton
Percentage
Quantty
CompanyCode
CostCenter
WBSElement
InternalOrder
GeneralLedger
Asset
SubNumber
ProcurementUnit
Account
See RequisitionHeader.csv
See RequisitionDetail.csv
(as is the typical use case), versus loading a "shell" or incomplete requisition with the intent of having the preparer enter additi
details in the UI and submit manually. If taking the latter approach, some of the information in this column may not be applicab
because in that case you just need to pass a small subset of validations to load the requisition and have it go into a Composing
litAccounting.csv (Import Requisitions)
ounting information via the requisition import, one record
uisition line accounting split. (If you are loading accounting
ut not actually splitting the accounting, the record count
same as in RequisitionDetail.csv; if you are splitting the
some or all cases the record count would be greater than or
ecord count in RequisitionDetail.csv). Field Descripton
accounting information via the requisition import (i.e.,
References Requisition_Number in RequisitionDetail.csv. This field, along with Line_Number, tie the split
ystem accounting
defaults toto the
records bedetail
set),recordsyou
defineddo not need any records in
in RequisitionDetail.csv.
oad a file with the Requisition_Number and Line_Number

References Line_Number in RequisitionDetail.csv. This field, along with Requisition_Number, tie the split
accounting records to the detail records defined in RequisitionDetail.csv.
ers. The number of the accounting split relative to the requisition line. (e.g., if there is only one accounting split
for a given requisition line, the value should be 1; if there are two splits, the value for the first split should
be 1 and the value for the second should be 2). The default if left blank is 1.
The percentage corresponding to the accounting split when splitting accounting by percentage. If you are
not actually splitting the accounting, and the SplitAccountingType for this line is Percentage, you should still
populate this field with "100".
The quantity corresponding to the accounting split when splitting accounting by quantity. If you are not
actually splitting the accounting, and the SplitAccountingType for this line is Quantity, you should still
populate this field with the total line quantity.
References BUKRS of company code previously defined in CompanyCode.csv. This is the company code of
the asset, general ledger, and/or cost center for the accounting split (those data elements include company
code as part of their unique key).
References KOSTL of a cost center previously defined in CostCenter.csv. This is the ID of the cost center for
the accounting split. If this field and the CompanyCode field are left blank, or if the system is configured to
respect system defaults, this field will be set to the requester's default value.
References POSID of a WBS element previously defined in WBSElement.csv. This is the ID of the WBS
element for the accounting split. If left blank, or if the system is configured to respect system defaults, this
field will be set to the commodity-based default value.
References AUFNR of an internal order previously defined in InternalOrder.csv. This is the ID of the internal
order for the accounting split. If left blank, or if the system is configured to respect system defaults, this
field will be set to the commodity-based default value.
References SAKNR of a general ledger previously defined in GeneralLedger.csv. This is the ID of the general
ledger for the accounting split. If this field and the CompanyCode field are left blank, or if the system is
configured to respect system defaults, this field will be set to the user or commodity-based default value.
References ANLN1 of an asset previously defined in Asset.csv. This is the ID of the asset for the accounting
split. If this field and the CompanyCode field are left blank, or if the system is configured to respect system
defaults, this field will be set to the commodity-based default value.
References ANLN2 of an asset previously defined in Asset.csv. This is the sub-number of the asset for the
accounting split. If this field and the CompanyCode field are left blank, or if the system is configured to
respect system defaults, this field will be set to the commodity-based default value.
References UniqueName of a purchasing unit previously defined in PurchasingUnit.csv. The split-accounting
level procurement unit field should not be used.
References UniqueName of an account previously defined in Account.csv. The account field is not used in
SAP variant.
), versus loading a "shell" or incomplete requisition with the intent of having the preparer enter additional
mit manually. If taking the latter approach, some of the information in this column may not be applicable,
just need to pass a small subset of validations to load the requisition and have it go into a Composing status.
If you have more than one accounting split for a given Integer
requisition line
If SplitAccountingType field in corresponding Decimal number

RequisitionDetail.csv record is null or set to _Percentage
If SplitAccountingType field in corresponding

Decimal number
RequisitionDetail.csv record is set to _Quantity
If an asset, general ledger, and/or cost center is referenced See description

on the accounting split.
If the accounting split should contain a cost center and you

want to override the requester's default or account for See description
scenarios where there may not be a default.
If the accounting split should contain a WBS element and

you want to override the default or account for scenarios See description
where there may not be a default
If the accounting split should contain an internal order and

If the accounting split should contain a general ledger and

If the accounting split should contain an asset code and

If the accounting split should contain an asset code that

has a sub-number, and you want to override the default or See description
account for scenarios where there may not be a default

Customer mapping
N/A
N/A
Back to homepage
ReceiptImport.csv (Import Receipts)

One record for every receipt line item.
Column Header
Receivable_Id
LineItem_Num
Is_Receiving_By_Count
Number_Accepted
Number_Rejected
Amount_Accepted
Amount_Rejected
Amount_Currency
Received_Date
External_Receipt_ID
Comment
Supplier
Supplier_Locaton
Commodity_Code
Quantty
Unit_Price
Unit_Price_Currency
Man_Part_Num
Item_Part_Num
mport.csv (Import Receipts)
rd for every receipt line item.
Field Descripton
The ID of the PO or contract the receipt is against.
When using ERP Order Method w/ order acknowledgement, the system can be configured to accept either
the internal Ariba PO ID or the PO Number assigned by your ERP (most customers opt for the latter in this
scenario).
The PO/contract line number the receipt is against.
A flag that Indicates whether the item is being received by quantity (TRUE) or amount (FALSE).
The number accepted for the receipt line item.
The number rejected for the receipt line item.
The amount accepted for the receipt line item.
The amount rejected for the receipt line item.

The currency of the accepted/rejected amount.
The date the receipt was created in source system. This field is not required but is visible on the receipt in
the P2X UI.
The ID associated with the receipt in the source system. This field is not displayed in the P2X UI but is
included in the Receipt Status export, and can be helpful for troubleshooting errors posting receipts to
PO/contracts in P2X.
A comment associated with the receipt line item. This field is only visible in the UI when a line item is
rejected, and not when the line item is accepted or received negatively. It is also included in the Receipt
Status export in all cases, and may be helpful for troubleshooting errors posting receipts to purchase
orders/contracts in P2X.
Placeholder for the supplier the receipt is for. However, this field does not drive any functionality and is not
visible in the P2X UI.
Placeholder for the supplier the receipt is for. However, this field does not drive any functionality and is not
visible in the P2X UI.
Placeholder for the commodity being received. However, this field does not drive any functionality and is
not visible in the P2X UI.
Placeholder for the quantity of the PO/contract line item the receipt is against. However, this field does not
drive any functionality and is not visible in the P2X UI.
Placeholder for the unit price of the PO/contract line item the receipt is against. However, this field does
not drive any functionality and is not visible in the P2X UI.
Placeholder for the unit price currency of the PO/contract line item the receipt is against. However, this field
does not drive any functionality and is not visible in the P2X UI.
Placeholder for the manufacturer part number associated with the PO/contract line item the receipt is
against. However, this field does not drive any functionality and is not visible in the P2X UI.
Placeholder for the item part number associated with the PO/contract line item the receipt is against.
However, this field does not drive any functionality and is not visible in the P2X UI.
When should this field be sent? Restrictons
Always Integer
Always (case-insensitive)
When receiving by quantity and sending an accepted (vs Decimal number
rejected) quantity
When receiving by quantity and sending a rejected (vs Decimal number
accepted) quantity
When receiving by amount and sending an accepted (vs Decimal number
rejected) amount
When receiving by amount and sending a rejected (vs Decimal number
accepted amount)
When receiving by amount Must be valid currency code
If you want users to see the date the item was received in M/D/YYYY format
the source system (Recommended)
If you will be using the Receipt Status export to
monitor/troubleshoot errors posting receipts to <= 255 char.
PO/contracts in P2X (Recommended)
If you want to display a "rejection reason" in cases of

rejections, or if you will be using the Receipt Status export
to monitor/troubleshoot errors posting receipts to <= 255 char.
purchase orders/contracts in P2X, and adding comments
would add value to that effort.
Never <= 255 char.
Never Decimal number
Never Must be valid currency code
Never <= 255 char.

Never <= 255 char.
Customer mapping
N/A
N/A
N/A
N/A
N/A
N/A
Back to homepage
Remittance.csv (Import Remittance)

One record for every payment transaction or cancellation.
Column Header
LOOKUPID
VERSION
VENDOR
POSTINGDATE
PAYMENTMETHOD
CHECKNO
STAT
NAME1
STREET
CITY
STATE
POSTALCODE
COUNTRY
PAYERBANKNO
PAYERBANKNAME
PAYERBANKACCNO
PAYEEBANKNO
PAYEEBANKNAME
PAYEEBANKACCNO
COMP_CODE
PAYDOC
CREATIONDATE
NETAMOUNT
CURRENCY
See RemittanceDetails.csv
ance.csv (Import Remittance)
cord for every payment transaction or cancellation.
Field Descripton
Together with VERSION, forms the unique identifier of the payment transaction. These fields are visible in
the P2P/Invoice Pro UI (under the History tab) as well as on the Ariba Network (as the Related Payment ID).
If sending a cancellation, this should match the LOOKUPID of the previously sent payment transaction.
Together with LOOKUPID, forms the unique identifier of the payment transaction. These fields are visible in
the P2P/Invoice Pro UI (under the History tab) as well as on the Ariba Network (as the Related Payment ID).
If sending a cancellation, this should match the VERSION of the previously sent payment transaction.
References LIFNR of supplier previously defined in Supplier.csv. This is the ID of the supplier to whom the
payment was sent.
The date of the payment. This field is not required in P2P/Invoice Pro, but it is required on the Ariba
Network (the transaction will fail when being passed from P2P/Invoice Pro to the Ariba Network if this field
is left blank), and is visible as the "Payment Date" in P2P/Invoice Pro as well as on the Ariba Network.
References UniqueName of previously defined payment method. This field is required and is visible in the
P2P/Invoice Pro UI as well as on the Ariba Network UI.
A reference number for the payment (e.g., check number for check payments). This field is not required but
is visible as a "Payment Reference Number" in P2P/Invoice Pro as well as on the Ariba Network.
The status of the payment transaction. Valid values are: 0(indicates paid) and 1(indicates cancelled). The
default is 0 if left blank.
A name or description of the address to which payment was sent. This field is not required and is not visible
in P2P/Invoice Pro, but is visible under the "Payee" section on the Ariba Network.
The street address to which payment was sent. If there are multiple lines they should be separated by line
feed characters. This field is not required and is not visible in P2P/Invoice Pro, but is visible under the
"Payee" section on the Ariba Network.
The city to which payment was sent. This field is not required and is not visible in P2P/Invoice Pro, but is
visible under the "Payee" section on the Ariba Network.
The state to which payment was sent (this is free text and not validated against a list of state abbreviations).
This field is not required and is not visible in P2P/Invoice Pro, but is visible under the "Payee" section on the
Ariba Network.
The postal code to which payment was sent. This field is not required and is not visible in P2P/Invoice Pro,
but is visible under the "Payee" section on the Ariba Network.
The two-letter abbreviation of the country to which payment was sent. This field is not required and is not
visible in P2P/Invoice Pro, but is visible under the "Payee" section on the Ariba Network.
The ID of the bank where the payment originated. This field is not required but is visible under the
"Originating Bank" section in P2P/Invoice Pro as well as on the Ariba Network.
The name of the bank where the payment originated. This field is not required but is visible under the
"Originating Bank" section in P2P/Invoice Pro.
The bank account number from where the payment originated. This field is not required but is visible under
the "Originating Bank" section in P2P/Invoice Pro.
The ID of the bank to where payment was sent. This field is not required but is visible under the "Receiving
Bank" section in P2P/Invoice Pro as well as on the Ariba Network.
The name of the bank where the payment was sent. This field is not required but is visible under the
"Receiving Bank" section in P2P/Invoice Pro.
The bank account number from where the payment was sent. This field is not required but is visible under
the "Receiving Bank" section in P2P/Invoice Pro.
References BUKRS of company code previously defined in CompanyCode.csv. Placeholder for the company
code associated with the transaction. However, this field does not drive any functionality and is not visible
in the P2P/Invoice Pro UI nor the Ariba Network.
Placeholder for the payment document number in SAP. However, this field does not drive any functionality
and is not visible in the P2P/Invoice Pro UI nor the Ariba Network.
A placeholder for the date the payment was created. However, this field does not drive any functionality
and is not visible in the P2P/Invoice Pro UI nor the Ariba Network.
A placeholder for the net amount of the payment. However, this field does not drive any functionality and is
not visible in the P2P/Invoice Pro UI nor the Ariba Network.
A placeholder for the currency of the payment. However, this field does not drive any functionality and is
nceDetails.csv
When should this field be sent? Restrictons
Combined with VERSION,

Always
should be <= 127 char.
Combined with LOOKUPID,

Always should be <= 127 char.
Always YYYYMMDD format
If you want users (and suppliers) to have visibility to a <= 50 char.

payment reference number (Recommended)
If you are sending both payments AND cancellations. If

you are only sending payments, you can leave blank and See description
let the system default to 0.
If you want suppliers to have visibility to the payee address <= 128 char.
information on the Ariba Network
If you want suppliers to have visibility to the payee address

information on the Ariba Network <= 50 char.
If you want suppliers to have visibility to the payee address See description
If you want users (and suppliers) to have visibility to the <= 25 char.
originating bank information.
If you want users (and suppliers) to have visibility to the
<= 50 char.
receiving bank information.
Never <= 50 char.
Never YYYYMMDD format
Never Must be valid currency code

Customer mapping
Back to homepage
RemittanceDetails.csv (Import Remittance)

One record for every payment transaction detail line (usually one
line per invoice).
Column Header
LOOKUPID
ITEM_NO
REFDOC
ITEMTEXT
CURRENCY
GROSSAMOUNT
CASHDISCOUNT
NETAMOUNT
DOC_NO
DOCDATE
PONUMBER
See Remittance.csv
anceDetails.csv (Import Remittance)
cord for every payment transaction detail line (usually one
r invoice).
Field Descripton
References LOOKUPID in Remittance.csv. This field ties the detail records to the header records defined in
Remittance.csv.
The line number for this detail line relative to the payment (e.g., if there is only one detail line for a given
payment, the value should be 1; if there are two lines, the value for the first line should be 1 and the value
for the second should be 2). This field is required and is visible on the Ariba Network.
The supplier invoice number (NOT the Ariba invoice number prefixed with "INV" nor the Ariba invoice
reconciliation number prefixed with "IR"). P2P/Invoice Pro will use either this field or ITEMTEXT to look up
the matching invoice document.
The Ariba invoice reconciliation number (this is the ID prefixed with "IR"). P2P/Invoice Pro will use either
this field or REFDOC to look up the matching invoice document.
The currency of the payment. This field is defaulted to your realm's default currency if left blank.
The gross amount of the payment. At least one of GROSSAMOUNT, CASHDISCOUNT, or NETAMOUNT is
required. This field is visible as the "Gross Amount" in P2P/Invoice Pro as well as on the Ariba Network.
The amount discounted on the payment. At least one of GROSSAMOUNT, CASHDISCOUNT, or NETAMOUNT
is required. This field is visible as the "Discount Applied" in P2P/Invoice Pro as well as on the Ariba Network.
The net amount (gross minus discount) of the payment. At least one of GROSSAMOUNT, CASHDISCOUNT, or
NETAMOUNT is required. This field is visible as the "Paid Amount" in P2P/Invoice Pro and as the "Net
Amount" on the Ariba Network. (Note that there is actual validation of the math here--e.g., if you send
$100 as the gross amount, $50 as the discount amount, and $40 as the net amount, the system will display
those values as is even though 100 minus 50 does not equal 40.)
The accounting document number in SAP. This field is not required in and of itself, but one of DOC_NO,
REFDOC, or ITEMTEXT is required on the Ariba Network (the transaction will fail when being passed from
P2P/Invoice Pro to the Ariba Network if one of these fields is not populated). This field not visible in
P2P/Invoice Pro, and is only visible on the Ariba Network when REFDOC is null and ITEMTEXT does not
match a valid IR.
A placeholder for the date of the invoice. However, this field does not drive any functionality and is not
visible in the P2P/Invoice Pro UI nor the Ariba Network.
A placeholder for the PO number of the invoice. However, this field does not drive any functionality and is
When should I populate this field? Restrictons
Always Integer
If you are matching to invoices in P2P/Invoice Pro using

the supplier invoice number instead of the Ariba invoice <= 50 char.
reconciliation ID.
If you are matching to invoices in P2P/Invoice Pro using
the Ariba invoice reconciliation ID instead of the supplier <= 50 char.
invoice number.
If transacting in currencies other than the default currency Must be valid currency code
configured in your realm.
Always (if not available in your source system, send the

Net Amount here) Decimal number
Always (if not available in your source system, send "0") Decimal number
Never, as long as you send either REFDOC or ITEMTEXT. <= 50 char.
Never YYYYMMDD format
Never <= 50 char.

Customer mapping
Back to homepage
RemittanceLocation.csv (Import Remittance Locations)
One record for every remittance location. Since one remittance

location record cannot be associated with multiple supplier locations
(1:n relationship,
Column Header
not n:n), if your vendor master supports an n:n
relationship
UniqueName
(i.e., one remittance location can be associated with
multiple
Name
ordering locations), you may need to create a unique
remittance location record for every valid ordering location/remittanc
location combination in your vendor master.
AddressUniqueName
Lines
City
State
CountryUniqueName
PostalCode
on.csv (Import Remittance Locations)
ery remittance location. Since one remittance

annot be associated with multiple supplier locations
not n:n), if your vendor master supports an n:n
Field Descripton
one remittance location can be associated with
A unique identifier for the remittance location.
locations), you may need to create a unique
The name of the remittance address as it must appear when data is sent to the address.
on record for every valid ordering location/remittance
tion in your vendor
A unique identifier for themaster.
remittance address associated with the remittance location. This ID
does not necessarily have to match the UniqueName of the remittance location, and can be
shared across multiple remittance location records if the physical address is the same.
The street address of the remittance location. If there are multiple lines they should be
separated by line feed characters.
The city of the remittance location.
The state of the remittance location.
The country of the remittance location.
The postal code of the remittance location.

Always <=50 char.
Always <=128 char.
Always <=50 char.
Always <=1024 char.

Always <=50 char.
Always <=50 char.
Always country code
When the remittance location address has a
postal code <=50 char.
Customer mapping
Back to homepage
UserConsolidated.csv (Import User Data [Consolidated File])

Column Header
UniqueName
PasswordAdapter
Name
EmailAddress
DefaultCurrency.UniqueName
TimeZoneID
LocaleID.UniqueName
Phone
Fax
Supervisor.UniqueName
Supervisor.PasswordAdapter
AlternateEmailAddresses
VanillaDeliverTo
PurchasingUnit
CardNumbers
SAPBillingAddress
SAPPlant
ApprovalLimit
ExpenseApprovalLimit
SAPCostCenter
SAPPurchaseOrg
SAPCompanyCode
SAPPurchaseGroup
SAPGeneralLedger
ImportCtrl
SAPEmployeeSupplierID
ted.csv (Import User Data [Consolidated File])
every active user.
Field Descripton
A unique identifier for the user. This is the user id the user enters when logging on to the Ariba site
if using application authentication. If remote authentication (SSO) is turned on, this will typically be
a user's corporate network ID.
Note that user IDs are case-sensitive when logging in or exchanging SSO messages.
This field in conjunction with UniqueName is used to uniquely define a user in Ariba and defines
the user's authentication mechanism.
If remote authentication is out of scope, this value should be "PasswordAdapter1" for all users. If
remote authentication is in scope, use "PasswordAdapter1" for users who will authenticate via
remote authentication and "ThirdPartyUser" for users who need to authenticate via the application
(e.g., contractors, etc., who don't have access to your network).
The full name (first and last) of the user. This is the name that appears in various places in the user
interface in Ariba.
The user email address.This email address is used by Ariba for sending notification messages for
approvals, escalations etc.
Use "no-reply@ansmtp.ariba.com" or "nobody@ansmtp.ariba.com" on your test site if you have to

use a dummy email address to prevent users from getting Ariba email notifications.
Default currency for the user when creating non-catalog requisitions and invoices in Ariba (the
default currency for catalog items is defined in the catalog). If this field is left blank it defaults to
the default currency configured in your site.
The time zone of the user, designated with a standard abbreviation such as PST. If the field is left
blank, the system defaults to the Ariba server time zone which is PST. This field actually drives very
little functionality in the system, with one exception being certain exports that contain date fields
without corresponding timestamps rely on this field to determine whether the date should render
pre- or post-midnight.
When a user logs in, the preferred locale determines the language, currency formats, date formats,
etc. for the user interface.
Users can change their preferred locale by modifying their user preferences.
The user's phone number. Visible in User Admin UI and on Network purchase orders when the
ship-to address record does not have a phone number.
The user's fax number. Visible in User Admin UI and on Network purchase orders when the ship-to
address record does not have a fax number.
References UniqueName of another user. This is the ID of the supervisor.
References PasswordAdapter of another user. This is the password adapter of the supervisor.
A comma-separated list of alternate email addresses for the user. Alternate email addresses are
used in a couple of ways in the system: 1. If email approval auto-reject functionality is enabled, this
allows for users with multiple email addresses to send email approvals from any of their accounts,
2. The requester on a non-PO invoice created on the AN is set based on the sold-to email address
input on the invoice, and this allows for identifying a user based on any of their valid email
accounts.
The user's preferred delivery information. Typically this is the user's full name. This is available on
the Ariba generated Purchase Order, essentially as an "attention line" in the ship-to section.
P2X only supports one deliver to field--there is no separate mailstop field. You may need to
account for first name, last name and mailstop in the same deliver to field if you have a need to
include the mailstop as part of the delivery information.
The system can be configured to set the value of this field to the value in the "Name" field, in which
case this field can be left blank or omitted.
References UniqueName of purchasing unit previously defined in PurchasingUnit.csv. Sets the

user's home purchasing unit. In the SAP variant of P2X, the purchasing unit can be mapped to the
company code instead of the user.
A comma-separated list of p-card numbers assigned to the user.
assigning as a default billing address to the user.
assigning as a default shipping address to the user.
It is not mandatory for users to have a default shipping address, but users who don't will receive a
warning message upon logging in until they have one.
The procurement approval limit for the user in the default currency for your site. This limit does not
apply to expense reports and travel authorizations.
If you have a need to load approval limits in currencies other than the default currency for your
site, contact your Ariba deployment team about implementing a customization to handle this
requirement.
The expense report or travel authorization approval limit for the user in the default currency for
your site.
References KOSTL of cost center previously defined in CostCenter.csv. Sets a default cost center for
the user.
References EKORG of purchase org previously defined in PurchaseOrg.csv. Sets a default purchase
org for the user.
A global default can be configured for this field in the Master Data Default Values screen.
References BUKRS of company code previously defined in CompanyCode.csv. Sets a default
company code for the user.
References EKGRP of purchase group previously defined in PurchaseGroup.csv. Sets a default

purchase group for the user.
A global default can be configured for this field in the Master Data Default Values screen.
References SAKNR of general ledger previously defined in GeneralLedger.csv. Sets a default general
ledger for the user. The GL would typically be based on the commodity, not the user, so is often not
populated on this file.
This field is for use in an FPC environment and determines whether a shared user record,
partitioned user record, or both, are created/updated when the file is loaded. If left blank, the
system defaults to creating only a shared user record when loaded in a parent realm, and only a
partitioned user record when loaded in a child realm. However, there may be cases when you want
to override the default, such as when giving users access to the parent realm, in which case they
will need a partitioned user record in the parent realm as well.
The valid values are "Shared", which creates/updates the shared user record only, and is the default
in a parent realm; "Partition", which creates/updated the partitioned user record only, and is the
default in a child realm; or "Both", which creates/updates both the shared user and partitioned
user records.
Placeholder for SAP Employee Supplier ID. However, this field does not drive any functionality and
is not visible in the P2X UI.
Highlighted cell indicates the field is
included in the Ariba-provided SAP
extracts and pre-populated values
indicate the source of the data
• <=255 char.
• No special characters except hyphen(-),
Always underscore (_), period (.) and @
• No spaces allowed
Always <= 50 char.
Has to be a valid email format

Always <= 255 char.
If you have a user population with different

default currencies and want to set defaults Must be a valid currency code
via file load versus having the user set it
him/herself
If your user population spans multiple time

zones and you are using exports from Ariba Must be a valid Ariba time zone ID
that contain date fields without
corresponding timestamps
Multi-language/country deployments where

you want this to be set for the user Must be a valid Ariba locale ID
automatically versus having the user set it
him/herself
If there is an active supervisor defined for the See description

user.
If there is an active supervisor defined for the
See description
user.
If there is a need to identify alternate email
addresses for some or all users, and you want <=100 char.
to maintain these via file load versus
maintenance in the User Manager UI
If you want to set the value to something

other than the user's name as defined in the
"Name" field; otherwise, the system can be
<=100 char.
configured to use the "Name" field as the
source and this field can be left blank or
omitted
If you are using purchasing unit functionality

and mapping purchasing units to users See description
instead of company codes
If you are assigining p-card to users and doing <=100 char.

so via file instead of via the Pcard Manager UI
If you want to default the billing address on a

req/PO based on user (as opposed to based See description
on company code, commodity, a global
default)
If you want to assign default shipping

addresses to users and do so via file instead See description
of or in addition to via UI or via self-service
user profile maintenance
If defining user approval limits for requisitions Integer

and/or invoices.
If defining an approval limit for travel or

expenses submitted in the Ariba Travel and Integer
Expense module.
If you want to default the cost center field on

a req or invoice based on user, and you want See description
to load the default via file instead of via self-
service user profile maintenance
If you want to default the purchase org field

on a req or invoice based on user, and you
want to load the default via file instead of via See description
self-service user profile maintenance or
setting a global default
If you want to default the company code field
on a req or invoice based on user, and you
want to load the default via file instead of via See description
self-service user profile maintenance
If you want to default the purchase group

field on a req or invoice based on user (versus
based on commodity or no default at all), and See description
you want to load the default via file instead
of via self-service user profile maintenance or
setting a global default
If you want to default the general ledger field

on a req or invoice based on user (versus
based on commodity or no default at all), and See description
you want to load the default via file instead
of via self-service user profile maintenance
If you are loading data into an FPC

environment and want to override the See description
default behavior for some or all records
Never <=100 char.

Customer mapping
USR02-BNAME
Always 'PasswordAdapter1'
BAPI_USER_GET_DETAIL-ADDRESS
Concat(FIRSTNAME+LASTNAME)
BAPI_USER_GET_DETAIL-ADDSMTP-E_MAIL
BAPI_USER_GET_DETAIL-PARAMETER(if PARID = 'FWS',

pick PARVA)
BAPI_USER_GET_DETAIL-LOGONDATA-TZONE
Concat( HR Language + HR country)
BAPI_USER_GET_DETAIL-ADDRESS concat(-TEL1_NUMBR-
TEL1_EXT)
BAPI_USER_GET_DETAIL-ADDRESS concat(FAX_NUMBER-
FAX_EXTENS)
HR (Cost Center Manager) User Id Cost Center Manager
/ARBA/USER/BUKRS_U
HR_GETEMPLOYEEDATA_FROMUSER-COSTCENTER
BAPI_USER_GET_DETAIL-PARAMETER(if PARID = 'EKO', pick

PARVA)
HR_GETEMPLOYEEDATA_FROMUSER-COMPANYCODE
BAPI_USER_GET_DETAIL-PARAMETER(if PARID = 'EKG', pick

PARVA)
N/A
Back to homepage
PaymentTermsConsolidated.csv (Import Payment Terms Data

[Consolidated File])
One record for every discount level per payment term,
including the 0% discount level, if applicable. As examples, a
simple "Net 30" term would contain one record in this file,
while a "2% 20, Net 30" term would contain two records--one
to represent the 2% discount if paid in 20 days, and a second
Column Header
to represent the net due date of 30 days.

UniqueName
Name
Descripton
InstallmentPercent
PayInDays
DiscountType
Discount
InstallmentNumber
msConsolidated.csv (Import Payment Terms Data
d File])
or every discount level per payment term,
e 0% discount level, if applicable. As examples, a
30" term would contain one record in this file,
20, Net 30" term would contain two records--one
the 2% discount if paid in 20 days, and a second
Field Descripton
the netAmaster
due datadate oftransactional
files and in 30 days.
unique identifier for the payment term. This value is referenced in the supplier
data exports, so is typically the code your ERP
uses (e.g., "N30" for Net 30 terms). This ID is displayed in the P2X UI under the
payment terms section of a PO/invoice/etc.
A descriptive name or title for the payment term (e.g., "Net 30"). This name is
displayed in the P2X UI when viewing the details of the payment terms on a
PO/invoice/etc. If your ERP does not contain three separate fields to store the ID, a
name, as well as a description, a common approach is to use the ID in this field as well.
A user-readable description of the payment terms (e.g., "Due in 30 days"). This

description is displayed in the P2X UI when viewing details of the payment terms on a
PO/invoice/etc and visible on the print version of PO's printed directly out of P2X.
The installment percentage for the payment term. This field must be set to 1, which
indicates 100 percent.
A value that specifies the number of days. This is the number of days in which the
payment must be made in order to qualify for the discounted specified in the
DiscountType/Discount fields.
The type of discount for the payment term, which can be either "percent" or "amount"
(case-insensitive).
A number that specifies the payment discount for early payment. This value is
interpreted as either a percentage or amount, depending on the value in the
DiscountType field. If using percentage discount, do not convert to decimal (e.g., use
"2", not ".02", to represent 2%).
This column header must always be present in the file, but the values should be left
blank for each record in this file.
Always <=50 char.
Always <=255 char.
Always <=255 char.
Always Must be set to 1
Always Integer
Column header must always be present in the file, but <=100 char.
no value is required
Customer mapping
T052-ZTERM
T052-ZTERM
FM FI_TEXT_ZTERM
Always '1'
T052-ZTAG1/T052-ZTAG2/T052-ZTAG3
Always 'percent'
T052-ZPRZ1/T052-ZPRZ2
Back to homepage
GroupConsolidated.csv (Import User to Group Mapping Data

[Consolidated File])
One record for every user/group/purchasing unit mapping.
Column Header
UniqueName
User_UniqueName
PasswordAdapter
PurchasingUnit
dated.csv (Import User to Group Mapping Data
File])
every user/group/purchasing unit mapping.
Field Descripton
References UniqueName of an out-of-the-box group or of a custom group previously defined in
CustomGroup.csv. This is the group to which you are assigning the user.
References UniqueName of user previously defined in SharedUser.csv. This is the ID of the user you
are assigning to the group.
adapter of the user you are assigning to the group.
References UniqueName of a purchasing unit previously defined in PurchasingUnit.csv. This is the

purchasing unit for which the user's group assignment will be effective.
If you are assigning purchasing unit

responsibility to a user's group assignment See description
Customer mapping
AGR_USERS-AGR_NAME
AGR_USERS-UNAME
Back to homepage
SupplierConsolidated.csv (Import Supplier Data [Consolidated File])
One record for every vendor.

Column Header
VendorID
Name
SystemID
NetworkID
DUNS
CustomDomainName
CustomDomainValue
PurchasingUnits
AmountRoundingForInvExceptonCalculaton
ImportCtrl
MinorityInfo
AddressID
Street
City
Country
State
PostalCode
CorporateEmailAddress
CorporateFax
CorporatePhone
CorporateURL
PreferredCurrency
PreferredLanguage
HasSyncRelatonship
HasTradingRelatonship
AnnualRevenueMaximum.Amount
AnnualRevenueMaximum.Currency.UniqueName
AnnualRevenueMinimum.Amount
AnnualRevenueMinimum.Currency.UniqueName
MinorityOwned
MinorityInfo
WomanOwned
NumberOfEmployees
OrganizatonType
StateOfIncorporaton
YearFounded
PaymentModel
(Import Supplier Data [Consolidated File])
dor.
Field Descripton
A unique identifier for the supplier. Typically the LIFNR ID of the vendor.
Supplier's name that is visible in supplier choosers in the UI and in the Supplier
Admin UI.
A unique identifier for the common supplier. If left blank, the default is taken from
the VendorID field.
• If you are suite-integrated and the supplier was created in Ariba Upstream prior
to being interfaced into P2P, you will send the Ariba System ID in this field.
• If you are not suite-integrated or the supplier is “net new” in Ariba, you can
leave the field blank.
In the first scenario, where you are matching up to existing supplier record, keep in
mind this field is case-sensitive (e.g., ACM_123 is not the same as acm_123).
The AN ID for the supplier. P2P uses this field as a unique ID to identify the
supplier on the Ariba Network in order to establish catalog connectivity.
The supplier's DUNS number.
This field allows you to add a custom domain (e.g., privateid, sap, psoft, etc.) to
the common supplier record.
This field allows you to define the value for the custom domain defined in
CustomDomainName.
References UniqueName of previously-defined purchasing unit(s) in

PurchasingUnit.csv. This field defines the purchasing unit(s) that a supplier belongs
to. Can contain multiple, comma-separated values (e.g., "DEU01,GBR01").
This field will be used to specify whether amounts need to be rounded during
invoice math error computation. If the field is set to 0 (by default) no rounding will
occur. If it is set to 1 then invoice line amounts will be rounded to currency
precision and then added up for computing the total cost for math error
calculation. If it is set to 2 then invoice line amounts will not be rounded. Instead
sum of invoice line items will be rounded to currency precision. The rounded total
cost will then be used during math error computation. Valid values are: 0 =
NoRounding 1 = RoundLineAmtToCurrencyPrecision 2 =
RoundTotalCostToCurrencyPrecision
This field is for use in an FPC environment and determines whether a supplier
organization record, partitioned supplier record, or both, are created/updated
when the file is loaded. If left blank, the system defaults to creating only a supplier
organization record when loaded in a parent realm, and only a partitioned supplier
record when loaded in a child realm. In a standalone (non-FPC) environment the
default creates/updates both supplier organization and partitioned supplier
records.
If you need to override the default (e.g., if you want to load partitioned suppliers
in the parent realm in a single-variant FPC configuration), the valid values are
"Shared", which creates/updates the shared user record only, and is the default in
a parent realm; "Partition", which creates/updated the partitioned user record
only, and is the default in a child realm; or "Both", which creates/updates both the
shared user and partitioned user records, and is the default in a standalone
environment.
The minority indicator string for the supplier (e.g., WOB [Women Owned
Business]). This field is visible on the supplier detail screen in the UI.
Deprecated

Always <= 64 char.
Always <=255 char.
If you need to define a SystemID different than

<= 64 char.
the VendorID
If the supplier is Ariba Network-enabled and

you want to capture the Network ID to assist <= 64 char.
with catalog connectivity
When you have a need to capture DUNS <= 64 char.

number
When you have a need to capture a

domain/value pair outside of networkid, duns, <=150 char.
buyersystemid, or internalsupplierid (e.g.,
privateid, sap, psoft, etc.)
When you have a need to capture a

domain/value pair outside of networkid, duns, <=384 char.
buyersystemid, or internalsupplierid (e.g.,
privateid, sap, psoft, etc.)
When using the PU functionality to filter <=100 char.

suppliers
If you need to set the value to 1 or 2 for some
or all of your suppliers, and want to do so via
this file (instead of manually, on a one-off See description
basis, in the UI). Leave blank if not using
invoicing functionality.
If you are loading data into an FPC

environment and want to override the default See description
behavior for some or all records
If you want this information displayed on the <=255 char.

supplier detail screen.
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Never
Customer mapping
LFA1-LIFNR
LFA1-NAME1
/ARBA/SYSTID_MAPS-SystemID
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Back to homepage
SupplierLocationConsolidated.csv (Import Supplier Location Data [Con

File])
One record for every supplier location.
Column Header
VendorID
LocatonID
Name
City
Street
PostalCode
Region
Country
Phone
Fax
EmailAddress
ContactName
PreferredOrderingMethod
PCardAcceptanceLevel
GhostPCardNumber
ChangeOrderRestrictons
AribaNetworkId
SplitOrderOnShipTo
Locale
ContactID
PaymentModel
ANPayEnabled
d.csv (Import Supplier Location Data [Consolidated
location.
Field Descripton
References VendorID of supplier previously defined in SupplierConsolidated.csv.
A unique identifier for the supplier location. Typically the LIFNR ID of the ordering address.
Supplier location's name that is visible in supplier location choosers in the UI and in the
Supplier Admin UI.
The city for the supplier location. Visible in the Supplier Admin UI, on the printed PO, and
The street address for the supplier location. If there are multiple lines they should be
separated by line feed characters. Visible in the Supplier Admin UI, on the printed PO, and
The postal code for the supplier location. Visible in the Supplier Admin UI, on the printed
PO, and when viewing supplier location details elsewhere in the UI.
The state for the supplier location. Visible in the Supplier Admin UI, on the printed PO, and
The two-letter abbreviation of the country where the supplier location is located. The
Country field determines the locale for this supplier location, which is used to determine
the language for communicating with the supplier location. Visible in the Supplier Admin
UI, on the printed PO, and when viewing supplier location details elsewhere in the UI.
The phone number of the supplier location. Visible in the Supplier Admin UI and when
The fax number for the supplier location. Visible in the Supplier Admin UI and when
viewing supplier location details elsewhere in the UI. It is also used to route quick-
enablement fax orders.
The email address for the supplier location. Visible in the Supplier Admin UI and when
The name of a contact person at the supplier location. Visible in the Supplier Admin UI and
The preferred ordering method for sending orders to the supplier location. The valid values
are:
• URL: Use this for suppliers with which you have established a relationship on the Ariba
Network.
• Email: Use this only when using “quick enablement” functionality via email for a supplier.
• Fax: Use this only when using “quick enablement” functionality via fax for a supplier.
• Print: Use this for suppliers with which you have not established a relationship on the
Ariba Network and with which you are not using “quick enablement” functionality.
These values are case-sensitive.
The default can be configured to any of the above values.
A number that indicates whether the supplier location accepts purchasing cards.
The value must be one of the following: 0 (The supplier location does not accept
purchasing cards), 1 (The supplier location accepts purchasing cards). The default can be
configured to be either 0 or 1.
References cardNumber of previously defined p-card in Pcard.csv. This is the ghosted p-

card number for the supplier locaton.
A number that indicates whether the supplier location accepts change orders.
The value must be one of the following: 0 (The supplier accepts change orders), 1 (The
supplier does not accept change orders). The default can be configured to be either 0 or 1.
The AN ID for the supplier location. P2P uses this field as a unique ID to identify the
supplier on the Ariba Network and to route purchase orders to the suppliers. For manual
suppliers, leave this field blank.
A Boolean value that indicates whether the supplier location can handle line items
aggregated onto an order if those line items have different shipping addresses. If you set
this field to true, P2X creates separate orders for each shipping address. The default can be
configured to be either TRUE or FALSE.
Locale that is used to determine the language in which the PO must be printed. If left
blank, the PO will be printed in the language associated with the supplier location country.
ID for a contact person associated with the supplier location. If left blank, the default is
taken from the LocationID field. In a typical SAP scenario, there is no need to have a
ContactID defined that is different than the LocationID and thus this field should not be
used.
Vestige of legacy functionality--no longer used. Specifies the payment model for the
supplier location. The payment model defines how payment transactions are handled. If
you want to send payment requests to Ariba SN, set this value to ANPay. If you want
payment requests to be processed in an external system, such as an ERP system, set this
value to ExternalPay. If you leave this value blank, the supplier location uses the payment
model for the supplier. If a payment model is not specified for the supplier, the supplier
location uses the payment model configured for your site. Valid values are: -1 = Default 0 =
ExternalPay 1 = LocalPay 2 = AribaNetworkPay
Deprecated
When is this field required? Restrictons Customer mapping

Always See description LFA1-LIFNR
Always <=50 char. WYT3-LIFN2
Always <=128 char. ADRC-NAME1
Always <=50 char. ADRC-CITY1
Always <=1024 char. ADRC-STREET
Always <=50 char. ADRC-POST_CODE1
If the address has a state/region <=50 char. ADRC-REGIO

Always ADRC-LAND1
country code
If you need this information displayed in <=70 char. ADRC-TEL_NUMBER

the UI
• <=70 char.
• If using quick enablement via
Always when using quick enablement via fax, format must be as follows:
fax for a supplier; otherwise only if you +<Country ADRC-FAX_NUMBER
need this information displayed in the UI Code><Area_Code><Telephon
e_Number> (e.g.,
+49(711)8707286)
Always when using quick enablement via

email for a supplier; otherwise only if you <=100 char. ADR6-SMTP_ADDR
need this information displayed in the UI
If you need this information displayed in
the UI <=100 char. LFM1-VERKF
If you are maintaining the preferred

ordering method in Ariba in your vendor
master. The default can be configured to
any of the valid values in which case
exceptions can be managed directly in See description
Ariba (e.g., setting default to Print and
manually changing to Fax/Email/URL on
an exception basis in the Supplier
Manager UI).
If you are maintaining this field in your

vendor master. The default can be
configured to either 0 or 1 in which case
Ariba (e.g., setting default to 0 and
manually changing to 1 on an exception
basis in the Supplier Manager UI).
If you are using ghosted p-cards and want

to map them to suppliers in this file See description
(instead of manually in the UI). Leave
blank if not using p-card functionality.

configured to either 0 or 1 in which case
Ariba (e.g., setting default to 0 and
manually changing to 1 on an exception
basis in the Supplier Manager UI).
If the PreferredOrderingMethod is set to <=255 char.

"URL"; otherwise, leave blank

configured to either TRUE or FALSE in
which case exceptions can be managed Valid values are TRUE/FALSE
directly in Ariba (e.g., setting default to (case-insensitive)
TRUE and manually changing to FALSE on
an exception basis in the Supplier
Manager UI).
If there is a need to specify a locale
(which drives language used on printed
PO) other than your realm default or the
locale associated with the supplier Must be a valid Ariba locale ID
location country, and you want to do so
via this file (instead of manually, on a
one-off basis, in the UI)
Never <=50 char. N/A
Never See description N/A

Never N/A
(case-insensitive)
Back to homepage
RemittanceLocationConsolidated.csv (Import Remittance Location Dat

One record for every remittance location. Since one remittance location record cannot be associate
relationship (i.e., one remittance location can be associated with multiple ordering locations), you m
location combination in your vendor master.
Column Header
SupplierLocatonID
RemitanceLocatonID
Name
PaymentMethod
AddressUniqueName
Lines
City
State
PostalCode
CountryUniqueName
BankInfo
BankAccountIDType
BankAccountType
BankAddressUniqueName
BankIDType
BankInfoName
BankAccountID
BankCity
BankCountry
BankStreet
BankPostalCode
BankRegion
BankID
BankName
ContactId
ted.csv (Import Remittance Location Data [Consolidated File])
Since one remittance location record cannot be associated with multiple supplier locations (1:n relationship,
can be associated with multiple ordering locations), you may need to create a unique remittance location rec
er.
Field Descripton
References LocationID of supplier location previously defined in
SupplierLocationConsolidated.csv.
A unique identifier for the remittance location. Since one remittance location record
cannot be associated with multiple supplier locations (1:n relationship, not n:n), if your
vendor master supports an n:n relationship (i.e., one remittance location can be associated
with multiple ordering locations), you may need to create a unique remittance location
record for every valid ordering location/remittance location combination in your vendor
master, and this field must be unique for every record. One common way to achieve
uniqueness is to concatenate the supplier location ID, a delimiter, and the remittance
location ID in this field. For example, if the supplier location ID in your vendor master is
001, and the remittance location ID in your vendor master is 555, the value in this field
might be "001-555".
The name of the remittance address as it must appear when data is sent to the address.
References UniqueName of a payment method type previously defined in

PaymentMethodType.csv. This is the payment method that will be used to remit payment
to the remittance location.
A unique identifier for the remittance address associated with the remittance location. This
ID does not necessarily have to match the UniqueName of the remittance location, and
can be shared across multiple remittance location records if the physical address is the
same. This is the field that is used to look up the remittance location on a Network invoice.
As such, even if you are using a concatenated approach for the RemittanceLocationID, you
should only use the remittance location ID from your vendor master in this field, because
that it what your suppliers would reference on their invoices. In above example, the value
of this field would be just "555", not "001-555".
The street address of the remittance location. If there are multiple lines they should be
separated by line feed characters.
The city of the remittance location.
The state of the remittance location.
The postal code of the remittance location.

The two-letter abbreviation of the country where the remittance location is located.
The unique internal identifier of the supplier payment bank location for the remittance
location.
References UniqueName of a bank account ID type previously defined in

BankAccountIDType.csv.
References UniqueName of a bank account type previously defined in

BankAccountType.csv.
A unique internal identifier for the address of the bank.
The unique internal identifier for a bank identifier type.
A user-visible name for the bank account.
The bank account identifier.
The bank city.
The country of the bank location.
The bank street address.
The bank ZIP or postal code.
The bank state.
The bank identifier.
The name of the bank where the account resides.
References ContactID of supplier location previously defined in

SupplierLocationConsolidated.csv. If left blank, the default is taken from the
SupplierLocationID field. In a typical SAP scenario, there is no need to have a ContactID
defined that is different than the LocationID and thus this field would not be used.
nsolidated File])
ultiple supplier locations (1:n relationship, not n:n), if your vendor master supports an n:n
to create a unique remittance location record for every valid Highlighted
orderingcelllocation/remittance
indicates the field is
Always See description LFA1-LIFNR/WYT3-LIFN2
Concatenation of supplier LFA1-LIFNR and

Always <=50 char. partner LFA-LIFNR
Always <=128 char. ADRC-NAME1
Always See description LFB1-ZWELS
Always <=50 char. LFA1-LIFNR
Always <=1024 char. ADRC-STREET

Always <=50 char. ADRC-CITY1
If the address has a state/region <=50 char. ADRC-REGIO
Always <=50 char. ADRC-POST_CODE1

Always country code ADRC-LAND1
If you want to associate bank details with <=50 char. N/A

remittance locations in P2X (rarely used)
If you want to associate bank details with

remittance locations in P2X (rarely used) See description N/A
If you want to associate bank details with See description N/A







If you want to associate bank details with

remittance locations in P2X (rarely used) <=255 char. N/A




Never See description N/A

Back to homepage
TaxTypeMap.csv (Import Tax Type Mappings)

One record for every tax type mapping.
Column Header
Name
TaxLineType
Import Tax Type Mappings)
ery tax type mapping.
Field Descripton
The common tax name. This is the tax name that appears on invoices.
A reference to the P2X/Invoice Pro line type. Valid pre-defined values are: SalesTax, VATTax,
GSTTax, PSTTax, HSTTax, QSTTax, WHTTax, UseTax. The Tax Line Type field values should
match either the pre-defined values or the values defined by your administrator
in the procure line type configuration.
Always <=50 char.
Always <=50 char.

Customer mapping
Back to homepage
PunchinGroup.csv (Import Punchin Groups)

One record for every group that will be referenced in punchout setup
requests.
Column Header
UniqueName
Name
v (Import Punchin Groups)
ery group that will be referenced in punchout setup
Field Descripton
A unique identifier for the punchin group.
A name for the punchin group. This value is visible in the UI wherever groups are referenced.
Always <=255 char.
Always <=255 char.
Customer mapping
Back to homepage
PurchOrdHeaderDetails.csv (Export Purchase Order to ERP)

One record for every purchase order.
Column Header
ERPORDERID
PMNTTRMS
CURRENCY
DOC_DATE
PUR_GROUP
VENDOR
CO_CODE
PURCH_ORG
ARIBA_DOC_TYPE
ORI_SYS_ID
ORI_SYS
HDTEXT
DOCDATE_USERTIMEZONE
SUPPLIERLOCATION
IsServiceOrder
See PurchOrdLineDetails.csv
See PurchOrdAcctDetails.csv
See PurchOrdLineAddDetails.csv
See PurchOrdScheduleDetails.csv
See PurchOrdLineText.csv
Details.csv (Export Purchase Order to ERP)
ery purchase order.
Field Descripton
Defines the unique purchase order ID for which it shows the status.
A unique code of the supplier payment terms.
Defines the type of currency used for the Purchase Order.
Defines the date of creation of the requisation
Defines a unique purchase group ID.
Defines the suppliers unique number for the changed Purchase Order.
Defines a unique Company code Number.
Defines a unique Purchase Organization ID.
Defines the ordering method category for every purchase order. Potential values are "ERPCC"
if the preferred ordering method of the supplier is Fax, Email, or Electronic Ordering, or "ERP"
if the preferred ordering method of the supplier is Print.
The reference ID of the originating system.
The system on which the requisition was created.
Defines the Title of ERP ORDER .
This field defines the creation date of the requisition in the user’s time zone. The format of
the date is YYYYMMDD. For example, 20140225.
The unique identifier of the supplier location for the purchase order.
Indicates whether this PurchaseOrder is a Service Order.
Format Customer mapping
<=50 char.
<=50 char.
<=50 char.
MM/DD/YYYY
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=128 char.
YYYYMMDD
<=50 char.
Boolean
Back to homepage
PurchOrdLineDetails.csv (Export Purchase Order to ERP)

One record for every purchase order line.
Column Header
ERPORDERID
PLANT
REQ_ID
HAS_ADHOC_SHIPTO_ADDRESS
ACCTASSCAT
MAT_GRP
PART_INV
CITY
DEFAULT_SHIPTO
PO_ITEM
POSTAL_CODE
ADDRESS_LINES
UNIT
NET_PRICE
ITEMONREQ
ITEM_CAT
STATE
PUR_MAT
COUNTRY
SHORT_TEXT
DISTRIB
SERVICE_LINE_ITEM_DETAILS
RECEIVINGTYPE
MATERIAL
CONV_UNIT
ORDERPR_UN
PBQ_DESC
PRICE_UNIT
REQUISITIONLINENUMBER
MaxAmount
ExpectedAmount
MaxAMount_currency
RequiresServiceEntry
Expectd_Currency
ServiceStartDate
ServiceEndDate
PARENT_LINE_NUMBER
See PurchOrdHeaderDetails.csv
ails.csv (Export Purchase Order to ERP)
ery purchase order line.
Field Descripton
Defines the unique ID of the location where line item must be shipped.
Defines the particular line item on the particular requisation.
Indicates shipping id is either valid ERP master data or adhoc value added in Ariba Buyer
Defines account assignment categories. Account assignment categories are used to specify
how to assign a line item expenditure to an account. Examples of account assignment
categories are assets,WBS elements, and cost centers.
Defines the unique commodity code for each line item.
Defines the SAP Partial invoice flag.
City where goods need to be shipped.
Default shipping id associated with the requester.
Defines the line number of the corrpeponding line item in the changed Purchase Order.
Postal code of the area where goods need to be shipped.
Address line containing valid shipping address or part of it.
Defines the unit of measure for each line item in the changed Purchase Order.
Defines the net amount of each line item in the Purchase Order.
Defines the line number of an item in the requisition.
Defines the code of the item category for each line item. Examples for item categories are
standard, subcontract, and consignment.
State where goods need to be shipped.
Defines the part number of every item in the Purchase Order.
Country where goods need to be shipped.
Provides the description of the line item.
Defines SAP Distribution Flag.
The services line item details in string format. This string will contain all the category specific
line item details in a xml format in a single string. This XML will contain all the category
specific fields in cXML format in a single column.
Defines the receiving type unique value. Potential values are:
• 0 (System Received)
• 1 (Auto Receipt on Due Date)
• 2 (Manual by Count)
• 3 (Manual by Amount)
• 4 (No Receipt)
• 5 (PCard Auto Receipt)
• 6 (Milestone Verification)
• 7 (Auto Receipt during Invoice Reconciliation)
• 8 (System Received by Amount)
• 9 (Auto Receipt on Due Date by Amount)
• 10 (No Receipt by Amount)
• 11 (PCard Auto Receipt by Amount)
• 12 (Auto Receipt by Amount during Invoice Reconciliation)
• 13 (Auto Receipt during Invoice or PCard Reconciliation)
• 14 (Auto Receipt by Amount during Invoice or PCard Reconciliation)
Defines the Item number of every item in the Purchase Order.

The conversion ratio from the unit of measure of the order to the unit of measure of the
PriceBasisQuantity.
Unit of measure for the quantity defined by Price Basis Quantity.
It defines the description that describes the Price basis quantity fields for each item in the
requisition line items
The quantity the price is quoted on.
The line number used externally to identify this line item. This is the line number of the
requisition line item associated with this order line item.
The Max Amount for the parent line item in Service PO.
The expected Amount for the parent line item in Service PO.
The currency code of MaxAmount.
Indication whether a service entry sheet is required or not.
The currency code of ExpectedAmount.
The Service Start date for the parent line item in Service PO.
The Service End date for the parent line item in Service PO.
Line number of the parent of this line item.
<=50 char.
<=50 char.
<=22 char.
Boolean
<=50 char.
<=50 char.
<=1 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=1024 char.
<=50 char.
Decimal number
<=10 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=2000 char.
<=1 char.
<=100 char.
Integer
<=255 char.
Decimal number
<=50 char.
<=2000 char.
Decimal number
Integer
BigDecimal
BigDecimal
<=50 char.
Boolean
<=50 char.
Date
Date
Integer
Back to homepage
PurchOrdAcctDetails.csv (Export Purchase Order to ERP)

One record for every purchase order line accounting split.
Column Header
ERPORDERID
SERIAL_NO
ASSET_NO
QUANTITY
ORDER_NO
PO_ITEM
G_L_ACCT
WBS_ELEM_E
DISTR_PERC1
SUB_NUMBER
COST_CTR
AMOUNT
RECEIVINGTYPE
SAP_SERIAL_NO
ails.csv (Export Purchase Order to ERP)
ery purchase order line accounting split.
Field Descripton
Defines the unique Purchase Order ID for which it shows a status.
Describes the serial number of each line item.
Defines the unique value of the Asset account assignment category for each line item.
Defines the quantity for each line item to be purchased.
Defines the unique value of the internal order account assignment category for that line item.
Defines the line number of the corresponding line item.
The unique value of the General ledger acounting type for each line item.
A unique code of the WBS element account assignment category for that line item.
The split accounting percentage on a particular line item.
Defines the sub-number of the asset account assignment category for that line item.
A unique value of the Cost center account assignment category for each line item.
Defines the amount for each line item.

• 4 (No Receipt)
Describes the SAP serial number of each line item.

<=50 char.
Integer
<=50 char.
Decimal number
<=50 char.
<=5 char.
<=50 char.
<=50 char.
Decimal number
<=4 char.
<=50 char.
Decimal number
Integer
<=100 char.
Back to homepage
PurchOrdLineAddDetails.csv (Export Purchase Order to ERP)

Column Header
ERPORDERID
UNDER_TOL
PO_ITEM
OVERDELTOL
Details.csv (Export Purchase Order to ERP)
Field Descripton
Sets the lower limit of the tolerance for every line item.
Sets the upper limit of the tolerance for every line item.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
Back to homepage
PurchOrdScheduleDetails.csv (Export Purchase Order to ERP)

Column Header
NET_PRICE
ERPORDERID
PREQ_NO
QUANTITY
DLV_DT
PREQ_ITEM
DELIV_DATE
PO_ITEM
RECEIVINGTYPE
eDetails.csv (Export Purchase Order to ERP)
Field Descripton
Defines the net amount of each line item of the Purchase Order.
Defines Purchase Order unique ID for which it shows a status.
This is the Originating System Reference ID.
Defines the quantity to be purchased for each line item in the purchase order.
Defines the delivery date for each line item converted in to requester's time zone and
yyyymmdd format.
This is the Originating System Line Number.
Defines the delivery date for each line item.

• 4 (No Receipt)
Decimal number
<=50 char.
<=50 char.
Decimal number
YYYYMMDD
Integer
YYYYMMDD
<=50 char.
Integer
Back to homepage
PurchOrdLineText.csv (Export Purchase Order to ERP)

One record for every purchase order.
Column Header
ERPORDERID
STRING
TDOBJECT
TDID
PO_ITEM
STRINGNUM
.csv (Export Purchase Order to ERP)
ery purchase order.
Field Descripton
Defines the unique Purchase Order ID for which it shows a status.
Defines the string (text) for each line item in the purchase order.
Defines an object of the text for each line item in the purchase order.
Defines a unique ID for the text of each line item in the purchase order.
Defines the string number of the text for each line item in the purchase order.
<=50 char.
<=255 char.
<=10 char.
<=4 char.
<=5 char.
Integer
Back to homepage
ChangePurchOrdHeaderDet.csv (Export Change Purchase Order)

One record for every change purchase order.
Column Header
ERPORDERID
PMNTTRMS
WAERS
EKGRP
LIFNR
EKORG
ORDERTYPE
VERSION
EBELN
HDTEXT
IsServiceOrder
See ChangePurchOrdLineDet.csv
See ChangePurchOrdAcctDet.csv
See ChangePurchOrdSchdlDet.csv
See ChangePurchOrdDelAcct.csv
See ChangePurchOrdDelItems.csv
See ChangePurchOrdLineText.csv
HeaderDet.csv (Export Change Purchase Order)
ery change purchase order.
Field Descripton
Defines the unique purchase order ID with latest version number.
A unique code of the supplier payment terms.
Defines the type of currency used for the changed Purchase Order.
Defines a unique purchase group ID.
Defines the suppliers unique number for the changed Purchase Order.
Defines a unique Purchase Organization ID.
Defines the ordering method category for every purchase order.
This is a supplemental version number of the original order. Ariba Buyer implements change
orders by sending an updated order to the supplier, as a revision of the original order. The
order number remains the same, but there is a supplemental version number.
Defines the unique ID for every version of the purchase order for which it shows the status.
Defines the Title of ERP ORDER . This value must match with an HDTEXT defined in
ChangePurchOrdHeaderDet.csv.
Indicates whether this PurchaseOrder is a Service Order
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
Integer
<=50 char.
<=128 char.
Boolean
Back to homepage
ChangePurchOrdLineDet.csv (Export Change Purchase Order)

One record for every change purchase order line.
Column Header
ERPORDERID
UNTTO
UEBTO
WERKS
EEIND
MATKL
CITY
DEFAULT_SHIPTO
EBELP
POSTAL_CODE
CHGSTATE
ITEMONREQ
NETPR
MWSKZ
MENGE
EPSTP
STATE
EMATNR
COUNTRY
TXZ01
RECEIVINGTYPE
DLV_DT
TWRKZ
KNTTP
HAS_ADHOC_SHIPTO_ADDRESS
ADDRESS_LINES
MEINS
REQ_ID
PREQ_ITEM
VRTKZ
CONV_UNIT
ORDERPR_UN
PBQ_DESC
PEINH
MaxAmount
ExpectedAmount
RequiresServiceEntry
Expectd_Currency
PARENT_LINE_NUMBER
MaxAMount_currency
ServiceStartDate
ServiceEndDate
See ChangePurchOrdHeaderDet.csv
LineDet.csv (Export Change Purchase Order)
ery change purchase order line.
Field Descripton
Defines the unique Purchase Order ID with its version number.
It sets the lower limit of the tolerance for every line item.
It sets the upper limit of the tolerance for every line item.
Defines the unique ID of the location where line item must be shipped.
Defines the delivery date for each line item in the changed Purchase Order.
Defines the unique commodity code for each line item.
City where goods need to be shipped.
Default shipping id associated with the requester.
Defines the line number of the corrpeponding line item in the changed Purchase Order.
Postal code of the area where goods need to be shipped.
Defines the state of the split accounting of line items; if it is Change, the value is 2.
Defines the line number of an item in the requisition.
Defines the Tax code as per evaluated receipt settlement (ERS) agreements. These
agreements have different tax rates depending on factors such as the tax laws in the location
of the supplier and requestor.
Defines the quantity for each line item to be purchased in the changed Purchase Order.
Defines the code of the item category for each line item. Examples for item categories are
standard, subcontract, and consignment.
State where goods need to be shipped.
Defines the part number of every item in the Purchase Order.
Country where goods need to be shipped.
It provides the description of the line item.
• 4 (No Receipt)
Defines the delivery date for each line item in the changed Purchase Order converted in
user's time zone and yyyymmdd format.
Defines the SAP Partial invoice flag.
This defines account assignment categories. Account assignment categories are used to
specify how to assign a line item expenditure to an account. Examples of account assignment
categories are assets,WBS elements, and cost centers.
Indicates shipping id is either valid ERP master data or adhoc value added in Ariba Buyer
Address line containing valid shipping address or part of it.
Defines the unit of measure for each line item in the changed Purchase Order.
This is the Originating System Reference ID.
This is the Originating System Line Number.
The conversion ratio from the unit of measure of the order to the unit of measure of the
PriceBasisQuantity.
The line number used externally to identify this line item. This is the line number of the
requisition line item associated with this order line item.
The Max Amount for the parent line item in Service PO.
The expected Amount for the parent line item in Service PO.
Indication whether a service entry sheet is required or not.
The currency code of ExpectedAmount.
The currency code of MaxAmount.
The Service Start date for the parent line item in Service PO.
The Service End date for the parent line item in Service PO.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
Integer
<=10 char.
Decimal number
<=50 char.
Decimal number
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=2000 char.
Integer
YYYYMMDD
<=1 char.
<=50 char.
Boolean
<=1024 char.
<=50 char.
<=50 char.
Integer
<=1 char.
Decimal number
<=50 char.
<=2000 char.
Decimal number
Integer
Decimal number
Decimal number
Boolean
<=50 char.
Integer
<=50 char.
Date
Date
Back to homepage
ChangePurchOrdAcctDet.csv (Export Change Purchase Order)

One record for every change purchase order line accounting split.
Column Header
ERPORDERID
ANLN1
MKNTM
AUFNR
EBELP
SAKTO
SERIAL_NO
PS_PSP_PNR
ANLN2
KOSTL
VRTKZ
AMOUNT
RECEIVINGTYPE
CHGSTATE
AcctDet.csv (Export Change Purchase Order)
ery change purchase order line accounting split.
Field Descripton
Defines the unique value of the Asset account assignment category for each line item.
Defines the percentage for the split accounting on a particular line item.
Defines the unique value of internal order account assignment category for te corresponding
line item. Ariba Buyer does not display this, because it is not mandatory for the user to enter
a value.
Defines the line number of line item for the changed Purchase Order.
Defines the unique value of the General ledger acounting type for each line item.
Defines the serial number of the line item in SAP.
Defines the unique code of the WBS Element account assignment category for the line item.
Ariba Buyer does not display this, because it is not mandatory for the user to enter a value.
Defines the sub-number of the asset account assignment category for the corresponding line
item.
Defines the unique value of the Cost center account assignment category for each line item.
Defines the amount for each line item.
• 4 (No Receipt)
Defines the split accounting state of the line item; if it is a change, the value is 2.
<=50 char.
<=50 char.
<=20 char.
<=50 char.
<=5 char.
<=50 char.
<=100 char.
<=50 char.
<=4 char.
<=50 char.
<=1 char.
Decimal number
Integer
Integer
Back to homepage
ChangePurchOrdSchdlDet.csv (Export Change Purchase Order)

One record for every change purchase order line.
Column Header
ERPORDERID
NETPR
QUANTITY
REQ_ID
DELIV_DATE
EBELP
RECEIVINGTYPE
SchdlDet.csv (Export Change Purchase Order)
ery change purchase order line.
Field Descripton
Defines the unique Purchae Order ID with its version number.
Defines the quantity for each line item to be purchased in the changed Purchase Order.
This is the Originating System Reference ID
Defines the delivery date of each line item in the changed Purchase Order.
Defines the line number of the corresponding line item in a changed Purchase Order.
• 4 (No Receipt)
<=50 char.
Decimal number
Decimal number
<=50 char.
<=50 char.
<=50 char.
Integer
Back to homepage
ChangePurchOrdDelAcct.csv (Export Change Purchase Order)

One record for every deleted accounting split on a change purchase
order (does not include accounting splits on deleted lines). If there are
no deleted splits on a change purchase order, there will be one record
Column Header
for that
SERIAL_NO
change purchase order.
PO_ITEM
ERPORDERID
DelAcct.csv (Export Change Purchase Order)
ery deleted accounting split on a change purchase
nclude accounting splits on deleted lines). If there are
on a change purchase order, there will be one record
Field Descripton
urchaseIt describes
order.the SAP serial number of each line item.
<=100 char.
<=5 char.
<=50 char.
Back to homepage
ChangePurchOrdDelItems.csv (Export Change Purchase Order)

One record for every deleted line on a change purchase order--if there
are no deleted lines on a change purchase order, there will be one
record for that change purchase order.
Column Header
ERPORDERID
PO_ITEM
PARENT_LINE_NUMBER
DelItems.csv (Export Change Purchase Order)
ery deleted line on a change purchase order--if there
es on a change purchase order, there will be one
ange purchase order.
Field Descripton
<=50 char.
<=50 char.
Integer
Back to homepage
ChangePurchOrdLineText.csv (Export Change Purchase Order)

One record for every change purchase order.
ERPORDERID
STRING
TDOBJECT
PO_ITEM
TDID
STRINGNUM
LineText.csv (Export Change Purchase Order)
ery change purchase order.
Field Descripton
Defines a string (text) for each line item in the Purchase Order.
Defines an object of the text for each line item in the Purcase Order.
Defines the line number of the line item in every Purchase Order.
Defines unique ID of the text for each line item in the Purchase Order.
Defines a string number of the text for each line item in the Purchase Order.
<=50 char.
<=255 char.
<=10 char.
<=5 char.
<=4 char.
Integer
Back to homepage
CancelPurchOrdHeader.csv (Export Cancel Purchase Order)

One record for every cancelled purchase order.
ERPORDERID
EBELN
VERSION
eader.csv (Export Cancel Purchase Order)
ery cancelled purchase order.
Field Descripton
Defines the unique Purchase Order ID with latest version number.
Defines the unique Purchase Order ID of every version for which it shows a status.
This is the a supplemental version number of the original order. Ariba Buyer implements
cancel orders by sending an updated order to the supplier, as a revision of the original order.
The order number remains the same, but there is a supplemental version number.
<=50 char.
<=50 char.
Integer
Back to homepage
ReceiptHeaderDetails.csv (Export Receipts to ERP)

One record for every receipt.
ARIBA_GRNO
APDAT
BUDAT
EBELN
BLDAT
RECVDAT
See ReceiptLineDetails.csv
tails.csv (Export Receipts to ERP)
ery receipt.
Field Descripton
Defines the unique ID of every receipt in Ariba Buyer, for which it shows a status.
Defines the date of approval of the receipt in MM/dd/yyyy HH:mm:ss ZZZZ format.
Defines the date of approval of the receipt.

Defines Purchase Order Number of the received items from an ERP.
Defines the receipt creation date.
Defines the receipt's received date in the timezone of the user. The date is in yyyyMMDD
format.
<=50 char.
MM/dd/yyyy HH:mm:ss ZZZZ
format (e.g., 03/24/2015
08:43:09 -0700)
YYYYMMDD format
<= 50 char.
YYYYMMDD format
YYYYMMDD format
Back to homepage
ReceiptLineDetails.csv (Export Receipts to ERP)

ERFMG
AMOUNTACCEPTED
ERFME
EBELP
ARIBA_GRNO
RECEIVINGTYPE
ARIBA_ITNO
EBELN
AribaPOLineNumber
See ReceiptHeaderDetails.csv
s.csv (Export Receipts to ERP)
ery receipt line item.
Field Descripton
Defines the total number of items accepted in the receipt order.
Defines the total ammount accepted for receipt in the receipt order.
Defines the unit of measure for each line item of the Purchase Order.
Defines the line number of a Purchase Order from an ERP.
Defines the unique ID of every receipt from Ariba Buyer, for which it shows a status.
Defines the unique receiving type value of the receipt item.
Defines the line number of an item in Ariba Buyer.
Defines the Purchase Order Number of the received items from an ERP.
Defines the line number of the associated item in the Purchase Order.
Decimal number
Decimal number
<=50 char.
<= 50 char.
<=50 char.
Integer
Integer
<=50 char.
Integer
Back to homepage
ReceiptHeaderExport.csv (Export Receipts)

One record for every receipt.
Id
EventStatus
Comments
Requester
ReceiptNumber
GoodsReturnTrackingNumber
ContractID
PONumber
EventDate
See ReceiptDetailExport.csv
See ReceiptAssetExport.csv
port.csv (Export Receipts)
ery receipt.
Field Descripton
A unique ID for this Receipt used to match between the header, line, asset files.
The status of the Receipt.
A string containing all the comments with date and creator information
The id of the submitter of the receipt.
The unique id of the receipt.
Goods return tracking number of rejected goods
The unique Contract ID associated with this receipt. This ID is appended to the receipts that
are directly created from a No-Release Contract Order.
The unique id of the PO this receipt is associated with.
date on which this status change occurred.

<=255 char.
<=255 char.
<=2000 char.
<=255 char.
<=50 char.
<=100 char.
<=50 char.
<=50 char.
format (e.g., 03/24/2015
08:43:09 -0700)
Back to homepage
ReceiptDetailExport.csv (Export Receipts)

Id
POAmount_Currency
AmountRejected_InBaseCurrency
NumberRejected
TotalAmountRejected
TotalAmountRejected_Currency
NumberAccepted
AmountRejected_Currency
TotalAmountAccepted_InBaseCurrency
TotalNumberAccepted
ReceivableLineNumber
AmountAccepted
TotalNumberRejected
TotalAmountAccepted
TotalAmountAccepted_Currency
UnitOfMeasure
ReturnBy
POAmount_InBaseCurrency
AmountRejected
TotalAmountRejected_InBaseCurrency
ReceiptNumber
POAmount
AmountAccepted_InBaseCurrency
AmountAccepted_Currency
ReceiptLineNumber
POQuantty
See ReceiptHeaderExport.csv
See ReceiptAssetExport.csv
ort.csv (Export Receipts)
ery receipt line item.
Field Descripton
The currency of the PO amount.
The amount rejected in base currency.
The number of items that were rejected.
The total amount rejected.
The currency of the total rejected amount.
The number of items that were accepted.
The currency of the rejected amount.
The total amount accepted in base currency.
The total number of this item that have been accepted (on all receipts for this PO).
The number of this line on the PO
The amount accepted.
The total number of this item that have been rejected (on all receipts for this PO).
The total amount accepted.
The currency of the total amount accepted.
The unit of measure for this item.
Indicates how the rejected goods are to be returned-either by replacement of goods or by
credit
The PO amount in base currency.
The amount rejected.
The total amount rejected in base currency.

The PO amount.
The amount accepted in base currency.
The currency of the amount accepted.
The number of this line on the receipt.
The quantity of items ordered.
<=255 char.
<=50 char.
Decimal number
Decimal number
Decimal number
<=50 char.
Decimal number
<=50 char.
Decimal number
Decimal number
Integer
Decimal number
Decimal number
Decimal number
<=50 char.
<=50 char.
<=20 char.
Decimal number
Decimal number
Decimal number
<=50 char.
Decimal number
Decimal number
<=50 char.
Integer
Decimal number
Back to homepage
ReceiptAssetExport.csv (Export Receipts)

One record for every item on each receipt line.
Id
TagNumber
ReceivableLineNumber
Locaton
ReceiptNumber
UnitNumber
SerialNumber
ReceiptLineNumber
See ReceiptHeaderExport.csv
See ReceiptDetailExport.csv
rt.csv (Export Receipts)
ery item on each receipt line.
Field Descripton
The tag number of the received item.
The number of this line on the PO.
The location where this item was received.
The unit number of the received item.
The serial number of the received item.
The number of this line on the receipt.
<=255 char.
<=50 char.
Integer
<=50 char.
<=50 char.
Integer
<=50 char.
Integer
Back to homepage
BudgetHeader.csv (Import Budgets)

Always only one record in this file.
Column Header
Title
See BudgetPeriods.csv
See BudgetLineItems.csv
See BudgetAllocation.csv
v (Import Budgets)
ecord in this file.
Field Descripton
A name for the overall budget. This value is visible in the budget admin UI. For the sake of
simplicity, most customers hard-code a value like "<Customer> Budget".
Always <=128 char.

Customer mapping
Back to homepage
BudgetPeriods.csv (Import Budgets)

One record for every budget period. You can define periods as weeks,
period by loading one record with an EndDate far into the future (e.g.
Column Header
AccountngPeriod
FiscalYear
StartDate
EndDate
See BudgetHeader.csv
v (Import Budgets)
ery budget period. You can define periods as weeks, months, quarters, years
one record with an EndDate far into the future (e.g., 12/31/9999).
Field Descripton
Together with FiscalYear, uniquely identifies a budget period.
Together with AccountingPeriod, uniquely identifies a budget period. This does not actually
have to be a year (e.g., if you are using one open-ended period, you can send something like
"N/A".
Start date of the budget period.
End date of the budget period.

eeks, months, quarters, years, etc., or you can define one open-ended
(e.g., 12/31/9999).

Always <=30 char.
Always <=12 char.
M/D/YYYY H:M:S <GMT offset>

Always format (e.g., "6/1/2009
23:59:59 +0530")
M/D/YYYY H:M:S <GMT offset>
Always format (e.g., "4/1/2009
00:00:00 +0530")
u can define one open-ended
Customer mapping
Back to homepage
BudgetLineItems.csv (Import Budgets)

One record for every budget line item.
Column Header
LineNumber
BudgetCode
Rank
Budget Check Disabled
CompanyCode
Internal Order
CostCenter
GeneralLedger
WBSElement
PurchaseGroup
PurchaseOrg
ProcurementUnit
Asset
SubNumber
Account
ProjectNumber
csv (Import Budgets)
ery budget line item.
Field Descripton
A line number for the budget line item. This field is required and, along with BudgetCode, is
used to tie the records in this file to the records in the BudgetAllocation.csv file. It should be
unique for every line in the file.
For the sake of simplicity, the most common approach to populating this field is sequential
numbering (e.g., if there are two line items in the budget, the value for the first line item
would be 1 and the value for the second would be 2).
A unique identifier for the budget line item. This field is required, and, along with
LineNumber, is used to tie the records in this file to the records in the BudgetAllocation.csv
file. It should be unique for every budget line item.
A number that specifies the rank of the budget code. The rank is used to determine which
budget line to use when a req line item split matches more than one budget line. The one
with the highest rank (lowest number) is used.
A boolean field that indicates whether this BudgetCode is disabled for budget check. If true,
then budget check will not be done for this BudgetCode, but will also not fail due to no
budget being found. The typical use case would be if P2X has been configured to fail budget
check when no budget is found, and there are some accounting strings that should not fail or
trigger a budget check. The default if left blank is FALSE.
References BUKRS of a company code previously defined in CompanyCode.csv. This is the

company code associated with the internal order.
References AUFNR of an internal order previously defined in InternalOrder.csv. This is the

internal order associated with the budget line item.
References KOSTL of a cost center previously defined in CostCenter.csv. This is the cost center
associated with the budget line item.
References SAKNR of a general ledger previously defined in GeneralLedger.csv. This is the
general ledger associated with the budget line item.
References POSID of a WBS element previously defined in WBSElement.csv. This is the WBS
element associated with the budget line item.
References EKGRP of a previously defined purchase group in PurchaseGroup.csv. This is the
purchase group associated with the budget line item.
References EKORG of a previously defined purchasing organization in PurchaseOrg.csv. This is
the purchase org associated with the budget line item.
References UniqueName of a purchasing unit previously defined in PurchasingUnit.csv. This is
the purchasing unit associated with the budget line item.
References ANLN1 of an asset previously defined in Asset.csv. This is the asset associated with
the budget line item.
References ANLN2 of an asset previously defined in Asset.csv. This is the sub-number of the
asset associated with the budget line item.
References UniqueName of an account previously defined in Account.csv. The account field is
not used in SAP variant.
This value refers to an existing WBSElement.ProjectNumber field.
Always Integer
Always <=256 char.
When there is a possibility of a given

accounting string matching multiple budget Integer
codes (due to wild-carding certain fields)
When P2X has been configured to fail budget

check when no budget is found for a particular Valid values are TRUE/FALSE
accounting string, but there are certain (case-insensitive)
accounting strings that should not fail that
check nor trigger an actual budget check
When loading budgets against cost elements

that are associated with company codes (e.g.,
cost centers, WBS elements, internal orders, See description
etc.)
When loading budgets against internal orders See description
When loading budgets against cost centers See description
When loading budgets against general ledgers See description
When loading budgets against WBS Elements See description
When loading budgets against purchase See description

groups
When loading budgets against purchase orgs See description
When loading purchasing-unit-specific budgets See description
When loading budgets against assets See description
When loading budgets against assets that have See description

sub-numbers defined
Customer mapping
N/A
N/A
Back to homepage
BudgetAllocation.csv (Import Budgets)

One record for every budget line item/period to which you are allocati
Column Header
BudgetCode
LineNumber
AccountngPeriod
FiscalYear
AllocatonAmt
Currency
AvailableAmt
AvailableCurrency
PercentageTolerance
csv (Import Budgets)
ery budget line item/period to which you are allocating/adjusting budget am
Field Descripton
References BudgetCode of a line item in BudgetLineItems.csv. This field, along with LineNumber, tie the records in this file to th
References LineNumber of a line item in BudgetLineItems.csv. This field, along with
BudgetCode, tie the records in this file to the records in BudgetLineItems.csv.
References AccountingPeriod of a period in BudgetPeriods.csv. This field, along with
FiscalYear, tie the records in this file to the records in BudgetPeriods.csv.
References FiscalYear of a period in BudgetPeriods.csv. This field, along with
AccountingPeriod, tie the records in this file to the records in BudgetPeriods.csv.
Total outlay for the budget period and budget code.
Currency of the allocated amount for the accumulator.
Available amount on ERP side. This will update Allocation amount with
'ExternalAvailable+Encumbered'. The system assumes the value loaded here has already
accounted for Ariba PO spend, but not Ariba in-flight requisitions.
Currency of the external available amount for the accumulator.

Percentage of the allocation by which the requisition amount can exceed before check failure.
If the tolerance is global (i.e., the same across all budgets loaded in a realm) this can be set
via system parameter and this field can be ignored.
locating/adjusting budget amounts.

If you are not loading AvailableAmt Decimal number
If you are loading AllocationAmt Must be valid currency code
If you are accounting for spend that occurred

outside of the PO in Ariba against budgets, and
doing it via budget definition files instead of Decimal number
BudgetAdjustments.csv
If you are loading AvailableAmt Must be valid currency code

If your tolerance settings can vary by budget
code; otherwise, leave blank and use the Decimal number
system-level tolerance
Customer mapping
Back to homepage
BudgetAdjustments.csv (Import Budget Adjustments)

One record for every budget line item/period to which you are adjusti
Column Header
Currency
Adjustment
BudgetCode
FiscalYear
AccountngPeriod
Comment
TransactonDate
nts.csv (Import Budget Adjustments)
ery budget line item/period to which you are adjusting budget amounts.
Field Descripton
References BudgetCode of a line item in BudgetLineItems.csv. This field, along with
LineNumber, tie the records in this file to the records in BudgetLineItems.csv.
References LineNumber of a line item in BudgetLineItems.csv. This field, along with
BudgetCode, tie the records in this file to the records in BudgetLineItems.csv.
References AccountingPeriod of a period in BudgetPeriods.csv. This field, along with
FiscalYear, tie the records in this file to the records in BudgetPeriods.csv.
References FiscalYear of a period in BudgetPeriods.csv. This field, along with
AccountingPeriod, tie the records in this file to the records in BudgetPeriods.csv.
Accounting period that the budget belongs to.
This is refered to from the BudgetPeriod.csv
Any comments for the adjustments that you are loading against the budget
Available amount on ERP side. This will update Allocation amount with
'ExternalAvailable+Encumbered'. The system assumes the value loaded here has already
accounted for Ariba PO spend, but not Ariba in-flight requisitions.
djusting budget amounts.

Customer mapping
Back to homepage
RelationType.csv (Import Relations)

One record for every relation type.
Column Header
UniqueName
Name
LeftClass
RightClass
(Import Relations)
ery relation type.
Field Descripton
Unique name for the relation type. (Sample Value: RelType1.)
The full name of the relation. (Sample Value: Company to Supplier Validation.)
The object type deemed to be the left-hand object the in the relation. This is the object that
will be filtered/validated against the object defined in RightClass. (Sample Value:
ariba.common.core.Supplier if filtering/validating suppliers by company code)
The object type deemed to be the right-hand object the in the relation. This is the object that
determines which LeftClass objects are visible/valid. (Sample Value:
"ariba..core.CompanyCode" if filtering/validating suppliers by company code)
Always <=50 char.
Always <=128 char.
Always <=256 char.
Always <=256 char.

Customer mapping
Back to homepage
PaymentHeaderExport.csv (Export Payment Requests)

One record for every reconciled invoice.
Column Header
PAYMENTID
REF_DOC_NO
COMP_CODE
GROSS_AMOUNT
GROSS_AMOUNT_ROUNDED
CURRENCY
DOC_DATE
PMNTTRMS
DIFF_INV
INVOICE_IND
PYMT_METH
ITEM_TEXT
BLINE_DATE
URL
ACCRUAL_PMNT_AMT
BLINE_DATE_ISO
BLINE_DATE_ISO_USERTIMEZONE
BLINE_DATE_USERTIMEZONE
See PaymentLineItemDet.csv
See PaymentAccountDet.csv
See PaymentDetailExport.csv
See PaymentTaxExport.csv
xport.csv (Export Payment Requests)
ery reconciled invoice.
Field Descripton
A unique identifier for the payment request document.
It defines the invoice number as refernce document number.The maximum permissible
length for this field is 16 characters.
It defines the company code of the payment.
The gross amount of the invoice.
The gross amount of the invoice rounded to the ERP precision configured in P2X.
The currency of the payment.
The invoice date.
The unique identifier of the payment terms.
The unique identifier of the supplier of the payment.
Indicates whether it is an invoice or a credit memo--if it is an invoice, this field will be set to
"X"; if it is a credit memo, this field will be null.
The payment method type used
The unique identifier of the invoice reconciliation document.
It defines the base line date of the payment.
payment URL
The tax accrual amount for the invoice.
It defines the base line date of the payment.
It defines the base line date of the payment in the requester's time zone.
It defines the base line date of the payment. The format of the date is YYYYMMDD.
<=50 char.
<=16 char.
<=50 char.
Decimal number
Decimal number
<=50 char.
YYYYMMDD
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=100 char.
Decimal number
format (e.g., 03/24/2015
08:43:09 -0700)
format (e.g., 03/24/2015
08:43:09 -0700)
YYYYMMDD
Back to homepage
PaymentLineItemDet.csv (Export Payment Requests)

One record for every reconciled invoice line item, excluding tax lines.
Column Header
PAYMENTID
TAX_CODE
POLINERECEIVINGTYPE
ITEM_AMOUNT
ITEM_AMOUNT_ROUNDED
QUANTITY
PO_UNIT
INVOICE_DOC_ITEM
PO_NUMBER
PO_ITEM
ITEM_TEXT
CATEGORY
ORDER
PO_PR_UOM
CONV_UNIT
IS_COMPOSITE
PRICE_UNIT
PBQ_DESC
See PaymentHeaderExport.csv
Det.csv (Export Payment Requests)
ery reconciled invoice line item, excluding tax lines.
Field Descripton
It defines the unique code of the tax type.
It defines the purchase order receiving type.
It defines an amount of the line item.
It defines an amount of the line item in ERP Precision.
It defines the quantity for every line item.
It defines a unit of measure.
It defines the line number of every line item.
It defines the unique ID of every purchase order for the ERP it belongs to.
It defines the line number of the corresponding line item.
This is the Line item description.
It defines the category of every line item.
It defines an ERP Purchase Order number.
Flag showing whether this line is composite or not.
<=50 char.
<=50 char.
<=50 char.
Decimal number
Decimal number
Decimal number
<=50 char.
Integer
<=50 char.
<=50 char.
<=2000 char.
Integer
<=50 char.
<=50 char.
Decimal number
(case-insensitive)
Decimal number
<=2000 char.
Back to homepage
PaymentAccountDet.csv (Export Payment Requests)

One record for every reconciled invoice line accounting split, excluding
tax lines.
Column Header
ITEM_AMOUNT
ITEM_AMOUNT_ROUNDED
WBS_ELEM
ASSET_NO
COSTCENTER
POLINERECEIVINGTYPE
QUANTITY
PO_UNIT
SERIAL_NO
INVOICE_DOC_ITEM
ORDERID
GL_ACCOUNT
TAX_CODE
PAYMENTID
CATEGORY
ORDER
PO_NUMBER
SUB_NUMBER
PO_PR_UOM
LINE_COMP_CODE
Det.csv (Export Payment Requests)
ery reconciled invoice line accounting split, excluding
Field Descripton
It defines the amount for every line item.
It defines the amount for every line item in ERP Precision.
It defines the unique code of the WBS Element account assignment category for that line
item.
It defines the unique value of the Asset account assignment category for each line item.
It defines the unique value of the Cost center account assignment category for each line item.
It defines the Purchase Order receiving type.
It defines the quantity for every line item.
It defines the unique unit of measure value.
It defines the serial number of every line item.
It defines the unique value of internal order account assignment category for that line item.
It defines the unique value of the General ledger acounting type for each line item.
It defines the unique tax type code.
It defines the category of every line item.
It defines an ERP Purchase order number.
It defines the asset Subnumber for the asset account assignemnt category for each line item.
It defines the unique value of the Company Code for the line item. This field will be
populated for non-po invoices and AllowLegalEntityCodeAtSplitLevel parameter is set to 'true'
Decimal number
Decimal number
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=100 char.
Integer
<=50 char.
<=50 char.
<=50 char.
<=50 char.
Integer
<=50 char.
<=50 char.
<=4 char.
<=50 char.
<=50 char.
Back to homepage
PaymentDetailExport.csv (Export Payment Requests)

One record for every reconciled invoice line accounting split, excluding
tax lines.
Column Header
PAYMENTID
ITEM_AMOUNT
ITEM_AMOUNT_ROUNDED
WBS_ELEM
ASSET_NO
COSTCENTER
INVOICE_DOC_ITEM
ORDERID
GL_ACCOUNT
COMP_CODE
TAX_CODE
PLANT
ITEM_TEXT
DB_CR_IND
LINE_TYPE_LOOKUP_CODE
HDR_LEVEL
PO_NUMBER
CHARGE_FLAG
Quantty
CONV_UNIT
IS_COMPOSITE
LINE_COMP_CODE
PO_PR_UOM
PRICE_UNIT
PBQ_DESC
port.csv (Export Payment Requests)
ery reconciled invoice line accounting split, excluding
Field Descripton
The amount of the accounting split.
The amount of the accounting split, rounded to the precision configured in P2X.
It defines the unique code of the WBS Element account assignment category for that line
item.
It defines the unique value of the Asset account assignment category for each line item.
It defines the unique value of the Cost center account assignment category for each line item.
It defines the unique value of internal order account assignment category for that line item.
It defines the unique value of the General ledger acounting type for each line item.
It defines the company code of the payment.
It defines the tax code.
It defines the unique code of the ship-to location for each line item.
It defines the reference line description.
The Debit/Credit Indicator. If the payment request is a debit, this field will be set to "S"; if the
payment request is a credit, this field will be set to "H".
It defines the category of line item.
It defines whether a line item is at the header level or not.
The line number of the parent line.
The quantity of the line item.
Flag showing whether this line is composite or not.
It defines the unique value of the Company Code for the line item. This field will be
populated for non-po invoices and AllowLegalEntityCodeAtSplitLevel parameter is set to 'true'

<=50 char.
Decimal number
Decimal number
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=50 char.
<=2000 char.
<=10 char.
Integer
(case-insensitive)
<=50 char.
Integer
Decimal number
Decimal number
(case-insensitive)
<=50 char.
<=50 char.
Decimal number
<=2000 char.
Back to homepage
PaymentTaxExport.csv (Export Payment Requests)

One record for every reconciled invoice tax line item.
Column Header
PAYMENTID
TAX_AMOUNT
TAX_AMOUNT_ROUNDED
TAX_CODE
REF_LINE_NUM
ITEM_TEXT
DB_CR_IND
t.csv (Export Payment Requests)
ery reconciled invoice tax line item.
Field Descripton
It defines the amount of tax.
It defines the amount of tax in ERP Precision.
It defines the tax code.
It defines the reference line number in the tax distribution vector.
It defines the reference line description.
The Debit/Credit Indicator. If the payment request is a debit, this field will be set to "S"; if the
payment request is a credit, this field will be set to "H".
<=50 char.
Decimal number
Decimal number
<=50 char.
Integer
<=255 char.
<=10 char.
Back to homepage
PreferredSupplierMap.csv (Import Preferred Supplier Mappings)
This file enables searching by preferred suppliers for Non-Catalog Item

Column Header
CommonId
MATKL
WERKS
LIFNR
CommonIdDomain
Map.csv (Import Preferred Supplier Mappings)
earching by preferred suppliers for Non-Catalog Items.

Field Descripton

CommodityCode.csv. This is the ID of the system commodity code you are mapping.
References MATKL of a material group code (i.e., ERP commodity code) previously
defined in ERPCommodityCode.csv. This is the material group that will be set when
the given company/commodity/account type is selected.
References WERKS of a plant previously defined in Plant.csv. This is the ship-to

address you want to default for the given company/commodity/account type.
The unique identifier of supplier that you want to associate with the commodity code.
This value must match a supplier defined in Supplier.csv

This is the domain of the system commodity code you are mapping.
Items.
Customer
When is this field required? Restrictons mapping
If Preferred suppliers should
be determined by UNSPSC
Commodity Code <=100 char
be determined by Material
Group <=50 char

be determined by Plant <=50 char
Always <=50 char
If UNSPSC code is
specified <=50 char
Back to homepage
BudgetPeriod.csv (Import Flex Master Data Budget Period)
The budget period is a Funds Management (FM) account assignment e

functional area. It is always used in conjunction with one or more fund
Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_BudgetPeriod
cus_ValidFrom
cus_ValidTo
(Import Flex Master Data Budget Period)
d is a Funds Management (FM) account assignment element like the fund, fu

is always used in conjunction with one or more funds.
Field Descripton
A unique identifier for the Budget Period
The Description for the Budget Period
CompanyCode for the Budget Period
Purchasing Unit for the Budget Period
Budget Period ID
Effective From Date
Effective Until Date

ment element like the fund, funds center, and
funds. Customer
Always <=128 char
If the User choices are <=50 char
required to be filtered by Must be a valid Company Code
Company Code

required to be filtered by Must be a valid PU
Purchasing Unit
<=100 char
Must be valid Date Format
Back to homepage
CommitmentItem.csv (Import Flex Master Data Commitment Item)
An element that represents the functional grouping of expenditures a

area.
Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_FMArea
cus_FiscalYear
cus_CommitmentItem
cus_ValidFrom
cus_ValidTo
cus_DescriptonLine1
cus_DescriptonLine2
cus_DescriptonLine3
cus_SuperiorCommitmentItem
m.csv (Import Flex Master Data Commitment Item)
epresents the functional grouping of expenditures and revenues within a fin

Field Descripton
A unique identifier for the CommitmentItem
The Description for the CommitmentItem
CompanyCode for the CommitmentItem
Purchasing Unit for the CommitmentItem
Funds management area to which the funds center is assigned.

Valid Fiscal Year for the Commitment Item
CommitmentItem ID
Effective From Date
Effective Until Date
The Description1 for the CommitmentItem
superordinate commitment item
m)
res and revenues within a financial management (FM)

Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
<=100 char
<=100 char
<=100 char
<=100 char
<=100 char
Back to homepage
EarmarkedFundsDocument.csv (Import Flex Master Data Earmarked F
Business transactions in Funds Management which claim already alloc

expenditures.
Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_EarmarkedFunds
cus_DocumentDate
cus_PostngDate
cus_EntryDate
cus_LastChangeDate
cus_Text
Document.csv (Import Flex Master Data Earmarked Funds Document)
tions in Funds Management which claim already allocated budget for expecte
Field Descripton
A unique identifier for the Earmarked Funds Document
The Description for the Earmarked Funds Document
CompanyCode for the Earmarked Funds Document
Purchasing Unit for the Earmarked Funds Document

ked Funds Document)
allocated budget for expected revenues or

Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
Back to homepage
EarmarkedFundsLineItem.csv (Import Flex Master Data Earmarked Fun
Document Line Items for Earmarked Funds

Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_EarmarkedFundsLineItem
cus_Item
cus_ItemText
ineItem.csv (Import Flex Master Data Earmarked Funds Line Item #)
ems for Earmarked Funds

Field Descripton
A unique identifier for the Earmarked Funds Line Item
The Description for the Earmarked Funds Line Item
CompanyCode for the Earmarked Funds Line Item
Purchasing Unit for the Earmarked Funds Line Item

d Funds Line Item #)
Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
<=100 char
Back to homepage
FMArea.csv (Import Flex Master Data FM Area)
The Funds Management Area is the organizational unit within an orga

funds management, budgeting, and budget execution
Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_FMArea
cus_FMAreaText
Amount
ort Flex Master Data FM Area)
ement Area is the organizational unit within an organization, used to represe

nt, budgeting, and budget execution
Field Descripton
A unique identifier for the FM Area
The Description for the FM Area
CompanyCode for the FM Area
Purchasing Unit for the FM Area

organization, used to represent a closed system for
Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
Decimal Number
Back to homepage
FunctionalArea.csv (Import Flex Master Data Functional Area)
The functional area maps the functional structure (such as public safe
expenditures of an organization (FM area). It describes how the funds
Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_FunctonalArea
cus_ValidFrom
cus_ValidTo
v (Import Flex Master Data Functional Area)
ea maps the functional structure (such as public safety, town planning and so
n organization (FM area). It describes how the funds are used.
Field Descripton
A unique identifier for the Functional Area
The Description for the Functional Area
CompanyCode for the Functional Area
Purchasing Unit for the Functional Area

safety, town planning and so on), especially the
unds are used. Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char

Back to homepage
Fund.csv (Import Flex Master Data Fund)
Funds represent financial resources that are provided for a specific pu

enables the exact source of the funds to be determined.
Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_FMArea
cus_Fund
cus_ValidFrom
cus_ValidTo
cus_Descripton
Flex Master Data Fund)
financial resources that are provided for a specific purpose by a sponsor and
source of the funds to be determined.
Field Descripton
A unique identifier for the Fund
The Description for the Fund
CompanyCode for the Fund
Purchasing Unit for the Fund

fic purpose by a sponsor and managed separately. This
Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
<=100 char
Back to homepage
FundedProgram.csv (Import Flex Master Data Funded Program)
Funded programs are programs within Funds Management (FM) with

Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_FMArea
cus_FundedProgram
cus_ValidFrom
cus_ValidTo
cus_Descripton
sv (Import Flex Master Data Funded Program)
are programs within Funds Management (FM) with an operational purpose

Field Descripton
A unique identifier for the Funded program
The Description for the Funded program
CompanyCode for the Funded program
Purchasing Unit for the Funded program

with an operational purpose and defined time frame.
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
<=100 char
Back to homepage
FundsCenter.csv (Import Flex Master Data Funds Center)
Funds Center represents the organizational areas of responsibility for

Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_FMArea
cus_FiscalYear
cus_FundsCenter
cus_ValidFrom
cus_ValidTo
cus_Descripton
Import Flex Master Data Funds Center)
resents the organizational areas of responsibility for budgetary monitoring an

Field Descripton
A unique identifier for the Funds Center
The Description for the Funds Center
CompanyCode for the Funds Center
Purchasing Unit for the Funds Center

y for budgetary monitoring and reporting
Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
<=100 char
<=100 char
Back to homepage
Grant.csv (Import Flex Master Data Grant)
Grant represents Fund Grant Programs

Column Header
UniqueName
Name
CompanyCode
PurchasingUnit
cus_Grant
cus_ValidFrom
cus_ValidTo
cus_Sponsor
cus_Descripton
cus_GrantType
cus_GrantTypeDescripton
cus_AwardType
cus_AwardTypeDescripton
Flex Master Data Grant)
Fund Grant Programs

Field Descripton
A unique identifier for the Funds Center
The Description for the Funds Center
CompanyCode for the Funds Center
Purchasing Unit for the Funds Center

Customer
Always <=128 char
Company Code

Purchasing Unit
<=100 char
<=100 char
<=100 char
<=100 char
<=100 char
<=100 char
<=100 char
Back to homepage
GLIndicator.csv (Import GL Indicators for Advance Payment)
Column Header
LTEXT
UMSKZ
mport GL Indicators for Advance Payment)
Field Descripton
The name of the ERP GL indicator
The unique identifier of the ERP GL indicator
Customer
Always
Always <=50 char
Back to homepage
ChargeType.csv (Import Charge Types)
Column Header
UniqueName
ANChargeName
Description
Name
mport Charge Types)
Field Descripton
A unique identifier for the charge
The unique name used for the charge type in Ariba Network. If this value is not
specified during the import operation, the Unique Name specified for the charge type
is used as its AN Charge Name.
Description of the charge type
user visible Name for the charge
Customer
Always <=50 char
Always <=50 char

Back to homepage
TaxType.csv
(Import Tax Types)
Column Header
UniqueName
Name
Category
Name
s)
Field Descripton
A unique identifier for tax type.
Name of the tax type. This is displayed on the user interface.
Integer value to specify the category of tax type. '2' for indirect taxes and '64' for
Withholding tax
user visible Name for the charge
Customer
Always <=50 char
Always
Back to homepage
TaxComponent.csv (Import Tax Components)
Column Header
UniqueName
InternalOrder
GLAccount
Project_WBS
Plant
Country
Asset
AccountCategory
CostCenter
CompanyCode
IsDeductible
EffectiveDate
TaxRate
AppliedAs
AbatementPercent
Description
TaxType
Name
ExpiryDate
State
v (Import Tax Components)
Field Descripton
unique name for the tax component. which can be a combination of the name country
and rate so that it can be maintained easily. This holds only for import/export as
components created in UI have a system generated unique name
The unique internal identifier of Internal Order for Accounting details in the tax
component
The unique internal identifier of GL Account field for Accounting details in the tax
component
The unique internal identifier of Project/WBS for Accounting details in the tax
component
The unique internal identifier of a plant. This value must match a plant defined in the
Plant.csv file. Specify this value if you want to apply this tax component only on line
items from the selected plant.
The country for which the tax code is applicable. The field is mapped to the uniqe
name field of the country object
The unique internal identifier of Asset for Accounting details in the tax component
The unique internal identifier of Account Category for Accounting details in the tax
component
The unique internal identifier of Cost Center for Accounting details in the tax
component
The unique internal identifier of CompanyCode for Accounting details in the tax
component
Flag which says is a tax component is deductible, if it is deductible then the
accounting information is taken from the tax component
The date from which the tax component/tax becomes effective
Rate of tax applicable for the tax component. This value must be negative for
withholding taxes.
Mode in which the tax component is applied eg. percent/perunit Valid values are 0
and 1. 0 = percent and 1 = perunit. This value must be 1 for withholding taxes as they
can only be applied as a percentage.
Percentage of Amount on which the tax rate has to be applied. There are some cases
in which tax is not applied on the 100% of the amount but may be applied on partial
amount. This field holds that percentage. When left blank or entered as 0, the value is
defaulted to 100%
The description for the tax component.
The unique internal identifier of a Taxtype. This value must match a plant defined in
the Taxtype.csv file. This field is not editable during update
A user-visible name for the tax component which will be only the type of the tax so
that it is understandable by the user.
The date by which the tax component expires
State in which the tax code is applicable
Customer
Always <=50 char
<=50 char
<=50 char
<=50 char
<=50 char
<=50 char
<=50 char
<=50 char
<=50 char
<=50 char
Must be valid Date Format (E.g. 09/09/2014)
<=50 char
Must be valid Date Format (E.g. 09/09/2014)

<=50 char
Back to homepage
TaxCodeHeader.csv (Import Tax Codes)
Column Header
LAND1
MWSKZ
TEXT1
Name
State
sv (Import Tax Codes)
Field Descripton
The unique internal identifier of the country where the tax code is located.
The unique internal identifier of the tax code.
Descritpion for the tax code.
A user-visible name for the tax code.
State for which the tax code is applicable if it includes state level taxes
Customer
<=50 char
Always <=50 char
<=50 char
Back to homepage
TaxCodeDetails.csv (Import Tax Codes)
Column Header
Component
AppliedOn
Sequence
MWSKZ
LAND1
v (Import Tax Codes)
Field Descripton
The unique name of the Tax Component. Maps to the Unique name field of the
TaxComponent cluster root
The amount on which the tax rate is applied. The value of this field must be Quantity if
the tax is applied per unit or it must be BaseAmount, NetAmount, or a valid formula
using defined sequences if the tax is applied as a percentage.
The sequence in which tax components are applied to a line item to calculate tax.
Every tax component should have a unique Order, which should be one or more
upper-case Latin letters. For example, A, B, C, or AA, AB, ZZ.
This value must match the MWSKZ column in the TaxCodeHeader.csv file.
The unique internal identifier of the country where the tax code is located.
Customer
Always <=50 char
Always <=250 char
Always <=2 char
Always <=50 char

Always
Back to homepage
TaxCodeLookupFieldMapping.csv (Import Tax Code Lookup Field Map)
Column Header
LineItemType
FieldName
DottedFieldPath
eldMapping.csv (Import Tax Code Lookup Field Map)
Field Descripton
Line item type for which the tax code lookup field mapping is required. Valid values
are ariba.purchasing.core.ReqLineItem, ariba.purchasing.core.InvoiceLineItem, and
ariba.purchasing.core.InvoiceReconciliationLineItem.
Field name specified in the Tax Code Lookup
Dotted field path for the line item field, which is to be mapped to the tax code lookup
field
Map)
Customer
Always <=50 char
Always <=50 char

Always <=100 char
Back to homepage
WHTLookupFieldMapping.csv (Import Tax Code Lookup Field Map for
Column Header
LineItemType
FieldName
DottedFieldPath
Mapping.csv (Import Tax Code Lookup Field Map for Withholding Taxes)
Field Descripton
Line item type for which the withholding tax code lookup field mapping is required.
Valid values are 'ariba.invoicing.core.InvoiceLineItem',
'ariba.invoicing.core.InvoiceReconciliationLineItem'
Field name specified in the Tax Code Lookup
Dotted field path for the line item field, which is to be mapped to the tax code lookup
field
p for Withholding Taxes)
Customer
Always <=50 char
Always <=50 char

Always <=100 char
Back to homepage
TaxRateLookupByTaxCode.csv (Import Tax Rates By Tax Code Lookup)
Column Header
Plant
Country
TaxCode
EffectiveDate
Rank
TaxRate
TaxType
TaxCode.csv (Import Tax Rates By Tax Code Lookup)
Field Descripton
The unique internal identifier of a plant. This value must match a plant defined in the
Plant.csv file.
The country for the tax code.
The unique internal identifier of a tax code. This value must match a tax code defined
in the TaxCode.csv file.
The date at which the tax rate becomes effective.
A number that indicates the rank of the tax rate. The rank is used to determine which
tax rate to use when a line item matches more than one tax rate. The tax rate with the
highest rank (lowest number) is used.
A number that indicates the tax rate.
The unique internal identifier of a tax type. This value must match a tax type defined
in the TaxTypeMap.csv file.
kup)
Customer
To determine tax rates by <=50 char
ShipTo
Always <=50 char
Always <=100 char
Always
Always
Always
Always <=50 char
Back to homepage
DocumentType.csv (Import Document Types for Advance Payment)
Defines the ERP document types that can be used for advance payme
Column Header Field Descripton When is this field required?
LineItemType LTEXT
FieldName BLART Always
s for Advance Payment)
e used for advance payments

Customer
Restrictons mapping
<=50 char
Back to homepage
GLIndicator.csv (Import GL Indicators for Advance Payment)
Column Header
LTEXT
UMSKZ
mport GL Indicators for Advance Payment)
Field Descripton
The name of the ERP GL indicator
The unique identifier of the ERP GL indicator
Customer
Always
Always <=50 char
Back to homepage
AdvancePaymentExport.csv (Export Advance Payments)
Export advance payments for integrations with external systems or ER

Column Header Field Descripton
The unique identifier of the ERP GL indicator of
GeneralLedger the advance payment
Amount of the advance payment in the user's
Amount currency
The unique identifier of the company code for the
purchase order associated with the advance
CompanyCode payment
The unique identifier of the ERP document type of
DocumentType the advance payment
The unique identifier for the payment method by
Payment Method which the advance payment is made
The unique identifier of the supplier to which the
Supplier advance payment is made
Unique identifier of the purchase order for which
Order ID the advance payment is created
Amount of the advance payment, converted to the
Amount_InBaseCurrency site base currency
Unique identifier of the advance payment
Advance Payment ID document
Payment Due Date The advance payment due date
Currency Currency being used by the user
Title Title or name of the advance payment document
Payments)
h external systems or ERP

Customer
Format mapping
<=50 char
Decimal number
<=50 char
<=50 char
<=50 char
<=50 char
<=50 char
Decimal number
<=50 char
<=50 char
<=128 char
Back to homepage
AdvancePaymentIDImport.csv (Import Advance Payment ID)
Imports ERP Advance payment ID for the advance payment successful

The unique identifier of the advance payment
AdvancePayment_ID document
The unique identifier of the payment request
ERP_Payment_ID created in the ERP for the advance payment
ce Payment ID)
ance payment successfully created in external system.

Customer
When is this field required? Format mapping
Always <=50 char
<=50 char
Back to homepage
AdvancePaymentErrorImport.csv
(Import Advance Payment Errors)
Imports ERP Advance payment ID for the advance payment successful

DATETIME2 The date of creation of the error record.
MESSAGE The description of the error.
MSGNR It defines the error number.
FLDNAME It defines a field name having an error.
MSGID It defines an error message ID.
The unique identifier of the advance payment
ADVANCEPAYMENTID document.
NUMINSET The number of error records in a batch.
The type of the transaction for which the error
TYPE was generated
ance payment successfully created in external system. Customer
Always Must be a valid Date
<=3 char
<=35 char
<=20 char
Always <=50 char
Always
<=50 char
Back to homepage
CancelAdvancePaymentIDImport.csv (Import Cancel Advance Paymen
Imports advance payments canceled in external system or ERP.
AdvancePayment_ID The date of creation of the error record.

ERP_Payment_ID The description of the error.
Cancel Advance Payment ID)
nal system or ERP.
When is this field required? Format Customer mapping

Always <=50 char
<=50 char
Back to homepage
CancelAdvancePaymentExport.csv (Export Cancel Advance Payments)
Export advance payment cancelations to external systems or ERP

Title Title or name of the advance payment document
Unique identifier of the advance payment
Advance Payment ID document
ERP_Payment_ID created in the ERP for the advance payment
Export Cancel Advance Payments)
ns to external systems or ERP

<=128 char
<=50 char
<=50 char
Back to homepage
AdvancePaymentRemittance.csv (Import Advance Payment Remittanc
Imports payments made against advance payments in external system

Currency Currency being used by the user
The amount the ERP specified for the advance
Amount payment in the user's currency
The unique identifier of the remittance document
DocID in the ERP
ERPRequestID created in the ERP for the advance payment
ance Payment Remittance)
ments in external system.

Customer
<=50 char
Decimal Number
Always <=512 char
Always <=512 char

Back to homepage
TaxCodeLookup.csv (Import Tax Code Lookups)
Column Header
CommodityCode
ShipFromCountry
ShipToCountry
SupplierLocation
TaxCode
Description
EffectiveDate
ExpiryDate
IsAccrual
PurchasingUnit
Rank
ShipFromState
ShipToState
ContactID
sv (Import Tax Code Lookups)
Field Descripton
The unique internal identifier of an ERP commodity code. This value must match an
ERP commodity code defined in ERPCommodityCode.csv.
The country from which the item is shipped.
The country to which the item is shipped.
The unique internal identifier of a Supplier location. This value must match the
UniqueName of the Supplier Locaiton defined in SupplierLocation.csv.
Supplier Locations are uniquely identified by UniqueName + ContactId.
The unique internal identifier of a tax code. This value must match a tax code defined
in TaxCode.csv.
a detailed description about the tax code lookup
The date on which the tax code lookup criteria becomes effective. This field can help
the tax admin to load the lookup data in prior and mention a effective date
The date on which the tax code lookup criteria expires

A Boolean value that indicates whether the tax code applies to items meant for
accrual.
The unique internal identifier of a purchasing unit. This value must match a
purchasing unit defined in PurchasingUnit.csv.
A number that specifies the rank of the tax code. The rank is used to determine which
tax code to use when a line item matches more than one tax code. The tax code with
the highest rank (lowest number) is used.
If there are custom columns used to define the lookup of a tax code then Rank should
be used to make the combination unique for the lookup to function accurately
The state from which the item is shipped.
The state to which the item is shipped.
Second part of the unique internal identifier of a Supplier location. This value must
match the ContactID column of the Supplier Locaiton defined in SupplierLocation.csv.
Supplier Locations are uniquely identified by UniqueName + ContactId.
Customer
If Tax is determined based on ERP <=50 char
Material Group
If Tax is determined based on <=50 char
ShipFrom
If Tax is determined based on ShipTo <=50 char
If Tax is determined based on <=50 char

Ordering Location
Always <=50 char
<=50 char
Determines tax based on relative

priority amongst multiple matches,
lower rank ones will be picked.
<=50 char
<=50 char
<=50 char
Back to homepage
ClosePurchOrdLineDetails.csv (Export Purchase Order Close Status)
Column Header
PARENT_LINE_NUMBER
SAP_PR_ITEM
SAP_PO_NO
VERSION
PREQ_ITEM
ARIBA_PO_ITEM
SAP_PO_ITEM
CLOSE_STATE
SAP_PR_NO
ARIBA_PO_NO
ARIBA_PR_ITEM
REQ_ID
ARIBA_PR_NO
eDetails.csv (Export Purchase Order Close Status)
Field Descripton
This is the line number of the requisition line item associated with this order line item
that is part of PO being cancelled.
Line number of the parent of this line item. This could apply for charge line items or
tax line items
Carries the ERP Req line number

s)
Customer
Restrictons mapping
Back to homepage
Column Header
PARENT_LINE_NUMBER
SAP_PR_ITEM
SAP_PO_NO
VERSION
PREQ_ITEM
ARIBA_PO_ITEM
SAP_PO_ITEM
CLOSE_STATE
SAP_PR_NO
ARIBA_PO_NO
ARIBA_PR_ITEM
REQ_ID
ARIBA_PR_NO
Field Descripton
This is the line number of the requisition line item associated with this order line item
that is part of PO being cancelled.
Line number of the parent of this line item. This could apply for charge line items or
tax line items
Carries the ERP Req line number

s)
Customer
Restrictons mapping
Back to homepage
Column Header
SAP_PO_NO
ARIBA_PO_NO
Field Descripton
This column contains the unique ERP PO identifier

Eg., 4000034567
This column contains the unique Ariba PO identifier, along with the version number.
E.g., EP12-V3
s)
Customer
Restrictons mapping
Back to homepage
PurchaseOrderCloseStatusItemImport.csv (Import Purchase Order Clo
Column Header
ARIBA_PO_ITEM
ARIBA_PO_NO
oseStatusItemImport.csv (Import Purchase Order Close Status)
Field Descripton
This column contains the line number of the PO item that needs to be closed out
Eg., 2
This column contains the unique Ariba PO identifier, along with the version number.
E.g., EP12-V3
r Close Status)
Restrictons Customer mapping

Back to homepage
DocumentType.csv (Import Document Types for Advance Payment)
Column Header
BLART
LTEXT
v (Import Document Types for Advance Payment)
Field Descripton
This column contains the unique name of the ERP Document type that you want to use in
Advance payment transaction.
This column contains the user friendly name of the ERP Document type that you want to use
in Advance payment transaction.
nt)
<=50 char
Back to homepage
AdvancePaymentCancelReasonCodesImport.csv (Import Advance Paym
Column Header
REASON
ALTERNATE_POSTING
TEXT
CancelReasonCodesImport.csv (Import Advance Payment Cancellation Reaso
Field Descripton
This column contains the Reason code for the cancellation of the advance payment.
This column contains indicates whether the reason code requires posting code
This column contains the user friendly text that describes the reason for cancelling the
advance payment
e Payment Cancellation Reasons)
<=5 char
Boolean
<=250 char
Back to homepage
AdvancePaymentErrorImport.csv (Import Advance Payment Errors)
Column Header
DATETIME2
MESSAGE
MSGNR
FLDNAME
MSGID
ADVANCEPAYMENTID
NUMINSET
TYPE
ErrorImport.csv (Import Advance Payment Errors)
Field Descripton
This column contains the date of creation of the error record
This contains the error message that ERP sends back to P2P whenever the Advance payment
fails in ERP
This column contains the error number sent in from ERP
This column indicates the field name that poses a problem in loading the Advance payment
into Ariba
This columns defines the message id from ERP to Ariba
This column carries the unique id of the advance payment that errored out in ERP
The number of error records in a batch.
This column indicates the type of the transaction for which the error was generated
s)
Date
<=3 char
<=35 char
<=20 char
<=50 char
<=50 char
Back to homepage
AdvancePaymentIDImport.csv (Import Advance Payment ID)
Column Header
AdvancePayment_ID
ERPPostingDate
ERP_Payment_ID
FISCALYEAR
IDImport.csv (Import Advance Payment ID)
Field Descripton
This column carries the unique identifier of the advance payment document in Ariba
This column is the date of posting a advance payment document in ERP.
This column is the ERP unique identifier of the advance payment request created in the ERP
This column indicates the financial year of the advance payment transaction.
<=50 char
Date
<=50 char
Integer
Back to homepage
CancelAdvancePaymentIDImport.csv (Import Cancel Advance Paymen
Column Header
ADVANCEPAYMENTID
ERPPAYMENTID
FISC_YEAR
ymentIDImport.csv (Import Cancel Advance Payment ID)
Field Descripton
This column carries the unique identifier of the advance payment document in Ariba
This column carries the unique identifier of the advance payment document in ERP
This column indicates the financial year of the advance payment transaction.
yment ID)
<=50 char
<=50 char
Integer
Back to homepage
CancelAdvancePaymentErrorImport.csv (Import Cancel Advance Paym
Column Header
DATETIME2
MESSAGE
MSGNR
FLDNAME
MSGID
ADVANCEPAYMENTID
NUMINSET
TYPE
ymentErrorImport.csv (Import Cancel Advance Payment Errors)
Field Descripton
This column contains the date of creation of the error record
This contains the error message that ERP sends back to P2P whenever the Advance payment
fails in ERP
This column contains the error number sent in from ERP
This column indicates the field name that poses a problem in loading the Advance payment
into Ariba
This columns defines the message id from ERP to Ariba
This column carries the unique id of the advance payment that errored out in ERP
The number of error records in a batch.
This column indicates the type of the transaction for which the error was generated
Payment Errors)
Date
<=3 char
<=35 char
<=20 char
<=50 char
Integer
<=50 char
Back to homepage
AdvancePaymentRemittance.csv (Import Advance Payment Remittanc
Column Header
Currency
Amount
DocID
ERPRequestID
Remittance.csv (Import Advance Payment Remittance Information)
Field Descripton
This column represents the currency of the advance payment amount
This column carries the ERP amount specified for the advance payment
This column represents the unique identifier of the remittance document in the ERP
The unique identifier of the payment request created in the ERP for the advance payment
ttance Information)
<=50 char
<=512 char
<=512 char
Back to homepage
AdvancePaymentRemittanceDetail.csv (Import Advance Payment Rem
Column Header
Currency
Amount
DocID
ERPRequestID
DocumentLineNumber
ERPRequestLineNumber
RemittanceDetail.csv (Import Advance Payment Remittance Information)
Field Descripton
This column represents the currency of the advance payment amount
This column carries the ERP amount specified for the advance payment
This column represents the unique identifier of the remittance document in the ERP
The unique identifier of the payment request created in the ERP for the advance payment
This column contains the line number for Advance payment lineitem remittance
This column represents the unique id for advance payment line number
Remittance Information)
<=50 char
<=512 char
<=512 char
Integer
Integer
Back to homepage
Task Name Task Description Data File Name File Column Name
Associates demand holding rule

with commodity codes. If you have
to define Line Type it should be
Catalog or Non Catalog along with
Import Demand commodity code and additional DemandHoldingRu
Holding Rules configuration rules. le.csv
UniqueName
DefinitionLine
CommodityCodeD
omain
CommodityCodeV
alue
Ranking
HasContract
LineType
Supplier
PurchasingUnit
AutoAggregation
Description
LineLevelThreshol
d
LineLevelThreshol
dCurrency
ConditionValue1
ConditionValue2
ConditionValue3
ConditionValue4
ConditionValue5
ConditionValue6
ConditionValue7
ConditionValue8
ConditionValue9
ConditionValue10
New File Column Field Name Field Description Data Type
A unique internal ID generated for

each holding rule during creation.
UniqueName UniqueName Do not modify the value. String
A boolean that defines the condition

fields that are used to determine the
holding rules for the commodity
code. You can only have one
definition line in your import file. To
indicate a definition line, set
DefinitionLine DefinitionLine DefinitionLine to YES. Boolean
The commodity code domain for the

CommodityCodeD system commodity code you specify
omain CommodityCode.Domain in the CommodityCode field. String
CommodityCodeV The system commodity code of the
alue CommodityCode.UniqueName item that needs to be held. String
An integer that determines how to

rank two demand holding rules for
the same commodity code. If a
purchase order line matches two or
more rules for the same commodity
code, the rule with the lowest
Ranking value is used. If left blank,
Ranking will be defaulted to 0. If two
rules for the same commodity code
with the same ranking value apply,
Ranking Ranking the result is random. Integer
Specifies whether a line item has a
HasContract HasContract contract associated with it. Boolean
Line type of the line item. The value
of this field can be 'Catalog' or 'Non
LineType LineType Catalog'. String
Supplier ID of the supplier of the line
Supplier Supplier.UniqueName item. String
The unique internal identifier of a
purchasing unit. This value must
match a purchasing unit defined in
PurchasingUnit ProcurementUnit.UniqueName PurchasingUnit.csv. String
Specifies whether the line item
should be marked for auto-
AutoAggregation AutoAggregation aggregation. Boolean
A user-visible description of the
holding rule mapping. This text
appears in the Description column
on the Demand Holding Rule page
Description Description in Ariba Administrator. String
The upper threshold value for the
line level amount. A line item is held
LineLevelThreshol if its amount is equal to or greater
d Amount.Amount than this threshold amount. BigDecimal
LineLevelThreshol The currency for the
dCurrency Amount.Currency.UniqueName LineLevelThreshold amount. String
For a definition line, enter the dotted

field path starting with Requisition,
for example:
Requisition.ProcurementUnit.Unique
Name. For rule lines,
ConditionValue1 contains the actual
value to use in testing if the rule
applies for ConditionValue1, for
example: 1000 (which means apply
this rule if the commodity code
matches and the
ConditionValue1 ConditionValue1 Name = 1000. String

for example:
matches and the

for example:
matches and the
for example:
matches and the

for example:
matches and the

for example:
matches and the
for example:
matches and the

for example:
matches and the

for example:
matches and the
for example:
ConditionValue10 contains the
actual value to use in testing if the
rule applies for ConditionValue10,
for example: 1000 (which means
apply this rule if the commodity
code matches and the
String Length Restrictions Sample Values Required Allow Null
50 DHR1001 true No
false No
50 unspsc false
100 44112002 false
0 true No
false false Yes
30 Catalog false Yes
50 Dell false
50 US005 false
false false Yes

50 Calendars false Yes
0 false
50
200 false Yes
200 false Yes
200 false Yes

200 false Yes
200 false Yes
200 false Yes

200 false Yes
200 false Yes
200 false Yes

200 false Yes
Reference To FieldReference To File
Back to homepage
Associates demand assignment rule

with commodity codes. If you have
to define Line Type it should be
Import Assignment Catalog or Non Catalog along with
Rules for Demand commodity code and additional DemandAssignme
Aggregation configuration rules. ntRule.csv
UniqueName
DefinitionLine
CommodityCodeD
omain
CommodityCodeV
alue
Ranking
HasContract
LineType
Supplier
PurchasingUnit
AssignTo
AssignToPassword
Adapter
Description
ConditionValue1
ConditionValue2
ConditionValue3
ConditionValue4
ConditionValue5
ConditionValue6
ConditionValue7
ConditionValue8
ConditionValue9
ConditionValue10

each assignment rule during
UniqueName UniqueName creation. Do not modify the value. String

assignment rules for the commodity
code. You can only have one
definition line in your import file. To
indicate a definition line, set
DefinitionLine DefinitionLine DefinitionLine to YES. Boolean
The commodity code domain for the

CommodityCodeD system commodity code you specify
omain CommodityCode.Domain in the CommodityCode field. String
CommodityCodeV The system commodity code of the
alue CommodityCode.UniqueName item that needs to be held. String
An integer that determines how to

rank two demand assignment rules
for the same commodity code. If a
purchase order line matches two or
more rules for the same commodity
code, the rule with the lowest
Ranking value is used. If left blank,
Ranking will be defaulted to 0. If two
rules for the same commodity code
with the same ranking value apply,
Ranking Ranking the result is random. Integer
Specifies whether a line item has a
HasContract HasContract contract associated with it. Boolean
Line type of the line item. The value
of this field can be 'Catalog' or 'Non
LineType LineType Catalog'. String
Supplier ID of the supplier of the line
Supplier Supplier.UniqueName item. String
The unique internal identifier of a
purchasing unit. This value must
match a purchasing unit defined in
PurchasingUnit ProcurementUnit.UniqueName PurchasingUnit.csv. String
The Assignment Rule which you
AssignTo AssignTo.UniqueName want to associate with whom. String
AssignToPassword
Adapter AssignTo.PasswordAdapter The PasswordAdapter for the User. String
assignment rule mapping. This text
appears in the Description column
on the Demand Holding Rule page
Description Description in Ariba Administrator. String

for example:
matches and the

for example:
matches and the

for example:
matches and the
for example:
matches and the

for example:
matches and the

for example:
matches and the
for example:
matches and the

for example:
matches and the

for example:
matches and the
for example:
ConditionValue10 contains the
actual value to use in testing if the
rule applies for ConditionValue10,
for example: 1000 (which means
apply this rule if the commodity
code matches and the
50 DHR1001 true No
false No
50 unspsc false
100 44112002 false
0 true No
false false Yes
30 Catalog false Yes
50 Dell false
50 US005 false
255 cnoll false

50 PasswordAdapter1 false
200 false Yes
200 false Yes
200 false Yes

200 false Yes
200 false Yes
200 false Yes

200 false Yes
200 false Yes
200 false Yes

200 false Yes
Back to homepage
Associates demand aggregation
rule. If you have to define
Import Demand CompanyCode along with ShipTo DemandAggregati
Aggregation Rules and DeliverTo configuration rules. onRule.csv
UniqueName
DefinitionLine
CompanyCode
Description
ShipTo
DeliverTo
Supplier
SupplierLocation
ConditionValue1
ConditionValue2

each demand aggregation rule
during creation. Do not modify the
UniqueName UniqueName value. String

demand aggregation rules. You can
only have one definition line in your
import file. To indicate a definition
DefinitionLine DefinitionLine line, set DefinitionLine to YES. Boolean
Unique internal identifier for the
CompanyCode CompanyCode.UniqueName CompanyCode. String
demand aggregation rule mapping.
This text appears in the Description
column on the
Description Description DemandAggregationRule. String
Enable or disable ShipTo as part of
grouping associate with the demand
aggregation rule. It should be either
ShipTo ShipTo true or false. Boolean
Enable or disable DeliverTo as part
of grouping associate with the
demand aggregation rule. It should
DeliverTo DeliverTo be either true or false. Boolean
Enable or disable Supplier as part of
grouping associate with the demand
aggregation rule. It should be either
Supplier Supplier true or false. Boolean
Enable or disable SupplierLocation
as part of grouping associate with
the demand aggregation rule. It
SupplierLocation SupplierLocation should be either true or false. Boolean
for example:
ConditionValue1 contains the TRUE
or FALSE value to use in testing if
the rule applies for ConditionValue1,
for example: the
ConditionValue1 ConditionValue1 Name = TRUE. String

for example:
ConditionValue1 contains the TRUE
or FALSE value to use in testing if
the rule applies for ConditionValue1,
for example: the
ConditionValue2 ConditionValue2 Name = TRUE. String
50 AGGR001 true No
false No
50
false false Yes
false false Yes
false false Yes
false false Yes

200 false Yes
200 false Yes


Procurement - Integration Tracker - SAP Variant

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Procurement - Integration Tracker - SAP Variant

Uploaded by

Copyright:

Available Formats

File Name Task

PurchasingUnit.csv Import Purchasing Units

Import Currency Conversion

POConditions.csv Import PO Conditions

AccountType.csv Import Account Types

ItemCategory.csv Import Item Categories

AccountCategory.csv Import Account Categories

CompanyCode.csv Import Company Codes

GeneralLedger.csv Import General Ledgers

Import Account Category Field

CostCenter.csv Import Cost Centers

InternalOrder.csv Import Internal Order Codes

Import Company Code Internal

WBSElement.csv Import WBS Elements

Asset.csv Import Assets

Network.csv Import Networks

ActivityNumber.csv Import Activity Numbers

Plant.csv Import Plants Data

Import Plant to Purchase

PurchaseGroup.csv Import Purchase Groups

IncoTerms.csv Import Incoterms

Import Supplier Data

Import Remittance Location Data

Import Purchase Organization to

Import Preferred Supplier

PunchinGroup.csv Import Punchin Groups

CustomGroup.csv Import Custom Groups

Import Group To Child Group

Import User Data (Consolidated

Import User to Group Mapping

Import Payment Terms Data

PaymentMethodType.csv Import Payment Method Types

Import Commodity Code/Import

Import Classification Code

ERPCommodityCode.csv Import ERP Commodity Codes

Import ERP Commodity to

UnitsOfMeasure.csv Import Units Of Measure

UnitsOfMeasureMap.csv Import Unit Of Measure Mapping

TaxType.csv Import Tax Types (New)

ChargeType.csv Import Charge Types (New)

TaxComponent.csv Import Tax Components (New)

TaxCodeHeader.csv Import Tax Codes (New)

TaxCodeDetails.csv Import Tax Codes (New)

TaxCodeLookup.csv Import Tax Code Lookups (Both)

Import Tax Code Lookup Field

Import Tax Code Lookup Field

BudgetHeader.csv Import Budgets in ZIP File Format

BudgetAdjustments.csv Import Budget Adjustments

Import Flex Master Data Budget

Import Flex Master Data

Import Flex Master Data

FMArea.csv Import Flex Master Data FM Area

Import Flex Master Data

Fund.csv Import Flex Master Data Fund

Import Flex Master Data Funded

Import Flex Master Data Funds

Grant.csv Import Flex Master Data Grant

Import Document Types for

Import GL Indicators for Advance

Import Advance Payment Status

Import Cancel Advance Payment

RelationType.csv Import Relations