10.07.2015 Views

BoostAero XML and CSV Implementation Guideline ... - SupplyOn

BoostAero XML and CSV Implementation Guideline ... - SupplyOn

BoostAero XML and CSV Implementation Guideline ... - SupplyOn

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

IMPLEMENTATION GUIDE for suppliers usingMachine-to-Machine (M2M) connection<strong>BoostAero</strong> <strong>XML</strong> <strong>and</strong> <strong>CSV</strong> <strong>Implementation</strong> <strong>Guideline</strong>Technical connection <strong>and</strong> integrationDocument Owner: <strong>SupplyOn</strong> Technical EDI ConsultantVersion: 3.8Date: June 2014Document available in English (only)Public 1/59


AuthorName Function ResponsibilityMario KischporskiGeorg BüxelAysel KirisgilSaskia RewitzerStefan Weggler<strong>SupplyOn</strong> AG,Project Team<strong>SupplyOn</strong> AG,Project Team<strong>SupplyOn</strong> AG,Technical EDI Consultant<strong>SupplyOn</strong> AG,Technical EDI Consultant<strong>SupplyOn</strong> AG,Technical EDI Consultant<strong>Implementation</strong> Guide initialMessage Format/InterfaceSpecifications/<strong>Guideline</strong>s (for <strong>BoostAero</strong> <strong>XML</strong>V2.10), explanations, sample files, Scheduler <strong>and</strong>Message Monitor screensMaintenance, until September 2011Maintenance, since October 2011Maintenance, since March 2012Document HistoryVersion Release date Description of Version0.1 - 0.5 2010 Template <strong>and</strong> initial content0.6 - 0.9 Q1 20111.0 June 2011 Release on website2.0 November 20112.1 24.01.20123.0 09.03.20123.1 April 2012Message formats, Interface specifications, explanations,sample files <strong>and</strong> scheduler addedMajor update:Layout updateDowntimes addedChange in 4.1.4 <strong>SupplyOn</strong> AS2 parameters <strong>and</strong> settings:Multiple Attachments: enabledIntegration of the <strong>CSV</strong> format description into the Boost<strong>XML</strong> guideHarmonization of AS2 subjects.Change in chapter 7, error h<strong>and</strong>ling.Change in chapter 6.1. Added DATETIME formatinformationChange in chapter 9. Added information regardingmessages sizes <strong>and</strong> limitations, automatic stop <strong>and</strong> timezonesChanged chapter 4.3.1. – BA <strong>XML</strong> default subjects3.2 May 2012Change in chapter 4.1.4 – AS2/MDN signature requirementcorrectedChange in chapter 4.1.5.3 – Screenshots updated3.3 July 2012 Added chapter 10.3 Partner acts as seller <strong>and</strong> buyer3.4 September 2012Adjusted description in chapter 9.2.5, scheduler option “onlynew” for Purchase Orders.3.5 February 20134.1.4 Added trusted certificate information for<strong>BoostAero</strong>Space members3.6 March 2013 9.2.5 Added missing Order Status “Partially Received” <strong>and</strong>“Rejected” to Scheduler (SSW)Public 2/59


3.7 January 2014 5.5 Added information about the Indentation suppression /“Pretty print” option3.8 June 2014 5.5 Pretty print format options – Update6.2 <strong>CSV</strong> encoding specification – Update8.2.1.2 Phase 2Added information for provision of test data9.2.3 Message Scheduler OverviewCustomer Group specific configuration9.2.7 Message Scheduler Details – Stock InformationChapter update – Information about new filter options forgoods receipt messagesPublic 3/59


List of abbreviationsAS2ASNBICBISBIS TPMCPCRLF<strong>CSV</strong>EAIEDIApplicability Statement 2 (= specification for data exchange)Advance Shipping NotificationBusiness Integration Conversion (the conversion module of the BIS executing themessage conversion/translation into another format)SEEBURGER Business Information Server (<strong>SupplyOn</strong>’s EDI messaging systemsoftware)BIS Trading Partner Management (e.g. <strong>SupplyOn</strong>’s configuration of all AS2communication partners within the BIS)Control PointCarriage Return Line FeedComma or (Semi) Colon Separated Values (Message Format)Enterprise Application Integration (system)Electronic Data InterchangeEDIINT AS2 Electronic Data Interchange Internet Integration – Applicability Statement 2HTTPHTTPSIMOM2MMDNSBSCMSOSSLVMI<strong>XML</strong>XSDHypertext Transfer ProtocolHypertext Transfer Protocol Secure (encryption vs. HTTP via SSL)Inventory MonitorMachine-to-Machine connectionMessage Disposition NotificationSelf BillingSupply Chain Management<strong>SupplyOn</strong>Secure Socket LayerVendor Managed InventoryExtended Markup Language<strong>XML</strong> Schema Definition (definition of the structure for <strong>XML</strong> documents)Public 4/59


Table of content1 Purpose of the document ................................................................................................................... 72 New shared aerospace SCM platform by <strong>SupplyOn</strong> ....................................................................... 73 Message Types .................................................................................................................................... 84 Communication type ......................................................................................................................... 124.1 AS2 via Internet (HTTPS) 124.1.1 Technical process of the communication ............................................................................. 124.1.2 Message Disposition Notification (MDN) .............................................................................. 134.1.3 Preconditions for AS2 communication .................................................................................. 134.1.4 <strong>SupplyOn</strong> AS2 parameters <strong>and</strong> settings .............................................................................. 144.1.5 AirSupply M2M Certificate Overview .................................................................................... 164.1.6 AirSupply CLEO LexiCom Communication Client Product <strong>and</strong> Service Fact Sheet Flyer ... 204.2 Shared EAI systems 214.3 Message (type) <strong>and</strong> AS2 subject 214.3.1 AS2 subjects for <strong>BoostAero</strong> <strong>XML</strong> ......................................................................................... 214.3.2 AS2 subjects for <strong>CSV</strong> ........................................................................................................... 225 <strong>BoostAero</strong> <strong>XML</strong> V2.10 message format <strong>and</strong> message types ........................................................ 235.1 General message rules 235.2 <strong>BoostAero</strong> <strong>XML</strong> V2.10 general message rules 235.3 <strong>BoostAero</strong> <strong>XML</strong> V2.10 message types 245.4 <strong>BoostAero</strong> <strong>XML</strong> V2.10 message format guidelines 245.5 <strong>BoostAero</strong> <strong>XML</strong> V2.10 pretty print format options 246 <strong>CSV</strong> message format <strong>and</strong> message types ...................................................................................... 256.1 General message rules 256.2 <strong>CSV</strong> general message rules <strong>and</strong> message structure 256.3 <strong>CSV</strong> message types 256.4 <strong>CSV</strong> message format guidelines 267 Routing/Syntax check & error h<strong>and</strong>ling.......................................................................................... 277.1 Error codes for all message types 277.2 Error codes for specific messages 288 Organization of integration projects ............................................................................................... 318.1 Organization, milestones <strong>and</strong> acceptance criteria for the integration project 328.2 Phases <strong>and</strong> acceptance 328.2.1 Phases .................................................................................................................................. 328.2.2 Acceptance ........................................................................................................................... 369 M2M transmission configuration ..................................................................................................... 369.1 Limitations <strong>and</strong> message sizes 369.1.1 Limitations ............................................................................................................................. 369.1.2 Message sizes ...................................................................................................................... 369.2 Message Scheduler 379.2.1 Time Zone ............................................................................................................................. 379.2.2 Automatic Stop...................................................................................................................... 379.2.3 Overview ............................................................................................................................... 389.2.4 Message Scheduler Details - 10 Forecast / Dem<strong>and</strong> Forecast ............................................ 429.2.5 Message Scheduler Details Display - 20 PO / Order ........................................................... 439.2.6 Message Scheduler Details - 40 VMI_GrossDem<strong>and</strong>s / VMI Dem<strong>and</strong> Forecast ................. 509.2.7 Message Scheduler Details Display – Stock Information ..................................................... 519.2.8 Message Scheduler Details – 46 VMI Monitor / Inventory Forecast .................................... 549.2.9 Message Scheduler Details - 50 SBI / Self Billing ................................................................ 559.3 Message Monitor 56Public 5/59


1 Purpose of the documentThis document functions as an <strong>Implementation</strong> Guide for suppliers to connect to the new sharedEuropean aerospace Supply Chain Management (SCM) Platform via a Machine-to-Machine (M2M) - alsoknown as EDI - connection. The <strong>Implementation</strong> Guide includes both technical details <strong>and</strong> generalinformation for high-level (business) context in order to provide suppliers with all necessary information.M2M/EDI with the SCM Platform means EDI from/to a supplier to/from the SCM application there is nodirect EDI connection or direct message flow between a supplier <strong>and</strong> its customer without the SCMapplication.2 New shared aerospace SCM platform by <strong>SupplyOn</strong><strong>SupplyOn</strong> sets up Supply Chain Management Platform for Airbus <strong>and</strong> other companies in the Europeanaerospace industry.<strong>SupplyOn</strong>, a globally leading provider of web-based solutions for Supply Chain Management (SCM) in themanufacturing industry, has been commissioned by Airbus to set up a platform to optimize logisticsprocesses. This platform will be available to all EADS divisions, as well as the entire European aerospaceindustry. It forms the basis for st<strong>and</strong>ardized, efficient SCM processes in the industry, <strong>and</strong> will supportcooperation with suppliers <strong>and</strong> make it more transparent.To drive forward process st<strong>and</strong>ardization within the European aerospace industry, Airbus is cooperatingin this project within EADS with Eurocopter <strong>and</strong> Astrium, <strong>and</strong> across <strong>and</strong> beyond EADS borders withthree other important corporate groups in the industry: Dassault Aviation, Safran <strong>and</strong> Thales. Thecooperation entitled <strong>BoostAero</strong>Space began in mid-2010. The initiative's objective is to communicate viaa central aerospace SCM platform with suppliers across several levels, <strong>and</strong> to replace the individualsupplier portals currently used."With this shared SCM platform for cross-company cooperation we are significantly strengthening thecompetitive position of European aerospace companies, <strong>and</strong> at the same time also making aconsiderable contribution to our cost reduction targets," says Matthias Naumann, Senior Vice President,Global Information Management Services <strong>and</strong> EADS. "The industry approach, which <strong>SupplyOn</strong> hasapplied in the automotive industry with great success, played a critical role in choosing this technologypartner."The new aerospace platform supports the collaborative SCM processes between customers <strong>and</strong>suppliers within the aerospace industry, <strong>and</strong> enables foresighted capacity planning, interactive fine tuningof delivery quantities <strong>and</strong> delivery dates, as well as order status tracking. All processes administered viathe platform are completely integrated into the internal systems of the company using it.Public 7/59


# Message Types(<strong>BoostAero</strong> <strong>XML</strong> /<strong>CSV</strong>)1 Dem<strong>and</strong> Forecast /Dem<strong>and</strong> ForecastOverview2 Dem<strong>and</strong> ForecastResponse /Dem<strong>and</strong> ForecastConfirmation3 Order /OrderOverviewDirectionToSupplierFromSupplierToSupplierDescriptionThe forecast process receives the forecast data from the ERPsystem <strong>and</strong> allows customers <strong>and</strong> suppliers to collaborate onforecast data. The forecast data is published by the ERPsystem frequently (supposed to export data once a week).The data contains of a header <strong>and</strong> a set of detail lines whilethe header describes the forecast in common such ascustomer material number, supplier ID, customer ID <strong>and</strong> thedetail lines contain the dem<strong>and</strong> quantities related to a dem<strong>and</strong>date. The imported customer forecast data is organized inhorizon types depending on the materials logistic family whileeach horizon is split into buckets which represent a timesubset of the horizon (a week or a month). The data isorganized in firm horizon, flexible horizon <strong>and</strong> provisionalhorizon. The firm horizon contains of all dem<strong>and</strong>s which areno longer subject of forecasting anymore (<strong>and</strong> are subject tobe already h<strong>and</strong>led by PO). The flexible horizon contains of alldem<strong>and</strong>s in the short term range which require a commitmentof supplier. The provisional horizon contains of all dem<strong>and</strong>s ina long term range which do yet not require a commitment ofthe supplier (but is optional for supplier to edit commitment).The supplier sends forecast confirmation message to theAirSupply application. Suppliers are requested to commit thedem<strong>and</strong>ed quantity by editing the forecast data in field„Supplier Commitment“ while customer users are required toagree on the committed supplier quantities in field „CommitTuning“. To notify either customer as well as supplier ofquantity mismatches as difference between the dem<strong>and</strong>edquantity <strong>and</strong> the supplier committed quantity, the systemmaintains exceptions which are supposed to highlightrequired activity in order to remove the quantity mismatchesby finding an agreement between customer <strong>and</strong> supplier.The purchase order process receives the PO data from thecustomer ERP system <strong>and</strong> allows customers <strong>and</strong> suppliers tocollaborate on the PO schedule line level. By performingchanges on the PO schedule line data, the customer <strong>and</strong>supplier can request changes regarding date, quantity <strong>and</strong>price, while each of this values can be enabled or disabled forcollaboration on customer level. On each completedcollaboration sequence, the changed data is submitted backto the ERP system. During its lifecycle the PO receiveschanges in its data material while all changes are submittedfrom ERP as order change requests <strong>and</strong> are read-only onAirSupply side. Furthermore the AirSupply PO processreceives changes in logistical values for shipped <strong>and</strong> receivedquantities by either ASN process or by Goods Receiptprocess.The logistical values influence the collaboration by (e.g.) notallowing reduction of PO schedule line quantities below thelogistical values – hence PO cannot be reduced in quantityPublic 9/59


# Message Types(<strong>BoostAero</strong> <strong>XML</strong> /<strong>CSV</strong>)4 Order Response /OrderConfirmation5 Despatch Advice /Despatch_Advice6 Stock Information:Inventory Forecast,Consumption Report<strong>and</strong>Receipt Advice /VMI_StockinformationDirectionFromSupplierFromSupplierToSupplierDescriptionbelow the quantities the supplier has already shipped or thequantities the customer has already received.The supplier sends order response data to the AirSupplyapplication. By performing changes on the PO schedule linedata, the supplier can request changes regarding date,quantity <strong>and</strong> price, while collaboration on these values can beenabled or disabled on customer level <strong>and</strong>/or on schedule linelevel. The non changes are for the supplier read-only.The following action codes are valid:- MODIFY- REJECT- ACCEPTThe Despatch advice is an electronic delivery notification sentby the supplier to the customer after goods pick-up, in order tooptimize the goods receipt process. It allows to:- know when the material has been dispatched or willbe ready for despatch- have the precise details of the shipment- facilitate the good receipt process by scanning the“UX label"- Reduce administrative acceptance disputes duringthe goods receipt because despatch advice data ischecked <strong>and</strong> the supplier will be notified about errorsbefore sendingThere are two main use cases covered by the stockmovement process:1) Goods receipt notifications sent by the customer to thesupplier referring to regular purchase orders. The goodsreceipt notification includes:- received quantity- cancelled quantity (to cancel a goods receipt that wasentered in error)- returned quantity (returned items that are poor quality,incomplete or damaged)The goods receipt information updates the state model of thepurchase order in AirSupply accordingly.2) Stock information sent by the customer to the supplierreferring to articles managed by VMI. In VMI the supplierneeds detailed information about the buyer’s current stocklevels <strong>and</strong> all corresponding movements. The notification sentby the buyer can therefore include:- goods receipt information (like in the purchaseorder process)- consumptions- movements regarding ownership (consignmentbuyer)- movements regarding stock type (qualityblocked free)Public 10/59


# Message Types(<strong>BoostAero</strong> <strong>XML</strong> /<strong>CSV</strong>)Direction7 Inventory Monitor ToSupplier8 Dem<strong>and</strong>Forecast (VMI) /VMI_Dem<strong>and</strong>s9 Supply Notification /VMI_Planned Receipt10 Self Billing /Self-Billing11 Back ControlMessage / StatusNotificationToSupplierFromSupplierToSupplierToSupplierDescription- Current stock level informationThe stock movements will update the VMI module inAirSupply accordingly (dem<strong>and</strong> netting).IMO (Inventory Monitor) is an aggregation of Stock Level(Total stock information), Material master Data (Materialnumbers/descriptions, Min/Max, Days of Supply etc.),Inventory Projection (includes the projected stock, thedem<strong>and</strong>s, the unconsumed dem<strong>and</strong>s, the in-transits, plannedreceipts, min/max stock, <strong>and</strong> min/max delivery proposal <strong>and</strong>timestamps of the last dem<strong>and</strong>-/stock updates etc. In the IMOoutbound message all day time buckets are included withdem<strong>and</strong> values or change in the average dem<strong>and</strong>. The IMOmessage contains the data shown in the screen “InventoryProjection” in AirSupply.Vendor Managed Inventory (VMI) dem<strong>and</strong>s or updates aresent to the supplier with this message type.The In-Transits quantities reflect the quantities contained inthe despatch advices the supplier already created. Anycreation of a new despatch advice will result in an increase ofthe related In-Transit quantities. A supplier can createdespatch advice either directly or on the basis of previouslycreated planned receipts. In the latter case, the creation of anew despatch advice will systematically decrease the related“planned receipt” quantities by the parts contained in thedespatch advice .At the same time, the In-Transit quantity willbe increased by the same amount.Invoice data is sent to the supplier for self billing.The message will be sent to the supplier in case of an importerror at AirSupply.Public 11/59


4 Communication typeAfter registration with <strong>SupplyOn</strong> the connection to <strong>SupplyOn</strong> is set up via AS2 via HTTPS (e.g. with theCLEO LexiCom Communication Client).4.1 AS2 via Internet (HTTPS)AS2 is a communication protocol st<strong>and</strong>ard for secure data transfer via the Internet. Electronic businessdocuments of any format (e.g. <strong>CSV</strong>, <strong>BoostAero</strong> <strong>XML</strong>) can be exchanged between business partners viaAS2.EDIINT AS2Supplier <strong>SupplyOn</strong> Customer4.1.1 Technical process of the communicationAS2 uses an "envelope" in which the EDI data is embedded, which then is submitted securely over theInternet. The data is transmitted with the Hypertext Transfer Protocol (HTTP), the core technology of theWorld Wide Web. The sender receives a digital receipt confirmation directly from the AS2 protocol, anMessage Disposition Notification (MDN), with which the sender can e.g. prove a delivery on time.An advantage <strong>and</strong> core characteristic of AS2 over other communication protocols is that with AS2 the(EDI) user is not dependent on deep technical message disposition protocols (e.g. on network level) butcan use the MDN as proof in message form.HTTPS functions as the transport protocol or layer, AS2 functions as the communication protocol or layer.Additional encryption over HTTP is done via SSL.HTTP headerMessage bodyMessage SignatureAS2 MessageAS2 MDNmethod POST POST AS2-to AS2 receiver AS2 receiverAS2-from AS2 sender AS2 senderAS2-subject Message subject Message subjectcontent-type multipart/signed multipart/signedcontent-length mime declaration mime declaration content-type text/xml message/disposition-notificationcontent-length Message (xml) message MDNmime declaration content-type application/pkcs7-signature application/pkcs7-signaturecontent-length SHA1-Signature signature signaturePublic 12/59


4.1.2 Message Disposition Notification (MDN)The purpose of the MDN is to acknowledge the receipt of a payload message. An MDN containsmachine-readable information on the delivery state of the payload message. E.g., it contains the messagedigest (MIC) of the payload message as calculated by the recipient.All AS2-messages which were sent to <strong>and</strong> successfully received by <strong>SupplyOn</strong> will lead to asynchronous MDN. The MDN is delivered in combination with the HTTP(S) response to the HTTP(S)request that carried the payload message.For the outbound direction (<strong>SupplyOn</strong> sending) it will be agreed during the integration project if the MDNshould be synchronous or asynchronous.Note: All status notification messages (see below chapter on error h<strong>and</strong>ling) are sent asynchronouslywithin a new HTTP(S) session.4.1.3 Preconditions for AS2 communicationPreconditions for the data exchange via AS2 are permanent Internet access <strong>and</strong> AS2 Drummond certifiedsoftware (e.g. the CLEO LexiCom Communication Client) on the supplier side which is able to h<strong>and</strong>lemulti MIME attachments.For the suppliers, who are using their own AS2 Client instead of the Cleo Client.Please check your AS2 Client, if the Client is able to provide the AS2 Subject in the corresponding field“subject”.If your AS2 Client is providing the AS2 Subject in the field content-disposition, please contact your AS2Client provider to see how you can use the subject field.<strong>SupplyOn</strong> is not able to read out the AS2 Subject from the field content-disposition.Example:AS2-To: SOAIRSTESTAS2-From: PartnerAS2TDate: Mon, 5 Sep 2011 02:51:34 GMTSubject: DEMAND FORECAST RESPONSEMessage-ID: AS2-Version: 1.2EDIINT-Features: AS2-ReliabilityDisposition-Notification-To: PartnerAS2TDisposition-Notification-Options: signed-receipt-protocol=optional,pkcs7-signature;signed-receiptmicalg=optional,sha1content-type: multipart/signed; micalg=SHA1; protocol="application/pkcs7-signature";boundary="_=2827911803508083Sterling2827911803508083MOKO"--_=2827911803508083Sterling2827911803508083MOKOContent-type: Application/<strong>XML</strong>content-disposition: attachment; filename="DEMAND FORECAST RESPONSE"content-id: Public 13/59


4.1.4 <strong>SupplyOn</strong> AS2 parameters <strong>and</strong> settingsThe communication settings per supplier are done on the <strong>SupplyOn</strong> EDI messaging system side(<strong>SupplyOn</strong> uses state of the art EDI messaging system software, the SEEBURGER Business IntegrationServer (BIS) in version 6 with the EDIINT AS2 Drummond certified communication adapter).On the supplier side the supplier is required to make the correct <strong>and</strong> corresponding communicationsettings.For the connection <strong>and</strong> technical M2M integration you will receive the AS2 parameter sheet with the<strong>SupplyOn</strong> AS2 parameters alongside with this <strong>Implementation</strong> Guide. Please fill out this parameter sheetcarefully <strong>and</strong> send it to EDI-Connect@<strong>SupplyOn</strong>.com.The <strong>SupplyOn</strong> Server Certificates are attached to the AS2 parameter sheet.The following settings apply to the AS2 setup to connect to <strong>SupplyOn</strong> as default. Exceptions from thedefault are not permitted.Payload Signing:Payload Encryption:Payload Compression:Transmission over HTTPS:Basic Authentication:MDN Signing:Multiple Attachments:enableddisabledenabled, using gzip algorithmenableddisabled (not required due to Certificate-based authentication)enabledenabledPublic 14/59


SecurityTransport LayerAS2 Settings Requirements ExplanationFor certificate based authentication trusted certificates arerequired. Self created/self signed certificates are NOT allowed.Only trusted certificates from the Trusted/Certificate Authorities(CA) are allowed, e.g.- Symantec/ VeriSignhttp://www.verisign.comIncluding its subordinate br<strong>and</strong>s GeoTrust, Equifax <strong>and</strong> Thawte- Commodohttp://www.comodo.com- TC TrustCenterhttp://www.trustcenter.deCommunicationCertificateTrustedTrusted: A Certificate Authority (CA) assigns, administrates<strong>and</strong> controls certificates. <strong>SupplyOn</strong> requires Class 2certificates.The validity is dependent on the certificate type. As the CA rootcertificates are trusted by <strong>SupplyOn</strong> the supplier needs toensure that he uses a valid (<strong>and</strong> not expired) certificate.Otherwise the AS2 connection to <strong>SupplyOn</strong> would be denied.24 months is the st<strong>and</strong>ard certificate validity.Certificate RequirementAS2 <strong>and</strong> SSL Certificate(key usage: digital signature <strong>and</strong> encryption)<strong>BoostAero</strong>Space members (BASM) may use X.509 certificatesissued by a BASM internally operated Certificate Authority(BASM PKI) which is compliant with the requirements definedin [BASBCP].- The accepted usage of certificates issued by a compliantBASM PKI is limited to technical M2M connectionsbetween BASM in their role as "M2M Supplier" <strong>and</strong><strong>SupplyOn</strong> unless agreed otherwise.- Test or basic validation certificates (e.g. based on E-Mailaddress or domain verification) issued by the issuingcertificate authority are not accepted for use in productionenvironments. BASBCP Boost Aerospace - BridgeCertificate Policyhttp://www.boostaerospace.com/SMA/<strong>BoostAero</strong>spaceBridgeCP.pdfDigital Signature _ Digital signature is required.Encryption_No additional encryption of the data is necessary, since thecommunication is already SSL encrypted (HTTPS)!Internetconnection- PermanentInternetconnection- Fixed <strong>and</strong>public URL or IPaddressm<strong>and</strong>atoryA permanent Internet connection has to be granted.Public 15/59


ClientAuthenticationMDNAS2 Settings Requirements ExplanationTransportProtocolAS2 via secureHTTP (HTTPS)HTTPS is a special form of the HTTP protocol offeringincreased security via SSL (128 Bit encryption). HTTPS isused to prevent the „observation“ during the transmission ofsensitive data.BasicAuthentication_Authentication of the sending interface system during thereceipt via username <strong>and</strong> password is NOT required <strong>and</strong> NOTpossible. Authentication is done via signing/certificates (seeCommunication Certificate for certificate based authentication).MDNM<strong>and</strong>atory(synchronous orasynchronous)The MDN is an instrument for transaction security. The MDN issent back by the recipient. It confirms the message receipt <strong>and</strong>provides proof that the correct recipient was reached, since hewas in the possession of the private key.The MDN is returned synchronously.MDN signed _ MDN signature is required.MDN encryption _No additional encryption of the MDN is necessary, since thecommunication is already SSL encrypted (HTTPS)!4.1.5 AirSupply M2M Certificate OverviewScope of the certificate overview is a set of recommendations when using X.509 v3 certificates forsupplier authentication in Machine to Machine (M2M) communication scenarios within the AirSupplysolution. M2M scenarios include communication based on the AS2 protocol as well as the HTTPSprotocol.The following areas are explicitly not in scope: User certificates which prove the identity of supplier or customer users of the <strong>SupplyOn</strong>marketplace or their corresponding organization. Other SSL/TLS server-authentication, E-Mail, <strong>XML</strong>-Security, code-signing, time-stamping, VoIP,IM, Web services, etc.4.1.5.1 General Topics<strong>SupplyOn</strong> will determine which CA certificates are included in M2M components on the <strong>SupplyOn</strong>marketplace, based on the benefits <strong>and</strong> risks of such inclusion to our customers.<strong>SupplyOn</strong> reserve the right to not include a particular CA certificate or to discontinue including aparticular CA certificate in M2M components on the <strong>SupplyOn</strong> marketplace at any time <strong>and</strong> forany reason.<strong>SupplyOn</strong> will not allow the usage of SELF-SIGNED CERTIFICATES in PRODUCTIONenvironments to prevent misuse due to missing certificate registration <strong>and</strong> managementprocesses. SELF-SIGNED CERTIFICATES may be used in TEST environments withoutPRODUCTION data.4.1.5.2 Generic Certificate RecommendationsAll certificates used for digital identities in scope of the PRODUCTION M2M connection to the suppliershould conform to the following criteria: The certificate is issued by one of the certificate authorities listed Trusted Issuers The assurance level of the corresponding registration process must assert the holder identity to alevel equal or comparable to the “Extended Validation” Test or basic validation certificates (e.g. based on E-Mail address or domain verification) issuedby the [Trusted Issuers] shall not be accepted.Public 16/59


4.1.5.3 Trusted Issuers (Certificate Authorities List)The following trusted issuers have been chosen to be accepted in scope of this context:Id. Certificate Authority Detail Information1 Symantec/ VeriSign http://www.verisign.comIncluding its subordinate br<strong>and</strong>s GeoTrust, Equifax <strong>and</strong>Thawte2 Commodo http://www.comodo.com3 TC TrustCenter http://www.trustcenter.de<strong>SupplyOn</strong> needs for the M2M Integration the following Certificate content:Key Usage: for digital signatureEnhanced Key Usage: for SSL encryptionPublic 17/59


A trusted Certificate contains up to three certificates for the key usage functionality. It is a chain.A self-signed certificate contains only one certificate for the key usage functionalityPublic 18/59


4.1.5.4 AS2 via the CLEO LexiCom AS2 Communication ClientIn case a direct AS2 connection is not possible for the supplier or the suppler does not use or haveDrummond AS2-certified EDI / Communication software, the supplier can establish a connection via AS2using the CLEO LexiCom Communication Client software. The CLEO LexiCom Client is an automatedcommunication solution for the secure transmission of data <strong>and</strong> EDI/<strong>CSV</strong>/<strong>XML</strong> messages over theInternet independent of the message formats submitted.A “Communication Client” (also referred to as “connector”) is a connection tool between a supplier <strong>and</strong>the new aerospace platform to establish connectivity for EDI.<strong>SupplyOn</strong> proposes/recommends only the CLEO LexiCom Client (in the most current version) as a preconfiguredCommunication Client to have a simple connection to <strong>SupplyOn</strong>. The supplier is free to useany other communication client. The CLEO LexiCom Client is pre-configured for a fast <strong>and</strong> easyconnection to <strong>SupplyOn</strong> with the correct AS2 parameters <strong>and</strong> settings. The supplier purchases the CLEOCommunication Client directly from ECS International BV in the Netherl<strong>and</strong>s – the main CLEO businesspartner in EMEA & Asia (license <strong>and</strong> support fees). Product support is provided directly by ECSInternational BV, by CLEO Inc, or an appointed CLEO reseller in your territory, but NOT by <strong>SupplyOn</strong>.Please refer to the attached CLEO LexiCom information.ECS International BV provides a LexiCom/<strong>SupplyOn</strong> installation & implementation service for a fixedprice – please also refer to the pricing <strong>and</strong> services information document by ECS.The CLEO LexiCom Client is AS2 Drummond certified.CLEO LexiCom e.g. builds an AS2 / HTTPS encrypted secure communication between exchangingparties. It can be installed in 30 minutes <strong>and</strong> is easy to configure <strong>and</strong> to administrate. The supplier c<strong>and</strong>ownload the CLEO LexiCom software <strong>and</strong> the pre-configured hosts for both the TEST <strong>and</strong>PRODUCTION environments, so the solution will present a pre-configured state for a <strong>SupplyOn</strong>connection. For detail instructions please refer to the step-by-step guide attachment by ECS.CLEO LexiCom communicates over the Internet with the <strong>SupplyOn</strong> SEEBURGER Business IntegrationServer (BIS), the EAI layer for the SCM application.Public 19/59


4.1.6 AirSupply CLEO LexiCom Communication Client Product <strong>and</strong> Service Fact Sheet FlyerOverview:<strong>SupplyOn</strong> cooperates with ECS International BV (operating as CLEO Europe) to provide the CLEOLexiCom communication client as a fully tested <strong>and</strong> integrated software to connect to <strong>SupplyOn</strong> AirSupplyfor M2M Supplier Integrations. The CLEO LexiCom software is pre-configured for the necessary<strong>SupplyOn</strong> AirSupply connectivity settings.M2MSuppliersIndustrialCustomersERP<strong>BoostAero</strong> <strong>XML</strong><strong>CSV</strong> MessagesLexiComERP<strong>BoostAero</strong> <strong>XML</strong><strong>CSV</strong> MessagesLexiCom<strong>SupplyOn</strong>AirSupplyERP<strong>BoostAero</strong> <strong>XML</strong><strong>CSV</strong> MessagesLexiComOther IndustrialCustomersOptional:Using ECS Transformation Servicesor VL Trader4.1.6.1 Product & Pricing:CLEO LexiCom is a high quality Drummond-certified communication software product supporting allst<strong>and</strong>ard communication protocols such as AS2, ebMS <strong>and</strong> others. CLEO LexiCom includes the preconfigured<strong>SupplyOn</strong> AirSupply AS2 settings for both TEST <strong>and</strong> PRODUCTION. The product <strong>and</strong> supportfees are:- Euro 999,-- (list price one time licence fee, purchased directly from the supplier from ECS)- Euro 199,80 (annual support fee, purchased directly by the supplier from ECS)This pricing is guaranteed until end of 2012. Certificate cost for the required AirSupply certificate-basedAS2 authentication may occur additionally on the supplier side by purchasing trusted certificates from therecommended Trusted Certificate Authorities. Please refer to the <strong>SupplyOn</strong> AirSupply M2M SupplierIntegration <strong>Implementation</strong> Guides regarding certificate requirements.4.1.6.2 <strong>Implementation</strong> & Testing Service <strong>and</strong> Pricing:ECS provides a ‘ready to communicate’ implementation service solution at a fixed price.For a fixed price of Euro 350,-- ECS provides the following <strong>Implementation</strong> & Testing Service as adefault service for each CLEO LexiCom communication client software purchase:- ECS will set-up <strong>and</strong> implement - via a remote connection to your server - all the requiredsettings so that you will be ready to exchange test messages via the AS2 TEST connectionwith <strong>SupplyOn</strong> via self-signed certificates.- We assist with the requirements for Signed / Trusted certificates for PRODUCTION.- After successful testing, ECS will finalize <strong>and</strong> test the implementation with all settings for theAS2 PRODUCTION connection with <strong>SupplyOn</strong> AirSupply– in order to go LIVE!Public 20/59


The Euro 350,-- implementation <strong>and</strong> testing service charge is sponsored by <strong>SupplyOn</strong> <strong>and</strong>h<strong>and</strong>led directly between <strong>SupplyOn</strong> <strong>and</strong> ECS. The supplier can opt-out not to use this service.All technical setup documentation <strong>and</strong> details on licensing, pricing <strong>and</strong> services can be found on the ECSwebsite: http://www.ecs-europe.nl > <strong>SupplyOn</strong> AirSupplyWhen you prefer ‘on site’ implementation services, please contact ECS under below contactinformation.All prices do not include VAT.ECS International B.V., Netherl<strong>and</strong>sProject Manager: Mr. Fred RinkelTelephone +31 229 574331Website: www.ecs-europe.nle-Mail: sales@ecs-europe.nl4.2 Shared EAI systemsDifferent supplier organizations (hence different <strong>SupplyOn</strong> customers) may use the same EAI system totransmit messages to <strong>SupplyOn</strong>. In this case the shared EAI system must ensure that each organizationinitiates an HTTPS session.Therefore it is not possible to transmit messages of different organizations within one HTTPStransmission.4.3 Message (type) <strong>and</strong> AS2 subjectA message subject is used to identify the message type (e.g. Order).An AS2 header field named SUBJECT is m<strong>and</strong>atory to allow the identification of the transmitted messagetype. The content of the SUBJECT field has to be individually agreed between <strong>SupplyOn</strong> <strong>and</strong> thesupplier. <strong>SupplyOn</strong> proposes the following values for the message type SUBJECT.4.3.1 AS2 subjects for <strong>BoostAero</strong> <strong>XML</strong>No. Message Type AS2 SUBJECT1 Dem<strong>and</strong> Forecast DEMAND_FORECAST2 Dem<strong>and</strong> Forecast Response DEMAND_FORECAST_RESPONSE3 Order ORDER4 Order Response ORDER_RESPONSE5 Despatch Advice DESPATCH_ADVICE6Stock Information:Inventory ForecastConsumption ReportReceipt AdviceInventoryForecastConsumptionReportReceiptAdviceAttention: The Stock Information consists of 3 different message types. Depending on themessage type one of the 3 AS2 subjects will be used.7 Inventory Monitor VMI_IMO_INVENTORY_FORECAST8 Dem<strong>and</strong> Forecast (VMI) VMI_DEMAND_FORECAST9 Supply Notification SUPPLY_NOTIFICATION10 Self Billing SELF_BILLING_INVOICE11 Back Control Message BACK_CONTROL_MESSAGEPublic 21/59


4.3.2 AS2 subjects for <strong>CSV</strong>No. Message type AS2 SUBJECT1 Dem<strong>and</strong> Forecast Overview ForecastOverview2 Dem<strong>and</strong> Forecast Confirmation ForecastConfirmation3 OrderOverview OrdersOverview4 OrderConfirmation OrderConfirmation5 Despatch_Advice SellerASN6 VMI_Stockinformation StockInformationAttention: Depending on the settings in the Message Scheduler one of the 3 Stock Informationmessage types will be received.7 Inventory Monitor IMO8 VMI_Dem<strong>and</strong>s SellerVMIDem<strong>and</strong>s9 VMI_Planned Receipt PlannedReceipts10 Self-Billing SellerSBInvoice11 Status Notification StatusNotificationPublic 22/59


Technical information <strong>and</strong> assistance: Samy Scemama, samy.scemama@boostmanagement.com,(+33) 6 10 25 45 595.3 <strong>BoostAero</strong> <strong>XML</strong> V2.10 message typesThe <strong>BoostAero</strong> <strong>XML</strong> V2.10 message types correspond 1:1 to the AS2 subject (see chapter 4.3.1 AS2Subjects for <strong>BoostAero</strong> <strong>XML</strong>).5.4 <strong>BoostAero</strong> <strong>XML</strong> V2.10 message format guidelinesThe message format guidelines for the respective business process are providing to you separately.<strong>BoostAero</strong> <strong>XML</strong> V2.10 sample files with explanations will be provided alongside with the messageformat guidelines. Interface specifications are used synonymously with the term message formatguideline. In this <strong>Implementation</strong> Guide <strong>and</strong> for the technical integration process the term MessageFormat <strong>Guideline</strong> is used.5.5 <strong>BoostAero</strong> <strong>XML</strong> V2.10 pretty print format optionsOnly until June 1 st 2014 the pretty print format is the default option for the <strong>BoostAero</strong> <strong>XML</strong> messagestructure, which means that the transferred messages contain indentations <strong>and</strong> linefeeds.This will be still valid for all suppliers which were connected before June 1 st 2014 to the productiveenvironment.<strong>SupplyOn</strong> however recommends not to use the pretty print format option, because the file size of themessages (files for the transmission) without indentations <strong>and</strong> linefeeds is significantly smaller.A change regarding format option can be done easily <strong>and</strong> separately for each message type duringruntime. Just send a corresponding request to EDI-Connect@<strong>SupplyOn</strong>.com.After June 1st 2014 the pretty format option is not used for the <strong>XML</strong> messages by default. All Supplierswhich will be connected after June 1 st 2014 to the productive environment will receive therefore all<strong>BoostAero</strong> <strong>XML</strong> messages from AirSupply without indentations <strong>and</strong> line breaks.Public 24/59


6 <strong>CSV</strong> message format <strong>and</strong> message typesAirbus recommends the use of <strong>BoostAero</strong> <strong>XML</strong> V2.10 as the message format for the M2M supplierintegration. Nevertheless, <strong>SupplyOn</strong> provides a simple way for a supplier to connect via M2M to<strong>SupplyOn</strong> by offering <strong>CSV</strong> as a message format.The <strong>CSV</strong> file format describes the structure of a text file for storage or for easy exchange of structureddata. The file extension “.csv” is an acronym for Comma Separated Values.The character encoding to use is no more defined, 7-bit ASCII is widely regarded as the lowest commondenominator.In <strong>CSV</strong> files can be tables or a list of lists of different lengths are shown within the text file, somecharacters have a special function to structure the data.- A symbol is used to separate data sets. This is usually the line break of the file-generatingoperating system - for the Windows operating system are in practice often actually twocharacters.- A symbol is used to separate data fields (columns) within the records. General for the comma isused. Depending on the software involved <strong>and</strong> user preferences <strong>and</strong> semicolon, colon, tab,space or other characters are common.- To use special characters in the data to, a text delimiters used. Normally this field delimiter is thequotation mark. "If the field delimiter itself is included in the data, it will be doubled in the datafieldAlongside with this <strong>Implementation</strong> guide you will receive the message format guidelines for each of themessage types.All <strong>CSV</strong> files within one transmission must be of the same message type because the message type istransmitted via the AS2 subject.6.1 General message rulesThe following rules apply to all messages (if no exception is specified within the respective fielddescription):- Negative numbers: The minus sign must be in front of the digits (e.g. -10)- Decimal numbers: Max. 5 decimal digits are allowed- DATETIME format is CCYYMMDDHHMMSS- DATE format is CCYYMMDD- TIME format is hhmmss- The currency will be described with 3 characters (e.g. EUR)6.2 <strong>CSV</strong> general message rules <strong>and</strong> message structureFor the <strong>CSV</strong> messages the following general rules apply:- Encoding is UTF-8- Each record is represented by one line- At the end of each line there is a CRLF (Carriage Return Line Feed), even if it is the last line of afile- The first line of a file is the header line (column names)- The delimiter character between fields is semicolon (;)- If the field value contains a semicolon the whole value must be enveloped by quotation marks(“…”)- If the field value contains a quotation mark, it must be duplicated (“”). The first character will beinterpreted as escape character6.3 <strong>CSV</strong> message typesThe <strong>CSV</strong> message types correspond 1:1 to the AS2 subject (see table chapter 4.3.2 AS2 Subjects for<strong>CSV</strong>)Public 25/59


6.4 <strong>CSV</strong> message format guidelinesThe message format guidelines for the respective business process are provided to you separately. <strong>CSV</strong>sample files with explanations will be provided alongside with the message format guidelines(also called interface description or specification).In this <strong>Implementation</strong> Guide <strong>and</strong> for the technical integration process the term Message Format<strong>Guideline</strong> is used.The color legend is very important for the messages that are sent from the supplier to the customer.Public 26/59


7 Routing/Syntax check & error h<strong>and</strong>lingIn case of routing or syntax errors, a dedicated message, type Status Notification, is used. The messagewill be sent via AS2 to the supplier. The message contains an error code .7.1 Error codes for all message typesError code Error Case Error Type DescriptionR001 Authorization error ROUTING ERRORSender ID <strong>and</strong> OrgCode within themessage mismatch with the BIS partnername stored in the CPR002 No entity found ROUTING ERRORNo entity was found in BIS TPM matchingwith the data from the messageR003 no buyer CP found ROUTING ERRORNo buyer CP found with the CP namegiven in the messageR004no networklinkNo networklink found with the buyer CPROUTING ERROR <strong>and</strong> the sellernumber given in thefoundmessageR005 no seller CP found ROUTING ERRORSeller CP given in the selected networklinkdoes not existR006R007R008R009no networkcommunicationrecord foundno supplytriggerfoundUnauthorized sellerControlPointMultiple sellerControlPointsROUTING ERRORROUTING ERRORROUTING ERRORROUTING ERRORS001 Parsing failed SYNTAX ERRORS002S003S004S005S006M<strong>and</strong>atory fieldmissingfield content toolongField content tooshortmismatching fieldtypeInvalid QualifierSYNTAX ERRORSYNTAX ERRORSYNTAX ERRORSYNTAXERRORSYNTAXERRORS007 Repetition Error SYNTAX ERRORC001 Missing reference CONTENT ERRORC002 Old message CONTENT ERRORNo network communication record foundat the networklink with matching logicalfilenameNo SupplyTrigger found in selectednetwork communication recordFor messages sent from a sellsidepartner: The seller ControlPoint which wasdetermined is not assigned to thecommunication partner that has sent themessageFor messages sent from a sellsidepartner: There is more than one sellerControlPoint ID determined within onetransmission<strong>SupplyOn</strong> is not able to parse the filebecause it’s not well formed or invalidregarding to the respective XSDA field defined m<strong>and</strong>atory in the interfacedescription is missingThe content of a field exceeds the max.length defined in the format descriptionThe content of a field falls below the min.length defined in the format descriptionThe content of a field doesn’t match thetype specified in the interface descriptionA code or qualifier within a field isunknownToo much repetitions for a field orsegmentA business object referenced in amessage doesn’t existA newer record than the importedmessage already exists *C003 Duplicate message CONTENT ERROR The message was already importedPublic 27/59


7.2 Error codes for specific messagesMessageErrorCodeDescriptionVMI_SO-PlannedShipmentsSO-OrderConfirmationSO-ForecastConfirmationC101C102C002C004C201C202C203C204C205C206C207C208C209C210C211C212C213C214C215C216C217C218C219C220C221C319C320C301C302C303C304C305C306Referenced material not foundUOM code in message differs from code UOM code in materialmaster dataAn newer record already exists at the application databaseA referred PO already exists at the application databaseInvalid field valueRequested quantity is below shipped quantityRequested quantity is below received quantityValue exceeds min/max limits for requested quantityRequested quantity is smaller than zeroThe requested quantity value mismatches the configured formatdirectionUnqualified requested date valueThe requested date exceeds the agreed dateValue exceeds min/max limits for requested dateCommon collaboration failureCollaboration failure due to collab mode restrictionsCannot perform any changes (usually depending on collab.mode)Change on a collab field which is not allowed for collaborationcannot perform the requested action (on the current status of POline)Missing comment on reject in simple modeMissing supplier acknowledgment number on commit in caseconfig. requires itKit not found/not loadableKit does not have a KIT headerKIT contains more than one headerKit does not contain any componentsAt least one component cannot be adjusted to give KIT headerquantityWrong data, e.g. no matching collaboration set foundPublishing failureVerification failureFirmHorizonStartDate of forecast header is before current weekThe firmHorizonPeriodUnit is invalidThe flexibleHorizonPeriodUnit is invalidThe provisionalHorizonPeriodUnit is invalidThe total horizon length exceeds the allowed maximum (36months)C307 Flexible horizon length may not be 0C308 Flexible bucket length may not be 0C309 Firm bucket length may not be 0 if horizon length > 0C310 Provisional bucket length may not be 0 if horizon length > 0C311The position is beyond the current horizon rangePublic 28/59


MessageSO-SellerASNErrorCodeC312C313C314C315C316C317C318C401C451C402DescriptionThe dem<strong>and</strong> quantity format does not match the uom formatThe delivery date of a position is beyond the horizon/sBucket structure definitions of the forecasts of a collab. set do notmatchUOMs of the forecasts of a collab. Set do not matchUOM Formats of the forecasts of a collab. Set do not matchCDTs of the forecasts of a collab. Set do not matchDVTs of the forecasts of a collab. Set do not matchInvalid UE numberM<strong>and</strong>atory UX field MissingPast estimated delivery dateC403 Missing Ship from name 2C404 Missing Ship from name 3C405C406C407C408C409C410C452C411C412C413C414C415C416C417C418C419C420C421C422C423C424C425C426C427C428C429C430C431C432C433C434C435C436Missing Ship from streetFuture manufacture datePast expiry dateInvalid label textInvalid batch numberMissing manufacturing countryM<strong>and</strong>atory header field missingM<strong>and</strong>atory address field missingWrong PO statusMissing manufacturerDuplicate serial numberInvalid number of serial numbersEmpty serial numberInvalid serial number lengthInvalid serial number charactersMissing purchase orderMismatching material numberMissing ship from addressMissing ship to addressMissing forwarder addressMismatching destinationInvalid UOMInvalid ship quantity precisionUX without positionsRemaining quantity is zeroPO shipping statusInvalid manufacturerMissing KIT headerMissing VMIASN without UXMissing UE weight UOMMissing UE weightMissing ASN modelsPublic 29/59


MessageErrorCodeC437C438C439C008C440C441C442C443C444C445C446C447C448C449C450DescriptionInvalid upload codeMissing ASN identifierMissing DA upload codeUE number not foundInvalid Transport ModeInvalid UX NumberMissing Serial NumberOnly one PO per UX is allowedThe shipped quantity is too smallThe shipped quantity is too bigThe shipped quantity is zeroThe shipped quantity isn't equal to the PO requested quantityKIT without HeaderKIT without componentsMissing m<strong>and</strong>atory UE fields.Public 30/59


Phase 1Phase 2Phase 3Phase 4Phase 5Phase 6Phase 78 Organization of integration projectsBefore the technical integration of the messages, the technical AS2 connection has to be set up first.Details on the integration process will be provided by the <strong>SupplyOn</strong> Technical EDI IntegrationManager.Public 31/59


As soon as the technical AS2 connection has been set up test messages will be exchanged between<strong>SupplyOn</strong> <strong>and</strong> the supplier. Please note that the test messages have to correspond to the <strong>SupplyOn</strong>message format guidelines.8.1 Organization, milestones <strong>and</strong> acceptance criteria for the integration project- The supplier has to prepare his system for sending <strong>and</strong> receiving messages via AS2 <strong>and</strong> toprocess AirSupply files before the project starts.- The <strong>SupplyOn</strong> contractual partner is responsible for receiving <strong>and</strong> sending messages, EDImapping, syntax validation <strong>and</strong> content accuracy of sent messages from <strong>SupplyOn</strong>.- The <strong>SupplyOn</strong> contractual partner has to configure the message scheduler. It contains allconfiguration options for creating a schedule which determines:• When a message will be sent to an EDI supplier (frequency)• Which content a message contains (filtering options)- The <strong>SupplyOn</strong> contractual partner has to use the message monitor. It shows a report over allmessages (inbound <strong>and</strong> outbound) for one supplier within the last 45 days.- Routing <strong>and</strong> syntax errors will be transmitted in the SO-Status Notification via AS2 connectionfrom <strong>SupplyOn</strong>.The integration phase starts with agreed project start date from the Deviating Price Agreement M2M.The project is scheduled for a period of maximum 10 weeks plus 2 weeks for migration preparation.PW (project week) 1 2 3 4 5 6 7 8 9 10 11 12Setup technical connectionPREPRD L<strong>and</strong>scapex x xProcess outbound messages x xProcess inbound messages Order Confirmationx Forecast Confirmationx VMI Planned Receiptsx8.2 Phases <strong>and</strong> acceptance8.2.1 Phases Despatch Advice x xAcceptance Test <strong>SupplyOn</strong>Setup technical connectionPRD L<strong>and</strong>scapeFollowing phases will be part of the project: Phase 1: Setup AS2 technical connection <strong>and</strong> testing on Integration L<strong>and</strong>scape Phase 2: Outbound message test Phase 3: Inbound message test Phase 4: Solution verification test Phase 5: Setup AS2 technical connection <strong>and</strong> testing on Productive L<strong>and</strong>scape Phase 6: Airbus migration - in responsibility of Airbus Phase 7: Post Go-Live supportxx x xProcess Post Golive Support x xPublic 32/59


8.2.1.1 Phase 1Setup AS2 technical connection <strong>and</strong> testingWork package: Duration 15 daysStep 1 - The Supplier <strong>and</strong> <strong>SupplyOn</strong> will be exchange the connectivity data for an AS2 connection. Bothparties have to setup the technical AS2 partner, firewall settings <strong>and</strong> certificates. After the technical setupthe connection test can start.Step 2 - The supplier has to provide a screenshot or a log file to <strong>SupplyOn</strong> when the AS2 setup wassuccessful.Test procedure- <strong>SupplyOn</strong> sends to the supplier a couple of test connectivity messages to verify the technical AS2connection functions.- The supplier verifies the AS2 Connection to/from <strong>SupplyOn</strong> is working.Acceptance criteriaEDI qualified person who underst<strong>and</strong>s AS2 technology <strong>and</strong> specific <strong>SupplyOn</strong> settingsThe validation is as follows- Two messages will be exchanged without errors from <strong>SupplyOn</strong> to the supplier- Two messages will be exchanged without errors from supplier to <strong>SupplyOn</strong>- The AS2 connection shows an SSL encryption- No firewall issues on message exchange- The certificate is from an approved institution8.2.1.2 Phase 2Outbound message testedWork packages: Duration 10 daysStep 1 -Test dataThere are two ways of providing test data.1. Supplier is already a H2M supplierIf a supplier is already rolled out as H2M supplier, test data can be taken directly from theproduction system. The supplier should than provide support access to the <strong>SupplyOn</strong> IntegrationManager who will download test data <strong>and</strong> import it into the test l<strong>and</strong>scape.2. Supplier is not yet a H2M supplierIn case the supplier is not yet rolled out as H2M supplier test data has to be provided directly bythe customer.Step 2 - Setup AirSupply messages scheduler<strong>SupplyOn</strong> provides the supplier each of the outbound message types defined in the Deviating PriceAgreement M2M.Step 3 - After a successful outbound message testing the supplier sends a screenshot or logfile to<strong>SupplyOn</strong> Integration Manager. The information has to show that the messages were received <strong>and</strong> canbe processed in the ERP System.Test procedureAfter receiving the test outbound messages the supplier has to inform <strong>SupplyOn</strong> Integration Contact- they have received the messages- the message can be mapped <strong>and</strong> processed- if mapping adjustments are necessaryThe supplier must communicate to <strong>SupplyOn</strong> if mapping adjustments are required <strong>and</strong> the solution datePublic 33/59


Acceptance criteria- The supplier has ensured that the qualified EDI contact person has understood the M2M<strong>Guideline</strong>s <strong>and</strong> format specifications- The processing of all test cases with• m<strong>and</strong>atory <strong>and</strong> optional fields• <strong>and</strong> processing to the backend integration occurs without errors.- All relevant test case messages have been shown to <strong>SupplyOn</strong> as successfully processed(Screenshots of processed message in the ERP or log file)- The project phase has been finished in time8.2.1.3 Phase 3Inbound message testedTarget: Inbound messages must pass <strong>SupplyOn</strong> routing <strong>and</strong> syntax validation testing without errorWork packages: Duration 10 days<strong>SupplyOn</strong> will provide the supplier sample test messages <strong>and</strong> instruction how to develop inboundmessage similar to the <strong>SupplyOn</strong> sample messages.Phase 2 (Outbound messages) <strong>and</strong> Phase 3 (Inbound messages) can be worked in parallelTest procedure- The supplier creates inbound response messages based on the <strong>SupplyOn</strong> Mapping Instructions- <strong>SupplyOn</strong> informs the supplier if the inbound message has syntax or routing errors- Additionally the routing <strong>and</strong> syntax error will be transmitted in a status notification via AS2connection to the supplier- The supplier has to correct the routing or the syntax error in the test messages- The adjustment has to correct within the agreed project time, <strong>and</strong> the supplier has to inform<strong>SupplyOn</strong> about the solution date.Acceptance criteria- The supplier has ensured that the technical EDI contact person has understood the AirSupplyM2M <strong>Guideline</strong>s <strong>and</strong> format specifications.- The processing of the test cases with m<strong>and</strong>atory <strong>and</strong> optional fields have been processed withouterrors.8.2.1.4 Phase 4Solution verification testWork packages: Duration 5 DaysThe acceptance test is used to complete the message flow without any routing <strong>and</strong> syntax errors in themessages between <strong>SupplyOn</strong> <strong>and</strong> the supplier.Test procedure:Outbound messagesAfter receiving the test outbound messages the supplier has to inform <strong>SupplyOn</strong> Integration Contact- they have received the messages- the message can be mapped <strong>and</strong> processed- if mapping adjustments are necessaryThe supplier must communicate to <strong>SupplyOn</strong> if mapping adjustments are required <strong>and</strong> the solution dateInbound messages- The supplier creates inbound response messages based on the <strong>SupplyOn</strong> Mapping InstructionsPublic 34/59


- <strong>SupplyOn</strong> informs the supplier if the inbound message has syntax or routing errors- Additionally the routing <strong>and</strong> syntax error will be transmitted in a status notification via AS2connection to the supplierAcceptance criteriaThe supplier has ensured that the mapping process for the outbound <strong>and</strong> inbound messages works for alltest cases without error.8.2.1.5 Phase 5Setup AS2 technical connection <strong>and</strong> testing on Productive L<strong>and</strong>scapeWork packages: 15 daysAS2 connection will be set up on the production l<strong>and</strong>scape. Transport all settings from test system toproductive system <strong>and</strong> setup message scheduler for productive system.Verify <strong>and</strong> exchange connectivity data for productive l<strong>and</strong>scape.The procedure is similar to the Integration L<strong>and</strong>scape, but the AS2 technical setup specifications aredifferent. (See <strong>SupplyOn</strong> AirSupply AS2 data parameter sheet)Step 1 - The Supplier <strong>and</strong> <strong>SupplyOn</strong> will be exchange the connectivity data for an AS2 connection. Bothparties have to setup the technical AS2 partner, firewall settings <strong>and</strong> certificates. After the technical setupthe connection test can start.Step 2 - The supplier has to provide a screenshot or a logfile to <strong>SupplyOn</strong> after a successful AS2connection.Test procedure- <strong>SupplyOn</strong> sends to the supplier a couple of test connectivity messages to verify the technical AS2connection functions.- The supplier sends to <strong>SupplyOn</strong> a couple of test messages to verify the technical AS2 connectionto <strong>SupplyOn</strong>- The supplier verifies the AS2 Connection to/from <strong>SupplyOn</strong> is working.Acceptance criteriaThe validation is as follows- Two messages will be exchanged without errors from <strong>SupplyOn</strong> to the supplier- Two messages will be exchanged without errors from supplier to <strong>SupplyOn</strong>- The AS2 connection shows an SSL encryption- No firewall issues on message exchange- The certificate is from a approved institution8.2.1.6 Phase 6Migration will be organized <strong>and</strong> coordinated by Airbus.8.2.1.7 Phase 7Post Go-Live support- Check of message transfer- H<strong>and</strong>over to <strong>SupplyOn</strong> Operation TeamPublic 35/59


8.2.2 AcceptanceFor each phase there will be an acceptance procedure. After both parties give notice of finishingpreparation the acceptance procedure will startAcceptance resultGO: the testing/milestone is compliant with the acceptance criteria defined at each phase of the projectNO-GO: the testing/milestone is not compliant with the acceptance criteriaIf acceptance testing is agreed to ‘NO-GO’, the project team shall establish a project action plan tomanage accepted risks.9 M2M transmission configuration9.1 Limitations <strong>and</strong> message sizesEach message type has a limitation of the number of exportable objects, in order to avoid too big files.9.1.1 LimitationsThe limitations are:Message Type Object level LimitDem<strong>and</strong> Forecast Position 5000Purchase Order Schedule Line 5000Inventory ForecastPosition 5000Consumption Report Position 5000Receipt Advice Position 5000Dem<strong>and</strong> Forecast (VMI) Position 5000Self Billing Position 5000VMI IMO Material 500Even if the limit is reached, the files are not cut hard. In order to avoid incomplete data in the export,objects belonging to other objects are exported even if the limit is reached (see example below). If thereare still remaining objects which were not be exported, the Message Monitor (column “Information”) willshow the text “Maximum number of messages reached, there may be still unsent messages”. In thiscase, the scheduler will be executed automatically again as soon as the system receives the supplier’sMDN for the previous exported package.Example: The scheduler for Purchase Order was executed. There are 7.000 Purchase Order ScheduleLine objects in AirSupply which have to be sent to the supplier. The Scheduler grabs the first 5.000objects. If PO Schedule Line with number 4.999 belongs to a Purchase Order which has 14 moreSchedule Lines, these lines are added to the file, even if the number of lines then exceeds the limit. In thiscase the file contains 5.013 PO Schedule Lines. The Message Monitor will show the text that there arestill unsent messages. After the supplier received the file <strong>and</strong> sent back the MDN to AirSupply, thescheduler will export the remaining 1.987 PO Schedule Lines.9.1.2 Message sizesThe message size of one AS2 transmission from AirSupply depends on the format, message type <strong>and</strong> thenumber of messages inside.9.1.2.1 <strong>BoostAero</strong> <strong>XML</strong>The maximum sizes of one AS2 transmission for <strong>BoostAero</strong> <strong>XML</strong> are:Public 36/59


Message Type Normal message size in MB ZIPed message size in MBDem<strong>and</strong> Forecast 160 16Purchase Order 110 13Inventory Forecast32 12Consumption Report 32 12Receipt Advice 32 12Dem<strong>and</strong> Forecast (VMI) 22 5Self Billing 40 2VMI IMO 240 6Status Notification 1 19.1.2.2 <strong>CSV</strong>The maximum sizes of one AS2 transmission for <strong>CSV</strong> are:Message Type Normal message size in MB ZIPed message size in MBDem<strong>and</strong> Forecast 11 2Purchase Order 7 1Inventory Forecast10 6Consumption Report 10 6Receipt Advice 10 6Dem<strong>and</strong> Forecast (VMI) 6 1Self Billing 6 1VMI IMO 30 3Status Notification 1 19.2 Message SchedulerThe user can enter the message scheduler display directly via the MyWorkspace screen.It contains all configuration options for creating a schedule which determines:- When a message will be sent to an EDI supplier (frequency)- Which content a message contains (filtering options)9.2.1 Time ZoneAirSupply provides the possibility to have your user profile in your own time zone. Therefore the timesshown in the message scheduler can vary due to different time zones in different user accounts. It isrecommended that each location (Supplier Site City), if in a different country or time zone, administratesits own scheduler jobs in order to be valid for the correspondent business hours.9.2.2 Automatic StopThe scheduler is designed to have an automatic stop at midnight, if you want the scheduler to cover a 24hour schedule, please set the Start Time to 00.30.Please note: The stop at midnight will be done within the respective user’s time zone.Public 37/59


9.2.3 OverviewThe message scheduler display contains the following overview213 4 5 6 7 8 9 10 11 12 13 14 15 16 1718 19 20 21 22 23Each configured scheduler job is represented by one line within this overview.Functional Description# Name Description1 Breadcrumb My <strong>SupplyOn</strong> > My Workspace > EDI Integration2 SchedulerMessage MonitorTwo Tabs where you can select if you want to see the scheduler orcheck the message monitor3 Column Selection Checkbox to select the respective scheduler job in order to executeone of the following actions:- Execute Now- Duplicate- DeleteDefault: Not selected4 Column Active Checkbox to activate / deactivate the respective scheduler job. Thechange will not be saved permanently until the user clicks on thebutton “Save Changes”After creating a scheduler job with the button “New Schedule” thecheckbox is selected by default.5 Column ID Unique ID which identifies the scheduler job (automatically set by thesystem)6 Column Msg. Type Dropdown menu where the message type of the respectivescheduler job can be selected.Valid data is:- 10 Forecast / Dem<strong>and</strong> Forecast- 20 PO / Order- 40 VMI_GrossDem<strong>and</strong>s / VMI Dem<strong>and</strong> Forecast- 41 VMI_StockInfo_StockLevel / Inventory Forecast- 42 VMI_StockInfo_StockMovements / Consumption Report- 43 StockInfo_GoodsReceipt / Receipt Advice- 44 StockInfo_ALL (only <strong>CSV</strong>)- 46 VMI_Monitor / Inventory Forecast- 50 SBI / Self BillingThe change will not be saved permanently until the user clicks on thebutton Save ChangesAfter creating a scheduler job the default value is 20 PO / OrderPublic 38/59


# Name Description7 Column Customer Group Dropdown menu to select the customer group or the default option“All” which determines a specific customer group or not (in case ofthe selection “All”)The list of possible values depends on the user’s right to view asupplier control point. Only the customer corporate groups aredisplayed for selection, which are linked to the supplier controlpoints.The change will not be saved permanently until the user clicks on thebutton Save Changes.After creating a scheduler job the default value is “All”.8 Column Supplier Site Dropdown menu to select the seller control point which determinesthe supplier’s destination EDI system.The list of possible value depends on the user’s right to see a controlpoint. Displayed are the names of the respective control point.The change will not be saved permanently until the user clicks on thebutton Save Changes.After creating a scheduler job the default value is the name of thefirst control point returned by the query.9 Column Options Click on edit opens the Detailed Scheduler Options screens for therespective scheduler job. If there are no detail options available forthe respective message type the string edit is not displayed.10 Column Last Execution Displays the date <strong>and</strong> time of the last run of the respective schedulerjob.Format depends on the date <strong>and</strong> time format configured for thecurrent userIf there was no run in the past the date <strong>and</strong> time remain empty.11 Column Next Execution Displays the next planned run of the scheduler job as configured.Format depends on the date <strong>and</strong> time format configured for thecurrent userIf neither the Active checkbox nor one of the weekday checkboxes isselected, the date <strong>and</strong> time remain empty.12 Column Start Date Input field to schedule the day of the earliest run of the respectivescheduler job. The format must be CCYY-MM-DDThe change will not be saved permanently until the user clicks on thebutton Save Changes.After creating a scheduler job the current date will be scheduled bydefault. The application directly validates the inserted date. Forinvalid dates an error message is displayed.13 Column Start Time Input field to schedule the time for the respective date of the earliestrun of the scheduler job.The format must be HH:MMThe change will not be saved permanently until the user clicks on thebutton Save Changes.After creating a scheduler job the current time will be scheduled bydefault. The application directly validates the inserted time. Forinvalid dates an error message is displayed.Public 39/59


# Name Description14 Column Frequency Input field to schedule the time period between the runs of therespective scheduler job. Only whole numbers between 1 <strong>and</strong> 99 arepossible. The associated time unit can be configured within columnFrequency Unit.The change will not be saved permanently until the user clicks onSave ChangesAfter creating a scheduler job the default value is “1”.15 Column Frequency Unit Dropdown menu to select the frequency unit corresponding to thefrequency value which is scheduled in column FrequencyPossible values are:- Month(s)• Only a frequency of 1 is allowed• The scheduler will be executed every month on thedefined start date at the specified start timeindependent from the weekdays• All weekdays will be activated automatically- Week(s)- Day(s)• The scheduler will be executed every [x] weeks onthe selected weekdays at the specified start timewith the defined frequency• Only a frequency of 1 is allowed• The scheduler will be executed on the specifiedweekdays at the defined start time- Hour(s)• A frequency between 1 <strong>and</strong> 24 is allowed, butvalues exceeding 12 are not recommended• The scheduler will be executed every [x] hours onthe selected weekdays starting at the specified starttime where [x] is the frequency- Minute(s)• A frequency between 30 <strong>and</strong> 99 is allowed• The scheduler will be executed every [x] minutes onthe specified weekdays starting at the specified starttime where [x] is the frequencyThe change will not be saved permanently until the user clicks on thebutton Save Changes.After creating a scheduler job the default value is “Day(s)”.16 Weekday columns For each weekday a checkbox exists. The respective job only runson days where the checkbox is selected.The change will not be saved permanently until the user clicks on thebutton Save Changes.After creating a scheduler job all checkboxes are selected by default.17 Column Comment Text field where the user can optionally enter a name or descriptionof the scheduler job. The maximum length is 50 digits, the field isempty by default.The change will not be saved permanently until the user clicks on thebutton Save Changes.Public 40/59


# Name Description18 Button Save Changes By clicking the button all currently configured values are permanentlysaved to the database.The application checks if the scheduled frequency of any scheduleris not more than 1 message per 30 minutes. Otherwise an errormessage is displayed which forces the user to change hisconfiguration.19 Button Reset Changes By clicking the button all scheduler values were reloaded from thedatabase <strong>and</strong> replace all changes since last saving.Deleted scheduler jobs will not be re-created.20 Button Execute Now By clicking the button all scheduler jobs which are active, will betriggered immediately to execute one run.The columns Last Execution <strong>and</strong> Next Execution were updated.21 Button New scheduler By clicking the button a new scheduler job is created as a new linebelow the last existing scheduler job.22 Button Duplicate By clicking the button all scheduler jobs which are active areduplicated as new lines below the last existing scheduler job.By default these new scheduler jobs are disabled, i.e. the Check Boxin column Active is not ticked.23 Button Delete By clicking the button all scheduler jobs which are activated will bedeleted from the database. A confirmation window will be displayedwhere the user must confirm to the deletion. After that the screen isrefreshed <strong>and</strong> the deleted scheduler jobs are not visible anymore.Public 41/59


9.2.4 Message Scheduler Details - 10 Forecast / Dem<strong>and</strong> ForecastThe corresponding message type is Dem<strong>and</strong> Forecast.124356Functional Description# Name Description1 Breadcrumb The Breadcrumb is:My <strong>SupplyOn</strong> > My Workspace > EDI Integration > Forecast FilterOptions ([Scheduler ID]-[Msg. Type]-[Seller Controlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexport3 Dropdown menu “DataMeasure”:If the checkbox is selected the resulting message only contains theForecast data not marked as “Exported (since last update)".This flag is true if there is no change on the data since the last run ofthe scheduler. The supplier then only receives the new or modifiedForecast data.The change will not be saved permanently until the user clicks on thebutton Save Changes.The checkbox is selected by default.The user can select one of the options below. The resulting messagethen will only contain the forecast data of the respective type.Possible values are:- ALL (default)- PUBDMD - published dem<strong>and</strong>- PRVDMD - previous published dem<strong>and</strong> (last (week) forecastimport)- SUPCOM - Supplier commitment- CUSTUN - Customer tuning{The change will not be saved permanently until the user clicks onthe button Save Changes.4 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.5 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.6 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.Public 42/59


9.2.5 Message Scheduler Details Display - 20 PO / OrderThe corresponding message type is Order.1253467Functional Description# Name Description1 Breadcrumb My <strong>SupplyOn</strong> > My Workspace > EDI Integration > PO FilterOptions ([Scheduler ID]-[Msg. Type]-[Seller Controlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexportIf the checkbox is selected the resulting message only contains thePO data where the flag “Exported (since last update)" is set to false.This flag is true if there is no change on the data since the last run ofthe scheduler.The triggers for setting the flag of the PO Schedule Line to false are:- all message imports (not relevant if changes occurred)- all status changes (not relevant if changes occurred)- UI changes of collaboration values (requested price, quantity <strong>and</strong>date) by customer user- Changes of Ordering Officer Master Data- Order Line-splittingThe supplier then only receives the new or modified PO data.The change will not be saved permanently until the user clicks on thebutton Save ChangesThe checkbox is selected by default.3 Dropdown Order Type The user can select one of the options below. The resulting messagewill only contain data from purchase orders of the respective type.Possible values are:- ALL (default)- OTHER- CALLUP / Supply InstructionThe change will not be saved permanently until the user clicks on thebutton Save Changes.Public 43/59


# Name Description4 Dropdown Order Status Multiple selection drop down menu where the user can select one ormore of the options below. The resulting message then will onlycontain data from purchase orders that have one of the selectedstatus values at the moment the scheduler job is running.Possible values are:- ALL (default)- NEW ORDER PUBLISHED- SUPP ACCEPTED WITH CHANGES- OPEN- SUPP CHANGE ORDER REQ- CANCELLATION REQ- CUST CHANGE ORDER REQ- PARTIALLY SHIPPED- SHIPPED- RECEIVED- CANCELLED- PARTIALLY RECEIVED- REJECTEDThe change will not be saved permanently until the user clicks on thebutton Save Changes.5 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.6 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.7 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.9.2.5.1 Supported Status Values“Status”“PO sub-status”“Logistical sub-status”Contains the total (summary) status which is in all facets identical to thecurrently operated status value (for all meaning <strong>and</strong> impact of collaborationstatus value.This value provides therefore 100% compatibility (from user perspective) tocurrent eSC system.However, internally the system will always maintain all 4 status values <strong>and</strong> it willdetect required activity <strong>and</strong> validation by the more detailed separated statusvalues (see below).Possible values are:NEW ORDER PUBLISHED, OPEN, CANCELLED, PARTIALLY SHIPPED,SHIPPED, PARTIALLY RECEIVED, RECEIVED, CUSTOMER CHANGEORDER REQUEST, SUPPLIER ACCEPTED WITH CHANGES, SUPPLIERCHANGE ORDER REQUEST, CANCELLATION REQUEST, REJECTEDContains the total PO status which is the major status of the PO schedule line.Possible values are:NEW ORDER PUBLISHED, OPEN, CANCELLED, REJECTEDContains the logistical status regarding shipping or receiving.Possible values are:Public 44/59


Empty, PARTIALLY SHIPPED, SHIPPED, PARTIALLY RECEIVED, RECEIVED“Action sub-status”Contains of the current collaboration activity which is either supplier or customerchanges or cancellation request (of customer).Possible values are:Empty, SUPPLIER ACCEPTED WITH CHANGES, CUSTOMER CHANGEORDER REQUEST, SUPPLIER CHANGE ORDER REQUEST,CANCELLATION REQUESTSUPPLIER ACCEPTEDWITH CHANGES(SAWC)OPENCANCELLATIONREQUEST (CANREQ)CANCELLEDPARTIALLY SHIPPEDSHIPPEDPARTIALLY RECEIVEDRECEIVEDCUSTOMER CHANGEORDER REQUEST(CCOR)SUPPLIER CHANGEORDER REQUEST(SCOR)Summarized, the meaning <strong>and</strong> impact of the status field values is as follows:Type Status Meaning/Remark(Summary)Status:NEW ORDERPUBLISHED (NOP)The order is published to the AirSupply system <strong>and</strong> iswaiting for reaction of supplier (“accept/modify, autoaccept,etc”)The supplier has reviewed a new order in status NOP<strong>and</strong> proposes a different promised date <strong>and</strong>/orquantity.The supplier has accepted the NOP order (or the autoaccepthas set NOP to OPEN after the 48-hourtimeout).The customer requests to cancel the PO scheduleline.The supplier accepted the cancellation request or thecustomer did cancel the schedule line which thesupplier has changed to status SAWC.CANCELLED can also come from a customercancellation of a NOP PO.This is a final status <strong>and</strong> accordingly blocks anycollaboration.While no collaboration is pending/ongoing, the POschedule line has received at least one part shipped(reported by ASN process) while not all parts arereported to be shipped.In case collaboration starts, the status will change toan according collaboration status.The partially shipped is only to be set as long as POschedule line has no received quantities (in whichcase it is set to PARTICALLY RECEIVED).While no collaboration is pending/ongoing, the POschedule line is reported all parts to be shipped(reported by ASN process).The partially shipped is only to be set as long as POschedule line has no received quantities (in whichcase it is set to PARTICALLY RECEIVED).While no collaboration is pending/ongoing the POschedule line is reported to have already receivedsome (at least one, not all) of the ordered goods(reported by GR process).While no collaboration is pending/ongoing the POschedule line is reported to have already received allof the ordered goods (reported by GR process).This is a final status <strong>and</strong> accordingly blocks anycollaboration.Customer has modified requested date <strong>and</strong>/or quantityon the PO schedule line.Supplier has modified promised date <strong>and</strong>/or quantityon the PO schedule line.Public 45/59


Type Status Meaning/RemarkREJECTEDWhen supplier has rejected a PO from status NOP(only in SIMPLE collaboration model).Status is in its restrictions <strong>and</strong> options h<strong>and</strong>led equalto status CANCELLED.PO sub-status: NEW ORDERPUBLISHED (NOP)The order is published to the AirSupply system <strong>and</strong> iswaiting for reaction of supplier (“accept/modify, autoaccept,etc”)OPENThe supplier has accepted the NOP order (or the autoaccepthas set NOP to OPEN after the 48-hourtimeout).CANCELLEDThe supplier accepted the cancellation request or thecustomer did cancel the schedule line which thesupplier has changed to status SAWC.CANCELLED can also come from a customercancellation of a NOP PO.This is a final status <strong>and</strong> accordingly blocks anycollaboration.RECEIVEDAutomatically set by Goods Receipt processing basedon comparison of requested <strong>and</strong> received quantity.This status is therefore comparable to the current finalstatus “RECEIVED” (on the “Status” member).REJECTEDWhen supplier has rejected a PO from status NOP(only in SIMPLE collaboration model).Status is in its restrictions <strong>and</strong> options h<strong>and</strong>led equalLogistical substatus:Action substatus:PARTIALLY SHIPPED(PARTSHIP)SHIPPEDPARTIALLY RECEIVED(PARTREC)RECEIVEDCUSTOMER CHANGEORDER REQUEST(CCOR)CANCELLATIONREQUEST (CANREQ)SUPPLIER CHANGEORDER REQUEST(SCOR)to status CANCELLED.Automatically set by DA processing based oncomparison of requested <strong>and</strong> shipped quantity.This status value is in severity order <strong>and</strong> mayoverwrite by “higher” logistical status SHIPPED,PARTIALLY RECEIVED or RECEIVED.Automatically set by DA processing based oncomparison of requested <strong>and</strong> shipped quantity.This status value is in severity order <strong>and</strong> mayoverwrite by “higher” logistical status PARTIALLYRECEIVED or RECEIVED.Automatically set by GR processing based oncomparison of requested <strong>and</strong> received quantity.This status value is in severity order <strong>and</strong> may beoverwritten by “higher” logistical status RECEIVED.Automatically set by GR processing based oncomparison of requested <strong>and</strong> received quantity.This status value identifies the logistical completion ofprocessing on PO.The action status is only contained <strong>and</strong> displayed aslong as the collaboration is in-process (<strong>and</strong> mayoverwrite by following-up status value depending onthe user action (<strong>and</strong> allowed user actions in common).The action status is only contained <strong>and</strong> displayed aslong as the collaboration is in-process (<strong>and</strong> mayoverwrite by following-up status value depending onthe user action (<strong>and</strong> allowed user actions in common).The action status is only contained <strong>and</strong> displayed aslong as the collaboration is in-process (<strong>and</strong> mayoverwrite by following-up status value depending onthe user action (<strong>and</strong> allowed user actions in common).Public 46/59


9.2.5.2 Collaboration9.2.5.2.1 Status change for full collaboration modelKey:VC = Value ChangeVR = Value ResetSM = Send MessageApply the made changes to the data content.Reject the made changes on the data content <strong>and</strong> keep former values.Send message to customer backend (ERP) system.NEW ORDER PUBLISHEDUser Group Action New Status ImpactCustomer modify NOP VC, SMCustomer cancel CANCELLED SMSupplier modify SAWCSupplier accept OPEN SMSUPPLIER ACCEPTED WITH CHANGESUser Group Action New Status ImpactCustomer modify CCORCustomer accept OPEN VC, SMCustomer accept + penalize 1 OPEN VC, SMCustomer reject NOP VR, SMCustomer cancel CANCELLED SMSupplier modify SAWC1 On SAWC the accept + penalize is only available if order type is CALLUP or SPARESPublic 47/59


OPENUser Group Action New Status ImpactCustomer modify CCORCustomer cancel CANREQSupplier modify SCORCUSTOMER CHANGE ORDER REQUESTUser Group Action New Status ImpactCustomer modify CCORCustomer cancel CANREQ VC, SMSupplier modify 2 CCOR VC, SMSupplier accept OPEN VC, SMSupplier reject 3 OPEN/NOP [3] VR, SMSUPPLIER CHANGE ORDER REQUESTUser Group Action New Status ImpactCustomer modify CCORCustomer accept OPEN VC, SMCustomer accept + penalize OPEN VC, SMCustomer reject OPEN VR, SMCustomer cancel CANREQSupplier modify SCORCANCELLATION REQUESTUser Group Action New Status ImpactCustomer modify 4 CCORSupplier accept CANCELLED SMSupplier reject OPEN VR, SMCANCELLEDNo action possiblePARTIALLY SHIPPEDUser Group Action New Status ImpactCustomer modify CCORSupplier modify SCORSHIPPEDNo action possible2 On CCOR suppliers’ modify is only available when “Allow-transition-CCOR-to-SCOR” is enabled. This is part of the flexibilitydesign.3 On CCOR the supplier reject leads to OPEN in case initial status was OPEN, to NOP in case CCOR was reached after an SAWC.4 only if “Collab Actor” = “Import”Public 48/59


PARTIALLY RECEIVEDUser Group Action New Status ImpactCustomer modify CCORSupplier modify SCORRECEIVEDNo action possible9.2.5.2.2 Status change for simple collaboration modelNEW ORDER PUBLISHEDUser Group Action New Status ImpactSupplier accept OPEN SMSupplier reject REJECTED SMOPENNo action possibleCANCELLATION REQUESTUser Group Action New Status ImpactSupplier accept CANCELLED SMSupplier reject OPEN SMCANCELLEDNo action possiblePARTIALLY SHIPPEDNo action possibleSHIPPEDNo action possiblePARTIALLY RECEIVEDNo action possibleRECEIVEDNo action possible9.2.5.2.3 Status change for nocollab collaboration modelNo action possiblePublic 49/59


9.2.6 Message Scheduler Details - 40 VMI_GrossDem<strong>and</strong>s / VMI Dem<strong>and</strong> ForecastThe corresponding message type is VMI Dem<strong>and</strong> Forecast.1234 5Functional Description# Description1 The Breadcrumb is: My <strong>SupplyOn</strong> > My Workspace > EDI Integration >VMI_GrossDem<strong>and</strong>s Filter Options ([Scheduler ID]-[Msg. Type]-[Seller Controlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexportIf the checkbox is selected the resulting message only contains thedem<strong>and</strong> data not marked as “Exported (since last update)".This flag is true if there is no change on the data since the last run ofthe scheduler. The supplier then only receives the new or modifieddem<strong>and</strong>.The change will not be saved permanently until the user clicks on thebutton Save Changes.The checkbox is selected by default.3 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.4 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.5 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.Public 50/59


9.2.7 Message Scheduler Details Display – Stock InformationStock Information is devided into four different scheduler jobs:- 41 VMI_StockInfo_StockLevel / Inventory Forecast- 42 VMI_StockInfo_StockMovements / Consumption Report,- 43 StockInfo_GoodsReceipt / Receipt Advice- 44 StockInfo_ALL (Only <strong>CSV</strong>)These are analogue to the following message types:- Inventory Forecast- Consumption Report- Receipt Advice9.2.7.1 41 VMI_StockInfo_StockLevel / Inventory Forecast <strong>and</strong> 42VMI_StockInfo_StockMovements / Consumption Report1234 541 VMI_StockInfo_StockLevel / Inventory Forecast1234 542 VMI_StockInfo_StockMovements / Consumption ReportFunctional Description# Description1 The Breadcrumb is: My <strong>SupplyOn</strong> > My Workspace > EDI Integration > VMI StockInformation Filter Options ([Scheduler ID]-[Msg. Type]-[SellerControlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexportIf the checkbox is selected the resulting message only contains thestock information not marked as “Exported (since last update)".This flag is true if there is no change on the data since the last run ofthe scheduler. The supplier then only receives the new or modifiedstock information.The change will not be saved permanently until the user clicks on thebutton Save ChangesThe checkbox is selected by default.Public 51/59


# Description3 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.4 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.5 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.9.2.7.2 43 StockInfo_GoodsReceipt / Receipt Advice12345643 StockInfo_GoodsReceipt / Receipt AdviceFunctional Description# Description1 The Breadcrumb is: My <strong>SupplyOn</strong> > My Workspace > EDI Integration > StockInformation Filter Options ([Scheduler ID]-[Msg. Type]-[SellerControlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexport3 Dropdown menu “ProcessKey”If the checkbox is selected the resulting message only contains thestock information not marked as “Exported (since last update)".This flag is true if there is no change on the data since the last run ofthe scheduler. The supplier then only receives the new or modifiedstock information.The change will not be saved permanently until the user clicks on thebutton Save ChangesThe checkbox is selected by default.The user can select one of the options below. The resulting messagethen will only contain goods receipt / receipt advice data of therespective process key.Possible values are: ALL (default)STA GRVMI GR4 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.Public 52/59


# Description5 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.6 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.9.2.7.3 44 StockInfo_ALL (Only <strong>CSV</strong>)1234 5Functional Description# Description1 The Breadcrumb is: My <strong>SupplyOn</strong> > My Workspace > EDI Integration > StockInformation Filter Options ([Scheduler ID]-[Msg. Type]-[SellerControlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexportIf the checkbox is selected the resulting message only contains thestock information not marked as “Exported (since last update)".This flag is true if there is no change on the data since the last run ofthe scheduler. The supplier then only receives the new or modifiedstock information.The change will not be saved permanently until the user clicks on thebutton Save ChangesThe checkbox is selected by default.3 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.4 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.5 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.Public 53/59


9.2.8 Message Scheduler Details – 46 VMI Monitor / Inventory ForecastThe corresponding message is Inventory Monitor.1234 5Functional Description# Description1 The Breadcrumb is: My <strong>SupplyOn</strong> > My Workspace > EDI Integration > VMI MonitorFilter Options ([Scheduler ID]-[Msg. Type]-[Seller Controlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexportIf the checkbox is selected the resulting message only contains thestock information not marked as “Exported (since last update)".This flag is true if there is no change on the data since the last run ofthe scheduler. The supplier then only receives the new or modifiedstock information.The change will not be saved permanently until the user clicks on thebutton Save ChangesThe checkbox is selected by default.3 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.4 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.5 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.Public 54/59


9.2.9 Message Scheduler Details - 50 SBI / Self BillingThe corresponding message type is Self Billing.1234 5Message Scheduler Details Display (SBI / Self Billing)Functional Description# Name Description1 The Breadcrumb is: My <strong>SupplyOn</strong> > My Workspace > EDI Integration > SBI FilterOptions ([Scheduler ID]-[Msg. Type]-[Seller Controlpoint])2 Checkbox Only changed<strong>and</strong> new data since lastexportIf the checkbox is selected the resulting message only contains theSBI data not marked as “Exported (since last update)".This flag is true if there is no change on the data since the last run ofthe scheduler. The supplier then only receives the new or modifiedSBI.The change will not be saved permanently until the user clicks on thebutton Save ChangesThe checkbox is selected by default.3 Information Text This informs about the configuration of the limitation (see 9.1.1). Theinformation text is shown independently from the configuration “Onlynew data”.4 Button Back By clicking the button the Scheduler Details Display is closed withoutany savings <strong>and</strong> the Message Scheduler Display is opened.A warning window will be displayed if the user did changes whichwould be lost. The user must confirm the exit.5 Button Save By clicking the button all currently configured values shown on thisscreen are permanently saved to the database.Public 55/59


9.3 Message MonitorThe user can enter the Message Monitor Display via the “Message Monitor” tab on the MessageScheduler View.The message monitor shows a report over all messages (inbound <strong>and</strong> outbound) for one supplier withinthe last 45 days.The following screen shows the Message Monitor123 4 5 6 7 8 9 10 11 12Each reported message which was triggered by a scheduler job <strong>and</strong> each message which a supplier hassent to <strong>SupplyOn</strong> is represented by one line within this overview.The st<strong>and</strong>ard search <strong>and</strong> filter options of the <strong>SupplyOn</strong> application are available for this screen.Functional DescriptionAll fields on this screen are for read-only.# Name Description1 Breadcrumb My <strong>SupplyOn</strong> > My Workspace > EDI Integration2 SchedulerMessage MonitorTwo Tabs where you can select if you want to see the scheduler orcheck the message monitor3 Column Date For outbound messages: Sending dateFor inbound messages: Date when the messages were reportedwithin the AirSupply application.4 Column Time For outbound messages: Sending timeFor inbound messages: Time when the messages were reportedwithin the AirSupply application.5 Column Direction Shows the direction of the respective message from the <strong>SupplyOn</strong>point of view.Possible values are:- IN- OUTPublic 56/59


# Name Description6 Column Msg.Type Shows the type of the respective message. Possible values are:- Forecast / Dem<strong>and</strong> Forecast- Forecast Response/ Dem<strong>and</strong> Forecast Response- PO / Order- PO Response/ Order Response- DA / Despatch Advice- VMI_GrossDem<strong>and</strong>s / VMI Dem<strong>and</strong> Forecast- VMI_StockInfo_StockLevel / Inventory Forecast- VMI_StockInfo_StockMovements / Consumption Report- VMI_StockInfo_GoodsReceipt / Receipt Advice- VMI_StockInfo_ALL- VMI_PlannedReceipts / Supply Notification- VMI_Monitor / Inventory Forecast- SBI / Self Billing7 Column Schedule ID The ID of the respective scheduler job which initiated the message.For inbound messages the field is filled with a dash “-“.8 Column Msg.ID Unique Message ID which is automatically set by the system foroutbound messages.For <strong>CSV</strong> there is an additional column dedicated to the message ID,but only for the first line.For <strong>BoostAero</strong> <strong>XML</strong> there is a dedicated field.Related to the inbound messages the value is taken from themessage content (message ID set by the supplier’s EDI system).9 Column Customer Group Displayed is not the ‘organization ID’ of the corporate group but the‘organization name’, or ‘All’ in case this option was selected by theuser for the related scheduled job.10 Column Supplier Site The seller controlpoint representing the supplier’s EDI system whichwas the sender/receiver of this message.11 Column Status The message transmission status.The following values are possible:- SUCCESS(the message was successfully transmitted)- ERROR(any transmission error occurred)- PENDING(a message was triggered out by a scheduler job <strong>and</strong> nowthe system is waiting for a success or error notification)Note: The transmission status is set depending on the positive ornegative synchronous response of the supplier on HTTP(S) level.There is no validation of an asynchronous response.If a message went on error, it must be manually resent by using the“Execute Now” button within the scheduler display.The data is considered as "downloaded" as soon as the message issuccessfully sent to the suppliers EDI system.Public 57/59


# Name Description12 Column Information The following information are shown within this field:- Error: If the scheduler export runs on error, the errormessage is shown here- Limit reached: If the limit for one scheduler execution isreached, the text “Maximum number of messages reachedwithin this transmission, processing loop with ID=Sxxxxxx” isshown. The scheduler will be executed automatically againas soon as the system receives the supplier’s MDN for theprevious exported package.- No data to transmit: If there are no data to transmit for theconfigured schedule, the text “Transmission contains nodata” is shownPublic 58/59


10 Additional Important Information10.1 Downtimes<strong>SupplyOn</strong> has scheduled downtimes on the weekend (for details on the specification of services, pleasesee www.supplyon.com). During downtimes <strong>SupplyOn</strong> is not able to receive messages. The supplier hasto take care that messages that have not been sent during that downtime will be restarted.10.1.1 Scheduled DowntimesThe supplier will be informed of a downtime 6 months in advance via e-mail <strong>and</strong> additionally on ourwebsite.10.1.2 Unscheduled DowntimesThe supplier will be informed immediately via e-mail.10.1.3 Transmissions within downtimesSchedules that have not been executed will not be caught up within the next schedule. If messagescannot be transmitted successfully the supplier has to manually restart the messages using the MessageMonitor.10.1.4 Downtimes <strong>and</strong> Cleo ClientIf you are using the Cleo Client for your AS2 connectivity please notice that there is no option forscheduling downtimes.10.1.5 Error notificationsErrors can only be seen within the AirSupply application, there is no e-mail notification to the supplier. Soif there was or is a downtime, the supplier needs to check autonomous if messages failed or not.10.2 File size limitations10.2.1 Upload file typesWithin AirSupply you can transmit files up to a size of 4MB. Files that exceed this limit will be blocked.This is mainly relevant for <strong>CSV</strong> files as these give the possibility to have several PO confirmations orforecast confirmations within one file. For Boost-<strong>XML</strong> you will send 1 Order Response or 1 Dem<strong>and</strong>Forecast Response within 1 file, so the risk of exceeding 4MB is minor.10.2.2 Download file typesFor the moment there is no limitation configured for the download of files but according to the limitation ofthe upload file size, we reserve the right to split files. So instead of receiving 1 x 20MB file, it couldhappen that you might receive 4 x 5MB files.10.3 Partner acts as seller <strong>and</strong> buyerIf a partner in AirSupply acts as a seller <strong>and</strong> buyer the same format should be used (e.g. BA <strong>XML</strong> asbuyer <strong>and</strong> seller). If not, two AS2 partners should be configured on both sides (one for buyside <strong>and</strong> onefor sellside).If different formats are used (e.g. IDoc <strong>XML</strong> on buyside <strong>and</strong> BA <strong>XML</strong> on sellside) <strong>and</strong> just one AS2partner is configured, the Status Notification message can be sent in one defined format (e.g. IDoc <strong>XML</strong>for buy- <strong>and</strong> sellside messages).Public 59/59

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!