Search Results get_routing_sequence




Overview
Explore in AI Chat

Overview

APPS.BOM_DEFAULT_RTG_HEADER is a server-side PL/SQL package body residing in the Oracle E-Business Suite Applications schema. Its business role is to supply defaulting and validation logic for routing header records within Oracle Bills of Material and Manufacturing. Routing headers define the manufacturing routing attributes attached to a manufactured item, and the package centralizes the derivation of defaulted column values, null-column normalization, and the generation of routing sequence identifiers. The package was originally authored in August 2000 and the shipped body carries the header revision identifier BOMDRTGB.pls 120.1 (dated 2006), with the internal package name constant declared as G_PKG_NAME with the value 'Rtg_Default_Rtg_Header'. In the Oracle EBS 12.1.1 and 12.2.2 releases, this object participates in the routing definition flow that supports discrete manufacturing, and it operates under the APPS synonym layer so that public APIs and forms can call it without fully qualified schema references.

Key Procedures and Functions

  • GET_ROUTING_SEQUENCE — Returns the primary key value for a new routing sequence. Internally it fetches the next value from the sequence associated with the routing base table and returns that number to the caller. This is the routine most commonly associated with the search term "get_routing_sequence" and is the standard mechanism used when inserting new routing sequence rows.
  • ATTRIBUTE_DEFAULTING — Applies default values to descriptive flexfield attribute columns on the routing header record.
  • ENTITY_ATTRIBUTE_DEFAULTING — Performs attribute defaulting at the entity level, coordinating the defaulting behavior across the routing header structure.
  • POPULATE_NULL_COLUMNS — Normalizes record structures by replacing sentinel or missing values with proper nulls, ensuring that incomplete incoming records do not persist invalid placeholder data.
  • GET_CFM_ROUTING_FLAG — Resolves the configuration-model (CFM) routing indicator used to distinguish routing behavior for configured items.
  • GET_MIXED_MODEL_MAP_FLAG — Determines the mixed-model mapping flag applicable to the routing header.
  • GET_CTP_FLAG — Determines the Capable-to-Promise (CTP) flag associated with the routing context.

The documented body excerpt also confirms that Get_Flex_Rtg_Header copies an incoming routing header record into an output record and replaces FND_API.G_MISS_CHAR sentinels with NULLs across the attribute_category and attribute1 through attribute3 columns, with a comment indicating that flexfield default APIs were planned for future enhancement.

Tables Accessed

  • BOM_OPERATIONAL_ROUTINGS — The base routing header table. The package reads and defaults columns that are written back to this table during routing creation and update.
  • BOM_OPERATIONAL_ROUTINGS_S — The sequence object associated with the routing base table, used by GET_ROUTING_SEQUENCE to obtain the next primary key value.
  • MTL_SYSTEM_ITEMS — The item master, consulted to validate item context and to derive item-dependent routing attributes.

Usage Notes

BOM_DEFAULT_RTG_HEADER is invoked by the routing maintenance forms and by public routing APIs during header record preparation. According to documented metadata, the package is referenced by four other packages, indicating it functions as a shared utility within the manufacturing module stack rather than as a standalone entry point. Custom code should call it through the APPS synonym, for example APPS.BOM_DEFAULT_RTG_HEADER.GET_ROUTING_SEQUENCE, to obtain a routing sequence identifier before inserting a new header row. Because GET_ROUTING_SEQUENCE returns NULL when an unexpected error occurs, callers must validate the returned value before using it as a primary key. Direct DML against the underlying tables should be avoided; defaulting logic belongs in this package so that forms, concurrent programs, and interface programs all observe identical validation behavior across 12.1.1 and 12.2.2.