OBIA 11g: After Oracle Spend Classification(OSC) with Procurement & Spend Analytics Integration, Uploading Dataset Files in [.CSV] Format Failed with Error: "Following EBS Auto Codes specified in Input File do not exist in Taxonomy"
(Doc ID 2428132.1)
Last updated on FEBRUARY 17, 2019
Applies to:Business Intelligence Applications Consumer - Version 18.104.22.168.1 and later
Information in this document applies to any platform.
On Oracle Business Intelligence Applications Consumer 22.214.171.124.1 version,
- The following document has been used for integrating Oracle Spend Classification(SC) 7.9.6.x with Oracle Procurement and Spend Analytics 126.96.36.199.x -->
OBIA 7x/11g : Clarification of the Taxonomy Administration in Spend Classification (Doc ID 1914095.1).
- After integration, trying to upload the sample dataset files (in Analytics -> Spend Classification -> Datasets) to sync EBS source for taxonomy.
- For e.g., 'Input File' - 'EBS Auto Code' values have the data in the following format and all the values are enclosed with double quotes - "Legal, Regulatory & Audit.Legal.General Legal Costs".
- When uploading the dataset, the below error messages are encountered for different dataset file formats.
When the delimiter -"Comma" is removed in the value of 'EBS Auto Code', [.TXT] & [.CSV] files are uploaded successfully without any issues.
Why the following file formats - [.XLS], [.TXT] & [.CSV] having 'Comma Separated Delimiter' throwing error in OBIA 11g?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document