Search Results insert_item_ccids

Overview

FWK_TBX_SEED is a PL/SQL seed-data package in the Oracle E-Business Suite Applications (APPS) schema, declared with AUTHID CURRENT_USER. Its header, fwktbx_seeds.pls version 120.2, dates from December 2005 and carries the "noship" designation, indicating it is an internal utility rather than a shipped product feature. The package exists to populate and maintain the demonstration and sample data used by the Oracle EBS "Toolbox" (TBX) framework — a set of illustrative entities such as employees, addresses, suppliers, items, purchase orders, and projects that support tutorials, samples, and framework testing.

Functionally, FWK_TBX_SEED provides a programmatic alternative to manual data entry for the TBX sample schema. Each procedure encapsulates the insert, update, or delete logic for one entity type, so callers need not construct direct DML against the underlying TBX tables. This promotes consistency between seeded records and the lookup, employee, and trading-partner structures they depend on. The package is documentation-classified as OTHER, reflecting its role as a supporting utility rather than a formal public API.

Key Procedures and Functions

The 17 documented procedures fall into distinct functional groups:

• Lookup maintenance: INSERT_LOOKUP_TYPE, INSERT_LOOKUP_CODE, UPDATE_LOOKUP_TYPE, UPDATE_LOOKUP_CODE, DELETE_LOOKUP_TYPE, and DELETE_LOOKUP_CODE manage lookup types and their associated codes, including display names, meanings, descriptions, and effective start and end dates.
• Party and HR seeding: INSERT_EMPLOYEE creates employee records with title, name components, e-mail, manager, position, salary, and date range. INSERT_ADDRESS creates address records with multiple address lines, country, city, postal code, telephone numbers, and effective dates.
• Supplier seeding: INSERT_SUPPLIER and INSERT_SUPPLIER_SITE create supplier headers and their sites, including hold flags, payment terms, carrier, purchasing-site indicator, and address linkage.
• Transaction seeding: INSERT_ITEM, INSERT_ITEM_CCIDS, INSERT_PO_HEADER, INSERT_PO_LINE, and INSERT_PO_SHIPMENT create catalog items, item cost-category assignments, and the purchase order header, line, and shipment hierarchy.
• Project seeding: INSERT_PROJECT_HEADER and INSERT_PROJECT_DETAIL create project headers and their detail records.

Only procedures are documented; no functions are listed. Parameter lists are not reproduced here; the procedures are named descriptively and accept the entity attributes required for their respective TBX tables.

Tables Accessed

The package reads and writes fourteen APPS synonyms plus DUAL. Lookup operations target FWK_TBX_LOOKUP_TYPES_TL and FWK_TBX_LOOKUP_CODES_B/TL, which follow the standard EBS translatable-table pattern. Employee and address seeding target FWK_TBX_EMPLOYEES and FWK_TBX_ADDRESSES. Supplier operations use FWK_TBX_SUPPLIERS and FWK_TBX_SUPPLIER_SITES. Item and purchasing procedures write to FWK_TBX_ITEMS, FWK_TBX_ITEM_CCIDS, FWK_TBX_PO_HEADERS, FWK_TBX_PO_LINES, and FWK_TBX_PO_SHIPMENTS. Project procedures populate FWK_TBX_PROJECT_HEADERS and FWK_TBX_PROJECT_DETAILS. DUAL is used for single-row evaluations, likely for sequence or default-value retrieval.

Usage Notes

FWK_TBX_SEED is referenced by zero other packages, indicating it is a terminal utility invoked directly rather than through a wider call graph. It is typically executed from SQL*Plus or a similar client during environment setup, developer sandbox initialization, or Toolbox framework exercises. Because it is an unshipped seed utility, it is not appropriate for production data loading; production integrations should use the corresponding EBS Open Interfaces and public APIs. The AUTHID CURRENT_USER declaration means execution depends on the calling user's privileges, so careful grant management is required. Custom code may call these procedures for test-data generation, but should treat the TBX tables as demonstration-only and avoid dependencies on them in delivered solutions.