Payables Open Interface Reference Guide

March 26, 2018 | Author: Madhu S Reddy Palla | Category: Accounts Payable, Invoice, Exchange Rate, Variable (Computer Science), Information Technology Management
Share
Report this link


Comments



Description

Oracle Payables Reference Guide Release 12.1 Part Number E12796-04 Content Previou Nex s s t Payables Open Interface Tables Payables Open Interface Tables The Payables Open Interface tables store invoice and supplier information for import into Payables base tables. The Invoice Open Interface Import program builds Payables invoices based on the invoice records in the Payables Open Interface tables. After the import program builds the invoices, they can be viewed, modified, and validated in the Invoice Workbench. The invoice data includes EDI and XML invoices from your suppliers, invoice records that you entered in the Quick Invoices window, invoices that you loaded with Oracle SQL*Loader, lease invoices that were transferred from Property Manager, credit card transaction data, and invoices that your suppliers entered and submitted online via Oracle iSupplier Portal. The Suppliers Open Interface Import, Supplier Sites Open Interface Import, and Supplier Sites Contacts Open Interface Import process supplier information and load them into the appropriate tables. This discussion includes the following topics: • • • • • • Understanding the Invoice Open Interface Tables Understanding the Suppliers Open Interface Tables Table Descriptions Account Overlay in Payables Open Interface Import Sequential Numbering During Import How the Quick Invoices Window Populates the Payables Open Interface Tables Related Topics Payables Open Interface Import, Oracle Payables User Guide Create Procurement Card Issuer Invoice, Oracle Payables User Guide Understanding the Invoice Open Interface Tables Use the Quick Invoices window, Oracle e-Commerce Gateway, the Credit Card Invoice Interface Summary, Property Manager, the Oracle Assets Export Lease Payments to Payables process, Oracle XML Gateway, or SQL*Loader to load invoice information into the interface tables: AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE. The Payables Open Interface program validates each record you select for import, and if the record contains valid data, then the program creates a Payables invoice with distributions and scheduled payments based on the invoice header and line information in the record. Records in the AP_INVOICE_LINES_INTERFACE table create one or more invoice distributions. Note that one row may create more than one distribution. For example, if you enter a Tax line in this table and prorate it across three Item lines, during Open Interface Import the system will create three Tax invoice distributions based on the single Tax line in this table. The interface tables include columns, which Payables uses to categorize and store specific invoice information. For example, invoice source information is stored in the column called SOURCE in AP_INVOICES_INTERFACE. Columns may have the following attributes: NOT NULL Columns You must enter values for all NOT NULL columns in the interface tables to successfully save your invoice data in the interface tables. If you do not enter a value in a NOT NULL column, then you cannot save the record in the interface table. Required Columns If you do not enter a valid value in a Required field, then the record will be rejected during import. NULL Columns Leave these columns null or the import process will fail. For example, during import Payables Open Interface Import updates the values of the STATUS and REQUEST_ID columns to create invoices. Payables does not support importing any data from these columns and you should leave these columns null for the records you load in the table. Conditionally Required Columns Payables requires you to enter values in a conditionally required column only if you have entered a value in another column on which the conditionally required column is dependent. Optional Columns You can use some columns in the interface tables to import additional invoice information for the invoices created by Payables Open Interface Import. Payables Open Interface Import imports the data that you load into these optional columns, provided that the information passes the validation checks during Payables Open Interface Import. Internal ID Columns These columns contain values that Payables uses internally and the user never sees. You can obtain these values only by looking in Payables tables. These ID columns correspond to other columns in the interface table. You do not need to enter a value for any of these ID columns if you enter a value in the corresponding column. For example, if you enter the TERMS_NAME you do not need to enter the TERMS_ID. If you enter values for both columns and the values do not match, the record will be rejected during import. For example, if you enter a TERMS_NAME and a TERMS_ID, and the TERMS_ID corresponds to a different TERMS_NAME, then the record will be rejected during import. Note that when you enter invoice records in the Quick Invoices window that Payables populates the ID columns. This enables faster processing of your invoice records. Tip: If you are manually entering records: the import process will work faster if you provide values for the internal ID columns instead of the corresponding columns. Understanding the Suppliers Open Interface Tables The Supplier Open Interface Import, Supplier Sites Open Interface Import and Supplier Site Contacts Open Interface Import process the information that the user loads into AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, and AP_SUP_SITE_CONTACT_INT tables respectively. When all validations are passed, records are inserted into PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS respectively. AP_SUPPLIERS_INT holds Supplier information that is loaded by the user for import. The columns in the table map to the corresponding columns in the PO_VENDORS table. Payables uses this information to create a new Supplier record when the Supplier Open Interface Import program is submitted. AP_SUPPLIER_SITES_INT holds Supplier Site information that is loaded by the user for import. The columns in the table map to corresponding columns in the PO_VENDOR_SITES_ALL table. Payables uses this information to create a new Supplier Site record when the Supplier Sites Open Interface Import program is submitted. Defaults The intent of the Supplier Open Interface Import is to emulate the entry of Suppliers. PO_SYSTEM_PARAMETERS. Each row in the table will be joined to the appropriate Supplier Site using the VENDOR_SITE_CODE and ORG_ID and/or the VENDOR_SITE_CODE_ID. the Suppliers Open Interface Import program assigns a default organization to each run based on the responsibility of the user initiating . As such. When loading existing supplier data into the interface tables. RCV_PARAMETERS. then the values for these columns are populated from the values defined in the Supplier Tab of Payables Options: • • • • • INVOICE_CURRENCY_CODE TERMS_DATE_BASIS PAY_GROUP_LOOKUP_CODE TERMS_ID or TERMS_NAME PAY_DATE_BASIS_LOOKUP_CODE During import if no value is found both in AP_SUPPLIER_SITES_INT and Payables Options. FINANCIALS_SYSTEM_PARAMS_ALL. The columns in the table map to corresponding columns in the PO_VENDOR_CONTACTS table.AP_SUP_SITE_CONTACT_INT holds Supplier Site Contact data that is loaded by the user for import. Columns may have the attributes listed in the Understanding the Invoice Open Interface Tables section. if data is NULL in any of the following columns of supplier site interface table (AP_SUPPLIER_SITES_INT). there are many values that will be automatically defaulted if not provided by the user.ALL. and Contacts through the Supplier Entry form as closely as possible. or hard-coded values. Sites. Users may find it helpful to review the Entering Suppliers and Supplier Sites Window Reference sections. the following checks are performed to ensure data is valid: Changes to Supplier Sites Open Interface Import When importing supplier sites using Supplier Sites Open Interface import. As these source tables are organized by operating unit and the supplier data is not. These defaults for Suppliers can come from AP_SYSTEM_PARAMETERS_ALL. then the import program must default as per the current logic. Payables uses this information to create a new Supplier Site Contact record when the Supplier Site Contacts Open Interface Import program is submitted. the AP_SUPPLIER_SITES_INT table. these validations include checks performed against existing lookup values or values derived from other tables. Payables Open Interface Table Descriptions The Payables Open Interface table descriptions list the columns in the AP_INVOICES_INTERFACE table. Processing on that row then stops and the program moves on to the next row. Validations As with defaults. Rejections If an invalid value is encountered when the concurrent process is evaluating each row. the AP_INVOICE_LINES_ INTERFACE table. it is necessary to default values for Supplier Sites from AP_SYSTEM_PARAMETERS_ALL or FINANCIALS_SYSTEM_PARAMS_ALL. AP_SUPPLIER_SITES_INT. a check is performed to make sure that the value supplied is that of an active record. the tables have no foreign key relationships. When these types of validations are done. the 'REJECT_CODE' column is populated with the relevant rejection message and the 'STATUS' is updated to 'REJECTED'. a record that has not been enddated or disabled. This is necessary in order to determine which default values to assign to supplier records.the concurrent request. However. and the AP_SUP_SITE_CONTACT_INT table. the AP_SUPPLIERS_INT table. Details of the validations performed can be found in the descriptions for the AP_SUPPLIERS_INT. AP_INVOICES_INTERFACE The following table summarizes the AP_INVOICES_INTERFACE table. In addition to checks done at the database level for correct data types. Nul l Type Column Name Comments . The defaults for Supplier Sites generally come from the Supplier record. the validations performed by the Suppliers Open Interface Import program are intended to emulate the processing done by the Supplier Entry form. Although columns are validated against columns in other tables. and AP_SUP_SITE_CONTACT_INT tables. in certain cases due to multiple organizations considerations. VENDOR_NUM. VARCHAR2(5 Required if there is more 0) than one invoice for the supplier during import VARCHAR2(2 Optional 5) DATE Optional INVOICE_NUM INVOICE_TYPE_ LOOKUP_CODE INVOICE_DATE PO_NUMBER VENDOR_ID VARCHAR2(2 Validated against: 0) PO_HEADERS.VENDOR _SITE_ID VARCHAR2(1 N/A 5) NUMBER Required VENDOR_NUM VENDOR_NAME VENDOR_SITE_ID VENDOR_SITE_CODE INVOICE AMOUNT INVOICE_CURRENCY_COD E VARCHAR2(1 Optional 5) Validated against: FND_CURRENCIES. VENDOR_NUM.VENDOR_ID One of the following is required unless you match to a PO: VENDOR_ID.SEGMENT1 NUMBER(15) Internal ID Validated against: PO_VENDORS. VENDOR_NUM.INVOICE_ID NO NUMBER(15) Required. Primary key. This T value is assigned in the NUL Quick Invoices window by L the AP_INVOICES_ INTERFACE_S sequence. VENDOR_NAME VARCHAR2(8 One of the following is 0) required: VENDOR_ID. VENDOR_NAME VARCHAR2(3 One of the following is 0) required unless you match to a PO: VENDOR_ID. VENDOR_NAME NUMBER(15) Internal ID Validated against: PO_VENDOR_SITES.CURRENC Y_CODE . EXCHANGE_RATE NUMBER Validated against: GL_DAILY_CONVERSION_TYP ES.TERMS_ID VARCHAR2(5 TERMS_NAME or TERMS_ID 0) required if no terms are available through matching or at the supplier site. Validated against: AP_TERMS. VARCHAR2(2 Optional 40) NUMBER(15) Internal ID Validated against: AP_AWT_GROUPS. CONVERSION_TYPE EXCHANGE_RATE_TYPE EXCHANGE_DATE TERMS_ID VARCHAR2(3 Conditionally required 0) DATE Conditionally required NUMBER(15) Internal ID TERMS_NAME or TERMS_ID required if no terms are available through matching or at the supplier site. AWT_GROUP_ID VARCHAR2(2 Optional 5) DATE Optional TERMS_NAME DESCRIPTION AWT_GROUP_ID AWT_GROUP_NAME LAST_UPDATE_DATE LAST_UPDATED_BY LAST_UPDATE_LOGIN CREATION_DATE CREATED_BY ATTRIBUTE_CATEGORY ATTRIBUTE [1-15] GLOBAL_ ATTRIBUTE_CATEGORY GLOBAL_ATTRIBUTE [120] STATUS NUMBER(15) Optional NUMBER(15) Optional DATE Optional NUMBER(15) Optional VARCHAR2(1 Optional 50) VARCHAR2(1 Optional 50) VARCHAR2(1 Optional 50) VARCHAR2(1 Optional 50) VARCHAR2(2 N/A 5) . SOURCE GROUP_ID REQUEST_ID PAYMENT_CROSS_RATE_ TYPE PAYMENT_CROSS_RATE_ DATE PAYMENT_CROSS_RATE PAYMENT_CURRENCY_CO DE WORKFLOW_FLAG DOC_CATEGORY_CODE VARCHAR2(8 Required 0) VARCHAR2(8 Optional 0) NUMBER N/A VARCHAR2(3 N/A 0) DATE NUMBER N/A N/A VARCHAR2(1 N/A 5) VARCHAR2(1 N/A ) VARCHAR2(3 Optional if Sequential 0) Numbering Profile option is "Partial" or "Always" VARCHAR2(5 N/A 0) VARCHAR2(2 Validated against 5) AP_LOOKUP_CODES VARCHAR2(2 Validated against: 5) PO_LOOKUP_CODES DATE DATE DATE N/A N/A N/A VOUCHER_NUM PAYMENT_METHOD_ LOOKUP_CODE PAY_GROUP_LOOKUP_CO DE GOODS_RECEIVED_DATE INVOICE_RECEIVED_DATE GL_DATE ACCTS_PAY_CODE_ COMBINATION_ID USSGL_TRANSACTION_ CODE EXCLUSIVE_PAYMENT_FLA G ORG_ID AMOUNT_APPLICABLE_ TO_DISCOUNT PREPAY_NUM NUMBER(15) N/A VARCHAR2(3 N/A 0) VARCHAR2(1 N/A ) NUMBER(15) N/A NUMBER Optional VARCHAR2(5 Validated against . If you do not enter a value. You assign the same value to the invoice's lines in the AP_INVOICE_LINES_INTERFACE table to identify the data as belonging to the same invoice. Payables uses the system date at the time of import as a default. Payables Open Interface .0) PREPAY_DIST_NUM PREPAY_APPLY_AMOUNT PREPAY_GL_DATE INVOICE_INCLUDES_PREP AY_FLAG NO_XRATE_BASE_AMOUN T VENDOR_EMAIL_ADDRESS TERMS_DATE REQUESTER_ID AP_INVOICES_ALL. then during import. If you enter more than one invoice for a supplier. If you assign a duplicate number for the supplier. The number must be unique for the supplier. Variable Description Validation: Must be a unique number for the supplier.INVOICE_N UM NUMBER(15) N/A NUMBER DATE N/A N/A VARCHAR2(1 N/A ) NUMBER Used only if Payables option Calculate User Exchange Rate is enabled VARCHAR2(2 Supplier e-mail address for 000) XML invoice rejections DATE N/A NUMBER(10) N/A INVOICE_ID Unique identifier for this invoice within this batch. or the invoices will have duplicate invoice numbers and will be rejected during import. Descriptio n Variable Validation: None Destinatio None n: INVOICE_NUM Enter the invoice number that you want to assign to the invoice created in Payables from this record. then be sure to enter unique invoice numbers rather than using the default. Payables may use the Invoice Date as the Terms Date and the GL Date for an invoice. . you can import prepayments using the Payables Open Interface Import program.INVOICE_TYPE_LOOKUP_ CODE n: INVOICE_DATE Date of the invoice. a Credit invoice must have an invoice amount that is less than zero. Variable Description Validation: The value must be in valid date format. Destinatio AP_INVOICES_ALL. If your GL Date Basis is Invoice Date. Destinatio AP_INVOICES_ALL. If you do not use Quick Invoices. If you match the invoice to a purchase order by entering a value here. the system uses the date you submit Payables Open Interface Import as the invoice date. the system assigns a value during Payables Open Interface Import based on the value of INVOICE_AMOUNT. If INVOICE_AMOUNT is zero or greater.Import does not create an invoice from this record. If you do not enter a value. If INVOICE_AMOUNT is less than zero. depending on your system setup. The invoice type must correspond to the invoice amount if it is Credit or Standard.INVOICE_NUM n: INVOICE_TYPE_LOOKUP_CODE Type of invoice: Credit or Standard.INVOICE_DATE n: PO_NUMBER Number of the purchase order to which you are matching the invoice. For example. If you do not enter a value. the invoice will be Standard. and if you do not specify a supplier in the AP_INVOICES_INTERFACE table. Variable Description Validation: The value must be Credit or Standard. during Payables Open Interface Import the system uses purchase order information to create distributions and populate various columns in the AP_INVOICE_DISTRIBUTIONS_ALL table. the invoice will be Credit. Destinatio AP_INVOICES_ALL. When using the Service Procurement. then the Invoice Date must be in an open or future period. If you have not yet entered the supplier in the Suppliers window. or PO_NUMBER. If the source is e-Commerce Gateway. Destinatio AP_INVOICES_ALL.VENDOR_SITE_ID. open purchase order for the same supplier. AP_INVOICE_LINES_INTERFACE. the PO_NUMBER value could be used to derive AP_INVOICES_ALL. VENDOR_NUM. You must identify the supplier by entering a value for one of the following columns in this table: VENDOR_ID. You can obtain a list of valid values from PO_VENDORS. VENDOR_NUM. VENDOR_SITE CODE. For other invoice sources.VENDOR_ID. enter it before import. or PO_NUMBER. and if you do not specify the supplier site. The purchase order must not be final matched. then enter it before import. you do not need to enter a value here at the invoice header level if you enter a value at the line level. VENDOR_SITE_ID. approved. Variable Description Validation: The ID you enter must be for an existing. Variable Description Validation: This value must match a valid. You can obtain a list of valid values from PO_HEADERS. valid supplier.PO_NUMBER. To match an invoice to a purchase order. You must identify the supplier by entering a value for one of the following columns in this table: VENDOR_ID. . tolerances are checked at Invoice Validation time. If you have not yet entered the supplier in the Suppliers window.VENDOR_ID n: VENDOR_NUM Supplier number.then the PO_NUMBER value is used to derive AP_INVOICES_ALL. Destinatio None n: VENDOR_ID The internal supplier identifier for the supplier. VENDOR_SITE_ID.VENDOR_ID. Payables will import invoices only if they are within the quantity and price tolerance you have specified in the Invoice Tolerances window.SEGMENT1. VENDOR_SITE_ID. VENDOR_SITE_ID Internal supplier site identifier. VENDOR_NUM. If you have not yet entered the supplier in the Suppliers window. This value is used to enter n: AP_INVOICES_ALL.VENDOR_ID. You can obtain a list of valid values from PO_VENDOR_SITES. Destinatio None. You can obtain a list of valid values from PO_VENDORS. This value is used to enter n: AP_INVOICES_ALL. Destinatio None. valid supplier site for the supplier you specify (VENDOR_NUM or VENDOR_ID). The site must also be a pay site. then enter it before import. valid supplier. You can obtain a list of valid values from PO_VENDORS. or PO_NUMBER.Variable Description Validation: The number must be for an existing. VENDOR_SITE CODE.VENDOR_SITE_ID.VENDOR_SITE_ID n: .VENDOR_NAME. valid. VENDOR_NAME Name of the supplier. You must identify the supplier by entering a value for one of the following columns in this table: VENDOR_ID. active supplier. Destinatio AP_INVOICES_ALL. Variable Description Validation: This must be an existing.VENDOR_ID. Variable Description Validation: The ID you enter must be for an existing.SEGMENT1. If you do not provide a valid value to identify the pay site in VENDOR_SITE_CODE or VENDOR_SITE_ID then import searches for a valid supplier pay site in the following order: • • • primary pay site for supplier single existing pay site for supplier derived from PO Number matched at the header level Import rejects the invoice if it cannot identify a valid supplier site. if you are entering an amount in US dollars.VENDOR_SITE_ID. then do not enter more than two numbers after the decimal point. If you do not provide a valid value to identify the pay site in VENDOR_SITE_CODE or VENDOR_SITE_ID then import searches for a valid supplier pay site in the following order: • • • primary pay site for supplier single existing pay site for supplier derived from PO Number matched at the header level Import rejects the invoice if it cannot identify a valid supplier site. This value is used to enter n: AP_INVOICES_ALL.VENDOR_SITE_CODE. Do not exceed the precision of the currency of for the invoice. Destinatio AP_INVOICES_ALL. active supplier site for the supplier you specify (VENDOR_NUM or VENDOR_ID). then the supplier site value defaults during import. Standard invoices must have an amount of zero or greater. Variable Description Validation: This must be a valid.VENDOR_SITE_CODE Supplier site name. Variable Description Validation: This value must equal the sum of the AMOUNT values in the AP_INVOICE_LINES_INTERFACE table for lines with the same INVOICE_ID. . You can obtain a list of valid values from PO_VENDORS. INVOICE_AMOUNT Amount of the invoice. For example. The amount must correspond to the invoice type. Destinatio None. If you do not enter a value.INVOICE_AMOUNT n: INVOICE_CURRENCY_CODE Currency code for the invoice. The site must also be a pay site. For example. Note: When the invoice currency and payment currency are associated fixed-rate currencies the PAYMENT_CROSS_RATE_TYPE. If the Payables option Require Exchange Rate Entry is enabled. then do not overwrite the value that the Quick Invoices window provided or import will reject the invoice record.PAYMENT_CROSS_RATE.EXCHANGE_RATE n: EXCHANGE_RATE_TYPE Type of exchange rate used to calculate the exchange rate between the invoice currency and your functional currency. then you can provide a value for NO_XRATE_BASE_AMOUNT instead). then during import Payables overwrites any value you enter with the fixed rate. Destinatio AP_INVOICES_ALL. you must enter a valid. then the import program supplies the exchange rate value. Variable Description Validation: If you entered the invoice record in the Quick Invoices window. then enter . then you must provide a value for EXCHANGE_RATE (or. active currency code from FND_CURRENCIES.INVOICE_CURRENCY_ CODE n: EXCHANGE_RATE Invoice exchange rate for a foreign currency invoice. If the value in the INVOICE_CURRENCY_CODE column is a foreign currency code. then you must provide either an exchange rate or sufficient information for Payables to derive the exchange rate during import. If you did not enter the invoice record in the Quick Invoices window. You can see any occurrences of Payables overwriting the exchange rate by reviewing the log file for the import. and PAYMENT_CROSS_RATE_DATE are not imported to AP_INVOICES_ALL Variable Description Validation: If you enter a code in a foreign currency. If the invoice currency has a fixed rate to your functional currency. if the Payables option Calculate User Exchange Rate is enabled. and if you enter SPOT or CORPORATE as the EXCHANGE_RATE_TYPE. If EXCHANGE_RATE_TYPE is User. Destinatio AP_INVOICES_ALL.CURRENCY_CODE. and you should leave this column null. then during import the system uses the Exchange Rate Type selected in the Payables Options window.EXCHANGE_DA n: TE TERMS_ID Internal identifier for the payment terms. or any user-defined rate type. Variable Description Validation: Payables uses five types of exchange rates: User. Corporate. EMU Fixed. then enter EMU Fixed.EXCHANGE_RATE_TYPE n: EXCHANGE_DATE Enter a value in this column if you enter a foreign currency code in the CURRENCY_CODE column. If you use Spot. If you use User as the exchange rate type. If the invoice currency and your functional currency are associated fixed-rate currencies. Destinatio AP_INVOICES_ALL. If you use EMU Fixed. Corporate. or user-defined rate type. you must either enter a value for EXCHANGE_RATE or. If you want to specify payment terms you need to enter a value in only one of the following columns: TERMS_NAME or TERMS_ID. Spot.a value in this column to indicate which exchange rate type you are using. The import process searches the following sources in the following order for payment terms and uses the first terms it finds: . Destinatio AP_INVOICES_ALL. if the Payables Option Calculate User Exchange Rate is enabled. Variable Description Validation: Must be in valid date format. Payables provides the exchange rate during import. If you leave this column null. Corporate. such as euro and another EMU currency. Payables uses the the invoice GL Date. You can enter a predefined or user-defined exchange rate type. If the invoice record has a foreign currency and you do not enter a value for EXCHANGE_RATE_TYPE. and user-defined. the value you enter here is validated against the GL Daily Rates table. You maintain payment terms in the Payment Terms window. The date you enter determines the exchange rate for a foreign currency invoice with a Spot. you can enter a value for NO_XRATE_BASE_AMOUNT instead. Variable Description . supplier site If none of these sources has a value for payment terms. If you use calendar-based payment terms and no calendar period is defined for the terms date. You maintain payment terms in the Payment Terms window. then the system uses the terms date as the due date when it creates the scheduled payment. Variable Description Validation: Terms must be valid terms in the AP_TERMS table.TERMS_ID. purchase order terms for the purchase order in the invoice header (if the invoice record is purchase order matched at the header level) 3. or indirectly through a receipt (if not more than one set of terms is represented) 4.1. invoice record header (TERMS_ID or TERMS_NAME) 2. Destinatio AP_INVOICES_ALL. The import process searches the following sources in the following order for payment terms and uses the first terms it finds: 1. purchase order terms for the purchase orders to which one or more lines are matched directly. then the system uses the terms date as the due date when it creates the scheduled payment. If you use calendar-based payment terms and no calendar period is defined for the terms date. then the invoice record is rejected. then the invoice record is rejected. invoice record header (TERMS_ID or TERMS_NAME) 2. or indirectly through a receipt (if not more than one set of terms is represented) 4. If you want to specify payment terms you need to enter a value in only one of the following columns: TERMS_NAME or TERMS_ID. purchase order terms for the purchase orders to which one or more lines are matched directly. n: TERMS_NAME Payment terms. supplier site If none of these sources has a value for payment terms. purchase order terms for the purchase order in the invoice header (if the invoice record is purchase order matched at the header level) 3. it is used only if you do not identify a withholding tax group for the invoice lines in the AP_INVOICE_LINES_INTERFACE.AWT_GROUP_ID or AP_INVOICE_LINES_INTERFACE.DESCRIPTION the Item Description from the purchase order line. Destinatio AP_INVOICES_ALL. . Destinatio None. then during Payables Open Interface Import the system will assign to AP_INVOICES_ALL. active terms in the AP_TERMS table.DESCRIPTIO n: N AWT_GROUP_ID Internal identifier for Automatic Withholding Tax Group.AWT_GROUP_NAME.Validation: Terms must be valid. it must be a valid value in AP_AWT_GROUPS. Variable Description Validation: None Destinatio AP_INVOICES_ALL.AWT_GROUP_NAME column.TERMS_ID. If you are matching to a purchase order and you do not enter a value here. The withholding tax group you identify in this table (AWT_GROUP_ID or AWT_GROUP_NAME) is used to assign a withholding tax group to a line only if you do not identify one for the invoice in one of the following columns: AP_INVOICE_LINES_INTERFACE.AWT_GROUP_ID or AP_INVOICE_LINES_INTERFACE. Variable Description Validation: If this value is used during import.AWT_GROUP_ID or AP_INVOICE_LINES_INTERFACE.AWT_GROUP_NAME.AWT_GROUP_ID. If you identify a withholding tax group in this table (AWT_GROUP_ID or AWT_GROUP_NAME). DESCRIPTION Enter the description that you want to assign to the invoice created from this record. You maintain withholding tax groups in the Withholding Tax Groups window. This value may be used to enter a value for n: AP_INVOICES_ALL. only if you do not enter n: another value for AP_INVOICE_LINES_INTERFACE. AWT_GROUP_NAME Automatic Withholding Tax Group. LAST_UPDATED_ DATE LAST_UPDATED_BY Enter the userid of the person who last updated this record (usually the same value as CREATED_BY). then during Payables Open Interface Import the system will use the system date. n: AP_PAYMENT_SCHEDULES. the system uses it to populate AP_INVOICES_ALL.AP_LAST_UPDATE_LOGIN.LAST_UPDATED_BY LAST_UPDATE_LOGIN The last date for this record. If you do not enter a value. Variabl e Description Validati None on: . then during Payables Open Interface Import the system will use the userid of the person who submits Payables Open Interface Import.LAST_UPDATED_DATE. Variable Description Validation: Must be in valid date format. AP_ n: PAYMENT_SCHEDULES.LAST_UPDATED_BY. If you enter a value in this column. Usually the same date as the CREATION_DATE.Variable Description Validation: Value must be valid and active in AP_AWT_GROUPS Destinatio None n: LAST_UPDATE_DATE Enter the last update date for this record (usually the same date as CREATION_DATE). Variable Description Validation: None Destinatio AP_INVOICES_ALL. Destinatio AP_INVOICES_ALL. Payables uses this date for reference and audit purposes only. If you do not enter a value here. CREATED_BY ATTRIBUTE_CATEGORY Enter the descriptive flexfield category for the descriptive flexfield information you want to import. Payables Open Interface Import transfers this ID to the AP_INVOICES_ALL and AP_PAYMENT_SCHEDULES tables during import so that the creator of the record becomes the invoice and scheduled payment creator. When Payables Open Interface Import creates an invoice from this record.Destina AP_INVOICES_ALL.CREATION_DATE. it does not use this date as the creation date for the invoice. then during Payables Open Interface Import the system will use the userid of the person who submits Payables Open Interface Import. n: AP_PAYMENT_SCHEDULES.CREATION_DATE CREATED_BY Enter the userid of the person that loads this record into the table. Variable Description Validation: None Destinatio AP_INVOICES_ALL.AP_LAST_UPDATE_LOGIN CREATION_DATE Enter the date on which you load this record into the interface table. If you do not enter a value.ATTRIBUTE_CATEGO n: RY ATTRIBUTE [1-15] . Variable Description Validation: None Destinatio AP_INVOICES_ALL.CREATED_BY.AP_LAST_UPDATE_LOGIN. Variable Description Validation: Must be in valid date format.AP_PAYMENT_SCHED tion: ULES. n: AP_PAYMENT_SCHEDULES. Destinatio AP_INVOICES_ALL. it uses the system date at the time you submit Payables Open Interface Import. Payables uses this date for reference and audit purposes. The structure of the information you enter in these columns (datatypes. value sets) must match the structure of the descriptive flexfield segments you have defined for your invoices or you will experience validation problems when you try to access the information in the invoice windows. Variable Description Validation: If you are using a localization. The structure of the information you enter in these columns (datatypes. see you localization user's guide. Variable Description Validation: None Destinatio AP_INVOICES_ALL.GLOBAL_ATTRIBUTE_ n: CATEGORY GLOBAL_ATTRIBUTE [1-20] Enter descriptive flexfield information that you want to import for an invoice. Destinatio AP_INVOICES_ALL. value sets) must match the structure of the descriptive flexfield segments you have defined for your invoices or you will experience validation problems when you try to access the information in the invoice windows. . you must enter appropriate values in this flexfield or the invoice will be rejected during import.ATTRIBUTE[1n: 15] GLOBAL_ATTRIBUTE_CATEGORY Enter the descriptive flexfield category for the descriptive flexfield information you want to import.Enter descriptive flexfield information that you want to import for an invoice. Variable Description Validation: None Destinatio AP_INVOICES_ALL.GLOBAL_ATTRIBUTE[1-20] n: STATUS Do not enter a value in this field. It is for internal use only. For more information. this value is the Quick Invoices Batch Name. or Payables Open Interface Import will not create an invoice from the record.SOURCE n: GROUP_ID Identifier for this batch. do not use the same source name for invoices that you enter in Quick Invoices. EDI Gateway (e-Commerce Gateway). RTS (Return to Supplier).Variable Descriptio n Validation: None Destinatio None n: SOURCE Source of the invoice data. ERS (Evaluated Receipt Settlement). Oracle Property Manager. for example. Examples include Quick Invoices. The lookup value must have the Type SOURCE. Processing records by Group allows you to concurrently import or purge subsets of records for the same Source. If you have defined additional sources. Oracle Payables Implementation Guide. you should use a source name for only one type of source. Destinatio AP_INVOICES_ALL. For example. You define additional values for Source in the Oracle Payables Lookups window. When you submit Payables Open Interface Import or Purge Payables Open Interface. and invoices you load with SQL*Loader. The Source name also determines which records will be selected for import or purge. Credit Card. For invoice records entered in the Quick Invoices window. Oracle Assets. You specify a Source name when you submit Payables Open Interface Import or Purge Payables Open Interface. See: Lookups. You may want to assign a Group ID if you are processing a large number of records. and user-defined. you must specify a Source and you can optionally specify a Group. Variable Descriptio . importing legacy data. Variable Description Validation: If you do not use a predefined source you must enter the name exactly as you have defined the lookup value in the Oracle Payables Lookups window. XML Gateway. If the invoice and payment currencies are the same. and the system will ignore the value you provided. Descriptio n Variable Validation: None Destinatio None n: PAYMENT_CROSS_RATE_TYPE If the invoice currency and payment currency are associated fixed-rate currencies.PAYMENT_CROSS_RATE_ TYPE n: PAYMENT_CROSS_RATE If the invoice currency and payment currency are different currencies and are both associated fixed-rate currencies (for example. If the invoice currency and payment currency are .n Validation: None Destinatio None n: REQUEST_ID The system populates this field with the concurrent request ID number for the Payables Open Interface Import process. enter EMU FIXED. Destinatio AP_INVOICES_ALL. Variable Description Validation: If the invoice currency and payment currencies are different fixed-rate currencies. Payables will overwrite whatever value you enter here with EMU FIXED. Payables will provide the cross rate during import. the fixed rate in the GL_DAILY_RATES table will be used. euro and another EMU currency). If you leave this value null. you can enter the fixed cross rate. Otherwise. this value must be null. Variable Description Validation: If this value is different from the cross rate in the GL_DAILY_RATES table. Leave this column null. then during import. leave this value null. such as Euro or an EMU national currency. This must be a valid. Variable Description Validation: If the invoice currency is not a fixed rate currency. .the same.PAYMENT_CURRENCY_ CODE n: WORKFLOW_FLAG Payables Open Interface Workflow status of the invoice record. you can enter 1 as the value. If the values for PAYMENT_CURRENCY_CODE and INVOICE_CURRENCY_CODE are different. You submit this workflow before import. and the two currencies must have a fixed rate effective as of the cross rate date or the invoice will be rejected.PAYMENT_CROSS_RATE n: PAYMENT_CROSS_RATE_DATE Date cross rate between invoice currency and payment currency is effective. you must enter a value for PAYMENT_CROSS_RATE_DATE. this value must be the same as INVOICE_CURRENCY_CODE. Destinatio AP_INVOICES_ALL. the PAYMENT_CROSS_RATE will be set to 1. and the PAYMENT_CROSS_RATE_TYPE and the PAYMENT_CROSS_RATE_DATE will both be null.PAYMENT_CROSS_RATE_DATE n: PAYMENT_CURRENCY_CODE Currency code for the payment. then during import PAYMENT_CURRENCY_CODE will be set to the same value as the INVOICE_CURRENCY_CODE. If the invoice currency is a fixed-rate currency. If you do not provide a value. Destinatio AP_INVOICES_ALL. Destinatio AP_INVOICES. active currency code from FND_CURRENCIES.CURRENCY_CODE. you can enter an associated fixedrate currency. Variable Description Validation: This value must be the exact cross rate in the GL_DAILY_RATES table. If you enter D. D. and CREDIT if the invoice amount is negative. then the invoice amount must be positive.FND_DOC_SEQUENCE_ CATEGORIES. Oracle Payables Implementation Guide. If you enter the value of Standard. Processing. you can enter the document category you want Payables Open Interface Import to assign to the invoice created from this record. If the Sequential Numbering profile value is "Always" and you do not enter a value in this column. then during import Payables will use STANDARD as the category if the invoice amount is zero or positive. The import program will not process invoice records with this status. instead of the Standard or Credit document category. Workflow is currently processing invoice record. Processed.If you are using the Payables Open Interface Workflow and you want Workflow to process this record. then the invoice amount must be negative. it must have an active. Workflow will not process this record. Workflow has processed the invoice record and it is ready for import. S. Invoice record will be processed by workflow. Variable Description Validation: The value is a valid value in AP_INVOICES_ALL. See: Payables Open Interface Import Workflow. To Be Processed. Null. The import program will not process invoice records with this status. enter Y. • • • • Y. If you enable the Allow Document Category Override Payables option. and the Allow Document Category Override Payables option is enabled. Not Applicable. and if you enter the value of Credit. We assume that a valid automatic sequence exists for such categories. Do not enter a value in this column unless the Sequential Numbering profile option is set to Partial or Always. If you enter a document category. . Invoice record is ready for import. Descriptio n Variable Validation: None Destinatio None n: DOC_CATEGORY_CODE If you are using automatic sequential numbering. then Payables Open Interface Import uses this column to assign a document category to the invoice it creates. the system validates the voucher number for uniqueness. If the supplier site does not have a value for Pay Group. Variable Description Validation: If you use manual sequential numbering. then enter a unique value for the voucher number you want to apply to the invoice created from this record. Destinatio AP_INVOICES_ALL. . Payment Methods are user defined in Oracle Payments PAY_GROUP_LOOKUP_CODE Pay Group to which the invoice will be assigned. Variable Validatio n: Description The value must be a valid value for the PAYMENT_METHOD lookup code.LOOKUP_CODE. the value will default from the supplier site.DOC_CATEGORY_CODE n: VOUCHER_NUM If you use manual sequential numbering.automatic sequence assigned to it. The number should not exceed nine digits or you will have problems processing the invoice in Payables. Variable Description Validation: The value must be a valid and active value in AP_LOOKUP_CODES. If neither the supplier nor the supplier site has a value.VOUCHER_NUM n: PAYMENT_METHOD_LOOKUP_CODE Method that will be used to pay the invoice. Payables ignores any value you load into this column and instead selects the next available number for the numbering sequence assigned to the document category for imported invoices. with a LOOKUP_TYPE value of PAYGROUP. then the value will default from the supplier. the system uses the default Pay Group Payables option. If you do not enter a value. If you use automatic sequential numbering. Destinatio AP_INVOICES_ALL. Purchase order matched invoices must use an organization consistent with the purchase order. and if your Terms Date Basis Payables option is set to Invoice Received. If this column has no value then the system uses the ORG_ID associated with the responsibility used to submit import.Destinatio AP_INVOICES_ALL. Payables will use the value as the terms date. Variable Description Validation: The value must have a valid date format. Destinatio AP_INVOICES_ALL. Variable Description Validation: The value must have a valid date format. Payables will use this value as the terms date.PAY_GROUP_ LOOKUP_CODE n: GOODS_RECEIVED_DATE If you do not provide a value for TERMS_DATE. Variable Description Validation: Must be a valid organization. Destinatio AP_INVOICES_ALL. Quick Invoices records are assigned the ORG_ID associated with the user's responsibility.ORG_ID n: GL_DATE .GOODS_RECEIVED_D n: ATE INVOICE_RECEIVED_DATE If you do not provide a value for TERMS_DATE. then if you provide a value here. then if you provide a value here.INVOICE_RECEIVED_DA n: TE ORG_ID Organization identifier. . and if your Terms Date Basis Payables option is set to Goods Received. Destinatio AP_INVOICES_ALL. Variable Description Validation: Must be a valid account in your chart of accounts. If you do not provide a value. you must enter a GL Date in a period that is within the latest open encumbrance year. The date must be in an open or future period. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Important: If you are using encumbrance accounting. then Payables uses the system date at time of import. then Payables uses the Goods Received Date. Payables defaults this value to invoice distributions during import. Payables looks for a GL Date value to assign to the invoice distribution. if it is populated. then Payables uses the Invoice Date. and it searches the following sources in the following order: invoice record line. During import. If not. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. If it is not. Payables assigns a value from the first source it finds. Payables uses the liability account when you create accounting entries for your invoices if you use accrual basis accounting.The GL Date for the invoice distributions. Note: The following occurs if the system searches at the GL Date Basis level: If the GL Date Basis option is set to Goods Received/Invoice Date. if it is populated. the system uses the account from the supplier site. invoice record header. The date must be in an open or future accounting period. (See also: Budgetary Control In Payables). GL Date Basis Payables option.ACCTS_ n: PAY_CODE_COMBINATION_ID USSGL_TRANSACTION_CODE . If the GL Date of an invoice is in a future period in Payables. Payables credits the liability account in an amount equal to the sum of your invoice distributions. then Payables uses the Goods Received Date. Variable Description Validation: Must be in valid date format. ACCOUNTING_DATE (if no n: value is provided at line level) ACCTS_PAY_CODE_COMBINATION_ID Liability account. If the GL Date Basis option is set to Goods Received/System Date. you can account for the invoice but you cannot pay it. GL Date parameter from import submission. Enter the default transaction code you want to assign to an invoice. Open Interface Import imports any USSGL information that you load into the interface tables and assigns the information to the invoices it creates. Variable Description Validation: None Destinatio AP_INVOICES_ALL.ORG_ID n: AMOUNT_APPLICABLE_TO_DISCOUNT Invoice amount applicable to discount. A pay alone invoice is paid with its own payment document without including other invoices for the supplier. If this column has no value then the system uses the ORG_ID associated with the responsibility used to submit import. Purchase order matched invoices must use an organization consistent with the purchase order. Variable Description Validation: None Destinatio AP_INVOICES_ALL. Variable Description Validation: Must be a valid organization. Quick Invoices invoice records are assigned the ORG_ID associated with the user's responsibility. Variable Description . Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. This value must be consistent with the ORG_ID value at the invoice header.EXCLUSIVE_PAYMENT_ n: FLAG ORG_ID Organization identifier.USSGL_TRANSACTION_ n: CODE EXCLUSIVE_PAYMENT_FLAG Pay Alone flag. is type Temporary. PREPAY_DISTRIBUTION_ID n: PREPAY_APPLY_AMOUNT If you are applying prepayments. is fully paid. Variable Description Validation: Must be a valid distribution number on the prepayment. and has not been fully applied. Leave this field blank to apply all available prepayment Item distributions. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. up to the prepayment amount. starting with the lowest distribution number first. . must be an Item distribution. Destinatio None. then import applies the specified prepayment first. Oracle Payables User Guide. starting with the oldest prepayment first. then applies remaining available prepayments (oldest first) up to the specified PREPAY_APPLY_AMOUNT. If the PREPAY_APPLY_AMOUNT exceeds the amount available on the specified prepayment. For more information see: Applying Prepayments to Invoices in the Open Interface. has the same invoice and payment currency as the invoice. Payables ensures that the prepayment amount does not exceed the invoice amount.Validation: None Destinatio AP_INVOICES_ALLAMOUNT_APPLICABLE_TO_DISCOU n: NT. and cannot be a reversal distribution. Import uses this information to populate n: AP_INVOICES_DISTRIBUTIONS_ALL. PREPAY_DISTRIBUTION_ID PREPAY_DIST_NUMBER Distribution number of a specific Item distribution on the specified prepayment that you want to apply. up to the amount of the invoice. Leave this column null to apply all available prepayments in chronological order. Variable Description Validation: The prepayment has a settlement date on or before the system date. the maximum currency amount of the prepayments you want to apply to the invoice. PREPAY_NUM Invoice number of a specific prepayment that you want to apply. Import uses this value and the INVOICE_AMOUNT to calculate and enter the invoice exchange rate. Oracle Payables User Guide. Used only if the Payables option Calculate User Exchange Rate is enabled and if the exchange rate type is User. n: INVOICE_INCLUDES_PREPAY_FLAG NO_XRATE_BASE_AMOUNT Invoice functional currency amount. then import will use the system date as the prepayment accounting date.Variable Description Validation: Must not exceed unpaid invoice amount or amount of available prepayments. Cannot be zero or a negative number. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Destinatio AP_INVOICES_DISTRIBUTIONS_ALL. Variable Description Validation: The date must be in an open or future period. If you do not enter a value. Variable Description Validation: None Destinatio AP_INVOICES_DISTRIBUTIONS_ALL. Variable Description Validation: If you provide a value for NO_XRATE_BASE_AMOUNT the Payables option Calculate User Exchange Rate must be . n: ACCOUNTING_DATE INVOICE_INCLUDES_PREPAY_FLAG A value of Y indicates that the invoice amount has been reduced by a prepayment. PREPAY_APPLY_AMOUNT n: PREPAY_GL_DATE Accounting date for the application of the prepayment. For more information see: Entering Invoices that Reference Prepayments. When the invoice is imported the amount paid on the invoice will not be reduced by the prepayment applied to it. This will be the GL date on the new Prepayment type distribution on the imported invoice. Destinatio AP_INVOICES_ALL.TERMS_DATE n: REQUESTER_ID . For a list of these import rejections. then you must provide the correct exchange rate or import will reject the invoice.enabled. and if the exchange rate type is User.BASE_AMOUNT n: VENDOR_EMAIL_ADDRESS Supplier e-mail address. If you enter values for both NO_XRATE_BASE_AMOUNT and EXCHANGE_RATE. Oracle Payables Implementation Guide. and the exchange rate type must be User. Descriptio n Variable Validation: None Destinatio None n: TERMS_DATE Date that Payables uses as the payment terms start date. Variable Description Validation: The value must be in a valid date format. Destinatio AP_INVOICES_ALL. Oracle XML Gateway populates this column when it loads XML invoice records to Payables. then you are required to enter a value for either NO_XRATE_BASE_AMOUNT or EXCHANGE_RATE. see: Processing Oracle XML Gateway Invoice Records. If the Payables option Calculate User Exchange Rate is enabled. Certain invoice import failures will cause a workflow notification of the problem to be sent to the supplier at this specified email address. If you leave this value blank then the system derives the value based on the Terms Date Basis Payables option if you have provided a value for the corresponding column. Required INVOICE_LINE_ID LINE_NUMBER LINE_TYPE_LOOKUP_CO DE LINE_GROUP_NUMBER AMOUNT NUMBER(1 5) VARCHAR2( Required 25) NUMBER NUMBER Optional Required . Payables uses this value only when it sends error notifications to the supplier for XML invoices.ID of person who requested the goods or services on the invoice. Descriptio n Variable Validation: None Destinatio None n: AP_INVOICE_LINES_INTERFACE Nu ll Type NO NUMBER(1 T 5) NU LL NUMBER(1 5) Column Name INVOICE_ID Comments Required Validated against: AP_INVOICES_INTERFACE Internal ID. existing employee. Must be unique for the INVOICE_ID. Value provided by the AP_INVOICE_LINES_INTERFACE_S sequence.REQUESTER_ID n: EXTERNAL_DOC_REF Identifier your supplier assigns to this invoice record. Destinatio AP_INVOICES_ALL. Required. Variable Description Validation: This ID must correspond to a valid. then you can define rules that use this value to generate a hierarchical list of approvers for the invoice. Primary key. If you use Invoice Approval Workflow. PO_DISTRIB UTION_ID Optional Validated against: PO_DISTRIBUTIONS.SHIPMENT_ NUM Internal ID Validated against: PO_DISTRIBUTIONS.LINE_LOCA TION_ID Optional Validated against: PO_LINE_LOCATIONS.PO_LINE_NUM Internal ID Validated against: PO_LINE_LOCATIONS.PO_DISTRIB UTION_NUM Optional Validated against: MTL_SYSTEM_ITEMS.NAME VARCHAR2( N/A 1) NUMBER Internal ID Validated against: PO_HEADERS.INVENTORY _ITEM_ID PO_LINE_ID PO_LINE_NUMBER NUMBER PO_LINE_LOCATION_ID NUMBER PO_SHIPMENT_NUM NUMBER PO_DISTRIBUTION_ID NUMBER PO_DISTRIBUTION_NUM NUMBER INVENTORY_ITEM_ID NUMBER .ACCOUNTING_DATE DESCRIPTION PRORATE_ACROSS_FLA G TAX_CODE FINAL_MATCH_FLAG PO_HEADER_ID DATE N/A VARCHAR2( Optional 240) VARCHAR2( Optional 1) VARCHAR2( Validated against: 15) AP_TAX_CODES.PO_HEADER_ID PO_NUMBER VARCHAR2( Optional 20) Validated against: PO_HEADERS.PO_LINE_ID Optional Validated against: PO_LINES.SEGMENT1 NUMBER Internal ID Validated against: PO_LINES. CODE_COMBINATION_ID Internal ID Validated against: AP_AWT_GROUPS.GROUP_ID AWT_GROUP_ID NUMBER(1 5) AWT_GROUP_NAME LAST_UPDATED_BY LAST_UPDATE_DATE LAST_UPDATE_LOGIN CREATED_BY CREATION_DATE ATTRIBUTE CATEGORY ATTRIBUTE [1-15] GLOBAL_ATTRIBUTE CATEGORY VARCHAR2( Optional 25) NUMBER(1 5) DATE NUMBER(1 5) NUMBER(1 5) DATE Optional Optional Optional Optional Optional VARCHAR2( Optional 150) VARCHAR2( Optional 150) VARCHAR2( Optional 150) .ITEM_DESCRIPTION QUANTITY_INVOICED SHIP_TO_LOCATION_CO DE UNIT_PRICE DISTRIBUTION_SET_ID VARCHAR2( Optional 240) NUMBER Optional VARCHAR2( N/A 25) NUMBER NUMBER(1 5) Optional Internal ID Validated against: AP_DISTRIBUTION_SETS. DISTRIBUTION_SET_ID DISTRIBUTION_SET_NA ME DIST_CODE_CONCATEN ATED DIST_CODE_COMBINATI ON_ID VARCHAR2( Optional 50) VARCHAR2( Optional 250) NUMBER(1 5) Internal ID Validated against: GL_CODE_COMBINATIONS. GLOBAL_ATTRIBUTE [120] PO_RELEASE_ID VARCHAR2( Optional 150) NUMBER Optional Validated against: PO_RELEASES_ALL Optional RELEASE_NUM ACCOUNT_SEGMENT BALANCING_SEGMENT COST_CENTER_SEGMEN T PROJECT_ID TASK_ID EXPENDITURE_TYPE EXPENDITURE_ITEM_DA TE EXPENDITURE_ ORGANIZATION_ID NUMBER VARCHAR2( Optional 25) VARCHAR2( Optional 25) VARCHAR2( Optional 25) NUMBER(1 5) NUMBER(1 5) Internal ID Validated against: PA_PROJECTS Internal ID Validated against: PA_TASKS VARCHAR2( Validated against: 30) PA_EXPENDITURE_TYPES DATE NUMBER(1 5) Validated against: PA_EXPENDITURE_TYPES Validated against PER_ORGANIZATION_UNITS. EXPENDITURE_ORGANIZATION_I D PA_ADDITION_FLAG PA_QUANTITY USSGL_TRANSACTION_ CODE STAT_AMOUNT TYPE_1099 INCOME_TAX_REGION ASSETS_TRACKING_FLA G TAX_CODE_ID VARCHAR2( Projects 1) NUMBER Projects VARCHAR2( General Ledger 30) NUMBER N/A VARCHAR2( N/A 10) VARCHAR2( N/A 10) VARCHAR2( N/A 1) NUMBER(1 N/A . RECEI PT_NUM VARCHAR2( N/A 25) VARCHAR2( N/A 25) VARCHAR2( N/A 25) NUMBER NUMBER(1 5) NUMBER(1 5) N/A Identifier of the corresponding receivable intercompany invoice in Oracle Receivables Identifier of the corresponding receivable intercompany invoice in Oracle Receivables RECEIPT_LINE_NUMBER MATCH_OPTION PACKING_SLIP RCV_TRANSACTION_ID PA_CC_AR_INVOICE_ID PA_CC_AR_INVOICE_LIN E_NUMBER REFERENCE_1 REFERENCE_2 PA_CC_PROCESSED_CO DE CREDIT_CARD_TRX_ID AWARD_ID VENDOR_ITEM_NUM VARCHAR2( Projects 30) VARCHAR2( Projects 30) VARCHAR2( N/A 1) NUMBER(1 5) NUMBER(1 5) Credit card transaction ID if the line is a credit card charge.5) PRICE_CORRECTION_FL AG ORG_ID RECEIPT_NUMBER VARCHAR2( N/A 1) NUMBER(1 5) Organization identifier VARCHAR2( Validated against 30) RCV_SHIPMENT_HEADERS. VARCHAR2( N/A 50) TAXABLE_FLAG PRICE_CORRECT_INV_N UM . VARCHAR(2 Optional. Grants requirement to store award.VENDOR_PRODUCT_NUM VARCHAR2( Value of Y indicates that the line 1) is taxable. Validated against 5) PO_LINES_ ALL. Used in combination with PERIOD_TYPE. Number of periods to generate deferred expenses.UNITS _OF_MEASURE NUMBER Invoice line subject to the price correction. UNIT_OF_MEAS_LOOKU P_CODE PRICE_CORRECT_INV_LI NE_NUM ASSET_BOOK_TYPE_CO DE ASSET_CATEGORY_ID VARCHAR2( Asset Book Defaults to the 15) distributions candidate for transfer to Oracle Assets. SERIAL_NUMBER MANUFACTURER MODEL_NUMBER WARRANTY_NUMBER DEFERRED_ACCTG_FLA G DEF_ACCTG_START_DA TE DEF_ACCTG_END_DATE DEF_ACCTG_NUMBER_O F_PERIODS DEF_ACCTG_PERIOD_TY PE VARCHAR2( Period type used in combination 15) with NUMBER_OF_PERIODS to generate deferred expenses. Alternative to END_DATE. 35) VARCHAR2( Name of the manufacturer. 30) VARCHAR2( Model information. NUMBER(1 5) Asset Category Defaults to the distributions candidate for transfer to Oracle Assets. Validated against XLA_LOOKUPS with lookup type XLA_DEFERRED_PERIOD_TYPE. 40) VARCHAR2( Warranty number. . Used for XML Invoices. The end date of the deferred expense period. 15) VARCHAR2( Flag that indicates whether to 1) generate deferred accounting for this line. DATE DATE NUMBER The start date of the deferred expense period.EXTERNAL_DOC_LINE_R EF VARCHAR2( Internal document reference 240) number from Accounts Receivables system. VARCHAR2( Serial number for item. Validated against MTL_UNITS_OF_MEASURE. VARCHAR2( Unit of Measure for quantity 25) invoiced. VARCHAR2( Primary key information that will 150) uniquely identify a record in other products view. NUMBER(1 5) Application identifier. REFERENCE_KEY2 . VARCHAR2( The employee number of the 30) employee who requested goods or services on the invoice line. If you use the Invoice Approval Workflow then you can define rules that use the requester ID to generate a hierarchical list of approvers for the line.PERSON_ID VARCHAR2( The first name of the employee 150) who requested goods or services on the invoice line. Validated against PER_ALL_PEOPLE_F. Valid 15) values from active HR employees. This value is used to derive the requester ID. This value is used to derive the requester ID.REQUESTER_ID VARCHAR2( Requester identifier. If you use the Invoice Approval Workflow then you can define rules that use the requester ID to generate a hierarchical list of approvers for the line. REQUESTER_FIRST_NAM E REQUESTER_LAST_NAM E REQUESTER_EMPLOYEE _NUM APPLICATION_ID PRODUCT_TABLE REFERENCE_KEY1 VARCHAR2( Product source table name. 30) VARCHAR2( Primary key information that will 150) uniquely identify a record in other products view. VARCHAR2( The last name of the employee 150) who requested goods or services on the invoice line. If you use the Invoice Approval Workflow then you can define rules that use the requester ID to generate a hierarchical list of approvers for the line. This value is used to derive the requester ID. Note that this is necessary to support the Account Method VAT feature. labor costs. VARCHAR2( Primary key information that will 150) uniquely identify a record in other products view. direct material costs. REFERENCE_KEY4 REFERENCE_KEY5 PURCHASING_CATEGOR Y PURCHASING_CATEGOR Y_ID COST_FACTOR_ID COST_FACTOR_NAME VARCHAR2( Cost component class name. production or conversion costs and so on. labor costs. CONTROL_AMOUNT ASSESSABLE_VALUE DEFAULT_DIST_CCID NUMBER NUMBER(1 5) . Used to identify the individual buckets or component costs that make up the total cost of an item for example. NUMBER Optional. freight costs. production or conversion costs and so on. freight costs.REFERENCE_KEY3 VARCHAR2( Primary key information that will 150) uniquely identify a record in other products view. 80) Used to identify the individual buckets or component costs that make up the total cost of an item for example. VARCHAR2( Primary key information that will 150) uniquely identify a record in other products view. NUMBER(1 5) NUMBER(1 5) Item category unique ID Identifier of the cost component class. user-enterable value to ensure that the calculated tax will be the same as on the physical document. Already addressed by lines project Tax Driver: Code combination identifier of the GL account associated with the transaction line. direct material costs. User enterable amount to be used as taxable basis. VARCHAR2( Item category concatenated 2000) segments. 240) VARCHAR2( Tax Driver: Transactoins 240) category assigned by user. 30) NUMBER(1 5)) Internal identifier for tax rate effective on the invoice date. The actual use will be stored at the distribution level. This value will default from Inventory Item attributes. SHIP_TO_LOCATION_ID PRODUCT_TYPE VARCHAR2( Tax Driver: Type of product. PRODUCT_CATEGORY PRODUCT_FISC_CLASSI FICATION USER_DEFINED_FISC_CL ASS TRX_BUSINESS_CATEG ORY TAX_REGIME_CODE TAX TAX_JURISDICTION_COD E TAX_STATUS_CODE TAX_RATE_ID TAX_RATE_CODE VARCHAR2( Tax rate name associated with 150) tax rate identifier. 240) Possible values are: Goods. NUMBER(1 5) Tax Driver: Ship to location ID. TAX_RATE_ID is unique while the TAX_RATE_CODE may have different tax rates based on date ranges. Service. VARCHAR2( A classification of a charge 30) imposed by a government through a fiscal or tax authority. 240) VARCHAR2( Tax Driver: Product fiscal 240) classification. VARCHAR2( Internal ID of the Tax 30) Jurisdiction.PRIMARY_INTENDED_US E VARCHAR2( Tax Driver: The purpose for 30) which the product may be used. Otherwise. value will be entered by user. NUMBER The rate specified for a tax TAX_RATE . VARCHAR2( Tax Driver: Product category. Value entered by user only if line is not PO matched. VARCHAR2( Tax Regime Code: The set of tax 30) rules that determines the treatment of one or more taxes administered by a tax authority. VARCHAR2( Tax status code. VARCHAR2( Tax Driver: Fiscal Classification. NUMBER Source document application identifier.INVOICE_ID or the line will not be imported. This column is populated by the AP_INVOICE_LINES_INTERFACE_S sequence. 30) VARCHAR2( Source document event class 30) code. 30) INVOICE_ID Enter the INVOICE_ID of the corresponding invoice in the AP_INVOICES_INTERFACE table. Variable Description Validation: This must match a value in AP_INVOICES_INTERFACE. Identifier of the lowest level for which tax is calculated. VARCHAR2( Source document entity code. You can enter a unique number for each invoice line of an invoice. INCL_IN_TAXABLE_LINE_ FLAG SOURCE_APPLICATION_I D SOURCE_ENTITY_CODE SOURCE_EVENT_CLASS _CODE SOURCE_TRX_ID SOURCE_LINE_ID SOURCE_TRX_LEVEL_TY PE TAX_CLASSIFICATION_C ODE VARCHAR2( Flag to indicate if the amount in 1) the tax line is included or not in the taxable line. . Destinatio None n: INVOICE_LINE_ID This value is not required in this table.INVOICE_ID. If this value does not match a value in AP_INVOICES_INTERFACE. NUMBER NUMBER Source document transaction identifier.status in effect for a period of time. This value is used only to assign lines in this table to invoices in the AP_INVOICES_INTERFACE table. VARCHAR2( Source document transaction 30) level type. this row (invoice line record) will not be imported and it will not appear on the Open Interface Rejections Report. VARCHAR2( Tax classification code. if you want to prorate tax across two Item lines. For example. enter an identical line group number value for each Item line to which you want to prorate the charge. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. The import program automatically generates the n: values for AP_INVOICE_DISTRIBUTIONS_ALL. Variable Description Validation: This value should be a number.LINE_ n: GROUP_NUMBER .Variable Description Validation: The value must be a number. These lookup codes are stored in the AP_LOOKUP_CODES table. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Destinatio None. Destinatio None n: LINE_NUMBER You can enter a unique number to identify the line. enter the same line group number for the two Item lines and the Tax line. Variable Description Validation: This value must be a positive whole number. TAX. Variable Description Validation: The code you enter must be ITEM.LINE_TYPE_LOOKUP_CODE n: LINE_GROUP_NUMBER If you want to prorate a charge to a group of lines. or FREIGHT. DISTRIBUTION_LINE_NUMBER LINE_TYPE_LOOKUP_CODE Enter the lookup code for the type of invoice distribution that you want Payables Open Interface Import to create from this record. AWT is not an acceptable value here. MISCELLANEOUS. then Payables uses the system date at time of import. you must enter a GL Date in a period that is within the latest open encumbrance year. Important: If you are using encumbrance accounting. If the GL Date Basis option is set to Goods Received/System Date. The date must be in an open or future period. During import. then Payables uses the Invoice Date. then Payables Open Interface Import will reject the invoice. then Payables uses the Goods Received Date. Note: The following occurs if the system searches at the GL Date Basis level: If the GL Date Basis option is set to Goods Received/Invoice Date.AMOUNT The invoice distribution amount. If not. then Payables uses the Goods Received Date. If you are matching to a purchase order. header of the invoice record. GL Date parameter from import submission. (See also: Budgetary Control In Payables). then Payables uses the Invoice Date. Variable Description Validation: Must be in valid date format. Payables looks for a GL Date value to assign to the invoice distribution.AMOUNT n: ACCOUNTING_DATE The GL Date for the invoice distributions. Note: Note the system searches at the GL Date Basis level and the GL Date Basis option is set to Invoice Received Date. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. GL Date Basis Payables option. and it searches the following sources in the following order: line of the invoice record. Variable Description Validation: If the total amount of all the invoice lines does not equal the amount of the invoice header that has the same INVOICE_ID. if it is populated. you can account for the invoice but you cannot pay it. and if the GL Date Basis option is set to Goods Received Date. . If the GL Date of an invoice is in a future period in Payables. then Payables uses the system date at time of import. the AMOUNT = QUANTITY_INVOICED x UNIT PRICE. if it is populated. If it is not. Payables assigns a value from the first source it finds. The date must be in an open accounting period. If you do not enter a value. then Payables will not prorate the cost and will create only one distribution. The system assigns the expense account of the Item line to the new invoice distribution. Miscellaneous. and miscellaneous for Miscellaneous type lines. .DESCRIPTION. or Freight). freight for Freight type lines. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Payables creates a distribution line for each line you prorate the charge to. If this column is set to N. enter Y. Destinatio None n: FINAL_MATCH_FLAG If you are certain that this is a final match against the purchase order. then during import the system uses the item description on the purchase order line to populate AP_INVOICE_DISTRIBUTIONS_ALL.Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Since you cannot final close purchase orders when you are matching to receipts. you cannot update the Final Match check box in the Distributions window. If no line group number is specified. Payables will prorate the charge to all Item lines. n: DESCRIPTION PRORATE_ACROSS_FLAG If you set this column to Y and this is a non-Item type line (Tax. Payables prorates tax for Tax type lines. ACCOUNTING_DATE n: DESCRIPTION Enter a description that you want to assign to the invoice distribution created from this record. and you match to a purchase order. Variable Description Validation: Line type is not Item. if the invoice is matched to a receipt then import ignores any value in this column. then Payables will prorate the charge to all Item type lines with the same LINE_GROUP_NUMBER as this line. Once you validate a final matched invoice distribution. and the purchase order cannot be final matched or inactive. then during Payables Open Interface Import the system uses purchase order information to create distributions and populate various columns in the AP_INVOICE_DISTRIBUTIONS_ALL table.FINAL_ n: MATCH_FLAG PO_HEADER_ID If you enter the record in the Quick Invoices window.PO_HEADER_ID. then you must provide a value for this column by entering a value in the PO Number field. and you must specify the supplier.VENDOR_ID. you must enter the PO_NUMBER or the PO_HEADER_ID. Variable Description Validation: This must be a valid value in PO_HEADERS. To match to a purchase order you can enter either the PO_HEADER_ID or the PO_NUMBER. If you are matching to a purchase order. Variable Description Validation: This must be a valid purchase order number for the same supplier. the PO_NUMBER value can be used to derive AP_INVOICE_DISTRIBUTIONS_ALL. If you do not specify a supplier in the AP_INVOICE_LINES_INTERFACE table.Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. If you specified a purchase order in AP_INVOICES_INTERFACE.VENDOR_SITE_ID. Destinatio None n: PO_NUMBER Enter a purchase order number if you are matching to a purchase order. If you match the invoice to a purchase order by entering a value here. it must match this purchase order number. and if you do not specify the supplier site. Internal identifier for the purchase order number. It must be for the same supplier and cannot be final matched. If you enter supplier information in another column and enter a value for PO_NUMBER. then the system will use the supplier on the purchase order and ignore any other supplier information you have entered. The match option for the purchase order shipment . the PO_NUMBER value is used to derive AP_INVOICE_DISTRIBUTIONS_ALL. This value is used to enter n: AP_INVOICES_ALL. If you do this. Alternatively. Variable Description Validation: This must be a valid value for PO_LINES. Destinatio None n: PO_LINE_NUMBER If you want to match to a purchase order line.PO_LINE_ID. For example. Variable Description Validation: This must be a valid value in PO_LINE_LOCATIONS. . PO_LINE_ID Internal identifier for the purchase order line number. the value you enter must exactly match the ITEM_ID or ITEM_DESCRIPTION of exactly one purchase order line for the PO_NUMBER. you can match to a line by entering the ITEM_DESCRIPTION "books" for an invoice that has exactly one line with an ITEM_DESCRIPTION of "books". If you are matching to a purchase order line you can enter either the PO_LINE_ID or the PO_LINE_NUMBER. you can identify a purchase order line number by entering only an ITEM_ID or an ITEM_DESCRIPTION.LINE_LOCATION_ID for the purchase order.PO_LINE_NUM. Destinatio None. Variable Description Validation: This must be a valid value for PO_LINES.PO_HEADER_ID. PO shipment cannot be finally closed. Destinatio None n: PO_LINE_LOCATION_ID Internal identifier for purchase order shipment.must be set to purchase order. enter a value for PO_LINE_NUMBER or PO_LINE_ID. you enter a SHIP_TO_LOCATION_CODE of "Taipei" for a purchase order with exactly one shipment with the location value of "Taipei".SHIPMENT_NUM. If you are matching to a distribution. Variable Description Validation: Value must match a distribution number on the purchase order and must be a valid value for . Variable Description Validation: This must be a valid value for PO_LINE_LOCATIONS. enter a value for either PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID.Destinatio None n: PO_SHIPMENT_NUM Number of the purchase order shipment. Alternatively. For example. PO shipment cannot be finally closed. If you are matching to a purchase order shipment.PO_DISTRIBUTION_ ID Destinatio None n: PO_DISTRIBUTION_NUM Purchase order distribution number. If you are matching to a purchase order distribution you can enter a value for PO_DISTRIBUTION_ID or PO_DISTRIBUTION_NUM. you can enter a value for SHIP_TO_LOCATION_CODE if exactly one shipment on the purchase order has the SHIP_TO_LOCATION_CODE you specify. Destinatio None n: PO_DISTRIBUTION_ID Internal identifier for purchase order distribution number. you must enter a value for PO_DISTRIBUTION_NUM or PO_DISTRIBUTION_ID. Variable Description Validation: This must be a valid value in INVOICE_DISTRIBUTIONS. If you want to match to the line with monitors and you don't know the purchase order number. and the system will attempt to match the invoice to a purchase order line.INVENTORY_ITEM_ID for exactly one line. you can enter an inventory item number.PO_DISTRIBUTIONS. enter the proper INVENTORY_ITEM_ID for the monitors. For example.PO_DISTRIBUTION_NUM. The system will match to the correct purchase order line for the monitors during import. and the system will match to the correct purchase order line. you can enter the exact description for the books. Destinatio None n: ITEM_DESCRIPTION Exact description of the item on the purchase order. Used during purchase order line matching. Variable Description Validation: The description must match PO_LINES.ITEM_DESCRIPTION. that includes a single line for monitors. Destinatio None n: QUANTITY_INVOICED . Used during purchase order matching. a supplier has one purchase order for PCs. and the system will attempt to match the invoice to a purchase order line. Destinatio None n: INVENTORY_ITEM_ID Inventory item identifier on the purchase order. If you have limited purchase order information. Variable Description Validation: This value must match the purchase order MTL_SYSTEM_ITEMS. if a purchase order has one line for books and one line for software. For example. If you have limited purchase order information. but you don't know the line number. you can enter a description in the column. . If you enter a value for UNIT_PRICE and do not enter a value for QUANTITY_INVOICED. Variable Description Validation: This must be an existing. If you enter a value for UNIT_PRICE and do not enter a value for QUANTITY_INVOICED. active value for PO_LINE_LOCATIONS. enter 5. and a negative number if AMOUNT is negative. the system will derive a value for QUANTITY_INVOICED during Payables Open Interface Import (QUANTITY_INVOICED = AMOUNT / UNIT PRICE). Used for purchase order matching. If the Invoice Match option on the purchase order shipment is Receipt. Used for purchase order matching. Import then fills each unbilled receipt quantity up to the amount of the invoice billed quantity.Number of units invoiced. For example.SHIP_TO_LOCATION_ID Destinatio None n: UNIT_PRICE Unit price of the distribution line item(s). Import reviews all receipts that have unbilled quantities for the purchase order shipment. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. you enter a SHIP_TO_LOCATION_CODE of "Taipei" for a purchase order with exactly one shipment with the value "Taipei". Variable Description Validation: This value must be a positive number if AMOUNT for this line is positive. you can enter a value for SHIP_TO_LOCATION_CODE if exactly one shipment on the purchase order has the SHIP_TO_LOCATION_CODE you specify. If the invoice quantity exceeds all available unbilled receipt quantities for the purchase order shipment. For example if there are 5 chairs on the invoice. Import then matches the billed quantity on the invoice to these receipts starting with the oldest receipt that has an unbilled quantity. import overbills the newest unbilled quantity by the remaining amount.QUANTITY_INVOICED n: SHIP_TO_LOCATION_CODE If you want to match to a purchase order shipment and have not entered a value for either PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID. the system will derive a value for QUANTITY_INVOICED during Payables Open Interface Import (QUANTITY_INVOICED = AMOUNT / UNIT PRICE). DISTRIBUTION SET_NAME.Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL.DISTRIBUTION_SET_ ID Destinatio None n: DISTRIBUTION_SET_NAME Name of the Distribution Set. You define Distribution Sets in the Distribution Sets window. then during import Payables automatically creates distributions for you based on the Distribution Set. Variable Description Validation: This must be an existing. if you are prorating. if you are prorating. Payables automatically creates distributions for you based on the Distribution Set. If you enter a value for DISTRIBUTION_SET_NAME or DISTRIBUTION_SET_ID. or if you provide an account. If you are matching to a purchase order and you enter a value in this column. Payables Open Interface Import will reject the invoice. then during Payables Open Interface Import. Do not enter a value here if you are matching this line to a purchase order. active value for AP_DISTRIBUTION_SETS. Variable Description Validation: This must be an existing. or if you enter an account. you do not need to enter the corresponding value for DISTRIBUTION_SET_ID. If you enter a value here. active value for AP_DISTRIBUTION_SETS. Destinatio None n: DIST_CODE_CONCATENATED . If you enter a Distribution Set name. Do not enter a value in this column if you are matching to a purchase order.UNIT_ n: PRICE DISTRIBUTION_SET_ID Internal identifier for the Distribution Set. the Quick Invoices window will automatically build the account for you. and must match a value for GL_CODE_COMBINATIONS. This value may be used to enter a value for n: AP_INVOICE_DISTRIBUTIONS_ALL.DIST_ CODE_COMBINATION_ID DIST_CODE_COMBINATION_ID Internal identifier for GL account to which the distribution amount will be charged.The GL account to which the distribution amount will be charged. Destinatio AP_INVOICES_ALL. If you enter records in any way other than the Quick Invoices window. see: Account Overlay in Payables Open Interface Import. see: Account Overlay in Payables Open Interface Import. Variable Description Validation: This must be a valid. active value in AP_AWT_GROUPS. If you enter Projects information in the Quick Invoices.CODE_ COMBINATION_ID.DIST_CODE_ COMBINATION_ID n: AWT_GROUP_ID Internal identifier associated with the automatic withholding tax group name. Variable Description Validation: The account code combination must be valid and in the exact flexfield structure you have defined for your Set of Books. you must provide this value. Destinatio None. Variable Description Validation: The account code combination must be valid and in the exact flexfield structure you have defined for your Set of Books.GROUP_ID . you do not need to enter a value here if you enter a value for AWT_GROUP_NAME. If you want to assign a withholding tax group to the line. For information on how Payables Open Interface Import builds an account based on the value you enter here. For information on how Payables Open Interface Import builds an account based on the value you enter here. .Destinatio None n: AWT_GROUP_NAME Automatic withholding tax group name.AWT_GROUP_NAME. When you enter a withholding tax group for a line. then all the withholding taxes in the group are applied to the line. it uses the system date at the time you submit Payables Open Interface Import. If you do not enter a value here. it does not use this date as the last update date for the invoice.LAST_ n: UPDATED_BY LAST_UPDATE_DATE Enter the last update date for this record (usually the same date as CREATION_DATE).NAME Destinatio None n: LAST_UPDATED_BY Enter the ID of the person who last updated this record (usually the same value as CREATED_BY). active value in AP_AWT_GROUPS. When the import program creates an invoice from a record in this table. Variable Description Validation: This must be a valid. then during Payables Open Interface Import the system will use the value you entered for AP_INVOICES_INTERFACE. If you do not enter a value for this column. Payables uses this date for reference and audit purposes only. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. then during Payables Open Interface Import the system will use the userid of the person who submits Payables Open Interface Import. then the system uses the supplier site value if there is one. You define automatic withholding tax group names in the Withholding Tax Groups window. If you did not enter a value. the system uses it to populate AP_INVOICE_DISTRIBUTIONS_ALL.AP_LAST_ UPDATE_LOGIN. If you do not enter a value.Variable Description Validation: Must be in valid date format. Payables Open Interface Import transfers this userid to the AP_INVOICE_DISTRIBUTIONS_ALL table during import so that the creator of the record becomes the invoice and scheduled payment creator. When Payables Open Interface Import creates an invoice from this record. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Destinatio None n: LAST_UPDATE_LOGIN The last update date for this record.AP_LAST_UPDATE_LO n: GIN CREATED_BY Enter the userid of the person or organization who loads this record into the table. If you enter a value in this column. Variable Description . Usually the same date as the CREATION_DATE. then during import the system will use the userid of the person who submits Payables Open Interface Import. the system will use the system date. it does not use this date as the creation date for the invoice distributions. then during Payables Open Interface Import. it uses the system date at the time you submit Payables Open Interface Import. If you do not enter a value.CREATED_ n: BY CREATION_DATE Enter the date on which you load this record into the table. Payables uses this date for reference and audit purposes. If a line is purchase order matched and the Transfer PO Descriptive Flexfield Information Payables option is enabled.Validation: Must be in valid date format. then the purchase order flexfield values are ignored during import. If you are using a Distribution Set that has a descriptive flexfield. then import uses the purchase order values for any corresponding open interface attribute columns that are null. value sets) must match the structure of the Descriptive Flexfield segments you have defined for your invoice distributions or you will experience validation problems when you try to access the information in the invoice windows.ATTRIBUTE_CATEG n: ORY ATTRIBUTE [1-15] Enter Descriptive Flexfield information that you want to import for an invoice distribution. The structure of the information you enter in these columns (datatypes. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL.CREATION_DA n: TE ATTRIBUTE_CATEGORY Enter the Descriptive Flexfield category for the Descriptive Flexfield information you want to import for an invoice distribution. if you enter data for any open interface attribute then that value will be used on the invoice instead of the purchase order value. If the Transfer PO Descriptive Flexfield Information Payables option is disabled.ATTRIBUTE [1n: 15] GLOBAL_ATTRIBUTE_CATEGORY . Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. any data you enter here will overwrite the descriptive flexfield on the Distribution Set. However. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Variable Description Validation: This value must match a valid value in PO_RELEASES. The structure of the information you enter in these columns (datatypes. Destinatio None n: RELEASE_NUM Release number of a blanket purchase order. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Used during purchase order matching.GLOBAL_ n: ATTRIBUTE_CATEGORY GLOBAL ATTRIBUTE [1-20] Enter descriptive flexfield information that you want to import for an invoice. you must enter appropriate values in this flexfield or the invoice will be rejected by import.Enter the Descriptive Flexfield category for the descriptive flexfield information you want to import.GLOBAL_ ATTRIBUTE[1-20] n: PO_RELEASE_ID Internal identifier for a purchase order release number. For more information. If you want to match to a blanket purchase order you must supply either the RELEASE_NUM or the PO_RELEASE_ID. value sets) must match the structure of the descriptive flexfield segments you have defined for your invoices or you will experience validation problems when you try to access the information in the invoice windows. . You can also optionally provide a line number. If you want to match to a blanket purchase order you must supply either the RELEASE_NUM or the PO_RELEASE_ID. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. see your localization user's guide. Variable Description Validation: If you are using a localization.PO_RELEASE_ID. and provide a shipment number. See: Account Overlay in Payables Open Interface Import. Payables will override the account segment with this value during import. enter a value here. Payables will override the cost center with this value during import. Variable Description Validation: The new account code must be valid. See: Account Overlay in Payables Open Interface Import. See: Account Overlay in Payables Open Interface Import. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. enter a value here. Variable Description Validation: The account code must be valid. Destinatio None n: ACCOUNT_SEGMENT If you want to override the account segment in the account for this line. Payables will override the balancing segment with this value during import.RELEASE_NUM.CODE_ n: COMBINATION_ID BALANCING_SEGMENT If you want to override the balancing segment in the account. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL.Variable Description Validation: This value must match a valid value in PO_RELEASES. enter a value here.CODE_ n: COMBINATION_ID COST_CENTER_SEGMENT If you want to override the cost center in the account. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Variable Description Validation: The account code must be valid.CODE_ n: COMBINATION_ID Projects Columns . • • • • • • PROJECT_ID TASK_ID EXPENDITURE_TYPE EXPENDITURE_ITEM_DATE EXPENDITURE_ORGANIZATION_ID PA_ADDITION_FLAG In addition. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Open Interface Import imports any USSGL information that you load into the interface tables and assigns the information to the invoices it creates.Enter project information from Oracle Projects in the following columns if you want to associate the invoice distribution (created from this record) with a project in Oracle Projects. If Projects is installed and you provide information for the projects columns. then during import Payables automatically populates the Projects related columns in AP_INVOICES and AP_INVOICE_DISTRIBUTIONS_ALL.USSGL_ n: TRANSACTION_CODE . If the invoice is matched to a purchase order and the purchase order has project related information. Oracle Projects uses the following columns to transfer invoice data: • • • • • • PA_QUANTITY PA_CC_AR_INVOICE_ID PA_CC_AR_INVOICE_LINE_NUM REFERENCE_1 REFERENCE_1 PA_CC_PROCESSED_CODE Variable Description Validation: The information provided in these columns is validated against Oracle Projects. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. then Projects will build the expense account based on this information.[Projects Columns] n: USSGL_TRANSACTION_CODE Enter the default transaction code you want to assign to an invoice. if you do not use a Distribution Set to create invoice distributions. then this value always defaults from the purchase order (even if that value is null and the supplier now has a value).STAT_AMOUNT Statistical quantity based on the unit of measure. Payables uses the default income tax type from the Distribution Set as the default value. Payables uses the supplier's income tax type as the default value. if your unit of measure is barrels. You can enter this field regardless of whether the supplier is defined as a 1099 supplier. Destinatio AP_INVOICES_DISTRIBUTIONS_ALL. Variable Description Validation: You must also enter a valid value for PO_UNIT_OF_MEASURE. Payables uses this information when you submit the 1099 Payments Report and the 1099 Form Reports. you can enter the number of barrels here. Oracle Payables User Guide. . for a United States 1099 reportable supplier. For unmatched invoices. Enter a 1099 Miscellaneous Tax Type. except MISC9. Oracle Payables User Guide. You can update this field of the imported invoice in the Distributions window even after you have accounted for a distribution. See:Entering Invoices for Suppliers Subject to Income Tax Reporting Requirements.STAT_ AMOUNT n: TYPE_1099 Income tax type. See also: 1099 Reporting Overview. MISC11 and MISC12). See also: Invoice Distribution Statistics in Oracle General Ledger. You can use the Update Income Tax Details Utility to make adjustments to many distributions at once. If you use a Distribution Set to create invoice distributions. and the supplier for this record must be defined as federally reportable. For example. See: Update Income Tax Details Utility and Report. You define a supplier as federally reportable by enabling the Federal option in the Suppliers window. Oracle Payables User Guide If you leave this value null and match to a purchase order. Variable Description Validation: The value must be a valid and active value in the AP_INCOME_TAX_TYPES table (MISC types 1-14. You record a price correction by entering a Standard or Credit invoice. If you do not enter a value.ASSETS_ TRACKING_FLAG n: PRICE_CORRECTION_FLAG Use a price correction when a supplier sends an invoice for a change in unit price for an invoice that you have matched to a purchase order. and entering the base-matched invoice in the PRICE_CORRECT_INV_NUM column. Variable Description Validation: The account must be set up as an existing asset category. and it must be either an asset clearing account or a construction-in-progress (CIP) clearing account. Variable Description Validation: You must also enter a value for INCOME_TAX_TYPE.TYPE_1099 n: INCOME_TAX_REGION If the supplier is a 1099 supplier.Destinatio AP_INVOICE_DISTRIBUTIONS_ALL.INCOME_TAX_REGI n: ON ASSETS_TRACKING_FLAG Enter Y if the invoice distribution should be imported into Oracle Assets using the Create Mass Additions for Assets program. Payables also updates the amount billed on the originally matched purchase order distributions. then during import the system uses the income tax region of the supplier site. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Destinatio AP_INVOICES_DISTRIBUTIONS. If you do not enter a value. enter the supplier's reporting region. setting this flag to Y. then Payables will automatically set this value to Y during import. Payables records and updates the invoiced unit price of previously matched purchase order shipment or distributions without adjusting the quantity billed so you can track price variances. and the line has an Asset type account entered for it. and you have enabled the Use Pay Site Tax Region Payables option. If you do not enter a value and you have instead entered a value for the Income Tax Region Payables option. . then during import the system will use that value as the default. Descriptio n Variable Validation: None Destinatio None n: ORG_ID Organization identifier. Variable Description Validation: A purchase order and receipt for the same supplier.See also: Price Corrections. then you can specify the receipt line you are matching to. supplier site. supplier site. and currency as the invoice you are entering must be approved and open. Also. and currency as the invoice you are entering must be approved and open. Descriptio n Variable Validation: None Destinatio None n: RECEIPT_NUMBER If you are matching to a purchase order receipt. then enter the receipt number. Also. the Invoice Match option for the purchase order shipment you are matching to is set to Receipt. n: RCV_TRANSACTION_ID RECEIPT_LINE_NUMBER If you are matching to a purchase order receipt. Destinatio This value is used to enter: AP_INVOICE_DISTRIBUTIONS_ALL. Oracle Payables User Guide. Variable Description Validation: A purchase order and receipt for the same supplier. the Invoice Match option for the purchase order shipment you are matching to is set to . Destinatio None n: PACKING_SLIP This column is not currently used. Descriptio n Variable Validation: None Destinatio None n: RCV_TRANSACTION_ID This value specifies a receipt record for matching. Variable Description Validation: The value must match the value specified in PO_SHIPMENTS. This value is used to match Oracle e-Commerce Gateway invoices to receipts. When you match to a purchase order or receipt in the Quick Invoices window. This must be a valid line number for the receipt. then the system populates this field based on the value of the purchase order shipment. RCV_TRANSACTION_ID Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. Destinatio None n: MATCH_OPTION Indicates if a match is to a purchase order or receipt. existing value for RCV_TRANSACTIONS.MATCH_OPTION. Variable Description Validation: This value must be a valid. RCV_TRANSACTION_ID n: PA_CC_AR_INVOICE_ID Identifier of the corresponding receivable intercompany invoice in Oracle Receivables .Receipt. 2 These columns references records in another application Descriptio n Variable Validation: None Destinatio None n: PA_CC_PROCESSED_CODE This column indicates the processing status of this invoice line by Oracle Projects in the Receiver Operating Unit. Descriptio n Variable Validation: None Destinatio None n: TAX_CODE_ID .Variable Descriptio n Validation: None Destinatio None n: PA_CC_AR_INVOICE_LINE_NUM Line number of the corresponding receivable intercompany invoice in Oracle Receivables Descriptio n Variable Validation: None Destinatio None n: REFERENCE_1 . Used during purchase order matching. Destinatio None n: . If you have limited purchase order information.TAX_ID. Destinatio AP_INVOICE_DISTRIBUTIONS_ALL. You can enter a value for either the TAX_CODE or TAX_CODE_ID. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL.CREDIT_ n: CARD_TRX_ID AWARD_ID This value is used only if you use Oracle Grants Management. you can enter a supplier item number in the column and the system will attempt to match the invoice to a purchase order line. Variable Description Validation: This value must match a valid value in PO_LINES_ALL.VENDOR_PRODUCT_NUM for exactly one line. Variable Description Validation: None Destinatio AP_INVOICE_DISTRIBUTIONS_ALL.TAX_CODE_ID n: CREDIT_CARD_TRX_ID This column is populated when credit card transactions for expense reports entered in Oracle Internet Expenses are imported to Payables. Further validations are the same as those for TAX_CODE. n: AWARD_SET_ID VENDOR_ITEM_NUM Supplier item number on the purchase order. Variable Description Validation: This must be a valid value for AP_TAX_CODES_ALL.Internal identifier for the tax code. Oracle Payables User Guide. Descriptio n Variable Validation: None Destinatio None n: SERIAL_NUMBER This column is the serial number for an item. Variable Description Validation: This value must be a valid purchase order matched invoice with a type of either Standard or Mixed. For more information. Variable Descriptio . Import uses this value for invoices from XML Gateway Descriptio n Variable Validation: None Destinatio None n: PRICE_CORRECT_INV_NUM If you have set the PRICE_CORRECTION_FLAG to Y to indicate that this is a price correction. You must provide sufficient purchase order information for the system to identify the purchase order amount that you want to update. Destinatio We use this to derive n: AP_INVOICE_DISTRIBUTIONS.TAXABLE_FLAG Y indicates that the line is taxable. see: Price Corrections. then you must enter the number of the base-matched invoice here.PRICE_CORRECT_INV_ID EXTERNAL_DOC_LINE_REF This column is an internal document reference number from Accounts Receivables system. Used for XML invoices. n Validation: None Destinatio None n: MANUFACTURER This column is the name of the manufacturer. Descriptio n Variable Validation: None Destinatio None n: MODEL_NUMBER This column is the model information. Descriptio n Variable Validation: None Destinatio None n: WARRANTY_NUMBER This column is a warranty number. Descriptio n Variable Validation: None Destinatio None n: DEFERRED_ACCTG_FLAG This column is a flag that indicates whether to generate deferred accounting for this line. Variable Descriptio n Validation: None Destinatio None n: DEF_ACCTG_START_DATE This column is the start date of the deferred expense period. Descriptio n Variable Validation: None Destinatio None n: DEF_ACCTG_END_DATE This column is the end date of the deferred expense period. Descriptio n Variable Validation: None Destinatio None n: DEF_ACCTG_NUMBER_OF_PERIODS This column is the number of periods to generate deferred expenses. Used in combination with PERIOD_TYPE. Alternative to END_DATE Descriptio n Variable Validation: None Destinatio None n: DEF_ACCTG_PERIOD_TYPE This column is the period type used in combination with NUMBER_OF_PERIODS to generate deferred expenses. Variable Description Validation: XLA_LOOKUPS with lookup type XLA_DEFERRED_PERIOD_TYPE Destinatio None n: UNIT_OF_MEAS_LOOKUP_CODE This column is the Unit of Measure for quantity invoiced. Variable Description Validation: MTL_UNITS_OF_MEASURE.UNIT_OF_MEASU RE Destinatio None n: PRICE_CORRECT_INV_LINE_NUM This column is the invoice line subject to the price correction. Descriptio n Variable Validation: None Destinatio None n: ASSET_BOOK_TYPE_CODE This column is the Asset Book Defaults to the distributions candidate for transfer to Oracle Assets Descriptio n Variable Validation: None Destinatio None n: ASSET_CATEGORY_ID This column is the Asset Category Defaults to the distributions candidate for transfer to Oracle Assets If you use Invoice Approval Workflow then you can define rules that use therequester ID to generate a hierarchical list of approvers for the line Descriptio n Variable Validation: None Destinatio None n: REQUESTER_LAST_NAME This column is the last name of the employee who requested goods or services on the invoice line.PERSON_I D Destinatio None n: REQUESTER_FIRST_NAME This column is the first name of the employee who requested goods or services on the invoice line. If you use Invoice Approval Workflow then you can define rules that use therequester ID to generate a hierarchical list of approvers for the line Descriptio n Variable Validation: None Destinatio None . This value is used to derive the requester ID. Variable Description Validation: PER_ALL_PEOPLE_F. Valid values from active HR employees. This value is used to derive the requester ID.Variable Descriptio n Validation: None Destinatio None n: REQUESTER_ID This column is the Requester identifier. This value is used to derive the requester ID. Descriptio n Variable Validation: None Destinatio None n: REFERENCE_KEY1 .n: REQUESTER_EMPLOYEE_NUM This column is the employee number of the employee who requested goods or services on the invoice line.5 These columns are primary keys that will uniquely identify a record in other products view . If you use Invoice Approval Workflow then you can define rules that use therequester ID to generate a hierarchical list of approvers for the line Descriptio n Variable Validation: None Destinatio None n: APPLICATION_ID This column is the Application Identifier Descriptio n Variable Validation: None Destinatio None n: PRODUCT_TABLE This column is the Product source table name. Descriptio n Variable Validation: None Destinatio None n: COST_FACTOR_NAME . Cost Component Classes are used to identify the individual buckets or component costs that make up the total cost of an item. production or conversion costs and so on. freight costs.Variable Descriptio n Validation: None Destinatio None n: PURCHASING_CATEGORY This column is the item category concatenated segments Descriptio n Variable Validation: None Destinatio None n: PURCHASING_CATEGORY_ID This column is the item category unique identifier Descriptio n Variable Validation: None Destinatio None n: COST_FACTOR_ID This column is the identifier of the cost component class. for example. direct material costs. labor costs. user-enterable value to ensure that the calculated tax will be the same as on the physical document. labor costs. freight costs. for example. direct material costs. It is a code combination identifier of the GL account associated with the transaction line. Descriptio n Variable Validation: None Destinatio None n: ASSESSABLE_VALUE This column is the user-enterable amount to be used as taxable basis Descriptio n Variable Validation: None Destinatio None n: DEFAULT_DIST_CCID This column is a Tax Driver.This column is the cost component class name. Cost Component Classes are used to identify the individual buckets or component costs that make up the total cost of an item. Note that this is necessary to support the Account Method VAT feature. production or conversion costs and so on. Descriptio n Variable Validation: None . Descriptio n Variable Validation: None Destinatio None n: CONTROL_AMOUNT This column is an optional. Descriptio n Variable Validation: None Destinatio None n: SHIP_TO_LOCATION_ID This column is a Tax Driver. Descriptio n Variable Validation: None Destinatio None n: PRODUCT_CATEGORY This column is a Tax Driver. It is the type of product. Otherwise. It is the ship to location ID. Value entered by user only if line is not PO matched. value will be entered by user. Possible values are: Goods. It is a product category. The actual use will be stored at the distribution level. .Destinatio None n: PRIMARY_INTENDED_USE This column is a Tax Driver. Descriptio n Variable Validation: None Destinatio None n: PRODUCT_TYPE This column is a Tax Driver. This value will default from Inventory Item attributes. Service. It is the purpose for which a product may be used. Descriptio n Variable Validation: None Destinatio None n: USER_DEFINED_FISC_CLASS This column is a Tax Driver. Descriptio n Variable Validation: None Destinatio None n: TAX_REGIME_CODE This column is a Tax Regime Code. It is a transactions category assigned by user.g. . The set of tax rules that determines the treatment of one or more taxes administered by a tax authority..Variable Descriptio n Validation: None Destinatio None n: PRODUCT_FISC_CLASSIFICATION This column is a Tax Driver. It is a Fiscal Classification. VAT Regime in Argentina. e. It is a Product Fiscal Classification. Descriptio n Variable Validation: None Destinatio None n: TRX_BUSINESS_CATEGORY This column is a Tax Driver. exempt. non-taxable.Variable Descriptio n Validation: None Destinatio None n: TAX This column is a classification of a charge imposed by a government through a fiscal or tax authority. Descriptio n Variable Validation: None Destinatio None n: TAX_RATE_ID . Descriptio n Variable Validation: None Destinatio None n: TAX_JURISDICTION_CODE This column is the Internal ID of the Tax Jurisdiction Descriptio n Variable Validation: None Destinatio None n: TAX_STATUS_CODE This column is the Tax status code. taxable standard rate.. zero rated. e.g. Descriptio n Variable Validation: None Destinatio None n: TAX_RATE This column is the rate specified for a tax status in effect for a period of time.This column is the Internal identifier for tax rate effective on the invoice date Descriptio n Variable Validation: None Destinatio None n: TAX_RATE_CODE This column is the tax rate name associated with tax rate identifier. Tax_rate_id is unique while a tax_rate_code may have different tax rates based on date ranges. Descriptio n Variable Validation: None Destinatio None . Descriptio n Variable Validation: None Destinatio None n: INCL_IN_TAXABLE_LINE_FLAG This column is the flag to indicate if the amount in the tax line is included or not in the taxable line. n: SOURCE_APPLICATION_ID This column is the source document application identifier Descriptio n Variable Validation: None Destinatio None n: SOURCE_ENTITY_CODE This column is the source document entity code Descriptio n Variable Validation: None Destinatio None n: SOURCE_EVENT_CLASS_CODE This column is the source document event class code Descriptio n Variable Validation: None Destinatio None n: SOURCE_TRX_ID This column is the source document transaction identifier Descriptio n Variable Validation: None Destinatio None . n: SOURCE_LINE_ID This column is the identifier of the lowest level for which Tax is calculated Descriptio n Variable Validation: None Destinatio None n: SOURCE_TRX_LEVEL_TYPE This column is the source document transaction level type Descriptio n Variable Validation: None Destinatio None n: TAX_CLASSIFICATION_CODE This column is the Tax Classification Code Descriptio n Variable Validation: None Destinatio None n: . ORG_ID -SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE' 중 하나 Table : AP_INVOICE_LINES_INTERFACE ================================== Required Columns for LINE_TYPE_LOOKUP_CODE = 'ITEM' =================================================== -INVOICE_ID : AP_INVOICES_INTERFACE. 'CREDIT' type 인 경우는 음수를 입력 -ORG_ID : AP_SYSTEM_PARAMETERS.Table : AP_INVOICE_INTERFACE ============================== Required Columns ================ -INVOICE_ID : AP_INVOICES_INTERFACE_S.INVOICE_ID .NEXTVAL 를 이용하여 생성됨 -INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함 -VENDOR_ID/VENDOR_NUM/VENDOR_NAME : Active 하여야 하며 PO_VENDORS 과 Mapping -VENDOR_SITE_ID/VENDOR_SITE_CODE : Active 한 Site 여야 하며 PO_VENDOR_SITES table 과 mapping -INVOICE_AMOUNT : 'STANDARD' type 인 경우에는 양수. NEXTVAL -LINE_NUMBER : 해당 invoice 내에서 unique 해야함. closed 혹은 final closed 된 PO NUMBER 는 안됨. validated against PO_RELEASES_ALL -PO_NUMBER or PO_HEADER_ID : Validated against PO_HEADER_ALL -PO_LINE_NUMBER or PO_LINE_ID : Validated against PO_LINES_ALL -PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID : Validated against PO_LINE_LOCATIONS_ALL If MATCH_OPTION is 'R'. -LINE_TYPE_LOOKUP_CODE : 'TAX' -TAX_CODE / TAX_CODE_ID : AP_TAX_CODES_ALL table 에서 mapping -AMOUNT -ACCOUNTING_DATE : Optional.NEXTVAL -LINE_NUMBER : 해당 invoice 내에서 unique 해야함. Defaulted from INVOICE_DATE or SYSDATE -DIST_CODE_CONCATENATED or DIST_CODE_COMBINATION_ID : select code_combination_id from gl_code_combinations where account_type = 'E' and enabled_flag = 'Y' and summary_flag = 'N' and sysdate between nvl(start_date_active. -LINE_TYPE_LOOKUP_CODE :'ITEM' -AMOUNT -ACCOUNTING_DATE: Optional.INVOICE_ID -INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.INVOICE_ID -INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.DIST_CODE_CONCATENATED / DIST_CODE_COMBINATION_ID : select code_combination_id from gl_code_combinations where account_type = 'E' and enabled_flag = 'Y' and summary_flag = 'N' and sysdate between nvl(start_date_active.-INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S. sysdate+1)) Required Columns for LINE_TYPE_LOOKUP_CODE = 'TAX' =================================================== -INVOICE_ID : AP_INVOICES_INTERFACE. sysdate+1)) 2. then populate: -RECEIPT_NUMBER : RCV_SHIPMENT_HEADERS. PO Matched Invoice 의 경우 Table: AP_INVOICE_INTERFACE ============================ Required Columns ================ -INVOICE_ID : AP_INVOICES_INTERFACE_S. then populate: -RELEASE_NUM or PO_RELEASE_ID : Blanket Release only.ORG_ID Table: AP_INVOICE_LINES_INTERFACE ================================= Required Columns for PO Matched Lines ===================================== -INVOICE_ID : AP_INVOICES_INTERFACE. sysdate-1) and nvl(end_date_active.NEXTVAL -LINE_NUMBER : 해당 invoice 내에서 unique 해야함. -LINE_TYPE_LOOKUP_CODE : 'ITEM' -AMOUNT : QUANTITY_INVOICED * UNIT_PRICE If MATCH_OPTION is 'P'. PO_HEADERS Table 과 mapping -INVOICE_AMOUNT : 'STANDARD' type 인 경우에는 양수.RECEIPT_NUM -RCV_TRANSACTION_ID or PO_LINE_LOCATION_ID : RCV_TRANSACTIONS 과 Mapping .NEXTVAL 를 이용하여 생성됨 -INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함 -PO_NUMBER : approved 된 PO 여야 하며 cancelled. Defaulted from INVOICE_DATE or SYSDATE . sysdate-1) and nvl(end_date_active. 'CREDIT' type 인 경우는 음수를 입력 -SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE' -ORG_ID : AP_SYSTEM_PARAMETERS_ALL.
Copyright © 2024 DOKUMEN.SITE Inc.