FA:SCM:PIM - Using UCM File From EBS and Run ESS Use Schedule Project Upload Job To Update Items in PIM/PDH (Doc ID 2718153.1)

Last updated on MAY 18, 2023

Applies to:

Symptoms

Scenario - Business in using the Oracle File Transfer Utility that is bundled in an EBS concurrent request

Clear and concise description of the business scenario: Business uses the Schedule Project Upload job to update a couple of item attributes. The ESS job has used the same file revision from UCM despite a new revision being uploaded to UCM twice a day. This is occurring for 2 of 2 import processes.

The major point of concern is the ESS Job or the Manage Item Batches is processing the 1st file every time. The 2nd and 3rd files were not imported.

User went through 3 cycles of uploading a file to UCM and having the ESS job process the file. Every file the user uploaded to UCM had different item counts. The files that were uploaded begin with TEST_EBS_PDH. The user added the 01 and 02 and 03 because they upload the same file name (and have for past 3 years and are required to do so as it has to match the manifest files also stored in UCM and called as a parameter). When you look at the item batches that processed you will see that the same 140 record file was process every time (Minus the 1 item that didn't exist).

When you look at the manage item batches that were process, there are 3 import batches that shows a record count of 140 for each batch, even when each batch should have different record counts. How can 3 import batches that should have imported different record counts, all show 140 records?

In TEST_EBS_PDH 01 upload.csv, there are 140 records.

In file TEST_EBS_PDH 02 upload.csv, there are 137 records.

In file TEST_EBS_PDH 03 upload.csv, there are 112 records in file.

Note - ESS Job is ran before uploading another file.

Changes

 Upgrade to 20C

Cause

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