BoostAero XML and CSV Implementation Guideline ... - SupplyOn

# Message Types(BoostAero XML /CSV)1 Demand Forecast /Demand ForecastOverview2 Demand ForecastResponse /Demand ForecastConfirmation3 Order /OrderOverviewDirectionToSupplierFromSupplierToSupplierDescriptionThe forecast process receives the forecast data from the ERPsystem and allows customers and 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 and a set of detail lines whilethe header describes the forecast in common such ascustomer material number, supplier ID, customer ID and thedetail lines contain the demand quantities related to a demanddate. 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 and provisionalhorizon. The firm horizon contains of all demands which areno longer subject of forecasting anymore (and are subject tobe already handled by PO). The flexible horizon contains of alldemands in the short term range which require a commitmentof supplier. The provisional horizon contains of all demands 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 thedemanded 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 demandedquantity and 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 and supplier.The purchase order process receives the PO data from thecustomer ERP system and allows customers and suppliers tocollaborate on the PO schedule line level. By performingchanges on the PO schedule line data, the customer andsupplier can request changes regarding date, quantity andprice, 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 and are read-only onAirSupply side. Furthermore the AirSupply PO processreceives changes in logistical values for shipped and 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