princing doubts

[Former Member]

1.what do you mean by statistical condition type?

2.Why do I use condition indexes? How do I activate them?

3.From which partner function of a customer does system read the customer tax classification?

[Former Member · Accepted solution]

Dear Rajesh,

3. From SHIP TO PARTY partner function of a customer system read the customer tax classification

regards,

Vishal

[former_member227476]

dear rajesh

1) Statistical:

It indicates the purpose of condition type is only for information purpose. The value of condition type will must be taken into consideration in the net value calculation. Ex: condition type “VPRS” (-cost), as this “VPRS’ copies the cost of material from the material master and deducts the value from net value per item to calculate profit margin so the purpose of having VPRS is only to copy the cost of the material and it sis not at all participating in calculation of net value. So that it should be a statistical

2) Condition Index:

By using condition Index for particular condition type we can maintain condition records. (Maintain condition record means, creation, change, setting deletion flag, copying etc)

Together with “condition update” we can restrict the usage of the condition type during sales order processing Ex: per particular sales order (3 or 4) or based on total condition value

3) i think from sold to party,

rewards if it helps

siva

[Former Member]

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).

Condition Index:

It can be created for particular condition type to maintain condition records.

When checked this specifies whether the system updates one or more condition indices when maintaining condition records.

This makes it possible to list or maintain condition records independently of condition type and condition table

Customer Tax classification:

It is based on the ship-to party.

Regards

AK

[Former Member]

statistical condition type indicates it well not include in the net value it is for statistical purpose onley exmp VPRS

You can use the index condition to specify here whether the condition index table is updated when the first field is filled or only once all index fields have been filled.

From ship to party system well read the tax classification

[Former Member]

statistical condition type indicates it well not include in the net value it is for statistical purpose onley exmp VPRS

could u plz tell me by taking an example.

[Former Member]

Statistical ConditionTypes are Conditions which are a component to calculate pricing, but does not adds to actual value to be billed. Statistical Condition type should not have Account Key in pricing procedure & accounting document for the same is not required, as it is statistical.

Regards,

Rajesh Banka

[former_member183879]

Condition Index:

SPRO--SDBASIC FUNCTIONSPRICING--MAINTAIN CONDITION INDEX

Here read the implementation guide. It is highly descriptive, and you can understand everything about condition index.

Statistical condition type

C.Ts are defined as statistical at the pricing procedure level. If done so, the value of such C.Ts wont be considered while calculating the net price of the item.

Tax classification

To my knowledge , it is Sold to party. Can somebody else also confirm this.

<b>Notes on Condition index, picked up from implementation guide is as follows.</b>

Maintain Condition Index

In this IMG activity, you specify which fields of the condition records are taken into account when creating the index. The selected fields are displayed as selection criteria in the application menu for selecting condition records. In addition to the possibility of searching for condition records using the condition type (for example, prices, surcharges, discounts) and the organizational data, you can define and use other selection criteria using the condition index.

Example

The standard system contains two indexes with which all condition records can be selected for a certain material (index 001) or a certain customer (index 002) independently of the condition type, for example.

Note

Note that the number of indexes to be updated reduces system performance when posting condition records. Take this into account when creating and activating indexes.

Default settings

Two indexes exist in the standard SAP R/3 System:

Index 001 takes the material, sales organization and distribution channel into account when creating the index.

Index 002 takes the customer, sales organization, distribution channel and division into account when creating the index.

For reasons of performance, the condition types for the condition index are not flagged in the standard system. If a condition type is to be taken into account for condition indexes, it must be activated (condition type detail screen).

Requirements

Before using condition indexes (standard and user-specific indexes), you must define overviews for condition maintenance. See the section "Overviews" for further information on the overviews for condition maintenance.

Actions if you use standard indexes

1. Check whether the condition indexes in the standard system (001 or 002) meet your requirements.

2. Activate each standard index that you want to use.

The indexes are inactive at delivery to avoid unused indexes being updated. Enter one of the two requirements for the index update.

Requirement 1: all index fields must be filled

Requirement 2: the first index field must be filled

3. In the field "Condition index" on the condition type detail screen, select every condition type to be taken into account when creating the index. The condition types are not flagged in the standard system.

4. You can change and display standard indices:

Change

Display

Actions if you create and use your own indexes

1. You can create a condition index either by copying an existing index and changing it afterwards or by carrying out the following steps.

2. Check whether the list of allowed fields meets your requirements. If you need new fields, you can include them in the field catalog for the condition index.

3. Create a condition index by entering a table between 501 and 999 and choosing the required fields from the list of the allowed fields.

The selected fields can have a maximum length of 100 characters.

Define the sequence of the fields so that the first field in the index is the field that is most frequently searched for. In addition, SAP recommends that you include the sales organization and the distribution channel.

Generate the condition index. Indexes created by you are activated automatically.

4. In the field "Condition index" on the detail screen of the respective condition type, select the condition types to be taken into account for the condition index.

Actions if you reorganize secondary indexes

You must reorganize condition indexes in the following cases:

If you created a new condition index and want to set it up for existing condition records.

If you changed an existing condition index and want to set it up with the current condition records.

Proceed as follows:

1. Enter a condition index or an interval of indexes.

2. Enter the date and the time as of which the index is to be set up.

Reward if this helps you