Search Results get_sr_info
Overview
CS_SERVICEREQUEST_PUB_W is the published wrapper package for the Oracle E-Business Suite Service Request (SR) API. It exposes a stable, callable interface over the internal CS_SERVICEREQUEST_PUB package, allowing external and custom code to create, modify, and update the status of service requests without depending on internal implementation details. The package is owned by APPS and is classified as a public API (OTHER). It exists primarily in Service (TeleService / Depot Repair / Field Service) installations where service requests are the core transactional entity. The "_W" suffix indicates the thin generated wrapper layer that performs datatype conversion between Java (via JTF typed tables) and PL/SQL, which is characteristic of Oracle's Rosetta-based integration infrastructure introduced for Java/BC4J interoperability.
Key Procedures and Functions
The documented package surface comprises 25 procedures. These divide into two functional groups.
- Rosetta table copy procedures (ROSETTA_TABLE_COPY_IN_P1 through _OUT_P19): These paired procedures translate between Java-side JTF collection types (JTF_VARCHAR2_TABLE_2000, JTF_VARCHAR2_TABLE_32767, JTF_VARCHAR2_TABLE_300, JTF_VARCHAR2_TABLE_100, JTF_NUMBER_TABLE, JTF_DATE_TABLE) and the PL/SQL record structures defined in CS_SERVICEREQUEST_PUB. The _IN variants marshal flat JTF arrays into nested tables such as the NOTES_TABLE, CONTACTS_TABLE, and EXT_ATTR_GRP_TBL_TYPE; the _OUT variants reverse the transformation. Each numbered group corresponds to a specific parameter set on the business procedures.
- Business API procedures: INITIALIZE_REC prepares a service request record for population; CREATE_SERVICEREQUEST inserts a new SR; UPDATE_SERVICEREQUEST modifies an existing SR; UPDATE_STATUS transitions an SR through its lifecycle status codes. These four procedures form the public transaction surface used by callers, with the Rosetta procedures supporting them behind the scenes.
Tables Accessed
The package references PLITBLM, an APPS synonym for a PL/SQL index-by and nested-table support structure used by the Rosetta marshalling layer to hold intermediate collection data during conversion. The substantive SR tables (CS_INCIDENTS_ALL, CS_INCIDENTS_B, CS_SR_CONTACTS, and notes tables) are accessed through the underlying CS_SERVICEREQUEST_PUB package rather than directly here; the wrapper itself is a thin conversion layer.
Usage Notes
CS_SERVICEREQUEST_PUB_W is typically invoked in three scenarios. First, from the Oracle Service forms when a user saves or updates an SR, where the form triggers the wrapper through the BC4J middle tier. Second, from Java or JDeveloper integrations that require SR creation via JTF-typed collections. Third, from custom PL/SQL code that needs a supported, upgrade-safe entry point. Because the "_W" layer is generated, modifications are not supported; developers must extend the internal CS_SERVICEREQUEST_PUB instead. Direct calls require populating the JTF tables, executing CREATE_SERVICEREQUEST or UPDATE_SERVICEREQUEST, and committing. Only one other package is documented as referencing this wrapper, confirming its narrow, integration-oriented role. Note that the AUTHID CURRENT_USER clause means resolution depends on the invoker's schema privileges against APPS synonyms.