Piccadilly Orders

TransdatiX.Convert Piccadilly Orders

Version 2.0.8 from 2009-05-25

Content

General

With this converter Orders from the bulgarian supermarket chain Piccadilly in EDIFACT-format can be converted to XML or CSV.

How to start the Converter

This TransdatiX.Convert converts your incoming data to the XML or CSV format as stated below. This output data then can either be directly imported by a program or delivered to a destination system by using a TransdatiX.Adapt.

You can use this TransdatiX.Convert for example fully automated within a process together with a TransdatiX.Adapt which is required for your target system. Also a integrated data transmission can be realized in one process. Read more about defining processes using the TransdatiX.Configurator (this document is only available in german yet).

Hints

The converter requires the order data from Piccadilly in EDIFACT-format.

Two interfaces are contained for converting EDIFACT-data either to XML or CSV.

The interface ConvertToXml generates an XML output file that includes the whole data structure.

The interface ConvertToCsv generates three CSV output files:
  • Envelope - Transmission Section
    Contains all data of the data group Envelope

  • Order - Order Heading Section
    Contains all data of the data group Order

  • Pos - Order Position Section
    Contains all data of the data group Pos


Structure of data - Overview

The following listing shows the formal data structure accepted by the converter. Bold descripitions means, that an element is required, excepting a term is quoted explicit within the description of the element.


Element name

Description

 
RootRoot element
 
  MessageMessage
    MessageIDInternal unique Identification
 
    EnvelopeTransmission Section
      MessageIDReference to MessageID in data group Message
      SenderIdSender
      RecipientIdRecipient
      MessageTypeEDIFACT Message Type Identifier
      TransmissionIdMessage Reference Number
      TestFlagTest Indicator
 
    OrderOrder Heading Section
      MessageIDReference to MessageID in data group Message
      OrderIDInternal unique Identification
      StatusOrder Type
      FunctionMessage Function
      NumberOrder Number
      DateOrder Date
      DeliveryDateDelivery Date requested. If LatestDeliveryDate is also given, this date means earliest delivery date.
      LatestDeliveryDateLatest delivery Date requested
      FreeText1Free Text
      FreeText2Free Text
      FreeText3Free Text
      FreeText4Free Text
      FreeText5Free Text
      PromotionalDealNumberNumber assigned by a vendor to a special promotion activity
      BuyerGLNThe Buyer's GLN
      SupplierGLNThe Supplier's GLN
      SupplierIdBuyerThe Buyers's internal identification number for the Supplier
      DeliveryGLNGLN of party to which goods should be delivered
      UltimateCustomerGLNGLN of the Ultimate Customer
      OrderedByGLNGLN of the party who issued an order (if different from Buyer)
      InvoiceeGLNGLN of the party to whom the invoice should be issued (if different from Buyer)
      CurrencyCurrency
      TransportModeMode of Transport
      TransportMediumType of means of transport
 
      PosOrder Detail Section
        MessageIDReference to MessageID in data group Message
        OrderIDReference to OrderID in data group Order
        NumberPosition number
        ItemGTINGTIN of article
        ItemEANCustomerEAN of article
        ItemIdSupplierSupplier's article number
        ItemIdBuyerBuyer's article number
        ItemNameArticle name
        ItemName2Article name 2
        QuantityOrder quantity
        UnitOrder Unit
        DeliveryDaterequested date of delivery
        FreeText1Free Text
        FreeText2Free Text
        FreeText3Free Text
        FreeText4Free Text
        FreeText5Free Text
        NetPriceNet price
        PromotionalDealNumberNumber assigned by a vendor to a special promotion activity



Data group Message - Message
Required field: yes, unlimited repeatable
Message

MessageID - Key field
Format: alphanumeric
Hint: Internal unique Identification



Data group Envelope - Transmission Section
Required field: yes
Transmission Section

MessageID - Key field
Format: alphanumeric
Hint: Reference to MessageID in data group Message

SenderId - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Sender
Mailbox-ID of Message Sender

RecipientId - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Recipient
Mailbox-ID of Message Recipient

MessageType - Required field: no
Format: alphanumeric with up to 6 character(s)
Hint: EDIFACT Message Type Identifier
If a transmission includes only Messages of the same type the message type can be specified within the envelope as an information for the recipient .

TransmissionId - Required field: no
Format: alphanumeric with up to 14 character(s)
Hint: Message Reference Number
Unique Reference for the transmission generated by the sender.

TestFlag - Required field: no
Possible values:
1=Interchange is a test
Hint: Test Indicator
Only used during testing period



Data group Order - Order Heading Section
Required field: yes, unlimited repeatable
Order Heading Section
Includes the Heading Data

MessageID - Key field
Format: alphanumeric
Hint: Reference to MessageID in data group Message

OrderID - Key field
Format: alphanumeric
Hint: Internal unique Identification

Status - Required field: no
Possible values:
220=Order
402=Cross Docking Order
22E=Supplier raised order (VMI = Vemndor Managed Inventory)
Hint: Order Type

Function - Required field: no
Possible values:
9=Original
42=Confirmation
Message confirming a transaction previously agreed via other means (e.g. phone).
Hint: Message Function

Number - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Order Number

Date - Required field: yes
Format: date
Hint: Order Date

DeliveryDate - Required field: no
Format: date
Hint: Delivery Date requested. If LatestDeliveryDate is also given, this date means earliest delivery date.

LatestDeliveryDate - Required field: no
Format: date
Hint: Latest delivery Date requested

FreeText1 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText2 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText3 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText4 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText5 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

PromotionalDealNumber - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Number assigned by a vendor to a special promotion activity

BuyerGLN - Required field: yes
Format: alphanumeric with up to 13 character(s)
Hint: The Buyer's GLN

SupplierGLN - Required field: yes
Format: alphanumeric with up to 13 character(s)
Hint: The Supplier's GLN

SupplierIdBuyer - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: The Buyers's internal identification number for the Supplier

DeliveryGLN - Required field: yes
Format: alphanumeric with up to 13 character(s)
Hint: GLN of party to which goods should be delivered

UltimateCustomerGLN - Required field: no
Format: alphanumeric with up to 13 character(s)
Hint: GLN of the Ultimate Customer

OrderedByGLN - Required field: no
Format: alphanumeric with up to 13 character(s)
Hint: GLN of the party who issued an order (if different from Buyer)

InvoiceeGLN - Required field: no
Format: alphanumeric with up to 13 character(s)
Hint: GLN of the party to whom the invoice should be issued (if different from Buyer)

Currency - Required field: no
Format: alphanumeric with up to 3 character(s)
Hint: Currency
ISO-Code of Order Currency

TransportMode - Required field: no
Possible values:
20=Rail transport
30=Road transport
50=Mail
100=Courier service
Hint: Mode of Transport

TransportMedium - Required field: no
Possible values:
25=Rail express
34=Road parcel express
51=Parcel post
53=Surface mail
55=Air mail
31=Truck
Hint: Type of means of transport



Data group Pos - Order Detail Section
Required field: yes, unlimited repeatable
Order Detail Section

MessageID - Key field
Format: alphanumeric
Hint: Reference to MessageID in data group Message

OrderID - Key field
Format: alphanumeric
Hint: Reference to OrderID in data group Order

Number - Required field: no
Format: integer
Hint: Position number

ItemGTIN - Required field: yes
Format: alphanumeric with up to 14 character(s)
Hint: GTIN of article
Please fill with 0000000000000 if not available

ItemEANCustomer - Required field: no
Format: alphanumeric with up to 14 character(s)
Hint: EAN of article

ItemIdSupplier - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's article number

ItemIdBuyer - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's article number

ItemName - Required field: no
Format: alphanumeric
Hint: Article name

ItemName2 - Required field: no
Format: alphanumeric
Hint: Article name 2

Quantity - Required field: yes
Format: decimal
Hint: Order quantity

Unit - Required field: no
Format: alphanumeric ***
Hint: Order Unit

DeliveryDate - Required field: no
Format: date
Hint: requested date of delivery

FreeText1 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText2 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText3 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText4 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

FreeText5 - Required field: no
Format: alphanumeric with up to 70 character(s)
Hint: Free Text

NetPrice - Required field: no
Format: decimal
Hint: Net price
Net price per unit including allowances/charges and excluding taxes

PromotionalDealNumber - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Number assigned by a vendor to a special promotion activity


Legal notes

All information contained in this document is provided without any whatsoever guarantees. TransdatiX expressly refuses all liability claims, explicit or implicit, including claims regarding suitability for selling or specific purpose. In no case TransdatiX or one of its suppliers can be held responsible for any damages, occuring direct or indirect, quite accidentally or as a consequential damage. Especially business losses, data losses or special damages are excluded explicitly from liability, even if TransdatiX or its suppliers pointed to the possibility of such damages. In any case liability claims are rejected to the legal highest possible dimension.


© 2002 - 2009 TransdatiX Software


Generated automatically 2009-05-25, 11:26:40