Results for “project_source”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The JA_CN_JOURNAL_LINES_REQ table is a staging and temporary holding object within the Oracle E-Business Suite Asia/Pacific Localizations module (product code JA), specifically supporting the China (CN) localization requirements. It stores journal lines for the current user session, itemizing them together with information about related subsidiary accounts where applicable. The table serves as an intermediate repository during the creation, validation, and reporting of journal entries, allowing the Chinese localization processes to assemble detailed line-level data—including account segment breakdowns, project and third-party attributions, and currency conversion details—before those lines are committed to the general ledger or consumed by downstream statutory reporting.

The object resides in the JA schema and is documented as VALID at release levels 12.1.1 and 12.2.2. The documented physical schema contains 74 columns. From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone, meaning it participates in no foreign-key relationships to other tables except for a single reference from LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES. In Data Vault terms this suggests the table behaves less like a conventional satellite and more like a self-contained transaction or staging hub, since its key structure is not decomposed into referenced hubs and links. Analysts should therefore treat it as a transient work table rather than a durable master or transactional entity.

Key Information Stored

Although the table comprises 74 columns, the most significant attributes cluster into identification, accounting, and attribution groups.

• Identification and context: JE_HEADER_ID, JE_LINE_NUM, JOURNAL_NUMBER, LINE_NUMBER, JE_CATEGORY, PERIOD_NAME, and DEFAULT_EFFECTIVE_DATE anchor each row to a journal header and accounting period.
• Ledger and entity: SET_OF_BOOKS_ID and LEDGER_ID identify the ledger, while LEGAL_ENTITY_ID is the single documented foreign key, referencing FV_LEGAL_ENTITIES. This is the principal business-key candidate linking journal lines to a legal entity.
• Accounting amounts: ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, and ACCOUNTED_CR capture the debit and credit values in both entered and functional currencies.
• Account flexfield: CODE_COMBINATION_ID plus the full range SEGMENT1 through SEGMENT30, alongside convenience columns COMPANY_SEGMENT, ACCOUNT_SEGMENT, and COST_CENTER.
• Currency conversion: CURRENCY_CODE, CURRENCY_CONVERSION_RATE, and CURRENCY_CONVERSION_TYPE.
• Project and third-party attribution: PROJECT_ID, PROJECT_NUMBER, PROJECT_SOURCE, THIRD_PARTY_ID, THIRD_PARTY_NUMBER, THIRD_PARTY_TYPE, PERSONNEL_ID, and PERSONNEL_NUMBER.
• Audit and workflow: STATUS, POPULATE_CODE, REQUEST_ID, the standard CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN columns, plus journal lifecycle columns such as JOURNAL_CREATED_BY, JOURNAL_APPROVER, JOURNAL_POSTED_BY, and JOURNAL_POSTER.

The metadata does not document a formal primary key or unique index; the surrogate identifier is typically derived from the combination of JE_HEADER_ID and JE_LINE_NUM (or LINE_NUMBER), which functions as the practical business key.

Common Use Cases and Queries

The table is most commonly accessed during localization reporting and diagnostic reconciliation of journal data prior to posting. Typical use cases include verifying that entered and accounted amounts balance within a session, auditing third-party and project attributions, and confirming currency conversion values for foreign-currency journals. A representative query retrieves all lines for a given legal entity and period:

• SELECT je_header_id, je_line_num, journal_number, account_segment, entered_dr, entered_cr, accounted_dr, accounted_cred FROM ja.ja_cn_journal_lines_req WHERE legal_entity_id = :entity_id AND period_name = :period;
• Balancing check: SELECT SUM(entered_dr) - SUM(entered_cr) FROM ja.ja_cn_journal_lines_req WHERE je_header_id = :header_id;
• Status-driven listing: SELECT * FROM ja.ja_cn_journal_lines_req WHERE status = :status AND request_id = :request_id;

Because the table is session-scoped, queries should generally be filtered by REQUEST_ID or CREATED_BY to avoid retrieving stale rows from prior runs.

Related Objects

• FV_LEGAL_ENTITIES — referenced by JA_CN_JOURNAL_LINES_REQ.LEGAL_ENTITY_ID; the sole documented foreign-key relationship.
• GL_JE_HEADERS and GL_JE_LINES — the general ledger targets that consume prepared journal data; joined via JE_HEADER_ID and line numbers.
• GL_CODE_COMBINATIONS — referenced through CODE_COMBINATION_ID for account validation.
• GL_LEDGERS / GL_SETS_OF_BOOKS — resolved via LEDGER_ID and SET_OF_BOOKS_ID.
• FND_CONCURRENT_REQUESTS — tied through REQUEST_ID for session traceability.
• JA_CN_JOURNAL_HEADERS-style companion objects and JA localization report programs that read this staging table during Chinese statutory journal generation.