Show TOC

 Changing Prices Collectively

You can change a vendor’s prices in info records, contracts, or scheduling agreements (only those with time-dependent conditions) in two ways:

  • Gross price

The price change is applied directly to the gross price.

  • Condition type

The price change relates to one particular condition type only. If the price change solely affects the freight costs, you can restrict the change to the condition type for freight costs.

If price scales exist and the period in which the changes are to be effective overlaps the validity periods of the scale levels, only the price in the first scale level is changed and this value is adopted in the remaining levels.

Example Example

The info record for the material Steel 1 and vendor Miller Corp. contains the following price scale:

12.01.1997 to 12.31.1997: $100

01.01.1998 to 31.12.1998: $120

You increase the prices of the conditions in the period 12.01.1997 to 12.31.1998 by 10%.

The price scale is then as follows:

12.01.1997 to 12.31.1997: $110

01.01.1998 to 31.12.1998: $110

End of the example.

Procedure

  1. Choose Start of the navigation path Master data Next navigation step Conditions Next navigation step Vendor price change Next navigation step <Document>. End of the navigation path

The initial screen appears.

  1. Enter the purchasing organization, vendor, and your remaining selection criteria.

  2. Specify whether the price change relates to the gross price or a condition type.

  3. Gross price

    Enter either an absolute value or a percentage.

    Condition type

    Cancel the selection of the Gross price field and enter the condition type and an absolute value or a percentage.

  4. Via the Sign (+/-) field, specify whether the value to be changed is positive or negative, or whether the previous condition (but not the +/- sign) is to be replaced by the new one.

  5. If the change is not to apply to the price levels of a scale, cancel the selection of the Scale lines field. Price changes in scales are only possible if they are expressed as percentages.

  6. Define the validity of the price change in one of the following two ways:

  7. – Enter the validity period in the Conditions valid from/to fields if the price change applies to a certain time period.

    SAP recommends this procedure.

    Please note that the existing validity periods are changed in accordance with the newly entered time period.

    If, for example, the conditions of an info record apply to the current year, but the price change applies to the months May and June only, the system divides the previous time period into three sub-periods: January - April, May – June, and July - December.

    – Enter the date as of which the change is to take effect in the Conditions valid on field. The change is then effective for all conditions that are valid on this key date.

  8. In the standard system, price changes are initially only simulated. To implement the changes, you must cancel the selection of the Test run field.

  9. Choose Start of the navigation path Program Next navigation step Execute Next navigation step . End of the navigation path

  10. The old and new prices are displayed with the validity period.

  11. Save the changes.

Note Note

When you apply price changes to scheduling agreements, contracts, or info records of your vendors, you can display the changes made in the relevant documents.

In outline agreements: Start of the navigation path Item Next navigation step Condition Next navigation step Environment Next navigation step Changes Next navigation step Per condition record. End of the navigation path

In info records: Start of the navigation path Extras Next navigation step Conditions Next navigation step Environment Next navigation step Changes Next navigation step Per condition record. End of the navigation path

End of the note.