Results for “op_fobc_mst”

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

Overview

OP_FOBC_MST is the Free on Board (FOB) code master table in the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. It stores the valid FOB code definitions used across the process manufacturing order lifecycle, including sales orders, purchase orders, proposals, receipts, and customer master records. FOB codes describe the point at which ownership and freight responsibility for goods transfers between shipper and consignee, making this table a controlled reference source that downstream transactional tables depend on.

The table is owned by the GML schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. It contains 16 documented columns and two unique indexes: OP_FOBC_MST_PK on FOB_CODE and OP_FOBC_MST01 on OF_FOB_CODE. Heuristically, based on its foreign key structure, this object can be modeled as a Data Vault hub: it holds a stable business key (FOB_CODE) with descriptive attributes and is referenced by many surrounding transactional and master tables, with no intervening link-table pattern evident in the documented relationships.

Key Information Stored

• FOB_CODE — the primary business key and the column targeted by the OP_FOBC_MST_PK unique index. This is the value referenced by every foreign key listed in the metadata.
• OF_FOB_CODE — a secondary unique-indexed column (OP_FOBC_MST01), likely an alternate or legacy FOB identifier maintained for compatibility.
• FOB_NAME — the descriptive name of the FOB code, used for display in order entry and reporting.
• ADDR_ID — foreign key to SY_ADDR_MST, linking the FOB definition to a specific address record.
• TEXT_CODE — foreign key to OP_TEXT_HDR, associating free-form descriptive text with the FOB code.
• DELETE_MARK — soft-delete indicator controlling whether the FOB code remains active and selectable.
• TRANS_CNT — transaction counter, typically used for concurrency or record-change tracking.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording who created and last modified the row.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent-program context columns identifying the process that created or updated the record.

The surrogate/primary identifier is FOB_CODE via OP_FOBC_MST_PK, while OF_FOB_CODE serves as a second documented unique business-key candidate.

Common Use Cases and Queries

Typical usage centers on validating and resolving FOB codes during order capture, shipment, and reporting. A frequent query joins the master to its descriptive text header:

• List active FOB codes: SELECT FOB_CODE, FOB_NAME FROM GML.OP_FOBC_MST WHERE DELETE_MARK = 0;
• Resolve FOB descriptions onto order lines: join OP_ORDR_DTL.FOB_CODE to OP_FOBC_MST.FOB_CODE to report the FOB name alongside order detail.
• Locate the address associated with a FOB code via ADDR_ID against SY_ADDR_MST for shipping documentation.
• Retrieve supplemental narrative text through TEXT_CODE against OP_TEXT_HDR.
• Audit recent maintenance using LAST_UPDATE_DATE and LAST_UPDATED_BY, or trace the originating concurrent request via REQUEST_ID.

Because the table is reference data rather than transactional data, reporting use cases predominantly involve lookup enrichment and validation of FOB values passed in from order, proposal, and receipt processing.

Related Objects

The documented foreign key relationships show this table both references and is referenced by significant GML objects:

• OP_TEXT_HDR — referenced through OP_FOBC_MST.TEXT_CODE, supplying descriptive text.
• SY_ADDR_MST — referenced through OP_FOBC_MST.ADDR_ID, supplying address details.
• OP_CUST_MST and OP_CUST_MST_OPM — customer master tables referencing FOB_CODE, defining default FOB terms per customer.
• OP_ORDR_HDR and OP_ORDR_DTL — process sales order header and detail tables carrying FOB_CODE.
• OP_PRSL_HDR — proposal header referencing FOB_CODE.
• PO_ORDR_HDR and PO_ORDR_DTL — process purchase order header and detail tables.
• PO_BPOS_HDR and PO_BPOS_DTL — blanket purchase order header and detail tables.
• PO_RECV_DTL — purchase receipt detail referencing FOB_CODE.

These dependencies confirm OP_FOBC_MST as a central reference hub whose FOB_CODE key propagates throughout process manufacturing order, customer, and receiving flows.