Results for “default_loct”

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

Overview

APPS.IC_ADJS_JNL_VW is a reporting and integration view in Oracle EBS (documented for 12.2.2 and applicable to 12.1.1) that presents inventory adjustment journal activity in a fully denormalized, human-readable form. The underlying IC_ADJS_JNL table stores adjustment journal lines using only internal identifiers — item IDs, lot IDs, warehouse codes, location codes, reason codes, accounting IDs, and status/grade codes. This view resolves those identifiers against their respective master tables (items, lots, warehouses, locations, reason codes, QC grades, statuses, organizations, and accounting units) so that each adjustment line surfaces descriptive text alongside its code. Consequently, the view is the primary source for inventory adjustment inquiries, reconciliation extracts, and downstream integration feeds that require descriptive attributes rather than surrogate keys.

Underlying Base Objects

The view is defined over IC_ADJS_JNL (the adjustment journal detail) joined to IC_JRNL_MST (the journal header, supplying journal_no, posted_ind, delete_mark, posting_id, in_use, and the ten descriptive attribute1–attribute14 columns), SY_DOCS_SEQ (document sequence and transaction type/line type), and SY_ORGN_MST (organization code). Detail attributes are enriched from IC_ITEM_MST (item number, description, and control flags such as dualum_ind, lot_ctl, sublot_ctl, loct_ctl, status_ctl, grade_ctl, lot_indivisible, plus default lot status and QC grade), IC_LOTS_MST (lot number, sublot, and description), IC_WHSE_MST for both from- and to-warehouse (name, location control flag, company code), IC_LOCT_MST for from- and to-location descriptions, IC_LOTS_STS for lot status descriptions, and QC_GRAD_MST for QC grade descriptions. SY_REAS_CDS supplies reason type and description, while GL_ACCU_MST, GL_ACCT_MST, and GL_PLCY_MST provide accounting unit number/description and account number/description. FND_PROFILE is referenced as a package within the WHERE/SELECT logic via fnd_profile.value('IC$DEFAULT_LOCT'). Column default_loct relates to that profile option.

Key Columns

• From/to pairs: doc_id/line_id, line_type/to_line_type, doc_line/to_doc_line, whse_code/to_whse_code, location/to_location, item_um/to_item_um, lot_status/to_lot_status, qc_grade/to_qc_grade, and qty/to_qty — enabling join-style adjustment reporting.
• Location column with default_loct: the view uses decode(d.location, fnd_profile.value('IC$DEFAULT_LOCT'), NULL, d.location) for location, with the same pattern for loct_desc, to_location, and to_loct_desc. This means locations equal to the IC$DEFAULT_LOCT profile value are returned as NULL, and the corresponding location descriptions are nulled as well. These aliases represent the "default location" concept against which filter-based logic was applied.
• Journal context: journal_no, journal_id, posted_ind, delete_mark, print_cnt, posting_id, in_use, assignment_type, journal_comment.
• Accounting: acctg_unit_id, acctg_unit_no, acctg_unit_desc, acct_id, acct_no, and acct_no_desc.
• Descriptive flags and statuses: default_lot_status, default_qc_grade, status_desc/to_status_desc, qc_grade_desc/to_qc_grade_desc, reason_desc1/reason_type.

Common Use Cases and Queries

Typical scenarios include adjustment journal inquiry, inventory-to-GL reconciliation extracts, audit of posted vs. unposted adjustments, and integration feeds that require item/lot/warehouse descriptions. Because location is suppressed when it equals the default location, reports that must show explicit locations should query the base table or re-derive the value. A representative query joining descriptive attributes for a journal is:

SELECT journal_no, doc_date, item_no, whse_name, location, loct_desc, lot_no, qty, item_um, acct_no, reason_desc1 FROM apps.ic_adjs_jnl_vw WHERE journal_no = :p_journal_no AND posted_ind = 'Y' AND delete_mark = 0 ORDER BY doc_line;

For extracting only non-default locations, filter on the resolved columns: WHERE location IS NOT NULL. This returns rows where the location column differs from the IC$DEFAULT_LOCT profile value, which is the practical anchor for a search such as "default_loct".