P. 1
48125026-PO1103B

48125026-PO1103B

|Views: 1,245|Likes:
Published by waelstar77

More info:

Published by: waelstar77 on Sep 24, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/11/2013

pdf

text

original

Sections

  • Purchasing Documents Open Interface
  • Summary of New Functionality
  • Functional Overview
  • Record and Error Processing
  • Original, Replace, and Update Submissions
  • Sourcing
  • Price Breaks
  • Adding or Deleting Lines in an Update Submission
  • Revision Numbering and Archiving
  • Setting Up
  • Monitoring Price Increases
  • Purchasing Documents Open Interface Table Descriptions
  • Derivation
  • Defaulting
  • Validation
  • Resolving Failed Purchasing Interface Rows
  • Price/Sales Catalog Notification Workflow
  • Workflow Customization Guidelines

Oracle® Purchasing Documentation Update

Purchasing Documents Open Interface

Release 10.7 and 11.0

April 1999

Oracle Purchasing Documents Open Interface Documentation Update Release 10.7 and 11.0 Copyright E 1998, 1999, Oracle Corporation. All Rights Reserved. Contributing Authors: Rachel Haas Contributors: Imran Ali, Barbara Hibino, John Houghton, Dave Stephens, Gopi Tummala, James Wang 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 is prohibited. 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 this document 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 US 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 licensee’s responsibility to take all appropriate fail–safe, back–up, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Oracle is a registered trademark, and Enabling the Information Age, Oracle Workflow, PL/SQL, and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. All other company or product names mentioned are used for identification purposes only, and may be trademarks of their respective owners.

Contents

Purchasing Documents Open Interface . . . . . . . . . . . . . . . . . . . . 1

Summary of New Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Record and Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Original, Replace, and Update Submissions . . . . . . . . . . . . . . . . . . . . . . . . . 7 Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Price Breaks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Adding or Deleting Lines in an Update Submission . . . . . . . . . . . . . . . . . 15 Revision Numbering and Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Setting Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Monitoring Price Increases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Purchasing Documents Open Interface Table Descriptions . . . . . . . . . . . 28 Derivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Defaulting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Resolving Failed Purchasing Interface Rows . . . . . . . . . . . . . . . . . . . . . . . . 48 Price/Sales Catalog Notification Workflow . . . . . . . . . . . . . . . . . . . . . . . . . 56 Workflow Customization Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

.

and Expiration Date on existing documents. The Purchasing Documents Open Interface uses Application Program Interfaces (APIs) to process catalog data in the Oracle Applications interface tables to ensure that it is valid before importing it into Oracle Purchasing. in the interface tables into blanket purchase agreements or catalog quotations in Purchasing. the supplier URL is Purchasing Documents Open Interface 1 . you know your supplier can send original or replacement price/sales catalogs in the form of blanket purchase agreements and catalog quotations. the Purchasing Documents Open Interface program converts the information. the Purchasing Documents Open Interface also enables the supplier to update existing blanket purchase agreements and catalog quotations with the price/sales catalog information. Summary of New Functionality If you already use a previous version of the Purchasing Documents Open Interface. or updated when the supplier sends an updated catalog. If your catalog quotation or blanket agreement uses a descriptive flexfield to reference suppliers’ Web sites. Price Breaks. The Purchasing Documents Open Interface supports the EDI transmissions of the price/sales catalogs (ANSI X12 832 or EDIFACT PRICAT) and responses to RFQs (ANSI X12 843 or EDIFACT QUOTES). You can also choose to update your item master and apply sourcing rules and release generation methods to the imported item for both blanket purchase agreements and quotations.Purchasing Documents Open Interface You can automatically import and update price/sales catalog information and request for quotation (RFQ) responses from suppliers through the Purchasing Documents Open Interface. Blanket purchase agreements or quotations can also be replaced with the latest price/sales catalog information when your supplier sends a replacement catalog. One way to import price/sales catalog data is through Electronic Data Interchange (EDI). You can choose whether to import the data as blanket purchase agreements or catalog quotations. item Description. After validating the price/sales catalog information or RFQ responses. Now. including price break information. unit of measure (UOM). The Update submission consists of the following functionality: • An update of the unit Price. without replacing the documents entirely.

7. Release 10. • The ability to add or expire individual item lines on a document. Notifications are generated if you enter values in the Price Update Tolerance fields in the Approved Supplier List window or the blanket purchase agreements. Therefore. the supplier must send an updated expiration date. The Expiration Date can also be sent by the supplier in an original or replacement price/sales catalog. If it cannot find a match between an incoming line in the Update submission and an existing line in Purchasing. it adds the line. This document replaces the Purchasing Documents Open Interface section of the Oracle Manufacturing.7. and can respond with Accept or Reject to the price increase in the new Exceeded Price Tolerances window. If you’re using Release 10. The supplier URL descriptive flexfield corresponds to the line–level column. you receive a notification. or in the PO: Price Tolerance (%) for Catalog Updates profile option. If you’re using Release 10. See: Monitoring Price Increases: page 22. Sales and Service Open Interfaces Manual.7 you can add lines but not delete them.7: The ability to expire lines on a blanket purchase agreement using the Expiration Date is not available with Release 10.7 does not include the Expiration Date feature. See the Oracle Purchasing Expiring Blanket Lines Documentation Update. See: Oracle Applications Flexfields Guide.7: The price tolerance feature is not available with Release 10. 2 Oracle Purchasing Documents Open Interface Documentation Update . The Expiration Date is a new field on a blanket purchase agreement. available with Release 11 only. Release 11. If you’re using these enhancements to the Purchasing Documents Open Interface. Distribution. in Release 10. To expire a line (on agreements only). For each document whose price is increased over the tolerance you set. The Purchasing Documents Open Interface handles this automatically. • A price tolerance feature that flags incoming prices exceeding a maximum price increase that you set. ATTRIBUTE14. These enhancements to the Purchasing Documents Open Interface are introduced in Maintenance Pack 11.3.0.also updated if sent. you can replace that section with this document.

7 Enhancements to the Purchasing Documents Open Interface are also available in a separate patch for Release 10.7 Summary of Features (Page 1 of 1) Purchasing Documents Open Interface 3 . item Description.7 Release 11 Release 11 Release 11 Release 11 Release 11 – Release 10.7 – – – Table 1 Release 10.Release 10.7. Functionality Release 11 Release 10. and price breaks Expiration of blanket lines Addition of document lines Price tolerance checking Workflow notification of exceeded price tolerances Update of UOM on agreement if open release exists Release 11 Release 10.7 and 11 of the enhanced Purchasing Documents Open Interface.7 Update of Price. UOM. The following table summarizes the main differences between Release 10.

to Oracle EDI Gateway. if sourcing 4 Oracle Purchasing Documents Open Interface Documentation Update .Functional Overview Figure 1 Purchasing Documents Open Interface Oracle EDI Gateway EDI Translator Electronic Transmission Service Provider Value–Added Network (VAN) or Internet Supplier or Trading Partner PO_ HEADERS_ INTERFACE Oracle Purchasing The import scripts that populate the interface tables PO_ LINES_ INTERFACE APIs The figure above shows the flow of price/sales catalog information from the supplier or trading partner. In the Parameters window of the EDI Catalog Inbound program (or EDI Response to RFQ Inbound program). then the supplier must provide the price/sales catalog information as a flat file using an EDI translator according to the EDI interface file definitions. you specify the name of the flat file and designate how the data sent by the supplier is to be used—if blanket purchase agreements or catalog quotations are to be created. to the Purchasing Documents Open Interface. and price break information. and finally into Purchasing. which includes line. Then. The PO_HEADERS_INTERFACE and PO_LINES_INTERFACE tables can also be loaded manually. shipment. through a program you write. if items are created or updated in the item master. the EDI Catalog Inbound program (or the EDI Response to RFQ Inbound program) loads the information into the PO_HEADERS_INTERFACE table and the PO_LINES_INTERFACE table. If you load the interface tables through EDI Gateway.

If no errors are found in the submission process. The Purchasing Documents Open Interface program receives the data. and ASL_DOCUMENTS). ASL_ITEMS. such as incomplete information from the supplier. The creation of items (if you allow updating of the item master) or sourcing rules also populates the corresponding tables (such as MTL_SYSTEM_ITEMS. Then. the Purchasing Documents Open Interface program first processes a record from the PO_HEADERS_INTERFACE table. including price breaks if any. derives and defaults any missing data. You can view the status of your submission by making note of the Request ID number and selecting View My Requests from the Help menu. You can launch the Purchasing Interface Errors Report in Purchasing to view the rows that were not imported by the Purchasing Documents Open Interface along with the failure reason(s) for each row. See: Oracle EDI Gateway User’s Guide. Purchasing Documents Open Interface 5 . after the data is loaded into the interface tables.) The EDI inbound program and the Purchasing Documents Open Interface program are run as a request set when you choose Submit Request in the EDI import programs window. Record and Error Processing To detect errors. The EDI inbound program loads the interface tables. the record identification number and the details of the error are written to the PO_INTERFACE_ERRORS table. and validates the data. and PO_LINE_LOCATIONS tables in Purchasing to create the blanket purchase agreement or catalog quotation. the Purchasing Documents Open Interface program validates the data and loads the validated data into Purchasing. the program processes the child records in the PO_LINES_INTERFACE table before going on to the next PO_HEADERS_INTERFACE record. ASL_SUPPLIERS. PO_LINES. Note: You can also run the Purchasing Documents Open Interface program separately in the Submit Request window in Purchasing. If the Purchasing Documents Open Interface program finds errors in the interface tables. the data in the Purchasing Documents Open Interface tables is loaded into the PO_HEADERS. (You also specify the location of the flat file through an EDI Gateway profile option.rules are created or updated.

If the program gets an error while processing a record. it can accept partial documents. If an error is found in a header. If no processing errors are found during processing. the header record and all successfully submitted child records are loaded into Purchasing. you must check the Purchasing Interface Errors report. It then flags the record as ”Not Processable.  Attention: It is important to check the Purchasing Interface Errors report (a report of the errors in the PO_INTERFACE_ERRORS table) after you import the price/sales catalog. Because the Purchasing Documents Open Interface saves or errors out line by line. to see which document lines were not submitted because of errors. none of its lines are processed. Therefore. and then flagged as processed by setting the PROCESS_CODE column to ACCEPTED. and you can find the error in the PO_INTERFACE_ERRORS table. and does the following: • Sets the PROCESS_CODE column value to REJECTED in the PO_HEADERS_INTERFACE table. • Begins processing the next header record. • Writes out the record identification number and the details of the error to the PO_INTERFACE_ERRORS table. 6 Oracle Purchasing Documents Open Interface Documentation Update . the program writes the error details to the PO_INTERFACE_ERRORS table and increments the record’s error counter. the Purchasing Documents Open Interface sets the PROCESS_CODE column to NOTIFIED for those lines with prices that exceed your price tolerance. In Release 11 only. does not process its lines. the Purchasing Documents Open Interface waits for you to accept or reject the price increase in the Exceeded Price Tolerances window before completing or rejecting the price change. The Purchasing Documents Open Interface rolls back the header. when the supplier sends an updated price/sales catalog. For these price updates only. it can accept partial documents. Because the Purchasing Documents Open Interface saves or errors out line by line. only that line is rolled back (not submitted to Purchasing). This means that if an error is found in a document line.” The Purchasing Documents Open Interface saves or errors out on a line–by–line basis.

your import program needs to specify the action code. your supplier can send you a flat file with one of three action codes (in the ACTION column of the PO_HEADERS_INTERFACE table): Original. or Update. the Purchasing Documents Open Interface first checks if a document in the submission already exists in Purchasing. It checks for a document with the same supplier document number (VENDOR_DOC_NUM) and supplier (VENDOR_ID or VENDOR_NAME) that is not finally closed or canceled. among the matching documents. Replace. If you’re not using EDI Gateway. it looks for documents that have the same document type (DOCUMENT_TYPE_CODE). supplier (VENDOR_ID or VENDOR_NAME). Replace. it looks for documents with effectivity dates that are the same as. Original A file with an action code of Original is one in which all the price/sales catalog information is new to your system. Your supplier should use the Original action code for a new price/sales catalog submission. and Replace or Update action codes for subsequent submissions. Choose Original when you’re submitting price/sales catalog information for the first time.) • Next. the replacement documents. (A supplier document number is a field that is specified in the flat file that the supplier sends. or within the effectivity dates of. the document in the Original submission is not created and an error is logged in the Purchasing Interface Errors report. Purchasing Documents Open Interface 7 . matching document already exists. and supplier document number (VENDOR_DOC_NUM) as the replacement documents. The Purchasing Documents Open Interface replaces these documents by doing the following: • First. For an Original submission.Original. If an active. and Update Submissions If you are using EDI Gateway to import the data (in the form of flat files) into the Purchasing Documents Open Interface. Replace A file with an action code of Replace replaces already–created blanket purchase agreements or catalog quotations with new documents containing the new price/sales catalog information.

Only the item description is updated in the item master. minus one day) and creates new documents with the new price/sales catalog information. The price is updated on the document only. it invalidates the old documents by setting their expiration dates to START_DATE –1 (the start date. Choose Replace when you want to replace the whole document because most of its fields. • Item Description • UOM • Price Breaks (for blanket purchase agreements) • Expiration Date (for blanket purchase agreements) • URL descriptive flexfield (if you have one) 8 Oracle Purchasing Documents Open Interface Documentation Update . within the original effectivity dates. header. the price and price breaks are not updated until or unless the buyer accepts the price update in the Exceeded Price Tolerances window. Any other updates. if you’ve enabled item description updates as described in Setting Up: page 16. if the price update exceeds the price tolerance you set. Purchasing replaces the one that is not canceled or finally closed. not in the item master. however. the Purchasing Documents Open Interface checks that there are no duplicate documents in Purchasing. As with an Original submission. and line information have changed or are out of date. but is canceled or finally closed. but it does not consider finally closed or canceled documents as duplicates. That is. Purchasing still replaces it with the new document. are made to the document when the price/sales catalog is imported. if two documents in Purchasing match an incoming document in the Replace submission.• Then. Update A file with an action code of Update updates the following information on already–submitted blanket purchase agreements or catalog quotations without creating completely new documents: • Unit Price In Release 11 only. If one document in Purchasing matches an incoming document.

Expired lines in Purchasing (lines whose Expiration Date has been reached) do not get updated. When the Purchasing Documents Open Interface updates a line on a blanket purchase agreement. This is done only if the UOM is updated on an agreement line for which an open release exists. The Purchasing Documents Open Interface updates documents by doing the following: • First.7. while for annual or bi–annual updates. Finally closed or canceled documents. For example. it does not update the open release for that line. weekly. it identifies the catalog quotation or blanket purchase agreement that needs to be updated by comparing the supplier document number (VENDOR_DOC_NUM in the PO_HEADERS_INTERFACE table) with the existing supplier document number (VENDOR_ORDER_NUM for a blanket agreement or QUOTE_VENDOR_QUOTE_NUMBER for a catalog quotation in the PO_HEADERS table). The Purchasing Documents Open Interface matches only to currently or future–effective documents that are not canceled or finally closed. Instead. and creates a new line with the updated UOM. the UOM can be updated. An Update submission for an expired line is treated as a new line to be added to the blanket purchase agreement. or even quarterly updates to existing documents. Purchasing cannot update the UOM on an agreement line if an open release exists against the line. If you are using Release 10. Purchasing Documents Open Interface 9 . a Replace submission may be better for your business needs. Choose Update when you want to update the fields listed above on existing documents. Only future releases use the updated information. the Purchasing Documents Open Interface uses the Expiration Date field to expire the line on the agreement. an Update submission can be used for daily. or those that are no longer effective. and will give an error in the Purchasing Interface Errors Report.A URL descriptive flexfield provides a supplier URL for additional information about an item. The supplier (VENDOR_ID or VENDOR_NAME) and document type (DOCUMENT_TYPE_CODE) must also match. and you want to preserve the existing documents’ sourcing rules.7: Since the Expiration Date is not available with Release 10. If an open release doesn’t exist against the line. do not get updated. Note: The Purchasing Documents Open Interface cannot update the UOM on an agreement line for which an open release exists.

For a one–time item. as long as it has not expired. the Purchasing Documents Open Interface updates the first line on the existing catalog quotation or blanket purchase agreement that matches the incoming line. This first line is also the line that is picked up for sourcing. and so on. revision number.• Next. it tries to match the item number used by your organization (along with the revision number and item category). in order: – Supplier item number – Item number used by your organization. If more than one line on the existing document matches the incoming line. and item category – Item description and item category If it can’t match the supplier item number. The following figure shows the flow of an Update price/sales catalog submission to Purchasing: 10 Oracle Purchasing Documents Open Interface Documentation Update . the item description is updated only if a supplier item number (VENDOR_PRODUCT_NUM) is provided and can be used to find a matching line on the original document. It identifies which lines on the existing documents need to be updated by matching the following. the Purchasing Documents Open Interface processes all the changed lines in the PO_LINES_INTERFACE table.

Figure 2 Update Submission Process Purchasing Documents Open Interface 11 .

Purchasing compares the effectivity dates of the incoming document with those of the existing sourcing rule for the item. If not. you can query the sourcing rule and define your own percentage splits between suppliers. For Original or Replace Submissions If you choose Yes to create sourcing rules in an Original or Replace submission.Sourcing When you import price/sales catalog information into Purchasing. • If a sourcing rule exists for the item. so as not to conflict with the existing sourcing rule. – If the effectivity dates of the incoming document are different than the existing sourcing rule’s effectivity dates. but are within or overlap the existing effectivity dates. If an entry does not exist. allocating 100 percent to the supplier providing the information. 12 Oracle Purchasing Documents Open Interface Documentation Update . Purchasing updates the item’s sourcing rule with the new effectivity dates. Purchasing adds the document to the entry. and document information that the supplier sends. Purchasing does the following: – If the effectivity dates of the incoming document are the same as the existing sourcing rule’s effectivity dates. If an entry exists. • Purchasing checks for an Approved Supplier List entry for the item and supplier/site combination. Purchasing generates a sourcing rule automatically. adding the supplier at an allocation of 100 percent. – If the effectivity dates of the incoming document do not overlap the existing sourcing rule’s effectivity dates. Purchasing adds the supplier to the existing sourcing rule with an allocation of 0 percent. To ensure that only one sourcing rule is used for the item. Purchasing checks if the supplier is in the sourcing rule. Later. you have the option of choosing Yes or No in the Create Sourcing Rules field in the Parameters window to enable Purchasing to create sourcing rules out of the supplier. then a new sourcing rule is not created. Purchasing checks if a sourcing rule is assigned to the item at the item level and does the following: • If no sourcing rules exist for the item. item. Purchasing creates a new entry with the new source document.

If one price break is rejected. and both of these line records would have the same INTERFACE_HEADER_ID: Purchasing Documents Open Interface 13 . and imports data into both the PO_LINES and PO_LINE_LOCATIONS tables in Purchasing. So if you wanted to create two price breaks corresponding to one blanket agreement or quotation line. That is. you would create two records in the PO_LINES_INTERFACE table. Replace. Price Breaks All action codes (Original. For Original or Replace Submissions The following. See: Adding or Deleting Lines in an Update Submission: page 15. additional columns are required in the PO_LINES_INTERFACE table if you want to import price break information: • LINE_NUM • SHIPMENT_NUM • QUANTITY • UNIT_PRICE If you are importing price break information through catalog quotations. one header– level record in the PO_HEADERS_INTERFACE table would have two records in the PO_LINES_INTERFACE table. and Update) support the importing of price breaks through the Purchasing Documents Open Interface. you can also optionally populate the following columns in the PO_LINES_INTERFACE table: • MIN_ORDER_QUANTITY • MAX_ORDER_QUANTITY Recall that the PO_LINES_INTERFACE table contains both line and shipment information. new sourcing information is created (as described above) only if the Update submission results in a new line being created. the whole line to which the price break belongs is rejected.For the Update Submission If you choose Yes to create sourcing rules in an Update submission.

Otherwise. 14 Oracle Purchasing Documents Open Interface Documentation Update . the order of the line and its price breaks is important. Just as with an Original or Replace submission. but different shipment numbers) follow the line to which they belong in the interface table. If the supplier sends new price breaks for an existing line. Use the INTERFACE_LINE_ID numbers to order price break (shipment) lines after their corresponding lines. If you are writing your own program to populate the interface tables. in an Update submission. make sure that the price break lines (lines with the same line and item number. the current price breaks are deleted and the new price breaks sent by the supplier are created.  Attention: In an Update submission. when two or more lines with the same line and item number are imported into the PO_LINES_INTERFACE table. the Purchasing Document Open Interface treats the subsequent lines as price breaks belonging to the first line. the Purchasing Document Open Interface treats the subsequent lines as price breaks belonging to the first line. with Shipment 1 information included – Line 1: the same line– level record (another row) in the PO_LINES_INTERFACE table. the Purchasing Documents Open Interface will treat them as duplicate lines (and update the previous line with the second).• One header– level record (row) in the PO_HEADERS_INTERFACE table corresponds to: – Line 1: one line– level record (row) in the PO_LINES_INTERFACE table. with Shipment 2 information included When two or more lines with the same line and item number are imported into the PO_LINES_INTERFACE table. For the Update Submission If the supplier updates an item’s price. the Purchasing Documents Open Interface deletes the item’s price breaks since they are no longer current with the new price.

as soon as you import them. or Expiration Date is updated. Note: Once a line has expired. You can expire lines on blanket purchase agreements only. depending on you which option you chose in the Document Types window. you also have the option of choosing Approved or Incomplete in the Approval Status field in the Parameters window. If you’re using Release 10. If the supplier does send an update to an expired line. The Purchasing Documents Open Interface handles this automatically. the Purchasing Documents Open Interface can add but not expire lines in Release 10.7. it adds the line. To expire a line. Revision Numbering and Archiving For the Update action code.) If Archive on Approval is chosen in the Document Types window in Purchasing and the document is imported as Approved. UOM.Adding or Deleting Lines in an Update Submission The Update submission enables the supplier to add or expire lines on existing blanket purchase agreements or catalog quotations. the supplier must send an updated Expiration Date for the line. a document is archived upon approval or printing. The profile option PO: Archive Catalog on Approval enables you to choose whether Purchasing archives blanket purchase agreements in a price/sales catalog submission upon approval. For all action codes. When importing price/sales catalog information. Therefore. See the table in the section Setting Up: page 16. then: • Setting PO: Archive Catalog on Approval to Yes archives the price/sales catalog documents once they are approved— in this case.7: The Expiration Date feature is not available with Release 10. (Quotations are not archived in Purchasing.7. item Description. not quotations. the document revision number is increased every time the unit Price. or when a new line is added (unless Archive on Approval is chosen in the Document Types window and PO: Archive Catalog on Approval is set to No). the update is treated as a new line to be added to the blanket purchase agreement. the supplier cannot send more updates to it. If it cannot find a match between the incoming line in the Update submission and an existing line in Purchasing. Purchasing Documents Open Interface 15 .

This may be helpful if you receive frequent price/sales catalog submissions and do not want Purchasing to take up extra space archiving every change. If Archive on Print is chosen in the Document Types window. and site levels. it does not matter how the PO: Archive Catalog on Approval profile option is set. Oracle Purchasing User’s Guide. depending on the option chosen in the Document Types window. See: Oracle EDI Gateway User’s Guide. Purchasing archives the imported price/sales catalog documents once they are printed.• Setting PO: Archive Catalog on Approval to No does not archive the price/sales catalog documents. the blanket purchase agreement is archived and its revision number increased only after all lines have either been accepted or rejected in the Exceeded Price Tolerances window. It can also be updated at the system administrator user. If the document is imported as Incomplete (see the table in the section Setting Up: page 16). Basic Purchasing functionality archives the document later upon approval or later upon printing. Note: You can monitor changes to blanket purchase agreements by using the PO Change History feature. you need to install and set up EDI Gateway for your organization. In Release 11. By default the PO: Archive Catalog on Approval profile option is set to No. Purchasing Setup Requirements The following setup steps are required before you can import the price/sales catalog: 16 Oracle Purchasing Documents Open Interface Documentation Update . The user can update this profile option. Setting Up If you want to import supplier price/sales catalog information into the Purchasing Documents Open Interface through EDI. The concurrent manager(s) that manages all processing also must be set up and running. application. responsibility. See: Purchase Order Features.

in the Control options region. This allows updating of item status codes at the site level. Make sure that both Purchasing and Inventory are listed in the Functional Area column and each has a default Category Set defined for it. make sure that the Default Category also appears in that List of Valid Categories. See: Defining Control Options.Allow Updating of the Item Master Allowing updating of the item master enables item description changes to be communicated quickly to Purchasing. Navigate to the Category Sets window by choosing Setup > Items > Categories > Category Sets in the Purchasing responsibility. check Allow Item Description Update. This allows updating of item descriptions. but in the item master as well. To allow updating of the item master: 1. Navigate to the Personal Profiles window and make sure that INV: Default Item Status is set to Active. Oracle Inventory User’s Guide. Only the item description is updated in the item master. Set Up Default Category Sets Make sure default category sets are set up appropriately for both Purchasing and Inventory by performing the following steps: 1. Navigate to the Purchasing Options window and. enter it in the list. Oracle Purchasing User’s Guide. If not. If you allow updating of the item master. Purchasing Documents Open Interface 17 . If you’ve selected the Enforce List of Valid Categories check box in the Category Sets window. the Purchasing Documents Open Interface updates the item description not just on blanket purchase agreements or quotations. Navigate to the Default Category Sets window by choosing Setup > Items > Categories > Default Category Sets in the Purchasing responsibility. Make sure that you have a default category set each for both Purchasing and Inventory in the Category Sets window. See: Defining Category Sets. 2. 2.

’directory’).ora file. responsibility. 18 Oracle Purchasing Documents Open Interface Documentation Update .Set the profile option PO: Archive Catalog on Approval If you typically archive documents on approval. the concurrent manager details log (viewable through the View Log button in the Submit Request window) can overflow and create errors. See: Revision Numbering and Archiving: page 15. which can cause overflow problems for large catalogs. To write log details to a file using Oracle Applications setup: 1. The user can update this profile option. setting this profile option to No means that Purchasing will not archive those changes made through the Purchasing Documents Open Interface. The profile option PO: Write Server Output to File enables you to write these log details to a flat file in the $APPL_TOP/log directory to avoid this overflow.put_names(’logfile’. application. To debug using SQL*Plus. 2. Set PO: Write Server Output to File to Yes. which will not overflow. 2. the log details are written to the concurrent manager log screen as usual. By default. Set the profile option PO: Write Server Output to File Set this profile option when you are debugging the Purchasing Documents Open Interface. After you run the Purchasing Documents Open Interface. Make sure the directory for the log file you want to write to in the next step is set in the environment variable APPLPTMP and that it is listed in the UTL_FILE_DIR parameter in the init. which improves performance. do the following before you run the Purchasing Documents Open Interface: 1. Specify the file name using FND_FILE. If you leave this profile option blank. When you import a price/sales catalog with a large number of items (about 100 or more). the log details are written to a flat file. the profile option is left blank. ’outfile’. If you set this profile option to Yes. For example: 3. Set PO: Write Server Output to File to Yes. It can also be updated at the system administrator user. look for a system– generated log file in the $APPL_TOP/log directory. Note: This profile option applies to the Purchasing Documents Open Interface only. and site levels. log details are not written at all. If you set this profile option to No.

fnd_file.put_names(’mylog.log’, ’myout.out’, ’/sqlcom/out’);

This will create a file called mylog.log in the /sqlcom/out directory. It is better to use /sqlcom/out because of write– access issues. If you have problems writing to the file, log into the machine where the database is installed. Set the Price Tolerance for the Update Submission (Release 11 Only) Define your price tolerance for price increases in an Update submission. Optionally use function security to control buyers’ access to the Exceeded Price Tolerances window. See: Monitoring Price Increases: page 22. If you’re using Release 10.7: The price tolerance feature is not available with Release 10.7. Set the Workflow Timeout for the Update Submission (Release 11 Only) If you import an Update price/sales catalog, decide whether you want to keep the default Timeout of seven days after notifying the buyer of a price update that exceeded the price tolerance. The default Timeout of seven days means if the buyer does not respond after seven days, the buyer will receive the notification again. If want to change this Timeout period, use the Workflow Builder. See: Catalog Price Update Approval Workflow: page NO TAG. For the Timeout feature to work, you must also submit the Workflow Background Process. See: To Schedule Background Engines, Oracle Workflow Guide. If you’re using Release 10.7: The price tolerance feature, including this workflow for notifying buyers of exceeded price tolerances, is not available with Release 10.7.

Importing the Price/Sales Catalog
The import programs window in EDI Gateway initiates both the EDI Catalog Inbound program (or EDI Response to RFQ Inbound program) to import the data from the supplier, and the Purchasing Documents Open Interface program to import the data into Purchasing.

Purchasing Documents Open Interface

19

After you submit the information in the Parameters window, make note of the Request ID number by selecting View My Requests from the Help menu so that you can later view the status of your submission. Note: The Purchasing Documents Open Interface program is also available separately in the Requests window in Purchasing, after you’ve successfully loaded the price/sales catalog data into the PO_HEADERS_INTERFACE and PO_LINES_INTERFACE tables. Commit Interval The Purchasing Documents Open Interface no longer uses this field to commit a certain number (Commit Interval) of documents at a time. Instead, it automatically commits or errors out the price/sales catalog line by line. Anything you enter in this field is ignored. See: Record and Error Processing: page 5. 

Attention: It is important to check the Purchasing Interface Errors report after you import the price/sales catalog. Because the Purchasing Documents Open Interface saves or errors out line by line, it can accept partial documents. Therefore, to see which document lines were not submitted because of errors, you must check the Purchasing Interface Errors report.

Create Sourcing Rules If you choose Yes in the Create Sourcing Rules field, make sure the Approval Status field for the submitted documents is Approved.

20

Oracle Purchasing Documents Open Interface Documentation Update

Sourcing rules can be created only when the Purchasing documents have a status of Approved. See also: Sourcing: page 12. Approval Status The following table shows the effects of the import Approval Status on a document’s current status, when you import an Update price/sales catalog.
Current Document Status Import Status Import as Incomplete Incomplete Approved Document remains Incomplete Document remains Approved Import as Approved Document changes to Approved Document remains Approved

Table 2 Document Status in Update Submission (Page 1 of 1)

Note that while a document is Incomplete, you cannot source from it until it is approved. Even in an Update submission, where you are updating only certain lines on a blanket purchase agreement or catalog quotation, if you choose Incomplete, the entire document, including the lines that weren’t updated, is considered Incomplete.

Purging the Open Interface Tables after Importing the Catalog
The ability to purge the open interface tables after you import the price/sales catalog into Purchasing is available with Release 11 only. If you want to purge data in the open interface tables after you have imported the data into Purchasing, use the Purge Purchasing Documents Open Interface Processed Data program, available through the Submit Request window in Purchasing. (This program removes data that has been accepted or rejected, not data that is still pending.) To remove data from the Purchasing Interface Errors table, set the Purge Data field in the Purchasing Interface Errors Report to Yes; the errors will not reappear the next time you run the report.

See Also
Purchasing Documents Open Interface, Oracle Purchasing User’s Guide Purchasing Interface Errors Report, Oracle Purchasing User’s Guide Inbound Price/Sales Catalog (832/PRICAT), Oracle EDI Gateway User’s Guide

Purchasing Documents Open Interface

21

or in the PO: Price Tolerance (%) for Catalog Updates profile option. In Release 10. any price increases the supplier sends are applied automatically to the documents in Purchasing. From there. optionally set a price update tolerance in the Supplier–Item Attributes window. If the price decreases. 22 Oracle Purchasing Documents Open Interface Documentation Update . If you still want to monitor price changes. In Release 11 In Release 11. are made. The price tolerance check is performed only on Update price/sales catalog submissions and only on price increases. is available with Release 11. do the following: • Make sure the imported price/sales documents are archived on approval (see: Revision Numbering and Archiving: page 15). on the blanket purchase agreement.0. All other line changes. • Use the PO Change History in the Purchasing menu to view all document changes. Purchasing does not check the decrease against your tolerance or notify you of the decrease. the Purchasing Documents Open Interface waits for the buyer to accept or reject the price increases in the Exceeded Price Tolerances window before completing or rejecting the price change.7.7 In Release 10. Oracle EDI Gateway User’s Guide Monitoring Price Increases The ability to monitor price increases. the buyer receives a notification for each affected document in the Notifications Summary window. Purchasing performs the price tolerance check against the price on the current revision of the document. The Purchasing Documents Open Interface Update submission makes all changes to documents except price changes that have exceeded your price tolerance. however. the buyer can access the Exceeded Price Tolerances window and accept or reject the price increase. Or create a custom report that isolates only price changes.Inbound Response to Request for Quote (843/QUOTE).3 only. If a price update in an Update price/sales catalog exceeds your tolerance. For these lines only. including the Price Update Tolerance Field and the notifications of exceeded price tolerances described in this section.

in the Terms and Conditions window. • The Price Update Tolerance field in the Supplier–Item Attributes window. at the item–supplier level. See: Overview of Function Security. Oracle Applications System Administrator’s Guide. Oracle Applications System Administrator’s Guide. " To set the price update tolerance: 1. See: Forms and Subfunctions. Buyers can then only view the Exceeded Price Tolerances window. Specify a price update tolerance at any of the following levels: • The Price Update Tolerance field on the original blanket purchase agreement.The Exceeded Price Tolerances window can also be used with function security to control buyers’ access to it. " To limit buyers’ access to the Exceeded Price Tolerances window: H Exclude the Accept/Reject Exceeded Price Tolerances subfunction from the buyer’s responsibility. Purchasing Documents Open Interface 23 .

at the commodity–supplier level. then the profile option. or supplier–item or supplier–commodity levels For blanket purchase agreements. If no Price Update Tolerance is set at any of these levels.• The Price Update Tolerance field in the Supplier–Item Attributes window. it does not default to the other levels. then the category level in the Approved Supplier List. since you cannot define a price tolerance at the document level. then Purchasing performs no price tolerance checking. For quotations. If you set more than one price update tolerance. then the category level in the Approved Supplier List. • The PO: Price Tolerance (%) for Catalog Updates profile option if you want the price tolerance to apply to everything. Purchasing looks first at the item level in the Approved Supplier List. Purchasing uses the first one it finds in the order described here. Example If you set the Price Update Tolerance field to 20 at the item–supplier level in the Supplier–Item Attributes window (and you haven’t set the price tolerance on the agreement). not just to specific documents. then the profile option. Purchasing uses the first price tolerance it finds to determine the price tolerance: it looks first at the document. If you set one price update tolerance. a price increase of more than 20 percent for that item and supplier will 24 Oracle Purchasing Documents Open Interface Documentation Update . then the item level in the Approved Supplier List.

and you haven’t set it to something else at a lower level.send the buyer a notification. Select the notification and choose Open. then no automatic price updates are allowed. To navigate to the Exceeded Price Tolerances window from the notification. open the Notifications Summary window and look for a notification titled Price tolerance exceeded during BLANKET update or Price tolerance exceeded during QUOTATION update. If you set the Price Update Tolerance to 20 on the agreement. " To accept or reject price increases: 1. Purchasing Documents Open Interface 25 . If you set the Price Update Tolerance to 0. After the price/sales catalog is imported into Purchasing. navigate to the Exceeded Price Tolerances window. To navigate to the Exceeded Price Tolerances window from the Navigator. a price increase of more than 20 percent on that document will issue a notification. The Price Update Tolerance fields and profile option apply only to documents in a price/sales catalog submission. That is. Note: The Price Tolerance field in the Purchasing Options window has nothing to do with these Price Update Tolerance fields. choose Purchasing Orders > Exceeded Price Tolerances. you will receive a notification of every price increase that occurs.

26 Oracle Purchasing Documents Open Interface Documentation Update . but simply accept or reject it. Its lines whose price updates exceeded the price tolerance are displayed below. You cannot change the price here.Choose the Open Document icon to open the Exceeded Price Tolerances window. The updated document’s header information is displayed at the top of the window.

Tolerance (%): The price tolerance that is set in Purchasing for this item. New Price: The updated price in the price/sales catalog submission.Document Status: Approval Status of Approved or Incomplete entered in the Parameters window when importing the price/sales catalog. Rev – Item revision number. for your reference. This price has exceeded your price tolerance. if any. Increase (%): Percentage by which the price of the current item on the document was exceeded. Choose Price Breaks to view price break changes. Price Increase: The difference between the original price and the updated price. Current Price: The current price of the item in Purchasing. Purchasing Documents Open Interface 27 . 2. You cannot change this field.

3. and the Purchasing Documents Open Interface program in Purchasing can derive (or default) some of the data into the Purchasing tables. choose Reject in the next step. See: Price/Sales Catalog Notification Workflow: page 56. Most of the column descriptions below that end with ID refer to internal identifier columns that uniquely identify a row in a table in 28 Oracle Purchasing Documents Open Interface Documentation Update . Save your work. or URL descriptive flexfield—have already been made. If you’ve customized the price/sales catalog workflow. Reject: The price is not updated on the document. 4. Your suppliers can send the data. Most of the columns in these tables correspond to columns in the PO_HEADERS and PO_LINES tables in Purchasing.You cannot modify the price breaks in this window. Only the price update is not made. Purchasing Documents Open Interface Table Descriptions Values for the columns in the PO_HEADERS_INTERFACE and PO_LINES_INTERFACE tables can come from multiple sources. Accept: The price update to the document line is accepted. you can enter data yourself through the Parameters windows in the EDI Catalog Inbound program or EDI Response to RFQ Inbound program. If you do not want to accept the price update or the new price breaks. In the Action column. UOM. Expiration Date. choose Accept or Reject to accept or reject each price update. Any other changes to the line—to the item Description. you can enable the Reject action to send the supplier a notification that the price update for this item has been rejected.

You do not have to enter values for columns in this category. For example. The INTERFACE_HEADER_ID column in the PO_HEADERS_INTERFACE table is the primary key (or unique identifier) for this table that other Purchasing tables can reference. Derived and/or Defaulted Optional Reserved for Future Use See Also Oracle Purchasing Applications Technical Reference Manual. For example. Most other ID columns are foreign keys—or identifiers that point—to other tables in Purchasing. but has reserved these columns for future enhancements. but are reserved for future functionality. The table descriptions below are based on what the Purchasing Documents Open Interface itself requires. For example. Some columns described below are not used currently by the Purchasing Documents Open Interface. As of this release. the Purchasing Documents Open Interface does not validate columns in this category before passing them into Purchasing. whether they are imported through a program you write or through EDI Gateway. Do not enter values in these columns. depending on whether other values are provided. whether the data is imported through EDI Gateway or a program you write.Purchasing. The following definitions are used: Required The Purchasing Documents Open Interface requires these values at a minimum. but EDI Gateway provides a value automatically. the Purchasing Documents Open Interface requires a value for the column INTERFACE_HEADER_ID. Release 11 Purchasing Documents Open Interface 29 . The Purchasing Documents Open Interface can derive or default columns in this category. the column AGENT_ID is a Derived and/or Defaulted column if a valid AGENT_NAME is provided. VENDOR_SITE_ID and VENDOR_SITE_CODE point to the PO_VENDOR_SITES table.

Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Number Number Type Date Date Number Required n n n Derived and/or Defaulted n n n n n n n n Optional n n n n n n n n n n n n n n Reserved for Future Use n n n n .ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Table 3 Purchasing Documents Open Interface (Headers) (Page 1 of 5) AGENT_ID AGENT_NAME RATE RATE_DATE RATE_TYPE_CODE RATE_TYPE CURRENCY_CODE RELEASE_DATE PO_RELEASE_ID RELEASE_NUM PO_HEADER_ID DOCUMENT_NUM DOCUMENT_SUBTYPE DOCUMENT_TYPE_CODE ORG_ID GROUP_CODE ACTION PROCESS_CODE INTERFACE_SOURCE_CODE BATCH_ID INTERFACE_HEADER_ID PO_HEADERS_INTERFACE Column Name Purchasing Documents Headers Table Description 30 Oracle Purchasing Documents Open Interface Documentation Update The following table describes the PO_HEADERS_INTERFACE table.

Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 3 Purchasing Documents Open Interface (Headers) (Page 2 of 5) COMMENTS CONFIRMING_ORDER_FLAG NOTE_TO_RECEIVER NOTE_TO_VENDOR REVISION_NUM REVISED_DATE APPROVED_DATE APPROVAL_STATUS FREIGHT_TERMS FOB FREIGHT_CARRIER TERMS_ID PAYMENT_TERMS BILL_TO_LOCATION_ID BILL_TO_LOCATION SHIP_TO_LOCATION_ID SHIP_TO_LOCATION VENDOR_CONTACT_ID VENDOR_CONTACT VENDOR_SITE_ID VENDOR_SITE_CODE VENDOR_ID VENDOR_NAME PO_HEADERS_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Number Number Type Date Date Required n n n Purchasing Documents Open Interface Derived and/or Defaulted n n n n n n n n n n Optional n n n n n n n n n n n n n n n n Reserved for Future Use n n n 31 .

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 3 Purchasing Documents Open Interface (Headers) (Page 3 of 5) FROM_TYPE_LOOKUP_CODE FROM_HEADER_ID VENDOR_LIST_HEADER_ID VENDOR_LIST APPROVAL_REQUIRED_FLAG VENDOR_DOC_NUM QUOTE_WARNING_DELAY RFQ_CLOSE_DATE REPLY_METHOD REPLY_DATE CLOSED_DATE CLOSED_CODE FROZEN_FLAG FIRM_FLAG PRINTED_DATE PRINT_COUNT EXPIRATION_DATE EFFECTIVE_DATE MIN_RELEASE_AMOUNT AMOUNT_LIMIT AMOUNT_AGREED ACCEPTANCE_DUE_DATE ACCEPTANCE_REQUIRED_FLAG PO_HEADERS_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Number Number Type Date Date Date Date Date Date Date conditionally conditionally conditionally Required Derived and/or Defaulted 32 Oracle Purchasing Documents Open Interface Documentation Update n n n n n n n n n n Optional n n n n n n n n n n n n Reserved for Future Use n n n n n n n n .

Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 3 Purchasing Documents Open Interface (Headers) (Page 4 of 5) REQUEST_ID LAST_UPDATE_LOGIN LAST_UPDATED_BY LAST_UPDATE_DATE CREATED_BY CREATION_DATE ATTRIBUTE15 ATTRIBUTE14 ATTRIBUTE13 ATTRIBUTE12 ATTRIBUTE11 ATTRIBUTE10 ATTRIBUTE9 ATTRIBUTE8 ATTRIBUTE7 ATTRIBUTE6 ATTRIBUTE5 ATTRIBUTE4 ATTRIBUTE3 ATTRIBUTE2 ATTRIBUTE1 ATTRIBUTE_CATEGORY USSGL_TRANSACTION_CODE PO_HEADERS_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Type Date Date Required Derived and/or Defaulted Purchasing Documents Open Interface n n n n n n Optional n n n n n n n n n n n n n n n n n n n n n n n Reserved for Future Use 33 .

PO_HEADERS_INTERFACE Column Name Type Required Derived and/or Defaulted Optional Reserved for Future Use 34 Oracle Purchasing Documents Open Interface Documentation Update ÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ PROGRAM_APPLICATION_ID PROGRAM_ID Number Number Date n n n n n n n n n n n PROGRAM_UPDATE_DATE REFERENCE_NUM Varchar2 Varchar2 Varchar2 Varchar2 Number LOAD_SOURCING_RULES_FLAG VENDOR_NUM FROM_RFQ_NUM WF_GROUP_ID Table 3 Purchasing Documents Open Interface (Headers) (Page 5 of 5) Following is a description of all of the required and conditionally required columns in the PO_HEADERS_INTERFACE table. and some other columns. INTERFACE_HEADER_ID Required This column indicates an identifier for the purchase order or catalog header. If you import price/sales catalog information through EDI Gateway. it provides a concurrent program grouping identifier for the submission. BATCH_ID Optional When you import the price/sales catalog information through EDI Gateway. Release 11. . this identifier is provided automatically. EDI Gateway) of the price/sales catalog data. INTERFACE_SOURCE_CODE Reserved for Future Use This column identifies the source (for example. Remaining column descriptions can be found in the Oracle Purchasing Applications Technical Reference Manual.

you do not have to enter a VENDOR_NAME. if you’re importing data through EDI Gateway. A NOTIFIED transaction. or update file. It is required to match incoming documents with existing documents.7: Since price tolerance checking is not performed in Release 10. Make sure the supplier is also set up as a trading partner in the EDI Gateway application. This column accepts values of ORIGINAL. REPLACE. or UPDATE. A PENDING transaction has not yet been processed. REJECTED. VENDOR_NAME Optional This column indicates the supplier for the document. It accepts values of PENDING. ACCEPTED.7. If you’re using Release 10. An ACCEPTED transaction has been successfully processed.PROCESS_CODE Optional This column indicates the status of a row in the interface table. this column would never have a value of NOTIFIED in Release 10. or NOTIFIED. the Purchasing Documents Open Interface sets the value to ACCEPTED. If you enter a VENDOR_ID. When you import price/sales catalog information through EDI Gateway. GROUP_CODE Reserved for Future Use This column indicates an identifier for the batch being imported. has been communicated to the buyer through the Notifications Summary window. ACTION Required This column indicates whether the price/sales catalog information is an original (new). REJECTED. Then.7. DOCUMENT_TYPE_CODE Required This column accepts values of BLANKET or QUOTATION. replacement. VENDOR_ID Required This column indicates the supplier identifier number. Make sure the supplier is also set up as a trading partner in the EDI Gateway Purchasing Documents Open Interface 35 . which includes a price update that exceeded the price tolerance. EDI Gateway defaults a value of PENDING in this column automatically. A REJECTED transaction contains an error which shows up in the Purchasing Interface Errors Report. or NOTIFIED.

if you’re importing data through EDI Gateway. If you enter a VENDOR_SITE_ID. if you’re importing data through EDI Gateway. the Purchasing Documents Open Interface cannot default a site. if you’re importing data through EDI Gateway. EFFECTIVE_DATE Conditionally Required This column must be populated when replacing an existing purchasing document. LOAD_SOURCING_RULES_FLAG Optional This column indicates whether to create sourcing rules with the purchasing document. VENDOR_SITE_ID Required This column indicates the supplier site for the document. you do not have to enter a VENDOR_SITE_CODE. The site also needs to be set up in EDI Gateway. If the supplier has more than one site. you do not have to enter a VENDOR_SITE_ID. If the supplier has more than one site. You choose this option in the Parameters window when importing the price/sales catalog. 36 Oracle Purchasing Documents Open Interface Documentation Update . The site also needs to be set up in EDI Gateway. If you enter a VENDOR_SITE_CODE. If you enter a VENDOR_NAME. The value in this column is used to locate the old price/sales catalog and expire it. the Purchasing Documents Open Interface cannot default a site.application. EXPIRATION_DATE Conditionally Required This column must be populated when replacing an existing purchasing document. VENDOR_SITE_CODE Required This column indicates the supplier site for the document. The value in this column is used to locate the old price/sales catalog and expire it. It is also required to make sure that documents in an Original submission don’t already exist in Purchasing. VENDOR_DOC_NUM Conditionally Required This column must be populated when replacing or updating an existing purchasing document. you do not have to enter a VENDOR_ID.

Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Number Number Number Number Number Number Type Date Required Purchasing Documents Open Interface n n Derived and/or Defaulted for internal use only n n n n n n Optional n n n n n n n Reserved for Future Use n n n n n n n 37 . the following columns are not used in Release 10. and PRICE_UPDATE_TOLERANCE. PRICE_BREAK_FLAG. The following table describes the PO_LINES_INTERFACE table.7. PRICE_CHG_ACCEPT_FLAG.7: Since price tolerance checking is not available with Release 10.ÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ EXPIRATION_DATE PO_RELEASE_ID PO_HEADER_ID RELEASE_NUM DOCUMENT_NUM REQUISITION_LINE_ID SHIPMENT_TYPE LINE_LOCATION_ID SHIPMENT_NUM PO_LINE_ID LINE_NUM GROUP_CODE ACTION_CODE ACTION INTERFACE_HEADER_ID INTERFACE_LINE_ID PO_LINES_INTERFACE Column Name Purchasing Documents Lines Table Description Table 4 Purchasing Documents Open Interface (Lines) (Page 1 of 8) PROCESS_CODE for Release 11 only If you’re using Release 10.7: PROCESS_CODE.

Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Table 4 Purchasing Documents Open Interface (Lines) (Page 2 of 8) LIST_PRICE_PER_UNIT UNIT_PRICE MAX_ORDER_QUANTITY MIN_ORDER_QUANTITY COMMITTED_AMOUNT QUANTITY UNIT_OF_MEASURE UOM_CODE VENDOR_PRODUCT_NUM ITEM_DESCRIPTION CATEGORY_ID CATEGORY ITEM_REVISION ITEM_ID ITEM LINE_TYPE_ID LINE_TYPE CONTRACT_NUM SOURCE_SHIPMENT_ID PRICE_UDATE_TOLERANCE for Release 11 only PRICE_BREAK_FLAG for Release 11 only PRICE_CHG_ACCEPT_FLAG for Release 11 only Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Number Number Number Number Number Number conditionally conditionally for internal use only for internal use only 38 Oracle Purchasing Documents Open Interface Documentation Update PO_LINES_INTERFACE Column Name Type Required Derived and/or Defaulted n n n n n n n n n n Optional n n n n n n n n n n n n n n n n Reserved for Future Use n n .

Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 4 Purchasing Documents Open Interface (Lines) (Page 3 of 8) CLOSED_CODE USSGL_TRANSACTION_CODE PRICE_BREAK_LOOKUP_CODE MIN_RELEASE_AMOUNT PRICE_TYPE TERMS_ID PAYMENT_TERMS RECEIPT_REQUIRED_FLAG INSPECTION_REQUIRED_FLAG CAPITAL_EXPENSE_FLAG TYPE_1099 TAX_NAME TAXABLE_FLAG TRANSACTION_REASON_CODE NOTE_TO_VENDOR HAZARD_CLASS_ID HAZARD_CLASS UN_NUMBER_ID UN_NUMBER NEGOTIATED_BY_PREPARER_FLAG NOT_TO_EXCEED_PRICE ALLOW_PRICE_OVERRIDE_FLAG MARKET_PRICE PO_LINES_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Number Type Required Derived and/or Defaulted Purchasing Documents Open Interface n n n n n n n n n n n n n n n n Optional n n n n n n n n n n n n n n n n n n n n Reserved for Future Use n n 39 .

Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 4 Purchasing Documents Open Interface (Lines) (Page 4 of 8) ACCRUE_ON_RECEIPT_FLAG PROMISED_DATE NEED_BY_DATE SHIP_TO_LOCATION_ID SHIP_TO_LOCATION SHIP_TO_ORGANIZATION_ID SHIP_TO_ORGANIZATION_CODE RECEIPT_DAYS_EXCEPTION_CODE QTY_RCV_EXCEPTION_CODE OVER_TOLERANCE_ERROR_FLAG QTY_RCV_TOLERANCE RECEIVING_ROUTING_ID RECEIVING_ROUTING ALLOW_SUBSTITUTE_RECEIPTS_FLAG ENFORCE_SHIP_TO_LOCATION_CODE DAYS_LATE_RECEIPT_ALLOWED DAYS_EARLY_RECEIPT_ALLOWED FIRM_FLAG RECEIVE_CLOSE_TOLERANCE INVOICE_CLOSE_TOLERANCE CLOSED_BY CLOSED_DATE CLOSED_REASON PO_LINES_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Number Number Number Number Type Date Date Date Required Derived and/or Defaulted 40 Oracle Purchasing Documents Open Interface Documentation Update n n n n Optional n n n n n n n n n n n n n n n n Reserved for Future Use n n n n n n n .

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 4 Purchasing Documents Open Interface (Lines) (Page 5 of 8) LINE_ATTRIBUTE11 LINE_ATTRIBUTE10 LINE_ATTRIBUTE9 LINE_ATTRIBUTE8 LINE_ATTRIBUTE7 LINE_ATTRIBUTE6 LINE_ATTRIBUTE5 LINE_ATTRIBUTE4 LINE_ATTRIBUTE3 LINE_ATTRIBUTE2 LINE_ATTRIBUTE1 LINE_ATTRIBUTE_CATEGORY_LINES FROM_LINE_LOCATION_ID FROM_LINE_ID FROM_HEADER_ID EXPIRATION_DATE EFFECTIVE_DATE FREIGHT_TERMS FOB FREIGHT_CARRIER PRICE_DISCOUNT LEAD_TIME_UNIT LEAD_TIME PO_LINES_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Type Date Date conditionally conditionally Required Derived and/or Defaulted Purchasing Documents Open Interface n n n Optional n n n n n n n n n n n n n n n n n n n n n Reserved for Future Use 41 .

Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 4 Purchasing Documents Open Interface (Lines) (Page 6 of 8) LAST_UPDATE_LOGIN LAST_UPDATED_BY LAST_UPDATE_DATE SHIPMENT_ATTRIBUTE15 SHIPMENT_ATTRIBUTE14 SHIPMENT_ATTRIBUTE13 SHIPMENT_ATTRIBUTE12 SHIPMENT_ATTRIBUTE11 SHIPMENT_ATTRIBUTE10 SHIPMENT_ATTRIBUTE9 SHIPMENT_ATTRIBUTE8 SHIPMENT_ATTRIBUTE7 SHIPMENT_ATTRIBUTE6 SHIPMENT_ATTRIBUTE5 SHIPMENT_ATTRIBUTE4 SHIPMENT_ATTRIBUTE3 SHIPMENT_ATTRIBUTE2 SHIPMENT_ATTRIBUTE1 SHIPMENT_ATTRIBUTE_CATEGORY LINE_ATTRIBUTE15 LINE_ATTRIBUTE14 LINE_ATTRIBUTE13 LINE_ATTRIBUTE12 PO_LINES_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Type Date Required Derived and/or Defaulted 42 Oracle Purchasing Documents Open Interface Documentation Update n n Optional n n n n n n n n n n n n n n n n n n n n n n n Reserved for Future Use .

Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Table 4 Purchasing Documents Open Interface (Lines) (Page 7 of 8) ITEM_ATTRIBUTE15 ITEM_ATTRIBUTE14 ITEM_ATTRIBUTE13 ITEM_ATTRIBUTE12 ITEM_ATTRIBUTE11 ITEM_ATTRIBUTE10 ITEM_ATTRIBUTE9 ITEM_ATTRIBUTE8 ITEM_ATTRIBUTE7 ITEM_ATTRIBUTE6 ITEM_ATTRIBUTE5 ITEM_ATTRIBUTE4 ITEM_ATTRIBUTE3 ITEM_ATTRIBUTE2 ITEM_ATTRIBUTE1 ITEM_ATTRIBUTE_CATEGORY ORGANIZATION_ID PROGRAM_UPDATE_DATE PROGRAM_ID PROGRAM_APPLICATION_ID REQUEST_ID CREATED_BY CREATION_DATE PO_LINES_INTERFACE Column Name Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number Number Number Type Date Date Required Derived and/or Defaulted Purchasing Documents Open Interface n n n n n n n Optional n n n n n n n n n n n n n n n n n n n n n n n Reserved for Future Use 43 .

PO_LINES_INTERFACE Column Name Type Required Derived and/or Defaulted Optional Reserved for Future Use 44 Oracle Purchasing Documents Open Interface Documentation Update ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ UNIT_WEIGHT Number n n n n n n n n WEIGHT_UOM_CODE Varchar2 Varchar2 Number Number VOLUME_UOM_CODE UNIT_VOLUME TEMPLATE_ID n TEMPLATE_NAME Varchar2 Varchar2 Varchar2 LINE_REFERENCE_NUM SOURCING_RULE_NAME Table 4 Purchasing Documents Open Interface (Lines) (Page 8 of 8) Following is a description of all of the required and conditionally required columns in the PO_LINES_INTERFACE table. this identifier is provided automatically. Remaining column descriptions can be found in the Oracle Purchasing Applications Technical Reference Manual. . GROUP_CODE Reserved for Future Use This column indicates an identifier for the batch being imported. If you import price/sales catalog information through EDI Gateway. If you import price/sales catalog information through EDI Gateway. INTERFACE_LINE_ID Required This column indicates the unique identifier of the line record in the PO_LINES_INTERFACE table. this identifier is provided automatically. and some other columns. INTERFACE_HEADER_ID Required This column indicates the unique identifier of the header record to which this line belongs. Release 11.

Both an ITEM and an ITEM_DESCRIPTION are required if an item is being created in the item master. A PENDING transaction has not yet been processed.EFFECTIVE_DATE Conditionally Required If you choose to create sourcing rules with the imported price/sales catalog information. which includes a price update that exceeded the price tolerance. or NOTIFIED. In an Update submission: When updating an existing line. ACCEPTED. has been communicated to the buyer through the Notifications Summary Purchasing Documents Open Interface 45 . the value in this column is still required if you choose to create sourcing rules with the imported price/sales catalog information. Both an ITEM and an ITEM_DESCRIPTION are required if an item is being created in the item master. ITEM Conditionally Required If you want to create items in the item master. then you need to provide a value in this column. then you need to supply the item information. ITEM_DESCRIPTION Conditionally Required If you want to create items in the item master. this column indicates the name of the sourcing rule. A NOTIFIED transaction. It is updated internally with values of null (which means PENDING). PROCESS_CODE Internal Use Only Used in Release 11 only. the value in this column is used to expire the line. If an item is being updated. EXPIRATION_DATE Conditionally Required In an Original or Replace submission: If you choose to create sourcing rules with the imported price/sales catalog information. SOURCING_RULE_NAME Optional If sourcing rules are being used. then you need to provide a value in this column. An ACCEPTED transaction has been successfully processed. this column indicates the status of a row in the interface table. When adding a new line. the ITEM_DESCRIPTION is required. then you need to supply the item information.

PRICE_BREAK_FLAG Internal Use Only Used in Release 11 only.7.7. If you’re using Release 10. Unless you are debugging the open interface. Release 10.7: Since price tolerance checking is not performed in Release 10. a line is never in a NOTIFIED state in Release 10. 46 Oracle Purchasing Documents Open Interface Documentation Update . Therefore. this column indicates internally to the Exceeded Price Tolerances window whether a price change in an Update submission includes price breaks. Y means that the price update was accepted. Release 10. This column is for internal use only.7 does not have the PRICE_BREAK_FLAG column. Unless you are debugging the open interface. do not use a program or script to update this column yourself.7 does not have the PRICE_CHG_ACCEPT_FLAG column. NULL means that the item price update is pending—waiting for the buyer to respond with Accept or Reject in the Exceeded Price Tolerances window. do not use a program or script to update this column yourself. Release 10. this column indicates internally whether a price has changed in an Update submission.7: Since price tolerance checking is not performed in Release 10. If you’re using Release 10. This column is for internal use only. If you’re using Release 10. This column is for internal use only.7.window.7. The Purchasing Documents Open Interface sets the value of this column to ACCEPTED or NOTIFIED. If the PROCESS_CODE value is NOTIFIED.7: Since price tolerance checking is not performed in Release 10. PRICE_CHG_ACCEPT_FLAG Internal Use Only Used in Release 11 only. N means that it was rejected.7 does not have the line–level PROCESS_CODE column. Unless you are debugging the open interface. do not use a program or script to update this column yourself.

Defaulting The Purchasing Documents Open Interface supports the same defaulting mechanisms as the Purchasing document entry windows. if you load the SHIP_TO_LOCATION value in the interface tables. the same derivation and defaulting rules apply to the interface tables as apply when you enter information in the Purchase Orders or Quotations windows. (Derivation refers to deriving a full value from a partial value given. • Default values that are no longer active or valid are not used. Purchasing Documents Open Interface 47 . Defaulting rules are applied as follows: • Defaults do not override values that you specify. Suppliers. the column ITEM_DESCRIPTION is derived or defaulted only if a valid ITEM or ITEM_ID is provided. then the key column is always used for processing. VENDOR_ID is used. Defaults can come from many sources. Purchasing uses the derivation source according to the following rules: • Key (ID) columns always override value columns. Financial Options. for example. defaulting refers to using a default value in Purchasing when no value is given. if VENDOR_NAME and VENDOR_ID contradict each other. and Master Item (or Organization Items) windows. Purchasing derives the SHIP_TO_LOCATION_ID from it instead of from the default ship–to information associated with your supplier. For example. If you populate both the key column and the corresponding value column. the VENDOR_ID is derived. • Derivation is performed before defaulting. if you provide a VENDOR_NAME or VENDOR_NUM.Derivation In general. and generally overrides defaulting.) For example. such as the Purchasing Options. For example. The Purchasing Documents Open Interface supports column value passing by user value.

please see the Oracle Applications Message Reference Manual. For specific information on the data implied by these columns. if a RATE_TYPE does not need to be defined (because exchange rate information is not needed) but contains a value. but also errors are signaled for those columns that have values but should not. an error will be signaled. Not only are all required columns validated so that they are populated with acceptable values. For more details on these messages. set the PROCESS_CODE column in the PO_HEADERS_INTERFACE table 48 Oracle Purchasing Documents Open Interface Documentation Update .Validation The Purchasing Documents Open Interface does not validate those columns described as ”Reserved for Future Use” on the previous pages. If multiple errors are detected. each error is written to the PO_INTERFACE_ERRORS table and displayed in the Purchasing Interface Errors Report. Release 11 for details. Other Validation The Purchasing Documents Open Interface performs the same validation as the Purchasing document entry windows before allowing the data to be committed to the base tables. A Note about Debugging for Release 11 If you receive an error in a document. Standard Validation Purchasing validates all required columns in the interface table. For example. see your Oracle Purchasing Applications Technical Reference Manual. Resolving Failed Purchasing Interface Rows Error Messages Purchasing may display specific error messages during interface processing. in HTML format on the documentation CD–ROM for Release 11. you can fix the error and resubmit the document again by reusing a header record in the PO_HEADERS_INTERFACE table using SQL*Plus. If you do this.

Table 5 Purchasing Documents Open Interface Error Messages (Page 1 of 7) Purchasing Documents Open Interface 49 .to PENDING and be sure to reset the following columns to NULL for all lines belonging to that header in the PO_LINES_INTERFACE table: • PROCESS_CODE • PRICE_CHG_ACCEPT_FLAG • PRICE_BREAK_FLAG If you’re using Release 10. the Purchasing Documents Open Interface creates one or more rows with error information in the PO_INTERFACE_ERRORS table.7. This report is generated through the Submit Request window and processed as other standard reports in Purchasing. The following table shows the error messages and their meaning: Error Message PO_PDOI_AMT_LIMIT_LT_AGREED Meaning Amount Limit (VALUE= &AMOUNT_LIMIT) is less than Amount Agreed (VALUE=&VALUE). Column &COLUMN_NAME should be 0. The Purchasing Interface Errors Report lists all the columns in the PO_INTERFACE_ERRORS table that failed validation along with the reason for the failure.7: These columns are not available with Release 10. Catalog being created with supplier document number [DOC_NUMBER] already exists. Amount Limit (VALUE= &AMOUNT_LIMIT) is less than Total Amount Released (VALUE=&VALUE). Viewing Failed Transactions You can report on all rows that failed validation by using the Purchasing Interface Errors Report. For each row in the Purchasing Documents Open Interface tables that fails validation. PO_PDOI_AMT_LIMIT_LT_TOTREL PO_PDOI_CATG_ALREADY_EXISTS PO_PDOI_COLUMN_NOT_NULL PO_PDOI_COLUMN_NOT_ZERO Column &COLUMN_NAME should not be NULL. Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ PO_PDOI_AMT_LIMIT_LT_RELEASE Amount Limit (VALUE= &AMOUNT_LIMIT) is less than Minimum Release Amount (VALUE=&VALUE).

DISCOUNT (VALUE =&VALUE) specified is invalid. Document Number (VALUE= &VALUE) specified is invalid. Buyer (VALUE=&VALUE) specified is not a valid buyer. PO_PDOI_EFF_DATE_GT_HEADER PO_PDOI_EXCEED_PRICE_NULL NOT TO EXCEED PRICE (VALUE= &VALUE) PO_PDOI_INVALID_ACTION Must be NULL if ALLOW_PRICE_OVERRIDE_FLAG is N. PO_PDOI_DERV_PART_NUM_ERROR Cannot derive ITEM_ID for the specified buyer item_number or VENDOR_PRODUCT_NUM. PO_PDOI_INVALID_CATEGORY_ID PO_PDOI_INVALID_CURRENCY PO_PDOI_INVALID_DISCOUNT PO_PDOI_INVALID_DOC_NUM PO_PDOI_INVALID_DOC_STATUS Sourcing rule can be created only if document is loaded as an approved document. It can either be Y or N. CATEGORY ID (VALUE =&VALUE) specified is inactive or invalid. Action (VALUE= &VALUE) is invalid. PO_PDOI_INVALID_FLAG_VALUE PO_PDOI_INVALID_FOB &COLUMN_NAME (VALUE =&VALUE) is invalid.Error Message PO_PDOI_COLUMN_NULL PO_PDOI_DERV_ERROR Meaning Column &COLUMN_NAME (VALUE=&VALUE) must be NULL. PO_PDOI_INVALID_BILL_LOC_ID PO_PDOI_INVALID_BUYER Bill–To Location ID (VALUE=&VALUE) is not valid. PO_PDOI_DIFF_ITEM_DESC PO_PDOI_DOC_NUM_UNIQUE Document Num must have a unique value. Currency Code (VALUE =&VALUE) specified is inactive or invalid. FOB (VALUE=&VALUE) specified is inactive or invalid. &VALUE already exists. Effective Date (VALUE =&VALUE) specified should not be less than the effective date specified. 50 Oracle Purchasing Documents Open Interface Documentation Update ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Derivation Error: &COLUMN_NAME (VALUE= &VALUE) specified is invalid. Pre–defined item description cannot be changed for this item. Table 5 Purchasing Documents Open Interface Error Messages (Page 2 of 7) .

&DOC_NUMBER specified is not a valid original catalog.Error Message PO_PDOI_INVALID_FREIGHT_CARR Meaning FREIGHT CARRIER (VALUE =&VALUE) specified is inactive or invalid. PO_PDOI_INVALID_ITEM_REVISION PO_PDOI_INVALID_ITEM_UOM_CODE PO_PDOI_INVALID_LEAD_TIME Lead Time Unit (VALUE=&VALUE) specified is inactive or invalid. &COLUMN_NAME (VALUE=&VALUE) must match the value from the PO_LINE_TYPES table (VALUE=&LINE_TYPE). Item Flag (VALUE= &VALUE) is invalid. HAZARD CLASS ID (VALUE =&VALUE) specified is inactive or invalid. &COLUMN_NAME There should be at least one line per document. PO_PDOI_INVALID_NUM_OF_LINES PO_PDOI_INVALID_OP_ITEM_ID ITEM ID (VALUE =&VALUE) is not a valid purchasable and outside operational item. PAYMENT TERMS (VALUE =&VALUE) specified is inactive or invalid. LINE TYPE ID (VALUE =&VALUE) specified is inactive or invalid. ITEM UOM CODE (VALUE =&VALUE) specified is inactive or invalid. PO_PDOI_INVALID_ORIG_CATALOG PO_PDOI_INVALID_PAY_TERMS Table 5 Purchasing Documents Open Interface Error Messages (Page 3 of 7) Purchasing Documents Open Interface 51 . ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ PO_PDOI_INVALID_FREIGHT_TERMS PO_PDOI_INVALID_HAZ_ID FREIGHT TERMS (VALUE =&VALUE) specified is inactive or invalid. PO_PDOI_INVALID_ITEM_FLAG PO_PDOI_INVALID_ITEM_ID ITEM ID (VALUE =&VALUE) is not a valid purchasable item. PO_PDOI_INVALID_INTER_LINE_REC Record specified in PO_LINES_INTERFACE is invalid. PO_PDOI_INVALID_LINE_TYPE_ID PO_PDOI_INVALID_LINE_TYPE_INFO PO_PDOI_INVALID_LOCATION_REC Information specified in PO_LINES_INTERFACE table does not match the parent record in PO_LINES table. REVISION NUM (VALUE =&VALUE) specified is inactive or invalid. It is neither a new record in PO_LINES nor PO_LINE_LOCATIONS.

PO_PDOI_INVALID_RCV_EXCEP_CD RCV EXCEPTION CODE (VALUE =&VALUE) specified is inactive or invalid. PO_PDOI_INVALID_SHIPMENT_TYPE SHIPMENT TYPE (VALUE= &TYPE) specified is not valid for TYPE LOOKUP CODE (VALUE=&VALUE) SHIP_TO_LOCATION_ID (VALUE=&VALUE) is not valid. PO_PDOI_INVALID_RATE_TYPE Rate Type (VALUE =&VALUE) specified is invalid. PO_PDOI_INVALID_REPLY_METHOD REPLY METHOD (VALUE =&VALUE) specified is inactive or invalid. (VALUE= &VALUE) has to be greater or equal to UNIT PRICE (VALUE=&UNIT_PRICE). Approval Status specified is invalid. SHIP_TO_ORGANIZATION_ID (VALUE=&VALUE) specified is inactive or invalid. Document Subtype (VALUE= &VALUE) specified is invalid. PO_PDOI_INVALID_SHIP_LOC_ID PO_PDOI_INVALID_SHIP_TO_LOC_ID PO_PDOI_INVALID_SHIP_TO_ORG_ID PO_PDOI_INVALID_START_DATE Effective Date (VALUE =&VALUE) specified should be less than the end date specified. 52 Oracle Purchasing Documents Open Interface Documentation Update ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ PO_PDOI_INVALID_PRICE_BREAK PO_PDOI_INVALID_PRICE_TYPE PRICE TYPE (VALUE =&VALUE) specified is inactive or invalid. PO_PDOI_INVALID_STATUS PO_PDOI_INVALID_TAX_NAME TAX NAME (VALUE =&VALUE) specified is inactive or invalid.Error Message PO_PDOI_INVALID_PRICE Meaning NOT TO EXCEED PRICE. TEMPLATE ID (VALUE =&VALUE) specified is inactive or invalid. PRICE BREAK LOOKUP CODE (VALUE=&VALUE) specified is inactive or invalid. PO_PDOI_INVALID_QUOTE_TYPE_CD PO_PDOI_INVALID_RATE The rate value (VALUE=&VALUE) specified is invalid. SHIP_TO_LOCATION_ID (VALUE=&VALUE) specified is inactive or invalid. PO_PDOI_INVALID_TEMPLATE_ID Table 5 Purchasing Documents Open Interface Error Messages (Page 4 of 7) .

Vendor (VALUE=&VALUE) specified is invalid or inactive. Item attribute(s) required update. &COLUMN_NAME (VALUE =&VALUE) specified is less than zero. However. UNIT OF MEASURE (VALUE =&VALUE) specified is inactive or invalid. &COLUMN_NAME (VALUE=&VALUE) specified is inactive or invalid for ITEM_ID (VALUE=&ITEM). &VALUE already exists. PO_PDOI_INVALID_VENDOR PO_PDOI_INVALID_VENDOR_SITE PO_PDOI_INVAL_MULT_ORIG_CATG PO_PDOI_ITEM_NOT_NULL ITEM_ID should not be null for outside operation LINE_TYPE.Error Message PO_PDOI_INVALID_TYPE_LKUP_CD Meaning Document Type Code (VALUE =&VALUE) specified is invalid. PO_PDOI_INVALID_VALUE &COLUMN_NAME must have a value of &VALUE. PO_PDOI_INVALID_VDR_CNTCT Vendor Contact (VALUE=&VALUE) is not an active and valid contact for the specified vendor site. PO_PDOI_INVALID_USSGL_TXN_CODE USSGL Transaction Code (VALUE =&VALUE) specified is invalid. &VALUE already exists. PO_PDOI_LINE_LOC_ID_UNIQUE PO_PDOI_LINE_NUM_UNIQUE PO_PDOI_LT_ZERO LINE_NUM must have a unique value. Multiple catalogs can be found with the same document number (&DOC_NUMBER). ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ PO_PDOI_INVALID_UN_NUMBER_ID PO_PDOI_INVALID_UOM_CODE UN NUMBER ID (VALUE =&VALUE) specified is inactive or invalid. Table 5 Purchasing Documents Open Interface Error Messages (Page 5 of 7) Purchasing Documents Open Interface 53 . LINE_LOCATION_ID must be unique. &VALUE already exists. this execution does not allow item update/creation. PO_PDOI_ITEM_RELATED_INFO PO_PDOI_ITEM_UPDATE_NOT_ALLOW PO_PDOI_LINE_ID_UNIQUE LINE_ID must have a unique value. Vendor Site (VALUE=&VALUE) is not an active and valid purchasing vendor site.

&COLUMN_NAME (VALUE= &VALUE) needs to be a numeric value. 54 Oracle Purchasing Documents Open Interface Documentation Update ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ PO_PDOI_NO_DATA_FOUND No rate found for currency_code (VALUE=&CURRENCY) and RATE_TYPE_CODE (VALUE=&RATE_TYPE). PO_PDOI_RATE_INFO_NULL RATE TYPE. PO_PDOI_OVERLAP_AUTO_RULE Sourcing rule (VALUE=&START_DATE) and (VALUE=&END_DATE) overlaps with an existing sourcing rule.Error Message PO_PDOI_MULT_BUYER_PART Meaning Multiple buyer parts are found which match the specified Item Num (VALUE=&VALUE). PO_PDOI_PO_HDR_ID_UNIQUE PO_PDOI_PRICE_BRK_AMT_BASED_LN Cannot create price breaks for amount– based lines in a BLANKET order agreement. PO_PDOI_VALUE_NUMERIC Table 5 Purchasing Documents Open Interface Error Messages (Page 6 of 7) . PO_PDOI_RULE_NAME_UNIQ PO_PDOI_SHIPMENT_NUM_UNIQUE PO_PDOI_SPECIF_DIFF_IN_LINES Shipment Num must have a unique value. &VALUE already exists. PO_HEADER_ID must be unique. PO_PDOI_QT_MIN_GT_MAX Minimum Quantity (VALUE =&MIN) specified is greater than maximum Quantity (VALUE =&MAX). Rule Name (VALUE= &VALUE) and Item Id (ID =&VALUE) should be unique. (VALUE = &VALUE) already exists. RATE_DATE and RATE must be null. &COLUMN_NAME (VALUE= &PO_HEADER_ID) specified in line is different from (VALUE=&VALUE) in header.

Default item categories are specified in Setup > Items > Category > Category Set. The category ID transmitted with the Item ID does not match the category ID already set up in the system for that item. make sure the documents in the data are submitted as approved. Navigate to the Descriptive Flexfield Segments window by choosing Setup > Flexfields > Descriptive > Segments.Error Message ORIGINAL_RFQ_NUM is invalid Meaning The original RFQ number that is transmitted already exists. See Also Purchasing Interface Errors Report. If it is null. Select another RFQ number. Other errors could be the result of the following: • If you create sourcing rules along with the imported data. date fields are in an incorrect format). Purchasing Documents Open Interface 55 . Sourcing rules can be created only when the Purchasing documents have a status of Approved. make sure that Purchasing is defaulting a category ID and that the category ID is enabled. ask the supplier to correct and resend the data. Table 5 Purchasing Documents Open Interface Error Messages (Page 7 of 7) Fixing Failed Transactions Some examples of errors could be that the supplier’s information does not conform with Purchasing data requirements (for example. Make sure that the default item category is one of the values in the rows. If errors exist in the supplier’s data. cross–reference rules set up between you and your supplier are inaccurate. Oracle Applications Flexfields Guide. See: Defining Descriptive Flexfield Structures. Oracle Purchasing User’s Guide ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Category ID is invalid for Item ID. or your own Purchasing or Oracle Applications data is not up to date. • Flexfields may need to be frozen and recompiled.

You can view or modify this workflow in the Oracle Workflow Builder. If you’re using Release 10.7: This workflow is available with Release 11 only.7. See the Oracle Workflow Guide. Workflow is an underlying technology that sends a notification to the buyer if the price tolerance is exceeded and waits for the buyer to accept or reject the price increase.Price/Sales Catalog Notification Workflow The price/sales catalog notification workflow uses the Price Update Tolerance you set to determine when a price increase in an Update price/sales catalog submission exceeds your tolerance. Disregard this section if you are using the enhanced Purchasing Documents Open Interface with Release 10. The Purchasing Documents Open Interface applies or does not apply the price increase depending on the buyer’s action. The following figure shows how the workflow affects line statuses in the Purchasing Documents Open Interface tables: 56 Oracle Purchasing Documents Open Interface Documentation Update . The buyer is notified automatically by the workflow. The supplier is notified of price update rejections only if you customize the workflow to do so.

Figure 3 Price/Sales Catalog Workflow Overview Purchasing Documents Open Interface 57 .

Oracle Workflow Guide. 58 Oracle Purchasing Documents Open Interface Documentation Update . " To display the workflow in the Oracle Workflow Builder: 1. 3. The name of its Workflow definition file is poxprcat. Expand the data source.Customizing the Issue Notifications Process You can view the workflow in a Process window using the Workflow Builder. See: Opening and Saving Item Types.wft. Expand the Processes branch. Choose Open from the File menu. then double–click the Issue Notifications process activity to display its diagram. and connect to the database. The Display name of the price/sales catalog notification workflow is PO Catalog Price Tolerance Exceeded Notifications. 2. then the item type branch within that data source. Required Modifications There are no required modifications you need to make to this workflow.

Choose Properties from the Edit menu. The activity’s Control Properties window appears. To help you with your customizations. You could modify the workflow to send the notification to people other than the buyer. You can modify the notification activities. " To change the Timeout period from seven days: 1. refer to the sections later that describe the components of this process. you may wish to customize it further to accommodate your organization’s specific needs. 3. however. You cannot modify any of the item attributes except for Supplier User Name. If you want to send the supplier an automatic notification of rejected price updates. See: Workflow Customization Guidelines: page 64. In the Workflow Builder. You could modify the process to send the buyer a reminder sooner or later than the activity Wait for Buyer Action from Exceeded Price Tolerances Form does by default. Select the Details tab. expand the Functions branch and select the Wait for Buyer Action from Exceeded Price Tolerances Form activity. You can modify the Issue Notifications process to suit your business needs. Some of these customizations are described below.) You cannot modify any of the function activities or messages in the workflow.Optional Customizations Although you can use the workflow as is. (Information about when you might customize this attribute is provided below. you could replace them in the Issue Notifications process with ones of your own. Purchasing Documents Open Interface 59 . you must modify the workflow. 2.

Create a function activity that for a given supplier assigns the correct supplier user name to the Supplier User Name item attribute. " To send automatic notifications of rejected price updates to the supplier: 1. See: Setting Up an Oracle Workflow Directory Service. 60 Oracle Purchasing Documents Open Interface Documentation Update . Change the Timeout to a period of time that best suits your organization’s needs. In Oracle Applications. submit the Workflow Background Process if you haven’t already. Create Workflow users and roles for your suppliers and associate e–mail addresses with them. See: To Schedule Background Engines. When you create a function activity in the Workflow Builder. you also have to create the PL/SQL stored procedure that the function activity calls. 2. Oracle Workflow Guide. Oracle Workflow Guide. Oracle Workflow Guide. 5. See: To Create a Function Activity. Place the function activity in the Issue Notifications process diagram.4. 3.

The Issue Notifications process has no result type. Unlike the PO Approval. PO Requisition Approval. You’ll always have your backup to revert to. Therefore. then choose Properties from the Edit menu. and PO Create Documents workflows in Release 11 of Purchasing. The PO Catalog Price Tolerances Exceeded Notifications Item Type The Issue Notifications process is associated with an item type called PO Catalog Price Tolerances Exceeded Notifications. select the process in the navigator tree. select the attribute in the Workflow Builder and choose Properties from the Edit menu. while you are testing your customizations. This item type identifies all workflow processes available with the price/sales catalog update submission. Deciding Whether to Modify the Original or Create a New Custom Process Customize the default (original) workflow that Purchasing provides. To view descriptions of each item type attribute. End (Valid) or End (Invalid) corresponding to any lookup type in the navigator tree. Then. Look in the Description field. if you need. indicating that when the process completes. it has no defined result of.You could place it after the Were Any Items Rejected? activity and before the Supplier Username Value activity. like you can with the other workflows in the Document Types window. These attributes reference information in the Purchasing application tables. The PO Catalog Price Tolerances Exceeded Notifications item type also has several attributes associated with it. only one price/sales catalog notification workflow can be called in Purchasing. you need to make your customizations to the default workflow. You can’t select a separate customization. for example. Purchasing Documents Open Interface 61 . Your new function activity will assign the supplier’s user name to the Supplier User Name item attribute. the Supplier Username Value activity retrieves the supplier name from the item attribute. The attributes are used and maintained by function activities as well as notification activities throughout the process. Summary of the Issue Notifications Process To view the properties of the Issue Notifications process. after you make a backup.

This process activity is runnable. The function activity Were Any Items Rejected? determines if any price updates were rejected. See Optional Customizations: page 59. Then the workflow waits for the buyer to respond before updating the price or price breaks. Issue Notifications Process Activities Following is a description of each activity listed by the activity’s display name. You can create all the components for an activity in the 62 Oracle Purchasing Documents Open Interface Documentation Update . If they were. the workflow cancels the notification so that it does not show up the next time the buyer queries for notifications. the supplier can be notified of the document lines whose prices were rejected through the function activity Notify Supplier of Price Updates that were Rejected if you customize the workflow to send automatic supplier notifications. If the buyer does not respond after the amount of time you specify in the Control Properties page of the activity Wait for Buyer Action from Exceeded Price Tolerances Form. The activity Notify Buyer of Price Updates that Exceed Tolerance sends the buyer a notification if any of the supplier price updates exceed the price tolerance you have set as described in the section Monitoring Price Increases: page 22. As soon as the buyer responds to all of the pending price updates. the notification is sent to the buyer again. indicating that it can be initiated as a top–level process to run by making calls to the Workflow Engine CreateProcess and StartProcess APIs.

this activity cancels the notification so that it doesn’t show up the next time the buyer queries for notifications. Purchasing Documents Open Interface 63 . Notify Buyer of Price Updates that Exceed Tolerance If any of the price updates in the price/sales catalog update submission exceed the tolerance you have set. Wait for Buyer Action from Exceeded Price Tolerances Form This activity waits for the buyer to respond to the notification. this activity sends the buyer a notification. The catalog submission (and the workflow) do not continue until the buyer responds. <PROCEDURE> represents the name of the procedure. All function activities execute PL/SQL stored procedures which you must create and store in the Oracle RDBMS. if you’ve customized the workflow to do so. The naming convention for the PL/SQL stored procedures used in the Issue Notifications process is: PO_WF_PO_PRICAT_UPDATE. the supplier can be be notified of the document lines whose prices were rejected through the function activity Notify Supplier of Rejected Price Updates.graphical Workflow Builder except for the PL/SQL stored procedures that the function activities call. the notification is sent to the buyer again. Were All Items Accepted or Rejected? This activity is not currently used by the workflow. One notification is sent for each document. If the buyer does not respond after the amount of time specified in the Control Properties page of this activity. Cancel any Outstanding Buyer Notifications As soon as the buyer responds to the notification.<PROCEDURE> PO_WF_PO_PRICAT_UPDATE is the name of the package that groups all the procedures used by the Issue Notifications process. If they were. Were Any Items Rejected? This activity determines if any price updates were rejected.

you can clearly see which Workflow activities are protected against customization (read–only). Workflow Customization Guidelines Following are some basic guidelines you should be aware of when customizing a workflow. See the Oracle Workflow Guide for further explanation of this feature. Supplier Username Value is a standard Workflow activity used to do comparisons. select About Oracle Workflow Builder from the Help menu in the Workflow Builder. Choose About Oracle Workflow Builder from the Help menu and make sure that it is unchecked.Supplier Username Value This activity makes sure that the supplier’s user name is on the list of user names in Oracle Applications. function activity. Also be sure that Allow modifications of customized objects is unchecked. From the Workflow Builder’s Navigator. To view your access level. It is associated with the Standard item type. See the Oracle Workflow Guide. This activity is used only if you create a function activity to populate the Supplier User Name item attribute. Access Levels You should always operate the Workflow Builder at the same consistent access level. Notify Supplier of Price Updates that were Rejected If the activity Were Any Items Rejected? records any price updates that the buyer rejected.  64 Attention: Oracle allows modifications only to those Workflow activities that are displayed as unprotected when Oracle Purchasing Documents Open Interface Documentation Update . because the level you work at affects the protection level of any changes you make to a workflow. you can determine if a Workflow activity—such as a process. this activity sends a notification to the supplier if your supplier is set up in Workflow to receive such notifications. It should be set to 100 or above. It’s very important that your access level be set to 100 or above because. or item attribute—is protected against customization by a red lock in the lower right corner of the icon. at this level. and which are unprotected (available for you to customize).

Purchasing Documents Open Interface 65 . even if you check both of the check boxes above. You can protect an individual activity through its access settings in the Control Properties window. Workflow enhancements that may be included in future upgrades of Purchasing work at an access level of 20. Checking both of these boxes means that only someone at your level (100) can overwrite your changes.you operate the Workflow Builder at an Access Level of 100 or above. checking the ”Lock at this Access Level” check box prevents a particular activity from being modified by anyone with an access level greater than 100. This is why. future upgrades will overwrite your changes. Unless instructed otherwise. At an Access Level of 100. if you work at an access level of 20. Do not modify protected Workflow objects. Checking the Preserve Customizations check box prevents the activity from being modified by anyone with an access level less than 100. you should not change your access level to something lower than 100 in an attempt to modify protected activities.  Attention: One reason it’s important to work at a consistent access level is upgrading. In the example above. The example below assumes an Access Level of 100 in the About Oracle Workflow Builder window. future Workflow upgrades will not overwrite your changes because only someone working at an access level of 100 can overwrite your changes.

Or.wft file to a backup directory/file. Enter the path name of the new directory in which you want to save a backup copy. Choose File to save the backup to a local hard disk. Open the workflow in the Workflow Builder. If you should ever have a problem with a workflow.wft file: $PO_TOP/admin/import 2. For example: D:\my_directory\my_backups 66 Oracle Purchasing Documents Open Interface Documentation Update . see: Overview of Oracle Workflow Access Protection.For complete information on how access levels work. From a UNIX prompt: 1. the first thing a support representative may ask you to do is to upload the original workflow and see if the problem still exists. Change to the directory that contains the . You can create a backup from a UNIX prompt or through the Workflow Builder. For example: cp poxprcat. Use the copy command to copy the . Select the workflow in the Navigator and choose Save As from the File menu.wft /my_directory/my_backups/poxprcat. Oracle Workflow Guide Backups and Testing Always make a backup of the original workflows that Purchasing provides before you customize them. you may have your own source control system. 2. Always test your customized workflow on a test database before uploading it to your actual database. Below are sample instructions for making backups. Oracle Workflow Guide Allowing Access to an Object. 3.wft/ Through the Workflow Builder: 1.

Purchasing Documents Open Interface 67 . you must check the Preserve Customizations check box in the process’s Control Properties window to preserve your added transition. if it is upgraded. If you copy an activity and change its internal name. Example You want to completely change Process D shown below. any future upgrades to the process provided by Purchasing will be ignored. you must check the Preserve Customizations check box in the process’s Control Properties window.  Attention: To protect your customizations to a process. decide whether to change the default activity that Purchasing provides. But if you do this.) Note: When you provide your own name to a Workflow object. function activity. or item type) to determine whether to apply the upgrade to the activity. Workflow upgrades look at the internal name and access settings of a workflow activity (such as a process. and you’ll have to reapply your call to that process after every upgrade. For example. You copy and rename it My Process. will overwrite your call to My Process. (Note: The upgrade will never overwrite My Process itself.Upgrade Support Future upgrades of Purchasing can include upgrades to the Purchasing workflows. you also must change its name in the icon in the Default Purchasing Process. you must Preserve Customizations on the Default Purchasing Process as well. Since you have changed its name. The following paragraphs describe how to help you make that decision. if you customize a process by adding a transition to a new activity in that process. And if you do this. a future upgrade to the Default Purchasing Process. since its name has changed. Otherwise. Each time you customize an activity (beyond the optional setup changes described in the Purchasing setup documentation). use a name that clearly indicates that it is a customization. or check the activity’s Preserve Customizations check box. or to copy and rename it. you protect your customization to that activity from being overwritten by future upgrades.

if there are any.If you keep the same name. if any. Future upgrades will upgrade the default process that is still there. but that you’re no longer using. In some situations. you may want to modify the default process directly if you think that your customizations are small enough to reapply after each upgrade of Purchasing. to your customized process. and you can optionally apply those upgrade changes. Based on the extent of your changes. If you make a lot of changes to a process. Therefore. this may be easier than reapplying your customizations to a completely new process created by the upgrade. If you are making minor changes to a process. you may want to copy and rename it. Process D. you’ll get future upgrades to the Default Purchasing Process. you need to decide which option will be easier for you. you can always uncheck the Preserve Customizations check box to overwrite your customizations with the upgrade. you don’t have to check the Preserve Customizations check box for the Default Purchasing Process. Note: If a future upgrade provides better functionality for your organization than your customizations. and your Process D changes will also be preserved as long as you checked its Preserve Customizations check box. 68 Oracle Purchasing Documents Open Interface Documentation Update .

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->