BoostAero XML and CSV Implementation Guideline ... - SupplyOn

More documents

Recommendations

Info

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 and 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 LimitDemand Forecast Position 5000Purchase Order Schedule Line 5000Inventory ForecastPosition 5000Consumption Report Position 5000Receipt Advice Position 5000Demand 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 and 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 and thenumber of messages inside.9.1.2.1 BoostAero XMLThe maximum sizes of one AS2 transmission for BoostAero XML are:Public 36/59
Message Type Normal message size in MB ZIPed message size in MBDemand Forecast 160 16Purchase Order 110 13Inventory Forecast32 12Consumption Report 32 12Receipt Advice 32 12Demand Forecast (VMI) 22 5Self Billing 40 2VMI IMO 240 6Status Notification 1 19.1.2.2 CSVThe maximum sizes of one AS2 transmission for CSV are:Message Type Normal message size in MB ZIPed message size in MBDemand Forecast 11 2Purchase Order 7 1Inventory Forecast10 6Consumption Report 10 6Receipt Advice 10 6Demand 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
Page 1 and 2: IMPLEMENTATION GUIDE for suppliers
Page 3 and 4: 3.7 January 2014 5.5 Added informat
Page 5: Table of content1 Purpose of the do
Page 9 and 10: # Message Types(BoostAero XML /CSV)
Page 11 and 12: # Message Types(BoostAero XML /CSV)
Page 13 and 14: 4.1.2 Message Disposition Notificat
Page 15 and 16: SecurityTransport LayerAS2 Settings
Page 17 and 18: 4.1.5.3 Trusted Issuers (Certificat
Page 19 and 20: 4.1.5.4 AS2 via the CLEO LexiCom AS
Page 21 and 22: The Euro 350,-- implementation and
Page 24 and 25: Technical information and assistanc
Page 26 and 27: 6.4 CSV message format guidelinesTh
Page 28 and 29: 7.2 Error codes for specific messag
Page 30 and 31: MessageErrorCodeC437C438C439C008C44
Page 32 and 33: As soon as the technical AS2 connec
Page 34 and 35: Acceptance criteria- The supplier h
Page 38 and 39: 9.2.3 OverviewThe message scheduler
Page 40 and 41: # Name Description14 Column Frequen
Page 42 and 43: 9.2.4 Message Scheduler Details - 1
Page 44 and 45: # Name Description4 Dropdown Order
Page 46 and 47: Type Status Meaning/RemarkREJECTEDW
Page 48 and 49: OPENUser Group Action New Status Im
Page 52 and 53: # Description3 Information Text Thi
Page 56 and 57: 9.3 Message MonitorThe user can ent
Page 58 and 59: # Name Description12 Column Informa

BoostAero XML and CSV Implementation Guideline ... - SupplyOn

Create successful ePaper yourself

Delete template?

Save as template?