Projects - Transaction Import Standard Integrator Changed With the Custom Package Instead of the Standard Package (Doc ID 2948866.1)

Last updated on MAY 17, 2023

Applies to:

Symptoms

Created a custom integrator for "Projects - Transaction Import" using the 'Duplicate' button.  Modified this custom integrator "Importer" by deleting the existing PL/SQL Procedure - PA_WEBADI_TRX_XFACE and added a custom package in this step.

But when opening the Standard Integrator, it is observed that the "Importer" is showing the custom package instead of the standard package, PA_WEBADI_TRX_XFACE.

-------------------------------

Replication Steps:

1. Creation of the custom integrator. Note that that custom package has been created before starting the creation of the new custom integrator.

a. Navigate to > Desktop Integrator > Desktop Integration Manager > Manage Integrators.
b. In the Integrators page, enter the Integrator Name = Projects - Transaction Import. Click the Go button.
c. In the Select Integrator page, enter Integrator = Projects - Transaction Import. Click the Go button button. Then Choose the Integrator Name = Projects - Transaction Import. Click the Duplicate button.
d. In the Integrator Information page, click the Next button.
e. In the Integrator : Copy of Projects - Transaction Import page, choose the Interface Name. Click the Next button.
f. In the Integrator : Copy of Projects - Transaction Import page, choose the Content Name. Click the Next button.
g. In the Integrator : Copy of Projects - Transaction Import page, add any Uploader Parameters and check any desired options. Click the Next button.
h. In the Integrator : Copy of Projects - Transaction Import page, enter the Importer Name. Click the Define/Update pencil icon for the Rule=PL/SQL API call under the Importer Rules section. In the Integrator : Copy of Projects - Transaction Import page, click the Delete button.
i. Gets back to the Integrator : Copy of Projects - Transaction Import page again. Click the Define/Update pencil icon for the Rule=PL/SQL API call under the Importer Rules section.
j. In the Integrator : Copy of Projects - Transaction Import page, enter in the Package Name, Procedure/Function Name with the custom package name and procedure/function name. Click the Apply button.
k. Back to the Integrator : Copy of Projects - Transaction Import page, see the Package Name with what was entered in the previous step. Click the Apply button.
l. Back to the Integrator : Copy of Projects - Transaction Import page. Click on the Submit button which creates the new custom integrator.

2. Click the Home button.

3. Review the standard integrator.

a. Navigate to > Desktop Integrator > Desktop Integration Manager > Manage Integrators.
b. In the Integrators page, enter the Integrator Name = Projects - Transaction Import. Click the Go button.
c. Click the Integrator Name = Projects - Transaction Import link.
d. In the Integrator Information page, click the Next button.
e. In the Integrator : Projects - Transaction Import page, choose the Interface Name. Click the Next button.
f. In the Integrator : Projects - Transaction Import page, choose the Content Name. Click the Next button.
g. In the Integrator : Projects - Transaction Import page, click the Next button.
h. In the Integrator : Projects - Transaction Import page again. Click the Define/Update pencil icon for the Rule=PL/SQL API call under the Importer Rules section.
i. In the Integrator : Projects - Transaction Import page, see the Package Name field has been changed to the custom package name as identified in step 1j.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.