Search Results inv_label_pub




Overview
Explore in AI Chat

Overview

INV_LABEL_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the PUB (public) API category. It provides the application programming interface for Oracle Inventory's label printing functionality, which allows organizations to generate and print item, container, location, and material labels directly from within the EBS environment. The package encapsulates the business logic required to compose label content, apply formatting rules, and submit label requests for output, insulating calling modules from the underlying label generation mechanics.

In Oracle EBS 12.1.1 and 12.2.2, the package is documented as VALID and is fully resolved against its dependencies, confirming that it is an active, supported component of the Inventory application. As a PUB package, it is intended to be called by other Oracle modules and by customer extensions rather than being restricted to a single internal consumer, making it the supported entry point for programmatic label printing.

Key Procedures and Functions

The ETRM metadata documents a single public procedure or function within the package signature:

  • PRINT_LABEL — The principal entry point of the package. This procedure drives the label printing operation: it accepts identifying information for the label request, assembles the required label data, and submits the request for formatting and physical output. Callers invoke PRINT_LABEL when a business event requires a label to be produced, such as receiving goods, completing a work in process transaction, or performing a move order.

No additional procedures or functions are documented as part of the public interface, so PRINT_LABEL should be treated as the complete supported API surface. Specific parameter lists are not enumerated in the ETRM extract and must be confirmed against the deployed package specification in the target instance before use.

Tables Accessed

The documented table reference for this package is the APPS synonym PLITBLM. PLITBLM is the label printing interface table used by the Oracle label generation infrastructure to hold label request records — including the print request identifier, label definition, quantity, and associated item or organizational attributes — while the request is queued, processed, and completed by the label printing concurrent program.

PRINT_LABEL interacts with PLITBLM to insert and manage these request rows, which the label printing engine subsequently reads to produce output. Because PLITBLM is accessed through an APPS synonym, the package operates against the base table through standard EBS naming and privilege conventions.

Usage Notes

INV_LABEL_PUB is most commonly invoked indirectly by standard EBS functionality rather than by end users directly. The dependency data shows that it is referenced by WSH_NEW_DELIVERY_ACTIONS and WSH_UTIL_CORE, both of which reside in the Oracle Shipping execution area. This indicates that label printing is triggered as part of delivery and shipping workflows — for example, when a delivery is confirmed or a move order is executed, the shipping logic calls into INV_LABEL_PUB.PRINT_LABEL to generate the corresponding labels.

The package further depends on FND_API, the standard Oracle Application Object Library API layer, confirming that it follows Oracle's public API conventions for error handling, message retrieval, and result reporting via the standard FND message stack. Custom code that calls PRINT_LABEL should therefore initialize and interrogate the FND message stack as it would for any other FND_API-based public interface.

Typical invocation contexts include: shipping and delivery confirmation flows in WSH; inventory transactions that require label output; and customer-written extensions or concurrent programs that call APPS.INV_LABEL_PUB.PRINT_LABEL in APPS schema context with the appropriate label request parameters. Application developers should verify the exact parameter signature against the deployed package specification, since the ETRM metadata documents only the procedure name and not its arguments.