Results for “xtr_journal_entry_actions”
48 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XTR_JOURNAL_ENTRY_ACTIONS is a Treasury (XTR) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores the journal structure information that Oracle Treasury uses to generate accounting journals from deal, transaction, and settlement activity. In practical terms, each row defines a rule telling the Treasury accounting engine which action to perform, on which amount or date type, for a given deal type, and how the resulting accounting entry should be built and balanced against a General Ledger code combination.
The table resides in the XTR schema and, per the documented 12.2.2 physical definition, contains 22 columns. It is tightly coupled to Treasury's accounting rule framework, referencing GL_CODE_COMBINATIONS for account derivation and looking up amount and date semantics from the XTR_AMOUNT_TYPES, XTR_DATE_TYPES, and XTR_AMOUNT_ACTIONS reference tables. Because the table is composed almost entirely of foreign key references that together form composite business keys, the heuristic Data Vault classification mined from its foreign key structure is link. This classification should be treated as a modeling suggestion: the object behaves as an associative entity connecting deal, amount, date, action, and GL account dimensions rather than as a standalone hub or descriptive satellite.
Key Information Stored
The table's principal columns define the accounting rule and the context in which it applies:
- ACTION_CODE — identifies the journal action to be performed; combined with DEAL_TYPE and AMOUNT_TYPE, it participates in the foreign key to XTR_AMOUNT_ACTIONS and is a core business-key candidate.
- DEAL_TYPE — the Treasury deal or instrument category the rule applies to; a leading business-key column shared by multiple foreign keys.
- AMOUNT_TYPE — the amount semantics (principal, interest, and similar) to which the action applies.
- DATE_TYPE — the date semantics used to time the journal entry.
- CODE_COMBINATION_ID — the GL account combination used when the journal is generated; foreign key to GL_CODE_COMBINATIONS.
- CREDIT_OR_DEBIT — controls whether the generated line is a debit or a credit.
- COMPANY_CODE, PORTFOLIO_CODE, PRODUCT_TYPE, DEAL_SUBTYPE, PARTY_GL — qualifiers that scope the rule to a company, portfolio, product, deal subtype, or counterparty accounting context.
- GET_PRIN_CCID_FROM_DEAL, GET_INT_CCID_FROM_DEAL, GET_GL_FROM_DEAL — indicator flags determining whether the principal account, interest account, or full GL account is derived dynamically from the deal rather than from CODE_COMBINATION_ID.
- EFFECTIVE_FROM, EFFECTIVE_TO — the date range over which the rule is valid, enabling date-effective rule maintenance.
- COMMENTS, AUDIT_INDICATOR — descriptive and control attributes.
- CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — standard Oracle EBS audit columns.
No single surrogate primary key column is documented in the supplied metadata; the unique business key is formed by the composite of DEAL_TYPE, AMOUNT_TYPE, and ACTION_CODE, which is also the pattern used by the foreign keys to XTR_AMOUNT_ACTIONS.
Common Use Cases and Queries
Typical uses center on troubleshooting and auditing Treasury journal generation, and on documenting accounting rule configuration.
- Listing all active rules for a deal type within a date range:
SELECT action_code, amount_type, date_type, credit_or_debit, code_combination_id FROM xtr_journal_entry_actions WHERE deal_type = :deal_type AND SYSDATE BETWEEN effective_from AND NVL(effective_to, SYSDATE);- Joining to GL_CODE_COMBINATIONS to display the account string for each rule:
SELECT a.action_code, g.concatenated_segments FROM xtr_journal_entry_actions a, gl_code_combinations_kfv g WHERE a.code_combination_id = g.code_combination_id;- Identifying rules that derive the account from the deal rather than a fixed CCID, useful when reconciling unexpected account assignments.
- Determining debit and credit pairing for a given deal and amount type when validating that journals will balance.
Related Objects
The following objects are most significant to XTR_JOURNAL_ENTRY_ACTIONS, based on documented foreign key relationships:
- GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to resolve the accounting flexfield.
- XTR_AMOUNT_TYPES — joined on DEAL_TYPE and AMOUNT_TYPE to validate amount semantics.
- XTR_DATE_TYPES — joined on DEAL_TYPE and DATE_TYPE to validate date semantics.
- XTR_AMOUNT_ACTIONS — joined on DEAL_TYPE, AMOUNT_TYPE, and ACTION_CODE; the definitive source of valid action codes.
- Additional Treasury accounting and deal tables consume these rules at journal creation time, and the resulting entries ultimately flow to Oracle General Ledger interfaces.
-
Journal structure information that Treasury uses to create journals
-
Journal structure information that Treasury uses to create journals
-
All journal entry actions, deal type, and deal subtype combinations
APPS.XTR_JOURNAL_COMBINATIONS_V·↳ XTR_DEAL_SUBTYPES·↳ XTR_DEAL_TYPES·↳ XTR_JOURNAL_ENTRY_ACTIONS·Explore XTR module →
-
APPS.XTR_JOURNAL_ENTRY_ACTIONS_V·↳ XTR_JOURNAL_ENTRY_ACTIONS·Explore XTR module →
-
All journal entry actions, deal type, and deal subtype combinations
APPS.XTR_JOURNAL_COMBINATIONS_V·↳ XTR_DEAL_SUBTYPES·↳ XTR_DEAL_TYPES·↳ XTR_JOURNAL_ENTRY_ACTIONS·Explore XTR module →
-
APPS.XTR_JOURNAL_ENTRY_ACTIONS_V·↳ XTR_JOURNAL_ENTRY_ACTIONS·Explore XTR module →
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - XTR Tables and Views 12.1.1
Created on 29-OCT-96
-
eTRM - XTR Tables and Views 12.2.2
Created on 29-OCT-96
-
eTRM - XTR Tables and Views 12.1.1
Created on 29-OCT-96
-
eTRM - XTR Tables and Views 12.2.2
Created on 29-OCT-96
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1