Supply Chain Merchandise Logistics E-Commerce Forecast Data

Transcription

1 Supply Chain Merchandise Logistics E-Commerce Forecast Data E-Commerce Forecast Data Page 1 of 13

2 Contents Introduction 3 Forecast data Electronic Forecast data 4 Forecast data - document mapping considerations 5 Segments VICS 830 Document planning schedule (with release capability) 6 Segment ST Transaction set header 7 Segment BFR Beginning segment for planning schedule 8 Segment LIN Line item identification 9 Segment UIT Unit detail 10 Segment FST Forecast schedule 11 Segment CTT Transaction totals 12 Segment SE Transaction set trailer 13 E-Commerce Forecast Data Page 2 of 13

3 Introduction Purpose of this implementation guide The purpose of this guide is to provide suppliers with the necessary information to enable the implementation of receiving electronic forecast data from Myer Pty Ltd. Who should use this guide This guide is intended for use by Myer suppliers to prepare for the implementation of Electronic Data Interchange (EDI) and to assist with applications integration, thereby ensuring successful electronic trading. E-Commerce Forecast Data Page 3 of 13

4 Electronic forecast data 1 The EDI forecast information document will be transmitted to the EDI network on Monday evenings. The frequency of these transmissions will be determined by the existing replenishment cycle, that is weekly/fortnightly/monthly as applicable to each trading partner. Forecast sales units will be transmitted for all Replenishment types set up for Forecasting. 2 Suppliers should schedule their receiving application to retrieve the forecast information from the network after 2.00 am on the following Tuesday morning. 3 Data for only replenishment items (at full SKU level) is available to be transmitted which will be converted to the appropriate suppliers EAN code and received as such. 4 Sales forecast information will only be transmitted at item (SKU)/national level, as this is the level at which they are currently produced in our forecast application. 5 Sales forecasts are available for either the next 14 weeks via EDI weekly or up to 12 months in Microsoft Excel ed by the Replenishment Team as required of your items (SKU s). (The 12 month forecast is updated monthly) This is a manual adhoc process. 6 Sales forecast information will be transmitted in unit value and not dollar value. 7 Functional acknowledgments for the EDI planning schedule document are expected from all suppliers at the functional group level. 8 The cost of transmissions will be based on the provision that the sender pays to send the document and the receiver pays to receive and retrieve the document. 9 Problem solving procedures... Any discussions of technical matters or in the case of transmission problems please contact Myer E-Commerce on option 6, option 2 Queries relating to the document content, for example, accuracy of figures transmitted, should be directed to the appropriate Replenishment Team contact. E-Commerce Forecast Data Page 4 of 13

5 Forecast data - document mapping considerations 1 The document type used for the transmission of sales forecast information is referred to as the VICS 830 document, planning schedule. 2 The document standard and version used for the Myer EDI forecast data is VICS. Trading partners will need to ensure that the disk containing VICS standard and version is loaded into their software before transmissions commence. 3 Within the beginning segment for planning schedule (BFR), the designated code for field BFR01 is 00 which determines that the data transmitted is original. The designated code for field BFR04 is BB, customer production (consumption) base which determines and qualifies the type of forecast. 4 The reference number segment (REF), where REF DP is the reference number of the department, refers exclusively to the Myer internal class group. 5 Within the line item segment (LIN), the designated code for field LIN02 is EN which refers to the supplier generated code describing style, size and colour of merchandise and maybe either an APN, UPC or EAN. 6 Within the forecast schedule segment (FST), the designated code for field FST02 is D which determines that the forecast data is to be used for planning purposes. The designated code for field FST03 is F and is the flexible interval used for forecast timing. E-Commerce Forecast Data Page 5 of 13

6 VICS 830 Document planning schedule (with release capability) Myer 830 planning schedule transaction set Explanation of requirement designators... M MANDATORY This element shall appear in the segment R UIRED Mandatory for compliance with industry guidelines C CONDITIONAL The presence of this data element is dependent upon the value or presence of other data elements in the document O OPTIONAL The inclusion of this element is at the option of the sending party, or is based on the mutual agreement of the trading partners Assumptions... Segments... 1 Forecast data will be at item (SKU)/national level 2 The frequency of transmission will be determined by the ABS order cycle 3 Forecasts are available for 14 weeks via EDI weekly and up to 12 months in Microsoft Excel ed by the Replenishment Team, this is amanual adhoc process. ST BFR LIN UIT FST Transaction set header Beginning segment for planning schedule Line item identification Unit detail Forecast schedule CTT Transaction totals SE Transaction set trailer E-Commerce Forecast Data Page 6 of 13

7 Segment ST Transaction set header 01 TRANSACTION SET 02 TRANSACTION SET 143 ID 3 3 M This is always set at "830" to represent the forecast document 329 AN 1 9 M Control number NOTES The number is sequentially assigned by the sender, starting with 1 within each functional group. For each functional group, the first transaction set control number will be 0001 and incremented by one for each additional transaction set within the group. ST*830* E-Commerce Forecast Data Page 7 of 13

8 Segment BFR Beginning segment for planning schedule 01 TRANSACTION SET 02 REFERENCE BER 353 ID 2 2 M Purpose code, in all cases 00=Original 127 AN 1 30 R This is, in all cases, set to a constant of "1" 04 SCHEDULE 675 ID 2 2 M Qualifier, this qualifies the type of forecast 05 SCHEDULE QUANTITY BB=Customer production (consumption) based 676 ID 1 1 M Qualifier, this field is set at A=Actual discrete quantities 06 DATE 373 DT 6 6 M YYMMDD Start of forecast period 07 DATE 373 DT 6 6 M YYMMDD End of forecast period 08 DATE 373 DT 6 6 M YYMMDD Date forecast is generated NOTE The date range specified in the BFR segment (that is in BFR06 and BFR07) is for the overall forecast period indicated in the document and does not indicate specific intervals within the overall forecast period. This range will show whether the forecast relates to 13 weeks, 13 months, 4 weeks, etc, and these are the dates that should be quoted in the case of queries. BFR*00*1*BB*A*080201*080301* E-Commerce Forecast Data Page 8 of 13

9 Segment LIN Line item identification 01 ASSIGNED IDENTIFICATION 02 PRODUCT / SERVICE 03 PRODUCT / SERVICE 04 PRODUCT / SERVICE 05 PRODUCT / SERVICE 350 AN 1 11 O Line item number within the document 235 ID 2 2 M ID qualifier set at CG=Commodity grouping (that is class group) 234 AN 1 30 M ID (actual number) This field contains the 4 digit class group number 235 ID 2 2 O ID Qualifier set at EN=APN 234 AN 1 30 C ID (actual number) The actual APN is expressed in this field LIN*001*CG*1234*EN* E-Commerce Forecast Data Page 9 of 13

10 Segment UIT Unit detail 01 Unit of Measure 355 ID 2 2 M Measurement code set at EA=Each UIT*EA E-Commerce Forecast Data Page 10 of 13

11 Segment FST Forecast schedule 01 QUANTITY 380 R 1 15 M Numeric value of quantity 02 FORECAST QUALIFIER 03 FORECAST TIG 680 ID 1 1 M Specifies the sender s confidence level of the forecast data, set at D=Planning 681 ID 1 1 M Qualifier set at F=Flexible interval 04 DATE 373 DT 6 6 M YYMMDD Start date of flexible interval 05 DATE 373 DT 6 6 O YYMMDD End date of flexible interval NOTE One FST segment occurs for each date range at the detail level (that is by month or week) that relates to the overall period specified in the BFR segment. For example, if the overall period of the document relates to one month, but the data is broken into weekly intervals, there will be 4 FST segments. FST*100*D*F*080201* E-Commerce Forecast Data Page 11 of 13

12 Segment CTT Transaction totals 01 BER OF LINE 354 NO 1 6 M The number of line items present in the transaction set CTT*12 E-Commerce Forecast Data Page 12 of 13

13 Segment SE Transaction set trailer 01 BER OF INCLUDED SEGMENTS 02 TRANSACTION SET CONTROL BER 96 NO 1 6 M 329 AN 4 9 M NOTE This must be the same number as in the ST segment (ST02) for the transaction set. SE*6* E-Commerce Forecast Data Page 13 of 13