Failed FBDI Import records lack process/request Id, hindering batch traceability — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood: Oracle Cloud SCM and Purchasing

Failed FBDI Import records lack process/request Id, hindering batch traceability

in Supply Chain Planning and Collaboration 1 comment

While importing work order supplies details using the FBDI bulk import process by submitting the ESS Job, we are unable to find the process ID or Request ID in the interface table for the failed records. As a result, it is difficult to identify the corresponding batch associated with the failures.

 

Import Process: Supply information (Work Order Information) Import.

ESS Job Name: Load Interface File for Import

FBDI Oracle documentation Link: Supply Chain Planning Work Order Supplies

FBDI Template: ScpWorkOrderSuppliesImportTemplate.xlsms

JobPackageName: oracle/apps/ess/scm/advancedPlanning/collection/configuration

JobDefName: CSVController

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!