EDI.LOG File
Reading the EDI.LOG file
The following table describes the data elements within the EDI.LOG file:
| Column Header |
Data |
| Trans Dt Time |
the date and time of
the entry |
| # of POs |
the number of documents |
| # of Lines |
the number of line
items in the file |
| Set/Run# |
file sent in Test or
Production mode / Run Number of the transaction |
| Trade Partner |
3 character trading
partner code for the document sender/recipient |
| Create Dt |
the document creation
date MMDDYY |
| Control# |
the EDI control number
used to identify the file as it travels across the network |
| Type |
the type of file being
sent or received |
| Vrs |
the software version
that translated the file |
| FileSize |
the byte size of the
file - can be used to reconcile your network charges |
Verify PO's and Functional Acknowledgements
The example below is a sample entry from the EDI.LOG file:
Trans Dt Time
# of PO's # of Lines
Set\Run# Trade Partner
Create Dt Control#
TYPE Vrs FileSize
02-04-05 10:50 AM Fri 02041 6
186 P 850\614
PUB ING 1697978P 050201 000000518
PO 10.60 19968
02-04-05 10:50 AM Fri FA
Sent to ING Using ICC |
Confirm PO's Have Not Been Received
The example below indicates that the ftp connection to the mailbox was
successful and there were no orders from Baker & Taylor to pull:
| 02-08-05 11:46 AM Tue Run
Number: 616 No new Purchase Orders received from BAK
Using ICC |
Verify POA's
The example below shows the successful transmission of a POA to Ingram:
Trans Dt Time
# of PO's # of Lines
Set\Run# Trade Partner
Create Dt Control#
TYPE Vrs FileSize
12-05-03 01:07 PM Fri 2
97
P 855\260 PUB ING 1697978P
031205 002600002 POA 8.76
13496
12-05-03 01:07 PM Fri POA Sent to ING |
Troubleshoot EDI Document Transmission Problems
Failed transmissions are noted in the EDI.LOG file:
04-18-05 09:28 AM Mon
Run Number: 2503 No new Purchase Orders received from
ING Using ICC
04-19-05 01:02 PM Tue E R R O R ! : Not connected.
See ICC850.log |
