Managing and applying sales and purchase agreements in Microsoft Dynamics ® AX 2012.
-
Upload
sophie-paul -
Category
Documents
-
view
219 -
download
0
Transcript of Managing and applying sales and purchase agreements in Microsoft Dynamics ® AX 2012.
Managing and applying sales and purchase agreements in Microsoft Dynamics® AX 2012
Sales and Purchase AgreementsSales and Purchase Agreements hold terms and commitments that are agreed with your trading partner. Microsoft Dynamics® AX 2012 offers the following features: Agreed terms are applied to purchase or sales order when using the
agreement – e.g., prices, discount, payment terms.
The agreement is applied during order creation process – Manually apply the agreement during order creation, or create orders directly from the agreement; the agreement is automatically selected during indirect order creation as, e.g., firming planned orders or direct delivery purchase orders.
Tracking the fulfillment of the commitments – Full visibility into the sales and purchase orders that are using the agreement, tracking actual trading against the commitment.
Commitments – Can be for a quantity or an amount of a specific product, or for products within a category.
Valid period – The period for which the commitment is valid.
On hold – Ability to disable the agreement from being used during order creation.
Intercompany sales and purchase agreements – Mirror the agreement in the buying and selling company, and use in the intercompany order chain.
Using the Sales or Purchase Agreement
ValidFrom
Valid To
For orders where the agreement is used, terms are applied: payment, price/discount, address
Committed amount or quantity
The agreement can allow the committed amount or
quantity to be exceeded
Tracking fulfillment
© 2012 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.
CCAX2012BV054