다음을 통해 공유


Set up purchase or sales agreement functionality

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic describes the following key steps to set up a purchase agreement or a sales agreement:

  • Enable configuration keys.

  • Set up a number sequence.

  • Set up a classification for purchase agreements and sales agreements.

Enable configuration keys

The following configuration keys must be selected to enable purchase agreements and sales agreements:

  • Purchase and sales agreement configuration key (TradeBlanketOrder)

  • Optional: Project I configuration key (ProjBasic)

  • Optional: Public sector configuration key (PublicSector)

The Purchase and sales agreement configuration key must be enabled. Additionally, the Project I configuration key must be enabled to make the project fields available in the Purchase agreements and Sales agreements forms, and to make purchase agreements and sales agreements available in Project.

For more information about how to enable configuration keys, see Configure application functionality.

Set up a number sequence

Number sequences automatically assign identification numbers to purchase agreements in the Purchase agreement form or sales agreements in the Sales agreements form. Before you create any new purchase agreements or sales agreements, follow these steps to set up a number sequence.

  1. In the Number sequences form, create a number sequence:

    1. Click Organization administration > Common > Number sequences > Number sequences.

    2. On the Action Pane, click Number sequence to create a new number sequence.

    3. In the Number sequence code field, enter a code for the number sequence.

    4. In the Name field, enter a description of how and where the number sequence is used. For example, if the number sequence is used for purchase agreements, you might enter Purchase agreement.

    5. On the Segments tab, define the format for the number sequence. Use the number sign (#) for numbers and the ampersand (&) for letters.

    6. On the General tab, define the interval and increment for the number sequence.

    7. Select the Continuous check box.

      Note

      To enable purchase agreement IDs or sales agreement IDs to be entered manually, select the Manual check box. For more information about the fields in this form, see Number sequences (list page).

    8. On the References FastTab, click Add, and then select a module and an agreement ID.

      • For purchase agreements, select Purchase and Purchase agreement ID.

      • For sales agreements, select Sales and Sales agreement ID.

  2. For purchase agreements, select and apply the number sequence in the Procurement and sourcing parameters form:

    1. Click Procurement and sourcing > Setup > Procurement and sourcing parameters.

    2. Click the Number sequences column, and then, in the grid, locate the reference for the purchase agreement.

    3. In the Number sequence code column, select the number sequence that you defined in the Number sequences form.

    4. Close the form.

  3. For sales agreements, select and apply the number sequence in the Accounts receivable parameters form:

    1. Click Accounts receivable > Setup > Accounts receivable parameters.

    2. Click the Number sequences column, and then, in the grid, locate the reference for the sales agreement.

    3. In the Number sequence code column, select the number sequence that you defined in the Number sequences form.

    4. Close the form.

Set up a classification for purchase agreements and sales agreements

When you create a new purchase agreement or sales agreement, you must always select the type of purchase agreement or sales agreement. You can also define your own purchase or sales agreement types, which allows you to use names that fit the domain of your organization, such as Blanket order.

Important

When Microsoft Dynamics AX 2009 is upgraded to Microsoft Dynamics AX 2012, purchase orders and sales orders that have a Blanket order type are automatically converted to purchase agreements and sales agreements, respectively. The default agreement type for purchase agreements is Blanket purchase agreement. The default agreement type for sales agreements is Blanket sales agreement.

Follow these steps to create agreement types.

  1. Click Procurement and sourcing > Setup > Purchase agreements > Purchase agreement classification.

    –or–

    Click Sales and marketing > Setup > Sales agreements > Sales agreement classifications.

  2. Enter a name in the Name field. If a name is already displayed in the grid, click New, and then enter a name.

  3. To define agreement types for a specific locale, click Translations to open a form where you can create one name per language.

  4. If the Public sector configuration key is selected, additional controls are available for purchase agreements.

    • To enter information about subcontractors on purchase agreements that use this classification, select the Subcontractors check box.

    • To enter information about insurance policies and bonds on purchase agreements that use this classification, select the Certifications check box.

    • To enter information about milestones and tasks on purchase agreements that use this classification, select the Activities check box.

    • To require the use of direct invoicing and prevent the use of release orders with purchase agreements that use this classification, select the Require direct invoicing check box.

Note

You cannot delete an agreement type that is currently used for existing purchase agreements or sales agreements.

See also

Purchase agreements (form)

Sales agreements (form)

Number sequences (list page)

Agreement classification (form)

Purchase and sales agreement configuration key (TradeBlanketOrder)

Project I configuration key (ProjBasic)

Public sector configuration key (PublicSector)