iProcurement Bulk Loader from an ATG/FND Perspective
(Doc ID 281530.1)
Last updated on AUGUST 25, 2021
Applies to:Oracle Concurrent Processing - Version 11.5.8 to 22.214.171.124 [Release 11.5]
Oracle E-Business Suite Technology Stack - Version 11.5.8 to 126.96.36.199 [Release 11.5 to 11.5.10]
Information in this document applies to any platform.
***Checked for relevance on 07-Dec-2012***
The purpose of this note is to describe how the Internet Procurement process 'Bulk Load Items & Price Lists' is intended to work from an ATG/FND perspective. While the general nature of this process is a functional, Internet Procurement issue, many of the reasons for the failure of this process are based on the underlying ATG/FND code or system configurations best analyzed by ATG/FND support engineers. Until now, documentation on the ATG aspect of this process has been sparse and has made troubleshooting difficult. This note, though lengthy, should make troubleshooting easier by providing an understanding of how each block of code works. As a minimum, the note provides a basic flow diagram to identify specifically where the process fails as an aid in logging a bug with Oracle Development should it be found necessary to do so.
Typically we see this class of problems in the concurrent request log with the following general format:
This paper does not cover problems with the actual parsing of the catalog/price list data. If the catalog data file is readable and cleanly moved from the web tier to the concurrent manager tier, then it is likely that only product specific problems remain. In those cases, the following note is useful:
<Note:558273.1>-How to Diagnose Issues in Bulkloading Items in iProcurement
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!