Search Results retro_details_incomplete

Overview

XTR_STREAMLINE_P is the core PL/SQL package in the Oracle E-Business Treasury Management (ETRM) module responsible for orchestrating the revaluation, retroactive testing, accrual, journal generation, and journal transfer event lifecycle. It encapsulates the business logic that moves exposure and hedge data through the ETRM processing pipeline, from rate generation through final transfer of accounting journals to the General Ledger. The package is owned by APPS and classified as OTHER in the ETRM 12.2.2 metadata, indicating it is not a formal public API but rather a supporting engine invoked internally by ETRM forms and concurrent programs.

The package defines a set of module-level constants that mirror the processing model: event codes such as C_RATES, C_REVAL, C_RETROET, C_ACCRUAL, C_JOURNAL, C_GENERATE, and C_TRANSFER, and process option codes such as C_PROCESS_REVAL ('10REVAL'), C_PROCESS_RETROET ('20RETROET'), C_PROCESS_ACCRUAL ('30ACCRUAL'), C_PROCESS_JOURNAL ('40JRNLGEN'), and C_PROCESS_TRANSFER ('50JRNLXFER'). It also defines company parameter codes C_REVAL_PARAM ('ACCNT_BPSTP') and C_RETRO_PARAM ('ACCNT_BTEST'), which reference the XTR_COMPANY_PARAMETERS table. For the user query "p_company," the relevant touchpoints are CHK_ELIGIBLE_COMPANY and the company parameter constants, which drive company-level eligibility and configuration checks.

Key Procedures and Functions

The documented procedures and functions (29 total) span several functional categories:

• Eligibility and validation: CHK_ELIGIBLE_COMPANY validates whether a given company is eligible for streamline processing. REVAL_DETAILS_INCOMPLETE and RETRO_DETAILS_INCOMPLETE check for incomplete revaluation and retroactive detail records, respectively. GET_PARTY_CREATED_ON retrieves a party's creation date for eligibility or dating logic.
• Event state management: EVENT_EXISTS checks whether an event is already defined; EVENT_AUTHORIZED determines whether an event has been authorized; GET_EVENT_STATUS returns the current status of an event.
• Batch control: LOCK_BATCH and LOCK_EVENT provide concurrency control by locking batch and event records. GET_PREV_NORMAL_BATCH and GET_LATEST_BATCH retrieve prior normal batches and the most recent batch for a given scope.
• Generation and authorization: GENERATE_REVAL_RATES and GENERATE_REVAL_DETAILS produce revaluation rates and detail rows; AUTHORIZE_REVAL_EVENT authorizes the revaluation event. Similarly, GENERATE_RETRO_DETAILS and AUTHORIZE_RETRO_EVENT handle retroactive testing; GENERATE_ACCRUAL_DETAILS and AUTHORIZE_ACCRUAL_EVENT handle accruals; GENERATE_JOURNAL_DETAILS builds journal entries; and TRANSFER_JOURNALS moves journals downstream (typically to GL).

Tables Accessed

The package reads and writes several ETRM base tables through APPS synonyms. XTR_COMPANY_PARAMETERS holds company-level settings such as C_REVAL_PARAM and C_RETRO_PARAM, which the eligibility and generation logic depends on. XTR_BATCHES and XTR_BATCH_EVENTS store batch and event headers, supporting batch locking and latest/previous batch lookups. XTR_REVALUATION_DETAILS and XTR_REVALUATION_RATES persist revaluation detail rows and rate data produced by the generation procedures. XTR_ACCRLS_AMORT stores accrual and amortization records, while XTR_HEDGE_RETRO_TESTS holds retroactive test results. XTR_PARTY_INFO supplies counterparty data used by GET_PARTY_CREATED_ON. Together these tables form the working set for the end-to-end streamline process.

Usage Notes

XTR_STREAMLINE_P is typically invoked by ETRM concurrent programs and forms that drive the Streamline process, such as those that generate revaluation, retroactive, accrual, and journal events and subsequently transfer journals to the General Ledger. It is not documented as referenced by other packages, reinforcing its role as a leaf-level implementation package rather than a reusable API. Custom code should generally avoid calling it directly; instead, organizations should rely on the standard concurrent programs that wrap it. Because the package writes to persistent ETRM tables, direct invocation requires careful transaction and locking discipline, particularly around LOCK_BATCH and LOCK_EVENT, and appropriate module and company context. For company-specific behavior, the C_REVAL_PARAM and C_RETRO_PARAM values in XTR_COMPANY_PARAMETERS, checked in part via CHK_ELIGIBLE_COMPANY, govern eligibility and processing options.