Cómo crear un nuevo tipo de condición en SAP-MM: Guía paso a paso

Hola,

1. Crea una tabla de condiciones para el documento que deseas mantener en M/03.

2. Mantén el tipo de condición que deseas en M/06.

3. Crea una Secuencia de Acceso y luego asigna tu tabla de condiciones que has creado en el paso 1. Usa en M/07.

4. Define el Esquema de Cálculo y asigna el tipo de condición que has creado en el paso 2. Usa el código M/08.

Número de paso: define tu propio número de paso para el precio base de tu tipo de condición.

Contador: Especifica el número para la secuencia de cálculo automático.

Tipo de Condición: Ingresa el tipo de condición que has creado recientemente.

Descripción: no es necesario especificar nada, se toma por defecto de donde se define el tipo de condición.

Desde y Hasta: Aquí especificas el número de paso en el que deseas calcular en el tipo de condición, por ejemplo

Pb00 es el tipo de condición para el precio bruto

para el precio bruto, el número de paso es 1. Ahora deseas dar un descuento de proveedor sobre el precio bruto, es decir, pb00.

ahora define el tipo de condición como dije anteriormente ZDIS por ejemplo.

Luego asigna ZDIS a tu procedimiento de cálculo, luego en el campo DE ingresa 1 y en el campo A ingresa 0, luego el sistema calcula automáticamente el descuento sobre el precio bruto cuando creas un pedido.

Clave de Cuenta: Sirve para determinar diferentes cuentas de mayor si así lo deseas.

Espero que sea útil.

Saludos

Govind

Hola,

Pasos:

1. Tipo de Condición - Representación de un aspecto de las actividades de precios. (M/06)

2. Necesitamos mantener los registros de condición para el tipo de condición respectivo (MEK1) seleccionando la tabla de condición correspondiente.

3. Secuencia de Acceso - Estrategia de búsqueda para encontrar el registro de condición válido. (M/07)

4. Esquema de Cálculo (M/08): Estrategia secuencial en la que se aplican los tipos de condición en el cálculo de precios.

- Colocar +Paso y número de contador .+ e ingresar el tipo de condición respectivo.

- De & A (El valor se calcula en función del valor total entre De y A.) Necesitamos ingresar los números de paso en los campos De y A.

- Indicador Manual (Para entrada manual)

- Obligatorio (Para hacer obligatoria la condición)

- Estadísticas (Para recargos y descuentos - Informes estadísticos)

- Imprimir (Por artículo y total)

Los indicadores restantes no son obligatorios para los Procedimientos Generales de Precios.

Espero que responda a su pregunta. Por favor, hágamelo saber si necesita alguna aclaración.

Define Pricing Procedure

Select the pricing procedure which is the standard and copy it and create our own pricing procedure.

Highlight it and double click the Control icon in the LHS screen.

We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.

The detail description of each column is given below.

Step:

Number that determines the sequence of the conditions with in a procedure.

It indicates the position of the condition type in pricing procedure.

Ex.: 10, 15 etc.

Counter:

System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.

Access number of the conditions with in a step in the pricing procedure.

During automatic pricing, the system takes into account the sequence specified by the counter.

Condition Type:

It represents pricing element in pricing procedure as a base price, discount, freight and tax.

The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.

Ex.: PR00 - Price

K004 - Material Discount

K005 - Customer/Material Discount

K007 - Customer Discount.

Description:

System copies description of condition type from its description (V/06).

From and To:

1. From: This can be used as a base to the condition type for calculating further value.

2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.

Manual:

This indicator specifies whether the specific condition type can be determined manually during sales order processing.

If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.

For Base Price and Taxes, the entry should be automatic.

For Discounts and Freights, The entry should be manual.

If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.

If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.

Mandatory:

This indicator specifies that particular condition type is mandatory in the pricing procedure.

If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.

If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.

Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.

If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.

Statistical:

This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.

It is used only for information purposes only.

This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).

This is commonly used for condition types

SKTO - Cash Discount

VPRS - Cost (Moving average price/Standard Price).

Print:

The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.

Subtotal:

The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.

Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.

If the same fields are used to store different condition amounts, the system totals the individual amounts.

These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.

Requirement:

It is a routine that is written by an ABAP consultant according to the business requirement.

By defining Requirement in condition technique we can restrict the access of condition type.

To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in