Lauren Daigle | LIBERADO EL EXPLOIT QUE AFE... | The Finest Hours 30692

AX2012_ENUS_DEVIV_08.pdf | Microsoft

Please download to get full document.

View again

of 54
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information Report
Category:

Others

Published:

Views: 6 | Pages: 54

Extension: PDF | Download: 0

Share
Related documents
Description
dynamics Ax 2012 development 4 chapter 8
Transcript
  Chapter 8: Use and Design of the Sales and Purchase Modules 8-1 CHAPTER 8: USE AND DESIGN OF THE SALES AND PURCHASE MODULES Objectives The objectives are: ã   Review the general features that are supported with sales and  purchase orders. ã   Describe how sales and purchase orders integrate with other modules, ã   Discuss the primary tables used in the purchase order flow. ã   Describe how the PurchType, PurchLineType, and PurchTotals classes work. ã   Describe how trade agreements are used and set up. ã   Review the data model for trade agreements. ã   Discuss how the trade agreement classes are used and can be extended. ã   Describe how sales and purchase agreements are used and set up. ã   Review the data model for sales and purchase agreements. ã   Discuss how the sales and purchase agreement classes are used and can be extended. ã   Describe how pricing policies are used. ã   Describe how charges are used and set up. ã   Review the data model for charges. ã   Describe how the FormLetter framework is used. ã   List the various documents that are processed through the FormLetter framework. ã   Describe the data model for updating documents. ã   Describe how the FormLetter classes relate to each other and generally work. ã   Describe how to make modifications to the FormLetter framework. ã   Describe the differences between the sales order and the sales quotation features, data model, and classes. ã   Describe the differences between the purchase order and the request for quotation features, data model, and classes. ã   Describe the differences between the purchase order and the  purchase requisitions features, data model, and classes. ã   Explain how to use and set up categories and category hierarchies. ã   Review the data model for categories and category hierarchies.  Development IV in Microsoft Dynamics ®  AX 2012 8-2 Introduction The sales and purchasing processes are important components of every business. Microsoft Dynamics ®  AX 2012 provides functionality businesses can use to manage purchase and sales information with the integration to inventory and the general ledger. The order to cash process is also referred to as the sales process, and involves many steps. These steps include gathering leads and opportunities that drive the creation of prospective customers, followed by the quotation process, and after the quotation is accepted, generating confirmed sales orders. Next is the picking and shipping of the products and then invoicing or billing the customer. After the customer receives the goods payment must be collected. Because every business has different processes the source to sell process steps can be conducted differently, Microsoft Dynamics AX 2012 helps businesses manage these processes that are usually controlled by the type of customer that includes, business-to-business (B2B), business-to-customer (B2C) or by specific  business requirements. The procure to pay process is also referred to as the purchase process, and it also includes many steps, and is similar to the source to sell process. These steps include requesting and qualifying a new vendor, submitting purchase requisitions  by employees requiring various products, followed by the request for quotation  process with the vendor. When the purchase requisitions and, or the request for quotations are approved, purchase orders are generated and then confirmed with the vendor. After the products are delivered, a product receipt is generated and the invoice is recorded for the purchase order, and then payments must be generated to the vendor. This course introduces the features in Microsoft Dynamics AX 2012 that support the sales and purchase processes, and it also reviews the data models and coding  patterns for many of the features. Since the customer and vendor data models and coding patterns are similar, the details of both will not be discussed. Sales and Purchase Orders This topic introduces the primary features available for sales orders and purchase orders in Microsoft Dynamics AX 2012. Additionally, the data models for sales and purchases will be reviewed and the coding patterns for purchases will also be discussed. Sales Order Feature Overview Sales orders in Microsoft Dynamics AX 2012 can be accessed from the Accounts receivable  module and the Sales and marketing  module. Although there are additional list pages and reports in each module that are different, the  basic sales order information that is available in each module is identical.  Chapter 8: Use and Design of the Sales and Purchase Modules 8-3 The primary components of a sales order consist of a header and one or more lines. Each sales order header is linked to one specific customer account. Each line of a sales order is linked to one specific item number or one specific sales category. When a sales order line is linked to an item number, the category field is defaulted based on the category assigned to the item. You can leave the item number field blank, and select only a category. Several types of sales orders exist and each has different functionality. ã   Journal : Does not have any inventory transactions, and cannot be  processed. Most often it is used as a template or place holder for a future sales order. ã   Sales order : The standard sales order that does have inventory transactions and can be processed. ã   Subscription : Special sales order used for repeating, for example a magazine subscription. ã   Return order : Used when a customer is returning items previously  purchased on a sales order. The quantities on this order are always negative. ã   Item requirements : Special sales order used with the Project management and Accounting  module. These cannot be created manually, and can only be generated from a project. After a sales order is created and the customer, item or category, quantity, and  pricing information are entered, the order must be processed. The four steps to  process a sales order include the following. 1.   Confirmation : The order entry process is completed and the details are printed or emailed to the customers to confirm the order. 2.   Picking list : A document called a picking list is generated for the warehouse workers. The warehouse workers use this document to find the required items in the warehouse and bring them to a  packaging or staging location for delivery. This is also referred to as picking the items. When this process is completed, the inventory is updated to show a status of picked so that the items cannot be used on other sales orders. 3.   Packing slip : A document called a packing slip is generated for the delivery of the items. The warehouse workers will use this document to verify the items that need to be packaged or delivered, and this document is usually sent with the shipment to the customer. When this process is completed, the inventory is updated to remove the quantities from the on hand inventory. 4.   Invoice : A document called an invoice is generated. When the invoice is generated for a sales order, it is the final step of the sales order process where the customer is effectively billed or invoiced for the items that are delivered. This process creates an open transaction on the customer’s account that must be paid for by the customer.  Development IV in Microsoft Dynamics ®  AX 2012 8-4 As a sales order is processed, the status of the order is updated and the related inventory transactions are simultaneously updated. Sales orders also support other features such as the following. ã   Support for multiple delivery addresses. ã   Delivery schedules used to schedule one line for delivery on different dates. ã   Ability to override pricing and discount information at the line level. ã   Options to add charges such as freight or installation fees. ã   Functions to create a purchase order or a production order from a sales order. ã   Options for reserving inventory. A reservation of inventory on a sales order ensures that the items will be available for delivery on the date agreed upon with the customer. Sales Order Integrations The Sales  module is used to keep track of sales activities. The following figure shows the interface with other modules in Microsoft Dynamics AX. FIGURE 8.1 SALES ORDER INTEGRATIONS WITH OTHER MODULES
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks