Results for “transaction_source_name”

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

Overview

APPS.WIP_FLOW_DERIVE is a PL/SQL defaulting package in Oracle EBS Work in Process (WIP) that supports the flow manufacturing scheduling and transaction forms. It consolidates the derivation of defaulted flow attributes — bill of material revisions, routing revisions, completion subinventories and locators, class codes, and schedule group information — into single database round-trips, so that the flow scheduling and move/complete forms populate their fields efficiently rather than issuing multiple queries per attribute. The package is declared AUTHID CURRENT_USER, so all unqualified object references resolve through the caller's schema, which for standard Oracle EBS usage is APPS. It is referenced by eight other packages, indicating its role as a shared derivation utility rather than an entry point in its own right.

Key Procedures and Functions

The package exposes eighteen documented subprograms. FLOW_FORM_DEFAULTING is the primary entry point: it defaults the complete set of flow-related information for a form in one database hit and accepts context for the transaction action, transaction type, item, organization, start date, and alternate routing, along with project and task identifiers. Several revision defaults are exposed individually as well: BOM_REVISION derives the bill revision and its effective date, and ROUTING_REVISION derives the routing revision and date. COMPLETION_SUB returns a default completion subinventory, while ROUTING_COMPLETION_SUB_LOC, COMPLETION_LOCATOR_ID, and COMPLETION_LOC derive the corresponding routing completion subinventory, locator, and completion locator values. CLASS_CODE defaults the WIP class code for a given organization, item, WIP entity type, and project. SCHEDULE_GROUP_ID and SCHEDULE_NUMBER support flow schedule identification, and BUILD_SEQUENCE, SRC_PROJECT_ID, and SRC_TASK_ID resolve source project and task context and build sequencing. LAST_UPDATED_ID and CREATED_BY_ID return audit-related identifiers, and ORGANIZATION_CODE and TRANSACTION_SOURCE_NAME provide descriptive defaults. SCHEDULED_FLOW_DERIVATION is the higher-level derivation routine used for scheduled flow operations.

Tables Accessed

The package reads and writes a focused set of WIP, BOM, and inventory tables through APPS synonyms. WIP_ENTITIES and WIP_FLOW_SCHEDULES supply the flow schedule and entity context that anchors most defaulting logic. WIP_JOB_NUMBER_S is used for job number generation. BOM_OPERATIONAL_ROUTINGS provides routing revision and operation information. MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, and MTL_ITEM_LOCATIONS supply organization defaults, valid subinventories, and locator validation. MTL_TRANSACTIONS_INTERFACE supports transaction interface population. FND_USER is queried for user-related identifiers, consistent with the CREATED_BY_ID and LAST_UPDATED_ID functions. DUAL serves internal scalar computations.

Usage Notes

WIP_FLOW_DERIVE is typically invoked from the Oracle Forms-based flow manufacturing scheduling, move, and completion windows, where field-level defaulting must be resolved quickly; the single-call design of FLOW_FORM_DEFAULTING is intended to minimize round-trips during form navigation. Individual functions may also be called from custom PL/SQL that needs to replicate standard form defaulting behavior — for example, when building an interface or a custom completion form. Because the package is referenced by eight other packages and is compiled AUTHID CURRENT_USER, custom callers should execute it within a schema that holds the APPS synonyms and appropriate privileges on the underlying WIP, BOM, and INV tables. It is not a public API in the sense of a documented business interface; the routines should be treated as internal defaulting helpers whose signatures may change between patch levels, so custom code should favor the packaged date-stamped version it was validated against.