Results for “source_transaction_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CRP_RESOURCE_V is an internal Oracle EBS view owned by the APPS schema within the CRP (Capacity) product module. It is documented in ETRM as a performance-oriented construct rather than a functional interface, and its status is VALID across Oracle EBS 12.1.1 and 12.2.2. The view provides a unified, consolidated result set of resource planning rows drawn from three distinct source objects, allowing capacity and material planning logic to query a single structure instead of issuing separate statements against each contributing table. Because the view is described as internal for performance, it should be treated as a supporting object rather than a supported end-user or integration interface; direct dependencies on it are typically limited to Oracle-supplied capacity planning programs and concurrent processes.
Underlying Base Objects
Per the documented view text, CRP_RESOURCE_V is defined as a UNION ALL over three referenced base objects, all resolved through SYNONYM entries in the APPS schema: CRP_RESOURCE_PLAN, MRP_SUGG_REP_SCHEDULES, and MRP_RECOMMENDATIONS.
- CRP_RESOURCE_PLAN — the primary capacity planning source, contributing resource plan rows directly (alias RES).
- MRP_SUGG_REP_SCHEDULES — supplies repetitive schedule suggestions (alias SUGG), synthesized into the unified column list.
- MRP_RECOMMENDATIONS — supplies planning recommendations (alias MR), filtered so that only rows with a disposition status other than 2, a non-null LINE_ID, and an ORDER_TYPE not in (13, 16, 4) are included.
Because the definition uses UNION ALL, duplicate rows are preserved and no distinct processing is applied. Literal substitutions are used to satisfy the shared column list for the second and third branches: TRANSACTION_ID and RESOURCE_ID receive -2 for MRP_RECOMMENDATIONS and -1 for MRP_SUGG_REP_SCHEDULES. This is directly relevant to the search term mrp_sugg_rep_schedules, which appears as one of the three documented source objects behind this view.
Key Columns
The view exposes a fixed eight-column projection. The documented columns are:
- ROW_ID — the ROWID of the originating base table row, carried through from each branch (RES.ROWID, SUGG.ROWID, MR.ROWID).
- TRANSACTION_ID — the originating transaction identifier; hard-coded to -1 for repetitive schedule suggestions and -2 for MRP recommendations.
- ORGANIZATION_ID — the inventory organization context for the planning row.
- COMPILE_DESIGNATOR — the plan or compile designator under which the row was generated.
- DEPARTMENT_ID — the department associated with the capacity row; mapped from REPETITIVE_LINE for repetitive schedules and LINE_ID for recommendations.
- RESOURCE_ID — the resource identifier; only populated from CRP_RESOURCE_PLAN, with -1 for the other two branches.
- ASSEMBLY_ITEM_ID — the assembly item; sourced from ASSEMBLY_ITEM_ID for resource plan rows and INVENTORY_ITEM_ID for the other branches.
- SOURCE_TRANSACTION_ID — the upstream transaction from which the capacity row originated.
Common Use Cases and Queries
Practical use is concentrated in capacity planning diagnostics and reconciliation. A typical query retrieves all rows for an organization and plan, using SOURCE_TRANSACTION_ID to trace how repetitive schedule and recommendation data fold into the capacity picture. Note that the negative TRANSACTION_ID sentinel values identify which underlying source produced each row.
A representative query:
SELECT transaction_id, organization_id, compile_designator, department_id, resource_id, assembly_item_id, source_transaction_id FROM apps.crp_resource_v WHERE organization_id = :org_id AND compile_designator = :designator;- To isolate repetitive schedule suggestions:
SELECT * FROM apps.crp_resource_v WHERE transaction_id = -1; - To isolate MRP recommendation rows:
SELECT * FROM apps.crp_resource_v WHERE transaction_id = -2; - To isolate native resource plan rows:
SELECT * FROM apps.crp_resource_v WHERE transaction_id <> -1 AND transaction_id <> -2;
Queries should be used for investigation and validation only. The internal designation and the reliance on ROWID-based retrieval mean consumers should prefer documented base tables for persistent integration requirements.
-
View: CRP_RESOURCE_V 12.1.1
Internal view for performance
APPS.CRP_RESOURCE_V·↳ CRP_RESOURCE_PLAN·↳ MRP_RECOMMENDATIONS·↳ MRP_SUGG_REP_SCHEDULES·Explore CRP module →
-
Table to maintain log of migrated records in receiving lots
-
View: CSI_T_TXN_LINES_V 12.2.2
View on top of Transaction Lines - CSI_T_TRANSACTION_LINES
APPS.CSI_T_TXN_LINES_V·↳ CSI_T_TRANSACTION_LINES·Explore CSI module →
-
View: CSI_T_TXN_LINES_V 12.1.1
View on top of Transaction Lines - CSI_T_TRANSACTION_LINES
APPS.CSI_T_TXN_LINES_V·↳ CSI_T_TRANSACTION_LINES·Explore CSI module →
-
Receiving lots transactions
-
This table contains transactions information collated from three source transaction tables - IGS_FI_CR_ACTIVITIES, IGS_FI_INVLN_INT_ALL and IGS_FI_APPLICATIONS for posting purposes. The information captured here is an interim step to create
-
APPS.MRPBV_PLAN_RESOURCE_LOADS·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CRP_RESOURCE_PLAN·Explore MRP module →
-
View: IGS_FI_POSTING_INT 12.1.1
This view is created to filter multi-org from table IGS_FI_POSTING_INT_ALL .
APPS.IGS_FI_POSTING_INT·↳ IGS_FI_POSTING_INT_ALL·Explore IGS module →
-
Counter group log of counter updates within a group
-
View: CRP_RESOURCE_V 12.2.2
Internal view for performance
APPS.CRP_RESOURCE_V·↳ CRP_RESOURCE_PLAN·↳ MRP_RECOMMENDATIONS·↳ MRP_SUGG_REP_SCHEDULES·Explore CRP module →
-
- Retrofitted
APPS.RCV_SERIAL_CORRECTION_V·↳ RCV_SERIAL_TRANSACTIONS·Explore PO module →
-
Receiving serial transactions
-
Receiving serial transactions
-
Receiving lots transactions
-
Table to maintain log of migrated records in receiving lots
-
APPS.MRPBV_PLAN_RESOURCE_LOADS·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CRP_RESOURCE_PLAN·Explore MRP module →
-
View of detailed resource requirements
APPS.CRP_RESOURCE_REQUIREMENTS_V·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CRP_RESOURCE_PLAN·Explore CRP module →
-
View: CSI_BIS_TXN_DTLS_V 12.2.2
View created for the Oracle IT - GSI
APPS.CSI_BIS_TXN_DTLS_V·↳ CSI_SYSTEMS_VL·↳ CSI_TXN_SUB_TYPES·↳ CSI_T_TRANSACTION_LINES·Explore CSI module →
-
- Retrofitted
APPS.RCV_SERIAL_CORRECTION_V·↳ RCV_SERIAL_TRANSACTIONS·Explore PO module →
-
Capacity resource plan
-
Transaction Details : Transaction Lines
-
View: IGS_FI_CRD_INT 12.1.1
No longer used.
APPS.IGS_FI_CRD_INT·↳ IGS_FI_CRD_INT_ALL·Explore IGS module →
-
View: IGS_FI_INVLN_INT 12.1.1
APPS.IGS_FI_INVLN_INT·↳ IGS_FI_INVLN_INT_ALL·Explore IGS module →
-
Counter group log of counter updates within a group
-
View: IGS_FI_CREDITS 12.1.1
This view is a multi-org filter flat view based on table IGS_FI_CREDITS_ALL.
APPS.IGS_FI_CREDITS·↳ IGS_FI_CREDITS_ALL·Explore IGS module →
-
This table contains information about all credit or payment transactions and is the central repository for all credits and payments related information in Student Finance.
-
Capacity resource plan
-
Transaction Details : Transaction Lines
-
View of detailed resource requirements
APPS.CRP_RESOURCE_REQUIREMENTS_V·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CRP_RESOURCE_PLAN·Explore CRP module →
-
View: CSI_BIS_TXN_DTLS_V 12.1.1
View created for the Oracle IT - GSI
APPS.CSI_BIS_TXN_DTLS_V·↳ CSI_SYSTEMS_VL·↳ CSI_TXN_SUB_TYPES·↳ CSI_T_TRANSACTION_LINES·Explore CSI module →
-
Used to store the history information related to the container's past transactions
-
Used to store the history information related to the container's past transactions
-
Backward compatible view for CS_CTR_COUNTER_VALUES_V
APPS.CSI_COUNTER_READINGS_BCV_V·↳ CSI_COUNTERS_BC_V·↳ CSI_COUNTER_READINGS·↳ CSI_COUNTER_READINGS_PVT·Explore CSI module →
-
APPS.MRPFV_PLAN_RESOURCE_LOADS·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CRP_RESOURCE_PLAN·Explore MRP module →
-
APPS.MRPFV_PLAN_RESOURCE_LOADS·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CRP_RESOURCE_PLAN·Explore MRP module →
-
Holds the counter readings interface data
-
GMO Material UNDispenses
-
GMO Material UNDispenses
-
View: IGS_FI_INV_INT 12.1.1
APPS.IGS_FI_INV_INT·↳ IGS_FI_INV_INT_ALL·Explore IGS module →
-
This interface table stores invoice data generated by invoice process.
-
Backward compatible view for CS_CTR_COUNTER_VALUES_V
APPS.CSI_COUNTER_READINGS_BCV_V·↳ CSI_COUNTERS_BC_V·↳ CSI_COUNTER_READINGS·↳ CSI_COUNTER_READINGS_PVT·Explore CSI module →
-
This interface table stores invoice lines data generated by invoice process.
-
this view shows all the resource requirements
APPS.MSC_RESOURCE_REQUIREMENTS_V·↳ MSC_DEPARTMENT_RESOURCES·↳ MSC_GET_NAME·↳ MSC_INTERORG_SHIP_METHODS·Explore MSC module →
-
View: IGS_FI_INVLN_INT_V 12.1.1
This view is created from multi-org filtered flat view IGS_FI_INVLN_INT for presentation of data in Charges History Form.
APPS.IGS_FI_INVLN_INT_V·↳ IGS_FI_INVLN_INT·↳ IGS_PS_UNIT_OFR_OPT·↳ IGS_PS_UNIT_TYPE_LVL·Explore IGS module →
-
Holds the counter readings interface data
-
View: IGS_FI_INV_IGF_V 12.1.1
This view is used to fetch all the charges from the view igs_fi_inv_int. A link with igs_fi_fee_type is also made to fetch the fee class defined for the fee type.This view has been primarily created for Financial Aid Disbursement to access
APPS.IGS_FI_INV_IGF_V·↳ IGS_FI_FEE_TYPE·↳ IGS_FI_INV_INT·Explore IGS module →
-
View: IGS_FI_INV_INT_V 12.1.1
This view is created by joining view IGS_FI_INV_INT and IGS_LOOKUPS_VIEW to resolve meaning of lookup codes.
APPS.IGS_FI_INV_INT_V·↳ IGS_FI_INV_INT·↳ IGS_LOOKUP_VALUES·Explore IGS module →
-
No longer used.
-
View: IGS_FI_OTC_CHARGES_V 12.1.1
The view contains information on the charges(of type external) that are created at the time of receipt creation.
APPS.IGS_FI_OTC_CHARGES_V·↳ IGS_FI_ACC·↳ IGS_FI_INVLN_INT·↳ IGS_FI_INV_INT·Explore IGS module →
-
View: IGS_FI_CREDITS_V 12.1.1
This is a multi-org view based on org filtered view IGS_FI_CREDITS and join with view IGS_LOOKUPS_VIEW and IGS_FI_CR_TYPES view to resolve Lookup Meaning and Credit Type Names from IDs
APPS.IGS_FI_CREDITS_V·↳ IGF_LOOKUPS_VIEW·↳ IGS_CA_INST·↳ IGS_EN_GEN_003·Explore IGS module →