NAF Nätverk för Affärsutveckling i Försörjningskedjan

Transcription

1 VCC EDI DEMANDS Training session in Chengdu and Shanghai Eric Ristenstrand VCC Elsa Nylander VCC Yang Huang (Tony) VCC Sten Lindgren Odette Sweden Michael Bogren Encode AB/Odette

2 Purpose of training is to give you: Driving forces an OEM demand and supplier s possibility( 驱 动 力 - 客 户 需 求 和 供 应 商 的 潜 在 需 求 ) General format and syntax understanding ( 常 规 的 格 式 与 语 法 规 则 的 理 解 ) VCC specific rules for interpreting requirements ( 沃 尔 沃 转 译 要 求 的 具 体 规 则 ) Requirements in ASN and on labels (ASN 和 标 签 的 相 关 要 求 ) Business rules in the relation with VCC ( 沃 尔 沃 的 商 务 规 则 ) Solutions for EDI and labelling (EDI 和 标 签 的 解 决 方 案 ) Information sources ( 信 息 源 )

3 Purpose of training is to give you: EDI = Electronic Data Interchange EDIFACT = Electronic Data Interchange For Admininstration Commerce and Transport ASN = Advanced Shipping Note = DESADV = Electronic Delivery Note DELFOR = DELivery FORcast (long and short horizon OTL = Odette Transport Label Odette = Organisation for Data Exchange by Teletransmission in Europe Odette (format) = Format/Syntax similar to EDIFACT but older OFTP/OFTP2 = Odette File Transfer Protocol = Communication method/protocol What is Business Rules? VCC says commitment status is 4 (forecast) Volvo AB says commitment status is 24 (ackording to commercial agreement) Scania says commitment status is 9 (User defined) VCC Immediate demand: DELFOR DESADV OTL

4 Purpose of training is to give you: Driving forces a demand and a possibility General format and syntax understanding VCC specific rules for interpreting requirements Requirements in ASN and on labels Business rules in the relation with VCC Solutions for EDI and labelling Information sources

5 Driving forces - a demand and a possibility Driving forces Information quality ( 高 质 量 信 息 ) Real time information( 实 时 信 息 ) Auto-ID Automated goods reception( 货 物 接 收 自 动 化 ) Lesser manual administration/input( 较 少 的 手 工 操 作 / 输 入 ) Impossible to handle information size without EDI( 只 有 EDI 能 处 理 的 大 容 量 信 息 ) Supplier perspective( 供 应 商 方 面 ) Easier planning( 计 划 工 作 更 容 易 ) Secure raw material( 确 保 原 材 料 库 存 安 全 ) MRP( 物 料 需 求 计 划 ) Output to sub suppliers( 下 级 供 应 商 的 订 单 输 出 )... Result Improved supplier rating( 结 果 - 提 升 供 应 商 的 评 分 等 级 )

6 Driving forces - Complete supply chain penetration 驱 动 力 - 完 整 供 应 链 的 渗 透 深 度 5 weeks information lead time Full EDI 25 50% EDI 5% EDI 0% EDI 0% EDI OEM/OEM clusters (OEM 群 ) Tier 1 Tier 2 Tier 3 Tier 4 Tier 5

7 Driving forces - Complete supply chain penetration??? weeks information lead time OEM/OEM clusters Tier 1 Tier 2 Tier 3 Tier 4 Tier 5

8 Driving forces - Tier 1 responsibility Full process Outbound process Check availability Produce/pick Pack Label Book transport Tier 1 Forecast/Schedule OEM Create ASN Send ASN Tier 2 Forecast/Schedule Check availability Break down structure Run MRP Order/VMI/schedule Tier 1 Forecast/Schedule OEM Produce/pick Pack Label Book transport Create/send ASN Inbound process Tier 2 Tier 1 Tracability OEM Reverse Tracability Reverse Tracability Create/send ASN Label Store ASN Store Batch No Track internally Crossreference with outbound Internal process

9 Basic Scenario for information flow and physical flow. VCC Information flow OFTP 2 / Internet Supplier Order (Blanket order) Schedule Call-offs ASN & Labels Invoice Physical flow

10 Basic Scenario for information flow and physical flow. VCC Information flow OFTP 2 / Internet Order (Blanket order) Forecast Call-offs ASN & Labels Invoice Supplier Commercial order/agreement for one or more parts from which VCC later will calloff. Same Order No over time. ( 商 务 订 单 /VCC 随 后 通 知 分 批 发 货 的 一 个 或 多 个 零 件 的 协 议 这 里 使 用 的 是 总 订 单 号, 保 持 不 变 ) Physical flow

11 Basic Scenario for information flow and physical flow. VCC Information flow OFTP 2 / Internet Order (Blanket order) Schedule (DELFOR) Call-offs (DELFOR) ASN & Labels Invoice Supplier 60 week horizon forecast for one or more parts. Should be used for planning, securing raw material, reserving resources and further. The forecast gives the supplier a better chance to plan over time.( 一 个 或 多 个 零 件 的 60 周 预 测 该 预 测 用 于 内 部 计 划, 确 保 原 材 料 安 全 订 购 相 关 资 源 及 其 他 该 预 测 能 给 供 应 商 较 好 的 开 展 计 划 工 作 ) Physical flow

12 Basic Scenario for information flow and physical flow. VCC Information flow OFTP 2 / Internet Order (Blanket order) Schedule (DELFOR) Call-offs (DELFOR) ASN & Labels Invoice Supplier 6 week horizon forecast for one or more parts. Should be used for planning production and dispatch. You must know how to interpret codes, qualifiers and dates. Most information for the labels can be found in the Schedule/Calloff. ( 一 个 或 多 个 零 件 的 6 周 预 测 该 预 测 用 于 生 产 计 划 和 成 品 发 运 供 应 商 需 知 道 如 何 转 译 代 码 修 饰 符 号 和 日 期 计 划 / 分 批 发 货 订 单 上 包 含 了 大 部 分 的 标 签 信 息 ) Physical flow

13 Basic Scenario for information flow and physical flow. VCC Information flow OFTP 2 / Internet Order (Blanket order) Schedule Call-offs ASN & Labels Invoice Supplier Collect data for outbound shipment, generate labels for each package and transport carrier. Generate the ASN and send it to VCC no later than one hour after shipment. ( 汇 总 发 出 的 货 物 信 息, 给 每 个 包 装 和 运 输 工 具 的 标 签 生 成 标 签 在 货 物 发 出 后 1 小 时 内 生 成 ASN 并 发 送 给 沃 尔 沃 工 厂 ) Physical flow

14 Information links between DELFOR, DESADV and INVOIC BGM ' DTM+137: :102' DTM+157: :102' NAD+BY+10206::92' NAD+SE+35850::92' GEI+3' NAD+ST+10206::92' LIN :IN' LOC ::92' LOC+159+PORT 2::92 BGM ' DTM+137: :203' MEA+AAX+AAD+KGM:5139' MEA+AAX+ABJ+MTQ:0.0' RFF+AAS: NAD+ST+10206::92' LOC ::92' NAD+SF+35850::92' NAD+SE+35850::92' NAD+CA+2008::92' CPS+1++1' PAC+1++NIL::92' QTY+52:30:C62' PCI++++S::10' GIN+ML+87485' LIN :IN' QTY+12:30' ALI+SE' RFF+ON: ' RFF+AAP: ' LOC+159+PORT 2::92' BGM ' DTM+137: :102' GEI+PM+::272 NAD+SE+35850::92' RFF+VA:BR NAD+BY+10206::92' RFF+VA:SE ' NAD+ST+10206::92++VOLVO CUX+2:EUR:4' LIN :IN RFF+AAK:102031

15 Purpose of training is to give you: Driving forces a demand or a possibility General format and syntax understanding VCC specific rules for interpreting requirements Requirements in ASN and on labels Business rules in the relation with VCC Solutions for EDI and labelling Information sources

16 VCC EDI DEMANDS IN THE LOGISTICS PROCESS EDIFACT (version D.96A) Electronic Data Intechange For Administration, Commerce & Transport. Newer format developed by UNECE. ODETTE (Version V3) Older Automotive format using EDIFACT format (similar). Same basic syntax, different data tags.

17 VCC EDI DEMANDS IN THE LOGISTICS PROCESS EDIFACT (version D.96A) Sample DELFOR from CHN03 here SAMPLE DELINS V3 from CHN03 to here

18 General format and syntax understanding: NAD+CN+CHN03::92++VOLVO CARS' NAD NAME AND ADDRESS Function: To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru PARTY QUALIFIER M an C082 PARTY IDENTIFICATION DETAILS C 3039 Party id. identification M an Code list qualifier C an Code list responsible agency, coded C an C058 NAME AND ADDRESS C 3124 Name and address line M an Name and address line C an Name and address line C an Name and address line C an Name and address line C an C080 PARTY NAME C 3036 Party name M an Party name C an Party name C an Party name C an Party name C an Party name format, coded C an..3 Explanation: First three letters is segment name NAD Each composite (010, 020, ) is separated with: + And within each composite, each data tag is separated with : When no more data comes in the segment, the segment is terminated with This sample is terminated after the first 3036 tag in composite C059 STREET C 3042 Street and number/p.o. box M an Street and number/p.o. box C an Street and number/p.o. box C an Street and number/p.o. box C an CITY NAME C an COUNTRY SUB-ENTITY IDENTIFICATION C an POSTCODE IDENTIFICATION C an COUNTRY, CODED C an..3

19 General format and syntax understanding: NAD+CN+CHN03::92++VOLVO CARS' NAD NAME AND ADDRESS Function: To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru PARTY QUALIFIER M an C082 PARTY IDENTIFICATION DETAILS C 3039 Party id. identification M an Code list qualifier C an Code list responsible agency, coded C an C058 NAME AND ADDRESS C 3124 Name and address line M an Name and address line C an Name and address line C an Name and address line C an Name and address line C an C080 PARTY NAME C 3036 Party name M an Party name C an Party name C an Party name C an Party name C an Party name format, coded C an..3 Explanation: First three letters is segment name NAD Each composite (010, C082, C058...) is separated with: + And within each composite, each data tag is separated with : When no more data comes in the segment, the segment is terminated with This sample is terminated after the first 3036 tag in composite C059 STREET C 3042 Street and number/p.o. box M an Street and number/p.o. box C an Street and number/p.o. box C an Street and number/p.o. box C an CITY NAME C an COUNTRY SUB-ENTITY IDENTIFICATION C an POSTCODE IDENTIFICATION C an COUNTRY, CODED C an..3

20 Purpose of training is to give you: Driving forces a demand or a possibility General format and syntax understanding VCC specific rules for interpreting requirements Requirements in ASN and on labels Business rules in the relation with VCC Solutions for EDI and labelling Information sources

21 VCC forecast/schedule scope - general Introduction: A message from buyer to supplier giving product requirements regarding details for short term delivery instructions and/or medium to long term product/service forecast for planning purposes according to conditions set out in a contract or order. 介 绍 : 根 据 买 方 与 卖 方 签 订 的 合 同 或 订 单, 买 方 发 给 卖 方 的 信 息, 该 信 息 包 含 了 用 于 计 划 目 的 的 短 期 产 品 需 求 和 / 或 中 长 期 的 产 品 / 服 务 需 求 预 测

22 VCC specific rules for interpreting requirements - General Long horizon schedule always overwrites all previous requirements ( 长 期 计 划 通 常 会 覆 盖 前 一 次 发 送 的 所 有 需 求 ) Short horizon schedule only overwrites information between two dates ( 短 期 计 划 只 覆 盖 选 定 日 期 之 间 的 信 息 ) The unloading point is always presented as a combination of Consignee (plant) Gate (area within plant) Dock (final unloading point) ( 卸 货 点 通 常 是 收 货 工 厂 的 组 合 信 息 : 收 货 人 - 大 门 ( 工 厂 内 的 区 域 )- 道 口 ( 最 终 卸 货 点 ) A Part No can only be held in stock in one (1) gate/dock at the time but can be moved( 通 常 卸 货 方 式, 一 个 大 门 / 道 口 只 对 应 一 个 零 件, 但 该 零 件 的 卸 货 点 可 以 调 整 )

23 VCC specific rules for interpreting requirements Header DELFOR delivery forecast/schedule Document date ( 文 件 日 期 ) Validity start date (equal)( 有 效 起 始 日 期 ( 同 等 信 息 ) Information on the involved parties (Buyer, Seller, Consignee) ( 相 关 的 伙 伴 信 息 ( 买 方 卖 方 收 货 人 )

24 VCC specific rules for interpreting requirements - Header DELFOR delivery forecast/schedule UNH DELFOR:D:96A:UN:A09040' Message header BGM ' 241 = Delivery schedule (BGM-Beginning of message) DTM+137: :102' 137 = Document/message date/time (DTM-DateTime DTM+157: :102' 157 = Validity start date (DTM-DateTime NAD+BY+CHN03::92' BY = Buyer assigned by seller (NAD-NameAddress) NAD+SE+ABC1D::92' SE = Seller assigned by buyer (NAD-NameAddress) UNS+D' Header/detailed section separation NAD+CN+CHN03::92' CN = Consignee assigned by buyer (NAD-NameAddress)

25 VCC specific rules for interpreting requirements Previous deliveries DELFOR delivery forecast/schedule Three previous deliveires are presented in the schedule, however all based on physically received goods( 计 划 会 显 示 供 应 商 前 3 批 发 运 的 货 物 信 息, 但 是 沃 尔 沃 实 际 已 收 的 货 物 ) A cumulative quantity is presented for each part however also based on physically received goods( 每 个 零 件 都 显 示 累 计 量, 但 同 样 是 沃 尔 沃 实 际 已 收 的 货 物 ) The cumulative quantity is presented with two dates; ackumulation start date (when started counting) and calculation date (when stopped counting, counting restarts annually)( 累 计 量 会 显 示 两 个 日 期 : 累 计 起 始 日 期 ( 何 时 开 始 计 算 ) 和 计 算 日 期 ( 何 时 结 算 计 算 ), 每 年 年 初 重 新 累 计 ) Goods in transit will be invisible until physically received( 不 显 示 在 途 货 物, 只 显 示 已 接 收 货 物 ) A backorder presented in the schedule can all be goods in transit( 计 划 中 显 示 的 延 期 交 货 数 量 可 能 是 在 途 货 物 )

26 VCC specific rules for interpreting requirements Previous deliveries DELFOR delivery forecast/schedule LIN :IN' 3 = Changed. IN Buyer s item/article number PIA+1+P04:DR 1 = Additional identification DR = Drawing revision number LOC+11+VTV' 11 = Place/port of discharge LOC+159+VTV' 159 = Additional internal destination DTM+257: :102' 257 = Calculation date DTM+51: :102' 51 = Cumulative quantity start date RFF+ON: ' ON = Order number RFF+AIF: ' AIF = Previous delivery instruction number QTY+70:210' 70 = Cumulative quantity received QTY+12:30' 12 = Despatch quantity QTY+48:30' 48 = Received quantity RFF+AAK:110197' AAK = Despatch advice number DTM+171: :102' 171 = Reference date/time x3...

27 VCC specific rules for interpreting requirements - Requirements A backorder (QTY+83) always appears first on each part (if present) ( 每 个 零 件 的 延 期 交 货 订 单 (QTY+83) 通 常 第 一 个 显 示 ( 如 果 存 在 ) The commitment on a requirement will stay 4 (forecast) also in the frozen period ( 锁 定 期 的 需 求 代 码 仍 保 持 为 4 ( 预 测 ) Quantities can change in the schedules and it is your responsibility to follow trends and fluctuations ( 计 划 中 的 数 量 会 变 动, 需 求 变 化 和 波 动 趋 势 由 供 应 商 负 责 跟 踪 ) Requirement dates are always Ship-from-dates if else not agreed ( 如 果 没 有 另 外 协 议, 计 划 中 的 需 求 日 期 通 常 是 供 应 商 的 发 运 日 期 )

28 VCC specific rules for interpreting requirements - Requirements QTY+83:60' 83 = Backorder quantity (QTY-Quantity) QTY+113:30' 113 = Quantity to be delivered (QTY-Quantity) SCC+4' 4 = Planning/forecast (SCC-Scheduling Conditions) DTM+2: :203' 2 = Delivery date/time, requested (DTM-DateTime) QTY+113:30' 113 = Quantity to be delivered SCC+4' 4 = Planning/forecast DTM+2: :203' 2 = Delivery date/time, requested QTY+113:30' 113 = Quantity to be delivered SCC+4' 4 = Planning/forecast DTM+2: :203' 2 = Delivery date/time, requested...

29 VCC forecast/schedule scope - General Sample inserted to a superior system

30 VCC forecast/schedule scope - General Sample inserted to a superior system

31 Purpose of training is to give you: Driving forces a demand or a possibility General format and syntax understanding VCC specific rules for interpreting requirements Requirements in ASN and on labels Business rules in the relation with VCC Solutions for EDI and labelling Information sources

32 VCC specific rules for ASN and labelling - General 2 The purpose and basic function of the message( 此 信 息 的 目 的 和 基 本 功 能 ) The purpose of the DESADV is to provide the ultimate consignee of the goods with detailed information relating to the actual contents of a shipment sent by a consignor. The message is based upon the definition of a shipment as a specified amount of goods sent by a specified consignor to a specified consignee on a specific occasion. (DESADV 的 目 的 是 给 终 端 收 货 人 提 供 发 货 人 发 出 的 实 物 具 体 信 息 该 信 息 定 义 了 具 体 场 合 下 由 具 体 发 运 人 给 具 体 收 货 人 发 送 具 体 货 物 量 ) Notification is to be given of deliveries to all Volvo units. ( 沃 尔 沃 所 有 工 厂 都 要 求 供 应 商 发 ASN) The message gives the following information: ( 该 消 息 包 括 以 下 信 息 ) To state the actual time for shipment.( 说 明 货 物 发 运 的 具 体 时 间 ) To provide specific information concerning transportation.( 提 供 运 输 的 具 体 信 息 ) To specify the actual packages and handling units in the shipment. ( 说 明 货 物 的 具 体 包 装 和 器 具 信 息 ) To specify the contents of the shipment.( 说 明 货 物 内 容 ) To provide the necessary documentation for customs clearance.( 提 供 清 关 的 必 要 文 件 )

33 VCC specific rules for ASN and labelling - General 4 Creation of a DESADV(DESADV 创 建 ) A DESADV shall state the actual contents of a shipment.(desadv 将 说 明 货 物 的 具 体 内 容 ) Notification must therefore not be made until the actual loading procedure is completed and no later than one hour after the goods have been shipped. ( 通 知 单 因 此 必 须 在 实 物 装 运 完 成 且 在 实 物 发 出 后 的 1 小 时 内 创 建 ) All articles which are delivered to the same place of discharge and has the same delivery occasion shall be specified in the same dispatch advice (DESADV). ( 发 往 同 一 卸 货 点 并 且 是 同 时 发 运 的 所 有 货 物, 必 须 在 同 一 个 发 运 通 知 单 上 (DESADV). In the event that the quantity of goods defined in a particular dispatch is too large to be accommodated in its entirety on one vehicle/trailer/container etc. It is necessary to redefine the shipment so it relates only to the Vehicle/trailer/container etc. on which it is being transported. ( 如 果 发 运 通 知 单 上 阐 述 的 货 物 数 量 太 大 导 致 无 法 装 入 一 辆 车 / 挂 车 / 集 装 箱 等, 需 要 重 新 定 义 发 运 通 知 单 上 的 货 物 信 息, 确 保 通 知 单 的 信 息 只 针 对 实 际 运 输 的 一 辆 车 / 挂 车 / 集 装 箱 等 )

34 VCC specific rules for ASN and labelling - General One message can only consist of one Dispatch Note Number (DESADVnumber). ( 一 条 信 息 只 包 含 一 个 发 运 通 知 单 号 (DESADV 号 码 ) ALL articles to one Place of Discharge should be on ONE Dispatch Note (DESADV). ( 所 有 发 往 同 一 卸 货 点 的 货 物 必 须 在 同 一 发 运 通 知 单 上 (DESADV)

35 Vcc specific rules for ASN and labelling-general 8 Detailed Information about Packaging This part of the DESADV is rather complicated. Therefore we will try to make some clarifications in this chapter and also in the examples in the next chapter. (DESADV 的 包 装 部 分 比 较 复 杂, 因 此 在 本 页 做 一 些 说 明, 后 几 页 有 实 例 说 明 ) 8.1 Package and Handling Unit (Two key expressions concerning the packaging) 包 装 和 器 具 ( 包 装 方 面 的 两 个 关 键 词 ). Package Unit( 包 装 ) A unit in which the article itself is loaded.( 装 载 货 物 的 单 元 ). Handling Unit( 器 具 ) A device which can be handled physically (e.g. pallet) and may carry one or several packages.( 可 以 实 际 操 作 并 且 能 搬 运 一 个 或 多 个 包 装 的 装 置 ( 比 如 托 盘 ) Handling Units can be differentiated:( 器 具 有 以 下 几 种 ) Simplified Handling Units (S)( 单 一 器 具 ) Consists of one package which is a packaging and handling unit at the same time.( 整 个 器 具 为 一 个 大 包 装 ) Non Simplified Handling Unit (M & G)( 非 单 一 器 具 ) Consists of one or more packages which are not handling units at the same time.( 器 具 上 包 含 一 个 或 多 个 小 包 装 ) Non-Simplified handling unit article number. ( 器 具 上 只 装 载 相 同 零 件 号 的 小 包 装 ) Mixed Handling Unit (G) (Not allowed in VCC China)( 混 包 装 器 具 )( 在 沃 尔 沃 中 国 区 不 允 许 使 用 ) Consists of more than one article number( 器 具 上 装 载 多 个 零 件 号 的 小 包 装 )

36 Example and reference to an Odette label (OTL1) DELFOR - NAD (CN) DELFOR - LOC 3225 (159) DESADV - LOC 3225 (159) DESADV - BGM 1004 DELFOR- LIN 7140 (IN) DESADV - LIN 7140 (IN) DESADV - QTY 6060 (52) DELFOR - NAD 3039 (SE) DESADV - NAD 3039 (CZ) DESADV - PIA 7140* DESADV - RFF 1154 GIR 7402 *=special agreements

37 VCC specific rules for ASN and labelling - Message Simplified handling unit (2 pallets) UNH DESADV:D:96A:UN:A01051' BGM ' DTM+137: :203' RFF+AAS:CMR ' RFF+CRN: ' NAD+CZ+ABCD1::92' NAD+SE+ABCD2::92 NAD+CN+BP2TH::92' LOC+11+TVV::92' NAD+CA+CARGOCARE::92' CPS+1++1' PAC+2++NIL::92' QTY+52:128:PCE' PCI++++S::92' GIR+3+123:ML' GIR+3+124:ML' LIN :IN++0' PIA+1+P04:DR' QTY+12:256:PCE' ALI+UK' RFF+ON: ' LOC+159+TVV::92' UNT ' Message header 351 = Despatch advice 137 = Document/message date/time AAS = Transport document number CRN = Conveyance reference number CZ = Consignor SE = Seller. Used if Seller and Consignor has different supplier id. CN = Consignee 11 = Place/port of discharge CA = Carrier Hierarchical id. number and 1 = inner packing Number of packages and package reference number. 52 = Quantity per pack S = Simplified handling unit 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number IN = Buyers article/item number. 0 = Single article package case 1 = Additional identification. DR = Drawing revision number 12 = Despatch quantity Country of origin ON = Order number 159 = Additional internal destination Message trailer

38 VCC specific rules for ASN and labelling Package and label Simpliefied handling unit (2 pallets)

39 VCC specific rules for ASN and labelling - Message Simpliefied handling unit (1 pallets, 16 smallboxes) UNH DESADV:D:96A:UN:A01051' BGM ' DTM+137: :203' RFF+AAS:CMR ' RFF+CRN: ' NAD+CZ+ABCD1::92' NAD+SE+ABCD2::92' NAD+CN+BP2TH::92' LOC+11+TVV::92' NAD+CA+CARGOCARE::92' CPS+1++1' PAC+16++NIL::92' QTY+52:56:PCE' PCI++++M::92' RFF+AAT:191 GIR+3+11:ML' GIR+3+12:ML' GIR+3+13:ML' GIR+3+14:ML' GIR+3+15:ML' GIR+3+16:ML' GIR+3+17:ML' GIR+3+18:ML' GIR+3+19:ML' GIR+3+20:ML' GIR+3+21:ML' GIR+3+22:ML' GIR+3+23:ML' GIR+3+24:ML' GIR+3+25:ML' GIR+3+26:ML' LIN :IN++0' PIA+1+P04:DR' QTY+12:896:PCE' ALI+UK' RFF+ON: ' LOC+159+TVV::92' UNT ' Message header 351 = Despatch advice 137 = Document/message date/time AAS = Transport document number CRN = Conveyance reference number CZ = Consignor SE = Seller. Used if Seller and Consignor has different supplier id. CN = Consignee 11 = Place/port of discharge CA = Carrier Hierarchical id. number and 1 = inner packing Number of packages and package reference number. 52 = Quantity per pack M = Homogenous handling unit AAT = Master label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number 3 = Package. ML = Marking/Label number IN = Buyers article/item number. 0 = Single article package case 1 = Additional identification. DR = Drawing revision number 12 = Despatch quantity Country of origin ON = Order number 159 = Additional internal destination Message trailer

40 VCC specific rules for ASN and labelling Package and label Homogeneous handling unit (1 pallet, 16 smallboxes)

41 Logistics units levels Level 5 - Vehicle RF Tag Layer 5 ( GHz) Vehicle Level 4 - Container Layer 4 (UHF) (ISO 17363) Container Level 3 - Pallet Layer 3 (UHF) (ISO 17364, ISO 17365) Pallet Pallet Unit Load Level 2 Small box Layer 2 (UHF) (ISO 17364, ISO 17365) Plastic Container Plastic Container Plastic Container Plastic Container Transport Unit Level 1 Packaging MAT Level 0 - Item Layer 1 (UHF) (ISO 17366) Layer 0 (UHF) (ISO 17367) Packing Packing Packing Packing Packing Packing Packing Packing Packing Item Item Item Item Item Item Item Item Item Item Item Item Item Item Item Item Item 41

42 Smallbox handling Homogenous handling unit One part per pallet Mixed handling unit Multiple parts per pallet S - Label M - Label S - Label G - Label S - Label 1 Simplified handling unit One part directly on pallet

43 Label positioning

44 Label positioning

45 Label positioning

46 Label fastening

47 Label fastening Do not..!

48 Label fastening Do not..!

49 Label fastening Do not..!

50 Purpose of training is to give you: Driving forces a demand or a possibility General format and syntax understanding VCC specific rules for interpreting requirements Requirements in ASN and on labels Business rules in the relation with VCC Solutions for EDI and labelling Information sources

51 Business rules in the relation with VCC - Summary Consignee gate dock in DELFOR, ALWAYS to be used in ASN (same data) (ASN 的 DELFOR 通 常 使 用 收 货 人 大 门 道 口 ( 同 一 数 据 ) Supplier (partner code) in DELFOR, ALWAYS to be used in ASN (same data) (ASN 的 DELFOR 通 常 使 用 同 一 供 应 商 代 码 ( 同 一 数 据 ) Always check previous delivery notes in DELFOR against all your deliveries ( 供 应 商 需 检 查 前 一 次 发 运 货 物 的 DELFOR 交 付 信 息 ) Always check possible backorders with goods in transit/goods not physically received ( 检 查 在 途 / 未 实 际 收 货 的 延 期 交 货 订 单 ) Keep track on the cumulative quantities for double check( 仔 细 核 查 累 计 数 量 ) Forecasts commitment never changes a forecast goes firm when in frozen period ( 预 测 代 码 不 变 进 入 锁 定 期 间 的 预 测 即 为 冻 结 订 单 ) Requirement dates are Ship From Dates( 预 测 计 划 的 需 求 日 期 是 供 应 商 的 发 运 日 期 ) System availability 24/365( 系 统 需 365 天 24 小 时 保 持 开 放 ) All Part No s are always Buyers Part No( 所 有 零 件 号 是 买 方 的 零 件 号 ) One shipment (one load) is one ASN. If a load cannot go on the same shipment, multiple ASN s must be transmitted( 一 票 货 对 应 一 个 ASN, 如 果 一 票 货 无 法 一 块 发 运, 必 须 发 送 跟 货 物 批 次 对 应 的 多 个 ASN ) Label correct and attach labels correctly( 正 确 的 标 签 内 容, 正 确 的 标 签 定 位 ) Transmit the ASN in time( 及 时 发 送 ASN)

52 Purpose of training is to give you: Driving forces a demand or a possibility General format and syntax understanding VCC specific rules for interpreting requirements Requirements in ASN and on labels Business rules in the relation with VCC Solutions for EDI and labelling Information sources

53 Solutions for EDI and labels Generally, there are two types of solutions: 一 般 有 两 种 解 决 方 案 : * Stand alone solution ( 独 立 式 解 决 方 案 ) Web EDI browsed solution for single or multiple OEM ( 网 络 EDI 为 单 个 或 多 个 OEM 创 建 网 页 浏 览 解 决 方 案 ) Web EDI for unique OEM (portal) browsed solution for single OEM ( 为 独 家 OEM 创 建 网 络 EDI ( 门 户 ) 为 单 个 OEM 创 建 网 络 浏 览 解 决 方 案 ) Specialized systems for EDI handling outside ERP/APS stand alone system with functionality to handle and satisfy OEM demands (multiple).(erp/aps 以 外 的 操 作 EDI 的 专 门 系 统 具 有 操 作 和 满 足 OEM 需 求 ( 多 个 ) 功 能 的 独 立 系 统 ** Integrated solutions ( 整 合 式 解 决 方 案 ) Integration via application at supplier premises EDI platform for conversion ( 在 供 应 商 处 安 装 应 用 系 统 实 现 整 合 EDI 转 换 平 台 ) Integration via application at outsouced location EDI platform for conversion ( 通 过 外 包 的 应 用 系 统 实 现 整 合 EDI 转 换 平 台 ) Integration via EDI Service Central EDI platform for conversion ( 通 过 EDI 服 务 商 实 现 整 合 中 央 EDI 转 换 平 台 )

54 Solutions for EDI and labels * Stand alone definition: A system or a service for EDI and labeling without any information exchange with other systems.( 独 立 解 决 方 案 定 义 : 实 现 EDI 和 标 签 作 业 的 系 统 或 服 务, 它 不 需 要 与 别 的 系 统 交 换 信 息 ) ** Integrated solution definition: A system or a service for EDI and some times labeling where data exchange with other systems exist. Level of integration varies.( 整 合 解 决 方 案 定 义 : 实 现 EDI 和 有 时 标 签 作 业 的 系 统 或 服 务, 它 与 其 他 系 统 交 换 信 息 整 合 程 度 有 很 多 种 )

55 Solutions for EDI and labels Stand alone solution Web EDI browsed solution for single or multiple OEM Web EDI for unique OEM (portal) browsed solution for single OEM Speacialized systems for EDI handling outside ERP/APS stand alone system with functionality to handle and satisfy OEM demands (multiple). OFTP2 Supplier enviroment: Web EDI provider VCC enviroment: ISDN/X.25

56 Solutions for EDI and labels Stand alone solution Web EDI browsed solution for single or multiple OEM Web EDI for unique OEM (portal) browsed solution for single OEM Speacialized systems for EDI handling outside ERP/APS stand alone system with functionality to handle and satisfy OEM demands (multiple). OFTP2 OEM enviroment: Supplier enviroment: Web EDI provider ISDN/X.25

57 Solutions for EDI and labels Stand alone solution Web EDI browsed solution for single or multiple OEM Web EDI for unique OEM (portal) browsed solution for single OEM Speacialized systems for EDI handling outside ERP/APS stand alone system with functionality to handle and satisfy OEM demands (multiple). Supplier enviroment: Web EDI provider (OEM) VCC enviroment:

58 Solutions for EDI and labels ERP/APS Stand alone solution Web EDI browsed solution for single or multiple OEM Web EDI for unique OEM (portal) browsed solution for single OEM Specialized systems for EDI handling outside ERP/APS stand alone system with functionality to handle and satisfy OEM demands (multiple). Supplier enviroment: OFTP2 VCC/OEM enviroment: Thin client or installed application ISDN/X.25

59 Solutions for EDI and labels Integrated solutions Integration via application at supplier premises EDI platform for conversion Integration via application at outsouced location EDI platform for conversion Integration via EDI Service Central EDI platform for conversion ERP/APS Supplier enviroment: OFTP2 VCC/OEM enviroment: EDI Platform ISDN/X.25

60 Solutions for EDI and labels Integrated solutions Integration via application at supplier premises EDI platform for conversion Integration via application at outsouced location EDI platform for conversion Integration via EDI Service Central EDI platform for conversion Supplier enviroment: Service provider: OFTP2 VCC/OEM enviroment: ERP/APS EDI Platform ISDN/X.25

61 Solutions for EDI and labels Integrated solutions Integration via application at supplier premises EDI platform for conversion Integration via application at outsouced location EDI platform for conversion Integration via EDI Service Central EDI platform for conversion Supplier enviroment: Service provider: OFTP2 VCC/OEM enviroment: ERP/APS EDI Platform ISDN/X.25

62 Purpose of training is to give you: Driving forces a demand or a possibility General format and syntax understanding VCC specific rules for interpreting requirements Requirements in ASN and on labels Business rules in the relation with VCC Solutions for EDI and labelling Information sources

63 Purpose of training is to give you: (main page) (specifications) (communication) (contacts) (help page) (links) (communication - OFTP2) (VCC web-edi) (EDIFACT specifications)