Ansicht
Dokumentation

Condition Types in the Requirements Class ( RELN40C_COPCOBJ_KONDART )

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Short text

Condition Types in the Requirements Class

Description

Definition of the condition type by sales document item

In Release 4.5A you can specify condition types in the requirements class. This enables you to determine different condition types for different sales document items in the same sales document. For example, in a given sales document you can price one item on the basis of a sales order cost estimate while for another item the result of the sales order cost estimate is only passed on to the condition as a statistical value. The sales order cost estimate refers to the sales order item.

In the requirements class you can specify condition types for pricing and condition types for statistical updating of the planned costs.

If you don't specify a condition type in the requirements class, the system determines the condition type through the sales document type. In this case the condition type applies to all sales document items in a sales document.

Condition Type for Fixed-Cost Transfer from Line Item

From Release 4.5A you can define a condition type for fixed-cost transfer from line items in the requirement class. The values for the fixed costs are only statistical. Transferring the fixed costs improves the reliability of contribution margin analysis.

The standard version of the SD component uses condition type EK 03 for the transfer of the fixed costs. The condition type for the fixed costs is maintained in addition to the condition type for cost transfer of line items. The condition type for the fixed costs is maintained in the requirements class.

Software/hardware requirements

Installation information

If you upgrade your system from a release earlier than 4.5A, you must create condition type EK03 and add it to the SD pricing procedure.

Effects on System Administration

Effects on Customizing

Make the necessary settings in the requirements class.

See also: Check Requirements Class

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

ABAP Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 2802 Date: 20240420 Time: 051059     sap01-206 ( 50 ms )