Agreement Upload File Format
Agreement line attributes can be updated either using the Edit Agreement page or through a background process using the agreement loader. The loader supports four file formats (TXT, XML, CIF, and cXML). Within a file, columns or tags correspond to different line attributes.
The table below lists the supported agreement line attributes and the corresponding column name or tag for the different upload file formats.
Agreement Line Catalog Attributes
|
Agreement Line Attribute |
Attribute Key |
XML Tag |
TXT Column |
cXML Tag |
CIF Column |
|---|---|---|---|---|---|
|
Line Type |
LINE_TYPE |
Specified as an attribute of the ITEM tag. For example: <ITEM lineType="Goods"> |
Line Type |
Extrinsic. For example: <Extrinsic name="LINE_TYPE">Goods </Extrinsic> |
Parametric Data ({Name:Value pair}) for example: {LINE_TYPE = Goods;} |
|
Category Name |
CATEGORY |
CATEGORY_NAME |
Category Name |
Classification |
Classification Codes, SPSC Code |
|
Item |
ITEM |
INTERNAL_ITEM_NUM |
Internal Item Number |
Extrinsic. For example: <Extrinsic name="ITEM"> CM96715</Extrensic> |
Internal Item Number |
|
Revision |
ITEM REVISION |
Specified as an attribute of the INTERNAL_ITEM_NUM tag. For example: <INTERNAL_ITEM_NUM revision="1"> |
Revision |
Extrinsic for example: <Extrinsic name="ITEM_REVISION"> 1</Extrinsic> |
Item Revision |
|
Supplier Item |
VENDOR_PRODUCT_NUM |
SUPPLIER_ITEM |
Supplier Item |
SupplierPartID |
Supplier Part ID |
|
Description |
DESCRIPTION |
DESCRIPTION |
Description |
ShortName |
Short Name |
|
Supplier Item Auxiliary Identifier |
SUPPLIER_PART_AUXID |
SUPPLIER_ITEM_AUXILIARY_IDENTIFIER |
Supplier Item Auxiliary Identifier |
SupplierPartAuxiliaryID |
Supplier Part Auxiliary ID |
|
Manufacturer Part Number |
MANUFACTURER_PART_NUM |
NAMEVALUE For example: <NAMEVALUE name="MANUFACTURER_PART_NUM"> ORACLE-101 </NAMEVALUE> |
Manufacturer Part Number |
ManufacturerPartID |
Manufacturer Part ID |
|
Supplier URL |
SUPPLIER_URL |
NAMEVALUE For example: <NAMEVALUE name="SUPPLIER_URL"> http://www.oracle.com </NAMEVALUE> |
Supplier URL |
URL |
Supplier URL |
|
Manufacturer URL |
MANUFACTURER_URL |
NAMEVALUE For example: <NAMEVALUE name="MANUFACTURER_URL"> http://www.oracle.com </NAMEVALUE> |
Manufacturer URL |
Extrinsic. For example: <Extrinsic name="MANUFACTURER_URL"> http://www.oracle.com </Extrinsic> |
Manufacturer URL |
|
Attachment URL |
ATTACHMENT_URL |
NAMEVALUE For example: <NAMEVALUE name="ATTACHMENT_URL"> http://www.attachmentURL.com </NAMEVALUE> |
Attachment URL |
Extrinsic. For example: <Extrinsic name="ATTACHMENT_URL"> http://www.attachmentURL.com </Extrinsic> |
Parametric Data ({Name:Value pair}) for example: {ATTACHMENT_URL= http://www.attachmentURL.com;} |
|
Thumbnail Image |
THUMBNAIL_IMAGE |
NAMEVALUE For example: <NAMEVALUE name="THUMBNAIL_IMAGE"> http://www.oracle.com/thumbimage.jpg </NAMEVALUE> |
Thumbnail Image |
Extrinsic. For example: <Extrinsic name="THUMBNAIL_IMAGE"> http://www.oracle.com/thumbimage.jpg </Extrinsic> |
Parametric Data ({Name:Value pair}) for example: {THUMBNAIL_IMAGE= http://www.oracle.com/thumbimage.jpg;} |
|
Manufacturer |
MANUFACTURER |
NAMEVALUE For example: <NAMEVALUE name="MANUFACTURER"> Oracle </NAMEVALUE> |
Manufacturer |
ManufacturerName |
Manufacturer Name |
|
Image URL |
PICTURE |
NAMEVALUE For example: <NAMEVALUE name="PICTURE"> http://www.oracle.com/image.jpg </NAMEVALUE> |
Image |
Extrinsic. For example: <Extrinsic name="PICTURE"> http://www.oracle.com/image.jpg </Extrinsic> |
Image |
|
Availability |
AVAILABILITY |
NAMEVALUE For example: <NAMEVALUE name="AVAILABILITY"> In Stock </NAMEVALUE> |
Availability |
Extrinsic. For example: <Extrinsic name="AVAILABLITY"> In Stock </Extrinsic> |
Availability |
|
Lead Time |
LEAD_TIME |
NAMEVALUE For example: <NAMEVALUE name="LEAD_TIME"> 6 </NAMEVALUE> |
Lead Time |
LeadTime |
Lead Time |
|
Long Description |
LONG_DESCRIPTION |
NAMEVALUE For example: <NAMEVALUE name="LONG_DESCRIPTION"> Sun Blade Servers </NAMEVALUE> |
Long Description |
Description |
Item Description |
|
UOM |
UOM_CODE |
UOM |
UOM |
UnitOfMeasure |
Unit of Measure |
|
Price |
UNIT_PRICE |
UNIT_PRICE |
Price |
Money |
Unit Price |
|
Alias |
ALIAS |
NAMEVALUE For example: <NAMEVALUE name="ALIAS"> Blades </NAMEVALUE> |
Alias |
Extrinsic. For example: <Extrinsic name="ALIAS"> Blades </Extrinsic> |
Parametric Data ({Name:Value pair}) for example: {ALIAS= Blades;} |
|
Comments |
COMMENTS |
NAMEVALUE For example: <NAMEVALUE name="COMMENTS"> Cooling Required </NAMEVALUE> |
Comments |
Extrinsic. For example: <Extrinsic name="COMMENTS"> Cooling Required </Extrinsic> |
Parametric Data ({Name:Value pair}) for example: {COMMENTS = Cooling Required;} |
|
UNSPSC |
UNSPSC |
NAMEVALUE For example: <NAMEVALUE name="UNSPSC"> 14111506 </NAMEVALUE> |
UNSPSC |
Extrinsic. For example: <Extrinsic name="UNSPSC"> 14111506 </Extrinsic> |
Parametric Data ({Name:Value pair}) for example: {UNSPSC = 14111506;} |
|
Expiration |
EXPIRATION_DATE |
EXPIRATION_DATE |
Expiration Date |
ExpirationDate |
Expiration Date |
|
Negotiated by Preparer Indicator |
NEGOTIATED_BY_PREPARER_FLAG |
Specified as an attribute of the PRICE tag. For example: <PRICE negotiated="Y"> |
Negotiated |
||
|
Amount |
AMOUNT |
AMOUNT |
Amount |
||
|
Quantity |
QUANTITY |
QUANTITY |
Quantity |
||
|
Start Date |
START_DATE |
START_DATE |
Start Date |
||
|
End Date |
END_DATE |
END_DATE |
End Date |
||
|
Ship to Organization Code |
SHIP_TO_ORGANIZATION_CODE |
SHIP_TO_ORG |
Ship-To Organization |
||
|
Deliver To |
SHIP_TO_LOCATION_ID |
SHIP_TO_LOCATION |
Ship-To Location |
||
|
Break Price |
PRICE_OVERRIDE |
BREAKPRICE |
Break Price |
||
|
Discount Percent |
PRICE_DISCOUNT |
DISCOUNT |
Discount |
||
|
Packaging String |
PACKAGING_STRING |
NAMEVALUE For example: <NAMEVALUE name="PACKAGING_STRING"> 1/PR 50/BX 200/CA</NAMEVALUE> |
Packaging String |
Extrinsic For example: <Extrinsic name="PACKAGING_STRING"> 1/PR 50/BX 200/CA</NAMEVALUE> |
For example: {PACKAGING_STRING=1/PR 50/BX 200/CA;} |
The upload files also contains columns or tags which are used by the loader process for internal processing. These attributes and the corresponding column name or tag in the different file formats are listed in the following table:
|
Attribute |
XML Tag |
TXT Column |
cXML Tag |
CIF Column |
|---|---|---|---|---|
|
Action |
Specified as an attribute of the ITEM tag. For example: <ITEM action="ADD"> |
Action |
<IndexITemAdd> <IndexItemDelete> |
DELETE |
|
Catalog Name |
name |
Title |
File Name |
File Name |
|
Line Number |
lineNum |
Line Number |
||
|
Language |
Specified as an attribute of the CATALOG tag. For example: <CATALOG xml:lang="en-US"> |
Language Section |
Specified as an attribute of the DESCRIPTION tag. For example: <DESCRIPTION xml:lang="en-US"> |
LANGUAGE |
The Agreement loader also supports:
-
Global Descriptive Flexfields created for line attributes (at the line level). TXT, XML, CIF, and cXML file formats support this
-
Context Sensitive Descriptive Flexfields created as item attributes or as line attributes (created at the Item level or the Line level). Only TXT file format supports this.
The attributes and the corresponding column name or tag in the different file formats to be used for uploading descriptive flexfields are listed in this table:
|
Attribute |
XML Tag |
TXT Column |
cXML Tag |
CIF Column |
|---|---|---|---|---|
|
Item Level Descriptive Flexfield Context |
N/A |
Item Descriptive Flexfield Context |
N/A |
N/A |
|
Item Level Descriptive Flexfield Context Segment |
N/A |
Item Descriptive Flexfield Context Segment |
N/A |
N/A |
|
Line Level Descriptive Flexfield Context |
N/A |
Line Descriptive Flexfield Context |
N/A |
N/A |
|
Line Level Descriptive Flexfield Context Segment |
N/A |
Line Descriptive Flexfield Context Segment |
N/A |
N/A |
|
Global Descriptive Flexfield (Item or Line Level) |
<NAMEVALUE name=""/> The name attribute can either be the Descriptive Flexfield name or Descriptive Flexfield code. For example: <NAMEVALUE name="COLOR"> BROWN </NAMEVALUE> |
{Descriptive Flexfield name or Descriptive Flexfield code |
<Extrinsic name=""/> The name attribute can either be the Descriptive Flexfield name or Descriptive Flexfield code. For example: <Extrinsic name="COLOR"> BROWN </Extrinsic> |
Parametric Data ({Name:Value pair}) The name attribute can either be the Descriptive Flexfield name or Descriptive Flexfield code. For example: {COLOR=Brown;} |
Upload Item or Line Level Context Sensitive Descriptive Flexfields Using the TXT File Format
To upload item or line level context sensitive descriptive flexfields using the TXT file format, you must specify a value for the Context and specify values for the segment using Name value pairs. Here are some of the examples:
Example 1:
You want to upload item level context sensitive descriptive flexfields that has two contexts with two segments each as shown in this table:
|
Context |
Segment 1 |
Segment 2 |
|---|---|---|
|
Dimension |
Width |
Height |
|
Electrical |
Voltage |
Pin |
The TXT upload file of the data mentioned in the above table would look like this:
|
Line Number |
Item |
Item Descriptive Flexfield Context |
Item Descriptive Flexfield Context Segment |
|---|---|---|---|
|
1 |
Computer Stand |
Dimension |
{Width=20;Height=20} |
|
2 |
Laptop |
Electrical |
{Voltage=220;Pin=3} |
Example 2:
If you want to load both a global descriptive flexfield (for example, Color) and the two context sensitive descriptive flexfields mentioned in the example 1 to the item, then a line in the TXT file would look like this:
|
Line Number |
Item |
Item Descriptive Flexfield Context |
Item Descriptive Flexfield Context Segment |
Color |
|---|---|---|---|---|
|
1 |
Laptop |
Electrical |
{Voltage=220;Pin=3} |
Black |
Example 3:
You want to upload line level context sensitive descriptive flexfields that has two contexts with two segments each as shown in this table:
|
Context |
Segment 1 |
Segment 2 |
|---|---|---|
|
Shipping |
FOB Origin |
FOB Destination |
|
Weight |
KG |
Lbs |
The TXT upload file of the data mentioned in the above table would look like this::
|
Line Number |
Item |
Line Descriptive Flexfield Context |
Line Descriptive Flexfield Context Segment |
|---|---|---|---|
|
1 |
6 Piece Dining Table |
Shipping |
{FOB Origin=Maryland;FOB Destination=Cambridge} |
|
2 |
Stained-glass Table Top |
Weight |
{KG=45;Lbs=99} |
Example 4:
If you want to load both a global descriptive flexfield (for example, Material) and the two context sensitive descriptive flexfields mentioned in the example 3 to the line, then a line in the TXT file would look like this:
|
Line Number |
Item |
Item Descriptive Flexfield Context |
Item Descriptive Flexfield Context Segment |
Color |
|---|---|---|---|---|
|
1 |
6 Piece Dining Table |
Shipping |
{FOB Origin=Maryland;FOB Destination=Cambridge} |
Leather |
Example 5:
If both line and item have a global descriptive flexfield with the name Color, the value of Color (Brown) would go to the item descriptive flexfield.
|
Line Number |
Item |
Color |
|---|---|---|
|
1 |
BMW 5 Series |
Brown |