Solution ID: 200782180 Date Last Revised: 02/14/2008

Title: Inbound Flat File Conversion

(R47002C)
Abstract: The Inbound Flat File Conversion (R47002C) UBE is used to convert an
external flat file into JD Edwards EnterpriseOne EDI or Interoperability tables.

Table of Contents

Overview
Flat File
Work With Flat File Cross-Reference (P47002)
Import Flat File to EnterpriseOne File (B4700240) BSFN
Troubleshooting Errors

Overview
The Inbound Flat File Conversion (R47002C) UBE is used to convert an external flat file
into a PeopleSoft EnterpriseOne EDI or Interoperability tables.

Each EnterpriseOne EDI/Interoperability document has its own unique set of interface
tables. A user can create a separate version of the Inbound Flat File Conversion
(R47002C) for each EDI/Interoperability document. The conversion program recognizes
both the flat file that it is reading from and the record types 00/RD UDC within the flat
file. Each flat file may contain records of differing length based on the
EDI/Interoperability table record that they correspond to. The Inbound Flat File
Conversion (R47002C) UBE uses the Flat File Cross-Reference (F47002) table to
convert the flat file into the EDI/Interoperability interface tables. The Flat File Cross-
Reference (F47002) table identifies which flat file the Inbound Flat File Conversion
(R47002C) UBE should read based on the EDI/Interoperability document that you are
receiving.

The Inbound Flat File Conversion (R47002C) UBE reads each record in the flat file and
maps the record data to each field of the interface tables based on the text qualifiers and
filed delimiters specified in the flat file. It then inserts the field data as one complete
record in the interface table. If the UBE encounters an error while converting data, it
withholds all the data in error and will not insert any records to the interface tables. Since
by definition the flat file is an external object created by third party software there is no
way for the Inbound Flat File Conversion (R47002C) UBE to determine which flat file
data field is formatted incorrectly. It is up to the individual user to determine what is
wrong with the flat file. If the UBE successfully converts all data and transfers it to the
interface tables, it automatically deletes the flat file after the conversion.

Back to Top

Flat File
A flat file is created by third- party software. This software may be in the form of a
Translator or any other third party utility. The Translator is third party software that
converts data from a third-party non-EnterpriseOne application table format to an EDI
Standard format and from the EDI Standard format to an EnterpriseOne application table
format.

To use a flat file to receive EDI/Interoperability documents, a map on a personal

Windows based PC must be created to the location of the flat file.

The format of the record in the flat file must follow the EDI/Interoperability interface
table. This means that every column in the table must be in the flat file record and that the
columns must appear in the same order as in the table. The first field value in the flat file
record indicates the record type. In other words, the first field value indicates the
conversion or creation table into which EDI/Interoperability interface tables to insert the
record.

All fields must be correctly formatted in order for the Inbound Flat File Conversion
(R47002C) UBE to correctly interpret each field and move it to the corresponding field in
the appropriate inbound interface table. This means that all fields must be placed in the
flat file in the exact order that they appear in the inbound interface table that the data is
being converted to. In addition, each field must be enclosed by a symbol that marks the
start and end of the field, typically, this symbol is a double quotation mark (“). Each field
must also be separated from the next field with a field delimiter, typically, this separator
value is a comma (,).

Flat File Support

NOTE: Due to the fact that the flat file is created by third party or Translator software,
Oracle does not support the flat file. It is up to the individual user to correctly format the
flat file.

***Please refer to the Knowledge Garden document "Flat File Creation Procedure"
200782390 on how to create a flat file for Xe/ERP8 from EnterpriseOne tables for use in
testing EDI/Interoperability issues. In 8.9 and above the flat file must be created through
a third party database utility. EDI Data can be manually entered via the various Status
Inquiry Revisions applications associated with a specific EDI transaction set.
Interoperability data can be entered though various Inquiry/Revisions applications
associated with the specific Interoperability process. Once the minimum required fields
are populated in the EDI/Interoperability interface tables and the corresponding
Edit/Update UBE has been run to verify the data is valid, the above document can be
used to create a flat file from data in the interface tables.

***Please refer to the Knowledge Garden document "One World Flat File Formatting"
200782177 for additional information on Flat File Formatting.

Translator Support

Oracle does not currently partner with or support any specific third party Translator
vendor.

Back to Top

Work With Flat File Cross-Reference (P47002)

The Work with Flat File Cross-Reference (P47002) application allows the user to add,
change, or delete Flat File Cross-Reference (F47002) data for EnterpriseOne EDI and
Interoperability processes. It is also used to define the location of the flat file on the
Windows client machine.
Above is an example of the Inbound 850 EDI transaction set.

1. Transaction Type: The specific transaction type stored in 00/TT UDC.

2. Direction Indicator: A code to indicate the direction of the transaction stored in
00/DN UDC.
3. Record Type: Used to mark EDI/Interoperability transaction records as header,
detail, etc. Stored in 00/RD UDC.
4. File Name: A valid EnterpriseOne EDI/Interoperability table.
5. Flat File Name: Path to the flat file on the local Windows PC.

In the detail, the record type and corresponding file names must be defined, along with
the flat file location on a local client machine.

Back to Top

Import Flat File to EnterpriseOne File (B4700240)

BSFN
The purpose of the Import Flat File to EnterpriseOne File (B4700240) BSFN is to import
an external flat file to EnterpriseOne table(s). Maximum length per line is 4095 and the
maximum record type is 40. Every line must have a record. Only one character is allowed
in the record type field and the flat file name and transaction type cannot be blank or
empty. Text Qualifier cannot be equal with Column Delimiter.

Import Flat File to EnterpriseOne File (B4700240) BSFN Support

In the Xe, ERP8, 8.9, and 8.10 releases the Import Flat File to EnterpriseOne File
(B4700240) BSFN and R47002C UBE was designed to run locally on a client machine.
Although EnterpriseOne has successfully tested running this BSFN on various Server
O/S in the past, there are certain variables for testing and server processing that cannot
always be accounted for. For instance, Server O/S changes and the way files are stored in
various O/S. NOTE: Currently Oracle only supports the R47002C UBE when it is run
locally on a Windows machine in the Xe, ERP8, 8.9 and 8.10 releases. In the 8.11 and
above releases Oracle supports running R47002C on the AS400, Linux, Unix, and
Windows server OS.

Technical Information

For specific information on the code see the B4700240.c file in C:\B7\Pathcode\source.
The Inbound Flat File Conversion (R47002C) UBE passes in the following parameters to
Import Flat File to EnterpriseOne File:

BC Name - Flat File -> szNameFlatFile

PO TypeTransaction -> szTypeTransaction
PO FieldDelimiter -> cColDelimiter
PO TextQualifier -> cTxtQualifier
UNDEFINED X cSuppressErrorMessage
VA evt_ErrorCode <- cErrorCode
VA evt_ErrorMessage <- szErrorMessageID

The Import Flat File to EnterpriseOne File (B4700240) BSFN uses the Primary Index
Detail (F98713) table to obtain primary index key detail. The reason for using the
Primary Index Detail (F98713) table is that we are opening a foreign table and the data
needs to formatted correctly prior to being inserted into an EnterpriseOne table. Since
local TAM specs may not exist prior to the opening of the tables referenced in the Flat
File Cross-Reference (F47002) table, the Primary Index Detail (F98713) specs are used.
Normally this table will not have a specific mapping in the System data source and will
fall under the Default Business Data table mapping in the Object Configuration Manager.
Therefore, it is necessary that the Primary Index Detail (F98713) table be mapped in the
System data source or exist in the Business Data data source. To map to the System data
source simply add an OCM mapping in System to point the Primary Index Detail
(F98713) table to the Central Objects data source. To generate the table in Business Data
from Table Design Aid perform the following steps.
From Table Operations click Generate Table.
Enter the correct Business Data data source and click OK.

NOTE: The Inbound Flat File Conversion (R47002C) UBE will not process unless the
above procedure is done correctly.

Back to Top

Troubleshooting Errors
This section lists the possible errors that can be encountered and written to the Work
Center when running the Inbound Flat File Conversion (R47002C) UBE.

Error
EnterpriseOne Description Cause/Resolution
Message
 Error 3003 Cause . . . . One or more of the
master files required for the
“Open of File execution of this program failed to
Unsuccessful” open successfully.
Resolution . . Please exit this
program and contact your
Operations department to have the verify the flat file name specified in
appropriate file(s) created in your the Flat File Cross-Reference
environment.
Error 128J CAUSE . . . . Insert failed for the
Record with the key fields &1
“FXXXX under one of the following
Insert Failed” conditions :
- Duplicate Key fields
- Fields have special characters
- Fields are not of the correct data
type
RESOLUTION. . Verify you have
right values for all the fields.
Error 0073 CAUSE . . . . The file name
entered does not exist in the
“Invalid File Software Versions Master file
Name” (F9801), does not exist in any
library for your user library list or
you are not authorized to the
specified file.
RESOLUTION. . Verify the file
name and reenter if necessary.
Error 4569 CAUSE. . . . An attempt was
made to load a program with an
“Invalid incorrect format.
Format”
RESOLUTION. . Check format.
The flat file cannot be opened in its
specified location in the Windows
directory. The Import Flat File to
EnterpriseOne File (B4700240)
business function uses a standard
ANSI C 'fopen' function to access the
flat file. If you receive this error
(P47002) table matches the flat file
name in the Windows directory.
Verify Windows OS settings are not
hiding file extensions or protecting
files. Contact your System
Administrator for assistance.
A database error occurred inserting to
a table. Review JDE.log for specific
cause and correct as necessary.
A table specified in the Flat File
Cross-Reference (P47002) record
does not exist in One World. Review
data in the Flat File Cross-Reference
(P47002) table and correct as
necessary.
The flat file being accessed contains
an invalid format and is not
formatted correctly. Verify the flat
file format matches that of the
EnterpriseOne table format.
PeopleSoft does not support the third
 party flat file and will not be able to
ascertain what is wrong. However
PeopleSoft can provide a standard
EDI 850 flat file to test with.

File Extensions are Hidden

From Start/Settings/Control Panel/Folder Options go to the View tab Hide file extension.
If this is checked the set up should be as follows.

No extensions showing in Windows Explorer.

The Flat File Cross-Reference (P47002) must have the extension listed or an “Open of
File Unsuccessful” error will occur.
Back to Top