This action might not be possible to undo. Are you sure you want to continue?
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.
This can happen only if your user profile option MULTIPLE_RATES_PER_JE is Yes . Also. Other values of statu s indicate an error condition. the journal entry name and description. P for posted. then BUDGET_VERSION_ID is required. then ENCUMBRANCE_TYPE_ID is required. An account s year to date balance is calculated as BEGIN_BALANCE_DR BEGIN_BALANCE_CR + PERIOD_NET_DR PERIOD_NET_CR. STATUS is U for unposted. Detail and summary foreign currency balances that are the result of posted foreign currency journal entries have TRANSLATED_FLAG s et to R . Segment values are stored in the S EGMENT columns. Y indicates that the translation is current. GL_CODE_COMBINATIONS Stores valid account combinations foreach Accounting Flexfield structure within your Oracle General Ledger application. Other statuses indicate that an error c ondition was found. sta tus. For foreign currency rows. and statistical balanc es for each accounting period that has ever been opened. the SEGMENT columns that are used are not guaranteed to be in any order. to indicate that the row is a candidate for revaluation. BALANCING_SEGMENT_VALUE is null if there is only one balancing segment value in your journal entry. or encumbrance balances. the REVALUATION_ STATUS column is notused. In this case. GL_BALANCES Stores actual. 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. including whether the account is enabled. All summary account balances have TEMPLA TE_ID not NULL. Summary accounts have SUMMARY_FLAG = Y and TEMPLATE_ID not NUL . or E for actual. GL_JE_BATCHES Stores journal entry batches. Associated with each account are certain codes and flags.. STATUS is U for unposted. the account needs to e re translated). Note that each Accounting Flexfield structure may use different SEGMENT columns within the table to store the flexfield value combination. the begin balance and period net columns contain the foreign currency balance. There is a one to many relationship between journal entry ba tches and journal entries. Detail foreign currency balances that are the result of foreign currency translation have TRANSLATED_FLAG set to Y or N . The table stores the period beginning balances in BEGIN_BALANC E_DR and BEGIN_BALANCE_CR. budget. whether detail posti ng ordetail budgeting is allowed. budget.e. Moreo ver. respect vely. The posting program changes STATUS_VERIFIED to I when posting is in process and Y af ter posting is complete. This table corresp onds to the Batch window of the Enter Journals form. I for in the process of being posted. Each row in this table includes the associated batch ID. and other information about the jour nal entry. This table stores functional currency. GL_BALANCES stores period activity for an account in the PERIOD_NET_DR and PERIO D_NET_CR columns. If ACTUAL_FLAG is B . description. P for posted. Summary foreign currency balances that are the result of foreign currency transl ation have TRANSLATED_FLAG set to NULL. If there is more than one. foreign currency. Each row includes the batch name. and other information. 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. ACTUAL_FLAG is either A . and others.GL_JE_HEADERS Stores journal entries. S for selected. the posting program does not re convert your foreign amount s. STATUS_VERIFIED is N when you create or modify an u nposted journal entry batch. BALANCING_SEGMENT_VALUE is the gr eatest balancing segment value in your journal entry. and encumbrance balances for detail and summary accounts. If ACTUAL_FLAG is E . The columns that end in ADB are not used. while the begin balance and period net BEQ columns con tain the converted functional currency balance. N indicates that the translation is out of date (i. running total debits and credits. B . This table corresponds to the Journals window of the Enter Journals f orm.
REMIT_TO_ADDRESS_ID. PRINTING_PENDING.L. and commit ment lines. and printing instructions. QUANTITY_INVOICED stores the amount of produc t invoiced. credit memo. RA_CUSTOMER_TRX_ALL This table stores invoice. Oracle Receivables stores the customer transaction identifier of the commitment in INITIAL_CUSTOMER_TRX_ID. debit memo. except on account credits which are not related to specific invoices/invoice l ines at creation time. and commitment lines are distinguished by the transaction type of the corr esponding RA_CUSTOMER_TRX_ALL record. Oracle Receivables creates your payment schedules and updates any commitments against this invoice. debit memos. SHIP_TO_SITE_USE_ID. credit memos. Each row includes general invoice information such as customer. For example. debit memo. will not have values in this column. BILL_TO_CUSTOMER_ID. debit memo. If you created an i nvoice against a commitment. credit memo. and INVOICE_CURRENCY_CODE are required even though they are null allowed. and a sales tax record must exist for each line. For invoices imported through AutoInvoice. PRIMARY_SALES_REP_ID. transacti on type. revenue records must exist for eac h line and add up to the line amount. and credit memo header inform ation. Invoices. credit memos are required to have a value in PREVIOUS_CUSTOMER_TRX_LINE_ID . QUANTITY_ORDERED sto res the amount of product ordered. otherwise it is null. Invoice. commitment. which are not related t o any invoice at creation. PRINTING_OPTION. PREVIOUS_CUSTOMER_TRX_ID stores the customer transaction identifier of the invoice you credited. QUANTITY_ORDERED and QUANTI TY_INVOICED must be the same. You need one row for each line. Required Columns: SOLD_TO_CUSTOMER_ID. TERM_ID. debit mem o. and credit memo you create in Oracle Receivables. Before an invoice can be compl eted. The primary key for this table i s CUSTOMER_TRX_ID. QUANTITY_ORDERED and QUANTITY_INVOICE D can be different. PREVIOUS_CUSTOMER_TRX_ID is null. RA_CUSTOMER_TRX_LINES_ALL This table stores information about invoice. BILL_TO_SITE_USE_ID. QUANTITY_CREDITED stores the amo . 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 N and TEMPLATE_ID NULL. commitment. an invoice can have one line for Product A and another line for Product B. C OMPLETE_FLAG stores Y for Yes and N for No to indicate if your invoice is complete. it must have at least one invoice line. For invoices entered through the window. SOLD_TO_SITE_USE_ID. If you entered a credit m emo. If you enter a credit memo. When you complete an invoice. You need one row for each invoice. and commitments are all distinguished by th eir transaction types stored in RA_CUST_TRX_TYPES_ALL. Also. In the case of on account credits.
Use LATEST_REC_FLAG to join to the later of the two rows. credit memo. and UNIT_SELLING_PRICE are required ev en though they are null allowed. credit memos (CM). and receipts (PMT). UOM_CODE stores the unit of measure code as defined in MTL_UNITS_OF_MEASURE. If your AutoAccounting is unable to complete your general ledger default account s using the AutoAccounting rules you define. A line_type of CB is created for a Chargeback line. If you are importing a transaction through AutoInvoice and the general ledger date of your transaction is in a closed accou nting period. Oracle Receivables updates this table when activity occurs against an inv oice. Instead.unt of product credited. CHARGES works just like the LINE type. For invoices with rules. The primary key for this table is CUST_TRX_LINE_GL_DIST_ID. ACCO UNT_CLASS defines which type of distribution row you are on. ACCOUNT_SET_FLAG is Y if this row is part of an account set. Transaction classes determine which columns in this table Oracle Receivables upd ates when a transaction occurs. UNIT_STANDARD_PRICE stores the list price per unit for thi s transaction line. unearned revenue and unbil led receivables for each invoice or credit memo line. debit memo. Oracle Receivables uses this information to post the proper amounts to your general ledger. For transactions imported through AutoInvoice. 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).COMPLETE_FLAG = Y). RA_CUST_TRX_LINE_GL_DIST_ALL This table stores the accounting records for revenue.UOM_CODE. on account credit. TAXING_RULE. Oracle Receivables groups different transactions bythe column CLASS. and whether a transaction relates to either the . QUANTI TY_ORDERED. If your invoice or credit memo has a transaction type where Post to GL is set to No. the distributions are not created when the invoice is i nitially created. AutoInvoice uses the general ledger date of the first open account ing period and stores the original general ledger date in ORIGINAL_GL_DATE. The ACCOUNT_CLASS REC represents the receivable account and is for the total amo unt of the invoice. 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. 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. debit memos(DM). there must be at least one row in the table RA_CUST_TRX_LINE_GL_DIST (which stores accounti ng information). incomplete general ledger accounts are stored in CONCATENATED_SEGMENTS. AR_PAYMENT_SCHEDULES_ALL This table stores all transactions except adjustments and miscellaneous cash rec eipts. or receipt. You must have at least one (b ut you can have multiple) accounting distributions for each invoice or credit me mo line. The primary key for this tabl e is CUSTOMER_TRX_LINE_ID. depos its (DEP). There can be at most two REC rows. An account set is a set of rows that represent a model distr ibution. the invoices are created when the Revenue Recognition program is run.chargebacks (CB). TAX signifies that this is a tax line. Each row includes the GL a ccount and the amount of the accounting entry. chargeback. LINE_TYPE differentiates between the different types of lines that are stored in this table. Account sets are used for invoices with rules. 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. These classes inc lude invoice (INV). LINE points to regular invoice lines that normally refer to an item . DESCRIPTION. even for non postable transactions. For every row in this table that belongs to a complete transaction (where RA_CUSTOMER_TRX. UNIT_STANDARD_PRICE. guarantees (GUAR). Oracle Receivables assigns Null to GL_DATE. The AMOUNT column in this table i s required even though it is null allowed. UNIT_STANDARD _PRICE and UNIT_SELLING_PRICE can be different. UNIT_SELLING_PRICE stores the selling price per unit for thi s transaction line. One that has a ACCOUNT_SE T_FLAG set to Y and the other has ACCOUNT_SET_FLAG set to N. You need one row for each accounting distribution.
If your type is Miscellaneous Cash. UNAPP. debit memos. debit me mos. AR_PAYMENT_SCHEDULES_ALL joins to the AR_CASH_RECEIPTS_ALL table for invoice related payment transactions using the foreign key CASH_RECEIPT_ID. which identifies the transaction that created the row. You use your receivables activities to s peed receipt entry and generate finance charges. Miscellaneous Cash. all of these references were in AR_BATCH_SOURCES. AR_RECEIVABLE_APPLICATIONS_ALL This table stores all accounting entries for your cash and credit memo applicati ons. For a receipt. STATUS changes from OP to CL for any transaction that has an AMOUNT_DUE_REMAINING value of 0(Zero). Fo r invoices with split terms. The primary key for this table is RECEIVABLES_TRX_ID. DUE_DATE and AMOUNT_DUE_REMAINING can differ for each installm ent of a split term invoice. chargebacks. 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. 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. receipts can be confir med or not confirmed as designated by the CONFIRMED_FLAG column. The aging reports al so utilize the current balances in AMOUNT_DUE_REMAINING to display outstanding a mounts for current and overdue debit items. invoices. and Finance Charg es. chargebacks. ASSOCIATED_CASH_RECEIPT_ID is the cash receipt of the payment you entered when you created the chargeback in this window. ACTUAL_DATE_CLOSED and GL_DATE_CLOSED are populated with the date of the latest transaction. AR_RECEIVABLES_TRX_ALL This table links accounting information with your Receivables Activities. Oracle Rece ivables uses one row for each activity. and UNI D. Possible statuses of your applications include APP. When a receiptis applied. then this colu mn indicates the credit balance amount currently available for this customer. If this amount is negative. The prim ary key for this table is PAYMENT_SCHEDULE_ID. Ora cle Receivables creates a new payment schedule record when you create a chargeba ck in the Receipts window. GL_DATE_CLO SED indicates the general ledger date on which your transaction was closed. or depos its. This column identifies which transactions Oracle Receivables selects when it dis plays current and overdue debit items in the aging reports. the amount due remaining includes on account and una pplied amounts. Each installment is differentiated by the TERMS_SEQ UENCE_NUMBER column. status. In AR_PAYME NT_SCHEDULES_ALL. 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. they are now in AR_RECEIPT_METHOD_ ACCOUNTS_ALL. you can associate either a distribution set or a standard accounting flexfield to your Receivables Activity. one record is created in RA_CUSTOMER_TRX_ALL and on e record is stored in AR_PAYMENT_SCHEDULES_ALL for each installment. 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. and guarantees as positive numbers in the AMOUNT_DUE _REMAINING and AMOUNT_DUE_ORIGINAL columns. In Release 9. ACC. STATUS and AMOUNT_DUE_REMAINING. Each row includes the amount applied. Oracle Receivables stores debit items such as invoices. The sum of the AMOUNT_DUE_REMAINING column for a customer for all confirmed payment schedules r eflects the current customer balance. You use this information to determine the applications of your payments or cr . In Release 10. AR_PAYMENT_SCHEDULES_ALL uses the foreign key CUSTOMER_TRX_ID to join to the RA_ CUSTOMER_TRX_ALL table for these transactions.RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALLtable. Oracle Receivables updat es AMOUNT_APPLIED. If you create a debit memo reversal when you reverse a receipt. deposits. Credit items such as credit memos an d receipts are stored as negative numbers. and accounting flexfield info rmation. Possib le types of activities include Adjustment.
For example. APPLIED_PAYMENT_SCHEDULE_ID and APPLIED_CUSTOMER _TRX_ID for this record belong to the invoice that is receiving the application. APPLIED_CU STOMER_TRX_ID and APPLIED_PAYMENT_SCHEDULE_ID identify the invoice or credit mem o that receives the application. The STATUS of a receivable application determines which fle xfield account Oracle Receivables uses. 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. if you enter a cash receipt of $500 as Unidentified. 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. on the other hand. The primary key for this table is RECEIVABLE_APPLICATION_ID. Payables 1234AP_INVOICES_ALL AP_INVOICE_DISTRIBUTIONS_ALL AP_PAYMENT_SCHEDULES_ALL AP_HOLDS_ALL . Oracle Recei vables uses the foreign key CODE_COMBINATION_ID to associate this payment with t he Unidentified flexfield account. CASH applications represent applications of a cash receipt. which uniquely identifi es the transaction that created the row. The corresponding UNAPP rows is alsocreated which will have a positive amount (the same amount as the application being reversed). do not have rows of status UNAPP. Ifyou reverse a ca sh application. A negative value in AMOUNT_APPL IED becomes a debit. CODE_COMBINATION_ID stores va lid Accounting Flexfield segment value combinations that will be credited in the General Ledger when this application is posted. If you apply a credit memo against the invoice. If you combine an on account credit and a receipt. If the cash receipt is not confirmed. a row with status APP with the inverse amount of the original ap plication (i. The CASH_RECEIPT_ID and the PAYMENT_SCHEDULE_ID of this record identif y the receipt you are applying. Oracle Receivables creates a record in the AR_RECEIVABLE_APPLICATIONS_A LL table. 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. a row is created in this table that has a status of UNAPP for the amount of the cash receipt. CM appl ications. There are two kinds of applications: CASH and CM (for credit memo applications).edit memos. and PAYMENT _SCHEDULE_ID identify the transaction that you are actually applying.e. 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. CASH_RECEIPT_ID stores the cash receipt identifier of th e receipt you entered. if you apply a receipt against an invoice. the applications of that receipt are not r eflected in the payment schedule of the transaction it is applied against. When a cash receipt is initially created. 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. the negative of the original application amount) is created. CASH_RECEIPT_ID. For example. This is stored in the column APPLICATION_TYPE. 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. Oracle Receivables creates a record in theAR_RECEIVABL E_APPLICATIONS_ALL table with AMOUNT_APPLIED = 500 and STATUS = UNID . CONFIRMED_FLAG is a denormalization from AR_CASH_RECEIPTS_ALL. Oracle Receivables concurrently creates a record of this receipt in the AR_CASH_RECEIPTS_ALL table. They only use row s with a status of APP. This column is null for a credit memo application. CUSTOMER_TRX_ID.
or T. Orac le Projects sets the ASSET_ADDITION_FLAG to P when the PA_ADDITION_FLAG is set t o Y. you must interface any project related invoice distribution to Oracle Projects before you can interface it to Oracle Assets. There is a row for each invoice distribution. 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. Your Oracle Payables application se ts the ASSETS_ADDITION_FLAG to U for distributions not tested by Oracle Assets. 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. 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. 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. Th e MATCH_STATUS_FLAG indicates the approval status for the distribution. PA_ADDITION_FLAG tracks the status of project related supplier invoice dis tribution lines and expense report distribution lines. Your Oracle Payables ap plication uses the INTEREST type invoice for interest that itcalculates on invoi ces that are overdue. There is one row for ea ch invoice you enter. 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. Oracle Assets then adjusts this flag after it tests a distribution for assignmen t as an asset.5. For supplier invoice distributions entered via Oracle Payables. Z or T. When you account for an invoice. An invoice can have one or more invoice distribution lines . Invoice distributions may be interfaced over/from Oracle Assets or Oracle Projects. the PA_ADDITION_ .AP_AE_LINES_ALL 6.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. AP_INVOICE_DISTRIBUTIONS_ALL AP_INVOICE_DISTRIBUTIONS_ALL holds the distribution line information that you en ter for invoices.AP_AE_HEADERS_ALL AP_INVOICES_ALL AP_INVOICES_ALL contains records for invoices you enter. An invoice can have multiple distributio n lines. with the PA_ADDITION_FLAG set to Y. To avoid the same invoice distribution being interfaced to both Oracle Projects and Oracle Assets. If the project relat ed invoice distribution is charged to a capital project in Oracle Projects. Z . A distribution l ine must be associated with an invoice. 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. your OraclePayables application creates accounting events. An invoice can also have one or more scheduled payments. 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. Values for CASH_POSTED_FLAG may be Y if distribution has been accounted and system is set up for cash basis accounting. Oracle Assets only picks up invoice distributions with the ASSET_AD DITION_FLAG set to U and if project related. 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.
. s ee QuickCodes listing for all the errors. or P for partially paid scheduled payments. Your Oracle Payables application does not pay invoices that h ave one or more unreleased holds recorded in this table.FLAG is set to N if the distribution is project related. For expense report distribut ions interfaced from Oracle Projects to Oracle Payables via Invoice Import. AP_PAYMENT_SCHEDULES_ALL AP_PAYMENT_SCHEDULES_ALL contains information about scheduled payments for an in voice.X is the same as W for a reversal distribution line.P is the same as H for a reversal distribution line. For non matching holds. This table holds inform ation referenced by the Invoice Holds window. N for unpaid scheduled payments. they can be ignored.W indicates a regular distribution that has been encumbered in advisory mode e ven though insufficient funds existed. . It is possible for your Oracle Payables application to pl ace a certain type of hold on an invoice.H indicates a regular distribution that has not been encumbered because it was put on hold. For supplier invoice adjustment lines interfaced from Oracle Projects to Oracle Payables (which must net to zero with another lin e). . Oracle Projects sets the PA_A DDITION_FLAG to Y or Z after the item is successfully processed. which would result in a duplicate primary key. In the strictest sense. there is one row for each hold pl aced on an invoice shipment match. or may be set t o a rejection code if the line is rejected during transfer to Oracle Projects.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.D is the same as Y for a reversal distribution line. Val ues for HOLD_FLAG may be Y to place a hold on the scheduled payment. For convert ed records. this value is set to N. AP_HOLDS_ALL AP_HOLDS_ALL contains information about holds that you or your Oracle Payables a pplication place on an invoice. .Y indicates aregular distribution that has been successfully encumbered by Pay ables. there is one row for each hold placed 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. Values for PAYMENT_STATUS_FLAG may be Y for fully paid payment schedules. the primary key is a concatenation of INVOICE_ID. then place another ho ld of the same type (if data changes before each submission of Approval). AP_HOLDS_A LL has no primary key. You need one row for each time you intend to make a payment on an invoice . But for practical purposes. or N not to do so. This row is never picked up by the Interface Supplier Invoic es process based on the AP_INVOICES. then release it. the value for the PA_ADDITION_FLAG is set to T. LINE_LOCATION_ID. You must correct the rejection reason an try to retransfer the line. An invoice may have one or more corresponding r ows in this table. . . Fo r expense report adjustment lines interfaced from Oracle Projects to Oracle Paya bles which net to zero with another line.Nor null indicates a regular line that has not been encumbered because it has not been looked at yet.INVOICE_TYPE_LOOKUP_CODE = EXPENSEREPORT. Both lines are associated with the original invoice by the Oracle Projects Interface Expense Re ports to AP process. For matching holds. thisvalue is set to T. enter a value for AMOUNT_REMAINING. 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. 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 . . Values for the ENCUMBERED_FLAG are as follows: .and HOLD_LOOKUP_CODE.
An accounting entry line is grou ped with other accounting entry lines for a specific accounting entry header. That is. 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. Y indicates that the accounting entry header has been transfe rred to GL. E indicates tha t an error was encountered during the transfer to GL process. An y such group of accounting entry lines should result in balanced entries in the functional currency.data that originated the accounting entry line. The transferred to GL status is marked in the GL_TRANSFER_FLAG. N. Possible values for GL_TRANSFER_FL AG are Y. . 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. either a ll its accounting entry lines are transferred or none at all. An accounting en try header can either be transferred over to GL or not at all. or E.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.