Results for “reason_id”

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

Overview

SY_REAS_CDS_B is the Reason Code base table owned by the GMA schema (Process Manufacturing Systems) and is a VALID object in Oracle EBS 12.1.1 and 12.2.2. The table stores Reason Code definitions that describe the underlying cause for an inventory increase or decrease. Reason codes are attached to transactions so that adjustments, movements, holds, cancellations, and reversals carry an auditable explanation rather than a bare quantity change. In this respect the table functions as a central, low-volatility classification list — a shared vocabulary of business justifications consumed by purchasing, inventory, process execution, and cost management modules across EBS.

Mined from the foreign-key structure, the heuristic Data Vault classification is hub-leaning. This is a modeling suggestion only: SY_REAS_CDS_B behaves like a reference hub, keyed by a single business identifier (REASON_CODE) that many dependent transaction tables reference, with its descriptive attributes (REASON_DESC1, REASON_DESC2, REASON_TYPE, FLOW_TYPE) functioning as satellite-style detail. Because the descriptive attributes change far less frequently than the transactions that point to it, the hub reading is a reasonable design heuristic.

Key Information Stored

• REASON_CODE — the business-key candidate and the only column in the unique index SY_REAS_CDS_B_PK. It is the value stamped onto every dependent transaction.
• REASON_ID — the surrogate identifier used for internal relational joins and for foreign keys from dependent tables.
• REASON_DESC1 / REASON_DESC2 — the printed description(s) of the reason, displayed on forms, reports, and transaction inquiries.
• REASON_TYPE — classifies the nature of the reason (for example, the operating category the reason belongs to).
• FLOW_TYPE — indicates whether the reason is associated with an inventory increase or decrease, the core semantic of the table.
• TEXT_CODE — foreign key to SY_TEXT_HDR, linking the reason to a reusable text block of longer explanatory notes.
• AUTH_STRING — authority/security string controlling which responsibilities or users may apply the reason.
• DELETE_MARK — soft-delete flag; records are deactivated rather than physically removed to preserve historical references.
• TRANS_CNT — usage counter reflecting how many transactions have referenced the reason.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns supporting concurrency and change tracking.

Note that the primary key constraint (SY_REAS_CDS_B_PK) is documented on REASON_CODE, while REASON_ID is carried as a separate surrogate column — a pattern typical of EBS reference tables where a short coded business key coexists with a numeric ID.

Common Use Cases and Queries

The most frequent use is translating a code into a meaningful description when reporting transaction detail. A typical lookup resolves the code on an inventory or purchasing transaction:

• Inventory adjustment reporting: join IC_TRAN_CMP or IC_TRAN_PND on REASON_CODE and select REASON_DESC1, FLOW_TYPE, and REASON_TYPE to report why a quantity changed.
• Purchasing hold and cancellation analysis: the PO_BPOS_DTL columns BPOHOLD_CODE, CANCELLATION_CODE, and CLOSURE_CODE all point at SY_REAS_CDS_B, so a query joining those columns to REASON_CODE yields the hold/cancel/close reason text at the blanket purchase order line level.
• Reason-code frequency analysis: aggregate by REASON_CODE and use TRANS_CNT to identify the most heavily used adjustment and discrepancy justifications.
• Security and configuration review: filter on AUTH_STRING and DELETE_MARK to list only active, authorized reason codes available to a given responsibility.
• Text expansion: join TEXT_CODE to SY_TEXT_HDR when long-form justification is required for audit documentation.

A representative pattern is SELECT r.REASON_CODE, r.REASON_DESC1, r.FLOW_TYPE FROM GMA.SY_REAS_CDS_B r WHERE r.DELETE_MARK = 0, joined to the consuming transaction table on the appropriate reason-code column, always honoring DELETE_MARK so retired codes do not distort reporting.

Related Objects

SY_REAS_CDS_B is the referenced side of a broad set of foreign keys, confirming its role as a shared reference hub:

• SY_TEXT_HDR — referenced by SY_REAS_CDS_B.TEXT_CODE for long descriptive text.
• PO_BPOS_DTL and PO_BPOS_HDR — reference the reason code through BPOHOLD_CODE, CANCELLATION_CODE, and CLOSURE_CODE; this is the object the originating search (po_bpos_dtl) implicates.
• PO_ORDR_HDR and PO_ORDR_DTL — reference it via POHOLD_CODE and CANCELLATION_CODE.
• PO_RECV_HDR (REASON_CODE) and PO_RTRN_DTL (RETURN_CODE) — purchasing receiving and returns.
• IC_TRAN_CMP, IC_TRAN_PND, and IC_TRAN_ARC — inventory transaction tables, joined on REASON_CODE.
• IC_XFER_MST — references three distinct columns: RELEASE_REASON_CODE, RECEIVE_REASON_CODE, and CANCEL_REASON_CODE.
• GL_ACCT_MAP — maps reason codes to accounts, joined on REASON_CODE.
• OP_ORDR_HDR and OP_ORDR_DTL (CHANGEREAS_CODE), PC_TRAN_PND (REASON_CODE), and GMP_RSRC_EXCP_DTL / GMP_RSRC_UNAVAIL_MAN (REASON_CODE) — process manufacturing change, resource, and transaction dependencies.

Because so many transaction tables depend on it, changes to REASON_CODE values must be managed carefully; deactivation through DELETE_MARK is preferred over deletion to avoid orphaning historical transaction references.