BISAC

Electronic Commerce Protocols

BISAC ECP Operational Protocol for Naming Conventions 

Back to EDI Cookbook Table of Contents

Overview

To establish a standard operating protocol for exchange on data files by using a standard naming convention which will be associated with a rule for processing. This will allow simple and standard exchange of data without conflict or lost of data.

File Naming Structure

To be compatible with older systems, we recommend the use of the eight dot three which is broken down by file name of eight bytes and the extension of three bytes.

Example: 8.3 Standard File Naming Convention or Extended File Naming Convention


File Name =
         vvvvvvvv.SFT (8.3 Standard File Naming Convention)
         variable.SFTTTTTT (Extended Naming Convention)
         vvvvvvvv Variable Unique Name Example: (MMDDhhmm)

                       S - Status Byte
                         F - Format Indicator
                           T - Transaction Type
Status Byte:
X = In the process of being transmitted/created (Sender)
C = Transmit/Create completed (Sender)
R = Receive in Process (Receiver)
E = Extraction Completed (Receiver)
A = Archive in Process (Receiver)
Format Indicator, BISAC:
X = X12
E = EDI+EUR *EDIFACT
F = Fixed Format
P = Proprietary
Transaction Types
Type Description X12 EDI+EUR Fixed Proprietary
P Purchase Order 850 ORDERS PO Mutually
A PO Confirmation 855 ORDRSP POA Defined
I Invoice 810 INVOIC INV -
T Title/Status 832 PRICAT TLS -
S Ship Notice 856 DESADV SHP -
B Bill&Ship Notice 857 - - -
C Chain Store Addresses 885 - - -
F Functional Ack 997 - - -
R Sales Reporting 852 - - -
Business Example (8.3 file naming convention)
In Trading Partner's Sub Directory on server
12141213.XXP Sender is transmitting an 850.
Don't touch.		 Sender Renames to C.
12141213.CXP 850 Sent successfully.
Okay for receiver to process.		 Receiver Renames to R.
12141213.RXP Receiver in process of receiving this file.
 		 Receiver Renames to E.
12141213.EXP Receiver has successfully extracted data
from file.		 Receiver Renames to A.
12141213.AXP File is ready for archive.

Rules
X   Files can only be touched by Sender.
C   Files can only be renamed to R.
R   Files can only be touched by receiver and must be renamed to E.
E   Files can only be renamed to A archive and deletion.
Business Example (Extended File Naming)
In Trading Partner's Sub Directory on server
R1214121301.XX850 Sender is transmitting an 850.
Don't touch.		 Sender Renames to C.
R1214121301.CX850 850 Sent successfully.
Okay for receiver to process.		 Receiver Renames to R.
R1214121301.RX850 Receiver in process of receiving this file.
 		 Receiver Renames to E.
R1214121301.EX850 Receiver has successfully extracted data from file. Receiver Renames to A.
R1214121301.AX850 File is ready for archive.

Rules
X   Files can only be touched by Sender.
C   Files can only be renamed to R.
R   Files can only be touched by receiver and must be renamed to E.
E   Files can only be renamed to A archive and deletion.

Back to EDI Cookbook Table of Contents