Guide M2M Changes. Go live of new functionalities: AirSupply Release May 27 th, 2017

Size: px

Start display at page:

Download "Guide M2M Changes. Go live of new functionalities: AirSupply Release May 27 th, 2017"

Willis Dalton
5 years ago
Views:

shared supply chain collaboration platform in the

1 Guide M2M Changes Go live of new functionalities: AirSupply Release May 27 th, 2017 SupplyOn, the shared supply chain collaboration platform in the manufacturing industry SupplyOn AG SupplyOn Intern

Overview of new functionalities included into the M2M messages Relevant Change Requests for M2M suppliers with full Access to AirSupply supplier login via Username and Password 1.

2 Overview of new functionalities included into the M2M messages Relevant Change Requests for M2M suppliers with full Access to AirSupply supplier login via Username and Password 1. Purchase Order (PO): Functionality Effect on frontend/ UI Effect on backend 1.1. Add OO to PO supplier M2M messages Yes Yes 1.2. PO New links to external documents, 2 new fields added to M2M message Yes Yes 1.3. Field Reason for last status change to OPEN added Yes Yes 1.4. Airbus - Spares Direct Delivery Yes Yes 2. Despatch Advice (DA): 2.1. DA New links to external documents, 2 new fields added to M2M message Yes Yes 3. Airbus - Spares Direct Delivery (SDD): New process, further information / Summary Changes PO + DA 3.1. Airbus - Spares Direct Delivery (SDD): Summary Changes PO Yes Yes 3.2. Airbus - Spares Direct Delivery (SDD): Summary Changes DA Yes Yes Go-Live of these functionalities: Possible Impact: After especially CSV messages in the old mapping format will create errors, as new fields will be integrated into the existing format. This will change the order of fields SupplyOn AG Page 2 2

3 1. Purchase Order (PO) 2017 SupplyOn AG Page 3 3

4 1.1. Add OO to PO supplier M2M messages As-Is: The information contain names and telephone numbers, but the M2M messages does not contain an information about the address of the Ordering Officer (OO). To-Be: The new field Ordering Officer will be added for suppliers on M2M message Purchase Orders The new field will be added to the M2M messages CSV and BoostAero XML. For PO CSV message the position of the new field ORDERING_OFFICER_ will be between the 2 existing fields: ORDERING_OFFICER_PHONE (Ord. Off. Phone) MATERIAL_SUPPLIER_PLANNER_CODE (Supplier Planner Code) For PO BoostAero XML message the position of the new field Ordering Officer will be placed as follows: <asram:definedcitradecontact> <asram: uriciuniversalcommunication> <asram:uriidentifier>airsupply-user@supplyon.com</asram:uriidentifier> </asram: uriciuniversalcommunication> </asram:definedcitradecontact> 2017 SupplyOn AG Page 4 4

5 1.2. PO New links to external documents, 2 new fields added to M2M message (1/2) As-Is: For the moment, there is no dedicated field in the Purchase Order available for a link to external portals / documents. To-Be (1/2): There will be 2 new fields in M2M Purchase Order messages, one on Header, one Schedule Line level. The new field Document Link Header (Header level) will be added to the CSV and BoostAero XML PO messages. For PO CSV message the position of the new field PO_DocumentLinkHeader will be between the 2 existing fields: PO_HeaderText (PO Header Text) PO_CustRef (Customer Reference) For PO BoostAero XML message the position of the new field Document Link Header will be placed as follows: <asram:applicablecipohsupplychaintradeagreement> <asram:contractreferencedcireferenceddocument> <asram:uriidentificationidentifier> </asram:contractreferencedcireferenceddocument> </asram:applicablecipohsupplychaintradeagreement> 2017 SupplyOn AG Page 5 5

6 1.2. PO New links to external documents, 2 new fields added to M2M message (2/2) To-Be (2/2): The new field Document Link Line (Schedule Line level) will be added to the CSV and BoostAero XML PO messages. For PO CSV message the position of the new field PO_DocumentLinkLine will be between the 2 existing fields: PO_LineText (PO Line Text) PO_SerialNumReq (Serial Number Required) For PO BoostAero XML message the position of the new field Document Link Line will be placed as follows: <asram:associatedcidocumentlinedocument> <asram:publicationdatetime> t10:43:29</asram:publicationdatetime> <asram:uuidlineidentifier> </asram:associatedcidocumentlinedocument> 2017 SupplyOn AG Page 6 6

7 1.3. Field Reason for last status change to OPEN added As-Is: Since Release 2016 (Wave 2) there is a new filed on the user interface which indicates the reason for the last Status change to OPEN. For the moment, this field is only visible on the user interface is not available in M2M messages. To-Be: The new field Reason for last status change to OPEN will be added to the SupplyOn Def. View for suppliers and in the M2M messages. The new field Reason for last status change to OPEN will be added to the CSV and BoostAero XML PO messages. For PO CSV message the position of the new field PO_ReasonForLastStatusChangeToOPEN will be between the 2 existing fields: PO_Status (Status) PO_NewForCust (New for Customer) For PO BoostAero XML message the position of the new field Reason for last status change to OPEN will be placed as follows: <asram:orderingcisupplychainschedule> <asram:associatedcidocumentlinedocument> <asram:linestatuscode listname="reason">customer Accept</asram:LineStatusCode> </asram:associatedcidocumentlinedocument> </asram:orderingcisupplychainschedule> 2017 SupplyOn AG Page 7 7

8 1.4. Airbus - Spares Direct Delivery (SDD) (1/2) As-Is: There is currently no functionality available for the process Spares Direct Delivery. To-Be (1/2): For the new process Spares Direct Delivery, there will be 3 new fields in Purchase Order CSV and BoostAero XML message. Sales Price / Sales Price Currency / Routing Instruction For PO CSV message the position of the new fields PO_SalesPrice and PO_SalesPriceCurrency will be between the 2 existing fields: PO_RequestedAmount (Total Line Amount) PO_OriginalComment (Original Comment) For PO BoostAero XML message the position of the new fields Sales Price and Sales Price Currency will be placed as follows: SalesPrice: <asram:includedcinote> <asram:contenttext>18.66</asram:contenttext> <asram:subjectcode>sp</asram:subjectcode> </asram:includedcinote> SalesPriceCurrency: <asram:includedcinote> </asram:includedcinote> <asram:contenttext>eur</asram:contenttext> <asram:subjectcode>spc</asram:subjectcode> 2017 SupplyOn AG Page 8 8

9 1.4. Airbus - Spares Direct Delivery (SDD) (2/2) To-Be (2/2): The new field Routing Instruction will be added to the CSV and BoostAero XML PO messages. For PO CSV message the position of the new field PO_RoutingInstructions will be between the 2 existing fields: PO_ElemDelvSite (Elementary Delivery Site) PO_ShipToId (Delivery Party ID) For PO BoostAero XML message the position of the new field Routing Instruction will be placed as follows: <asram:specifiedcipolsupplychaintradedelivery> <asram:informationcinote> <asram:contenttext>ship from 8 to 11 am</asram:contenttext> <asram:subjectcode>ri</asram:subjectcode> </asram:informationcinote> </asram:specifiedcipolsupplychaintradedelivery> 2017 SupplyOn AG Page 9 9

10 2. Despatch Advice (DA) 2017 SupplyOn AG Page 10 10

11 2.1. DA New links to external documents, 2 new fields added to M2M message (1/2) As-Is: For the moment, there is dedicated field in the Despatch Advice for a link to external portals/ documents. To-Be (1/2): There will be 2 new fields in Despatch Advice M2M messages CSV and BoostAero XML. In these 2 fields the supplier can send for example a link to an external portal. The fields are always optional and can be filled by the supplier. The new field DOCUMENTLINKHEADER (Header level) will be added to the CSV DA message. The position of this field will be between the 2 existing fields: TRANSPORTMODE FLEXIBLEFIELD1 For DA BoostAero XML message the position of the new field Document Link Header (Header level) will be placed as follows: <asram:applicablecidahsupplychaintradedelivery> <asram:additionalreferencedcireferenceddocument> <asram:uriidentificationidentifier> </asram:additionalreferencedcireferenceddocument> <asram:applicablecidahsupplychaintradedelivery> 2017 SupplyOn AG Page 11 11

12 2.1. DA New links to external documents, 2 new fields added to M2M message (2/2) To-Be (2/2): The new field DOCUMENTLINKUE (UE level) will be added to the CSV DA message. The position of this field will be between the 2 existing fields: MANUFACTURINGCOUNTRY FLEXIBLEFIELD1_POS (used for Delivery Note Number ) For DA BoostAero XML message the position of the new field Document Link Line (UE level) will be placed as follows: <asram:includedcidalsupplychaintradelineitem> <asram:typecode>material</asram:typecode> <asram:specifiedcidalsupplychaintradeagreement> <asram:additionalreferencedcireferenceddocument> <asram:uriidentificationidentifier> </asram:additionalreferencedcireferenceddocument> </asram:specifiedcidalsupplychaintradeagreement> </asram:includedcidalsupplychaintradelineitem> 2017 SupplyOn AG Page 12 12

13 3. Airbus - Spares Direct Delivery (SDD) New process, further information / Summary Changes PO + DA 2017 SupplyOn AG Page 13 13

14 3.1. Airbus - Spares Direct Delivery (SDD): Summary Changes PO Most of the SDD information will be adapted to existing fields. There will 3 new PO fields, which are explained in chapter 1.4 ( Sales Price / Sales Price Currency / Routing Instruction ) These information should be communicated in the Spares Direct Delivery process from Airbus in the mentioned fields. Short Name Description Field Differentiate normal order and SDD order Final customer PO A normal order should be different from an order with a spares direct delivery. It s expected to be filled with SDD in case of a SDD order. The Customer PO should be communicated in the Purchase Order in AirSupply. The supplier needs to enter both reference in case of direct deliveries on their delivery notes. Elementary Delivery Site FlexField1 - PO schedule line level Shelf-life limitation Shelf Life in months for the ordered part. FlexField3 - PO schedule line level End-Customer Code The Customer Code should be communicated in the Purchase Order in AirSupply. FlexField5 - PO schedule line level End-Customer VAT-ID The VAT ID End-Customer should be communicated in AirSupply. FlexField7 - PO schedule line level Aircraft Registration number Sales price and Sales currency Routing instruction End-Customer SHIP-TO Code The Aircraft Registration number should be communicated in the dedicated fields in the PO Line. See chapter 1.4. Sales Price and Sales Currency are new fields on PO schedule line level. See chapter 1.4. The routing information is a new field on PO schedule line level for routing instructions to the supplier. The Ship to Code Reference should be communicated the Purchase Order in AirSupply. FlexField8 - PO schedule line level SalesPrice / SalesPriceCurrency RoutingInstructions DeliveryPartyID - PO schedule line level 2017 SupplyOn AG Page 14 14

15 3.2. Airbus - Spares Direct Delivery (SDD): Summary Changes DA For DA, all SDD information will be adapted to existing fields. These information should be communicated in the Spares Direct Delivery process by the supplier in the mentioned fields. Short Name Description Field Flight number The delivery information Flight number needs to be filled by the supplier. Flexible Field 1 - Header level AWB (AirWayBill) The delivery information AirWayBill needs to be filled by the supplier. Transport Document Country of origin The delivery information Country of origin needs to be filled by the supplier. Ship From Country SupplyOn AG Page 15 15

This Training documentation is for Access suppliers using the Purchase Order process.

Introduction This Training documentation is for E-Mail Access suppliers using the Purchase Order process. This process can be split into the following 4 main steps that are explained in details in the