Search Results update_claims

Overview

The APPS.DPP_BPEL_UPDATECLAIM package is a technical wrapper generated to expose the claims update capability of the Oracle E-Business Suite Demand Planning and Procurement (DPP) module through a BPEL (Business Process Execution Language) web service interface. Its purpose is to bridge the strongly typed PL/SQL record and collection structures used internally by the DPP claims processing private package (DPP_CLAIMS_PVT) with the flattened SQL types that can be marshalled across a SOAP/BPEL boundary for external systems integration. In EBS Release 12.1.1 and 12.2.2 this package is part of the ETRM integration layer that allows external applications — typically procurement or supplier-facing systems — to submit claim header and claim line updates into the planning tables derived from the PLITBLM family.

Key Procedures and Functions

The package declares seven documented program units, six of which are PL/SQL-to-SQL conversion functions and one of which is the actual business API entry point.

• PL_TO_SQL6 / SQL_TO_PL6 — Conversion functions for the DPP_CLAIMS_PVT.DPP_TXN_HDR_REC_TYPE record. They map the internal claims transaction header record to and from the SQL type DPP_CLAIMS_PVT_DPP_TXN_HDR_R4, enabling the header structure to be passed through the BPEL interface.
• PL_TO_SQL8 / SQL_TO_PL8 — Conversion functions for the DPP_CLAIMS_PVT.DPP_TXN_LINE_REC_TYPE record, mapping to and from DPP_CLAIMS_PVT_DPP_TXN_LINE_6. These handle individual claim line records.
• PL_TO_SQL7 / SQL_TO_PL7 — Conversion functions for the DPP_CLAIMS_PVT.DPP_TXN_LINE_TBL_TYPE collection, mapping to and from its SQL counterpart DPP_CLAIMS_PVT_DPP_TXN_LINE_5. These handle the nested table of claim lines submitted with a header.
• DPP_CLAIMS_PVT$UPDATE_CLAIMS — The public wrapper procedure around the private DPP_CLAIMS_PVT.UPDATE_CLAIMS logic. It accepts the standard EBS API parameters (P_API_VERSION, P_INIT_MSG_LIST, P_COMMIT, P_VALIDATION_LEVEL) together with the standard out parameters (X_RETURN_STATUS, X_MSG_COUNT, X_MSG_DATA), and takes the header record and line table as IN OUT NOCOPY parameters. This allows a caller or a BPEL partner link to pass in, validate, and persist modified claim transactions.

Tables Accessed

The only table documented against this package is PLITBLM, referenced via an APPS synonym. PLITBLM is the interface (staging) table used by Oracle Advanced Planning and related DPP modules to receive inbound planning and procurement data before it is validated and moved through the module's business logic. In the context of this package, the wrapper reads and updates claims-related staging rows so that approved claim header and line changes can be applied. The actual persistence into destination claim and planning tables happens inside DPP_CLAIMS_PVT.UPDATE_CLAIMS, which the wrapper delegates to.

Usage Notes

This package is a generated BPEL bridge, not a called-by-form API. It is intended for integration scenarios in which an external system invokes a web service to update claim data. Typical invocation is through the DPP BPEL process definition, which imports the SQL types and calls DPP_CLAIMS_PVT$UPDATE_CLAIMS, passing the converted header and line structures.

• The wrapper should not be called directly from Oracle Forms or standard concurrent programs; those paths call DPP_CLAIMS_PVT directly.
• Custom code that must invoke the update from PL/SQL should call DPP_CLAIMS_PVT.UPDATE_CLAIMS using the native DPP_TXN_HDR_REC_TYPE and DPP_TXN_LINE_TBL_TYPE structures rather than the SQL-converted equivalents used here.
• The P_COMMIT parameter controls transactional scope; in an integration context it is normally set so the BPEL process retains control of commit boundaries across multiple claim updates.
• Validation behaviour is governed by P_VALIDATION_LEVEL and P_INIT_MSG_LIST, and any errors are returned through the standard X_RETURN_STATUS / X_MSG_DATA pair for the calling BPEL process to interpret.