ASPECT4 Logistics A Presentation of Release 9.1

More documents

Recommendations

Info

$(Microsoft PowerPoint - Sammenligning endelig - alle pr\346s januar ...$

32 Cockpit for Capacity Overview In order to provide a better view of the capacity situation, EG has developed a cockpit for this function. A typical cockpit may look like this:
Check against Accumulated Capacity The application 'Check Production' (8330) has been added the function of checking against accumulated free capacity. The purpose of adding the function is to allow for any later overbooking; so far, there has been an implicit presumption of a decreasing capacity utilization about the check. The check is activated when the availability code is 9 on the capacity resource and sum files have been generated for the capacity resource. If there is no valid sum file, the previous functionality prevails. The function of checking against accumulated capacity is meant not only for checking whether the required production can be carried out at the required time, but also for checking that it will not result in an overbooking later on. In other words, the function allows for the fact that we have not yet levelled out production. Thus, compared with the previous check against the sum file, the check has been extended to check against minimum free capacity at all times. The functionality is based on the existing functionality of sum files. Therefore, sum files must be generated and updated for the resource with application 'Rebuild Summary Capacity Profiles' (8291) and 'Start Update of Capacity Profile' (8292), respectively. The sum files are updated by trigger and at any time they describe the accumulated capacity and the accumulated requirements up to any time of changed requirements. However, you can define a period of indifference (system parameter SUMKAP). If it is 0, all events will be reflected, but it gives an improved performance to set it at minimum 1 day. This means, that overbooking may occur within a particular day, but the error is not accumulated. Since a subsequent fine planning is expected anyway, this will typically be acceptable. Changed Control of Breakdown of Sales Plan The way in which application 'Break Down Sales Plan' (8211) has so far functioned, allowance has been made for minimum/maximum order size and unit order size when creating purchase order forecasts and production order forecasts. This can now be optimized. The application had the company parameter 'Net requirement calculation – gross' (NEDBRYD) that defined a number of breakdown preconditions. In order to enable the use of copy applications, the optimizing information has now been turned into application parameters for 'Break Down Sales Plan' (8211). Solution 'Break Down Sales Plan' (8211) has been modified to the effect that optimizing parameters for breakdown must be specified as application parameters. Besides, the following fields have been added to the parameters: Check Purch Quantities: A specification of whether allowance must be made for minimum/unit/maximum order size when calculating order size: 0: Do not consider order sizes. 1: Consider order sizes. Quantity Check Purchase: A specification of which order size to correct against: 0: Correct against minimum order size. 1: Correct against minimum and unit order size. 2: Correct against minimum, unit, and maximum order size. Check Prod Quantities: A specification of whether allowance must be made for minimum/unit/maximum order size when calculating order size: 0: Do not consider order sizes. 1: Consider order sizes. Quantity Check Production: A specification of which order size to correct against: 0: Correct against minimum order size. 1: Correct against minimum and unit order size. 2: Correct against minimum, unit, and maximum order size. Implementation When implementing release 9.1, the application parameters must be set up under file name NEDBRYD. If allowance to order size must be made as previously, the new optimizing parameters must be set up as shown below: 33
Page 1 and 2: ASPECT4 Logistics A Presentation of
Page 3 and 4: About ASPECT4 Logistics Release 9.1
Page 5 and 6: Triggers Dynamic rearrangement is b
Page 7 and 8: Order Entry via EDI or BusinessConn
Page 9 and 10: Item File Item master records inclu
Page 11 and 12: Sales Price Corr in Currency: The c
Page 13 and 14: Unit Price: Price per sales unit (p
Page 15 and 16: Rules and Restrictions This chapter
Page 17 and 18: Transport Management The purpose of
Page 19 and 20: Planning a Transportation The plann
Page 21 and 22: despatch unit reported back (exampl
Page 23 and 24: When you choose to manually create
Page 25 and 26: • Postadjustment of order prices
Page 27 and 28: • Each order line is checked to s
Page 29 and 30: Minor Enhancements - Outgoing Logis
Page 31: Cockpit for Receiving Invoices INWA
Page 35 and 36: Max Size of Data Queues The use of
Page 37 and 38: New Standard Cost Methods It is now
Page 39 and 40: even coded in different ways. And t
Page 41 and 42: STFE Processing under eXposer The S
Page 43 and 44: Implementing Release 9.1 This imple
Page 45 and 46: In application 'Maintain applicatio
Page 48: We create value for you, your busin

ASPECT4 Logistics A Presentation of Release 9.1

Create successful ePaper yourself

Delete template?

Save as template?