1. Order Promising in Microsoft Dynamics ® AX 2012 Order Promising

2.  Provides seamless integration with order entry process  User interaction & guidance when customer-requested dates cannot be met  Simulated what-if scenarios integrated in order entry process  Bridges the conceptual gap between (selling company) ship and (buying company) receipt dates  Order promising gives receipt date at receiving point, ship date at shipping point  Order promising takes transit constraints into account  Aligns with product supply strategy for realistic date promising  Fixed sales lead time  Variable lead time dependent upon Available to Promise check on projected inventory and production/supply schedule  Variable lead time dependent upon Capable to Promise check on projected material, parts availability, and production capacity Order promising in Microsoft Dynamics AX 2012 supports company product supply and customer strategy:

3. Order Promising Scenarios

4. ATP is the uncommitted portion of a company’s inventory and planned production maintained in the master schedule to support customer order promissing. The ATP quantity is the uncommitted inventory balance in the first period and is normally calculated for each period in which a receipt is scheduled -APICS Dictionary Answers the question: When can I ship the product to the customer based on planned material availability?

5. Order Promising Scenarios Performs multi-level BoM calculatation Considers projected, available production capacity Considers projected, available material and parts Considers lead times and issue&receipt margins Answers the question: When is the earliest that I can ship the product to the customer, given cross-site capacity and material constraints?

6. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Microsoft Dynamics, and the Microsoft Dynamics logo are trademarks of the Microsoft group of companies. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. CCAX2012BV057