1. Taking and processing sales orders in Microsoft Dynamics® AX 2012
5/19/2018 8:16 PM
Sales order process
Taking and processing sales orders in Microsoft Dynamics® AX 2012
Say Title
MICROSOFT CONFIDENTIAL
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
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.

2. Value proposition
The sales order process in Microsoft Dynamics AX 2012 offers features that support the following areas:
Global sales
Provides efficient multi-currency, multi-language, multi-site support for organizations that sell products both locally and globally.
Efficient sales order entry and processing
Automatically applies organizational policies to ensure process compliance.
Automatically applies terms and conditions set by prior agreement with the customer.
Flexibly integrates customer processes from collaborative trading networks to solely Microsoft Dynamics AX 2012 client-based interactions.
Seamlessly integrates with other Microsoft Dynamics AX 2012 modules to provide access to real-time inventory, financial, manufacturing, and planning updates.
Read title
The objective of this slide is to cover some of the key messages related to sales order process. The key messages tie into the datasheet on sales order process, and the datasheet should be consulted in order to understand, backup, and communicate the key messages listed here.
Global sales
Dynamics Ax2012 provides efficient multi-currency, multi-language, multi-site support for organizations that sell products both locally and globally. In addition hereto For organizations with geographically distributed sales and distribution locations, Dynamics Ax supports taking into account different time zones between the customer, sales office and distribution location, when as an example giving order promisses.
Efficient sales order entry and processing
Dynamics Ax2012 Automatically applies organizational policies to ensure compliance. As an example Dynamics Ax2012 may seamlessly apply customer credit limit policies upon order entry and order processing.
Dynamics Ax2012 Automatically applies terms and conditions agreed to by the customer. As an example Dynamics Ax2012 may seamlesslyapplies negociated trade agreements upon order entry.
Dynamics Ax2012 Flexibly integrates customer processes from collaborative trading networks to solely Microsoft Dynamics AX 2012 client-based interactions. As an example Dynamics Ax2012 sales process supports electronic document interchange not only for the sales documents (such as order confirmation), but for outbound shipping documents as well as invoices.
Dynamics Ax2012 Seamlessly integrates with other Microsoft Dynamics AX 2012 modules to provide access to real-time inventory, financial, manufacturing, and planning updates. Such that the user interacting with Dynamics Ax is at all times looking at real time data and status on these data (!!). He does not have to await cross module batch jobs to be executed to look at cross module updated data.

3. Elements in the sales order process
Issue change order confirmation
Reschedule sales deliveries
Enter sales order
Apply terms and conditions
Enter products and customer requirements
Determine pricing and discounting
Perform credit checks
Perform order promising and schedule sales deliveries
Issue order confirmation
Release for picking
Follow progress of order fulfillment
Read title
The objective of this slide is to provide high level insight into the sales process capabilities of Microsoft Dynamics 2012.
The sales order process wheel depicts a number of selected process elements within the sales order process. The sales order process elements highlighted here and supported by Dynamics Ax are (Read from slide: start with Enter sales order).
Apart from the Enter SO element, all of the elements within the sales process wheel may be sequenced and repeated in a unlimited number of different variations, depending upon the specific business and order scenario. Each circle represents a selective key element of the sales order process, which may represent a specific step, a task, or may be seamlessly integrated in other steps or tasks.
The process wheel only depicts selective key elements of the sales order process, and not the fulfilment or billing processes. Of cause this extended process is supported in Dynamics Ax with seamless integration. However that is not presented on this slide. Separate Ax2012 presentations exist for these process elements. Please consult these for a complete process overview.
The customer order decoupling point, on the left of the slide, determines the sequence of and the number of iterations for the elements presented in the sales order process wheel.
Customer order decoupling point scenarioes supported (on the left side of the slide) briefly sketches the various highlevel scenarioes supported salse order process wise in Microsoft Dynamics The Customer order decoupling point is the axis used when differentiating the sequencing and the relative importance of the process elements illustrated in the process wheel.
Let me give you a couple of examples:
In a typical sell from stock environment basically the sales order process high level consists of the following steps/tasks:
Order entry: Enter SO, Apply terms and conditions, Enter products and customer requirements, determine pricing and discounting, perform credit limit check, Perform order promising and Schedule sales deliveries. All of these elements are applied in one task
Issue order confirmation (sales order acknowledgement)
Release for picking (releasing to warehouse and outbound operations)
Follow up fulfilment progress
Now in comparison, in a typical make to order environment the step determine pricing and discounting, will in many cases be a separate task after order entry.
In an ETO environment, Enter SO will typically be preceded by a lengthy sales quotation phase where steps such as Negotiate terms and conditions, Enter products and customer requirements, determine pricing and discounting, perform
Credit limit check, Perform order promising and Schedule sales deliveries are extensively executed before the SO is entered.
These examples should be used to illustrate, that the sales order process wheel does not depict a firm sequence of steps and tasks. But the wheel and the elements
serve as illustration of key areas within the sales order process supported by Microsoft Dynamics 2012; areas whose relevance and sequence is business dependant.
Thank you for your attention!
Aftermath (do not say)
In the sales order process wheel Issue order confirmation and issue change order confirmation represents the business document communicated to the customer as part of the sales order process. Release to pick task
represents the internal decoupling point where the sales order feeds into the order fulfilment process, by which the order and its line items are picked, packed, and shipped from inventory and a packing slip is issued. Following
the order fulfilment process is a billing process, where a customer is billed and an invoice is issued. No separate decoupling point between the sales order process and the billing process are depicted in the sales order process
wheel.
In the sales order process wheel Follow up fulfilment progress covers the monitoring of the order fulfilment by the sales processer.

4. CCAX2012BV054