Translator for use in an automated order entry system

Abstract

Translations for data structures for transferring catalog and system order information between a manufacturer and a customer. The translations and data structures are configured to allow custom systems to be automatically ordered where the manufacturer and customer use different file formats. These translations and data structures advantageously allow a manufacturer and customer to electronically order systems, and specifically, non-commodity systems, quickly and easily.

Claims

What is claimed is:

1. A method for translating a data structure for providing a catalog from a manufacturer to a customer from a first file to a second file format so as to enable a customer to perform an automated order entry process, the first file format and the second file format being encoded on compute readable media, the method comprising:

translating a catalog header portion from the first file format to a corresponding set of elements in the second file format;

translating a system identification portion from the first file format to a corresponding set of elements it the second file form a, the system identification portion including a system type indicator, the system type indicator inhabiting weather a system is a bundled system or a custom system;

a system effective date element, the system effective date element indicating an effective date that a particular configuration is allowed to be purchased;

a system discontinue data element, the system discontinue date element indicating a data by which a system is to be discouraged; and,

translating a system option portion from the firs file format to a corresponding set of elements in the second file format.

2. The method of claim 1, wherein the firm file format is a proprietary file format and the second file format is an industry standard file format.

3. The method of claim 2, wherein the second file format substantially conforms to an electronic data interchange (EDI) format.

4. The method of claim 1 wherein the system identification portion includes a plurality of business rule elements that apply to a particular system.

5. The method of claim 4 wherein the plurality of business rule elements include a system identification element, the system identification element providing a manufacture assigned unique identifier.

6. The method of claim 4 wherein the plurality of business rule elements include the system identification effective date element, the system identification effective date element providing an effective date that a particular configuration is allowed to be purchased.

7. The method of claim 4 wherein the plurality of business rule elements include a system of identification action element, the system identification action element programmable informing a customer what function to perform a system.

8. The method of claim 7 wherein the functions to be performed include an add function, a replace function and a discontinue function.

9. The method of claim 1 wherein the system option portion includes a plurality of relationship indicator elements.

10. The method of claim 9 wherein the plurality of relationship indicator elements include a relationship identification element, the relationship identification element providing an indicator that communicates for a component, a relationship of the component to other components.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to automated order entry systems and more particularly to translators for use in automated order entry systems.

2. Description of the Related Art

Electronic commerce, or e-commerce includes the transfer of orders or other sales communications, credit information, electronic "funds", and digital products. Electronic commerce provides speed and convenience to many types of commercial activities. Interest in electronic commerce has heightened with the advent of widely accessible communication systems such as the Internet. Other types of electronic commerce include direct telephone line connections, interactive cable or television services, facsimile services, local and wide area network communications and the like. Electronic data communications technologies, particularly the Internet, have greatly enhanced marketing and retail opportunities and activities.

Electronic commerce has not been fully realized. There is a need to incorporate electronic communications technologies to synchronize customer interactions with businesses. More specifically, electronic commerce capabilities need to be expanded to synchronize business relationships with customers. For example, present electronic commerce businesses do not provide customers with the capability of configuring non-commodity items such as services and configuration options that permit a customer to create a product and order the product so created. Additionally, electronic commerce presently fails to provide cohesive, integrated manufacturing processes that automate customer relationships.

SUMMARY OF THE INVENTION

In accordance with the present invention, translations for data structures for transferring catalog and system order information between a manufacturer and a customer are shown. The translations and data structures are configured to allow custom systems to be automatically ordered where the manufacturer and customer use different file formats. These translations and data structures advantageously allow a manufacturer and customer to electronically order systems, and specifically, non-commodity systems, quickly and easily.

More specifically, in one aspect the invention relates to A method for translating a data structure for providing a catalog from a manufacturer to a customer from a first file format to a second file format. The method includes: translating a catalog header portion from the first file format to a corresponding set of elements in the second file format; translating a system identification portion from the first file format to a corresponding set of elements in the second file format; and; translating a system option portion from the first file format to a corresponding set of elements in the second file format. The system identification portion includes a system type indicator, the system type indicator indicating whether a system is a bundled system or a custom system.

In another aspect, the invention relates to A method for translating a data structure to a first file format from a second file format for providing an order to a manufacturer from a customer using a catalog that includes custom systems. The method includes: translating a plurality of elements in the second format to an order header portion in the first format; translating a plurality of elements in a second format to an order detail portion in the first format; and, translating a plurality of elements in the second format to an option detail portion in the first format. The order detail portion includes information about a specific configuration for the order. The option detail portion includes information allowing ordering of a custom system.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numbers objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.

FIG. 1 is a block diagram of a computer system in accordance with an embodiment of the invention.

FIG. 2 is a block diagram of a computer server network including a communication medium in accordance with an embodiment of the invention.

FIG. 3 is a block diagram of an automated order entry process in accordance with several embodiments of the invention.

FIG. 4 is a block diagram of the data structures of the automated order entry process of FIG. 3.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to a person of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.

FIG. 1 illustrates a block diagram of a computer system 100 upon which an embodiment of the present invention may be implemented. Computer system 100 includes a bus 101 or other communication mechanism for communicating information, and a processor 102 coupled to bus 101 for processing information. Computer system 100 further comprises a memory dynamic storage 104 coupled to bus 101 for storing information and instructions to be executed by processor 102. Computer system 100 also includes a read only memory (ROM) and/or other static storage device 106 coupled to bus 101 for storing static information and instructions for processor 102. A data storage device 107, such as a magnetic disk or optical disk, is coupled to bus 101 for storing information and instructions.

Computer system 100 may also be coupled via bus 101 to a display device 121, such as a cathode ray tube (CRT), for displaying information to a computer user. Optionally, computer system 100 operates as a computer server or as a computer system coupled to a computer server. An input device 122, including alphanumeric and other keys, is typically coupled to bus 101 for communicating information and command selections to processor 102. Another type of user input device is cursor control 123, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 102 and for controlling cursor movement on display 121.

Referring now to FIG. 2, computer system 100 is shown coupled to communication medium 250, which may be a multi-point network, a point-to-point communications link, etc. any of type of circuit-style network link capable of transferring data. Communication medium 250 may be an X0.25 circuit, a physical type of line, such as a T1 or E1 line, or an electronic industry association (EIA) 232 (RS-232) serial line. In addition, communication medium 250 may utilize a fiber optic cable, twisted pair conductors, coaxial cable, or a wireless communication system, such as a microwave communication system. Coupled to communication medium 250 is database server 200, which, according to an embodiment of the present invention, provides data across communication medium 250 to a plurality of servers, shown as servers 252, 254, 256 and 258. In an embodiment of the invention, servers 252, 254, 256 and 258 each represent servers of a customer or a third party in communication with customers via communication medium 250. For example, server 258 is shown further coupled to customer server 260 and customer server 262.

OVERVIEW

The present invention is related to the use of computer systems and servers to facilitate and automate a manufacturing process, the process, hereinafter referred to as an Automated Order Entry (AoE) process, is outlined in FIG. 3. Referring to FIG. 3, the manufacturing process is shown including communication with customers via the communication medium 250 and server 200. The AoE process first includes creation of a data file 310 for transport via the communication medium 250. The data file 310 includes an electronic catalog suited for one or more customers. The catalog allows customers (as well as suppliers or third parties) to host the data and configure both commodity and non-commodity products and services, as explained in further detail below. The term "customer" or "customer hosted" includes third parties acting on behalf of a customer, supplier or manufacturer and hosting on behalf of the customer, supplier or manufacturer

FIG. 3 shows a data file 310 including an electronic catalog transmitted from server 200 to a customer server 254. The data file is in a structured data format which is one of a proprietary format (PFF), EDI (Electronic Data Interchange) format, an SGML (Structured General Markup Language), such as XML (eXtensible Markup Language) or HTML, or another format familiar to persons of ordinary skill in the art. Data file 310 is in an industry supported communication protocol. For example, the data optionally may be configured to be transferred via a "value added network type protocol," or be configured for a direct connection with a customer via a T1 line, such as a direct "pipe" line, or be configured for a TCP/IP protocol. The data file 310 is optionally first translated in translator 320 to an industry standard format, such as Electronic Data Interchange (EDI), or, if not translated, transmitted in a proprietary format to customer server 254. The customer server receives data file 310 and acknowledges non-commodity or commodity product in the data file 310 using acknowledgement file 336.

The AoE process continues on the customer server 254, wherein the data file enables the customer to host data file 310 and create orders, including internal purchase orders and files for transport to the manufacturer server 200. The customer transmits the order file 338 via communication medium 250 to manufacturer server 200. The order file 338 is optionally translated via translator 330 to an industry standard format prior to transmitting the order file 338 via the communication medium 250. The manufacturer receives either a proprietary file format or an industry standard format order file 338. If the order file 338 is in an industry standard format, the order file is first translated in translator 320. The manufacturer acknowledges the order file 338, process the order file 338, thereby validating the order via order acknowledgement file 340. Acknowledgement file 340 is transmitted via communication medium 250 to customer server 254, and is optionally translated into an industry standard format in translator 320, and translated into a proprietary file format by the customer in translator 330.

The AoE process further includes an inventory control process by which appropriate data feeds inventory control process 360. In one embodiment, the catalog acknowledgement file 336, indicates whether the data file including the electronic catalog 310 was `accepted` by the customer. If accepted, the data file 310 is made available by AoE server 200 within the AoE process to the inventory control process 360 to ensure appropriate inventory levels for products included in the electronic catalog that fall within a predetermined category of products. In another embodiment, the acknowledgement file 336 is not required to begin the inventory control process. For example, customers that lack the capability to send acknowledgment files. Such customers optionally may acknowledge and verify data files by other methods, such as a telephone call. Accordingly, in another embodiment, the inventory control process begins upon creation of the catalog or at other appropriate junctions within the manufacturing process. For example, certain catalogs include products that can be "bundled" as pre-built components, and other catalogs include products that are non-commodity type configurable products. Yet other catalogs include a mixture of both types of products. Each of these types of catalogs may be made available to the inventory control process.

FIG. 4 sets forth the flow of data structures to a customer from a manufacturer and to the manufacturer from a customer. More specifically, a Catalog data structure 400 is generated by AoE server Database 200 in a PFF. The Catalog data structure is then translated from the PFF data structure to an industry standard format. This data structure is transmitted to the customer via transmission medium 250. The customer then acknowledges receipt of the Catalog with a Catalog Acknowledgement data structure 402. The Catalog Acknowledgement data structure 402 is translated from an industry standard format to a PFF via translator 320. If, for a particular customer, no acknowledgement is required, then the customer can proceed directly with ordering from the catalog after receipt of the catalog. In either case, the next step is the generation of an Order data structure 404 by the customer. The Order data structure is transmitted to the manufacturer using an industry standard format. The Order data structure is translated from the industry standard format to a PFF via translator 320. Once the Order data structure is processed, then the manufacturer may optionally generate and provide an Order Acknowledgement data structure 406 to the customer. It will be appreciated that additional variations on this flow may be used by those skilled in the art. For example, order cancel/change data structures and order cancel/change acknowledgement data structures may also be used in this flow.

DATA STRUCTURES AND TRANSLATIONS

The following data structures and translations show the operation of translator 320 as well as the data structures that are transmitted via communication medium 250.

More specifically, Table 1 sets forth the proprietary file format (PFF) data structure and translation to an EDI format for a Catalog data structure 400. In Table 1 (as well as throughout the other Tables), the EDI structures are set forth on the left and the corresponding PFF structure are set forth on the right. For example, the EDI structure BCT.01 corresponds to and is translated from the PFF structure Catalog Type, the EDI structure BCT.02 corresponds to and is translated from the PFF structure Catalog Version Number, etc . . . . Translator 320 performs the translation for each data structure that is provided to communication medium 250.

    TABLE 1
    File name =
        CUSTOMERUSA + Date (ccyymmdd) + Sequence number + extension
        Example: CUSTOMERUSA199808313.CAT
    File Wrapper:
    Record tag: RTG
        From source: string length 30 ("DELLUSA")
        To destination: string length 10 ("CUSTOMERUSA")
        File type: string 15 ("CATALOG")
    Catalog Header (occurs once for each catalog file):
    Record tag:CAT
    BCT.01        Catalog Type: (string length 1 - value D = Delta).
    BCT.02        Catalog Version Number: (number length 4 - values 1 to 9999).
    DTM.02        Catalog Date: (string length 10 - format mm/dd/yyyy).
    DTM.03        Catalog Time: (string length 8 - format hh:mm:ss).
    DTM.04        Catalog Time Code (string length 2 - value CS = Central
     Standard Time)
    CUR.02(1)     Currency: (string length 3 - values USD or CAN).
    CUR.03(1)     Exchange Rate: (number 10)
    CUR.02(2)     Exchange From Currency/To Currency: (string length 3)
    PER.02        Catalog Contact: Dell Sales (string length 32 - i.e.: Stephan
     Moran).
    PER.04        Catalog Contact phone number (number length 10 - format
     9999999999).
    System ID record (occurs once for each system type):
    Record tag: SVS
    LIN.01        Loop Counter: number length 5 (sequential counter).
    LIN.03        System ID: (number length 9 - values 1 to 999999999; Dell
     assigned).
    LIN.05        System ID Text description: (string length 30, "POWER
     PORTABLE
                  BUNDLE").
    DTM.02(1)     System ID Effective Date: (string length 10 - format
     mm/dd/yyyy).
    G53.01        System ID Action: (string length 1 - values A = Add, R =
     Replace, D =
                  Discontinue).
    REF.02        Replace Old System ID: (number length 9 - values 1 to
     999999999).
                  Note: When System Action = R
    CTP.03(1)     System ID Purchase Price: (number length 10 - values .01 to
     9999999.99).
    CTP.03(2)     Default Shipping Price: (number length 10 - values .01 to
     9999999.99).
                  Note: If shipping is built into system ID.
    TXI.02        Sales Tax Amount: (number length 10 - values .01 to
     9999999.99).
                  Note: If sales tax is built into system ID.
    C00101(CTP)   System Type: (string length 3 - values BNL = Bundle, CUS =
     custom).
    PID.05(1-6)   System Specification Description (string length 480, system
     specifications)
    DTM.02(2)     System Discontinue Date: (string length 10 - format
     mm/dd/yyyy).
        System Option Record (can occur multiple times for each system ID):
        Record tag: OPT
        SLN.02      Relationship id: (string length 2 - values are "PO" for
     parent option,
                    "CH" for child option, and "OR" for orphan option (no
     children)
        SI.07       Record Type: (string length 2 - values default system
     configuration =
                    CF,
                    valid options for a system ID = OP).
        SI.03       Option Indicator: (string length 7).
                    Note: See Option Indicator values.
        SI.05       Option Legend Code: (string length 7 - value 64 m, 128 m).
        SI.02       Option Action Code: (string length 1 - D = downgrade, U =
     upgrade,
                    A = in addition, C = configuration)
        PID.05      Option Legend Friendly Description: (string length 60-64
     Meg
                    memory).
        CTP.03      Option Price: (number length 10 - values .01 to
     9999999.99).
                    Note: Roll up detail part number pricing. Will be dependant
     on the
                    option action code as to what price it is
        Part record (can occur multiple times for each System Option Record):
            Record tag: PRT
            SAC.13    Part number: (number length 8 - values 230-1122).
            SAC.10    Part Quantity: (number length 4 - values 1 to 9999).
            SAC.15    Part Description: (string length 30 - values text
     description).
            SAC.05    Part Price: (number length 10 - values .01 to
     9999999.99).
                      Note: Part number contracted prices.
            N/A       Additional Shipping Price: (number length 10 - values
                      .01 to 9999999.99). Note: When applies, else it will be
     zero.
    Trailer record (occurs once for each catalog file):
    Record tag: TRL

                             TABLE 2
                     Option Indicator Values:
                      1 base-option = BASE
                      2 processor-option = PROC
                      3 memory-option = MEM
                      4 keyboard-option = KEYB
                      5 video-option = MONITOR
                      6 video-board-option = VIDB
                      7 video-memory-option = VIDM
                      8 hd-option = HD
                      9 ctl1-option = CNTRL
                      10 fd-option = FLPD
                      11 os-option = OS
                      12 point-option = MOUSE
                      13 nic-option = NIC
                      14 modem-option = MODEM
                      15 tbu-option = TAPEB
                      16 cdrom-option = CDROM
                      17 sound-option = SOUND
                      18 spkers-option = SPKERS
                      19 cache-option = CACHE
                      20 cable-option = CABLE
                      21 doc-dsk-option = DOCDSK
                      22 bundle-option = BUNDLE
                      23 hd-opt-option = HDOPT
                      24 ctl-opt-option = CNTRLO
                      25 sw1-option = SW1
                      26 sw2-option = SW2
                      27 opt1-option = OPT1
                      28 opt2-option = OPT2
                      29 initsvc-option = INITSVC
                      30 ext-svc-option = EXTSVC
                      31 dirline-option = DIRLINE
                      32 svc1-option = SVC1
                      33 svc2-option = SVC2
                      34 svc3-option = SVC3
                      35 svc4-option = SVC4
                      36 misc1-option = MISC1
                      37 misc2-option = MISC2
                      38 misc3-option = MISC3
                      39 misc4-option = MISC4
                      40 misc5-option = MISC5
                      41 misc6-option = MISC6
                      42 misc7-option = MISC7
                      43 system-integration = SI
                      44 comments = COMMENT
                      45 dock-sol = CSTMSOL
                      46 customer-kit = CUSTKIT
                      47 Dellware = DELLWAR

    TABLE 3
    File name =
        DELLUSA + Date (ccyymmdd) + Sequence number + extension
        The sequence number is 4 characters in length
        Example: DELLUSA199808310003.CATACK
    File Wrapper:
    Record tag: RTG
    From source: string length 10 ("CUSTOMERUSA")
    To destination: string length 30 ("DELLUSA")
    File type: string 15 (`CATACK")
    Acknowledgment Header (occurs once for each catalog ack file):
    Record tag: HDR
    BGN.01  Transaction purpose code: (string length 2, value 06 =
            confirmation)
    BGN.02  Reference ID (string length 30 - value, Dell Catalog number).
    BGN.06  Acknowledgement Version Number ( number length 4 - values
            1 to 9999).
    BGN.03  Acknowledgement Date: (string length 10 - format
            mm/dd/yyyy).
    BGN.04  Acknowledgement Time: (string length 8 - format hh:mm:ss).
    BGN.05  Acknowledgement Time Code (string length 2 - value ES =
            Eastern Standard Time)
    N1.02   Acknowledgement Contact: Customer (string length 32 - i.e.:
            Natalie Wong).
    PER.02  Acknowledgement phone number (number length 10 - format
            9999999999).
        Acknowledgment Detail (occurs once for each catalog system ID):
        Record tag: DTL
        OTI.01 Application acknowledgement code: (string length 2, value
            IA = item accept, IR = item reject)
        OTI.02 Original transaction identifier: (string length 3, value TN =
            transaction reference nbr)
        OTI.03 Original transaction number: (string length 30, value =
            System ID number from Catalog File)
        TED.02 Item reject text: (string length 60, value is free form text -
            only used if the Application ack code = IR)
    Trailer record (occurs once for each catalog acknowledgment file):
    Record tag: TRL
    SE.01 RECORD COUNT: NUMBER, LENGTH 7

    TABLE 4
    File name =
        DELLUSA + Date (ccyymmdd) + Sequence number(XXX) + extension
        Example: DELLUSA19990608001.ORDER
    File Wrapper:
    Record tag: RTG
    From source: string length 10 ("CUSTOMERUSA")
    To destination: string length 30 ("DELLUSA")
    File type: string 15 (`ORDER")
    ORDER HEADER (occurs once for each order):
    Record tag: OHDR
    Sender ISA control number: (number length 15)
    Sender GS control number: (number length 15)
    Sender TS control number: (number length 9)
    Translation DateTime Stamp (string length 8 -format mmddyyyy)
    File reference Id: (string length 15 - unique file id that order is sent
     in)
    BEG.01      Transaction purpose code: (string length 2, value 00 =
     Original)
    BEG.02      Purchase order type: (string length 2, value LE for Lease or PO
     for Purchase)
    BEG.03      Purchase order number: (string length 22)
    BEG.04      Purchase order release number: (string length 30)
    BEG.05      Purchase order date: (string length 8 - format mmddyyyy)
    CUR.02      Currency code: (string length 3 - values = USD, future use of
     CAN)
    CUR.03      Exchange Rate: (string number 10)
    CUR.05      Exchange From Currency/To Currency: (string 10)
    DTM.02(1)   Order Processed Date: (string length 8 - format mmddyyyy).
    DTM.03(1)   Order Processed Time: (string length 6 - format hhmmss).
    DTM.04(1)   Order Processed Time Code (string length 2 - value ES = Eastern
     Standard
                Time or CS = Central Standard Time)
    DTM.02(2)   Planned Ship Date (string length 8 - format mmddyyyy).
    Address loop (occurs twice, once for bill to, once for ship to)
        N.101     Loop Id:(string length 3, values ST = ship to , BT = Bill to)
        N.102     Name (string length 30, values ST = Hub Prime name, BT =
     Customer
                  DT&M)
        N.201     Additional Name 1 (string length 30, values ST = CSR contact
     name,
                  BT = blank)
        N.301(1)  Address line 1 (string length 30)
        N.302(1)  Address line 2 (string length 30)
        N.301(2)  Address line 3 (string length 30)
        N.401     City (string length 30)
        N.402     State (string length 2)
        N.403     Zip (string length 9)
        N.404     Country code (string length 2 values = US, future use of CN)
        PER.02    Contact name (string length 30 when ST = end user name, BT =
     not
                  used)
        PER.04    Contact phone number (number length 10, format 9999999999, ST
     =
                  end user phone nbr, BT = not used).
    TAX.01      Sales Tax Code (String length 20 - if filled in then this is a
     tax exempt
                number and is considered non-taxable, if blank that this is a
     taxable order)
    TD.401 (EXP only, not present when STND) Planned Ship Code (String length 5
     - values are
                STND for standard or EXP for expedited)
    TD.512      Shipping Service (String length 2 - values are 1D = one day, 2D
     = two day,
                3D = three day, ON = overnight, DF = default shipping service
     per contract)
    FOB.01      Shipping Payment Terms (string length 2 - BP = pay by buyer,
                standard shipping, PC = prepaid but charged to customer which
     will be used
                in preferred carrier situations)
    REF.03      Shipping Preferred Carrier Name: (String length 30 carriers
     name for
                preferred shipping when shipping payment terms = PC)
    REF.02      Shipping Preferred Account Number: (String length 35 - account
     number for
                carrier when shipping payment terms = PC)
    AMT.02      Shipping Charge (number length 10 - values .01 to 9999999.99,
     will be zero
                if using preferred carrier shipping)
    Reference Information (occurs up to three times if needed)
    REF.02      Order reference id: (string length 3 - values RQ = Purchase
     Order
                Requisition Number
                               P4 = ProjectCode
                               PS = Purchase Order Suffix
                               PP = Purchase Order Revision Number
    REF.03      Order reference number: (string length 30)
        Length of Lease (In terms of years): (number length 1; Length of the
     leasing period
        ider record b/c some customers may not have this field included in
     their order file.**
    CREDIT CARD PAYMENT (occurs up to three times, if using a Corporate Credit
     for
    Payment)
    Record Tag: CCC
    SPI.03 Credit Card number: (string length 21)
    REF.02      Credit Card Type: (string length 1, values are V = Visa, M =
     mastercard,
                A = AMEX, D = Discover)
    DTM.06      Credit Card expiration: (date, format = mm/yy)
    SPI.05 CID: (string length 6, values are customer specific)
    N.102       Credit Card Full Name: (string length 30, name as it appears on
     Credit Card)
                Credit Card First Name: (string length 14)
                Credit Card Middle Initial: (string length 1)
                Credit Card Last Name: (string length 15)
    N.301(3)    Credit Card Address Line 1: (string length 30)
    N.302(3)    Credit Card Address Line 2: (string length 30)
    N.401(3)    Credit Card City: (string length 30)
    N.402(3)    Credit Card State: (string length 2)
    N.403(3)    Credit Card Zip: (string length 5)
    N.403(3)    Credit Card Zip + 4: (string length 4)
    PERO4(2)    Credit Card Area Code: (string length 3)
    PERO4(2)    Credit Card Phone Number: (string length 7)
    REF.01      Credit Card Reference Number: (string length 25)
    MSG.01(1)   Credit Card Description 1:(string length 40)
    MSG.01(2)   Credit Card Description 2:(string length 40)
    MSG.01(3)   Credit Card Description 3:(string length 40)
    MSG.01(4)   Credit Card Description 4:(string length 40)
                Percentage of Payment: (string length 3)
                Daily Limit on Charge: (string length 6)
    ORDER DETAIL (occurs once for system ID):
    Record tag: ODTL
    PO.101      Loop counter (number length 5 - sequential counter)
    PO.102      Order quantity (number length 2 - values 1 to 50)
    PO.104      Unit price. (number length 10 - values .01 to 9999999 99, order
     total)
    PO.107      System ID: (number length 9 - values 1 to 999999999; Dell
     assigned).
        OPTION DETAIL (occurs once for each option)
        Record tag: OOPT
        SLN.01    Option Counter: (number length 5 - sequential counter).
        SLN.02    Option Indicator: (string length 7).
                  Note: See Option Indicator values.
        SLN.04    Option Quantity: (number length two)
        PID.05    Option Legend Code: (string length 7 - value 64 m, 128 m).
        PO.301    Option Action Code: (string length 1 - D = downgrade, U =
     upgrade,
                  A = in addition, C = configuration).
        Line Items Total (occurs once for each system + each option detail)
        Record tag: OAMT
        REF.02    Line item count: (number, length 7)
        AMT.02    Line item total (number length 10 - values .01 to
     9999999.99).
    Trailer record (occurs once for each Order file):
    Record tag: OTRL
    STT.01    RECORD COUNT: NUMBER, LENGTH 7
    AMT.02    Grand Total Order Amount (number length 10 - values .01 to
     9999999.99
              (items total + shipping + tax))

    TABLE 5
    File name =
        CUSTOMERUSA + Date (ccyymmdd) + Sequence number(XXX) +
        extension
        Example: CUSTOMERUSA19990608001.ORDERACK
    File Wrapper:
    Record tag: RTG
    From source: string length 30 ("DELLUSA")
    To destination: string length 10 ("CUSTOMERUSA")
    File type: string 15 (`ORDERACK")
    ACK HEADER (occurs once for each order):
    Record tag: AHDR
    BAK.08      Order File reference Id: (string length 15 - order file id that
                order was sent in)
    BAK.01      Transaction purpose code: (string length 2, value 00 =
                Original)
    BAK.02      Acknowledgement type: (string length 2, value AD = Ack
                w/detail, no change)
    BAK.03      Purchase order number: (string length 22)
    BAK.04      Purchase order date: (string length 10 - format mmddyyyy)
    DTM.02(1)   Order Acknowledgment Date: (string length 8, format
                mmddyyyy).
    DTM.03(1)   Order Acknowledgment Time: (string length 6, format
                hhmmss).
    DTM.04(1)   Order Acknowledgment Time Code: (string length 2, value
                ES = Eastern Standard Time)
    ACK DETAIL (occurs once for each ORDER DETAIL from Order):
    Record tag: ADLT
    PO1.06          Ack Detail qualifier: (string length 2, value = CF for
                    system, OP = Option)
    PO.101/sln.01   Line Item: (number length 5, loop counter from CF
                    and OP records).
    PO.102/sln.04   Order quantity: (number length 2, value 1 to 50)
    PO.104/sln.06   Unit price: (number length 10, value .01 to
                    9999999.99)
    PO.107/SLN.10   Reference ID: (number length 9, value 1 to
                    999999999, when Ack Detail Qual = CF then this
                    will be the system Id, when Ack Detail Qual. = OP
                    will be the Option Legend Code)
        ACK STATUS (occurs once for each Ack Detail Record)
        Record tag: ASTS
        ACK.01      Line Item Status Code: (string length 2, IA = item
                    accepted, IR = item rejected)
        ACK.02      Line Item Error Counter: (number length 3, if Line
                    Item Status Code = IR, total number of errors, If
                    Line Item Status Code = IA, then this will be blank.)
    AMT (occurs once for each Dell order, 1:M relationship from PO:Dell
    Order):
        Record tag: AMT
        N9.02       Dell Order Number: (string length 10)
        AMT.02      Confirmed Order Total: (number length 10 value .01 to
                    9999999.99)
                    Confirmed Shipping Total: (number length 10 value
                    .01 to 9999999.99)
                    Confirmed Tax Total: (number length 10, value .01 to
                    9999999.99)
                    Confirmed Line Item Total: (number length 10)
        DTMO2(2)    Order Expected Ship Date: (string length 8, format
                    mmddyyyy).
        ACK ERROR (Each error when ASTS record status = IR)
        Record tag: AERR
        ACK.06      Line Item IR error msg: (string length 45 - if status
                    code = IR, error message)
    Trailer record (occurs once for each Order Ack file):
    Record tag: TRL
    CTT.01      Total number of line items (number length 10).

                                  832 Price/Sales Catalog
                                 Functional Group ID = SC
                                       Introduction:
    This Standard contains the format and establishes the data contents of the
     Price/Sales Catalog Transaction
    Set (832) for use within the context of an Electronic Data Interchange
     (EDI) environment. The transaction
    set can be used to provide for customary and established business and
     industry practice relative to
    furnishing or requesting the price of goods or services in the form of a
     catalog.
                                         Heading:
        Pos.  Seg.                                      Req.             Loop
     Notes and
         No.  ID    Name                                Des.   Max.Use  Repeat
     Comments
     M   010  ST    Transaction Set Header                M       1
     M   020  BCT   Beginning Segment for Price/Sales Catalog   M       1
         070  DTM   Date/Time Reference                   O      10
         090  CUR   Currency                              O       5
                    LOOP ID-NI                                           >1
         150  NI    Name                                  O       1
         200  PER   Administrative Communications Contact   O     >1
                                          Detail:
        Pos.  Seg.                                      Req.             Loop
     Notes and
         No.   ID   Name                                Des.   Max.Use  Repeat
     Comments
                    LOOP ID-LIN                                          >1
         010   LIN  Item Identification                   O       1
         015   G53  Maintenance Type                      O       1
        n1
         030   DTM  Date/Time Reference                   O      10
         040   REF  Reference Identification              O     >1
         070   PID  Product/Item Description              O      200
         166   TXI  Tax Information                       O     >1
                    LOOP ID-CTP                                           100
         170   CTP  Pricing Information                   O       1
                    LOOP ID-SLN                                          >1
         350   SLN  Sublime Item Detail                   O       1
         360   SI   Service Characteristic Identification   O     >1
         370   PID  Product/Item Description              O     >1
         390   CTP  Pricing Information                   O     >1
         450   SAC  Service, Promotion, Allowance, or Charge   O     >1
                    Information

• Inventors
  Gosko, Theresa M.;
• Assignee
  Dell Products L.P. (Round Rock, TX)
• Published
  Mar-22-2005
• Current US Classes:
  705/26
  707/100
  707/102
  707/201
  707/203
• Application #
  592739
• International Classes
  G06F 017//60; G06F 007//00; G06F 017//30
• Field of Search
  707/102 707/100 707/201 707/203 707/101 705/26 705/1 705/27 705/28 705/30 703/13 703/27
• Examiner
  Chilcot; Richard
• Agent
  Hamilton & Terrile, LLP, Terrile; Stephen A.
• US Patent References:
  4959686
  4972318
  5202977
  5319542
  5325304
  5465290
  5611051
  5699526
  5712989
  5765143
  5819107
  5825651
  5870717
  5870719
  5909570
  5946663
  5963919
  5983200
  6014637
  6052670
  6055516
  6115641
  6117180
  6119102
  6167383
  6253188
  6292784
  6314415
  6317648
  6366914
  6408303
  6415196
  6427091
  6442748
  6487623
  6502102
  6542912