Key Tables: Financials General Ledger 123456789GL_SETS_OF_BOOKS GL_IMPORT_REFERENCES GL_DAILY_RATES GL_JE_LINES GL_PERIODS GL_JE_HEADERS GL_JE_BATCHES GL_BALANCES GL_CODE_COMBINATIONS

GL_SETS_OF_BOOKS Stores information about the sets of books you define in your Oracle General Led ger application. Each row includes the set of books name, description, functiona l currency, and other information. This table corresponds to the Set of Books fo rm. GL_IMPORT_REFERENCES Stores individual transactions from subledgers that have been summarized into Or acle General Ledger journal entry lines through the Journal Import process. You can specify the journal entry sources for which you want to maintain your transa ction s origin by entering Yes in the Import Journal References field of the Journal Sources form. For each source that has Import Journal References set to Yes , Oracle General Ledg er will populate GL_IMPORT_REFERENCES with one record for each transaction in yo ur feeder system. GL_DAILY_RATES Stores the daily conversion rates for foreign currency transactions. It replaces the GL_DAILY_CONVERSION_RATES table. It stores the rate to use when converting between two currencies for a given conversion date and conversion type. Each row in this table has a corresponding inverse row in which the from and to currenci es are switched. For example, if this table contains a row with a from_currency of YEN, a to_curr ency of CND, a conversion_type of Spot, and a conversion_date of January 1, 1997 , it will also contain a row with a from_currency of CND, a to_currency of YEN, a conversion_type of Spot, and a conversion_date of January 1, 1997. In general, this row will contain a rate that is the inverse of the matching row . One should never insert directly into this table. They should instead insert i nto the DAILY_RATES_INTERFACE table. Data inserted into the GL_DAILY_RATES_INTER FACE table will be automatically copied into this table. 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. GL_PERIODS Stores information about the accounting periods you define using the Accounting Calendar form. Each row includes the start date and end date of the period, the period type, the fiscal year, the period number, and other information. There is a one to many relationship between a row in the GL_PERIOD_SETS table and rows inthi s table.

GL_JE_HEADERS Stores journal entries. There is a one to many relationship between journal entry ba tches and journal entries. Each row in this table includes the associated batch ID, the journal entry name and description, and other information about the jour nal entry. This table corresponds to the Journals window of the Enter Journals f orm. STATUS is U for unposted, P for posted. Other statuses indicate that an error c ondition was found. CONVERSION_FLAG equal to N indicates that you manually changed a converted amount in the Journal Entry Lines zone of a foreign currency journa l entry. In this case, the posting program does not re convert your foreign amount s. 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 gr eatest balancing segment value in your journal entry. GL_JE_BATCHES Stores journal entry batches. Each row includes the batch name, description, sta tus, running total debits and credits, and other information. This table corresp onds to the Batch window of the Enter Journals form. STATUS is U for unposted, P for posted, S for selected, I for in the process of being posted. Other values of statu s indicate an error condition. STATUS_VERIFIED is N when you create or modify an u nposted journal entry batch. The posting program changes STATUS_VERIFIED to I when posting is in process and Y af ter posting is complete.

GL_BALANCES Stores actual, budget, and encumbrance balances for detail and summary accounts. This table stores functional currency, foreign currency, and statistical balanc es for each accounting period that has ever been opened. ACTUAL_FLAG is either A , B , or E for actual, budget, or encumbrance balances, respect vely. If ACTUAL_FLAG is B , then BUDGET_VERSION_ID is required. If ACTUAL_FLAG is E , then ENCUMBRANCE_TYPE_ID is required. GL_BALANCES stores period activity for an account in the PERIOD_NET_DR and PERIO D_NET_CR columns. The table stores the period beginning balances in BEGIN_BALANC E_DR and BEGIN_BALANCE_CR. An account s year to date balance is calculated as BEGIN_BALANCE_DR BEGIN_BALANCE_CR + PERIOD_NET_DR PERIOD_NET_CR. Detail and summary foreign currency balances that are the result of posted foreign currency journal entries have TRANSLATED_FLAG s et to R , to indicate that the row is a candidate for revaluation. For foreign currency rows, the begin balance and period net columns contain the foreign currency balance, while the begin balance and period net BEQ columns con tain the converted functional currency balance. Detail foreign currency balances that are the result of foreign currency translation have TRANSLATED_FLAG set to Y or N . N indicates that the translation is out of date (i.e., the account needs to e re translated). Y indicates that the translation is current. Summary foreign currency balances that are the result of foreign currency transl ation have TRANSLATED_FLAG set to NULL. All summary account balances have TEMPLA TE_ID not NULL. The columns that end in ADB are not used. Also, the REVALUATION_ STATUS column is notused. GL_CODE_COMBINATIONS Stores valid account combinations foreach Accounting Flexfield structure within your Oracle General Ledger application. Associated with each account are certain codes and flags, including whether the account is enabled, whether detail posti ng ordetail budgeting is allowed, and others. Segment values are stored in the S EGMENT columns. Note that each Accounting Flexfield structure may use different SEGMENT columns within the table to store the flexfield value combination. Moreo ver, the SEGMENT columns that are used are not guaranteed to be in any order. Th e Oracle Application Object Library table FND_ID_FLEX_SEGMENTS stores informatio n about which column in this table is used for each segment of each Accounting F lexfield structure. Summary accounts have SUMMARY_FLAG = Y and TEMPLATE_ID not NUL

L. Detail accounts have SUMMARY_FLAG = Receivables 123456RA_CUSTOMER_TRX_ALL RA_CUSTOMER_TRX_LINES_ALL RA_CUST_TRX_LINE_GL_DIST_ALL AR_PAYMENT_SCHEDULES_ALL AR_RECEIVABLES_TRX_ALL AR_RECEIVABLE_APPLICATIONS_ALL

and TEMPLATE_ID NULL.

RA_CUSTOMER_TRX_ALL This table stores invoice, debit memo, commitment, and credit memo header inform ation. Each row includes general invoice information such as customer, transacti on type, and printing instructions. You need one row for each invoice, debit mem o, commitment, and credit memo you create in Oracle Receivables. Invoices, debit memos, credit memos, and commitments are all distinguished by th eir transaction types stored in RA_CUST_TRX_TYPES_ALL. If you entered a credit m emo, PREVIOUS_CUSTOMER_TRX_ID stores the customer transaction identifier of the invoice you credited. In the case of on account credits, which are not related t o any invoice at creation, PREVIOUS_CUSTOMER_TRX_ID is null. If you created an i nvoice against a commitment, Oracle Receivables stores the customer transaction identifier of the commitment in INITIAL_CUSTOMER_TRX_ID, otherwise it is null. C OMPLETE_FLAG stores Y for Yes and N for No to indicate if your invoice is complete. When you complete an invoice, Oracle Receivables creates your payment schedules and updates any commitments against this invoice. Before an invoice can be compl eted, it must have at least one invoice line, revenue records must exist for eac h line and add up to the line amount, and a sales tax record must exist for each line. Required Columns: 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 are required even though they are null allowed. The primary key for this table i s CUSTOMER_TRX_ID. RA_CUSTOMER_TRX_LINES_ALL This table stores information about invoice, debit memo, credit memo, and commit ment lines. For example, an invoice can have one line for Product A and another line for Product B. You need one row for each line. Invoice, debit memo, credit memo, and commitment lines are distinguished by the transaction type of the corr esponding RA_CUSTOMER_TRX_ALL record. Also, credit memos are required to have a value in PREVIOUS_CUSTOMER_TRX_LINE_ID , except on account credits which are not related to specific invoices/invoice l ines at creation time, will not have values in this column. QUANTITY_ORDERED sto res the amount of product ordered. QUANTITY_INVOICED stores the amount of produc t invoiced. For invoices entered through the window, QUANTITY_ORDERED and QUANTI TY_INVOICED must be the same. For invoices imported through AutoInvoice, QUANTITY_ORDERED and QUANTITY_INVOICE D can be different. If you enter a credit memo, QUANTITY_CREDITED stores the amo

unt of product credited. UOM_CODE stores the unit of measure code as defined in MTL_UNITS_OF_MEASURE. UNIT_STANDARD_PRICE stores the list price per unit for thi s transaction line. UNIT_SELLING_PRICE stores the selling price per unit for thi s transaction line. For transactions imported through AutoInvoice, UNIT_STANDARD _PRICE and UNIT_SELLING_PRICE can be different. DESCRIPTION, TAXING_RULE, QUANTI TY_ORDERED, UNIT_STANDARD_PRICE,UOM_CODE, and UNIT_SELLING_PRICE are required ev en though they are null allowed. LINE_TYPE differentiates between the different types of lines that are stored in this table. LINE points to regular invoice lines that normally refer to an item . TAX signifies that this is a tax line. The column LINK_TO_CUST_TRX_LINE_ID ref erences another row in this table that is the invoice line associated with the r ow of type TAX. FREIGHT works the same way as TAX but there you can have at most one FREIGHT type l ine per invoice line of type LINE. You can also have one lin e of type FREIGHT that has a null LINK_TO_CUST_TRX_LINE_ID (and this is referred to as header level freight). CHARGES works just like the LINE type. A line_type of CB is created for a Chargeback line. For every row in this table that belongs to a complete transaction (where RA_CUSTOMER_TRX.COMPLETE_FLAG = Y), there must be at least one row in the table RA_CUST_TRX_LINE_GL_DIST (which stores accounti ng information), even for non postable transactions. The primary key for this tabl e is CUSTOMER_TRX_LINE_ID. RA_CUST_TRX_LINE_GL_DIST_ALL This table stores the accounting records for revenue, unearned revenue and unbil led receivables for each invoice or credit memo line. Each row includes the GL a ccount and the amount of the accounting entry. The AMOUNT column in this table i s required even though it is null allowed. You need one row for each accounting distribution. You must have at least one (b ut you can have multiple) accounting distributions for each invoice or credit me mo line. Oracle Receivables uses this information to post the proper amounts to your general ledger. If your invoice or credit memo has a transaction type where Post to GL is set to No, Oracle Receivables assigns Null to GL_DATE. If your AutoAccounting is unable to complete your general ledger default account s using the AutoAccounting rules you define, incomplete general ledger accounts are stored in CONCATENATED_SEGMENTS. If you are importing a transaction through AutoInvoice and the general ledger date of your transaction is in a closed accou nting period, AutoInvoice uses the general ledger date of the first open account ing period and stores the original general ledger date in ORIGINAL_GL_DATE. ACCO UNT_CLASS defines which type of distribution row you are on. The ACCOUNT_CLASS REC represents the receivable account and is for the total amo unt of the invoice. There can be at most two REC rows. One that has a ACCOUNT_SE T_FLAG set to Y and the other has ACCOUNT_SET_FLAG set to N. Use LATEST_REC_FLAG to join to the later of the two rows. ACCOUNT_SET_FLAG is Y if this row is part of an account set. An account set is a set of rows that represent a model distr ibution. Account sets are used for invoices with rules. The rows represent how t he actual distribution rows should be created and what percentage of the actual distribution should be allocated to each account. For invoices with rules, the distributions are not created when the invoice is i nitially created. Instead, the invoices are created when the Revenue Recognition program is run. The primary key for this table is CUST_TRX_LINE_GL_DIST_ID. AR_PAYMENT_SCHEDULES_ALL This table stores all transactions except adjustments and miscellaneous cash rec eipts. Oracle Receivables updates this table when activity occurs against an inv oice, debit memo, chargeback, credit memo, on account credit, or receipt. Oracle Receivables groups different transactions bythe column CLASS. These classes inc lude invoice (INV), debit memos(DM), guarantees (GUAR), credit memos (CM), depos its (DEP),chargebacks (CB), and receipts (PMT). Transaction classes determine which columns in this table Oracle Receivables upd ates when a transaction occurs, and whether a transaction relates to either the

RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALLtable. AR_PAYMENT_SCHEDULES _ALL joins to the RA_CUSTOMER_TRX_ALL table for non payment transaction entries su ch as the creation of credit memos, debit memos, invoices, chargebacks, or depos its. AR_PAYMENT_SCHEDULES_ALL uses the foreign key CUSTOMER_TRX_ID to join to the RA_ CUSTOMER_TRX_ALL table for these transactions. AR_PAYMENT_SCHEDULES_ALL joins to the AR_CASH_RECEIPTS_ALL table for invoice related payment transactions using the foreign key CASH_RECEIPT_ID. When a receiptis applied, Oracle Receivables updat es AMOUNT_APPLIED, STATUS and AMOUNT_DUE_REMAINING. STATUS changes from OP to CL for any transaction that has an AMOUNT_DUE_REMAINING value of 0(Zero). ACTUAL_DATE_CLOSED and GL_DATE_CLOSED are populated with the date of the latest transaction. For a receipt, the amount due remaining includes on account and una pplied amounts. Oracle Receivables stores debit items such as invoices, debit me mos, chargebacks, deposits, and guarantees as positive numbers in the AMOUNT_DUE _REMAINING and AMOUNT_DUE_ORIGINAL columns. Credit items such as credit memos an d receipts are stored as negative numbers. In Release 10, receipts can be confir med 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 r eflects the current customer balance. If this amount is negative, then this colu mn indicates the credit balance amount currently available for this customer. Fo r invoices with split terms, one record is created in RA_CUSTOMER_TRX_ALL and on e record is stored in AR_PAYMENT_SCHEDULES_ALL for each installment. In AR_PAYME NT_SCHEDULES_ALL, DUE_DATE and AMOUNT_DUE_REMAINING can differ for each installm ent of a split term invoice. Each installment is differentiated by the TERMS_SEQ UENCE_NUMBER column. If you create a debit memo reversal when you reverse a receipt, Oracle Receivabl es creates a new payment schedule record for the debit memo and fills in REVERSE D_CASH_RECEIPT_ID with the CASH_RECEIPT_ID of the receipt that was reversed. Ora cle Receivables creates a new payment schedule record when you create a chargeba ck in the Receipts window. ASSOCIATED_CASH_RECEIPT_ID is the cash receipt of the payment you entered when you created the chargeback in this window. GL_DATE_CLO SED indicates the general ledger date on which your transaction was closed. This column identifies which transactions Oracle Receivables selects when it dis plays current and overdue debit items in the aging reports. The aging reports al so utilize the current balances in AMOUNT_DUE_REMAINING to display outstanding a mounts for current and overdue debit items. ACTUAL_DATE_CLOSED gives the date on which you applied a payment or credit to an open transaction that set AMOUNT_DU E_REMAINING to 0 for that transaction. Oracle Receivables uses ACTUAL_DATE_CLOSE D to determine which transactions to include when you print statements. The prim ary key for this table is PAYMENT_SCHEDULE_ID, which identifies the transaction that created the row. AR_RECEIVABLES_TRX_ALL This table links accounting information with your Receivables Activities. Possib le types of activities include Adjustment, Miscellaneous Cash, and Finance Charg es. If your type is Miscellaneous Cash, you can associate either a distribution set or a standard accounting flexfield to your Receivables Activity. Oracle Rece ivables uses one row for each activity. You use your receivables activities to s peed receipt entry and generate finance charges. The other types of activities t hat were valid in release 9 and no longer valid in Release 10 were converted (as part of the upgrade) such that the actual accounting flexfield CODE_COMBINATION _ID is stored in the table instead of the RECEIVABLES_TRX_ID. In Release 9, all of these references were in AR_BATCH_SOURCES; they are now in AR_RECEIPT_METHOD_ ACCOUNTS_ALL. The primary key for this table is RECEIVABLES_TRX_ID. AR_RECEIVABLE_APPLICATIONS_ALL This table stores all accounting entries for your cash and credit memo applicati ons. Each row includes the amount applied, status, and accounting flexfield info rmation. Possible statuses of your applications include APP, UNAPP, ACC, and UNI D. You use this information to determine the applications of your payments or cr

edit memos. CONFIRMED_FLAG is a denormalization from AR_CASH_RECEIPTS_ALL. If the cash receipt is not confirmed, the applications of that receipt are not r eflected in the payment schedule of the transaction it is applied against. There are two kinds of applications: CASH and CM (for credit memo applications). This is stored in the column APPLICATION_TYPE. CASH applications represent applications of a cash receipt. When a cash receipt is initially created, a row is created in this table that has a status of UNAPP for the amount of the cash receipt. Each subsequent application creates two rows one with a status of APP for the amount being applied to the invoice and one wi th status UNAPP for the negative of the amount being applied. Ifyou reverse a ca sh application, a row with status APP with the inverse amount of the original ap plication (i.e. the negative of the original application amount) is created. The corresponding UNAPP rows is alsocreated which will have a positive amount (the same amount as the application being reversed). For example: UNAPP 100 creation of a$100 cash receipt APP 60 application of $60 of this cash receipt UNAPP 60 thi s row takes away (debits) unapplied APP 60 reversal of the $60 application UNAPP 60 this rows puts back(credits) unapplied The sum of the AMOUNT_APPLIED column f or CASH applications should always equal the amount of the cash receipt. CM appl ications, on the other hand, do not have rows of status UNAPP. They only use row s with a status of APP. CASH_RECEIPT_ID stores the cash receipt identifier of th e receipt you entered. Oracle Receivables concurrently creates a record of this receipt in the AR_CASH_RECEIPTS_ALL table. This column is null for a credit memo application. CODE_COMBINATION_ID stores va lid Accounting Flexfield segment value combinations that will be credited in the General Ledger when this application is posted. A negative value in AMOUNT_APPL IED becomes a debit. The STATUS of a receivable application determines which fle xfield account Oracle Receivables uses. For example, if you enter a cash receipt of $500 as Unidentified, Oracle Receivables creates a record in theAR_RECEIVABL E_APPLICATIONS_ALL table with AMOUNT_APPLIED = 500 and STATUS = UNID . Oracle Recei vables uses the foreign key CODE_COMBINATION_ID to associate this payment with t he Unidentified flexfield account. CUSTOMER_TRX_ID, CASH_RECEIPT_ID, and PAYMENT _SCHEDULE_ID identify the transaction that you are actually applying. APPLIED_CU STOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID identify the invoice or credit mem o that receives the application. For example, if you apply a receipt against an invoice, Oracle Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_A LL table. The CASH_RECEIPT_ID and the PAYMENT_SCHEDULE_ID of this record identif y the receipt you are applying. APPLIED_PAYMENT_SCHEDULE_ID and APPLIED_CUSTOMER _TRX_ID for this record belong to the invoice that is receiving the application. If you apply a credit memo against the invoice, Oracle Receivables creates a re cord in the AR_RECEIVABLE_APPLICATIONS_ALL table that has theCUSTOMER_TRX_ID and the PAYMENT_SCHEDULE_ID of the credit memo you are applying. The APPLIED_PAYMEN T_SCHEDULE_ID and the APPLIED_CUSTOMER_TRX_ID of this record belong to the invoi ce that is receiving the application. If you combine an on account credit and a receipt, Oracle Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_A LL table. The PAYMENT_SCHEDULE_ID and the CASH_RECEIPT_ID of this record identify the rece ipt. The APPLIED_PAYMENT_SCHEDULE_ID and the APPLIED_CUSTOMER_TRX_ID of this rec ord identify the on account credit that you are combining with the receipt. The primary key for this table is RECEIVABLE_APPLICATION_ID, which uniquely identifi es the transaction that created the row.

Payables 1234AP_INVOICES_ALL AP_INVOICE_DISTRIBUTIONS_ALL AP_PAYMENT_SCHEDULES_ALL AP_HOLDS_ALL

5- AP_AE_LINES_ALL 6- AP_AE_HEADERS_ALL AP_INVOICES_ALL AP_INVOICES_ALL contains records for invoices you enter. There is one row for ea ch 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 EX PENSE REPORT must relate to a row in AP_EXPENSE_REPORT_HEADERS_ALL unless the re cord has been purged from AP_EXPENSE_REPORT_HEADERS_ALL. Your Oracle Payables ap plication uses the INTEREST type invoice for interest that itcalculates on invoi ces that are overdue. Your Oracle Payables application links the interest invoic e to the original invoice by inserting the INVOICE_ID in the AP_INVOICE_RELATION SHIPS table. AP_INVOICE_DISTRIBUTIONS_ALL AP_INVOICE_DISTRIBUTIONS_ALL holds the distribution line information that you en ter for invoices. There is a row for each invoice distribution. A distribution l ine must be associated with an invoice. An invoice can have multiple distributio n lines. Your Oracle Payables application automatically creates rows in this tab le 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; ituses 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 OraclePayables application creates accounting events, accounti ng entry headers and accounting entry lines for those distribution lines that ha ve accounting dates included in the selected accounting date range for the Payab les Accounting Process.The accounting entries can then be transferred over to Ge neral Ledger by running the Transfer to General Ledger process which creates jou rnal entries. Values for POSTED_FLAG may be Y for accounted distributions or N f or distributions that have not been accounted. Values for ACCRUAL_POSTED_FLAG ma y 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 dist ribution has not been accounted or system is not set up for cash basis accountin g or P if distribution has been partially accounted in the cash set of books. Th e MATCH_STATUS_FLAG indicates the approval status for the distribution. Values f or the MATCH_STATUS_FLAG can be null or N for invoice distributions that Approva l has not tested or T for distributions that have been tested or A for distribut ions that have been tested and approved. Invoice distributions may be interfaced over/from Oracle Assets or Oracle Projects. Your Oracle Payables application se ts 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 assignmen t 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 relat ed invoice distribution is charged to a capital project in Oracle Projects, Orac le Projects sets the ASSET_ADDITION_FLAG to P when the PA_ADDITION_FLAG is set t o Y, Z or T. Oracle Assets only picks up invoice distributions with the ASSET_AD DITION_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 dis tribution 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 O racle Projects Interface Supplier Invoice process. Oracle Projects sets the PA_A DDITION_FLAG to Y or Z after the item is successfully processed, or may be set t o a rejection code if the line is rejected during transfer to Oracle Projects; s ee QuickCodes listing for all the errors. You must correct the rejection reason an try to retransfer the line. For supplier invoice adjustment lines interfaced from Oracle Projects to Oracle Payables (which must net to zero with another lin e), the value for the PA_ADDITION_FLAG is set to T. For expense report distribut ions 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 Invoic es process based on the AP_INVOICES.INVOICE_TYPE_LOOKUP_CODE = EXPENSEREPORT. Fo r expense report adjustment lines interfaced from Oracle Projects to Oracle Paya bles which net to zero with another line, thisvalue is set to T. Both lines are associated with the original invoice by the Oracle Projects Interface Expense Re ports to AP process. Values for the ENCUMBERED_FLAG are as follows: - Y indicates aregular distribution that has been successfully encumbered by Pay ables; - W indicates a regular distribution that has been encumbered in advisory mode e ven though insufficient funds existed; - H indicates a regular distribution that has not been encumbered because it was put on hold; - Nor 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 neit her the original nor the reversal distributions were looked at and they offset e ach other so, they can be ignored. AP_PAYMENT_SCHEDULES_ALL AP_PAYMENT_SCHEDULES_ALL contains information about scheduled payments for an in voice. 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 ma ke payments on an invoice and how much to pay in an automatic payment batch. Val ues 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 convert ed records, enter a value for AMOUNT_REMAINING. AP_HOLDS_ALL AP_HOLDS_ALL contains information about holds that you or your Oracle Payables a pplication place on an invoice. For non matching holds, there is one row for each hold placed on an invoice. For matching holds, there is one row for each hold pl aced on an invoice shipment match. An invoice may have one or more corresponding r ows in this table. Your Oracle Payables application does not pay invoices that h ave one or more unreleased holds recorded in this table. This table holds inform ation referenced by the Invoice Holds window. In the strictest sense, AP_HOLDS_A LL has no primary key. It is possible for your Oracle Payables application to pl ace a certain type of hold on an invoice, then release it, then place another ho ld of the same type (if data changes before each submission of Approval), which would result in a duplicate primary key. But for practical purposes, the primary key is a concatenation of INVOICE_ID, LINE_LOCATION_ID,and HOLD_LOOKUP_CODE. AP_AE_LINES_ALL An accounting entry line is an entity containing a proper accounting entry with debits or credits both in transaction currency as well as functional currency al ong with an account and other reference information pointing to the transaction

data that originated the accounting entry line. An accounting entry line is grou ped with other accounting entry lines for a specific accounting entry header. An y such group of accounting entry lines should result in balanced entries in the functional currency. AP_AE_HEADERS_ALL An accounting entry header is an entity grouping all accounting entry lines crea ted for a given accounting event and a particular set of books. An accounting en try header can either be transferred over to GL or not at all. That is, either a ll its accounting entry lines are transferred or none at all. The transferred to GL status is marked in the GL_TRANSFER_FLAG. Possible values for GL_TRANSFER_FL AG are Y, N, or E. Y indicates that the accounting entry header has been transfe rred to GL. N indicates that the accounting entry header has not been transferre d to GL due to 2 possible reasons: either the transfer process has not run or it has run but the accounting entry had an accounting error on it. E indicates tha t an error was encountered during the transfer to GL process.