The join relationship with GL tables and XLA (SubLedger Accounting) tables
詳細
1.関連テーブルの接続関係:
GL_JE_BATCHES (je_batch_id) => GL_JE_HEADERS (je_batch_id);
GL_JE_HEADERS (je_header_id) => GL_JE_LINES (je_header_id);
GL_JE_LINES (je_header_id, je_line_num) => GL_IMPORT_REFERENCES (je_header_id, je_line_num) ;
GL_IMPORT_REFERENCES (gl_sl_link_table, gl_sl_link_id) => XLA_AE_LINES (gl_sl_link_table, gl_sl_link_id) ;
XLA_AE_LINES (application_id, ae_header_id) => XLA_AE_HEADERS (application_id, ae_header_id) ;
XLA_AE_HEADERS (application_id, event_id) => XLA_EVENTS (application_id, event_id);
XLA_EVENTS (application_id, entity_id) => XLA.XLA_TRANSACTION_ENTITIES (application_id, entity_id);
2.AP仕訳遡及
APデータについてxlaを見つけます.xla_transaction_entities表の記録後は、(1)のように分けて遡る必要がある.entity_codeはTRANSACTIONSとBILLS_RECEIVABLEの場合、表のフィールドsource_id_int_1対応はra_customer_trx_allテーブルのcustomer_trx_id; フィールドsecurity_id_int_1対応はorg_id (2). entity_コードがADJUSTMENTSの場合、表のフィールドsource_id_int_1対応はar_adjustments_allテーブルのadjustment_id; フィールドsecurity_id_int_1対応はorg_id (3). entity_codeがRECEIPTSの場合、表中のフィールドsource_id_int_1対応はar_cash_receipts_allテーブルのcash_receipt_id; フィールドsecurity_id_int_1対応はorg_id (4). entity_codeはTHIRD_PARTY_MERGEの場合は総勘定に転送されないので遡及はありません.*/
The real tables (they're infact views) which store this information are :Oracle Payables :-----------------XLA_AP_INV_AEL_GL_V - Payable invoice entries (Gen. Ledger)XLA_AP_INV_AEL_SL_V - Payable invoice entries (Subledger)XLA_AP_PAY_AEL_GL_V - Payment voucher entries (Gen.Ledger)XLA_AP_PAY_AEL_SL_V - Payment voucher entries (Subledger)Oracle Receivables :--------------------XLA_AR_ADJ_AEL_SL_V - AR adjustment entries (Subledger)XLA_AR_INV_AEL_SL_V - AR invoices (Sugledger)XLA_AR_REC_AEL_SL_V - AR receipts (Subledger)XLA_AR_ADJ_AEL_GL_V - AR adjustment entries (Gen.Ledger)XLA_AR_INV_AEL_GL_V - AR invoices (Gen.Ledger)XLA_AR_REC_AEL_GL_V - AR receipts (Gen.Ledger)For the rest of the modules, you can check out the XLA% views or synonyms in APPS schema.The form. displays information from these views/synonyms and in the Record History, shows it as XLA_AEL_GL_V
1.関連テーブルの接続関係:
GL_JE_BATCHES (je_batch_id) => GL_JE_HEADERS (je_batch_id);
GL_JE_HEADERS (je_header_id) => GL_JE_LINES (je_header_id);
GL_JE_LINES (je_header_id, je_line_num) => GL_IMPORT_REFERENCES (je_header_id, je_line_num) ;
GL_IMPORT_REFERENCES (gl_sl_link_table, gl_sl_link_id) => XLA_AE_LINES (gl_sl_link_table, gl_sl_link_id) ;
XLA_AE_LINES (application_id, ae_header_id) => XLA_AE_HEADERS (application_id, ae_header_id) ;
XLA_AE_HEADERS (application_id, event_id) => XLA_EVENTS (application_id, event_id);
XLA_EVENTS (application_id, entity_id) => XLA.XLA_TRANSACTION_ENTITIES (application_id, entity_id);
2.AP仕訳遡及
APデータについてxlaを見つけます.xla_transaction_entities表の記録後は、(1)のように分けて遡る必要がある.entity_codeはTRANSACTIONSとBILLS_RECEIVABLEの場合、表のフィールドsource_id_int_1対応はra_customer_trx_allテーブルのcustomer_trx_id; フィールドsecurity_id_int_1対応はorg_id (2). entity_コードがADJUSTMENTSの場合、表のフィールドsource_id_int_1対応はar_adjustments_allテーブルのadjustment_id; フィールドsecurity_id_int_1対応はorg_id (3). entity_codeがRECEIPTSの場合、表中のフィールドsource_id_int_1対応はar_cash_receipts_allテーブルのcash_receipt_id; フィールドsecurity_id_int_1対応はorg_id (4). entity_codeはTHIRD_PARTY_MERGEの場合は総勘定に転送されないので遡及はありません.*/
The real tables (they're infact views) which store this information are :Oracle Payables :-----------------XLA_AP_INV_AEL_GL_V - Payable invoice entries (Gen. Ledger)XLA_AP_INV_AEL_SL_V - Payable invoice entries (Subledger)XLA_AP_PAY_AEL_GL_V - Payment voucher entries (Gen.Ledger)XLA_AP_PAY_AEL_SL_V - Payment voucher entries (Subledger)Oracle Receivables :--------------------XLA_AR_ADJ_AEL_SL_V - AR adjustment entries (Subledger)XLA_AR_INV_AEL_SL_V - AR invoices (Sugledger)XLA_AR_REC_AEL_SL_V - AR receipts (Subledger)XLA_AR_ADJ_AEL_GL_V - AR adjustment entries (Gen.Ledger)XLA_AR_INV_AEL_GL_V - AR invoices (Gen.Ledger)XLA_AR_REC_AEL_GL_V - AR receipts (Gen.Ledger)For the rest of the modules, you can check out the XLA% views or synonyms in APPS schema.The form. displays information from these views/synonyms and in the Record History, shows it as XLA_AEL_GL_V