Globalization Flexfields

This document describes the globalization flexfields that store certain pieces of country- and region-specific information in the Oracle Applications data model. It contains explanations of the meaning of flexfield segment columns in country- or region-specific contexts that you may need to reference to write custom reports or use for other data extraction.

Overview

The Oracle Applications data model stores information about each business entity used by Oracle Payables, Oracle Purchasing, and so on. For a given business entity, such as an AP Invoice, there are columns to hold attributes associated with a typical invoice as used throughout the world.

However, since statutory and practical requirements can differ from region to region, designing an economical data model can be challenging. One possible but unwieldy solution might require hundreds of additional columns to store attributes required in Argentina, Brazil, the Czech Republic. Instead, Oracle Applications uses a separate mechanism for storing certain pieces of country- or region-specific information about these business entities, the globalization flexfield, using standard flexfields technology.

A globalization flexfield is a pre-defined descriptive flexfield. Each major business entity table includes ten to twenty flexfield segment columns, with contexts for various countries or regions that require additional information about that entity. In turn, some pieces of country-specific code expect certain country-specific information to reside in particular generic segment columns.

To write custom reports against country-specific data, you need to know how to interpret data contained in these flexfield segment columns. For a given table, use the information in this section to see whether we have defined a country- or region-specific context and learn the meaning of segment columns whenever that context is active. Typically, the context is stored in the GLOBAL_ATTRIBUTE_CATEGORY column, and the generic segments are named GLOBAL_ATTRIBUTEn, where n is a number between 1 and 20. Refer to the appropriate TRM to confirm the names of these columns.

Note that this mechanism allows a single table to store information that spans the entire globe, where each individual table row can be associated with a different country- or region-specific context.

For example, suppose you are trying to write a custom report used in Brazil that includes information about freight carriers. With the Oracle Inventory Technical Reference Manual, you might learn that the ORG_FREIGHT table holds definitions for each freight carrier, and learn about the columns that hold generic information about freight carriers. In addition, you should refer to the information below to learn that the ORG_FREIGHT.GLOBAL_ATTRIBUTE5 column stores the Inscription Number whenever the GLOBAL_ATTRIBUTE_CATEGORY holds the context JL.BR.INVSDFCR.ORG_FREIGHT.

For more information, see the Oracle Applications Flexfields Guide.

AP_AWT_TAX_RATES_ALL

AP_AWT_TAX_RATES_ALL contains tax rates for Withholding tax type tax codes. Oracle Payables predefines the Standard and Penalty tax rate types for withholding taxes. In addition, Certificate rate types are assigned to a specific supplier site and Exception rate types are assigned to a specific invoice. START_AMOUNT and END_AMOUNT columns are only used if the parent withholding tax uses amount ranges.

Flexfield: JG_AP_AWT_TAX_RATES

Argentina Context: JL.AR.APXTADTC.TAX_RATES

This table shows the column names and field prompts for this context.

AP_BANK_ACCOUNTS_ALL

AP_BANK_ACCOUNTS_ALL contains information about your bank accounts. You need one row for each bank account you define. Each bank account must be affiliated with one bank branch. When you initiate an automatic payment batch, enter a manual check, or create a Quick payment, you can select a bank account that you define in this table.

This table corresponds to the Bank Accounts window.

Flexfield: JG_AP_BANK_ACCOUNTS

Brazil Context: JL.BR.APXSUMBA.AR.Additional

This table shows the column names and field prompts for this context.

Denmark Context: JE.DK.APXSUMBA.INT.EDI_INFO

This table shows the column names and field prompts for this context.

Denmark Context: JE.DK.APXSUMBA.SUP.EDI_INFO

This table shows the column names and field prompts for this context.

Germany Context: JE.DE.APXSUMBA.DD_CODE

This table shows the column name and field prompt for this context.

Sweden Context: JE.SE.APXSUMBA.PAYMENT_TYPE

This table shows the column name and field prompt for this context.

AP_BANK_BRANCHES

AP_BANK_BRANCHES contains information about the bank branches you define when you set up your banks. You need one row for each bank branch you use. One bank branch may have multiple bank accounts.

This table corresponds to the Bank Branch region of the Banks window.

Flexfield: JG_AP_BANK_BRANCHES

Brazil Context: JL.BR.APXSUMBA.AR.Additional

This table shows the column name and field prompt for this context.

Colombia Context: JL.CO.APXSUMBA.BANKS

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.APXSUMBA.BANK_INFO

This table shows the column name and field prompt for this context.

AP_CHECKS_ALL

AP_CHECKS_ALL stores information about payments issued to suppliers or refunds received from suppliers. You need one row for each payment you issue to a supplier or refund received from a supplier. Your Oracle Payables application uses this information to record payments you make to suppliers or refunds you receive from suppliers. Your Oracle Payables application stores the supplier name and bank account name for auditing purposes, in case either one is changed after you create the payment. Your Oracle Payables application stores address information for all payments. If you allow changes to the supplier payment address on manual payments or Quick payments, your Oracle Payables application maintains the new address information in this table. Your Oracle Payables application uses BANK_ACCOUNT_NUM, BANK_NUM, and BANK_ACCOUNT_TYPE for the supplier‘s bank information when you use the Electronic payment method. Your Oracle Payables application stores a dummy value for CHECK_STOCK_ID for refunds, thus, CHECK_STOCK_ID should not be treated as a foreign key to AP_CHECK_STOCKS_ALL in the case of refunds.

Flexfield: JG_AP_CHECKS

Thailand Context: JA.TH.APXPAWKB.CHECKS

This table shows the column names and field prompts for this context.

AP_EXPENSE_REPORT_HEADERS_ALL

AP_EXPENSE_REPORTS_HEADERS_ALL stores header information about the expense reports entered in Oracle Payables and Oracle Self-Service Expenses.

There is one row for each expense report you enter. Your Oracle Payables application uses this information to create invoice header information when you transfer expense reports to invoice tables. Transfer expense reports to invoice tables using the Payables Invoice Import Program.

Your Oracle Payables application places the invoice ID in the VOUCHNO column when you transfer an expense report. To import invoices from an external source, Oracle recommends that you use the new Payables Open Interface tables.

This table corresponds to the header region of the Expense Reports window.

Flexfield: JG_AP_EXPENSE_REPORT_HEADERS

Thailand Context: JA.TH.APXXXEER.REPORT_HEADERS

This table shows the column names and field prompts for this context.

AP_INVOICES_ALL

AP_INVOICES_ALL contains records for invoices you enter. There is one row for each invoice you enter. An invoice can have one or more invoice distribution lines. An invoice can also have one or more scheduled payments.

An invoice of type EXPENSE REPORT must relate to a row in AP_EXPENSE_REPORT_HEADERS_ALL unless the record has been purged from AP_EXPENSE_REPORT_HEADERS_ALL. Your Oracle Payables application uses the INTEREST type invoice for interest that it calculates on invoices that are overdue. Your Oracle Payables application links the interest invoice to the original invoice by inserting the INVOICE_ID in the AP_INVOICE_RELATIONSHIPS table.

This table corresponds to the Invoices window.

Flexfield: JG_AP_INVOICES

Argentina Context: JL.AR.APXINWKB.INVOICES

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.APXINWKB.AP_INVOICES

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.APXINWKB.AP_INVOICES

This table shows the column name and field prompt for this context.

Colombia Context: JL.CO.APXINWKB.INVOICES

This table shows the column name and field prompt for this context.

Czech Republic Context: JE.CZ.APXINWKB.INVOICE_INFO

This table shows the column names and field prompts for this context.

Denmark Context: JE.DK.APXINWKB.EDI_INFO

This table shows the column names and field prompts for this context.

France Context: JE.FR.APXINWKB.TAX_RULE

This table shows the column name and field prompt for this context.

Hungary Context: JE.HU.APXINWKB.TAX_DATE

This table shows the column name and field prompt for this context.

Poland Context: JE.PL.APXINWKB.INVOICE_INFO

This table shows the column names and field prompts for this context.

Singapore Context: JA.SG.APXINWKB.INVOICES

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.MODELO347

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.MODELO347PR

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.MODELO349

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.APXINWKB.MODELO415

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.MODELO415_347

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.MODELO415_347PR

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.OTHER

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.INVOICE_INFO

This context is disabled and no longer used.

Taiwan Context: JA.TW.APXINWKB.INVOICES

This table shows the column names and field prompts for this context.

Thailand Context: JA.TH.APXINWKB.INVOICES

This table shows the column names and field prompts for this context.

AP_INVOICES_INTERFACE

AP_INVOICES_INTERFACE stores header information about invoices that you create or load for import. The invoice data can come from the following sources: EDI invoices from your suppliers that you load through Oracle e-Commerce Gateway, invoices that you load using Oracle SQL*Loader, lease invoices from Property Manager credit card transaction data that you load using the Credit Card Invoice Interface Summary and invoices that you enter through the Invoice Gateway. There is one row for each invoice you import. Your Oracle Payables application uses this information to create invoice header information when you submit the Payables Open Interface program.

AP_INVOICES_INTERFACE contains a unique invoice ID which is used to interface with AP_INVOICES_ALL.

Flexfield: JG_AP_INVOICES_INTERFACE

Argentina Context: JL.AR.APXIISIM.INVOICES_FOLDER

This table shows the column names and field prompts for this context.

Belgium Context: JE.BE.APXIISIM.EFT

This table shows the column name and field prompt for this context.

Brazil Context: JL.BR.APXIISIM.INVOICES_FOLDER

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.APXIISIM.INVOICES_FOLDER

This table shows the column name and field prompt for this context.

Czech Republic Context: JE.CZ.APXIISIM.INVOICE_INFO

This table shows the column names and field prompts for this context.

Denmark Context: JE.DK.APXIISIM.EDI_INFO

This table shows the column names and field prompts for this context.

Finland Context: JE.FI.APXIISIM.KKL_VIITE

This table shows the column names and field prompts for this context.

Finland Context: JE.FI.APXIISIM.VAPAA_VIITE

This table shows the column name and field prompt for this context.

France Context: JE.FR.APXIISIM.TAX_RULE

This table shows the column name and field prompt for this context.

Hungary Context: JE.HU.APXIISIM.TAX_DATE

This table shows the column name and field prompt for this context.

Netherlands Context: JE.NL.APXIISIM.FOREIGN

This table shows the column names and field prompts for this context.

Norway Context: JE.NO.APXIISIM.NORWAY

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.APXIISIM.INVOICE_INFO

This table shows the column names and field prompts for this context.

Singapore Context: JA.SG.APXIISIM.INVOICES_FOLDER

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXIISIM.MODELO347

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXIISIM.MODELO347PR

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXIISIM.MODELO349

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.APXIISIM.OTHER

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.APXINWKB.MODELO347

This context is disabled and no longer used.

Spain Context: JE.ES.APXINWKB.MODELO347PR

This context is disabled and no longer used.

Spain Context: JE.ES.APXINWKB.MODELO349

This context is disabled and no longer used.

Spain Context: JE.ES.APXINWKB.OTHER

This context is disabled and no longer used.

Sweden Context: JE.SE.APXIISIM.BANK_SISU

This table shows the column names and field prompts for this context.

Sweden Context: JE.SE.APXIISIM.BANK_UTLI

This table shows the column names and field prompts for this context.

Sweden Context: JE.SE.APXIISIM.POST_INLAND

This table shows the column names and field prompts for this context.

Sweden Context: JE.SE.APXIISIM.POST_UTLAND

This table shows the column names and field prompts for this context.

Switzerland Context: JE.CH.APXIISIM.DTA

This table shows the column name and field prompt for this context.

Switzerland Context: JE.CH.APXIISIM.SAD

This table shows the column name and field prompt for this context.

Taiwan Context: JA.TW.APXIISIM.INVOICES_FOLDER

This table shows the column names and field prompts for this context.

Thailand Context: JA.TH.APXIISIM.INVOICES_INTF

This table shows the column names and field prompts for this context.

AP_INVOICE_DISTRIBUTIONS_ALL

AP_INVOICE_DISTRIBUTIONS_ALL holds the distribution line information that you enter for invoices. There is a row for each invoice distribution. A distribution line must be associated with an invoice. An invoice can have multiple distribution lines.

Your Oracle Payables application automatically creates rows in this table when: 1) you choose a distribution set at the invoice level 2) you import expense reports 3) you match an invoice to a purchase order or receipt; it uses information from the matched purchase order or receipt 4) you import invoices via the Open Interface Import process 5) you select to automatically calculate tax 6) you select to automatically do withholding.

Each invoice distribution line has its own accounting date. When you account for an invoice, your Oracle Payables application creates accounting events, accounting entry headers and accounting entry lines for those distribution lines that have accounting dates included in the selected accounting date range for the Payables Accounting Process. The accounting entries can then be transferred over to General Ledger by running the Transfer to General Ledger process which creates journal entries.

Values for POSTED_FLAG may be Y for accounted distributions or N for distributions that have not been accounted. Values for ACCRUAL_POSTED_FLAG may be Y if distribution has been accounted and system is set up for accrual basis accounting or N if either distribution has not been accounted or accrual basis accounting is not used.

Values for CASH_POSTED_FLAG may be Y if distribution has been accounted and system is set up for cash basis accounting, N if either distribution has not been accounted or system is not set up for cash basis accounting or P if distribution has been partially accounted in the cash set of books.

The MATCH_STATUS_FLAG indicates the approval status for the distribution. Values for the MATCH_STATUS_FLAG can be null or N for invoice distributions that Approval has not tested or T for distributions that have been tested or A for distributions that have been tested and approved.

Invoice distributions may be interfaced over/from Oracle Assets or Oracle Projects. Your Oracle Payables application sets the ASSETS_ADDITION_FLAG to U for distributions not tested by Oracle Assets; Oracle Assets then adjusts this flag after it tests a distribution for assignment as an asset. To avoid the same invoice distribution being interfaced to both Oracle Projects and Oracle Assets, you must interface any project-related invoice distribution to Oracle Projects before you can interface it to Oracle Assets. If the project-related invoice distribution is charged to a capital project in Oracle Projects, Oracle Projects sets the ASSET_ADDITION_FLAG to P when the PA_ADDITION_FLAG is set to Y, Z or T. Oracle Assets only picks up invoice distributions with the ASSET_ADDITION_FLAG set to U and if project-related, with the PA_ADDITION_FLAG set to Y, Z, or T. PA_ADDITION_FLAG tracks the status of project-related supplier invoice distribution lines and expense report distribution lines. For supplier invoice distributions entered via Oracle Payables, the PA_ADDITION_FLAG is set to N if the distribution is project-related, otherwise it is set to E and it is updated by Oracle Projects when the distribution is processed by the Oracle Projects Interface Supplier Invoice process. Oracle Projects sets the PA_ADDITION_FLAG to Y or Z after the item is successfully processed, or may be set to a rejection code if the line is rejected during transfer to Oracle Projects; see QuickCodes listing for all the errors. You must correct the rejection reason and try to retransfer the line. For supplier invoice adjustment lines interfaced from Oracle Projects to Oracle Payables (which must net to zero with another line), the value for the PA_ADDITION_FLAG is set to T. For expense report distributions interfaced from Oracle Projects to Oracle Payables via Invoice Import, this value is set to N. This row is never picked up by the Interface Supplier Invoices process based on the AP_INVOICES.INVOICE_TYPE_LOOKUP_CODE = EXPENSE REPORT. For expense report adjustment lines interfaced from Oracle Projects to Oracle Payables which net to zero with another line, this value is set to T. Both lines are associated with the original invoice by the Oracle Projects Interface Expense Reports to AP process.

Values for the ENCUMBERED_FLAG are as follows: Y indicates a regular distribution that has been successfully encumbered by Payables; W indicates a regular distribution that has been encumbered in advisory mode even though insufficient funds existed; H indicates a regular distribution that has not been encumbered because it was put on hold; N or null indicates a regular line that has not been encumbered because it has not been looked at yet; D is the same as Y for a reversal distribution line; X is the same as W for a reversal distribution line; P is the same as H for a reversal distribution line; R indicates a line to be ignored by encumbrance and approval code because neither the original nor the reversal distributions were looked at and they offset each other so, they can be ignored.

This table corresponds to the Distributions window.

Flexfield: JG_AP_INVOICE_DISTRIBUTIONS

Argentina Context: JL.AR.APXINWKB.DISTRIBUTIONS

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.APXINWKB.D_SUM_FOLDER

This table shows the column name and field prompt for this context.

Canada Context: JA.CA.APXINWKB.INVOICE_DISTR

This context is disabled and no longer used.

Colombia Context: JL.CO.APXINWKB.DISTRIBUTIONS

This table shows the column names and field prompts for this context.

Czech Republic Context: JE.CZ.APINXWKB.FINAL

This table shows the column names and field prompts for this context.

Hungary Context: JE.HU.APXINWKB.FINAL

This table shows the column names and field prompts for this context.

Italy Context: JE.IT.APXINWKB.DISTRIBUTIONS

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.APINXWKB.FINAL

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.APXINWKB.STAT_CODE

This context is disabled and no longer used.

Spain Context: JE.ES.APXINWKB_DISTS.INV_DIST

This context is disabled and no longer used.

Slovakia Context: JE.SK.APINXWKB.FINAL

This table shows the column names and field prompts for this context.

AP_INVOICE_LINES_INTERFACE

AP_INVOICE_LINES_INTERFACE stores information used to create one or more invoice distributions. Note that one row in this table may create, during the import process, more than one invoice distribution. For example, if you enter a Tax line in this table and prorate it across multiple Item lines, during Open Interface Import the system may create multiple Tax invoice distributions based on the single Tax line in this table.

Flexfield: JG_AP_INVOICE_LINES_INTERFACE

Argentina Context: JL.AR.APXIISIM.LINES_FOLDER

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.APXIISIM.LINES_FOLDER

This table shows the column name and field prompt for this context.

Canada Context: JA.CA.APXIISIM.LINES_FOLDER

This context is disabled and no longer used.

Colombia Context: JL.CO.APXIISIM.LINES_FOLDER

This table shows the column names and field prompts for this context.

Czech Republic Context: JE.CZ.APXIISIM.FINAL

This table shows the column name and field prompt for this context.

Hungary Context: JE.HU.APXIISM.FINAL

This table shows the column names and field prompts for this context.

Hungary Context: JE.HU.APXIISIM.STAT_CODE

This context is disabled and no longer used.

Hungary Context: JE.HU.APXINWKB.STAT_CODE

This context is disabled and no longer used.

Italy Context: JE.IT.APXIISM.DISTRIBUTIONS

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.APXIISIM.FINAL

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.APXIISIM.STAT_CODE

This context is disabled and no longer used.

Poland Context: JE.APXINWKB.STAT_CODE

This context is disabled and no longer used.

Slovakia Context: JE.SK.APXIISM.FINAL

This table shows the column names and field prompts for this context.

AP_PAYMENT_SCHEDULES_ALL

AP_PAYMENT_SCHEDULES_ALL contains information about scheduled payments for an invoice. You need one row for each time you intend to make a payment on an invoice. Your Oracle Payables application uses this information to determine when to make payments on an invoice and how much to pay in an automatic payment batch.

Values for HOLD_FLAG may be ‘Y‘ to place a hold on the scheduled payment, or ‘N‘ not to do so. Values for PAYMENT_STATUS_FLAG may be ‘Y‘ for fully paid payment schedules, ‘N‘ for unpaid scheduled payments, or ‘P‘ for partially paid scheduled payments. For converted records, enter a value for AMOUNT_REMAINING.

This table corresponds to the Scheduled Payments window.

Flexfield: JG_AP_PAYMENT_SCHEDULES

Brazil Context: JL.BR.APXINWKB.AP_PAY_SCHED

This table shows the column names and field prompts for this context.

AP_REPORTING_ENTITIES_ALL

AP_REPORTING_ENTITIES_ALL contains information about the reporting entities you define for 1099 reporting. You must define at least one reporting entity for your company or agency; however, you can define as many reporting entities as you require to satisfy your multi-organization reporting needs. Each tax reporting entity you define must have a unique Tax Identification Number. When you submit your 1099 reports, you submit the reports once for each tax reporting entity you define. This table corresponds to the Reporting Entity window.

Flexfield: JG_AP_REPORTING_ENTITIES

Portugal Context: JE.PT.APXTRDRE.TAX_INFO

This table shows the column names and field prompts for this context.

AP_SYSTEM_PARAMETERS_ALL

AP_SYSTEM_PARAMETERS_ALL contains the parameters and defaults you define for operating your Oracle Payables application system. This table contains information such as your set of books, your functional currency and your default bank account and payment terms. Your Oracle Payables application also uses this information to determine default values that cascade down to supplier and invoice entry. This table corresponds to the Payables Options window. There is only one row in this table. There is no primary key for this table.

Flexfield: JG_AP_SYSTEM_PARAMETERS

Brazil Context: JL.BR.APXCUMSP.SYS_PARAMETER

This table shows the column names and field prompts for this context.

AP_TAX_CODES_ALL

AP_TAX_CODES_ALL contains information about the tax codes you define. You need one row for each tax code you want to use when entering invoices.

When you enter invoices, you can use a list of values to select a tax code defined in this table. Your Oracle Payables application also uses TAX_RATE to calculate use tax when you enter a taxable amount for an invoice.

This table corresponds to the Tax Codes window.

Flexfield: JG_AP_TAX_CODES

Argentina Context: JL.AR.APXTADTC.TAX_NAMES

This table shows the column names and field prompts for this context.

Argentina Context: JL.AR.APXTADTC.VAT

This table shows the column name and field prompt for this context.

Brazil Context: JL.BR.APXTADTC.AP_TAX_CODES

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.APXTADTC.AP_TAX_CODES

This table shows the column name and field prompt for this context.

Colombia Context: JL.CO.APXTADTC.TAX_NAMES

This table shows the column names and field prompts for this context.

Czech Republic Context: JE.CZ.APXTADTC.TAX_ORIGIN

This table shows the column name and field prompt for this context.

Hungary Context: JE.HU.APXTADTC.TAX_ORIGIN

This context is disabled and no longer used.

Korea Context: JA.KR.APXTADTC.WITHHOLDING

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.APXTADTC.TAX_ORIGIN

This table shows the column name and field prompt for this context.

Portugal Context: JE.PT.APXTADTC.TAX_INFO

This table shows the column names and field prompts for this context.

Singapore Context: JA.SG.APXTADTC.TAX_CODE

This context is disabled and no longer used.

Switzerland Context: JE.CH.APXTADTC.TAX_INFO

This table shows the column name and field prompt for this context.

Taiwan Context: JA.TW.APXTADTC.TAX_CODES

This table shows the column name and field prompt for this context.

Thailand Context: JA.TH.APXTADTC.TAX_CODES

This table shows the column name and field prompt for this context.

AR_CASH_RECEIPTS_ALL

The AR_CASH_RECEIPTS_ALL table stores one record for each receipt that you enter. Oracle Receivables concurrently creates records in the AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, and AR_RECEIVABLE_APPLICATIONS_ALL tables for invoice-related receipts. For receipts that are not related to invoices, such as miscellaneous receipts, Receivables creates records in the AR_MISC_CASH_DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ALL table.

Receivables associates a status with each receipt. These statuses include:

• APP - Applied

• UNAPP - Unapplied

• UNID - Unidentified

• NSF - Non-sufficient funds

• REV - Reversed receipt

• STOP - Stop payment

Receivables does not update the status of a receipt from UNAPP to APP until the entire amount of the receipt is either applied or placed on account. A receipt can have a status of APP even if the entire receipt amount is placed on account.

Cash receipts proceed through the confirmation, remittance, and clearance steps. Each step creates rows in the AR_CASH_RECEIPT_HISTORY table. The CODE_COMBINATION_ID column in this table stores the accounts that are debited and credited as part of the cycle of steps.

The RECEIVABLES_TRX_ID column links the AR_CASH_RECEIPTS_ALL table to the AR_RECEIVABLES_TRX_ALL table and identifies the receivables activity that you select when you enter miscellaneous receipts.

The DISTRIBUTION_SET_ID column links the AR_CASH_RECEIPTS_ALL table to the AR_DISTRIBUTION_SETS_ALL table and identifies the distribution set and the distribution set line accounts that are credited when you enter miscellaneous receipts.

The CUSTOMER_BANK_ACCOUNT_ID column replaced the CUSTOMER_MICR_ID column as a pointer to the customer bank account. The CUSTOMER_BANK_ACCOUNT_ID column is a foreign key to the AP_BANK_ACCOUNTS_ALL table for bank accounts that do not belong to you and have a type of EXTERNAL.

The GL_DATE and REVERSAL_GL_DATE columns were also moved to the AR_CASH_RECEIPT_HISTORY_ALL table because each step has its own General Ledger date and accounting impact.

The primary key for this table is CASH_RECEIPT_ID, which identifies the receipt transaction that created the row for the receipt.

Flexfield: JG_AR_CASH_RECEIPTS

Argentina Context: JL.AR.ARXRWMAI.RGW_FOLDER

This table shows the column names and field prompts for this context.

Greece Context: JE.GR.ARXRWMAI.RA_INFO

This table shows the column names and field prompts for this context.

Portugal Context: JE.PT.ARXRWMAI.RA_INFO

This table shows the column names and field prompts for this context.

Taiwan Context: JA.TW.ARXRWMAI.CASH_RECEIPTS

This context is disabled and no longer used.

AR_INTERIM_CASH_RCPT_LINES_ALL

The AR_INTERIM_CASH_RCPT_LINES_ALL table is a temporary table that stores entries for each QuickCash receipt application. After you run the Post QuickCash program, Oracle Receivables creates an entry in the AR_RECEIVABLE_APPLICATIONS_ALL table for each application. Receivables then deletes data from this table.

The primary keys for this table are CASH_RECEIPT_ID and CASH_RECEIPT_LINE_ID.

Flexfield: JG_AR_INTERIM_CASH_RCPT_LINES

Brazil Context: JL.BR.ARXRWMAI.Additional Info

This table shows the column names and field prompts for this context.

AR_MEMO_LINES_ALL_B

The AR_MEMO_LINES_ALL_B table stores information about standard memo lines for debit memos, on-account credits, debit memo reversals, chargebacks, and invoices. If AutoAccounting is based on standard line items, Oracle Receivables uses this table to obtain the revenue account.

This table also stores the tax code, unit standard price, unit of measure, and standard invoicing and accounting rules for each standard memo line.

The primary key for this table is MEMO_LINE_ID.

Flexfield: JG_AR_MEMO_LINES

Argentina Context: JL.AR.ARXSTDML.AR_MEMO_LINES

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.ARXSDML.Additional

This context is disabled and no longer used.

Brazil Context: JL.BR.ARXSTDML.Additional

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.ARXSTDML.AR_MEMO_LINES

This table shows the column names and field prompts for this context.

Hungary Context: JE.HU.ARXSTDML.STAT_CODE

This table shows the column name and field prompt for this context.

Poland Context: JE.PL.ARXSTDML.STAT_CODE

This table shows the column name and field prompt for this context.

AR_PAYMENT_SCHEDULES_ALL

The AR_PAYMENT_SCHEDULES_ALL table stores all transactions except adjustments and miscellaneous cash receipts. Oracle Receivables updates this table when activity occurs against an invoice, debit memo, chargeback, credit memo, on-account credit, or receipt. Oracle Receivables groups different transactions by entering one of these values in the CLASS column:

• INV - Invoice

• DM - Debit Memo

• GUAR - Guarantee

• CM - Credit Memo

• DEP - Deposit

• CB - Chargeback

• PMT - Receipt

Transaction classes determine if a transaction relates to either the RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALL table. Using the CUSTOMER_TRX_ID foreign key column, the AR_PAYMENT_SCHEDULES_ALL table joins to the RA_CUSTOMER_TRX_ALL table for non-payment transaction entries, such as the creation of credit memos, debit memos, invoices, chargebacks, or deposits. Using the CASH_RECEIPT_ID foreign key column, the AR_PAYMENT_SCHEDULES_ALL table joins to the AR_CASH_RECEIPTS_ALL table for invoice-related payment transactions.

When a receipt is applied, Oracle Receivables updates the AMOUNT_APPLIED, AMOUNT_DUE_REMAINING, and STATUS columns. The STATUS column changes from OP to CL for any transaction that has an AMOUNT_DUE_REMAINING value of 0. For a receipt, the amount due that remains includes on-account and unapplied amounts. Oracle Receivables stores debit items such as invoices, debit memos, chargebacks, deposits, and guarantees as positive numbers in the AMOUNT_DUE_REMAINING and AMOUNT_DUE_ORIGINAL columns. Credit items such as credit memos and receipts are stored as negative numbers.

Receipts can be confirmed or not confirmed as designated by the CONFIRMED_FLAG column. The sum of the AMOUNT_DUE_REMAINING column for a customer for all confirmed payment schedules reflects the current customer balance. If this amount is negative, then the AMOUNT_DUE_REMAINING column indicates the credit balance amount that is currently available for this customer. For invoices with split terms, Oracle Receivables creates one record in the RA_CUSTOMER_TRX_ALL table and one record in the AR_PAYMENT_SCHEDULES_ALL table for each installment. In the AR_PAYMENT_SCHEDULES_ALL table, the DUE_DATE and AMOUNT_DUE_REMAINING columns can differ for each installment of a split term invoice. Each installment is differentiated by the TERMS_SEQUENCE_NUMBER column.

If you create a debit memo reversal when you reverse a receipt, Oracle Receivables creates a new payment schedule record for the debit memo and populates the REVERSED_CASH_RECEIPT_ID column with the CASH_RECEIPT_ID column for the receipt that was reversed. Oracle Receivables creates a new payment schedule record when you create a chargeback in the Receipts window. The ASSOCIATED_CASH_RECEIPT_ID column is the cash receipt of the payment that you entered when you created the chargeback in this window.

The ACTUAL_DATE_CLOSED and GL_DATE_CLOSED columns are populated with the date of the latest transaction. The ACTUAL_DATE_CLOSED column gives the date that you applied a payment or credit to an open transaction that set the AMOUNT_DUE_REMAINING column to 0 for that transaction. Oracle Receivables uses the ACTUAL_DATE_CLOSED column to determine which transactions to include when you print statements. The GL_DATE_CLOSED column indicates the General Ledger date that your transaction was closed on. This column identifies which transactions Oracle Receivables selects when it displays current and overdue debit items in the aging reports. The aging reports also use the current balances in the AMOUNT_DUE_REMAINING column to display outstanding amounts for current and overdue debit items.

The primary key for this table is PAYMENT_SCHEDULE_ID, which identifies the transaction that created the row.

Flexfield: JG_AR_PAYMENT_SCHEDULES

Brazil Context: JL.BR.ARXTWMAI.Additional

This table shows the column names and field prompts for this context.

AR_RECEIPT_CLASSES

The AR_RECEIPT_CLASSES table stores user-defined receipt classes. Receipt classes determine if receipts that are assigned to a receipt class are manually or automatically created and also indicate the required processing steps, such as confirmation, remittance, and clearance.

The primary key for this table is RECEIPT_CLASS_ID.

Flexfield: JG_AR_RECEIPT_CLASSES

Brazil Context: JL.BR.ARXSUDRC.Additional

This table shows the column name and field prompt for this context.

Chile Context: JL.CL.ARXSUDRC.RECEIPT_CLASS

This table shows the column names and field prompts for this context.

AR_RECEIVABLE_APPLICATIONS_ALL

The AR_RECEIVABLE_APPLICATIONS_ALL table stores all accounting entries for both your cash and credit memo applications. The APPLICATION_TYPE column stores either CASH or CM (for credit memo applications). Each row in this table includes the amount applied, status, and accounting flexfield information.

Possible statuses of your applications include:

• APP - Applied

• UNAPP - Unapplied

• ACC - On-Account

• UNID - Unidentified

You use this information to determine the applications of your payments or credit memos. The status of a receivable application determines which flexfield account that Receivables uses. For example, if you enter a cash receipt of $500 as Unidentified, Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_ALL table with $500 in the AMOUNT_APPLIED column and UNID in the STATUS column. Receivables uses the CODE_COMBINATION_ID foreign key column to associate this payment with the Unidentified flexfield account. The CODE_COMBINATION_ID column stores valid Accounting Flexfield segment value combinations that are credited in General Ledger when this application is posted.

Cash applications represent cash receipt applications. The sum of the AMOUNT_APPLIED column for cash applications should always equal the amount of the cash receipt. A negative value in the AMOUNT_APPLIED column becomes a debit when this application is posted to General Ledger.

When a cash receipt is initially created, Receivables creates a row in this table for the cash receipt amount with a status of UNAPP. For each subsequent application, Receivables creates two rows: one row with a status of APP for the amount that is applied to the invoice, and one row with status of UNAPP for the negative of the amount that is applied.

If you reverse a cash application, Receivables creates two new rows: one row with status of APP for the original application‘s inverse amount (the negative of the original application amount), and one row with a status of UNAPP for the positive amount of the application that is reversed.

For example:

Credit memo applications, on the other hand, do not have rows with a status of UNAPP. Credit memo applications use only rows with a status of APP.

The CASH_RECEIPT_ID column stores the cash receipt ID of the receipt that you entered. Receivables concurrently creates a record for this receipt in the AR_CASH_RECEIPTS_ALL table. This column is null for a credit memo application. The CUSTOMER_TRX_ID and PAYMENT_SCHEDULE_ID columns also identify the transaction that you are actually applying.

The APPLIED_CUSTOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID columns identify the invoice or credit memo that receives the application.

For example, if you apply a receipt against an invoice, Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_ALL table. The CASH_RECEIPT_ID and PAYMENT_SCHEDULE_ID columns for this record identify the receipt that you are applying. The APPLIED_CUSTOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID columns for this record belong to the invoice that is receiving the application.

If you apply a credit memo against the invoice, Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_ALL table. The CUSTOMER_TRX_ID and PAYMENT_SCHEDULE_ID columns for this record identify the credit memo that you are applying. The APPLIED_CUSTOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID columns for this record belong to the invoice that is receiving the application.

If you combine an on-account credit and a receipt, Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_ALL table. The CASH_RECEIPT_ID and PAYMENT_SCHEDULE_ID columns for this record identify the receipt. The APPLIED_CUSTOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID columns for this record identify the on-account credit that you are combining with the receipt.

The CONFIRMED_FLAG column is a denormalization from the AR_CASH_RECEIPTS_ALL table. If the cash receipt is not confirmed, the applications of that receipt are not reflected in the payment schedule of the transaction that the receipt is applied against.

The primary key for this table is RECEIVABLE_APPLICATION_ID, which uniquely identifies the transaction that created the row.

Flexfield: JG_AR_RECEIVABLE_APPLICATIONS

Brazil Context: JL.BR.ARXRWMAI.Additional Info

This table shows the column names and field prompts for this context.

AR_SYSTEM_PARAMETERS_ALL

The AR_SYSTEM_PARAMETERS_ALL table stores information that you supply to customize Oracle Receivables. This table stores installation-wide options. At least one row must always exist in this table.

There is no primary key for this table.

Flexfield: JG_AR_SYSTEM_PARAMETERS

Argentina Context: JL.AR.ARXSYSPA.SYS_PARAMETERS

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.ARXSYSPA.Additional Info

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.ARXSYSPA.SYS_PARAMETERS

This table shows the column names and field prompts for this context.

Taiwan Context: JA.TW.ARXSYSPA.SYS_PARAMETERS

This context is disabled and no longer used.

AR_VAT_TAX_ALL_B

The AR_VAT_TAX_ALL_B table contains tax codes that are defined in the Tax Codes and Rates window. Each row represents a tax code and a tax rate valid for the period between the START_DATE and the END_DATE columns. For example, if you define a VAT code with a 10% rate, the TAX_RATE column would store 10.

The primary keys for this table are TAX_CODE and START_DATE.

Flexfield: JG_AR_VAT_TAX

Argentina Context: JL.AR.ARXSUVAT.AR_VAT_TAX

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.ARXSUVAT.Tax Information

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.ARXSUVAT.VAT_TAX

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.ARXSUVAT.AR_VAT_TAX

This table shows the column names and field prompts for this context.

Czech Republic Context: JE.CZ.ARXSUVAT.TAX_ORIGIN

This table shows the column name and field prompt for this context.

Hungary Context: JE.HU.ARXSUVAT.TAX_ORIGIN

This table shows the column name and field prompt for this context.

Korea Context: JA.KR.ARXSUVAT.VAT

This table shows the column name and field prompt for this context.

Poland Context: JE.PL.ARXSUVAT.TAX_ORIGIN

This table shows the column name and field prompt for this context.

Portugal Context: JE.PT.ARXSUVAT.TAX_INFO

This table shows the column names and field prompts for this context.

Singapore Context: JA.SG.ARXSUVAT.VAT_TAX

This context is disabled and no longer used.

Taiwan Context: JA.TW.ARXSUVAT.VAT_TAX

This table shows the column name and field prompt for this context.

FA_ADDITIONS_B

FA_ADDITIONS_B contains descriptive information to help you identify your assets. Oracle Assets does not use this table to calculate depreciation.

When you add an asset, Oracle Assets inserts a row into this table and into FA_ASSET_HISTORY.

When you change the asset information stored in this table, Oracle Assets updates it in this table. It also creates a new row in FA_ASSET_HISTORY.

When you perform a unit retirement, Oracle Assets reduces the CURRENT_UNITS by the units retired.

UNIT_ADJUSTMENT_FLAG is set to YES by the Additions form if you change the number of units for an asset. The Transfers form resets it to NO after you reassign the remaining units.

Oracle Assets does not support ASSET_IDs that exceed 2,000,000,000.

Flexfield: JG_FA_ADDITIONS

Argentina Context: JL.AR.FAXASSET.ADDITIONS_ADD

This table shows the column name and field prompt for this context.

Argentina Context: JL.AR.FAXASSET.FA_ADDITIONS

This context is disabled and no longer used.

Chile Context: JL.CL.FAXASSET.ADDITIONS_ADD

This table shows the column name and field prompt for this context.

Colombia Context: JL.CO.FAXASSET.ADDITIONS_ADD

This table shows the column name and field prompt for this context.

Greece Context: JE.GR.FAXASSET.ASSET

This table shows the column names and field prompts for this context.

Mexico Context: JL.MX.FAXASSET.ADDITIONS_ADD

This table shows the column name and field prompt for this context.

FA_ADJUSTMENTS

FA_ADJUSTMENTS stores information that Oracle Assets needs to create journal entries for transactions. The posting program creates journal entries for regular depreciation expense from information in FA_DEPRN_DETAIL. Oracle Assets inserts a row in this table for the debit and credit sides of a financial transaction. All the rows for the same transaction have the same value in the TRANSACTION_HEADER_ID column.

The SOURCE_TYPE_CODE column tells you which program created the adjustment:

The ADJUSTMENT_TYPE column tells you which type of account Oracle Assets adjusts.

DEBIT_CREDIT_FLAG is DR if the amount is a debit and CR if the amount is a credit.

ADJUSTMENT_AMOUNT is the amount debited or credited to the account.

ANNUALIZED_ADJUSTMENT is the adjustment amount for a period times the number of periods in a fiscal year. The depreciation program uses it to calculate the depreciation adjustment for an asset when you perform multiple retroactive transactions on the asset. Oracle Assets calculates ADJUSTMENT_PER_PERIOD by dividing the ADJUSTMENT_AMOUNT for a retroactive transaction by the number of periods between the period you entered the transaction and the period that it was effective. For current period transactions, this column is zero.

PERIOD_COUNTER_CREATED IS the period that you entered the adjustment into Oracle Assets.

PERIOD_COUNTER_ADJUSTED is the period to which the adjustment applies. It is the same as PERIOD_COUNTER_CREATED, unless you enter a reserve adjustment, in which case PERIOD_COUNTER_ADJUSTED is the last period of the fiscal year to which the adjustment applies.

CODE_COMBINATION_ID indicates the Accounting Flexfield combination Oracle Assets debits or credits for all transactions except reclassifications and intercompany transfers. This CODE_COMBINATION_ID is generated using the Account Generator, and the posting program does not perform any further processing.

Flexfield: JG_FA_ADJUSTMENTS

Argentina Context: JL.AR.FAXSUCAT.FA_ADJUSTMENTS

This context is disabled and no longer used.

FA_BOOKS

FA_BOOKS contains the information that Oracle Assets needs to calculate depreciation.

When you initially add an asset, Oracle Assets inserts one row into the table. This becomes the "active" row for the asset. Whenever you use the Depreciation Books form to change the asset‘s depreciation information, or if you retire or reinstate it, Oracle Assets inserts another row into the table, which then becomes the new "active" row, and marks the previous row as obsolete. At any point in time, there is only one "active" row in the table for an asset in any given depreciation book. Generally, Oracle Assets uses the active row, but if you run a report for a prior accounting period, Oracle Assets selects the row that was active during that period. You can identify the active row for an asset in a book because it is the only one whose DATE_INEFFECTIVE and TRANSACTION_HEADER_ID_OUT are NULL.

When Oracle Assets terminates a row, the DATE_INEFFECTIVE and TRANSACTION_HEADER_OUT are set to the DATE_EFFECTIVE and TRANSACTION_HEADER_IN of the new row, respectively. This means that you can easily identify rows affected by the same transaction because they have the same DATE_EFFECTIVE / DATE_INEFFECTIVE and TRANSACTION_HEADER_ID_IN / TRANSACTION_HEADER_ID_OUT pairs. When Oracle Assets creates the new row, the value used for the TRANSACTION_HEADER_ID_IN column is the same as the TRANSACTION_HEADER_ID in the row inserted into FA_TRANSACTION_HEADERS, and the DATE_EFFECTIVE is the system date.

When you retire an asset, Oracle Assets inserts a new row to reduce the COST by the amount retired.

When you reinstate an asset, Oracle Assets inserts a new row to increase the COST by the COST_RETIRED in the corresponding row in FA_RETIREMENTS.

RATE_ADJUSTMENT_FACTOR is originally 1. It is used to spread depreciation over the remaining life of an asset after an amortization or revaluation. If you perform a revaluation or an amortized adjustment, Oracle Assets resets the Rate Adjustment Factor to prorate the remaining recoverable net book value over the remaining life. This fraction is calculated as [Recoverable Cost - what Depreciation Reserve would be]/Recoverable Cost. The depreciation program uses this value to adjust the depreciation rate for an asset.

COST_CHANGE_FLAG is set to YES by the Depreciation Books form if you change the financial information for an asset and elect to expense the resulting depreciation adjustment. The depreciation program resets it to NO when it depreciates the asset.

ADJUSTMENT_REQUIRED_STATUS tells the depreciation program to make an adjustment to depreciation expense for retroactive transactions. The Depreciation Books form sets it to ADD for a retroactive addition, the Transfers form sets it to TFR for a retroactive transfer, and it is NONE for all other cases.

ADJUSTED_COST is used to calculate depreciation; it is the remaining depreciable basis since addition or latest amortized adjustment or revaluation.

Oracle Assets resets the Adjusted Cost at the beginning of the fiscal year for assets depreciating under NBV-based methods. ADJUSTED_CAPACITY is similar.

TAX_REQUEST_ID is the concurrent request number for the Mass Copy process that copied the asset into a tax book. This column is always NULL for corporate book rows.

PERIOD_COUNTER_CAPITALIZED is the period in which you capitalized a construction-in-process (CIP) asset.

TRANSACTION_HEADER_ID_IN identifies the transaction that created the row.

Flexfield: JG_FA_BOOKS

Argentina Context: JL.AR.FAXASSET.FA_BOOKS

This table shows the column name and field prompt for this context.

Chile Context: JL.CL.FAXASSET.FA_BOOKS

This table shows the column name and field prompt for this context.

Colombia Context: JL.CO.FAXASSET.FA_BOOKS

This table shows the column names and field prompts for this context.

Mexico Context: JL.MX.FAXASSET.FA_BOOKS

This table shows the column name and field prompt for this context.

FA_BOOK_CONTROLS

FA_BOOK_CONTROLS contains control information that affects all assets in a depreciation book.

LAST_PERIOD_COUNTER is the last period for which you ran the depreciation program on a book. Oracle Assets uses it to prevent you from running the depreciation program multiple times for a period and to ensure that you run it for consecutive periods.

INITIAL_PERIOD_COUNTER is the period prior to the one in which you created this book.

INITIAL_DATE is the last date on which you ran depreciation for this book on your previous system before you started using Oracle Assets.

ACCOUNTING_FLEX_STRUCTURE determines which Accounting Flexfield structure the depreciation book uses. It matches aCHART_OF_ACCOUNTS_ID in GL_CODE_COMBINATIONS. Oracle Assets uses it to configure Accounting Flexfield pop-up windows and to runreports that use the account number.

DEPRN_REQUEST_ID is the concurrent request number for the last time you ran the depreciation program on a book. Oracle Assets updates this columnas soon as the depreciation program begins running.

DEPRN_STATUS specifies whether depreciation is locking the book. Oracle Assets uses DEPRN_STATUS to prevent you from entering transactions while depreciation is running. It can be:

Flexfield: JG_FA_BOOK_CONTROLS

Argentina Context: JL.AR.FAXSUBCT.FA_BOOK_CTRLS

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.FAXSUBCT.FA_BOOK_CONTROL

This context is disabled and no longer used.

Chile Context: JL.CL.FAXSUBCT.FA_BOOK_CTRLS

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.FAXSUBCT.FA_BOOK_CONTROL

This context is disabled and no longer used.

Colombia Context: JL.CO.FAXSUBCT.FA_BOOK_CTRLS

This table shows the column names and field prompts for this context.

Mexico Context: JL.MX.FAXSUBCT.FA_BOOK_CTRLS

This table shows the column names and field prompts for this context.

FA_CATEGORY_BOOKS

FA_CATEGORY_BOOKS provides cost and reserve accounts for a book and category combination.

The Asset Categories form inserts a row in this table for each book in which you use an asset category. For example, if you define a category for three depreciation books, Oracle Assets inserts three rows into this table.

Flexfield: JG_FA_CATEGORY_BOOKS

Argentina Context: JL.AR.FAXSUCAT.FA_CAT_BOOKS

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.FAXSUCAT.FA_CAT_BOOKS

This table shows the column name and field prompt for this context.

Colombia Context: JL.CO.FAXSUCAT.FA_CAT_BOOKS

This table shows the column names and field prompts for this context.

Mexico Context: JL.MX.FAXSUCAT.FA_CAT_BOOKS

This table shows the column name and field prompt for this context.

Mexico Context: JLMX.FAXSUCAT.FA_CAT_BOOKS

This context is disabled and no longer used.

FA_MASS_ADDITIONS

FA_MASS_ADDITIONS stores information about assets that you want to automatically add to Oracle Assets from another system. You can use this table to load assets for system conversions.

When you run the mass additions create process, Oracle Assets inserts one row into this table for each invoice line it selects from Oracle Payables.

When you run the mass additions post process, Oracle Assets creates assets or adjustments from any rows in which the POSTING_STATUS is POST.

Mass additions post inserts rows into FA_ADDITIONS, FA_ASSET_HISTORY, FA_ASSET_INVOICES, FA_BOOKS, FA_DISTRIBUTION_HISTORY, FA_TRANSACTION_HEADERS, FA_INVOICE_TRANSACTIONS, FA_DEPRN_SUMMARY, FA_DEPRN_DETAIL, and FA_TRANSFER_DETAILS. Oracle Assets then changes POSTING_STATUS and QUEUE_NAME to POSTED.

POSTING_STATUS shows the status of a mass addition. POSTING_STATUS and QUEUE_NAME are the same, except when you assign user-defined queue names, or you split or merge a mass addition. The following table summarizes the relationship between POSTING_STATUS and QUEUE_NAME:

POST_BATCH_ID identifies the post mass additions concurrent request that posted your assets to Oracle Assets.

ADD_TO_ASSET_ID identifies the asset to which you are adding the cost of the mass addition in this row.

PARENT_ASSET_ID identifies the parent asset of a mass addition. The mass addition post process inserts this value into the PARENT_ASSET_ID column in the FA_ADDITIONS table when you post the mass addition.

PARENT_MASS_ADDITION_ID identifies the mass addition into which you merged this mass addition.

When you add the cost of a mass addition to an existing asset, NEW_MASTER_FLAG is set to YES by the Prepare Mass Additions form when the resulting asset has the asset category and description of the mass addition. This value is NO when the resulting asset has the asset category and description of the existing asset.

ATTRIBUTE1 through ATTRIBUTE30 descriptive flexfield segments are NOT the same as on FA_ADDITIONS, since they are on a different table.

For more information on loading this table, read the Importing Asset Information into Oracle Assets Using Mass Additions essay in the Oracle Financials and Oracle Government Financials Implementation Manual.

When you add a mass addition to an existing asset, Oracle Assets does not allow you to enter a salvage value for the mass addition. If adding the mass addition changes the salvage value of the destination asset, you can adjust the salvage value of the destination asset in the Depreciation Books form.

Flexfield: JG_FA_MASS_ADDITIONS

Argentina Context: JL.AR.FAXMADDS.FA_MASS_ADD

This table shows the column name and field prompt for this context.

Chile Context: JL.CL.FAXMADDS.FA_MASS_ADD

This table shows the column name and field prompt for this context.

Colombia Context: JL.CO.FAXMADDS.FA_MASS_ADD

This table shows the column name and field prompt for this context.

Mexico Context: JL.MX.FAXMADDS.FA_MASS_ADD

This table shows the column name and field prompt for this context.

FND_CURRENCIES

FND_CURRENCIES stores information about currencies. Each row includes the currency code (CURRENCY_CODE) established by ISO (International Standards Organization) standard, the name of the currency (NAME), a flag to indicate whether the currency is enabled for use at your site (ENABLED_FLAG), a flag to indicate if this is a currency or a statistical unit (CURRENCY_FLAG), and the territory code of the issuing country (ISSUING_TERRITORY_CODE). Each row also includes the number of digits to the right of the decimal point (PRECISION), the extended precision (EXTENDED_PRECISION), the symbol denoting the currency, a description of the currency, and descriptive flexfield attribute columns. There is also information on when the currency becomes active and inactive, and the minimum accountable unit for the currency. You need one row for each currency defined with Oracle Application Object Library. Oracle Application Object Library uses this information to display dynamic currency values. You can also use this information to assign a currency to a set of books.

Flexfield: JG_FND_CURRENCIES

Argentina Context: JL.AR.FNDNLDCX.CURRENCIES

This table shows the column name and field prompt for this context.

Brazil Context: JL.BR.FNDNLDCX.FND_CURRENCY

This table shows the column name and field prompt for this context.

GL_JE_HEADERS

GL_JE_HEADERS stores journal entries. There is a one-to-many relationship between journal entry batches and journal entries. Each row in this table includes the associated batch ID, the journal entry name and description, and other information about the journal entry. This table corresponds to the Journals window of the Enter Journals form. STATUS is ‘U‘ for unposted, ‘P‘ for posted. Other statuses indicate that an error condition was found. A complete list is below.

CONVERSION_FLAG equal to ‘N‘ indicates that you manually changed a converted amount in the Journal Entry Lines region of a foreign currency journal entry. In this case, the posting program does not re-convert your foreign amounts. This can happen only if your user profile option MULTIPLE_RATES_PER_JE is ‘Yes‘. BALANCING_SEGMENT_VALUE is null if there is only one balancing segment value in your journal entry. If there is more than one, BALANCING_SEGMENT_VALUE is the greatest balancing segment value in your journal entry.

Following is a list of STATUS codes for this table:

Flexfield: JG_GL_JE_HEADERS

Greece Context: JE.GR.GLXJEENT.HEADER

This table shows the column names and field prompts for this context.

GL_JE_LINES

GL_JE_LINES stores the journal entry lines that you enter in the Enter Journals form. There is a one-to-many relationship between journal entries and journal entry lines. Each row in this table stores the associated journal entry header ID, the line number, the associated code combination ID, and the debits or credits associated with the journal line. STATUS is ‘U‘ for unposted or ‘P‘ for posted.

Flexfield: JG_GL_JE_LINES_INFO

Colombia Context: JL.CO.GLXJEENT.THIRDPARTY

This table shows the column name and field prompt for this context.

Poland Context: JE.PL.GLXJEENT.SEQUENCE

This table shows the column names and field prompts for this context.

Turkey Context: JE.TR.GLXJEENT.SEQUENCE

This table shows the column names and field prompts for this context.

Czech Context: JE.CZ.GLXJEENT.SEQUENCE

This table shows the column names and field prompts for this context.

Hungary Context: JE.HU.GLXJEENT.SEQUENCE

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.GLXJEENT.SEQUENCE

This table shows the column names and field prompts for this context.

Slovakia Context: JE.SK.GLXJEENT.SEQUENCE

This table shows the column names and field prompts for this context.

GL_SETS_OF_BOOKS

GL_SETS_OF_BOOKS stores information about the sets of books you define in your Oracle General Ledger application. Each row includes the set of books name, description, functional currency, and other information. This table corresponds to the Set of Books form.

Flexfield: JG_GL_SETS_OF_BOOKS

Greece Context: JE.GR.GLXSTBKS.BOOKS

This table shows the column names and field prompts for this context.

Czech Context: JE.CZ.GLXSTBKS.BOOKS

This table shows the column names and field prompts for this context.

Hungary Context: JE.HU.GLXSTBKS.BOOKS

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.GLXSTBKS.BOOKS

This table shows the column names and field prompts for this context.

Slovakia Context: JE.SK.GLXSTBKS.BOOKS

This table shows the column names and field prompts for this context.

HR_LOCATIONS_ALL

HR_LOCATIONS_ALL holds information about specific work locations defined for an enterprise, including address details.

Flexfield: JG_HR_LOCATIONS

Argentina Context: JL.AR.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

Greece Context: JE.GR.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

Italy Context: JE.IT.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

Korea Context: JA.KR.PERWSLOC.WITHHOLDING

This table shows the column names and field prompts for this context.

Singapore Context: JA.SG.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.PERWSLOC.PRL_NO

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.PERWSLOC.PRL_YES

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.PERWSLOC.RENTED_LOCATION

This context is disabled and no longer used.

Taiwan Context: JA.TW.PERWSLOC.LOC

This table shows the column names and field prompts for this context.

HZ_CUSTOMER_PROFILES

The HZ_CUSTOMER_PROFILES table stores information about the credit characteristics of a single customer account. A profile class defined in the HZ_CUSTOMER_PROFILE_CLASSES table can be used to provide default values for the attributes in this table. The default values copied into this table can be modified to more closely match the customer account defined in this table.

The primary key for this table is CUST_ACCOUNT_PROFILE_ID.

Flexfield: JG_HZ_CUSTOMER_PROFILES

Brazil Context: JL.BR.ARXCUDCI.Additional Info

This table shows the column names and field prompts for this context.

HZ_CUST_ACCOUNTS

The HZ_CUST_ACCOUNTS table stores information about customer relationships established with a party. Since a party can have multiple customer accounts, this table may contain several records for a single party. For example, an individual person may establish a personal account, a family account, and a professional account for a consulting practice. Note that the focus of this table is a business relationship and how transactions are conducted in the relationship.

The primary key for this table is CUST_ACCOUNT_ID.

Flexfield: JG_HZ_CUST_ACCOUNTS

Argentina Context : JL.AR.ARXCUDCI.CUSTOMERS

This table shows the column names and field prompts for this context.

Chile Context : JL.CL.ARXCUDCI.CUSTOMERS

This table shows the column names and field prompts for this context.

Colombia Context : JL.CO.ARXCUDCI.CUSTOMERS

This table shows the column names and field prompts for this context.

Greece Context : JE.GR.ARXCUDCI.CUSTOMERS

This table shows the column name and field prompt for this context.

HZ_CUST_ACCT_SITES_ALL

The HZ_CUST_ACCT_SITES_ALL table stores information about customer account sites or locations for customer accounts. One customer account can have multiple sites or locations. Address information for a site is stored in the HZ_LOCATIONS table.

The primary key for this table is CUST_ACCT_SITE_ID.

Flexfield : JG_HZ_CUST_ACCT_SITES

Argentine Context : JL.AR.ARXCUDCI.Additional

This table shows the column names and field prompts for this context.

Brazil Context : JL.BR.ARXCUDCI.Additional

This table shows the column names and field prompts for this context.

Brazil Context : JL.BR.ARXSURMT.Additional

This table shows the column name and field prompt for this context.

Colombia Context : JL.CO.ARXCUDCI.Additional

This table shows the column names and field prompts for this context.

Korea Context : JA.KR.ARXCUDCI.VAT

This table shows the column names and field prompts for this context.

HZ_CUST_PROFILE_CLASSES

The HZ_CUST_PROFILE_CLASSES table stores information about the credit characteristics that are common across a group of customer accounts. The characteristics specified in this table can be used as default characteristics for similar customer accounts. For example, you can create a profile class called Large Independent Retail Stores and can specify several attributes that describe this class of customer. In the future, you can assign new customers to this class so that the new customer inherits the characteristics of the class.

The primary key for this table is PROFILE_CLASS_ID.

Flexfield: JG_HZ_CUSTOMER_PROFILE_CLASSES

Brazil Context: JL.BR.ARXMACPC.Additional Info

This table shows the column names and field prompts for this context.

HZ_CUST_SITE_USES_ALL

The HZ_CUST_SITE_USES_ALL table stores information about the business purposes assigned to a customer account site. A customer account site can have multiple purposes; however, each record in this table only specifies one purpose for a customer account site. For example, a customer account site may be assigned as a Ship-To site in one record and as a Bill-To site in another record. Note that address information about sites is stored in the HZ_LOCATIONS table.

The primary key for this table is SITE_USE_ID.

Flexfield: JG_HZ_CUST_SITE_USES

Greece Context : JE.GR.ARXCUDCI.RA

This table shows the column name and field prompt for this context.

Portugal Context : JE.PT.ARXCUDCI.RA

This table shows the column name and field prompt for this context.

Spain Context : JE.ES.ARXCUDCI.RA

This table shows the column name and field prompt for this context.

MTL_ITEM_TEMPLATES

MTL_ITEM_TEMPLATES is the definition table for item templates. It contains the user-defined name (TEMPLATE_NAME) and description (DESCRIPTION).

You can use a template to set certain item attributes. When you apply a template to an item, the enabled item attributes are propagated to the item. You may apply several different templates to an item to achieve a layering of attributes.

Flexfield: JG_MTL_ITEM_TEMPLATES

Brazil Context: JL.BR.INVIDTMP.Fiscal

This table shows the column names and field prompts for this context.

MTL_PARAMETERS

MTL_PARAMETERS maintains a set of default options like general ledger accounts; locator, lot, and serial controls; inter-organization options; costingmethod; etc. for each organization defined in Oracle Inventory.

Each organization‘s item master organization (MASTER_ORGANIZATION_ID) and costing organization (COST_ORGANIZATION_ID) are maintained here.

You specify which manufacturing calendar the organization will use (CALENDAR_CODE), as well as the set of exceptions to this calendar(CALENDAR_EXCEPTION_SET_ID).

NEGATIVE_INV_RECEIPT_CODE indicates whether this organization will allow negative balances in inventory. It is used in the transaction system toensure, for example, that you do not over-issue a particular item (if you have indicated that negative balances are not allowed).

For lot number and serial number auto-generation, you can specify whether you want the numbers generated from defaults defined at the organization level orthe item level (LOT_NUMBER_GENERATION,SERIAL_NUMBER_GENERATION). You can also specify uniqueness constraints for lot numbers(LOT_NUMBER_UNIQUENESS) and serial numbers (SERIAL_NUMBER_TYPE).

Among the accounting defaults that can be defined here are valuation accounts, receiving accounts, profit and loss accounts, and inter- organization transfer accounts.

Flexfield: JG_MTL_PARAMETERS

Italy Context: JE.IT.INVSDOIO.NPI parameters

This table shows the column names and field prompts for this context.

Thailand Context: JA.TH.INVSDOIO.Parameter Info

This context is disabled and no longer used.

MTL_SYSTEM_ITEMS_B

MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. You can specify item-related information in fields such as: Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning, MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing.

You can set up the item with multiple segments, since it is implemented as a flexfield. Use the standard ‘System Items‘ flexfield that is shipped with the product to configure your item flexfield. The flexfield code is MSTK.

The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. Therefore, the same item can be defined in more than one organization.

Each item is initially defined in an item master organization. The user then assigns the item to other organizations that need to recognize this item; a row is inserted for each new organization the item is assigned to. Many columns such as MTL_TRANSACTIONS_ENABLED_FLAG and BOM_ENABLED_FLAG correspond to item attributes defined in the MTL_ITEM_ATTRIBUTES table. The attributes that are available to the user depend on which Oracle applications are installed. The table MTL_ATTR_APPL_DEPENDENCIES maintains the relationships between item attributes and Oracle applications.

Two unit of measure columns are stored in MTL_SYSTEM_ITEMS table. PRIMARY_UOM_CODE is the 3-character unit that is used throughout Oracle Manufacturing. PRIMARY_UNIT_OF_MEASURE is the 25-character unit that is used throughout Oracle Purchasing.

Items now support multilingual description. MLS is implemented with a pair of tables: MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_TL. Translations table (MTL_SYSTEM_ITEMS_TL) holds item descriptions in multiple languages. DESCRIPTION column in the base table (MTL_SYSTEM_ITEMS_B) is for backward compatibility and is maintained in the installation base language only.

Flexfield: JG_MTL_SYSTEM_ITEMS

Argentina Context: JL.AR.INVIDITM.SYSTEM_ITEMS

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.INVIDITM.AR.Fiscal

This context is disabled and no longer used.

Brazil Context: JL.BR.INVIDITM.XX.Fiscal

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.INVIVATT.Fiscal

This context is disabled and no longer used.

Colombia Context: JL.CO.INVIDITM.Infl_Adj

This context is disabled and no longer used.

Colombia Context: JL.CO.INVIDITM.SYSTEM_ITEMS

This table shows the column names and field prompts for this context.

Hungary Context: JE.HU.INVIDITM.STAT_CODE

This table shows the column name and field prompt for this context.

Italy Context: JE.IT.INVIDITM.NPI_SYSTEM_ITEM

This table shows the column names and field prompts for this context.

Poland Context: JE.PL.INVIDITM.STAT_CODE

This table shows the column name and field prompt for this context.

OE_ORDER_LINES_ALL

OE_ORDER_LINES_ALL stores information for all order lines in Oracle Order Management.

Flexfield: JG_OE_ORDER_LINES

Argentina Context: JL.AR.OEXOEORD.LINES

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.OEXOEORD.LINES

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.OEXOEORD.LINES

This context is disabled and no longer used.

ORG_FREIGHT_TL

ORG_FREIGHT is the definition table for freight carriers. It also holds the distribution account information.

The freight carrier (FREIGHT_CODE) and freight charge distribution account (DISTRIBUTION_ACCOUNT) are used in inter-organization transfers.

Freight carriers are defined in the Freight Carriers window in Oracle Inventory.

Flexfield: JG_ORG_FREIGHT

Brazil Context: JL.BR.INVSDFCR.ORG_FREIGHT

This table shows the column names and field prompts for this context.

PO_HEADERS_ALL

PO_HEADERS_ALL contains header information for your purchasing documents. You need one row for each document you create. There are six types of documents that use PO_HEADERS_ALL:

• RFQs

• Quotations

• Standard purchase orders

• Planned purchase orders

• Blanket purchase orders

• Contracts

Each row contains buyer information, supplier information, brief notes, foreign currency information, terms and conditions information, and the status of the document.

Oracle Purchasing uses this information to record information that is related to a complete document.

PO_HEADER_ID is the unique system-generated primary key and is invisible to the user. SEGMENT1 is the system-assigned number you use to identify the document in forms and reports. Oracle Purchasing generates SEGMENT1 using the PO_UNIQUE_IDENTIFIER_CONT_ALL table if you choose to let Oracle Purchasing generate document numbers for you. SEGMENT1 is not unique for the entire table. Different document types can share the same numbers. You can uniquely identify a row in PO_HEADERS_ALL using SEGMENT1 and TYPE_LOOKUP_CODE or using PO_HEADER_ID.

If APPROVED_FLAG is ‘Y‘, the purchase order is approved. If your document type is a blanket purchase order, contract purchase order, RFQ, or quotation, Oracle Purchasing uses START_DATE and END_DATE to store the valid date range for the document. Oracle Purchasing only uses BLANKET_TOTAL_AMOUNT for blanket purchase orders or contract purchase orders.

If you autocreate a quotation from an RFQ using the Copy Document window, Oracle Purchasing stores the foreign key to your original RFQ in FROM_HEADER_ID. Oracle Purchasing also uses FROM_TYPE_LOOKUP_CODE to indicate that you copied the quotation from an RFQ.

Oracle Purchasing does not use SUMMARY_FLAG and ENABLED_FLAG. Because future vers ions of Oracle Purchasing will use them, SUMMARY_FLAG and ENABLED_FLAG should always be ‘N‘ and ‘Y‘ respectively.

You enter document header information in the Header region of the Purchase Orders, RFQs, and Quotations windows.

Flexfield: JG_PO_HEADERS

Brazil Context: JL.BR.POXPOEPO.PO_HEADERS

This table shows the column name and field prompt for this context.

PO_LINES_ALL

PO_LINES_ALL stores current information about each purchase order line. You need one row for each line you attach to a document. There are five document types that use lines:

• RFQs

• Quotations

• Standard purchase orders

• Blanket purchase orders

• Planned purchase orders

Each row includes the line number, the item number and category, unit, price, tax information, matching information, and quantity ordered for the line. Oracle Purchasing uses this information to record and update item and price information for purchase orders, quotations, and RFQs.

PO_LINE_ID is the unique system-generated line number invisible to the user. LINE_NUM is the number of the line on the purchase order. Oracle

Purchasing uses CONTRACT_NUM to reference a contract purchase order from a standard purchase order line. Oracle Purchasing uses ALLOW_PRICE_OVERRIDE_FLAG, COMMITTED_AMOUNT, QUANTITY_COMMITTED, MIN_RELEASE_AMOUNT only for blanket and planned purchase order lines.

The QUANTITY field stores the total quantity of all purchase order shipment lines (found in PO_LINE_LOCATIONS_ALL).

Flexfield: JG_PO_LINES

Brazil Context: JL.BR.POXPOEPO.PO_LINES

This table shows the column name and field prompt for this context.

PO_LINE_LOCATIONS_ALL

PO_LINE_LOCATIONS_ALL contains information about purchase order shipment schedules and blanket agreement price breaks. You need one row for each schedule or price break you attach to a document line. There are seven types of documents that use shipment schedules:

• RFQs

• Quotations

• Standard purchase orders

• Planned purchase orders

• Planned purchase order releases

• Blanket purchase orders

• Blanket purchase order releases

Each row includes the location, quantity, and dates for each shipment schedule. Oracle Purchasing uses this information to record delivery schedule information for purchase orders, and price break information for blanket purchase orders, quotations and RFQs.

PO_RELEASE_ID applies only to blanket purchase order release shipments. PO_RELEASE_ID identifies the release on which you placed this shipment.

SOURCE_SHIPMENT_ID applies only to planned purchase order release shipments. It identifies the planned purchase order shipment you chose to release from.

PRICE_OVERRIDE always equals the purchase order line price for standard purchase order shipments. For blanket and planned purchase orders, PRICE_OVERRIDE depends on the values of the ALLOW_PRICE_OVERRIDE_FLAG and NOT_TO_EXCEED_PRICE in the corresponding row in PO_LINES_ALL:

• If ALLOW_PRICE_OVERRIDE_FLAG is ‘N‘, then PRICE_OVERRIDE equals UNIT_PRICE in PO_LINES_ALL.

• If ALLOW_PRICE_OVERRIDE_FLAG is ‘Y‘, the PRICE_OVERRIDE can take any value that is smaller than NOT_TO_EXCEED_PRICE in PO_LINES_ALL.

The QUANTITY field corresponds to the total quantity ordered on all purchase order distribution lines (found in PO_DISTRIBUTIONS_ALL).

Oracle Purchasing automatically updates QUANTITY_RECEIVED, QUANTITY_ACCEPTED, and QUANTITY_REJECTED when you receive, return, or inspect goods or services. Oracle Payables automatically updates QUANTITY_BILLED when you match an invoice with a purchase order shipment. Oracle Purchasing automatically updates QUANTITY_CANCELLED when you cancel a purchase order shipment.

Oracle Purchasing sets APPROVED_FLAG to ‘Y‘ when you approve the corresponding purchase order if there are no problems associated with the shipment and its related distributions.

Oracle Purchasing sets ENCUMBERED_FLAG to ‘Y‘ and enters the ENCUMBERED_DATE when you approve a purchase order if you use encumbrance.

Flexfield: JG_PO_LINE_LOCATIONS

Brazil Context: JL.BR.APXINWKB.SHIP_MATCH

This context is disabled and no longer used.

Brazil Context: JL.BR.APXPMTCH.SHIPMENT_MATCH

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.POXPOEPO.PO_SHIPMENTS

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.POXPOERL.PO_SHIPMENTS

This table shows the column names and field prompts for this context.

PO_RELEASES_ALL

PO_RELEASES_ALL contains information about blanket and planned purchase order releases. You need one row for each release you issue for a blanket or planned purchase order. Each row includes the buyer, date, release status, and release number. Each release must have at least one purchase order shipment (PO_LINE_LOCATIONS_ALL). RELEASE_NUM is the number you assign to the release.

Flexfield: JG_PO_RELEASES

Brazil Context: JL.BR.POXPOERL.PO_RELEASES

This table shows the column name and field prompt for this context.

PO_SYSTEM_PARAMETERS_ALL

PO_SYSTEM_PARAMETERS_ALL stores default, control, and option information you provide to customize Oracle Purchasing to your company‘s needs. PO_SYSTEM_PARAMETERS_ALL corresponds to the Purchasing Options window. This table has no primary key. The table should never have morethan one row.

Flexfield: JG_PO_SYSTEM_PARAMETERS

Brazil Context: JL.BR.POXSTDPO.PO_OPTIONS

This table shows the column names and field prompts for this context.

PO_VENDORS

PO_VENDORS stores information about your suppliers. You need one row for each supplier you define. Each row includes the supplier name as well as purchasing, receiving, payment, accounting, tax, classification, and general information. Oracle Purchasing uses this information to determine active suppliers. VENDOR_ID is the unique system-generated receipt header number invisible to the user. SEGMENT1 is the system-generated or manually assigned number you use to identify the supplier in forms and reports. Oracle Purchasing generates SEGMENT1 using the PO_UNIQUE_IDENTIFIER_CONTROL table if you choose to let Oracle Purchasing generate supplier numbers for you. This table is one of three tables that store supplier information. PO_VENDORS corresponds to the Suppliers window.

Flexfield: JG_PO_VENDORS

Argentina Context: JL.AR.APXVDMVD.SUPPLIERS

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.APXVDMVD.VENDORS

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.APXVDMVD.SUPPLIERS

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.APXVDMVD.SUPPLIERS

This table shows the column names and field prompts for this context.

Greece Context: JE.GR.APXVDMVD.SUPPLIERS

This table shows the column name and field prompt for this context.

Italy Context: JE.IT.APXVDMVD.WHT_INFO

This table shows the column names and field prompts for this context.

Taiwan Context: JA.TW.APXVDMVD.PO_VENDORS

This table shows the column names and field prompts for this context.

PO_VENDOR_SITES_ALL

PO_VENDOR_SITES_ALL stores information about your supplier sites. You need a row for each supplier site you define. Each row includes the site address, supplier reference, purchasing, payment, bank, and general information. Oracle Purchasing uses this information to store supplier address information.

This table is one of three tables that store supplier information. PO_VENDOR_SITES_ALL corresponds to the Sites region of the Suppliers window.

Flexfield: JG_PO_VENDOR_SITES

Argentina Context: JL.AR.APXVDMVD.SUPPLIER_SITES

This table shows the column name and field prompt for this context.

Brazil Context: JL.BR.APXVDMVD.SITES

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.APXVDMVD.SUPPLIER_SITES

This table shows the column name and field prompt for this context.

Czech Context: JE.CZ.APXVDMVD.PO_VENDORS

This context is disabled and no longer used.

Israel Context: JE.IL.APXVDMVD.TAXPAYER_ID

This context is disabled and no longer used.

Italy Context: JE.IT.APXVDMVD.DOC_CATEGORY

This table shows the column name and field prompt for this context.

Korea Context: JA.KR.APXVDMVD.WITHHOLDING

This table shows the column name and field prompt for this context.

RA_BATCH_SOURCES_ALL

The RA_BATCH_SOURCES_ALL table stores information about the sources of your invoices, credit memos, and commitments. Each row includes information about invoice, batch, and credit memo numbering. Oracle Receivables creates one row for each batch source that you define. Receivables uses batch sources to default a transaction type during invoice entry and to determine invoice, batch, and credit memo numbering.

The BATCH_SOURCE_TYPE column stores INV for manual batches or FOREIGN for imported batches. The STATUS, CREDIT_MEMO_BATCH_SOURCE_ID, AUTO_BATCH_NUMBERING, and AUTO_TRX_NUMBERING columns are required even though they are null allowed.

The primary key for this table is BATCH_SOURCE_ID.

Flexfield: JG_RA_BATCH_SOURCES

Argentina Context: JL.AR.RAXSUMSC.BATCH_SOURCES

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.RAXSUMSC.Additional

This table shows the column names and field prompts for this context.

Taiwan Context: JA.TW.RAXSUMSC.BATCH_SOURCES

This table shows the column names and field prompts for this context.

RA_CUSTOMER_TRX_ALL

The RA_CUSTOMER_TRX_ALL table stores invoice, debit memo, commitment, bills receivable, and credit memo header information. Each row in this table includes general invoice information such as customer, transaction type, and printing instructions. One row exists for each invoice, debit memo, commitment, bill receivable, and credit memo that you create in Oracle Receivables. Invoices, debit memos, credit memos, bills receivable, and commitments are distinguished by their associated transaction types, which are stored in the RA_CUST_TRX_TYPES_ALL table.

If you entered a credit memo, the PREVIOUS_CUSTOMER_TRX_ID column stores the customer transaction ID of the invoice that you credited. In the case of on-account credits, which are not related to any invoice when the credits are created, the PREVIOUS_CUSTOMER_TRX_ID column is null. If you create an invoice against a commitment, Receivables stores the customer transaction ID of the commitment in the INITIAL_CUSTOMER_TRX_ID column. Otherwise, the INITIAL_CUSTOMER_TRX_ID column is null.

The COMPLETE_FLAG column stores Y or N to indicate if the invoice is complete. When you complete an invoice, Receivables creates your payment schedules and updates any commitments against this invoice. Before an invoice can be completed, the invoice must have at least one invoice line, revenue records must exist for each line and add up to the line amount, and a sales tax record must exist for each line.

The SOLD_TO_CUSTOMER_ID, SOLD_TO_SITE_USE_ID, BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID, PRINTING_OPTION, PRINTING_PENDING, TERM_ID, REMIT_TO_ADDRESS_ID, PRIMARY_SALES_REP_ID, and INVOICE_CURRENCY_CODE columns are required even though they are null allowed.

The primary key for this table is CUSTOMER_TRX_ID.

Flexfield: JG_RA_CUSTOMER_TRX

Argentina Context: JL.AR.ARXTWMAI.TGW_HEADER

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.ARXTWMAI.Additional Info

This table shows the column names and field prompts for this context.

Chile Context: JL.CL.ARXTWMAI.TGW_HEADER

This table shows the column names and field prompts for this context.

Colombia Context: JL.CO.ARXTWMAI.TGW_HEADER

This table shows the column names and field prompts for this context.

Czech Republic Context: JE.CZ.ARXTWMAI.TAX_DATE

This table shows the column names and field prompts for this context.

Hungary Context: JE.HU.ARXTWMAI.TAX_DATE

This table shows the column name and field prompt for this context.

Poland Context: JE.PL.ARXTWMAI.TAX_DATE

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.ARXTWMAI.INVOICE_INFO

This context is disabled and no longer used.

Spain Context: JE.ES.ARXTWMAI.MODELO347

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.ARXTWMAI.MODELO347PR

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.ARXTWMAI.MODELO349

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.ARXTWMAI.MODELO415

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.ARXTWMAI.MODELO415_347

This table shows the column name and field prompt for this context.

Spain Context: JE.ES.ARXTWMAI.MODELO415_347PR

This table shows the column names and field prompts for this context.

Spain Context: JE.ES.ARXTWMAI.OTHER

This table shows the column name and field prompt for this context.

Spain Context: JE.EX.ARXTWMAI.OTHER

This context is disabled and no longer used.

Taiwan Context: JA.TW.ARXTWMAI.RA_CUSTOMER_TRX

This table shows the column names and field prompts for this context.

Slovakia Context: JE.SK.ARXTWMAI.TAX_DATE

This table shows the column name and field prompt for this context.

RA_CUSTOMER_TRX_LINES_ALL

The RA_CUSTOMER_TRX_LINES_ALL table stores information about invoice, debit memo, credit memo, bills receivable, and commitment lines. For example, an invoice can have one line for Product A and another line for Product B. Each line requires one row in this table.

Invoice, debit memo, credit memo, bills receivable, and commitment lines are distinguished by the transaction type of the corresponding row in the RA_CUSTOMER_TRX_ALL table. Credit memos must also have a value in the PREVIOUS_CUSTOMER_TRX_LINE_ID column. On-account credits, which are not related to specific invoices or invoice lines when they are created, will not have values in this column.

The QUANTITY_ORDERED column stores the amount of product that was ordered. The QUANTITY_INVOICED column stores the amount of product that was invoiced. For manually entered invoices, the QUANTITY_ORDERED and QUANTITY_INVOICED columns must be the same. For invoices that were imported through AutoInvoice, the QUANTITY_ORDERED and QUANTITY_INVOICED columns can be different. If you enter a credit memo, the QUANTITY_CREDITED column stores the amount of product that was credited.

The UOM_CODE column stores the unit of measure code as defined in the MTL_UNITS_OF_MEASURE table. The UNIT_STANDARD_PRICE column stores the list price per unit for this transaction line. The UNIT_SELLING_PRICE column stores the selling price per unit for this transaction line. For transactions that were imported through AutoInvoice, the UNIT_STANDARD_PRICE and UNIT_SELLING_PRICE columns can be different. The DESCRIPTION, TAXING_RULE, QUANTITY_ORDERED, UNIT_STANDARD_PRICE, UOM_CODE, and UNIT_SELLING_PRICE columns are required even though they are null allowed.

Receivables uses the LINE_TYPE column to distinguish between the different types of lines that are stored in this table. LINE represents regular invoice lines that normally refer to an item. TAX represents a tax line. The LINK_TO_CUST_TRX_LINE_ID column references the invoice line that is associated with the row that holds the TAX line type. FREIGHT is similar to TAX, but you can have at most one freight line per invoice line. You can also have one freight line that has a null LINK_TO_CUST_TRX_LINE_ID column. An invoice that has one freight line with a null LINK_TO_CUST_TRX_LINE_ID column has header-level freight.

CB represents a chargeback line. For every row in this table that belongs to a completed postable or nonpostable transaction, where the RA_CUSTOMER_TRX.COMPLETE_FLAG is Y, there must be at least one row in the RA_CUST_TRX_LINE_GL_DIST table that stores accounting information. There must be at least one row in this table even for nonpostable transactions.

The primary key for this table is CUSTOMER_TRX_LINE_ID.

Flexfield: JG_RA_CUSTOMER_TRX_LINES

Argentina Context: JL.AR.ARXTWMAI.LINES

This table shows the column names and field prompts for this context.

Brazil Context: JL.BR.ARXTWMAI.Additional Info

This table shows the column names and field prompts for this context.