Search Results ic_adjs_jnl_vw
Overview
IC_ADJS_JNL_VW is an Oracle EBS database view owned by the APPS schema, defined within the GMI (Process Manufacturing Inventory) product family. It presents inventory adjustment journal data by joining journal header, journal detail, item master, lot, warehouse, location, reason code, grade, and accounting information into a single denormalized result set. The view carries a VALID status and is documented in ETRM for both EBS 12.1.1 and 12.2.2.
This view is commonly used in reporting and integration scenarios where adjustment transactions must be extracted together with their descriptive context. Rather than resolving foreign keys manually across the numerous Process Manufacturing tables, developers and report authors query IC_ADJS_JNL_VW to retrieve adjustment lines already enriched with item numbers, descriptions, warehouse names, lot attributes, reason descriptions, and accounting unit details.
Underlying Base Objects
The view is defined over a set of Process Manufacturing synonyms and supporting reference objects. The key documented base objects are:
- IC_ADJS_JNL — the primary adjustment journal detail source (aliased D in the view text, with the TO_ columns drawn from an aliased E).
- IC_JRNL_MST — journal master header data (aliased M).
- IC_ITEM_MST — item master attributes (aliased I).
- IC_LOTS_MST — lot and sublot information (aliased L).
- IC_LOTS_STS — lot status descriptions (aliased LD, LE).
- IC_WHSE_MST — warehouse master (aliased WD, WE).
- IC_LOCT_MST — location master (aliased LOD, LOE).
- QC_GRAD_MST — quality control grade descriptions (aliased QD, QE).
- SY_REAS_CDS — reason code lookup supplying REASON_TYPE and the documented reason description column (aliased R).
- SY_ORGN_MST — organization master (aliased O).
- GL_ACCT_MST, GL_ACCU_MST, GL_PLCY_MST — accounting account and accounting unit sources (aliased AC, A).
- SY_DOCS_SEQ — document sequence support.
- FND_PROFILE — used to resolve the IC$DEFAULT_LOCT profile value in the LOCATION and LOCT_DESC DECODE expressions.
Key Columns
The view exposes a wide set of adjustment attributes. Frequently referenced columns include:
- ORGN_CODE, JOURNAL_NO, JOURNAL_ID, POSTED_IND, DELETE_MARK, JOURNAL_COMMENT — journal identification and status.
- TRANS_TYPE, DOC_ID, LINE_TYPE, LINE_ID, DOC_LINE, DOC_DATE, COMPLETED_IND — adjustment line identity and timing.
- REASON_CODE, REASON_TYPE, REASON_DESC1 — reason code lookup attributes. REASON_DESC1, the column most often searched by users, provides the human-readable reason description associated with the adjustment.
- ITEM_ID, ITEM_NO, ITEM_DESC1, DUALUM_IND, LOT_CTL, SUBLOT_CTL, ITEM_LOCT_CTL, STATUS_CTL, GRADE_CTL, LOT_INDIVISIBLE — item master controls.
- LOT_ID, LOT_NO, SUBLOT_NO, LOT_DESC, LOT_STATUS, STATUS_DESC, QC_GRADE, QC_GRADE_DESC — lot, sublot, status, and grade data for both source and destination.
- WHSE_CODE, WHSE_NAME, LOCATION, LOCT_DESC and their TO_ counterparts — from/to warehouse and location details.
- QTY, QTY2, TO_QTY, TO_QTY2, ITEM_UM, ITEM_UM2 — adjustment quantities and units of measure.
- ACCTG_UNIT_ID, ACCTG_UNIT_NO, ACCTG_UNIT_DESC, ACCT_ID, ACCT_NO — accounting integration attributes.
Common Use Cases and Queries
Typical usage includes adjustment audit reports, reason code analysis, inventory reconciliation extracts, and integrations that feed downstream costing or accounting systems. A common query filters on reason description and posted status:
- SELECT JOURNAL_NO, DOC_DATE, ITEM_NO, ITEM_DESC1, WHSE_CODE, QTY, REASON_CODE, REASON_DESC1 FROM APPS.IC_ADJS_JNL_VW WHERE REASON_DESC1 = 'Cycle Count Adjustment' AND POSTED_IND = 'Y';
- SELECT REASON_CODE, REASON_DESC1, COUNT(*) FROM APPS.IC_ADJS_JNL_VW GROUP BY REASON_CODE, REASON_DESC1;
- SELECT JOURNAL_NO, ITEM_NO, LOT_NO, QTY, ACCT_NO FROM APPS.IC_ADJS_JNL_VW WHERE ACCTG_UNIT_NO = :p_acct_unit;
Because the view joins numerous master tables, queries should be filtered by organization, date range, or journal identifiers to maintain acceptable performance on larger installations.
-
View: IC_ADJS_JNL_VW
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:GMI.IC_ADJS_JNL_VW, object_name:IC_ADJS_JNL_VW, status:VALID, product: GMI - Process Manufacturing Inventory , description: Inventory Adjustment Journal view , implementation_dba_data: APPS.IC_ADJS_JNL_VW ,
-
View: IC_ADJS_JNL_VW
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:GMI.IC_ADJS_JNL_VW, object_name:IC_ADJS_JNL_VW, status:VALID, product: GMI - Process Manufacturing Inventory , description: Inventory Adjustment Journal view , implementation_dba_data: APPS.IC_ADJS_JNL_VW ,
-
SYNONYM: APPS.GL_ACCU_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:GL_ACCU_MST, status:VALID,
-
SYNONYM: APPS.GL_ACCT_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:GL_ACCT_MST, status:VALID,
-
12.1.1 FND Design Data
12.1.1
-
SYNONYM: APPS.IC_ADJS_JNL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IC_ADJS_JNL, status:VALID,
-
SYNONYM: APPS.SY_REAS_CDS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:SY_REAS_CDS, status:VALID,
-
SYNONYM: APPS.SY_DOCS_SEQ
12.2.2
owner:APPS, object_type:SYNONYM, object_name:SY_DOCS_SEQ, status:VALID,
-
12.2.2 FND Design Data
12.2.2
-
SYNONYM: APPS.GL_ACCU_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:GL_ACCU_MST, status:VALID,
-
SYNONYM: APPS.GL_ACCT_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:GL_ACCT_MST, status:VALID,
-
SYNONYM: APPS.QC_GRAD_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:QC_GRAD_MST, status:VALID,
-
SYNONYM: APPS.SY_DOCS_SEQ
12.1.1
owner:APPS, object_type:SYNONYM, object_name:SY_DOCS_SEQ, status:VALID,
-
SYNONYM: APPS.QC_GRAD_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:QC_GRAD_MST, status:VALID,
-
SYNONYM: APPS.IC_JRNL_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IC_JRNL_MST, status:VALID,
-
SYNONYM: APPS.IC_LOTS_STS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IC_LOTS_STS, status:VALID,
-
SYNONYM: APPS.GL_PLCY_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:GL_PLCY_MST, status:VALID,
-
SYNONYM: APPS.IC_ADJS_JNL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IC_ADJS_JNL, status:VALID,
-
SYNONYM: APPS.IC_JRNL_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IC_JRNL_MST, status:VALID,
-
SYNONYM: APPS.SY_REAS_CDS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:SY_REAS_CDS, status:VALID,
-
SYNONYM: APPS.IC_LOTS_STS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IC_LOTS_STS, status:VALID,
-
SYNONYM: APPS.IC_LOCT_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IC_LOCT_MST, status:VALID,
-
SYNONYM: APPS.GL_PLCY_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:GL_PLCY_MST, status:VALID,
-
SYNONYM: APPS.IC_LOCT_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IC_LOCT_MST, status:VALID,
-
SYNONYM: APPS.SY_ORGN_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:SY_ORGN_MST, status:VALID,
-
SYNONYM: APPS.SY_ORGN_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:SY_ORGN_MST, status:VALID,
-
SYNONYM: APPS.IC_LOTS_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IC_LOTS_MST, status:VALID,
-
SYNONYM: APPS.IC_WHSE_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IC_WHSE_MST, status:VALID,
-
SYNONYM: APPS.IC_LOTS_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IC_LOTS_MST, status:VALID,
-
SYNONYM: APPS.IC_WHSE_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IC_WHSE_MST, status:VALID,
-
SYNONYM: APPS.IC_ITEM_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IC_ITEM_MST, status:VALID,
-
SYNONYM: APPS.IC_ITEM_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IC_ITEM_MST, status:VALID,
-
VIEW: APPS.IC_ADJS_JNL_VW
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:GMI.IC_ADJS_JNL_VW, object_name:IC_ADJS_JNL_VW, status:VALID,
-
VIEW: APPS.IC_ADJS_JNL_VW
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:GMI.IC_ADJS_JNL_VW, object_name:IC_ADJS_JNL_VW, status:VALID,
-
eTRM - GMI Tables and Views
12.1.1
description: Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow. ,
-
eTRM - GMI Tables and Views
12.2.2
description: Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow. ,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE: APPS.FND_PROFILE
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FND_PROFILE, status:VALID,
-
PACKAGE: APPS.FND_PROFILE
12.1.1
owner:APPS, object_type:PACKAGE, object_name:FND_PROFILE, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
eTRM - GMI Tables and Views
12.2.2
description: Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow. ,
-
eTRM - GMI Tables and Views
12.1.1
description: Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow. ,