Purchasing Document Publishing and Communication

Purchasing Document Publishing and
Communication
ORACLE WHITE PAPER
FEBRUARY 2015
Table of Contents
Introduction
Oracle Business Intelligence Publisher
Setup
Design/Modify Layout Templates
Obtain Procurement Data Source
Extend the Data Model (New in R9.2)
Create or Modify Layout Templates
Setup Oracle Business Intelligence Publisher
Setup Oracle Fusion Purchasing
Communicate the PDF from Oracle Fusion Purchasing
During Approvals
Schedule Processes
Communicate Dialog
10
Integration with Oracle Fusion Procurement Contracts
10
Conclusion
11
Appendix A - List of XML Fields Applicable to Purchase Orders and Agreements
11
Appendix B - Sample XML for Draft Purchase Orders
27
Appendix C - Sample XML for Archived Purchase Orders
46
Appendix D - Sample XML for Draft Purchase Agreements
65
Appendix E - Sample XML for Archived Purchase Agreements
78
1 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION
Introduction
Purchase orders and blanket agreements between buying organizations and suppliers have been in
existence for a long time, and as such, certain standards have developed regarding common terms,
conditions, and details that these documents must contain. However, every organization has its own
business requirements that further define the format of these documents. Also, certain industries may
require additional attributes that need to be communicated and agreed upon between the buying
organization and their suppliers. Essentially, there is no single format for these documents that can
satisfy all organizations and business practices.
In order to address the individual business requirements governing the procurement information to be
shared with suppliers, Oracle Fusion Purchasing provides a document publishing solution that is
flexible and easy to implement. By leveraging the capabilities provided by Oracle Business Intelligence
Publisher, buying organizations can quickly create professional looking documents that satisfy all of
their needs.
The purpose of this document is to provide customers with the information they need to create and
modify Rich Text Format (RTF) or Adobe Portable Document Format (PDF) templates that are used to
generate purchasing documents. This document also outlines the various methods that can be used to
deliver these documents to suppliers based on the preferred communication method postal mail, fax
or email.
The information in this document is meant to supplement the collateral developed by Oracle Business
Intelligence Publisher. Please visit the following location to access these materials:
http://www.oracle.com/technetwork/middleware/bi-publisher/overview/index.html
Oracle Business Intelligence Publisher

Figure 1 represents the fundamental concept behind procurement document publishing. You design your layout
using tools provided by Oracle Business Intelligence Publisher, capture procurement data in Oracle Fusion
Purchasing and utilize the Oracle Business Intelligence Publisher engine to merge the layout with the data structure
to generate a document output in Adobe PDF format. Oracle Business Intelligence Publisher Desktop, a tool that
extends Microsoft Word, simplifies the process of designing layouts.
Figure 1. Document Publishing Fundamental Concept
Setup
The following setup steps are needed to enable and implement document publishing in Oracle Fusion Purchasing.
The next sections will describe each further.
Before you begin working with reports in Oracle Business Intelligence Publishing, refer to the following resources to
familiarize yourself with the Customize feature. The Customize feature allows you to leverage prepackaged reports
without making modifications to those reports that can be lost during patching or upgrade.
Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher Appendix G (Using the
Customize Feature)
YouTube Video posted by Oracle Learning Library titled BI Publisher Extensibility Training - BIP Customize
Feature

Oracle Fusion Purchasing provides prepackaged reports to generate the PDF documents that are communicated to
suppliers. These prepackaged reports include the Purchase Document PDF Report (applicable only for releases
prior to 9.2), the Purchase Order PDF Report, and the Purchase Agreement PDF Report. The Purchase Order PDF
Report and the Purchase Agreement PDF Report are available starting in Release 9.2 and should be used instead
of the Purchase Document PDF Report. As shown in Figure 1 above, these reports comprise of a procurement data
source and a layout template.
Obtain Procurement Data Source
The procurement data source (represented as an XML) can either be obtained from the XML files located at the end
of this document, or, starting in Release 9.2, directly from Oracle Business Intelligence Publisher. There are 2 ways
to extract the data source from Oracle Business Intelligence Publisher:
1. If you have the BI Publisher Data Model Developer role, you can find the data models in the following path:
Catalog > Shared Folders > Procurement > Purchasing > Data Models. There is a data model for Purchase
Orders and a separate one for Purchase Agreements. You can export the data source from these data models by
navigating to Edit > Data (tab). Specify values for the parameters (mentioned at the end of this section) and then
select View to see the XML. Use the Export button to save the XML.
2. Click View
3. Click Export
1. Enter Parameters
Figure 2. Export Data Source from Data Model
2. Alternatively, you can extract the data source from the provided reports. You will first need to enable XML as an
output parameter for the layout. You can do this by following these steps:
Navigate to Catalog > Shared Folders > Procurement > Purchasing, create a custom copy of the report you
want to work with and then click Edit from the custom version you just created (placed in the Custom >
Procurement > Purchasing folder by default).
Select View a List
Figure 3. Access List View of Layout
In the Output Formats dropdown, select Data (XML)
Figure 4. Set XML as Output Format for Layout
Open the report using either the Report Viewer (View Report button) or navigate to Open > Shared Folders >
Custom > Procurement > Purchasing. Note: To enable the View Report button, you may need to set the
Properties of the report as follows:
Figure 5. Enable Report Viewer
Enter values for the parameters (described below) and once the results are displayed, navigate to Actions >
Export > Data. You will be prompted to save the data source as an XML file.
1. Select Actions
2. Select Export
3. Choose Data
Figure 6. Export Data Source from Report
Whether you use option 1 or option 2 to obtain the data source, you will need to provide values for these parameters
to generate the corresponding XML file for purchase orders:
Sold-to LE
Document Number
Change Order Number
Is Document in Draft Status? (Y/N)
To extract sample data from the purchase agreement data model, you will need to provide values for these
parameters:
Procurement BU
Document Number
Change Order Number
Is Document in Draft Status? (Y/N)
Extend the Data Model (New in R9.2)
If you need to include fields that are not part of the seeded data model, you can leverage Oracle Business
Intelligence Publisher to edit the data model before generating the XML data source. For example, you might want
to include Supplier Contact Title in your purchasing document. Refer to the online help for further instructions on
working with data models, editing data sets and how you can join to other tables to access those fields. You can
access this help from the Get Started region of the Home page. You will need the BI Publisher Data Model
Developer role to make these modifications. Be sure to copy the data model to the Custom folder before making
modifications. Once you make your changes to the data model, ensure that the report points to your modified data
model for the changes to take effect.
Create or Modify Layout Templates
Once you have obtained the data source, you will need a layout to use with the data source. There are two layout
template types that are supported with the Oracle Fusion Purchasing prepackaged reports. The following table
describes the differences between these types.
LAYOUT TEMPLATE TYPES SUPPORTED IN ORACLE FUSION PURCHASING
Format
Usage
Rich Text Format

(RTF)
Oracle Business Intelligence Publisher provides a plug-in utility for Microsoft Word that automates layout design and enables you to
upload templates directly from a Microsoft Word session. The RTF format also supports advanced formatting commands providing the
most flexible and powerful of the layout options. RTF templates support only PDF outputs in Oracle Fusion Purchasing.
Portable Document
Format (PDF)
PDF templates are used primarily when you must use a predefined form as a layout for a report (for example, a form provided by a
government agency). Because many PDF forms already contain form fields, using the PDF form as a template simply requires mapping
data elements to the fields that exist on the form. You can also design PDF templates using Adobe Acrobat Professional. PDF templates
support only PDF output.
You can either design your own RTF/PDF layout template or you can download one of the RTF templates provided
in the prepackaged reports and make modifications based on your business requirements.
To download one of the prepackaged reports, navigate to Catalog > Shared Folders > Procurement > Purchasing,
create a custom copy of the report you want to download and then click Edit from the custom version you just
created (placed in the Custom > Procurement > Purchasing folder by default). You may find it easier to work with
one of the prepackaged reports to make your modifications if the change is simple. For example, you might want to
add a field that isnt shown on the seeded report, such as Supplier Contact Email Address or Requester MailStop.
If you are using RTF templates, Oracle Business Intelligence Publisher integrates with MS Word to simplify the
creation/modification of RTF templates. You will need to download the Oracle Business Intelligence Publisher
Template Builder and install it on the client. The Template Builder can be downloaded from the Get Started region
of the Home page. The data source obtained in previous steps will serve as the local XML file that is loaded into MS
Word. For further instructions on working with RTF templates, refer to Chapter 5, Section 5.1 (Creating RTF
Templates Using the Template Builder for Word - Overview) of the Fusion Middleware Report Designer's Guide for
Oracle Business Intelligence Publisher.
If you are using PDF templates, refer to Chapter 7 (Creating PDF Templates) of the Fusion Middleware Report
Designer's Guide for Oracle Business Intelligence Publisher for step-by-step instructions.
Once youve created or modified your layouts, you will need to upload them to the appropriate report in the custom
folder. Do not modify the name of the report when you copy it to the custom folder. Refer to Chapter 2, Section 2.6.2
(Creating and Editing Reports - Adding a Layout by Uploading a Template File) of the Fusion Middleware Report
Designer's Guide for Oracle Business Intelligence Publisher for instructions.

After the layouts are uploaded to Oracle Business Intelligence Publisher, you will need to configure the email, print
and/or fax servers you plan on using to communicate the purchasing documents. Refer to Chapter 11 (Setting Up
Delivery Destinations) of the Administrator's Guide for Oracle Business Intelligence Publisher for details.

1. Login to Oracle Fusion Purchasing with the Procurement Applications Administrator role
2. Navigate to Tools > Setup and Maintenance
3. Launch the Configure Procurement Business Function Task
4. Select the Procurement Business Unit you want to configure
5. On the Document Types tab, select the document type and then choose the correct layout for the document. The
layouts from both the custom folder and the seeded folder will appear in this list.
Figure 7. Configure Procurement Business Function for a Business Unit
The table below shows the seeded layout corresponding to each document type:
SEEDED LAYOUTS FOR PURCHASING DOCUMENT TYPES
Document Type
Document Layout
Purchase Order
Purchase Order Layout
Blanket Purchase Agreement
Purchase Agreement Layout
Contract Purchase Agreement
Purchase Agreement Layout
Communicate the PDF from Oracle Fusion Purchasing

Once the appropriate servers are configured in Oracle Business Intelligence Publishing, you can communicate the
PDF to the supplier using any of the following methods:
During Approvals
Launching using Schedule Processes
Launching the communicate dialog when viewing documents online
During Approvals
If the system is defined to communicate purchasing documents as part of the approval process, the documents will
be communicated to the supplier using the method specified on the purchasing document. However, if the supplier
site is configured for B2B communication, the system will deliver the document through electronic messaging, rather
than the method specified on the document. The method specified on the document will be used in Schedule
Processes and the Communicate Dialog.
Schedule Processes
When using this program to communicate purchasing documents, you can either communicate a single document or
a group of documents. The documents will be communicated to the supplier using the method specified on the
purchasing document. If the communication method on the document is set to Print, you can optionally specify a
different printer to use.
Figure 8. Communicate Purchasing Documents Dialog
1. Login to Oracle Fusion Purchasing with the Procurement Applications Administrator role
2. Navigate to Administration > Communicate Purchasing Documents
3. Click Submit New Process
4. Select the Procurement Business Unit
5. Indicate which documents you want to communicate: New documents, Changed documents, both New and
Changed documents, or Specified (a specific document)
6. If you choose Specified, enter the Sold-to BU and the Document Number/Change Order corresponding to the
document you want to communicate
7. Otherwise, indicate the type of document(s) you want to communicate: Purchase Order, Blanket Purchase
Agreement or Contract Purchase Agreement
8. Further filter the list of documents you want to communicate by specifying any of the following: Buyer, Supplier,
Supplier Site
9. Submit the process
Communicate Dialog
You can also choose to communicate a purchasing document while viewing it online. This is a useful option when
the original method of communication (either during approval or through the Schedule Processes program) fails.
When you perform this action, you have the option of communicating the document using the method identified on
the purchasing document, or you can change the method (e.g. email), the destination (e.g. email address), and the
preferred language for single use. The defaulting order for the preferred language is supplier site, procurement BU,
and finally, the base language of the application instance.
Figure 9. Communicating Documents using the Communicate Action/Dialog
Integration with Oracle Fusion Procurement Contracts
If you have Oracle Fusion Procurement Contracts installed, any terms associated with the purchasing document will
be included with the main document, resulting in a single document that is communicated to the supplier.
Each purchasing document type must be associated with the appropriate contract terms layout, just like each
document type is associated with a document layout. This is achieved through the Configure Procurement Business
Function for the business unit.
The table below shows the seeded contract terms layout associated with each document type:
SEEDED LAYOUTS FOR USE WITH ORACLE FUSION PROCUREMENT CONTRACTS
Document Type
Document Layout
Purchase Order
Oracle Contract Terms Template
Blanket Purchase Agreement
Contract Purchase Agreement
If you need to customize this template, you can find the prepackaged report in the following path: Oracle Business
Intelligence Publisher > Catalog > Enterprise Contracts > Contract Terms Printing > Contract Terms Download and
Preview.
Conclusion
Oracle Business Intelligence Publisher combined with Oracle Fusion Purchasing provide a highly efficient publishing
solution. This allows organizations to create procurement documents that are professional looking and satisfy the
specific needs of the organization.
Appendix A - List of XML Fields Applicable to Purchase Orders and Agreements

These next few sections provide the XML files needed as sample data to create your layout templates. These files
are only needed for versions prior to Release 9.2.
Note: There may be fields in the sample XML files that are not listed here. Those fields are needed for the
conditional logic built into the seeded templates.
AVAILABLE XML FIELDS
Header - General
XML Attribute
Description
Segment1
The display number used to identify a purchase order/purchase agreement.
RevisionNum
The display number used to identify a purchase order/purchase agreement revision.
CustomerNum
The suppliers identification number for the buying organization.
VendorOrderNum
The suppliers order number corresponding to the buying organizations purchase

order/purchase agreement.
SupplierNumber
The suppliers order number corresponding to the buying organizations purchase

DocumentStyle
The style associated with the document. Document styles allow buying organizations to control
the look and feel of purchasing documents to suit various types of purchases. For example,
buying organizations can create a document style geared towards buying services rather than
items. This would allow certain item-specific fields (such as item revision).
Tax Registration Number
The unique display number assigned to the sold-to legal entity by a tax authority in order to
manage tax liabilities. This field is applicable to purchase orders only.
ChangeOrderNum
The unique identifier of a purchasing document change order. This field is applicable to change
orders only.
ChangeOrderDesc
A text description capturing the reason or purpose of the change order. This field is applicable
to change orders only.
Header - Terms
XML Attribute
Description
AcceptanceRequiredFlag
A flag indicating that the supplier must agree to and accept the terms of the purchase
AcceptanceDueDate
The date by which the supplier should indicate acceptance of the purchase order/purchase
agreement.
CarrierPartyName
The display name of a company that transports goods from one point to another by land, sea,
or air.
ModeOfTransportName
Type of transportation used to ship the product, such as truck, air or boat. New in Release 9.
ServiceLevelName
Priority of transportation that affects how quickly goods are transported. New in Release 9.
Fob
Freight (or Free) on Board: The point or location where the ownership title of goods is
transferred from the supplier to the buyer.
FreightTerms
Additional terms governing transportation of the goods from one location to another.
PaymentTermsName
The conditions under which the supplier will accept payment.
PayOnCode
Indicates whether the supplier accepts payment upon the buying organizations receipt of the
goods.
TermsAndConditions
Corresponds to the Terms & Conditions defined for Procurement Business Unit. This field does
not depend on Oracle Fusion Procurement Contracts.
AgingOnsetPointValue
Indicates the mutually agreed event point at which consigned material begins to age.
Consigned material are those that are in the possession of one party (for example, customers,
dealers, agents) but remain the property of another party (for example, the manufacturer) by
agreement with those in possession. The possible values for aging onset point are: None,
Receipt and Shipment. New in Release 9. This field is applicable to agreements only.
AgingPeriodDays
Indicates the maximum number of days the material may be consigned. New in Release 9. This
field is applicable to agreements only.
ConsumptionAdviceSummaryValue
Indicates the granularity at which consumption advices will be generated. A consumption

advice is a periodic report of the consumed inventory that was under consignment so far,
generated by the buyer and sent to the seller.The possible values for consumption advice
summary are Organization, Item and Transaction Date, Organization and Item, Organization
and All Organizations. New in Release 9. This field is applicable to agreements only.
ConsumptionAdviceFrequencyValue
Indicates the default value of the frequency at which the consumption advice will be generated
for all consumption transactions for consigned inventory purchased under this agreement. A
consumption advice is a periodic report of the consumed inventory that was under consignment
so far, generated by the buyer and sent to the seller. The possible values for consumption
advice frequency are Daily, Weekly and Monthly. New in Release 9. This field is applicable to
agreements only.
PayOnUseValue
This attribute determines whether to generate invoices automatically on behalf of the supplier
when supplier owned material stocked in buying organization's premise is consumed by the
buying organization. New in Release 9. This field is applicable to agreements only.
Header - Amounts
XML Attribute
Description
OrderedDisplay
The total amount of the purchase order. This field is applicable to purchase orders only.
OriginalOrderAmountDisplay
The original total amount of the purchase order.
AmountChangeDisplay
Represents the total amount changed from the previous active purchase order. This field is
applicable to purchase order change orders only.
TotalTaxDisplay
This field is applicable to purchase orders only.
RecoverableTaxDisplay
NonRecoverableTaxDisplay
BlanketTotalAmountDisplay
A value that represents the total amount expected to be released on purchase orders over the
lifetime of the agreement. This field is applicable to agreements only.
AmountLimit
A value that represents the maximum amount across all purchase orders that can be released
against the purchase agreement. This field is applicable to agreements only.
MinReleaseAmount
A value that indicates the minimum amount that can be released on a purchase order. This
PriceUpdateTolerance
The tolerance that governs price increases for future changes to the agreement. This field is
applicable to agreements only.
Header - Contacts
XML Attribute
Description
PersonName
The display name of a buyer specified on the document.
PersonEmailAddress
The email address for a buyer specified on the document.
PersonWorkPhone
The phone number for a buyer specified on the document.
PersonFax
The fax for a buyer specified on the document.
SupplierContactPartyName
The display name of a supplier employee who represents the supplier in communications with
the buying organization.
SupplierContactEmailAddress
The email address for a supplier employee who represents the supplier in communications with
the buying organization.
SupplierContactPhone
The phone number for a supplier employee who represents the supplier in communications
with the buying organization.
SupplierContactFax
The fax for a supplier employee who represents the supplier in communications with the buying
organization.
Requester
The display name of a requester. All fields related to the requesters contact details are
applicable to purchase orders only.
RequesterEmail
The email address for a requester.
RequesterPhoneNumber
The phone number for a requester.
RequesterFaxNumber
The fax for a requester.
Header - Addresses
XML Attribute
Description
ProcurementBuName
The display name of the business unit that manages, owns, and is responsible for the
purchasing transactions in an organization, including the creation and management of the
purchasing document that is communicated to the supplier. All fields related to the
Procurement BU are applicable to agreements only.
ProcBuAddress
A single field that captures all address information, separated by line breaks
ProcBuAddressLine1
ProcBuAddressLine2
ProcBuAddressLine3
ProcBuAddressLine4
ProcBuBuilding
ProcBuFloorNumber
ProcBuTownOrCity
ProcBuRegion1
ProcBuRegion2
ProcBuRegion3
ProcBuCountry
ProcBuPostalCode
ProcBuLongPostalCode
ProcBuAddlAddressAttribute1
The fields related to Sold-to BU are no longer applicable from Release 9 onwards.
SoldToBuName
The display name of the business unit responsible for the payment transactions resulting from
the purchasing transaction. All fields related to the Sold-to BU are applicable to purchase
orders only.
SoldToBuAddress
SoldToBuAddressLine1
SoldToBuBuilding
SoldToBuFloorNumber
SoldToBuTownOrCity
SoldToBuRegion1
SoldToBuRegion2
SoldToBuRegion3
SoldToBuCountry
SoldToBuPostalCode
SoldToBuLongPostalCode
SoldToBuAddlAddressAttribute1
SoldToLeName
The display name of the legal entity associated with the Sold-to Business Unit. All fields related
to the Sold-to LE are applicable to purchase orders only.
SoldToLeAddress
SoldToLeAddressLine1
SoldToLeTownOrCity
SoldToLeStateProvn
SoldToLeRegion1
SoldToLeRegion2
SoldToLeRegion3
SoldToLeCountry
SoldToLePostalCode
BillToBuName
The business unit that processes supplier invoices for the purchase order. New in Release 9.
BillToLocationName
The display name of the location to where the supplier should send the invoices. All fields
related to the Bill-to Location are applicable to purchase orders only.
BillToAddress
BillToLocAddressLine1
BillToLocBuilding
BillToLocFloorNumber
BillToLocRegion1
BillToLocRegion2
BillToLocRegion3
BillToLocCountry
BillToLocPostalCode
BillToLocTownOrCity
BillToLocLongPostalCode
BillToLocAddlAddressAttribute1
LineLocShipToLocationName
The display name of the location to where the supplier should ship the goods. All fields related
to the Ship-to Location are applicable to purchase orders only.
LineLocShipToAddress
ShipToLocAddressLine1
ShipToLocBuilding
ShipToLocFloorNumber
ShipToLocTownOrCity
ShipToLocRegion1
ShipToLocRegion2
ShipToLocRegion3
ShipToLocCountry
ShipToLocPostalCode
ShipToLocLongPostalCode
ShipToLocAddlAddressAttribute1
SupplierPartyName
The display name of an organization or individual that provides goods or services to the buying
organization for payment, bound by a contractual obligation.
SupplierAddress
SupplierSiteAddress1
SupplierSiteBuilding
SupplierSiteFloorNumber
SupplierSiteCity
SupplierSiteProvince
SupplierSiteCounty
SupplierSiteState
SupplierSiteCountry
SupplierSitePostalCode
SupplierSitePostalPlus4Code
SupplierSiteAddrElementAttribute1
RequesterAddressLine1
RequesterAddressFloorNumber
RequesterAddressBuilding
RequesterAddressTownOrCity
RequesterAddressRegion1
RequesterAddressCountry
RequesterAddressPostalCode
RequesterAddressLongPostalCode
RequesterAddlAddressAttr1
Header Flags & Codes
All fields related to the requesters address are applicable to purchase orders only.
XML Attribute
Description
TypeLookupCode
Possible values include: Standard, Blanket, Contract
CurrencyCode
A code indicating the three-letter ISO code associated with a currency.
CurrencyName
The display name of the three-letter ISO code associated with a currency.
HeaderCancelFlag
A flag indicating document cancellation. This field is applicable to change orders only.
HeaderCoCanceledFlag
A flag indicating cancellation of a change order. This field is applicable to change orders only.
ConfirmingOrderFlag
A flag indicating that the order or agreement is a confirmation of a previous informal agreement
with the supplier.
ContermsExistFlag
A flag indicating that contract terms defined in Oracle Fusion Procurement Contracts have
been applied to the document.
DocumentCreationMethod
The method in which the document was created. Possible values include: COPY_DOCUMENT,
AWARD_SOURCING, PDOI, AUTOCREATE, CREATEDOC, PO_WEB_SERVICE,
ENTER_PO
Header Dates & Text Fields

XML Attribute
Description
OrderDateDisplay
The day the purchase order was first communicated, acknowledged, or implemented.
ChangeOrderDateDisplay
The day the change order was first communicated, acknowledged, or implemented.
CreationDate
The date the purchasing document was created
StartDate
The date that the purchase agreement becomes effective. This field is applicable to
agreements only.
EndDate
The date corresponding to when the agreement expires. This field is applicable to agreements
only.
Comments
A text description of the purchase order/purchase agreement
Header Notes, Attachments & Flexfields

XML Attribute
Description
HeaderNoteToVendor
A text description capturing the instructions to the supplier.
HeaderNoteToAuthorizer
A text description capturing the instructions to the approver.
HeaderNoteToReceiver
A text description capturing the instructions to the receiver in the docking area to be reviewed
while performing the receipt.
File and URL attachments are supported at this level refer to the sample XMLs in this whitepaper for appropriate syntax
AttributeCategory
Related to descriptive flexfields (DFF)
Attribute1-20
AttributeDate1-10
AttributeTimestamp1-10
AttributeNumber1-10
GlobalAttributeCategory
GlobalAttribute1-20
Lines General
XML Attribute
Description
LineNum
The display number used to identify a purchase order/purchase agreement line.
ItemNumber
The display number of an item representing anything you make, purchase, or sell, including
components, subassemblies, finished products, or supplies.
ItemRevision
The identifier of an inventory item version being referenced on an order line.
ItemDescription
A text description capturing details about the item being purchased.
VendorProductNum
The display name of a supplier's identification number or code for the goods ordered on your
order/agreement line.
LineType
The display name of a line type that indicates whether a purchase is for goods or services.
Segment1
The display number used to identify a purchase order/purchase agreement.
BlanketHeaderDocNumber
The blanket purchase agreement referenced on the line. This field is applicable to purchase
orders only.
ContractHeaderDocNumber
The contract purchase agreement referenced on the line. This field is applicable to purchase
orders only.
SupplierRefNumber
A tracking code provided by the supplier for a specific configuration of a requested item. This
field is applicable to purchase orders only.
ManufacturerPartNumber
SupplierPartAuxid
The suppliers alternate part number or identifier for the item.
AgingPeriodDays
Indicates the maximum number of days the material may be consigned. New in Release 9. This
Lines Quantitites, UOM, Prices & Amounts

XML Attribute
Description
Quantity
The ordered quantity for the purchase order line. This field is applicable to purchase orders
only.
UnitOfMeasure
The display name of a division of quantity defined as a standard of measurement or exchange.
UomCode
A code indicating the division of quantity defined as a standard of measurement or exchange.
QuantityCommitted
The quantity that the buying organization has committed to purchase. This field is applicable to
agreements only.
BaseUom
The base unit of measure (UOM) for the item ordered. This field is applicable to purchase
orders only.
BaseQty
The ordered quantity converted from the transaction UOM to base UOM. This field is applicable
to purchase orders only.
UnitPrice
The price of the item on the document line.
NotToExceedPrice
The price limit that cannot be exceeded on purchase orders released against this agreement
line. This field is applicable to agreements only.
MinReleaseAmount
A value that indicates the minimum amount that can be released against this agreement line.
This field is applicable to agreements only.
CommittedAmount
A value that represents the total amount expected to be released against this agreement line.
This field is applicable to agreements only.
CancelledAmountDisplay
This field is applicable to purchase order change orders only.
AmountDisplay
The total amount of the line.
OriginalAmountBeforeCancellationDisplay
This field is applicable to purchase order change orders only.
Lines Flags & Codes

XML Attribute
Description
LineCancelFlag
This field is applicable to change orders only.
AllowPriceOverrideFlag
Indicates whether the price on a purchase order line released against the agreement can differ
from the agreement line price. This field is applicable to agreements only.
PriceBreakLookupCode
Refers to whether the price breaks defined for the line should be applied cumulatively or noncumulatively. This field is applicable to agreements only.
UnNumber
The display name of a United Nations identification number for the hazardous material.
UnNumberDescription
The text description of a United Nations identification number for the hazardous material.
HazardClass
The display name of a classification of hazardous materials, to facilitate safety regulations

compliance.
PurchaseBasis
Possible values include: Goods, Services
Lines Dates & Text Fields

XML Attribute
Description
ExpirationDate
Date after which the item can no longer be ordered. This field is applicable to agreements only.
CancelDate
CancelReason
A text description capturing user entered comments provided during a cancellation request.
Lines Notes, Attachments & Flexfields

XML Attribute
Description
LineNoteToVendor
A text description capturing the instructions to the supplier.
TextAttachmentsContent
Short text attachment at line
AttributeCategory
Attribute1-20
AttributeDate1-10
AttributeNumber1-10
GlobalAttribute1-20
Shipments/Schedules General (Applicable to Purchase Orders Only)

XML Attribute
Description
ShipmentNum
The display number used to identify a purchase order schedule.
SupplierOrderLineNumber
The display number of the document line that the supplier has created in its system against a
purchase order schedule.
CarrierName
The display name of a company that transports goods from one point to another by land, sea,
or air. New in Release 9.
Type of transportation used to ship the product, such as truck, air or boat.
ModeOfTransportName
New in Release 9.
ServiceLevelName
Priority of transportation that affects how quickly goods are transported. New in Release 9.
Shipments/Schedules Quantities, UOM, Prices & Amounts

XML Attribute
Description
QuantityDisplay
The ordered quantity for the purchase order schedule.
UnitOfMeasure
UomCode
SecondaryQuantity
The quantity converted in the secondary unit of measure of a dual UOM controlled item.
SecondaryUnitOfMeasure
The display name of an alternative unit of measure that is allowed to quantify a dual UOM
controlled item.
SecondaryUomCode
A code indicating the alternative unit of measure that is allowed to quantify a dual UOM
controlled item.
PriceOverride
The unit price associated with the schedule.
AmountDisplay
The total amount associated with the schedule.
DaysEarlyReceiptAllowed
The maximum acceptable number of days early for receipts.
DaysLateReceiptAllowed
The maximum acceptable number of days late for receipts.
QuantityCancelled
CancelledAmountDisplay
OriginalAmountBeforeCancellationDisplay
Shipments/Schedules Addresses
XML Attribute
Description
LineLocShipToLocationName
The display name of the location to where the supplier should ship the goods.
LineLocShipToAddress
ShipToLocBuilding
ShipToLocPostalCode
ShipToLocRegion1
ShipToLocRegion2
ShipToLocRegion3
ShipToLocTownOrCity
ShipToLocCountry
Shipments/Schedules Flags & Codes

XML Attribute
Description
ScheduleCancelFlag
TaxableFlag
CountryOfOriginCode
Shipments/Schedules Dates & Text Fields

XML Attribute
Description
NeedByDate
The day that the buying company has requested that the supplier deliver the item.
PromisedDate
The day that the supplier has promised to deliver the ordered item.
CancelDate
CancelReason
A text description capturing user entered comments provided during a cancellation request.
This field is applicable to change orders only
Shipments/Schedules Notes, Attachments & Flexfields

XML Attribute
Description
ScheduleNoteToReceiver
A text description capturing the instructions to the receiver in the docking area to be reviewed
while performing the receipt.
TextAttachmentsContent
Short text attachment at schedule
AttributeCategory
Attribute1-20
AttributeDate1-10
AttributeNumber1-10
GlobalAttribute1-20
Distributions General (Applicable to Purchase Orders Only)

XML Attribute
Description
DistributionNum
The display number used to identify a purchase order distribution.
DestinationSubinventory
The display name of a subinventory to which the requested item should be delivered.
Distributions Quantities, UOM & Amounts

XML Attribute
Description
QuantityOrdered
The ordered quantity for the purchase order distribution.
UnitOfMeasure
UomCode
AmountOrderedDisplay
The total amount associated with the distribution.
Distributions Contacts
XML Attribute
Description
Requester
The display name of a requester.
RequesterPhoneNumber
The phone number for a requester.
RequesterEmailAddress
The email address for a requester.
RequesterFaxNumber
The fax for a requester.
Distributions Addresses
XML Attribute
RequesterAddressFloorNumber
Description
RequesterAddressBuilding
RequesterMailstop
RequesterAddressTownOrCity
RequesterAddressCountry
RequesterAddressPostalCode
RequesterAddressLongPostalCode
RequesterAddressAddlAddressAttribute1
DeliverToLocAddressLine1
The final location where the purchased items are delivered.
DeliverToLocFloorNumber
DeliverToLocBuilding
DeliverToLocTownOrCity
DeliverToLocRegion1
DeliverToLocRegion2
DeliverToLocRegion3
DeliverToLocCountry
DeliverToLocPostalCode
DeliverToLocLongPostalCode
DeliverToLocAddlAddressAttribute1
Distributions Flexfields
XML Attribute
Description
AttributeCategory
Attribute1-20
AttributeDate1-10
AttributeNumber1-10
Line Item Attributes Applicable to Blanket Purchase Agreements Only

XML Attribute
Description
Description
A translatable text description capturing details about the item being purchased.
LongDescription
A translatable text long description capturing details about the item being purchased.
SupplierUrl
Manufacturer
ManufacturerUrl
ManufacturerPartNum
AttachmentUrl
Alias
LeadTime
Unspsc
ThumbnailImage
The URL corresponding to the thumbnail image.
Picture
The URL corresponding to the image.
Availability
Comments
Price Breaks General (Applicable to Blanket Purchase Agreements Only)

XML Attribute
Description
ShipmentNum
The display number used to identify a price break line.
Price Breaks Quantitites, UOM & Prices

XML Attribute
Description
Quantity
The quantity needed to purchase in order to receive the discounted price.
UnitOfMeasure
UomCode
PriceOverride
The break price expressed as a price.
PriceDiscount
The break price expressed as a percentage discount.
Price Breaks Addresses
XML Attribute
Description
ShipToLocationName
The name of the location for which the price break applies.
ShipToAddress
A single field that captures all address information, separated by line breaks.
ShipToLocBuilding
ShipToLocPostalCode
ShipToLocRegion1
ShipToLocRegion2
ShipToLocRegion3
ShipToLocTownOrCity
ShipToCountry
Price Breaks Dates

XML Attribute
Description
PriceBreakStartDate
The day that the break price takes effect.
PriceBreakEndDate
The day that the break price expires.
Price Breaks Flexfields

XML Attribute
Description
AttributeCategory
Attribute1-20
AttributeDate1-10
AttributeNumber1-10
GlobalAttribute1-20
Appendix B - Sample XML for Draft Purchase Orders

<PdfDraftPurchaseOrderHeaderVO>
<PdfDraftPurchaseOrderHeaderVORow>
<Segment1>1001183</Segment1>
<RevisionNum>0</RevisionNum>
<CustomerNum>11</CustomerNum>
<VendorOrderNum>ABCD1000603</VendorOrderNum>
<SupplierNumber>1011</SupplierNumber>
<DocumentStyle>Purchase Order</DocumentStyle>
<TaxRegistrationNumber>SYS12125</TaxRegistrationNumber>
<ChangeOrderNum>1</ChangeOrderNum>
<ChangeOrderDesc>Change</ChangeOrderDesc>
<AcceptanceRequiredFlag>N</AcceptanceRequiredFlag>
<AcceptanceDueDate>1987-01-01</AcceptanceDueDate>
<CarrierPartyName>1158NAME</CarrierPartyName>
<Fob>Origin</Fob>
<FreightTerms>Due</FreightTerms>
<PaymentTermsName>45 Net</PaymentTermsName>
<PayOnCode>RECEIPT</PayOnCode>
<TermsAndConditions>A</TermsAndConditions>
<OrderedDisplay>2,000.00</OrderedDisplay>
<AmountChangeDisplay>0.00</AmountChangeDisplay>
<OriginalOrderAmountDisplay>2,000.00</OriginalOrderAmountDisplay>
<TotalTaxDisplay>0.00</TotalTaxDisplay>
<RecoverableTaxDisplay>0.00</RecoverableTaxDisplay>
<NonRecoverableTaxDisplay>0.00</NonRecoverableTaxDisplay>
<PersonName>Clare Furey</PersonName>
<PersonEmailAddress>cf@email.com</PersonEmailAddress>
<PersonWorkPhone>1234</PersonWorkPhone>
<PersonFax>1234</PersonFax>
<SupplierContactPartyName>Clare Furey</SupplierContactPartyName>
<SupplierContactEmailAddress>cf@email.com</SupplierContactEmailAddress>
<SupplierContactPhone>1234</SupplierContactPhone>
<SupplierContactFax>1234</SupplierContactFax>
<Requester>Clare Furey</Requester>
<RequesterEmail>cf@email.com</RequesterEmail>
<RequesterPhoneNumber>1234</RequesterPhoneNumber>
<RequesterFaxNumber>1234</RequesterFaxNumber>
<SoldToBuName>Vision Operations</SoldToBuName>
<SoldToBuAddress>475 Park Avenue New York, NY 10022 New York UNITED
STATES</SoldToBuAddress>
<SoldToBuAddressLine1>475</SoldToBuAddressLine1>
<SoldToBuBuilding>1</SoldToBuBuilding>
<SoldToBuFloorNumber>1</SoldToBuFloorNumber>
<SoldToBuTownOrCity>New York</SoldToBuTownOrCity>
<SoldToBuRegion1>New York</SoldToBuRegion1>
<SoldToBuRegion2>NY</SoldToBuRegion2>
<SoldToBuCountry>US</SoldToBuCountry>
<SoldToBuPostalCode>10022</SoldToBuPostalCode>
<SoldToBuLongPostalCode>10022</SoldToBuLongPostalCode>
<SoldToBuAddlAddressAttribute1>475</SoldToBuAddlAddressAttribute1>
<SoldToLeName>Vision Operations</SoldToLeName>
<SoldToLeAddress>475 Park Avenue New York, NY 10022 New York UNITED

STATES</SoldToLeAddress>
<SoldToLeAddressLine1>475</SoldToLeAddressLine1>
<SoldToLeTownOrCity>New York</SoldToLeTownOrCity>
<SoldToLeRegion1>New York</SoldToLeRegion1>
<SoldToLeRegion2>NY</SoldToLeRegion2>
<SoldToLeCountry>US</SoldToLeCountry>
<SoldToLePostalCode>10022</SoldToLePostalCode>
<SoldToLeStateProvn>NY</SoldToLeStateProvn>
<BillToLocationName>V1- New York City</BillToLocationName>
<BillToAddress>90 Fifth Avenue New York, NY 10022-3422 New York UNITED
STATES</BillToAddress>
<BillToLocAddressLine1>475</BillToLocAddressLine1>
<BillToLocBuilding>1</BillToLocBuilding>
<BillToLocFloorNumber>1</BillToLocFloorNumber>
<BillToLocTownOrCity>New York</BillToLocTownOrCity>
<BillToLocRegion1>New York</BillToLocRegion1>
<BillToLocRegion2>NY</BillToLocRegion2>
<BillToLocCountry>US</BillToLocCountry>
<BillToLocPostalCode>10022</BillToLocPostalCode>
<BillToLocLongPostalCode>10022</BillToLocLongPostalCode>
<BillToLocAddlAddressAttribute1>475</BillToLocAddlAddressAttribute1>
<LineLocShipToLocationName>M1- Seattle Mfg</LineLocShipToLocationName>
<LineLocShipToAddress>3455 108th Avenue Seattle, WA 98101 King UNITED
STATES</LineLocShipToAddress>
<ShipToLocAddressLine1>475</ShipToLocAddressLine1>
<ShipToLocBuilding>1</ShipToLocBuilding>
<ShipToLocFloorNumber>1</ShipToLocFloorNumber>
<ShipToLocTownOrCity>New York</ShipToLocTownOrCity>
<ShipToLocRegion1>New York</ShipToLocRegion1>
<ShipToLocRegion2>NY</ShipToLocRegion2>
<ShipToLocCountry>US</ShipToLocCountry>
<ShipToLocPostalCode>10022</ShipToLocPostalCode>
<ShipToLocLongPostalCode>10022</ShipToLocLongPostalCode>
<ShipToLocAddlAddressAttribute1>475</ShipToLocAddlAddressAttribute1>
<SupplierPartyName>CV_SuppA01</SupplierPartyName>
<SupplierAddress>Gruvfaltsgatan 45 768 90 Kiruna SWEDEN</SupplierAddress>
<SupplierSiteAddress1>475</SupplierSiteAddress1>
<SupplierSiteBuilding>1</SupplierSiteBuilding>
<SupplierSiteFloorNumber>1</SupplierSiteFloorNumber>
<SupplierSiteCity>New York</SupplierSiteCity>
<SupplierSiteCounty>New York</SupplierSiteCounty>
<SupplierSiteProvince>New York</SupplierSiteProvince>
<SupplierSiteState>New York</SupplierSiteState>
<SupplierSiteCountry>US</SupplierSiteCountry>
<SupplierSitePostalCode>10022</SupplierSitePostalCode>
<SupplierSitePostalPlus4Code>10022 4567</SupplierSitePostalPlus4Code>
<SupplierSiteAddrElementAttribute1>475</SupplierSiteAddrElementAttribute1>
<RequesterAddressLine1>475</RequesterAddressLine1>
<RequesterAddressBuilding>1</RequesterAddressBuilding>
<RequesterAddressFloorNumber>1</RequesterAddressFloorNumber>
<RequesterAddressTownOrCity>New York</RequesterAddressTownOrCity>
<RequesterAddressRegion1>New York</RequesterAddressRegion1>
<RequesterAddressRegion2>NY</RequesterAddressRegion2>
<RequesterAddressCountry>US</RequesterAddressCountry>
<RequesterAddressPostalCode>10022</RequesterAddressPostalCode>
<RequesterAddressLongPostalCode>10022</RequesterAddressLongPostalCode>
<RequesterAddlAddressAttr1>475</RequesterAddlAddressAttr1>
<TypeLookupCode>STANDARD</TypeLookupCode>
<HeaderChangeOrderStatus>INCOMPLETE</HeaderChangeOrderStatus>
<CurrencyCode>USD</CurrencyCode>
<CurrencyName>US Dollar</CurrencyName>
<HeaderCancelFlag>N</HeaderCancelFlag>
<HeaderCoCanceledFlag>N</HeaderCoCanceledFlag>
<ConfirmingOrderFlag>N</ConfirmingOrderFlag>
<ContermsExistFlag>N</ContermsExistFlag>
<DocumentCreationMethod>COPY_DOCUMENT</DocumentCreationMethod>
<OrderDateDisplay>2012-05-23 01:52:03.0</OrderDateDisplay>
<ChangeOrderDateDisplay>2012-05-23 01:52:03.0</ChangeOrderDateDisplay>
<CreationDate>2012-05-23 01:52:03.0</CreationDate>
<Comments>NO_BPEL</Comments>
<HeaderNoteToAuthorizer>Note to Authorizerc</HeaderNoteToAuthorizer>
<HeaderNoteToVendor>Note to Supplier</HeaderNoteToVendor>
<HeaderNoteToReceiver>Note to Receiver</HeaderNoteToReceiver>
<TextAttachmentsContent>Attachment</TextAttachmentsContent>
<ModeOfTransportName>Transport</ModeOfTransportName>
<ServiceLevelName>Service</ServiceLevelName>
<BillToBuName>Name</BillToBuName>
<AttributeCategory>Y</AttributeCategory>
<Attribute1>1</Attribute1>
<AttributeDate1>1</AttributeDate1>
<AttributeTimestamp1>1</AttributeTimestamp1>
<AttributeNumber1>1</AttributeNumber1>
<GlobalAttributeCategory>Y</GlobalAttributeCategory>
<GlobalAttribute1>1</GlobalAttribute1>
<PdfDraftPurchaseOrderHeaderVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<FileName>1</FileName>
<Url>1</Url>
<Title>1</Title>
<Description>1</Description>
</AttachmentsVORow>
</PdfDraftPurchaseOrderHeaderVOToAttachmentsVOAccessor>
<PdfDraftPurchaseOrderLine>
<PdfDraftPurchaseOrderLineVORow>
<LineNum>1</LineNum>
<ItemNumber>2</ItemNumber>
<ItemRevision>2</ItemRevision>
<ItemDescription>Item 01 for Goods</ItemDescription>
<VendorProductNum>2</VendorProductNum>
<LineType>Goods</LineType>
<BlanketHeaderDocNumber>1001</BlanketHeaderDocNumber>
<ContractHeaderDocNumber>1001</ContractHeaderDocNumber>
<SupplierRefNumber>1007</SupplierRefNumber>
<ManufacturerPartNumber>1007</ManufacturerPartNumber>
<SupplierPartAuxid>1007</SupplierPartAuxid>
<Quantity>10</Quantity>
<UomCode>Ea</UomCode>
<UnitOfMeasure>Each</UnitOfMeasure>
<BaseQty>100</BaseQty>
<BaseUom>Each</BaseUom>
<UnitPrice>100</UnitPrice>
<CancelledAmountDisplay>0.00</CancelledAmountDisplay>
<AmountDisplay>1,000.00</AmountDisplay>
<OriginalAmountBeforeCancellationDisplay>1,000.00</OriginalAmountBeforeCancellationDisplay>
<RecoverableTaxDisplay>1,000.00</RecoverableTaxDisplay>
<NonRecoverableTaxDisplay>1,000.00</NonRecoverableTaxDisplay>
<LineCancelFlag>N</LineCancelFlag>
<UnNumber>NA1133</UnNumber>
<UnNumberDescription>Cement</UnNumberDescription>
<HazardClass>Flammable</HazardClass>
<PurchaseBasis>GOODS</PurchaseBasis>
<CancelDate>2012-05-24</CancelDate>
<CancelReason>Cancel</CancelReason>
<LineNoteToVendor>On time</LineNoteToVendor>
<TextAttachmentsContent>Attach</TextAttachmentsContent>
<PdfDraftPurchaseOrderLineVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfDraftPurchaseOrderLineVOToAttachmentsVOAccessor>
<PdfDraftPurchaseOrderLineLocation>
<PdfDraftPurchaseOrderLineLocationVORow>
<ShipmentNum>1</ShipmentNum>
<SupplierOrderLineNumber>1</SupplierOrderLineNumber>
<QuantityDisplay>7</QuantityDisplay>
<SecondaryQuantity>100</SecondaryQuantity>
<SecondaryUomCode>Ea</SecondaryUomCode>
<SecondaryUnitOfMeasure>Each</SecondaryUnitOfMeasure>
<PriceOverride>100</PriceOverride>
<AmountDisplay>700.00</AmountDisplay>
<DaysEarlyReceiptAllowed>5</DaysEarlyReceiptAllowed>
<DaysLateReceiptAllowed>5</DaysLateReceiptAllowed>
<QuantityCancelled>5</QuantityCancelled>
<OriginalAmountBeforeCancellationDisplay>700.00</OriginalAmountBeforeCancellationDisplay>
<ScheduleCancelFlag>N</ScheduleCancelFlag>
<TaxableFlag>Y</TaxableFlag>
<CountryOfOriginCode>US</CountryOfOriginCode>
<NeedByDate>2012-05-23</NeedByDate>
<PromisedDate>2012-05-23</PromisedDate>
<ScheduleNoteToReceiver>Note to Receiver</ScheduleNoteToReceiver>
<CarrierName>Name</CarrierName>
<PdfDraftPurchaseOrderLineLocationVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfDraftPurchaseOrderLineLocationVOToAttachmentsVOAccessor>
<PdfDraftPurchaseOrderDistribution>
<PdfDraftPurchaseOrderDistributionVORow>
<DistributionNum>1</DistributionNum>
<DestinationSubinventory>Stores</DestinationSubinventory>
<QuantityOrdered>5</QuantityOrdered>
<AmountOrderedDisplay>500.00</AmountOrderedDisplay>
<RequesterEmailAddress>cf@email.com</RequesterEmailAddress>
<RequesterMailstop>1</RequesterMailstop>
<RequesterAddressAddlAddressAttribute1>475</RequesterAddressAddlAddressAttribute1>
<DeliverToLocAddressLine1>3455 108th Avenue</DeliverToLocAddressLine1>
<DeliverToLocAddressLine2>3455</DeliverToLocAddressLine2>
<DeliverToLocFloorNumber>1</DeliverToLocFloorNumber>
<DeliverToLocBuilding>1</DeliverToLocBuilding>
<DeliverToLocTownOrCity>Seattle</DeliverToLocTownOrCity>
<DeliverToLocRegion1>King</DeliverToLocRegion1>
<DeliverToLocRegion2>WA</DeliverToLocRegion2>
<DeliverToLocCountry>US</DeliverToLocCountry>
<DeliverToLocPostalCode>98101</DeliverToLocPostalCode>
<DeliverToLocLongPostalCode>98101</DeliverToLocLongPostalCode>
<DeliverToLocAddlAddressAttribute1>475</DeliverToLocAddlAddressAttribute1>
</PdfDraftPurchaseOrderDistributionVORow>
</PdfDraftPurchaseOrderDistribution>
</PdfDraftPurchaseOrderLineLocationVORow>
</PdfDraftPurchaseOrderLineLocation>
</PdfDraftPurchaseOrderLineVORow>
</PdfDraftPurchaseOrderLine>
</PdfDraftPurchaseOrderHeaderVORow>
</PdfDraftPurchaseOrderHeaderVO>
Appendix C - Sample XML for Archived Purchase Orders

<PdfArchivePurchaseOrderHeaderVO>
<PdfArchivePurchaseOrderHeaderVORow>
<DocumentStyle>Purchase Order</DocumentStyle>
<TaxRegistrationNumber>SYS12125</TaxRegistrationNumber>
<Fob>Origin</Fob>
<OrderedDisplay>2,000.00</OrderedDisplay>
<OriginalOrderAmountDisplay>2,000.00</OriginalOrderAmountDisplay>
<TotalTaxDisplay>0.00</TotalTaxDisplay>
<RequesterEmail>cf@email.com</RequesterEmail>
<SoldToBuName>Vision Operations</SoldToBuName>
<SoldToBuAddress>475 Park Avenue New York, NY 10022 New York UNITED
STATES</SoldToBuAddress>
<SoldToBuBuilding>1</SoldToBuBuilding>
<SoldToBuFloorNumber>1</SoldToBuFloorNumber>
<SoldToBuTownOrCity>New York</SoldToBuTownOrCity>
<SoldToBuRegion1>New York</SoldToBuRegion1>
<SoldToBuCountry>US</SoldToBuCountry>
<SoldToBuPostalCode>10022</SoldToBuPostalCode>
<SoldToBuLongPostalCode>10022</SoldToBuLongPostalCode>
<SoldToLeName>Vision Operations</SoldToLeName>
<SoldToLeAddress>475 Park Avenue New York, NY 10022 New York UNITED

STATES</SoldToLeAddress>
<SoldToLeTownOrCity>New York</SoldToLeTownOrCity>
<SoldToLeRegion1>New York</SoldToLeRegion1>
<SoldToLeCountry>US</SoldToLeCountry>
<SoldToLePostalCode>10022</SoldToLePostalCode>
<SoldToLeStateProvn>NY</SoldToLeStateProvn>
<BillToLocationName>V1- New York City</BillToLocationName>
<BillToAddress>90 Fifth Avenue New York, NY 10022-3422 New York UNITED
STATES</BillToAddress>
<BillToLocBuilding>1</BillToLocBuilding>
<BillToLocFloorNumber>1</BillToLocFloorNumber>
<BillToLocTownOrCity>New York</BillToLocTownOrCity>
<BillToLocRegion1>New York</BillToLocRegion1>
<BillToLocCountry>US</BillToLocCountry>
<BillToLocPostalCode>10022</BillToLocPostalCode>
<BillToLocLongPostalCode>10022</BillToLocLongPostalCode>
<TypeLookupCode>STANDARD</TypeLookupCode>
<HeaderChangeOrderStatus>PROCESSED</HeaderChangeOrderStatus>
<HeaderNoteToAuthorizer>Note to Authorizerc</HeaderNoteToAuthorizer>
<BillToBuName>Name</BillToBuName>
<PdfArchivePurchaseOrderHeaderVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfArchivePurchaseOrderHeaderVOToAttachmentsVOAccessor>
<PdfArchivePurchaseOrderLine>
<PdfArchivePurchaseOrderLineVORow>
<BlanketHeaderDocNumber>1001</BlanketHeaderDocNumber>
<ContractHeaderDocNumber>1001</ContractHeaderDocNumber>
<SupplierRefNumber>1007</SupplierRefNumber>
<ManufacturerPartNumber>1007</ManufacturerPartNumber>
<BaseQty>100</BaseQty>
<BaseUom>Each</BaseUom>
<OriginalAmountBeforeCancellationDisplay>1,000.00</OriginalAmountBeforeCancellationDisplay>
<RecoverableTaxDisplay>1,000.00</RecoverableTaxDisplay>
<NonRecoverableTaxDisplay>1,000.00</NonRecoverableTaxDisplay>
<PdfArchivePurchaseOrderLineVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfArchivePurchaseOrderLineVOToAttachmentsVOAccessor>
<PdfArchivePurchaseOrderLineLocation>
<PdfArchivePurchaseOrderLineLocationVORow>
<SupplierOrderLineNumber>1</SupplierOrderLineNumber>
<QuantityDisplay>7</QuantityDisplay>
<SecondaryQuantity>100</SecondaryQuantity>
<SecondaryUomCode>Ea</SecondaryUomCode>
<SecondaryUnitOfMeasure>Each</SecondaryUnitOfMeasure>
<AmountDisplay>700.00</AmountDisplay>
<DaysEarlyReceiptAllowed>5</DaysEarlyReceiptAllowed>
<DaysLateReceiptAllowed>5</DaysLateReceiptAllowed>
<QuantityCancelled>5</QuantityCancelled>
<OriginalAmountBeforeCancellationDisplay>700.00</OriginalAmountBeforeCancellationDisplay>
<ScheduleCancelFlag>N</ScheduleCancelFlag>
<TaxableFlag>Y</TaxableFlag>
<CountryOfOriginCode>US</CountryOfOriginCode>
<NeedByDate>2012-05-23</NeedByDate>
<PromisedDate>2012-05-23</PromisedDate>
<ScheduleNoteToReceiver>Note to Receiver</ScheduleNoteToReceiver>
<CarrierName>Name</CarrierName>
<PdfArchivePurchaseOrderLineLocationVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfArchivePurchaseOrderLineLocationVOToAttachmentsVOAccessor>
<PdfArchivePurchaseOrderDistribution>
<PdfArchivePurchaseOrderDistributionVORow>
<DistributionNum>1</DistributionNum>
<DestinationSubinventory>Stores</DestinationSubinventory>
<QuantityOrdered>5</QuantityOrdered>
<AmountOrderedDisplay>500.00</AmountOrderedDisplay>
<RequesterEmailAddress>cf@email.com</RequesterEmailAddress>
<RequesterMailstop>1</RequesterMailstop>
<DeliverToLocAddressLine1>3455 108th Avenue</DeliverToLocAddressLine1>
<DeliverToLocFloorNumber>1</DeliverToLocFloorNumber>
<DeliverToLocBuilding>1</DeliverToLocBuilding>
<DeliverToLocTownOrCity>Seattle</DeliverToLocTownOrCity>
<DeliverToLocRegion1>King</DeliverToLocRegion1>
<DeliverToLocCountry>US</DeliverToLocCountry>
<DeliverToLocPostalCode>98101</DeliverToLocPostalCode>
<DeliverToLocLongPostalCode>98101</DeliverToLocLongPostalCode>
</PdfArchivePurchaseOrderDistributionVORow>
</PdfArchivePurchaseOrderDistribution>
</PdfArchivePurchaseOrderLineLocationVORow>
</PdfArchivePurchaseOrderLineLocation>
</PdfArchivePurchaseOrderLineVORow>
</PdfArchivePurchaseOrderLine>
</PdfArchivePurchaseOrderHeaderVORow>
</PdfArchivePurchaseOrderHeaderVO>
Appendix D - Sample XML for Draft Purchase Agreements

<PdfDraftAgreementHeaderVO>
<PdfDraftAgreementHeaderVORow>
<DocumentStyle>Blanket Purchase Agreement</DocumentStyle>
<Fob>Origin</Fob>
<AmountLimit>100</AmountLimit>
<MinReleaseAmount>100</MinReleaseAmount>
<PriceUpdateTolerance>10</PriceUpdateTolerance>
<BlanketTotalAmountDisplay>10.00</BlanketTotalAmountDisplay>
<ProcurementBuName>Vision Operations</ProcurementBuName>
<ProcBuAddress>475 Park Avenue New York, NY 10022 New York UNITED
STATES</ProcBuAddress>
<ProcBuAddressLine1>475</ProcBuAddressLine1>
<ProcBuBuilding>1</ProcBuBuilding>
<ProcBuFloorNumber>1</ProcBuFloorNumber>
<ProcBuTownOrCity>New York</ProcBuTownOrCity>
<ProcBuRegion1>New York</ProcBuRegion1>
<ProcBuRegion2>NY</ProcBuRegion2>
<ProcBuCountry>US</ProcBuCountry>
<ProcBuPostalCode>10022</ProcBuPostalCode>
<ProcBuLongPostalCode>10022</ProcBuLongPostalCode>
<ProcBuAddlAddressAttribute1>475</ProcBuAddlAddressAttribute1>
<TypeLookupCode>BLANKET</TypeLookupCode>
<HeaderChangeOrderStatus>INCOMPLETE</HeaderChangeOrderStatus>
<StartDate>2012-05-23 01:52:03.0</StartDate>
<EndDate>2012-05-23 01:52:03.0</EndDate>
<HeaderNoteToAuthorizer>Note to Authorizer</HeaderNoteToAuthorizer>
<AgingOnsetPointValue>None</AgingOnsetPointValue>
<AgingPeriodDays>1</AgingPeriodDays>
<ConsumptionAdviceSummaryValue>Organization</ConsumptionAdviceSummaryValue>
<ConsumptionAdviceFrequencyValue>Daily</ConsumptionAdviceFrequencyValue>
<PayOnUseValue>Value</PayOnUseValue>
<PdfDraftAgreementHeaderVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfDraftAgreementHeaderVOToAttachmentsVOAccessor>
<PdfDraftAgreementLine>
<PdfDraftAgreementLineVORow>
<QuantityCommitted>10</QuantityCommitted>
<NotToExceedPrice>100</NotToExceedPrice>
<CommittedAmount>100</CommittedAmount>
<AllowPriceOverrideFlag>N</AllowPriceOverrideFlag>
<PriceBreakLookupCode>CUMULATIVE</PriceBreakLookupCode>
<ExpirationDate>2012-05-24</ExpirationDate>
<PdfDraftAgreementLineVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfDraftAgreementLineVOToAttachmentsVOAccessor>
<PdfDraftAgreementItemAttribute>
<PdfDraftAgreementItemAttributeVORow>
<Description></Description>
<LongDescription></LongDescription>
<SupplierUrl></SupplierUrl>
<Manufacturer></Manufacturer>
<ManufacturerUrl></ManufacturerUrl>
<ManufacturerPartNum></ManufacturerPartNum>
<AttachmentUrl></AttachmentUrl>
<Alias></Alias>
<LeadTime></LeadTime>
<Unspsc></Unspsc>
<ThumbnailImage></ThumbnailImage>
<Picture></Picture>
<Availability></Availability>
<Comments></Comments>
</PdfDraftAgreementItemAttributeVORow>
</PdfDraftAgreementItemAttribute>
<PdfDraftAgreementPriceBreak>
<PdfDraftAgreementPriceBreakVORow>
<PriceDiscount>100</PriceDiscount>
<ShipToLocationName>M1- Seattle Mfg</ShipToLocationName>
<ShipToAddress>3455 108th Avenue Seattle, WA 98101 King UNITED

STATES</ShipToAddress>
<PriceBreakStartDate>2012-05-23</PriceBreakStartDate>
<PriceBreakEndDate>2012-05-23</PriceBreakEndDate>
<PdfDraftAgreementPriceBreakVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfDraftAgreementPriceBreakVOToAttachmentsVOAccessor>
</PdfDraftAgreementPriceBreakVORow>
</PdfDraftAgreementPriceBreak>
</PdfDraftAgreementLineVORow>
</PdfDraftAgreementLine>
</PdfDraftAgreementHeaderVORow>
</PdfDraftAgreementHeaderVO>
Appendix E - Sample XML for Archived Purchase Agreements

<PdfArchiveAgreementHeaderVO>
<PdfArchiveAgreementHeaderVORow>
<DocumentStyle>Blanket Purchase Agreement</DocumentStyle>
<Fob>Origin</Fob>
<AmountLimit>100</AmountLimit>
<PriceUpdateTolerance>10</PriceUpdateTolerance>
<BlanketTotalAmountDisplay>10.00</BlanketTotalAmountDisplay>
<ProcurementBuName>Vision Operations</ProcurementBuName>
<ProcBuAddress>475 Park Avenue New York, NY 10022 New York UNITED
STATES</ProcBuAddress>
<ProcBuBuilding>1</ProcBuBuilding>
<ProcBuFloorNumber>1</ProcBuFloorNumber>
<ProcBuTownOrCity>New York</ProcBuTownOrCity>
<ProcBuRegion1>New York</ProcBuRegion1>
<ProcBuCountry>US</ProcBuCountry>
<ProcBuPostalCode>10022</ProcBuPostalCode>
<ProcBuLongPostalCode>10022</ProcBuLongPostalCode>
<TypeLookupCode>BLANKET</TypeLookupCode>
<HeaderChangeOrderStatus>PROCESSED</HeaderChangeOrderStatus>
<StartDate>2012-05-23 01:52:03.0</StartDate>
<EndDate>2012-05-23 01:52:03.0</EndDate>
<HeaderNoteToAuthorizer>Note to Authorizer</HeaderNoteToAuthorizer>
<AgingOnsetPointValue>None</AgingOnsetPointValue>
<ConsumptionAdviceSummaryValue>Organization</ConsumptionAdviceSummaryValue>
<ConsumptionAdviceFrequencyValue>Daily</ConsumptionAdviceFrequencyValue>
<PayOnUseValue>Value</PayOnUseValue>
<PdfArchiveAgreementHeaderVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfArchiveAgreementHeaderVOToAttachmentsVOAccessor>
<PdfArchiveAgreementLine>
<PdfArchiveAgreementLineVORow>
<QuantityCommitted>10</QuantityCommitted>
<NotToExceedPrice>100</NotToExceedPrice>
<CommittedAmount>100</CommittedAmount>
<AllowPriceOverrideFlag>N</AllowPriceOverrideFlag>
<PriceBreakLookupCode>CUMULATIVE</PriceBreakLookupCode>
<ExpirationDate>2012-05-24</ExpirationDate>
<PdfArchiveAgreementLineVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfArchiveAgreementLineVOToAttachmentsVOAccessor>
<PdfArchiveAgreementItemAttribute>
<PdfArchiveAgreementItemAttributeVORow>
<Description></Description>
<LongDescription></LongDescription>
<SupplierUrl></SupplierUrl>
<Manufacturer></Manufacturer>
<ManufacturerUrl></ManufacturerUrl>
<ManufacturerPartNum></ManufacturerPartNum>
<AttachmentUrl></AttachmentUrl>
<Alias></Alias>
<LeadTime></LeadTime>
<Unspsc></Unspsc>
<ThumbnailImage></ThumbnailImage>
<Picture></Picture>
<Availability></Availability>
<Comments></Comments>
</PdfArchiveAgreementItemAttributeVORow>
</PdfArchiveAgreementItemAttribute>
<PdfArchiveAgreementPriceBreak>
<PdfArchiveAgreementPriceBreakVORow>
<PriceDiscount>100</PriceDiscount>
<ShipToLocationName>M1- Seattle Mfg</ShipToLocationName>
<ShipToAddress>3455 108th Avenue Seattle, WA 98101 King UNITED
STATES</ShipToAddress>
<PriceBreakStartDate>2012-05-23</PriceBreakStartDate>
<PriceBreakEndDate>2012-05-23</PriceBreakEndDate>
<PdfArchiveAgreementPriceBreakVOToAttachmentsVOAccessor>
<AttachmentsVORow>
<Url>1</Url>
<Title>1</Title>
</AttachmentsVORow>
</PdfArchiveAgreementPriceBreakVOToAttachmentsVOAccessor>
</PdfArchiveAgreementPriceBreakVORow>
</PdfArchiveAgreementPriceBreak>
</PdfArchiveAgreementLineVORow>
</PdfArchiveAgreementLine>
</PdfArchiveAgreementHeaderVORow>
</PdfArchiveAgreementHeaderVO>
Oracle Corporation, World Headquarters
Worldwide Inquiries
500 Oracle Parkway
Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA
Fax: +1.650.506.7200
CONNECT WITH US
blogs.oracle.com/oracle
facebook.com/oracle
twitter.com/oracle
oracle.com
Copyright 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.0115
Purchasing Document Publishing and Communication
February 2015
Author: Manjula Evans
Contributing Authors: Suman Guha, Vijay Kartik, Rohit Lobo, Boyuan Zhu

Purchasing Document Publishing and Communication

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Purchasing Document Publishing and Communication

Caricato da

Copyright:

Formati disponibili

Purchasing Document Publishing and

Oracle Business Intelligence Publisher

Design/Modify Layout Templates

Obtain Procurement Data Source

Extend the Data Model (New in R9.2)

Create or Modify Layout Templates

Setup Oracle Business Intelligence Publisher

Setup Oracle Fusion Purchasing

Communicate the PDF from Oracle Fusion Purchasing

Integration with Oracle Fusion Procurement Contracts

Appendix A - List of XML Fields Applicable to Purchase Orders and Agreements

Appendix B - Sample XML for Draft Purchase Orders

Appendix C - Sample XML for Archived Purchase Orders

Appendix D - Sample XML for Draft Purchase Agreements

Appendix E - Sample XML for Archived Purchase Agreements

1 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Oracle Business Intelligence Publisher

2 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Figure 1. Document Publishing Fundamental Concept

Design/Modify Layout Templates

3 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Figure 2. Export Data Source from Data Model

Figure 3. Access List View of Layout

In the Output Formats dropdown, select Data (XML)

4 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Figure 4. Set XML as Output Format for Layout

Figure 5. Enable Report Viewer

5 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Figure 6. Export Data Source from Report

6 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Rich Text Format

Setup Oracle Business Intelligence Publisher

7 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Setup Oracle Fusion Purchasing

Figure 7. Configure Procurement Business Function for a Business Unit

Purchase Order Layout

Blanket Purchase Agreement

Purchase Agreement Layout

Contract Purchase Agreement

Purchase Agreement Layout

Communicate the PDF from Oracle Fusion Purchasing

8 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Figure 8. Communicate Purchasing Documents Dialog

9 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Figure 9. Communicating Documents using the Communicate Action/Dialog

Integration with Oracle Fusion Procurement Contracts

10 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Oracle Contract Terms Template

Blanket Purchase Agreement

Oracle Contract Terms Template

Contract Purchase Agreement

Oracle Contract Terms Template

Appendix A - List of XML Fields Applicable to Purchase Orders and Agreements

The display number used to identify a purchase order/purchase agreement.

The display number used to identify a purchase order/purchase agreement revision.

The suppliers identification number for the buying organization.

The suppliers order number corresponding to the buying organizations purchase

The suppliers order number corresponding to the buying organizations purchase

11 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

Tax Registration Number

The conditions under which the supplier will accept payment.

Indicates the granularity at which consumption advices will be generated. A consumption

12 | PURCHASING DOCUMENT PUBLISHING AND COMMUNICATION

The original total amount of the purchase order.