Results for “get_supplier”

40 results




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

Overview

FLM_MULTIPLE_SUPPLIERS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports multiple-source supplier selection for Kanban replenishment in Oracle Flow Manufacturing. When a Kanban pull sequence is sourced from more than one approved supplier, each supplier is assigned a sourcing percentage. The package uses those percentages, together with the suppliers already represented on existing Kanban cards, to determine the correct supplier and supplier site for each newly created card. In effect, it enforces the sourcing ratio across the population of Kanban cards rather than selecting a supplier arbitrarily. The package header identifies the release lineage through the header comment $Header: flmmsups.pls 120.1.12020000.2 2012/07/13, and it is documented within the ETRM repository as API classification OTHER, with two documented procedures. The package is relevant to both 12.1.1 and 12.2.2 deployments of Flow Manufacturing, where Kanban replenishment is configured against purchasing sourcing rules.

Key Procedures and Functions

  • GET_SUPPLIER — Returns the supplier and supplier site to be used for the creation of a new Kanban card. As documented, the procedure takes into account the suppliers appearing on existing cards and the sourcing percentages assigned to each supplier when calculating which supplier should be applied to the new card. The header notes that a p_cardstatus parameter was added under Bug#14230963, indicating that card status influences the calculation of eligible existing cards. The procedure returns the supplier identifier, the supplier site identifier, a return code, and an error message through its output parameters.
  • MULTIPLE_SUPPLIER_KANBAN_CARDS — Calculates the number of Kanban cards that should be allocated to each supplier based on the configured sourcing percentages. This procedure underpins the distribution logic used by GET_SUPPLIER by establishing how many cards each supplier is entitled to across the pull sequence.

No parameter lists are reproduced here; the documented signatures comprise pull sequence identifier, organization identifier, card status, and the standard return code and error message outputs for GET_SUPPLIER, and pull sequence identifier, return code, and error message for MULTIPLE_SUPPLIER_KANBAN_CARDS. The package body exposes these two procedures only.

Tables Accessed

  • MTL_KANBAN_CARDS — The primary repository of Kanban card records. The package reads existing cards to establish current supplier distribution and writes or influences new card creation.
  • MTL_KANBAN_PULL_SEQUENCES — Defines the pull sequence, including the organization and sourcing context to which the Kanban cards belong.
  • MTL_PULL_SEQ_SUPPLIERS — Holds the suppliers and their sourcing percentages for a given pull sequence; this is the source of the percentage weighting applied by both procedures.
  • PLITBLM — A PL/SQL index-by table type used internally for array processing, typically to hold intermediate supplier or card collections during the calculation.

All access occurs through APPS synonyms, consistent with standard EBS coding practice and the 12.2 online patching editioning model.

Usage Notes

FLM_MULTIPLE_SUPPLIERS is invoked by the Flow Manufacturing Kanban card creation and replenishment flows rather than by end users directly. It is referenced by five other packages within the EBS codebase, which is consistent with its role as a shared service for supplier determination. Typical invocation points include the Kanban card generation concurrent programs and the Kanban workbench forms where cards are created or re-created against a pull sequence. Because supplier selection depends on the current population of cards, the procedure should be called within the transaction that creates the card so that consecutive calls observe the updated distribution. Customizations that bypass this package and assign suppliers directly risk violating the sourcing percentages and should be avoided. Error handling should always inspect the returned x_retcode and x_err_msg values, since supplier configuration gaps in MTL_PULL_SEQ_SUPPLIERS will surface as errors at card creation time.