Sie sind auf Seite 1von 37

11/19/13

Document 1265891.1

What Are The Guidelines For Loading Agreement Lines - Spreadsheet Data - In The Buyer Work Center? (Doc ID 1265891.1)
Modified: 13-May-2013 Type: HOWTO

In this Document Goal Solution Using a Spreadsheet to Load Catalog Data Introduction to the Catalog Structure Using a Spreadsheet to Load the Catalog Data Opening the Spreadsheet Text Template File Spreadsheet Tips Getting Started Encoding Section Language Section Catalog Section Optional Catalog Information Example 1: Sample #ENCODING, Language, and Catalog Sections Header Section Optional Header Information Example 2: Sample Header Sections Data Section Data Types The data types are listed below. Adding, Updating, and Expiring Items Item Uniqueness Identifying Lines for Update Further Notes Required and Validated Information Determining Shopping Category and Purchasing Category Assignment Example 3: Loading Items Example 4: Updating Items Price Breaks Example 5: Price Break Example 6: Expiring Items Case Sensitivity Blanking Out a Descriptor Example 7: Deleting Information Reclassifying an Item Under Another Category
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 1/37

11/19/13

Reclassifying an Item Under Another Category

Document 1265891.1

Reviewing and Saving Your Spreadsheet File Loading Your Spreadsheet File Loading the File to a GBPA Loading the File to a BPA or Quotation Error Tolerance Run Time Job Status Resolving Errors Format errors Validation errors Further Notes Handling Special Characters Loading Images Translating Catalogs Descriptors Pricing

APPLIES TO:
Oracle Purchasing - Version 12.0.1 to 12.1.3 [Release 12 to 12.1] Information in this document applies to any platform. ***Checked for relevance on 13-MAY-2013***

GOAL
What are the guidelines for uploading Global Blanket Agreement Lines in the Agreements section of the Buyer Work Center?

SOLUTION
Oracle iProcurement Readme

Using a Spreadsheet to Load Catalog Data


Note: Some of the tables in this document print better in landscape format.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 2/37

11/19/13

Document 1265891.1

This document covers the following topics: Introduction to the Catalog Structure Using a Spreadsheet to Load the Catalog Data Getting Started Encoding Section Language Section Catalog Section Header Section Data Types Data Section Reviewing and Saving Your Spreadsheet File Loading Your Spreadsheet File Resolving Errors Handling Special Characters Loading Images Translating Catalogs This document explains how to create and load your catalog items into the Oracle iProcurement catalog using the spreadsheet loader. You can use any combination of spreadsheet text files and XML files to maintain your catalog items. You are not restricted to using one method or the other. For example, if you load your initial catalog data using XML, you can update the items using a spreadsheet text file. This document is also available in the appendix in the Oracle iProcurement Implementation Guide.

Introduction to the Catalog Structure


At a high level, there are two areas that define the catalog--The catalog data and the catalog schema. Catalog data consists of the items and services available for purchase. The associated prices for these items and services are also considered part of the catalog data. Catalog items loaded using the spreadsheet loader are always loaded to a purchasing document such as GBPA, BPA or Quotation. The purchasing document being loaded to is selected in the user interface just before you load the file. Catalog schema is comprised of a combination of categories, category descriptors (sometimes known as category attributes or local attributes) used to describe items in a specific category, and base descriptors (sometimes known as base attributes) used to describe any item or service in the catalog. There are three types of categories in the catalog. Together, these categories define the catalog's hierarchy: Purchasing Item categories. Every item in the catalog must belong to a Purchasing Item category. Purchasing Item categories are recognized by different Oracle Applications such as Oracle Purchasing, Oracle Inventory, Oracle Daily Business Intelligence, and Oracle iProcurement. The association of Purchasing Item categories with catalog items enables a range of functionality in Oracle Applications. Shopping categories, also known as genus categories, are used to group similar items for presentation to the iProcurement user. Shopping Categories generally have names that are more end-user friendly than Purchasing Item categories, and are displayed prominently in many iProcurement pages to help requesters find what they are shopping for. Shopping categories are not mandatory for all items in the catalog, but they are highly recommended for items that are intended for iProcurement requesters. Shopping categories are found at the lowest level of the category hierarchy; therefore a shopping category can never be a parent category to a child category. Browsing categories, also known as navigation categories (or master or intermediate level categories), are used to define the iProcurement category hierarchy. The category hierarchy helps requesters browse for catalog items. These types of categories can be either a parent or child to another category, but cannot contain any items. Furthermore, there are two types of descriptors in the catalog: Category descriptors apply only to items within a specific shopping category. Ink Color is an example of a category descriptor for the shopping category Ball Point Pens. Category descriptors can vary from one item category to another, and they are
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 3/37

11/19/13

Document 1265891.1

always optional. Base descriptors apply to all items or services in the catalog. Price is an example of a base descriptor. Some base descriptors, such as Price and Unit of Measure, are required; others, such as Manufacturer, are optional. The combination of categories and descriptor make up your catalog schema. Typically, catalog schema is loaded using a separate, XML file (see the Readme_XML_Schema.htm document); however, there are some instances in which you may need to create both the schema and the item and price data in one file. There are two profile options that can be used to dictate whether you can include schema in your catalog spreadsheet file: POR: Auto Load Shopping Categories. Setting this profile option to Yes ensures that if the loader encounters a category in the data section of the text file that does not exist in the catalog, it creates the category. Setting this profile option to No causes the loader to reject the item belonging to this category (unless you use the Apply e-Commerce Gateway Mapping option on the Upload Document page when uploading, and category mapping already exists in Oracle e-Commerce Gateway). The default for this profile option is No. (In spreadsheet loading, if this profile option is set to Yes, the loader creates both a name and key for your category; the key is the same as the name.) If you choose Yes for this profile option, you must map the new category to a Purchasing Category in Oracle Applications to successfully create requisitions for items in that category. See the online Help in the iProcurement Catalog Administration for more information on mapping.

Note: If mapping is successful after using the Apply Category Mapping option, the POR: Auto Load Shopping Categories profile option is ignored.

POR: Auto Load Category Descriptors: Setting this profile option to Yes ensures that descriptors referenced in the text file that do not exist in the catalog are created as category descriptors. Setting this profile option to No causes the loader to reject the item that references the non-existent descriptors. The default for this profile option is No. For more information on Oracle iProcurement profile options, see the Oracle iProcurement Implementation Guide. For information on setting profile options (user profiles), please refer to the Oracle Applications User's Guide or the Oracle Applications System Administrator's Guide.

Using a Spreadsheet to Load the Catalog Data


Catalog content loaded into the catalog is divided into the following sections: 1. Encoding (optional): Used to define the character set that is used in the file. 2. Language (required): Used to identify the language in which the catalog data is loaded. 3. Catalog (required): Used to identify the catalog. 4. Header (required): Used to identify the document to which you plan to upload line level data. 5. Data (required): Includes line item and price information.

Opening the Spreadsheet Text Template File


After you extract the spreadsheet text file template from the Zip file, follow these steps to open it: 1. To open the text template, start your spreadsheet software (for example, Microsoft Excel). 2. From your spreadsheet software, open the text template. If you cannot find the template file in the Open dialog box, make sure that you are pointing to the correct directory, and set the File Type in the dialog box to All files.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 4/37

11/19/13

Document 1265891.1

3. Most spreadsheet software applications will ask you for the data type of the file. Select Delimited. You will then be asked to set delimiters for your data. Choose Tab. Do not change the tab appearance in the file.

Spreadsheet Tips
Use the following spreadsheet tips: On your spreadsheet template, leave the fields directly below the Language Section, #ENCODING, Catalog Section, Header Section, and Data Section blank. These sections are headers, not fields into which data must be entered. Also leave a blank row between these sections, to avoid format errors. The maximum sizes mentioned later may be limited by your spreadsheet application. For example, Long Description allows up to 2,000 bytes, but your spreadsheet application may not allow this many characters in a column. If the maximum number of characters is limited by your spreadsheet application, open the .txt file in a text editor after you have completed your edits in the spreadsheet. Edit the file in the text editor to add more characters. Based on the default column formats, your spreadsheet program may have automatically applied some conversions to your data. For example, in some spreadsheet programs, leading or trailing zeros may be stripped. You should not change the format of the columns to fix the data. (For example, in Microsoft Excel, when you select a column and choose Cells ... from the Format menu, the Category is set to General.) Instead, always check your finished file in a text editor. Fix any problems in the text editor, if needed. (Alternatively, if you are using Microsoft Excel, you can enter a single quotation mark (') in the spreadsheet field before the data to enforce a number or date format. Then save the file.)

Getting Started
You can download resources from the iProcurement Administration Tool to assist you in the spreadsheet loading process. Follow these steps to download resources:

1. 2. 3. 4. 5. 6.

Use the iProcurement Catalog Administration responsibility to access the iProcurement Administration home page. From Agreements Summary view, select the Upload sub-tab Click Upload. Click Download Resources. Choose the type of file you plan to upload (e.g., Tab-delimited) Specify a category if you plan to upload items for a single category only. This field is optional. When you specify a category, iProcurement populates additional information into the template and data files that are specific to the category, such as the names of category descriptors. 7. Click Download, and save the Zip file onto your computer.

The compressed Zip file contains: A A A A A A readme file for the specific type of file you plan to upload (such as this file, for spreadsheet uploads). pre-populated template for the file type you specified (such as a spreadsheet template with column headings). text data file containing the names of all categories currently existing in the Catalog text data file containing the names of all units of measure (UOMs) currently defined in Oracle Applications. text data file containing the names of all line types currently existing. text data file containing the names of all job codes currently existing.

The text data files are included to help you review your organization's existing catalog structure. They are provided for your information, but are not required for the spreadsheet loader to function. You may use the pre-populated template as a starting point, or you can create a spreadsheet file from scratch.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

5/37

11/19/13

Document 1265891.1

Encoding Section
If you are loading any special characters (such as ) in your spreadsheet file, and you are not using a UTF-8 editor, you must specify the proper character or multibyte encoding value, as shown in either of the following examples, to inform the spreadsheet loader of the encoding:

# E N C O D I N GC p 1 2 5 2

Or:

# E N C O D I N GU n i c o d e

Other language characters, such as Chinese, may require a different encoding value. Specify the encoding using the Internet Assigned Numbers Authority (IANA) registered character set names. A list of registered character sets is available from IANA at the following URL: http://www.iana.org/assignments/character-sets. The encoding must support the format in which the file is saved. For example, if you specify Cp1252, the spreadsheet or text editor you are using must also support Cp1252 characters. The bulk loader uses the encoding to "read" the contents of the file. If this encoding does not support the characters in the file nor matches the encoding in which the file was saved, the system may misinterpret your file's content. If you do not specify encoding in your spreadsheet file, iProcurement uses the Java default, and the first line of the spreadsheet file should be the Language Section. You may omit the encoding if you are not using special characters in the file. When you download the spreadsheet template file, an encoding defaults. This default encoding comes from the profile option FND: NATIVE CLIENT ENCODING. For example, if this profile option is set to WE8MSWIN1252, the encoding in the spreadsheet is Cp1252. (WE8MSWIN1252 is the technical name for the Cp1252 encoding. When you set the profile option, you select from a list of values.) If the FND: NATIVE CLIENT ENCODING profile option is not set, the encoding in the downloaded template defaults based on the language of Oracle iProcurement you are using (also called the session language). For example, in an American English session language, the encoding is Cp1252. Generally, you should download the template in the same language in which you will bulk load it, so that the Encoding code and spreadsheet column names match the bulk load language. If, however, you need to bulk load the template in a different language than which you downloaded it, first make sure the column headings in your bulk load file match the template headings in that language. Then make sure the encoding is correct as described in the table in the next section and, if not, update it.

Note: If the default encoding does not match the session language, you need to either change the encoding or change the column headings. (The encoding defaults from the FND: NATIVE CLIENT ENCODING profile option, if set, but the column headings are always displayed in the session language.) The FND: NATIVE CLIENT ENCODING profile option and the Client Character Encoding field on the Preferences page are the same. Changing one changes the other, at the user level.

For a list of the valid encodings by language, see the table in the next section.

Language Section
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 6/37

11/19/13

Document 1265891.1

The spreadsheet files that you submit must conform to the Langcode(-Subcode) standard. The Langcode must be a two-letter language code as defined by ISO 639, Codes for the representation of the names of languages. The Subcode must be a country code from ISO 3166, Codes for the representation of names of countries. (See the list of language and territory codes in the table below.) For example, the following illustrates setting the language to English and the country to theUnited States:

L a n g u a g eS e c t i o nE N U S

The language you specify must be installed in the Oracle iProcurement database. For more information on providing translations for catalog content, see: Translating Catalogs. The Oracle iProcurement catalog supports the following language code and territory code combinations, if the corresponding language is installed: Encoding Language Language Code Territory Code

Cp1252

American English

EN

US

Cp1256

Arabic

AR

AE

Cp1252

Brazilian Portuguese

PT

BR

Cp1252

British English

EN

GB

Cp1251

Bulgarian

BG

BG

Cp1252

Canadian French

FR

CA

Cp1252

Catalan

CA

CT

Cp1250

Croatian

HR

YU

Cp1250

Czech

CZ

CZ

Cp1252

Danish

DA

DK

Cp1252

Dutch

NL

NL

Cp1256

Egyptian

EG

EG
7/37

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/19/13

Document 1265891.1

Cp1252

Finnish

FI

FI

Cp1252

French

FR

FR

Cp1252

German

DE

DE

Cp1253

Greek

EL

GR

Cp1255

Hebrew

IW

IL

Cp1250

Hungarian

HU

HU

Cp1252

Icelandic

IS

IS

Cp1252

Italian

IT

IT

MS932

Japanese

JA

JP

MS949

Korean

KO

KR

Cp1252

Latin American Spanish

ES

MX

Cp921

Lithuanian

LT

LT

Cp1252

Norwegian

NO

NO

Cp1250

Polish

PL

PL

Cp1252

Portuguese

PT

PT

Cp1250

Romanian

RO

RO

Cp1251

Russian

RU

SU

MS936

Simplified Chinese

ZH

CN

Cp1250

Slovak

SK

SI

Cp1250

Slovenian

SL

SI

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

8/37

11/19/13

Document 1265891.1

Cp1252

Spanish

ES

ES

Cp1252

Swedish

SV

SE

MS874

Thai

TH

TH

MS950

Traditional Chinese

ZH

TW

Cp1254

Turkish

TR

TR

Catalog Section
This section is required, but its fields are optional.

Optional Catalog Information


The following table describes the required catalog section fields: Field Name Default Required? Value

Description

Title

Optional

(No default)

Name used to identify your file, for your own identification purposes. There is currently no validation performed on this value. The limit is 255 bytes.

Date

Optional

(No default)

Date of this file, for your own identification purposes.

Source Optional

(No default)

Source information for this file, for your own identification purposes.

Example 1: Sample #ENCODING, Language, and Catalog Sections The following table shows a sample #ENCODING, Language and Catalog sections in the spreadsheet template: #ENCODING Cp1252

Language Section

EN-US

Catalog Section

Title

Source
9/37

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/19/13

Document 1265891.1

Acme Catalog

www.acmecatalog.com

Header Section
This section is required, but its fields are optional and are used for your own identification purposes only. The spreadsheet loader does not validate or store any of the information contained in the header section. When you specify a Purchasing Document in the user interface during the upload process, the loader obtains the proper context from the document you have selected.

Optional Header Information


The following table describes the optional header section fields: Default Required? Value

Field Name

Description

Document Type

Optional

(No default)

Document Number

Optional

(No default)

Operating Unit

Optional

(No default)

Supplier

Optional

(No default)

Supplier Site

Optional

(No default) Information about the document this file will be loaded to, for your own identification purposes. You are not required to provide any values in this section.

Currency

Optional

(No default)

Effective From

Optional

(No default)

Effective To

Optional

(No default)

Requesting Org

Optional

(No default)

Purchasing Org

Optional

(No default)

Purchasing Site

Optional

(No default)

Enabled

Optional

(No default)
10/37

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/19/13

Document 1265891.1

Example 2: Sample Header Sections The following table shows a sample header section in the spreadsheet template: #ENCODING Cp1252

Language Section*

EN-US

Catalog Section

Title

Date

Source

Acme Catalog

Header Section

Document Type

Document Number

Operating Unit

Supplier Supplier Site

Currency Effective From

Effective To

GBPA

10299

Vision Operations

Acme

HQ

USD

2000-01-01

2099-1231

Data Section
The data section of your spreadsheet file is used to create and maintain items and their respective prices.

Data Types
Each descriptor comes with a data type. When you specify the item and price information in your file, be sure to use the correct data type for the descriptors. For example, Lead Time is a Number data type. If you enter the text four instead of the number 4 for Lead Time, the system gives you an error.

The data types are listed below.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/37

11/19/13

Document 1265891.1

Data Type

Text

Values for this descriptor must be text or numbers only. The values cannot be translated; they always display the same in all languages.

Translatable Values for this descriptor (text or numbers) can be translated; the catalog allows you to Text display different values for this descriptor in different languages. See: Translating Catalogs.

Number

Values for this descriptor must be a number only. The values can contain decimals (such as .86). Some descriptors, like price and lead time, cannot have a negative value.

Adding, Updating, and Expiring Items


Catalog items may be maintained using the action commands: ADD, SYNC. The action command ADD always adds a new line to your catalog. SYNC adds an item if it is new and updates it if it already exists. To expire an item, use the SYNC action and provide an Expiration Date for the item. An item expires at the end of its expiration date. If an item has an expiration date of 2006-12-12, it will no longer appears in search results on 2006-12-13. Item Uniqueness The spreadsheet loader determines whether an item is new or already existing based on item information provided in the file. If an item is determined to already exist in the purchasing document to which you are loading, SYNC updates the item. Otherwise, SYNC adds the item to the document as a new line.

Note: Item uniqueness criteria apply only to lines within the Purchasing Document you are uploading to. Identical items may exist in other Purchasing Documents, but they are not considered.

Depending on what information is provided about an item, the spreadsheet loader determines item uniqueness using one of the five rules below, in order of precedence: Precedence User Provides Descriptors used to determine Item Uniqueness

Internal Item Number

Internal Item Number Revision Supplier Part Number Supplier Part Auxiliary ID

Supplier Part Number

Supplier Part Number


12/37

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/19/13

Document 1265891.1

Supplier Part Auxiliary ID Null Internal Item Number

Job Code Null Internal Item Number Null Supplier Part Number

Job Code

Description Null Internal Item Number Null Supplier Part Number Null Job Code

Description Purchasing Category

Line Number Null Internal Item Number Null Supplier Part Number Null Job Code Null Description

Line Number

Identifying Lines for Update


The SYNC action updates an item if it already exists. When the loader looks for existing items in the catalog, it uses Item Uniqueness rules in order of precedence as listed above. The rule with the lowest precedence number that can be applied is used. For example, if both Internal Item Number and Description are provided in an upload file for a particular catalog item, the first uniqueness rule is used to identify existing catalog item. Using this uniqueness rule, an item in the catalog is considered the same as the one being uploaded if their values for Internal Item Number, Revision, Supplier Part Number and Supplier Part Auxiliary ID are the same. Descriptors that are not used as part of the uniqueness criteria can be used to update catalog items. That is, because Description is provided but not used in determining item uniqueness, if an existing item is found in the catalog, the spreadsheet loader updates its description with the description provided in the file. If the spreadsheet loader, using one of the five uniqueness rules above, identifies more than one catalog item that may be eligible for updates, it looks to see if a Line Number has been provided. If a Line Number is provided, the loader updates that line. If a Line Number is not provided, the loader updates the line with the greatest Line Number among the matching lines. Some descriptor values cannot be updated using the loader. For example, because Internal Item Number, and Supplier Part Number are always used as part of the uniqueness criteria whenever they are provided (by way of being first on the list of uniqueness rules
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 13/37

11/19/13

Document 1265891.1

precedence), these descriptors cannot be updated using the loader. Additionally: When a descriptor is used as part of the uniqueness criteria, it cannot be updated. Purchasing Category of Oracle Inventory items cannot be changed on Purchasing Documents through the spreadsheet loader. They must be changed from Oracle Inventory. Job Code and Purchasing Category relationships are pre-configured and therefore cannot be changed on Purchasing Documents through the spreadsheet loader. They should be configured properly prior to using the spreadsheet loader. Further Notes

If you specify the same item, with the same criteria as described in this section, more than once in the same file, the system processes the last identical entry and rejects the previous ones. For example, you specify a supplier of Acme, a supplier part number of 123456, a supplier part auxiliary ID of Green, and a description of Green industrial tool box. Later in the same file, you specify this same data, except that the description is Green and gold industrial tool box. This item is loaded with a description of Green and gold industrial tool box. iProcurement users may add some catalog items to their favorites lists. When you update a descriptor to these items using the loader, they are reflected in the user's favorite lists. For example, if a user adds the item Mechanical Pencil $1.99 to his favorite list, and later on you update the price to $2.49. The next time the user views his favorites list, he will see the price increase to $2.49. Expired lines are not considered for updates. Once expired, a catalog item cannot be updated or unexpired via the loader. For this reason, you should be cautious when mass expiring catalog items using the loader. Expired lines may be updated using the Professional Buyer's WorkCenter. For more information on the Buyer's WorkCenter, see the Oracle Purchasing User Guide.

Required and Validated Information


The following table describes the default base descriptors you will see in the template. User defined base descriptors will also appear in the template. If you specified a category during the download, additional fields may appear representing the category descriptors for the category you chose.

Note: The maximum byte lengths given below are not necessarily the same as character lengths. For example, 700 Japanese characters are typically longer than 700 bytes, and a special symbol (though it is a single character), may be more than one byte. Therefore, the actual, byte limits are given below. How these translate to character limits depends on the language and characters you are using and how the database administrator has configured the database character set.

Field Name

Key

Required? Default

Description and Validation

Data Type

Size (in Bytes)

Action

--

Required

(No default)

Indicates whether the information in the Text file should be added or updated in the catalog. Valid options are ADD, and SYNC.

--

Line Number --

Optional

(No default)

The line number of an item cannot be updated using the spreadsheet loader.

Number

--

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

14/37

11/19/13

Document 1265891.1

However, this field can be used to identify an existing item for update using the SYNC action.

Line Type

--

Optional

Goods

The spreadsheet loader uses Line Type to Text determine the value and purchase basis of the item being uploaded.

--

Category

PURCHASING_CATEGORY Conditional As configured in Oracle Purchasing

A Purchasing Category is required of all Text Catalog items, and should be provided here. When a Purchasing Category is not provided, iProcurement attempts to derive a default value. See section Determining Shopping Category and Purchasing Category Assignment.1

250

Shopping Category

SHOPPING_CATEGORY

Optional

(No default)

A shopping category is not required in Text order for an item to be loaded. However, having a shopping category enables more features (such as category browsing and Content Security) to be used on the item.1

250

Job Code

JOB_CODE

Conditional (No default)

Job code is required for line types with a purchase basis of Temporary Labor.

Text

--

Internal Item INTERNAL_ITEM_NUM Number

Optional

(No default)

To reference an item from Oracle Inventory, provide the Inventory item's item number in this field.

Text

--

Item Revision

ITEM_REVISION

Optional

Revision from Oracle Inventory

Item revision of an Inventory item cannot Number be updated using the spreadsheet loader. However, this field can be used to identify an existing item for update using the SYNC action.

--

Supplier Item

SUPPLIER_ PART_NUM

Optional

(No default)

Supplier item number.

Text

25

Supplier Part SUPPLIER_ Auxiliary ID PART_AUXID

Optional

(No default)

Alternative part number or identifier for Text the item. For example, you could use this field to show that an item with the same Supplier and Supplier Item number can be purchased in two different units of measure (UOMs). Requesters would see the item (with the same Supplier Item number) twice, but with different UOMs in the Supplier Part Auxiliary ID field.

255

Description

DESCRIPTION

Required when adding the item

(No default)

Short description of the item or service. If short description is not provided but a long description is provided, iProcurement uses the truncated long description of up

Translatable 240 Text

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

15/37

11/19/13

Document 1265891.1

to 240 bytes as the item's description.

UNSPSC Code

UNSPSC

Optional

(No default)

The United Nations Standard Product and Text Service Code is an open, nonproprietary system of codes and standardized descriptions for classifying goods and services. To view a list of the UNSPSC codes, go to http://www.eccma.org. (This information does not appear on the requisition, nor is it validated against existing UNSPSC codes.)

700

Price

PRICE

Required (No when default) adding some types of items

Must be a number greater than or equal Number to 0, such as 10, 1.99, or 2,000. Must not use any special formatting, such as currency symbols. The bulk loader uses the language code in the file to interpret the decimal separator in the number. If the decimal separator is not valid for the specified language, then the bulk loader rejects the price line. See: Translating Catalogs. Price is used for line types with a value basis of Quantity.

--

Amount

AMOUNT

Required (No when default) adding some types of items

For line types with a value basis of Fixed Price or Rate, provide the Amount using this field.

Unit

UOM

Required when adding the item

(No default)

Must be a valid unit of measure code defined in Oracle Applications.

Text

30

Manufacturer MANUFACT URER

Optional

(No default)

Name of the manufacturer of each item or Translatable 240 service. Typically, you would complete Text this field only if you are not the manufacturer of the listed item or service. (This information does not appear on the requisition.)

Manufacturer MANUFACT Item URER_PART_ NUM

Optional

(No default)

Manufacturer-assigned part number of Text each item or service. Typically, you would complete this field only if you are not the manufacturer of the listed item or service. (This information does not appear on the requisition.)

30

Alias

ALIAS

Optional

(No default)

Alternate description or identifier for each Translatable 700 item or service that people can enter Text when performing a search. For example, an alias for soda might be pop. To enter more than one alias, separate each alias
16/37

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/19/13

Document 1265891.1

with a comma--for example: soda,pop,cola. (This information does not appear on the requisition.)

Lead Time

LEAD_TIME

Optional

(No default)

Amount of time, expressed in days, Number between the order date and the shipment date. Use any number greater than or equal to 0, such as 7 or 1.5. Seven is invalid. (This information does not appear on the requisition.)

--

Image

PICTURE

Optional

(No default)

File name of the image that is associated Text with the item; for example: bluepen.gif. The image must reside on the local server, in the image directory specified in POR: Hosted Images Directory. Alternatively, you can enter a URL at which the image can be viewed. If so, enter the full URL; for example: http://www.us.oracle.com/logo.gif. (This information does not appear on the requisition.) See: Loading Images.

700

Thumbnail Image

THUMBNAIL_ IMAGE

Optional

(No default)

File name of a smaller, thumbnail image Text for the item, for displaying on the Search Results Summary, Search Results, and Compare Items pages; for example: bluepen.gif. The image must reside on the local server, in the image directory specified in POR: Hosted Images Directory. Alternatively, you can enter a URL at which the image can be viewed. If so, enter the full URL; for example: http://www.us.oracle.com/logo.gif. (This information does not appear on the requisition.) See: Loading Images.

700

Attachment URL

ATTACHMENT_ URL

Optional

(No default)

URL at which an attachment for each item or service can be viewed. Include the full URL; for example: http://www.us.oracle.com/attachment.gif. On the Item Details page, this URL displays in an Additional Information field. (This information does not appear on the requisition.)

Text (but 700 displayed as a URL in search results and item details)

Supplier URL SUPPLIER_URL

Optional

(No default)

URL for the supplier's Web site. Include the full URL; for example: http://www.us.oracle.com. On the Item Details page, this URL displays in an Additional Information field. (This information does not appear on the requisition.)

Text (but 700 displayed as a URL in search results and item details)

Manufacturer MANUFACT URL URER_URL

Optional

(No default)

URL for the manufacturer's Web site. Include the full URL; for example: http://www.us.oracle.com. On the Item

Text (but 700 displayed as a URL in


17/37

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/19/13

Document 1265891.1

Details page, this URL displays in an Additional Information field. (This information does not appear on the requisition.)

search results and item details)

Long Description

LONG_ DESCRIPTION

Optional

(No default)

Detailed description of your item or service. (This information does not appear on the requisition.)

Translatable 2000 Text

Availability

AVAILABILITY

Optional

(No default)

Status of item availability from supplier.

Text

700

Comments

COMMENTS

Optional

(No default)

Any additional comments about the item.

Text

700

Expiration Date

EXPIRATION_DATE

Optional

(No default)

Use to specify when an item will be no longer available in the catalog. An expiration date of 2006-12-12 indicates that an item will no longer appear in search results on 2006-12-13.

Date

--

1 - If the category exists in the catalog already, you can enter either the name or key here. Category names are language specific.

Determining Shopping Category and Purchasing Category Assignment


A valid Purchasing Category is required for all line items in the catalog. A valid Shopping Category is optional. If you provide partial category information in an upload file, Oracle iProcurement may be able to derive Purchasing or Shopping category information, in the following ways: Shopping Category Purchasing Category Behavior

Not Provided

Not Provided

If a default Purchasing Category has been defined in Oracle Purchasing, the default Purchasing Category is used. Otherwise, an error message is displayed, and the item is not processed. The spreadsheet loader will derive Shopping Category using the Purchasing to Shopping Category Mapping. It is acceptable if Shopping Category is not found from mapping since Shopping Category is optional.

Not Provided

Valid Purchasing Category

The provided Purchasing Category is used. The spreadsheet loader will derive Shopping Category using the Purchasing to Shopping Category Mapping. It is acceptable if Shopping Category is not found from mapping since Shopping Category is optional.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

18/37

11/19/13

Document 1265891.1

Not Provided

Invalid Purchasing Category

An error message is displayed, and the item is not processed.

Valid Shopping Category

Not Provided

The spreadsheet loader will derive Purchasing Category using the Shopping to Purchasing Category Mapping. If no valid mapping exists, The default Purchasing Category is used. If no default Purchasing Category exists, an error message is displayed, and the item is not processed.

Valid Shopping Category

Valid Purchasing Category

The user provided values are used.

Valid Shopping Category

Invalid Purchasing Category

An error message is displayed, and the item is not processed.

Invalid Shopping Category

Not Provided

If POR: Auto Load Shopping Categories is Yes, a new Shopping Category will be created and used. Otherwise, and error message is displayed, and the item is not processed. If a default Purchasing Category has been defined in Oracle Purchasing, the default Purchasing Category is used. Otherwise, an error message is displayed, and the item is not processed

Invalid Shopping Category

Valid Purchasing Category

If POR: Auto Load Shopping Categories is Yes, a new Shopping Category will be created and used. Otherwise, and error message is displayed, and the item is not processed. The user provided value for Purchasing Category is used.

Invalid Shopping Category

Invalid Purchasing Category

If POR: Auto Load Shopping Categories is Yes, a new Shopping Category will be created. An error message is displayed, and the item is not processed.

Oracle e-Commerce Gateway Mappings can be used to provide additional category derivation logic during upload. The Oracle eCommerce Gateway provides advanced mapping functionality, but also requires additional configuration before the spreadsheet loader can be used. For this reason, you should reserve the use of Oracle e-Commerce Gateway for situations that require it. When Oracle e-Commerce Gateway Mapping is turned on during the upload process, iProcurement treats any Shopping Categories you provide as Supplier Categories. For example, if you provide a Shopping Category but not a Purchasing Category, and turn on the e-Commerce Gateway Mapping option during the upload of a particular catalog item, the item's Shopping Category is used in the
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 19/37

11/19/13

Document 1265891.1

following way: The Shopping Category is considered as the item's Supplier Category. Using the e-Commerce Gateway, iProcurement looks for a Supplier-to-Internal Category Mapping. If an Internal Category is found, it is temporarily considered as the item's Purchasing Category. Using Purchasing-to-Shopping Category Mapping definitions, iProcurement looks for a Shopping Category value. If a Shopping Category is found, using Shopping-to-Purchasing Category Mapping definitions, iProcurement looks for a Purchasing Category. Since you did not provide a Purchasing Category, the mapped Purchasing Category is used as the item's Purchasing Category. Depending on your category mapping configuration, the spreadsheet loader may add the item to your catalog using a combination of mapped values for Shopping and Purchasing categories. If your mapping configuration is incomplete, the spreadsheet loader generates an error.

Example 3: Loading Items


In this spreadsheet example, two items are added to the catalog.

Note: This example does not show all of the columns you would see in an actual template. It does show all required columns, plus any other columns specific to the example.

#ENCODING Cp1252

Language Section*

EN-US

Catalog Section

Title

Date

Source

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

20/37

11/19/13

Document 1265891.1

Acme Catalog

Header Section

Document Document Number Operating Supplier Type Unit

Supplier Site Currency Effective From

Effective To

These

Optional

Fields

Are

For

Your

Comments Only

Data Section

Action

Category

Shopping Description Category

Long Description

Unit

Price

Supplier Part Auxiliary ID

Supplier Size Part Number

ADD

CLOTHING.SHIRTS Shirts

Green TShirt

100% cotton, heavy weight.

Each

10

Green

TS-01

ADD

CLOTHING.SHIRTS Shirts

Red T-Shirt 100% cotton, heavy weight.

Each

10

Red

TS-01

The descriptor Size is a category descriptor specific to the Shopping Category Shirts.

Example 4: Updating Items


In this spreadsheet example, two items are updated in the catalog.

Note:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 21/37

11/19/13

Document 1265891.1

This example does not show all of the columns you would see in an actual template. It does show all required columns, plus any other columns specific to the example.

If the following items exist in a GBPA: Internal Item Line Number Supplier Part Revision Number Category Supplier Part Auxiliary ID Price Expiration Date Description

3255156

TS-01

Green

CLOTHING.SHIRTS 10

2099-1231

Green T-shirt

3255156

TS-01

Red

CLOTHING.SHIRTS 10

2099-1231

Red T-shirt

3255157

TS-01

Black

CLOTHING.SHIRTS 10

2099-1231

Black T-shirt

20112

PT-01

Red

CLOTHING.PANTS

10

2099-1231

Red Exercise Pants

20112

PT-01

Black

CLOTHING.PANTS

10

2099-1231

Black Exercise Pants

A file containing the information below updates the price, description, and expiration date of lines 1 and 4 of the GBPA.

Note: This example does not show all of the columns you would see in an actual template. It does show all required columns, plus any other columns specific to the example.

#ENCODING

Cp1252

Language Section*

EN-US
22/37

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

11/19/13

Document 1265891.1

Catalog Section

Title

Date

Source

Acme Catalog

Header Section

Document Type

Document Number

Operating Unit

Supplier

Supplier Site

Currency

Effective From

Effective To

These

Optional

Fields

Are

For

Your

Comments Only

Data Section

Action

Internal Item Number

Supplier Part Number

Description

Price

Expiration Date

SYNC

3255156

TS-01

SALE! Green Tshirt

5.00

2006-12-31

SYNC

PT-01

SALE! Red Exercise 5.00 Pants

2006-12-31

Item uniqueness rules are used to determine which Catalog items are updated, resulting in the following list of GBPA items: Internal Item Line Number Supplier Part Revision Number Category Supplier Part Auxiliary ID Price Expiration Date Description

3255156

TS-01

Green

CLOTHING.SHIRTS 5

2006-1231

SALE! Green T-shirt

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

23/37

11/19/13

Document 1265891.1

3255156

TS-01

Red

CLOTHING.SHIRTS 10

2099-1231

Red T-shirt

3255157

TS-01

Black

CLOTHING.SHIRTS 10

2099-1231

Black T-shirt

20112

PT-01

Red

CLOTHING.PANTS

2006-1231

SALE! Red Exercise Pants

20112

PT-01

Black

CLOTHING.PANTS

10

2099-1231

Black Exercise Pants

Price Breaks
Price breaks for items may be loaded using the spreadsheet loader. When a line item contains price breaks, and there are errors with one or more of the price breaks but no other errors with the line item, the item is loaded but the price breaks result in errors. Price Breaks loaded to GBPAs and BPAs using the spreadsheet loader are always treated as new price breaks (ADDs). Price Breaks loaded to Quotations always replace existing Price Breaks. iProcurement retrieves the latest price break for an item when duplicates exist. The following table describes the Price Break fieldnames you will see in the template: Description and Validation Data Type

Field Name

Key

Required? Default

Ship-To Org --

Optional

(No default)

Text

Ship-To Location

--

Optional

(No default)

Text

Quantity

--

Optional

(No default)

Number

Effective From

--

Optional

(No default)

Date

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

24/37

11/19/13

Document 1265891.1

Effective To

--

Optional

(No default)

Date

Break Price

--

Optional

(No default)

Number

Discount

--

Optional

(No default)

Number

Example 5: Price Break


In this spreadsheet example, a price break is added to an existing catalog item.

Note: This example does not show all of the columns you would see in an actual template. It does show all required columns, plus any other columns specific to the example.

#ENCODING

Cp1252

Language Section*

EN-US

Catalog Section

Title

Date

Source

Acme Catalog

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

25/37

11/19/13

Document 1265891.1

Header Section

Document Type

Document Number

Operating Unit

Supplier

Supplier Site

Currency

Effective From

Effective To

These

Optional

Fields

Are

For

Your

Comments

Only

Data Section

Action

Line Number

Quantity

Effective From

Effective To

Break Price

Discount

SYNC

10

SYNC

10

Example 6: Expiring Items


This example expires the two on-sale items in our catalog. Based on our previous examples, we have the following items in our catalog. Internal Item Line Number Supplier Part Revision Number Category Supplier Part Auxiliary ID Price Expiration Date Description

3255156

TS-01

Green

CLOTHING.SHIRTS 5

2006-1231

SALE! Green T-shirt

3255156

TS-01

Red

CLOTHING.SHIRTS 10

2099-1231

Red T-shirt

3255157

TS-01

Black

CLOTHING.SHIRTS 10

2099-1231

Black T-shirt

20112

PT-01

Red

CLOTHING.PANTS

2006-1231

SALE! Red Exercise Pants

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

26/37

11/19/13

Document 1265891.1

20112

PT-01

Black

CLOTHING.PANTS

10

2099-1231

Black Exercise Pants

A file containing the information below expires lines 1 and 4:

Note: This example does not show all of the columns you would see in an actual template. It does show all required columns, plus any other columns specific to the example.

#ENCODING

Cp1252

Language Section*

EN-US

Catalog Section

Title

Date

Source

Acme Catalog

Header Section

Document Type

Document Number Operating Unit

Supplier

Supplier Site

Currency Effective From

Effective To

These

Optional

Fields

Are

For

Your

Comments Only

Data Section

Action

Category

Description

Expiration Date

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

27/37

11/19/13

Document 1265891.1

SYNC

CLOTHING.SHIRTS SALE! Green Tshirt

<Replace with Today's Date>

SYNC

CLOTHING.PANTS

SALE! Red Exercise Pants

<Replace with Today's Date>

Case Sensitivity
Some values are case sensitive and will be considered as updated if their case has changed. All values are case sensitive except the following values: Category, such as Ball Point Pens Descriptor, such as Ink Color or Lead Time Unit of Measure, such as EA Supplier Site For example, you can specify the category as Ball Point Pens or Ball point pens, and they would be treated as the same. Your item would be added to the category Ball Point Pens. But the supplier item number AB457Z would be treated as a different item number than ab457z. The system would add ab457z to the catalog if AB457Z already exists.

Blanking Out a Descriptor


If you want to delete the value for a particular descriptor for an item, use the text #DEL, as shown in the following example. You cannot delete values for descriptors that must be populated (such as category), and you cannot delete descriptors which are being used in determining item uniqueness. Example 7: Deleting Information The following table shows a sample spreadsheet template that uses #DEL to delete a value that describes an item: #ENCODING Cp1252

Language Section*

EN-US

Catalog Section

Title

Date

Source

Acme Catalog
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 28/37

11/19/13

Document 1265891.1

Header Section

Document Type

Document Number Operating Unit

Supplier

Supplier Site

Currency Effective From

Effective To

These

Optional

Fields

Are

For

Your

Comments

Only

Data Section

Action

Category

Description

Long Description

UNSPSC Code

SYNC

CLOTHING.SHIRTS Black T-shirt #DEL

00112233

In this example, item "Black T-shirt" no longer has a value for Long Description in the catalog. The Long Description descriptor itself still displays, but for your item, no value exists for Long Description.

Reclassifying an Item Under Another Category


If you want to move items formerly under one category, such as Ball Point Pens, to another category, such as Felt Pens, list all of the items under Felt Pens using the SYNC action.

Note: When you move an item from one category to another, you lose its category descriptors. For example, you originally add an item under the category Felt Pens, using Tip Width and Ink Color as category descriptors. You then move the item to Ball Point Pens. The item will no longer display the Tip Width and Ink Color you specified, even if Ink Color exists in the new category. Category descriptors are specific to each category.

Reviewing and Saving Your Spreadsheet File


See the tables in the previous sections that describe the information in the template to be sure that the information in your spreadsheet file will validate successfully. Save your file as a tab-delimited text with any filename. (If you did not provide a Title for your file, the bulk loader stores the file name in the system.) The bulk loader has no file size limitations; however, larger files may take some time to load.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

29/37

11/19/13

Document 1265891.1

Loading Your Spreadsheet File


Once you have created and reviewed your spreadsheet file, load it to Oracle iProcurement.

Loading the File to a GBPA


Follow these steps to load the file to a GBPA:

1. Use the Purchasing responsibility to access the Professional Buyer'sWorkCenter home page. Alternatively, if the GBPA document has been enabled for catalog administrator authoring, use the iProcurement Catalog Administration responsibility to access the iProcurement Administration home page.

2. From Agreements Summary view, select an agreement to Update.

3. Navigate to the Lines sub-tab.

4. Select Add Lines via Upload, click Go.

5. For File Type, select Tab-delimited text.

6. Enter the File Name and path, or click Browse to navigate to your spreadsheet file.

7. Specify your desired values for approval, mapping, and error tolerance options.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

30/37

11/19/13

Document 1265891.1

8. Click Submit to send your file. As soon as the load is started, the screen displays a confirmation message and job number. To check the status of your job, return to Agreement Summary page.

Loading the File to a BPA or Quotation


Follow these steps to load the file to a BPA or Quotation:

1. Use the iProcurement Catalog Administration responsibility to access the iProcurement Administration home page.

2. From Agreements Summary view, select the Upload sub-tab

3. Click Upload.

4. For Document Type, select BPA or Quotation.

5. Enter the document number you want to upload to.

6. For File Type, select Tab-delimited text.

7. Enter the File Name and path, or click Browse to navigate to your spreadsheet file.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

31/37

11/19/13

Document 1265891.1

8. Specify your desired values for mapping, and error tolerance options.

9. Click Submit to send your file. As soon as the load is started, the screen displays a confirmation message and job number. To check the status of your job, return to Upload Summary page.

Error Tolerance
The loader can automatically stop the loading process when the number of line errors exceeds a certain number. This may be useful if you are loading large files and a simple editing error has caused all the line items in your file to error out. Instead of waiting for the entire file to finish loading, you can instruct the loader to stop after a certain tolerance threshold.

Run Time
Large files may take some time to load. You do not need to remain logged in while your job completes. If you need, click the Refresh or Reload button on your browser to update the status.

Job Status
To check the status of your job, return to Agreement Summary (for GBPA) or Upload History page (for BPA and Quotations). The follow job statuses are possible: Pending (waiting to be processed) Running (processing the file) Completed Error (did not load the file at all because of a format or encoding error, or loaded part of the file but rejected some of its lines)

Resolving Errors
The View Errors page alerts you to errors in your spreadsheet file. Oracle iProcurement looks for errors in your file in two phases: format errors and validation errors.

Format errors
Format errors occur when the spreadsheet file fails validation. Some examples of format errors include special characters in your file that are not covered by the character set specified in the #ENCODING declaration, or extra rows or columns in your spreadsheet. If a format error is encountered, the load process stops, and an Error status is returned. The View Errors page provides additional information about why your file failed upload. Fix the file and resubmit it for processing.

Validation errors
Once format errors, if any, are resolved, Oracle iProcurement checks for validation errors. Validation errors occur when information that you entered in your spreadsheet file does not match corresponding information already held within Oracle iProcurement or Oracle Applications. For example, if you enter values for Unit or Currency that Oracle Applications does not recognize, a validation
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 32/37

11/19/13

Document 1265891.1

error will occur. The individual item or price for which the validation errors occurred will be rejected. The View Errors page provides information about lines that have been rejected. Fix the file and resubmit it for processing. Further Notes

When a file is uploaded with multiple lines, it is possible for some but not all of the uploaded lines to contain validation errors. The spreadsheet loader handles partial validation errors in one of two ways. For GBPA uploads, lines that do not contain errors are processed and can become available for downstream processing (such as review and approval by buyers) in Oracle Applications. You must discard errors from the View Errors page before resubmitting additional files. For BPA and Quotation uploads, if there is at least 1 error in the uploaded file, the entire file is rejected. An uploaded file must be entirely free of errors before any of its lines are processed into Oracle Applications.

Handling Special Characters


If you want to include special characters (such as trademark symbols) in your text file, follow the steps below. You only need to follow these steps if the special characters are not supported by the encoding in which the file was saved. For example, a file created inGermany likely supports saving files with umlaut characters, and you do not have to follow these instructions for inserting umlaut characters. Follow these instructions if the encoding in which your file is saved does not support the special character. Trademark or copyright symbols are examples of these. These steps are just one method for copying special characters into the bulk load file. You may have other methods. To insert special characters in your spreadsheet text file: 1. Open your text file in your spreadsheet application. 2. Access the Character Map utility in Windows. Depending on your computer's configuration, you may be able to find this utility in the Start menu: choose Program, then Accessories, then System Tools. 3. Select the proper encoding for the contents of the file. For example, if the contents of the file are in German, select the Windows Western encoding (Cp1252). See Encoding Section. You may find the encoding in a Subset drop-down menu or in an advanced view area of the Character Map window. 4. In the Characters to Copy field, double-click the special character from the characters display in the Character Map window. You may need to select a font such as Times New Roman from the Font menu in the Character Map window. 5. Copy and paste the text or character from the Characters to Copy field to your file. (You can use the Copy button in the Character Map window and the Paste command in the spreadsheet application.) 6. Make sure the proper encoding is entered in the #ENCODING field in the spreadsheet text file, as usual, according to the language contents of the file. See Encoding Section. 7. Save and upload your spreadsheet .txt file. An alternative to using the Character Map utility is to use the "Alt" number key sequence for the special character. (Hold down the Alt key while entering the number sequence. You must use the number keypad on your keyboard to enter the numbers.) For example: Alt + 0153--Trademark TM Alt + 0174--Registered trademark Alt + 0169--Copyright
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1 33/37

11/19/13

Document 1265891.1

Alt + 0196--A umlaut These numbers are the decimal equivalents of a letter. For example, 065 is the decimal equivalent of A.

Note: Do not use HTML code or character sequences, or Java scripts, in the bulk load file. For security reasons, Oracle Applications Framework (the technology upon which Oracle iProcurement is built) ignores these. For example, <B>Buy Now</B> displays as <B>Buy Now</B> in the catalog. The sequence &copy; (instead of the copyright symbol) displays as &copy; in the catalog.

Loading Images
You can specify or load two kinds of images for items: Images that display on the Item Details page when requesters view the details of an item. (Use the Image field in the bulk load file.) Smaller, thumbnail versions of the images that display on the Search Results Summary, Search Results, and Compare Items pages. (Use the Thumbnail Image in the bulk load file.) For a complete overview of image management, including recommendations on thumbnail image sizes, see the Image Management section of the Oracle iProcurement Implementation Guide. There are two ways to associate items with images in your bulk load file: Copy the images to the local server and indicate the image file names in the spreadsheet file. Reference the URLs of the images in the spreadsheet file. To copy the images to the local server: 1. For the POR: Hosted Images Directory profile option, enter the directory path you use to store image files. This path usually corresponds to the OA_MEDIA directory. Contact your database administrator or installation team for the exact location of your OA_MEDIA directory. Behind the scenes, the catalog uses the Application Framework Agent and POR: Hosted Images Directory profile options to locate the image. For example, if Application Framework Agent is set to http://abc.com:8888 and POR: Hosted Images Directory is set to /OA_MEDIA/US/, then the catalog locates the image abc.gif at http://abc.com:8888/OA_MEDIA/US/abc.gif. (If you specify a full URL, such as http://abc.com:8888/abc.gif, in the bulk load file, then the catalog goes directly to that URL. The catalog constructs the URL based on the profile options described here only when a catalog image name, with no URL, is specified in the bulk load file.) 2. Ask your database administrator to transfer the pictures to the directory you specified above. 3. Use the appropriate columns in your spreadsheet file to specify the image file name, such as bluepen.gif. To specify an image for the Item Details page, use the Image column. To specify a thumbnail image for the search results and comparison pages, use the Thumbnail Image field.

Note: The file name for the image is case sensitive. For example, if the image file name is bluepen.gif, but you specify BluePen.gif in the Image field, the image will not display.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

34/37

11/19/13

Document 1265891.1

4. Load your spreadsheet file. To specify the URL of the image that resides on the Internet: 1. Obtain the full path of the image (for example, http://www.oracle.com/toplogo2.gif). 2. Insert this full path into the appropriate columns in your spreadsheet file. To specify an image for the Item Details page, use the Image column. To specify a thumbnail image for the search results and comparison pages, use the Thumbnail Image field. 3. Load your spreadsheet file. If you specify both a server image (in the Image field) and an Image URL for an item, Oracle iProcurement displays the server image.

Note: Instead of creating separate detail and thumbnail images, you could use the same image file name or URL for both the Image and Thumbnail Image fields. Then set either the POR: Thumbnail Width or POR: Thumbnail Height profile option to resize the image for thumbnails. For instructions, see the Image Management section of the Oracle iProcurement Implementation Guide.

Translating Catalogs
You can load your catalog items in any or all of the languages that Oracle iProcurement supports. The language you specify in your file must be installed in the Oracle iProcurement database. When you add an item to the catalog, it is added only in the language specified at the beginning of your spreadsheet file and the creation language of your purchasing document. To provide your catalog items in another language, translate the spreadsheet file and load it again specifying the supported language and the action command SYNC. When you expire an item, the item and its translations are expired together.

Descriptors
When an item is created in another language, only the translatable descriptors (those with a Translatable Text data type) need to be specified in the spreadsheet file (along with minimally required values). All of the non-translatable descriptors, such as Manufacturer Item number, are automatically inherited from the original language in which the item was created. If you change the value of a nontranslatable descriptor when loading the translated file, the change will appear in all languages installed in the Oracle iProcurement database. Only translatable descriptors can vary by language. For example, if you change the Manufacturer Item number in one language, it is changed in all languages; however, if you change the item's Description, it is changed only in the language specified in the file. Load your catalog items in one language at a time. For example, load your catalog items in English, using the EN-US language code, then translate and load that catalog file in French using the FR-FR language code.

Note: When you use descriptor names as column headings in your spreadsheet file, the descriptor names must match exactly those given in the system for that language. To ensure that the column headings are valid for the language you are translating to, log on to Oracle iProcurement in that language and download the spreadsheet template file. The file will include column headings in that language. Either copy your translated item information to this file, or overwrite the column headings in your existing file with the translated column headings (whichever is easier for you).

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

35/37

11/19/13

Document 1265891.1

Alternatively, the column headings in your spreadsheet may also reference descriptor keys (which are not language specific). For instance, a column heading of LONG_DESCRIPTION will reference the long description descriptor in all languages because LONG_DESCRIPTION is a descriptor key.

Pricing
Pricing does not need to be included in the translated file. When an item is translated to another language, its pricing is also automatically copied over to that language. As with all non-translatable descriptors, if you change the pricing information in one language, it is changed in all languages. For example, you bulk load an item that costs 2 USD, specifying EN-US (English) in the file. Later, you change EN-US to FR-FR (French) and change the price from 2 USD to 4 USD. The price is changed in all languages. Price list currencies are independent of language. The system uses the language code specified in your file to determine the decimal separator in a number. For example, if you specify American English (EN-US) in the file, the system interprets periods as decimal separators. If you specify German (DE-DE) in the file, the system interprets commas as decimal separators. The following table shows some examples: Language Price in in Bulk Load Bulk Load Displayed Price when ICX: Numeric File File characters is 10,000.00

Displayed Price when ICX: Numeric characters is 10.000,00

EN-US

2,000

2,000.00

2.000,00

DE-DE

2,000

2.00

2,00

EN-US

10000.00

10,000.00

10.000,00

DE-DE

10000.00

1,000,000.00

1.000.000,00

EN-US

1.2,5

This price is rejected by the bulk loader, because EN-US does not expect a comma as a decimal separator.

This price is rejected by the bulk loader, because EN-US does not expect a comma as a decimal separator.

DE-DE

1.2,5

12.50

12,50

DE-DE

1,2.5

This price is rejected by the bulk loader, because DE-DE does not expect a period as a decimal separator.

This price is rejected by the bulk loader, because DE-DE does not expect a period as a decimal separator.

EN-US

1,29

129.00

129,00

DE-DE

1,29

1.29

1,29

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

36/37

11/19/13

Document 1265891.1

Note: Decimal separators are influenced by the profile option ICX: Numeric characters in Oracle Applications. If this profile option is set to use periods as decimal separators, then the decimal separator that requesters see is a period regardless of their language. The bulk loader uses the language code in the file to determine where the decimal separator is placed. The profile option determines how the price displays to requesters. (If the profile option ICX: Numeric characters is not set, Oracle iProcurement uses the nls_numeric_parameters database setting to determine how to display the price.)

Readme File - Using a Spreadsheet to Load Catalog Data Copyright 2006 Oracle Corporation. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other purpose. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the US Government, the following notice is applicable: Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial computer software" and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are "restricted computer software" and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the Programs. Oracle is a registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=c2iomjfk3_45&id=1265891.1

37/37