|
1. File name clarification.
Import: Orders - ref page 6.2 - * Importing
File convention, three file types appear to be defined
DIO?????
OEx?????
ICx?????
DIO????? -> DI = EDI & O = Orders - Sales orders we assume (as purchase
orders & sales order responses are exported) - please confirm.
The files OE* and IC* and even AR* files are ACCPAC specific and you do not need to know anything about these. The DI* files belong to EDI-PAC. Note all these files must be in the same directory to work together - an ACCPAC convention.
The EDI-PAC files
DICxxxxx. are order confirmations created by the order Export function. These files can be used as 856, 855, etc.
DIIxxxx. are Exported invoices (810's) or Exported credit notes (812's).
DIOxxxx. are files of inbound (850) POs to be imported as Order Entry sales orders,
DIPxxxx are Exported POs (850's) from ACCPAC PO.
Return to Top
2. Are file extensions required for any of these files?
The file extensions for all files in ACCPAC and EDI-PAC are very important. They relate to a "company database". In the same directory you may have several company databases. ie DI*.SAM OE*.SAM AR*.SAM and another company such as DI*.DAT OE*.DAT and AR*.DAT. Under the ACCPAC System Manager when setting up each company database the extension as well as a directory is used.
NOTE: The inbound and outbound ascii files to/from EDI-PAC must exist in the proper data directory with the proper extension.
Return to Top
3. What is the file naming convention for exporting Invoices, Sales Order
Response & Purchase Orders.
The following are the naming conventions for the EDI-PAC files;
DICxxxxx. are order confirmations created by the order Export function. These files can be used as 856, 855, etc.
DIIxxxx. are Exported invoices (810's) or Exported credit notes (812's).
DIOxxxx. are files of inbound (850) POs to be imported as Order Entry sales orders,
DIPxxxx are Exported POs (850's) from ACCPAC PO.
Return to Top
4. In Appendix C: O/E Import/Export Format two (2) formats are described:
A) ORDER ENTRY IMPORT/EXPORT FORMAT and
B) P/O EXPORT FORMAT
What is the difference between these?
The ORDER ENTRY IMPORT/EXPORT
FORMAT is used for the importing of sales orders PLUS the exporting of
sales order responses PLUS the exporting of invoices.
The P/O
EXPORT FORMAT is used for exporting purchase orders.
This way it makes it quite easy for the mapper to create inbound POs, outbound confirmations, invoices and credit notes with only 1 format! The contents are obviously important as well as the file names.
Return to Top
5. Define the order of record types in each usage of the ORDER
ENTRY IMPORT/EXPORT FORMAT and advise if multiple messages can be included
in a single file.
Only multiple messages of s single type such as order confirmations, or invoices or inbound POs can exist in a file. The file naming convention determines the document type. See Q1 above. But inbound POs can have simple orders and orders with SDQ segments all in the same file for different trading partners.
It is important to ensure you update your EDI-PAC version as the support for the SDQ types is always improving. In the later versions you no longer need to use the HST type records. Only the DST type for SDQs are required.
For example. using your examples...
i.e. For a simple Sales Orders WITHOUT SDQ segments:
HDR
DET
DET
..
DET
HDR
DET
DET
..
DET
<>
HDR
DET
DST
DST
DET
DST
DST
DST
DET etc.
Return to Top
6. Please define Order Type options - Page C-1
"O, S, F
O= active sales Order S= Standing order, F=future order.
Return to Top
7. Please define Order on Hold options - Page C-1.
I assume 1 = Yes, 0 = No
To rephrase; TRUE=1 FALSE=0
Return to Top
8. Please explain the significance of the "*" character in front of
several of the field names.
These indicate mandatory fields that must be present for a minimum import. There are technical notes and layouts on the product diskette in the \DOC directory. Because the files change more frequently than the manuals, these are most accurate, and should be used in place of the manual.
Return to Top
9. For Item # and Purchase Order # the manual (page c-4) indicates right
justification if only 1 segment defined - otherwise left justified. What
does it mean by segments in this instance?
This refers to how you have defined your ACCPAC IC data item code. Either with multiple segments or with a single large unformatted item number. For a single, large unformatted (1 segment) number, it will be left justified, that way they don't have to provide fillers.
Return to Top
10. Are the fields described as decimals (0, 2 or 4) right justified or
left?
Return to Top
11. For fields not specified, are they left justified?
Return to Top
|
