Results for “oep_cmerge_oepic”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OEP_CMERGE_OEPIC is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified in the ETRM repository under the generic API category OTHER. Its name follows the Oracle Applications naming convention for customer merge subprocessors: the OEP prefix associates it with Oracle Order Entry / Order Management, CMERGE denotes customer merge processing, and the OEPIC suffix identifies the specific merge step it performs for the Order Entry module. The package is declared AUTHID CURRENT_USER, meaning that at runtime its unqualified object references resolve through the privileges of the invoking schema rather than through the definer's privileges. The header comment "$Header: oepicps.pls 115.0 99/07/16 08:27:57 porting ship $"indicates an original porting-era source file that has been carried forward with minimal modification into the 12.1.1 and 12.2.2 code lines.

The package exists to satisfy a narrow but essential requirement in the Oracle Customer Merge (CMERGE) framework: when a source customer or site is merged into a target customer or site, order entry data that references the source party must be re-pointed to the target party. OEP_CMERGE_OEPIC participates in that orchestration as a subprocess callable from the central customer merge driver.

Key Procedures and Functions

The package exposes exactly one documented program unit:

• MERGE — The single public procedure of the package, declared in the specification as accepting a request identifier, a set number, and a process mode flag. The request identifier links the invocation to a specific customer merge request tracked by the merge framework; the set number distinguishes one batch or work set of merge candidates from another within the same request; and the process mode governs whether the procedure performs its work or reports what it would do. The procedure's purpose is to apply the order entry side of the merge, updating or reconciling order entry references that point at the source entity so they instead reference the surviving target entity. No other procedures or functions are documented for this package, and its specification requires no additional visible API surface.

Tables Accessed

ETRM records that the package references the following objects through APPS synonyms:

• RA_CUSTOMER_MERGES — The central customer merge transactions table. This table stores the pairing of source and target entities together with processing state for each merge request. OEP_CMERGE_OEPIC reads it to determine the source and target customer or site for the request identified by the incoming parameters, and may update rows to reflect that the order entry portion of the merge has completed.
• SO_PICKING_RULES — The order management picking rules table. Because picking rules can be defined at customer or site level, merges must consolidate or re-point such rules so that shipping and picking behavior for the target customer remains correct after the merge.

Usage Notes

OEP_CMERGE_OEPIC is not intended for direct invocation by end users or by arbitrary custom code. It is a component of the Oracle Customer Merge processing framework, which in Oracle EBS is driven either from the Customers standard form when a user submits a customer merge, or through the customer merge concurrent programs that process queued merge requests. The same package typically appears as a registered subprocess in the merge framework's list of target application hooks, and ETRM records that it is referenced by one other package, consistent with a driver package calling MERGE with the appropriate request identifier, set number, and process mode.

Because the audit trail of a customer merge is permanent and difficult to reverse, integrators should treat this package as internal infrastructure. Custom code that needs a test pass of order entry merge logic can invoke it in the non-updating process mode, but production executions must be triggered only through the sanctioned merge framework. Any direct call must supply a valid request identifier and set number, or the procedure will have no eligible rows to process.