Search Results csp_sch_int_pvt_w
Overview
CSP_SCH_INT_PVT_W is a PL/SQL package in the APPS schema that forms part of Oracle E-Business Suite's Supply Chain Planning (CSP) integration layer. The "_W" suffix and the "ROSETTA_TABLE_COPY" procedure naming convention indicate that this is a generated Rosetta wrapper package whose primary role is to marshal data between PL/SQL collection types and the underlying staging or interface tables used by the scheduling integration subsystem. In the EBS architecture, CSP modules support constraint-based and supply chain scheduling, and integration packages such as CSP_SCH_INT_PVT_W act as the private helper layer beneath the public CSP_SCH_INT_PVT API. The wrapper packages are machine-generated in large numbered families (P13, P14, P15, and so on) to work around PL/SQL compiler and method-size limits, each handling a slice of an oversized data transfer operation. The object holds a VALID status in the 12.1.1 and 12.2.2 releases, and the ETRM metadata classifies its API classification as OTHER, meaning it is not intended as a documented extension or callback point for customer development.
Key Procedures and Functions
The metadata documents 33 procedures and functions, the visible portion of which follow a strict paired pattern of ROSETTA_TABLE_COPY_IN_Pnn and ROSETTA_TABLE_COPY_OUT_Pnn, where nn ranges from P13 through at least P22 in the excerpted listing.
- ROSETTA_TABLE_COPY_IN_P13 through ROSETTA_TABLE_COPY_IN_P22 — Each of these procedures performs the inbound half of a table-copy operation for a discrete partition of the overall payload. They move data from PL/SQL collection structures into the target interface table, with the numeric suffix identifying the data segment each procedure owns.
- ROSETTA_TABLE_COPY_OUT_P13 through ROSETTA_TABLE_COPY_OUT_P22 — The symmetric outbound counterparts. Each procedure reads a segment of interface data back into PL/SQL collections so that the parent package, CSP_SCH_INT_PVT, can process it in memory.
The numbered partitions exist because a single monolithic copy routine would exceed PL/SQL structural limits; splitting the work across P13 through P22 (and the corresponding lower-numbered partitions not shown) permits the complete dataset to be transferred in manageable chunks. No parameter lists are published for these routines in the metadata, and they should be treated as internal implementation details of CSP_SCH_INT_PVT.
Tables Accessed
The documentation records a single table referenced through APPS synonyms: PLITBLM. This is the standard Oracle designer and developer utility table used for long-identifier storage and table-based lookups, and its presence here is consistent with a generated wrapper that resolves column or table references dynamically during the Rosetta copy operation. In practice, the substantive data movement performed by the IN and OUT procedures targets the CSP scheduling interface structures owned by the parent package CSP_SCH_INT_PVT.
Usage Notes
CSP_SCH_INT_PVT_W is referenced only by CSP_SCH_INT_PVT and references no other application packages, confirming its position as a strictly private subordinate module. It is not invoked directly from Oracle Forms, concurrent program definitions, or supported public APIs. Customers performing upgrades or applying patches should expect this object to be regenerated automatically by Oracle's build and installation utilities, and any manual modification would be overwritten at the next patch cycle. The package depends on the JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_300, and JTF_VARCHAR2_TABLE_4000 collection types supplied by the JTF foundation layer, which is typical of Rosetta-generated code. Because the package is classified as OTHER and is documented as VALID, it requires no customer-directed configuration or extension work; it should be treated purely as internal infrastructure supporting the Supply Chain Planning scheduling integration.
-
PACKAGE: APPS.CSP_SCH_INT_PVT_W
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSP_SCH_INT_PVT_W, status:VALID,
-
PACKAGE: APPS.CSP_SCH_INT_PVT_W
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSP_SCH_INT_PVT_W, status:VALID,
-
PACKAGE: APPS.CSP_SCH_INT_PVT
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSP_SCH_INT_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSP_SCH_INT_PVT_W
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSP_SCH_INT_PVT_W, status:VALID,
-
PACKAGE BODY: APPS.CSP_SCH_INT_PVT_W
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSP_SCH_INT_PVT_W, status:VALID,
-
PACKAGE: APPS.CSP_SCH_INT_PVT
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSP_SCH_INT_PVT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
TYPE: APPS.JTF_VARCHAR2_TABLE_4000
12.2.2
owner:APPS, object_type:TYPE, object_name:JTF_VARCHAR2_TABLE_4000, status:VALID,
-
PACKAGE: APPS.CSP_SCH_INT_PVT_W
12.1.1
-
PACKAGE: APPS.CSP_SCH_INT_PVT_W
12.2.2
-
APPS.CSP_SCH_INT_PVT_W dependencies on CSP_SCH_INT_PVT_W
12.1.1
-
APPS.CSP_SCH_INT_PVT_W dependencies on CSP_SCH_INT_PVT_W
12.2.2
-
TYPE: APPS.JTF_VARCHAR2_TABLE_300
12.1.1
owner:APPS, object_type:TYPE, object_name:JTF_VARCHAR2_TABLE_300, status:VALID,
-
TYPE: APPS.JTF_VARCHAR2_TABLE_300
12.2.2
owner:APPS, object_type:TYPE, object_name:JTF_VARCHAR2_TABLE_300, status:VALID,
-
APPS.CSP_SCH_INT_PVT_W dependencies on CSP_SCH_INT_PVT
12.2.2
-
APPS.CSP_SCH_INT_PVT_W dependencies on CSP_SCH_INT_PVT
12.1.1
-
TYPE: APPS.JTF_DATE_TABLE
12.1.1
owner:APPS, object_type:TYPE, object_name:JTF_DATE_TABLE, status:VALID,
-
TYPE: APPS.JTF_DATE_TABLE
12.2.2
owner:APPS, object_type:TYPE, object_name:JTF_DATE_TABLE, status:VALID,
-
PACKAGE BODY: APPS.CSP_SCH_INT_PVT_W
12.1.1
-
PACKAGE BODY: APPS.CSP_SCH_INT_PVT_W
12.2.2
-
TYPE: APPS.JTF_VARCHAR2_TABLE_100
12.1.1
owner:APPS, object_type:TYPE, object_name:JTF_VARCHAR2_TABLE_100, status:VALID,
-
TYPE: APPS.JTF_VARCHAR2_TABLE_100
12.2.2
owner:APPS, object_type:TYPE, object_name:JTF_VARCHAR2_TABLE_100, status:VALID,
-
TYPE: APPS.JTF_NUMBER_TABLE
12.2.2
owner:APPS, object_type:TYPE, object_name:JTF_NUMBER_TABLE, status:VALID,
-
TYPE: APPS.JTF_NUMBER_TABLE
12.1.1
owner:APPS, object_type:TYPE, object_name:JTF_NUMBER_TABLE, status:VALID,
-
APPS.CSP_SCH_INT_PVT_W dependencies on CSP_SCH_INT_PVT
12.1.1
-
APPS.CSP_SCH_INT_PVT_W dependencies on CSP_SCH_INT_PVT
12.2.2
-
APPS.CSP_SCH_INT_PVT_W dependencies on JTF_VARCHAR2_TABLE_100
12.2.2
-
SYNONYM: PUBLIC.PLITBLM
12.2.2
owner:PUBLIC, object_type:SYNONYM, object_name:PLITBLM, status:VALID,
-
SYNONYM: PUBLIC.PLITBLM
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:PLITBLM, status:VALID,
-
APPS.CSP_SCH_INT_PVT_W dependencies on JTF_VARCHAR2_TABLE_100
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.CSP_SCH_INT_PVT_W dependencies on JTF_NUMBER_TABLE
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.CSP_SCH_INT_PVT_W dependencies on JTF_NUMBER_TABLE
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
APPS.CSP_SCH_INT_PVT_W dependencies on JTF_VARCHAR2_TABLE_100
12.1.1
-
APPS.CSP_SCH_INT_PVT_W dependencies on JTF_NUMBER_TABLE
12.1.1
-
PACKAGE: APPS.FND_API
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FND_API, status:VALID,
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,