Shulou(Shulou.com)06/01 Report--

Let's explain and analyze the use of each field:

1. Step: it represents which condition type is put in front and which is put in the back when creating PO. If the step number is the same, then whoever chooses it first will be in front.

2. Counting: it doesn't have any practical meaning, it's just a number.

3. Condition type: the previously defined condition type is assigned to the pricing scheme.

4. Description: bring it out automatically according to the condition type.

5. From: means that if one condition type needs to use other condition types, you need to fill in the step number of another condition type. Please see step 3, "excluding tax net price", excluding tax net price should be total price-tax money, we have defined tax money as "negative", and here from 1 to 2, represents excluding tax net price = 1PBXX+2 input tax, because input tax is negative, so it is equivalent to the total price-tax money.

6. To: ditto.

7, manual: pricing conditions will not be automatically brought out, you need to select manually, if you do not check "manual" will be automatically brought out, this should be used in conjunction with the "manual entry" in "define condition type".

8. Required: if this field is checked, then the condition type must be selected, otherwise an error will be reported.

9. Statistics: never used.

10. Printing: whether the condition type allows printing when printing PO using the system standard function.

11. Subtotal: never understood. It is said that the price in this condition type is saved in a certain field.

12. Requirements: to determine whether there is a conflict between condition types, it is generally used for PBXX and PB00, and the others are rarely used.

13. Computing type: this computing type is more complex and requires the assistance of ABAP developers. Mainly used for price calculation, for example, here is when I enter the "tax code", the tax rate is automatically brought into the "input tax" condition class, and then calculate the tax money. Write down the development code and use it directly later.

14. Basic type: unused.

15. Subject code: the sales module determines the subject.

16. Interest: the purchasing module determines the subject: if it is not entered, it will be included in the inventory cost by default.

Version 2:

The options of the calculation scheme are described below:

Step: it is used to identify the number of the condition type in the scheme. The step number must be arranged in ascending order, but there can be intervals in the middle. Usually we set intervals between steps, mainly to facilitate the modification of the calculation scheme in the future.

Count: used to identify different types of calculation conditions in the same step.

CTYP: this is the type of condition described in section 3. When the condition type is entered, the system will automatically bring out the description of the condition type, such as the total price.

From and to: from and to is used in general to indicate the numerical summation of the type of condition from which step begins to which step ends. Note: when only from is entered, it indicates which step in which step the condition value is used as the basis for calculating the condition type.

Manual: controls whether the price condition can be taken out automatically. If it is not selected, it can be taken out automatically, but it is only applicable if the condition type does not assign access order. If the price condition has an assigned access order, whether the condition can be automatically taken out also depends on whether the corresponding condition can be found in the condition table. If the corresponding condition cannot be found, it still cannot be taken out automatically.

Required: control whether the price condition is necessary, not select means it is not necessary, select to indicate that the price condition must be added to the price condition.

Statistics: indicates that the conditional value does not change other values in the pricing scheme, but this option is not valid for the condition that the pricing category is the base price, and this option is often used in conjunction with the condition that the pricing category is the cost of delivery. and check the "accruals" of control data 2 in the condition. Application example: in the current purchase order, if there are additional delivery costs, such as transportation costs and when the transport supplier is inconsistent with the purchase order supplier, you can increase the delivery cost condition in the pricing scheme and select the selected item under the condition.

Print: this option doesn't seem to work.

Subtotal: I don't know where to use it at present.

Requirements: used to assign a requirement to a condition, which is calculated by the solution when the condition meets the requirement, and the requirement can also be customized.

Calculation type: a method of calculation that sets conditions different from system standards, such as the separation of price and tax on a unit price, which can be customized.

Basic type: it is used to set the condition calculation, which is different from the default calculation base of the system, such as the material is priced according to the gross weight instead of the basic unit of the system.

Subject code: I don't know where to use it at present

Interest: transaction codes can be customized to meet financial accounting requirements for some special procurement expenses, such as delivery costs.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.