Anda di halaman 1dari 68

Common File Name

CurrencyConversionRate.csv
Suppliers

SupplierConsolidated.csv
Users and Groups

CustomGroup.csv

UserConsolidated.csv

GroupConsolidated.csv

CommodityCode.csv
Commodites / UOM

ClassificationCodeMap.csv
Commodites /
ERPCommodityCode.csv

UnitsOfMeasure.csv
Task

Import Currency Conversion Rates

Import Supplier Data (Consolidated File)

Import Custom Groups

Import User Data (Consolidated File)

Import User to Group Mapping Data


(Consolidated File)

Import Commodity Code/Import Commodity


Code Hierarchy

Import Classification Code Relationships


Import ERP Commodity Codes

Import Units Of Measure


File Descripton

Customer-defined conversion rates between currencies.

This file defines the first layer of the Ariba supplier hierarchy, the top-level vendor
information.

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.

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 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.

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.
Procurement Strategic Spend
When Is This Task Needed? Suite Sourcing Analysis UI Alternative

When transacting in multiple currencies Y Y Y N

When maintaining suppliers via file instead of or in


addition to via UI Y Y N Y

When using custom groups and maintaining via file


instead of or in addition to via UI (e.g., large volume Y Y Y Y
of custom groups)

When maintaining users via file load instead of or in


addition to via UI (or organic growth in APC) Y Y Y Y

When maintaining user/group assignments and/or


responsible user assignments via file load instead of
or in addition to via UI or via self-service user profile Y Y Y Y
maintenance

When updating or replacing pre-loaded UNSPSC


codes and maintaining via file instead of or in Y Y N 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 Y N N 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 N Y Y

When updating pre-loaded UNUOM units of measure Y Y Y N


Ariba- Load format and
Where to load in FPC (multi-ERP Required for
provided Automated Load Owner
setup) <Customer>
SAP Code mechanism

CSV File only


Y Parent HTTPS post only TBD <Customer>

CSV File only


Single: Parent or both
Y HTTPS post only TBD <Customer>
Multi: Both

CSV File only


N Parent HTTPS post only TBD <Customer>

CSV File only


Y Both HTTPS post only TBD <Customer>

CSV File only


Y Parent* HTTPS post only TBD <Customer>

CSV File only


N Parent HTTPS post only TBD Ariba

CSV File only


N Parent HTTPS post only TBD Ariba
CSV File only
Single: Parent or child
Y HTTPS post only TBD <Customer>
Multi: Child

CSV File only


N Parent HTTPS post only TBD Ariba
Best Practice Recommendation
Source
Maint. Method Frequency Due Date
System

Utilize current customer currency


conversion teams and practices to
maintain rates. Ariba does not
provide or update currency
conversion rates as a service. A
single table of conversion rates
governs all applications so be sure
to consider rates needed for all
solutions.

More input to come from Vendor


Strategy workstream.

For Spend Analysis, these are


typically managed through the UI
for things like dashboard
templates and data access
controls.

Ensure User ID exactly matches


(case sensitive) Single Sign-On ID

ERP source of truth is highly


recommended to avoid rogue user
permissions.

Use UNSPSC (and not custom) as


this is the structure used by the
Ariba Network and Suppliers

N/A
N/A

Use ANSI standard to align with


general procurement practices
and suppliers
Completion Date Status

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

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.
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Does not drive any functionality in P2X/Invoice Pro/APC
Deprecated
Highlighted cell indicates the field is
included in the Ariba-provided SAP
extracts and pre-populated values
indicate the source of the data

When is this field required? Restrictons


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
Highlighted cell indicates the field is
included in the Ariba-provided SAP
extracts and pre-populated values
indicate the source of the data

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

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.
When is this field required? Restrictons
Always Must be valid currency code
Always Must be valid currency code
Always Decimal number
Always YYYYMMDD format
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.
When is this field required? Restrictons

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

UserConsolidated.csv (Import User Data [Consolidated File])


One record for every active user.

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.

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.

References WERKS of plant previously defined in Plant.csv. This is the ID of the plant you are
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

When is this field required? Restrictons

• <=255 char.
• No special characters except hyphen(-),
Always underscore (_), period (.) and @
• No spaces allowed

Always See description

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 you need this information in the system <=70 char.

If you need this information in the system <=50 char.

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.


Highlighted cell indicates the field is
included in the Ariba-provided SAP
extracts and pre-populated values
indicate the source of the data

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

Always 'PasswordAdapter1'
/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

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.
References PasswordAdapter of user previously defined in SharedUser.csv. This is the password
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.
When is this field required? Restrictons

Always See description

Always See description

Always See description

If you are assigning purchasing unit See description


responsibility to a user's group assignment
Highlighted cell indicates the field is
included in the Ariba-provided SAP
extracts and pre-populated values
indicate the source of the data

Customer mapping

AGR_USERS-AGR_NAME

AGR_USERS-UNAME

Always 'PasswordAdapter1'
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.
When is this field required? Restrictons

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)

Always See description


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.

References UniqueName of a commodity code previously defined in


CommodityCode.csv. This is the ID of the UNSPSC code you are mapping the custom or
services code to.
When is this field required? Restrictons

Always See description

Always See description

Always See description

Always See description


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.
When is this field required? Restrictons

Always <=50 char.

Always <=255 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.
When is this field required? Restrictons

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