Elements of the Condition Technique zz

http://www.sapclub.org/blog/syssam/articles/3725.html

排斥条件Excluding conditions

在定价程序中，条件condition能够链接到requirements；

Requirements能够检查condition exclusion indicator，如果设置，则忽略该condition；

Condition exclusion indicator可以设置在condition type或者condition record；

Contents:

Condition Types

Condition Records and Tables

Access Sequences

Calculation Schemas

Condition Types:

Condition Type只能在之中定义。

路径是：Material Management à Purchasing à Conditions à Define Price Determination Process à Define Condition Types

我选择了PB00来做个说明：

Condition Type: PB00 Name: Gross Price

Access Sequence: 0002

存取顺序一会会有详细说明。

Control data1:

Field	Description	Remarks
Cond. class	Condition Class	定价等级，用来区分Condition Type，主要看A和B两大类。A是discount/surcharge，B是prices
Calculat.type	Calculation Type	计算类型，可以是固定金额，百分数，又或者是根据数量，金额，重量等等计算
Cond.category	Condition Category	定价类别，表示该condition type是价格还是费用等，该字段有很多的控制功能
Rounding rule	Rounding Rule	舍入规则
StrucCond.	Structure Condition	结构定价 (不明白)
Plus/minus	Plus/Minus	正负，正表示是discount负表示是surcharge，或者可以两者都行

Condition Class:

A Discount or surcharge

B Prices

C Expense reimbursement
D Taxes
E Extra pay
F Reserved (IS-OIL)
G Tax Classification
H Determination sales deal
Q Reserved (IS-OIL)
W Wage Withholding Tax

Calculation Type:

A Percentage

B Fixed amount
C Quantity

D Gross weight

E Net weight

F Volume

G Formula

H Percentage included

I percentage (travel expenses)

L Points

M Quantity – monthly price

N Quantity – yearly price

O Quantity – daily price

P Quantity – weekly price

Q Reserved (IS-OIL)

R Distance-dependent

S Number of shipping units

T Multi-dimensional

Rounding Rule:

Commercial 商业，就是4舍5入

A Round up 向上舍入，就是总是入

B Round down 向下舍入，就是总是舍

Condition Category：

You can assign a condition category to a condition type. The condition category has various control functions. For example, condition category U (for precious metal discounts and surcharges) causes a new price determination process to be carried out at the time of goods receipt, and condition category E (for cash discount) causes the discount to be derived from the terms of payment.

The following condition categories are relevant to Purchasing:

Cat.	Description	Assigned to the following condition type in the standard system:	Further information
H	Base price	PB00	A condition type with the condition category H must always exist in the calculation schema. Exception: Stock transfers. If an access sequence is assigned to the condition type, you must assign a supplementary calculation schema to the condition type. Otherwise, the system is not able to calculate a net or effective price. If you manually enter a price in the purchasing document, it is inserted into the condition type.
B	Delivery costs	FRA1	If you use this condition category, you can enter separate invoices for material costs and delivery costs (e.g. freight charges). You must flag the condition type as "provision-relevant". You must assign a transaction/event key in the schema (for account determination purposes).
N	Non-deductible input tax	NAVS	Depending on the tax code in the PO item and the tax calculation schema, the system calculates the non-deductible tax portion and inserts it in the condition type with the category N. The condition type has the calculation rule "absolute amount". Normally, the access sequence that regulates tax code determination is assigned to the condition type.
d	Vendor’s confirmed price	EDI1, EDI2	If the vendor confirms a price via EDI, the system inserts the price in the condition type with category d.
E	Cash discount	SKTO	The system derives a percentage from the terms of payment and inserts it in the condition type with the category E. The condition type is included in the calculation on a statistical basis only.
U	Precious metal discount/surcharge	GAU1, GAU2	See
G	Moving average price	P101	The system inserts the moving average price/valuation price of the material in the condition type with category G. This makes sense if no purchase price exists (e.g. in the case of stock transfers).
J	Sales price excl. taxes (only for Retail)	MVK2 (prior to Release 4.5A, MVK1)	The system inserts the currently valid sales price (excluding tax) for the ordering store in the condition type with category J. If sales price valuation is active in the valuation area of the store, the condition type should exist in the calculation schema used for determining the purchase price.
W	Sales price incl. taxes (only for Retail)	MVK0	The system inserts the currently valid sales price (including tax) for the ordering store in the condition type with category W. If sales price valuation is active in the valuation area of the store, the condition type should exist in the calculation schema used for determining the purchase price.

PB00是gross price，也就是总价，对应以上字段我们知道它的

Condition class是 B, 也就是价格

Calculation Type是C, 也就是数量相关的，比如衣服，表示每件多少钱，或者每打，单位可以变化，但是是Material的计量单位。

Condition Category是H, 是基本价格

Rounding Rule是商业的4舍5入

Structure Condition没有设定

Plus/Minus是正和负，也就是可以为正也可以为负，不知道负的情况可能是什么时候？赔本生意?

Group Condition:

Field	Description	Remarks
Group cond.	Group Condition Indicator	是否是group condition
RoundDiffComp	Rounding difference comparison
GrpCond.routine	Routine number for creating group key

会在Group condition之中再详细说明

PB00在我的系统之中不是一个group condition

Changes which can be made:

Field	Description	Remarks
Manual entries	Manual entries Indicator	人手操作定义，可以是没有限制，以及不能，也可以为人手和自动设置优先级
Header condit.		是否是header condition
Item condition		是否是item condition
Delete		是否可以被删除，也就是在purchasing document之中，用户是否可以删除这个condition type
Amount/percent		在purchasing document之中是否可以改变amount和百分比
Value		在purchasing document之中是否可以改变value
Qty relation		在purchasing document之中是否可以改变Unit
Calculat.type		在purchasing document之中是否可以改变calculation type

PB00对于人手操作是没有限制的: _ no limitations

不是一个header condition

是一个item condition

在处理document时候不可以被删除

在处理document时候可以改变amount和percent

在处理document时候不能改变value

在处理document时候可以改变material的unit

在处理document时候不能改变calculation type

Master date:

Field	Description	Remarks
Valid from		Condition record之中的valid from的default value
Valid to		Condition record之中的valid to的default value
RefConType		Reference condition type，一般用于相同内容不同名城的condition type，这样在condition record之中只是需要包含被reference的condition type
RefApplicatio		Reference application
PricingProc		Price procedure，用于determin那些包含在gross里面的一些附加condition type，那些condition type没有access seq，也就意味着没有哪个condition table会存储这些记录，而它们只能与gross price一起存在
delete fr. DB		定义删除condition record时候的操作
Condition index		是否update condition index

PB00的default valid from/to是today和31.12.9999

没有reference的condition type和application

PB00是gross price所以有很多其他condition type附加在PB00的condition record之上，使用RM0002来查找这些condition type

删除的时候只是设置删除标志

不会更新condition index

Scales:

Field	Description	Remarks
Scale basis		使用数量还是金额的scale
Check value		是否要升序或者降序输入scale
Scale type		From还是to 或者graduated
Scale formula		计算scale base value的公式
Unit of meas.		当使用group condition的时候的unit

Scale basis:

B Value scale

C quantity scale

D gross weight scale

E net weight scale

F volume scale

G scale based on a formula

L point scale

M time period scale - month

N time period scale - year

O time period scale - day

P time period scale - week

R distance

S number of shipping units

T reserved (IS-OIL, time prices)

X reserved (IS-OIL, day prices)

Scale type:

Can be maintained in condition record

A base-scale

B to-scale

C not used

D graduated-to interval scale

PB00是基于quantity scale

对于scale的输入没有checking

Scale type在输入condition record的时候决定

没有定义scale base value的计算公式

因为不是group condition，所以也没有为group condition定义scale unit

Control data 2:

Field	Description	Remarks
Currency conv.	Currency conversion after multiplication indicator	决定货币转换是在价格乘以数量之前或者之后
Accruals	Condition is relevant for accrual (e.g. freight)	Statistical condition
Inv.list cond.	Condition for invoice list	Internal costing
Int-comBillCond	Condition for inter-company billing
Promotion cond.	Condition for promotions	是否只是在promotion有效
Variant cond.	Condition for configuration
Qty conversion	Quantity conversion	Only when quantity-dependent
Exclusion	Condition exclusion indicator
Rel.Acc.Assig.	Relevance for account assignment

Sales pricing:

Field	Description	Remarks
Rel. to pricing	Sales price calculation: relevant to pricing
Pricing on/off	SP calculation: “relevant to pricing” ID can be changed

Special Pricing Function-Promotion and Sales deal

http://www.slideshare.net/arun_bala1/sap-sd-sales-deal-promotion
PPT demo

http://help.sap.com/saphelp_45b/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm

Steps:

You create promotions and sales deals in the same way. To create a new sales deal:

1. Choose Logistics
® Sales/distribution ® Master data in the main menu screen.

You reach the Sales Master Data screen.

2. Choose Agreements
® Sales deal ® Create.

You reach the Create Sales Deal screen.

3. Enter a sales deal type (for example, 0101) and choose Continue.

The Overview Agreement screen will appear. The system will propose a validity period.

4. Enter the optional data, such as:

– Short description of the sales deal

– An external reference (from the customer)

– The number of the promotion, if any, to which the sales deal is assigned

– Special payment terms



If you assign the sales deal to a promotion, the system proposes any special payment terms that you have defined for the promotion.

5. If you do not want to create condition records for the sales deal at this time, save your data. If you want to create condition records immediately, go to the next procedure.

Creating Condition Records Within a Sales Deal

You can create condition records for a sales deal in the following ways:

• At the same time as you enter the master data for the sales deal in the system. (In this case, the system automatically creates the link between the condition records and the specific sales deal.)
• By creating a new sales deal with reference to an existing sales deal and copying some or all of the condition records over
• By adding new condition records into an existing sales deal.(In this case, you enter the number of the sales deal manually.)
• By copying existing condition records into a sales deal you have already created.

For further information about copying condition records, see Copying Condition Records.

Steps:

To create condition records directly from within a sales deal:

1. Choose Pricing in the overview screen of the sales deal.

The system displays a list of valid condition types for this type of sales deal.

2. Select the condition type for which you want to create a condition record and enter your data.
3. If you want to create additional condition records for the sales deal, choose Back to return.

The system returns you to the dialog box that lists the valid condition types you can use.

4. After you have created the condition records you want, choose Back and save your data.

Release Status

Use

The release status for condition records in a sales deal enable you to limit the use of records that have already been created.

Release status has the following characteristics:

• no entry: released
• A: Blocked
• B: Released for price simulation
• C: released for price simulation and planning

The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.

Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.

When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.

A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.

The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.

The release status for condition records in a sales deal is displayed in the status information and on the detail screens for condition maintenance.

If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.

Awarding release status is only possible for sales deals and not for bonus agreements or individual record levels. Maintenance of the status for individual condition records is not implementable for the current status of the condition master records. This is connected with the overlapping of validity periods in combination with the release status, which does not occur in sales deals, as you can not create a condition record with the same key in another sales deal.

SD--定价过程的16个字段的作用说明 zz

http://blog.csdn.net/CompassButton/archive/2007/08/25/1759141.aspx

SD--定价过程的16个字段的作用说明收藏

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 theconditionswithin 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 conditionswithin 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.

1. {+}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 case of cut-off period for rebates).
• For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
• This Requirement will ensure that these condition types will appear only during the billing document processing.
• If new Requirements are to be defined we follow the procedure given below.
  • Go to T.Code: VOFM. - Maintain Requirements & Formulas
  • Click on the "Requirements" in the top menu and then click on "pricing".
  • We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
  • And we assign the application type like V - Sales/Distribution etc.

AltCty - Condition formula for alternative calculation type:

• It is again a Routine that is written by ABAP Consultant.
• It is an alternative formula for the condition type that can be used instead of standard formulas.
• For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
• Ex.: 950 0 Profit Margin 11.
• So we assign 11 - Profit Margin.
• If new routines are to be defined we follow the procedure given below.
  • Go to T.Code: VOFM. - Maintain Requirements & Formulas

• • Click on the "Formulas" and then on the "Condition Values".
  • We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
  • And we assign the application type.

AltCBV - Alternative formula for condition base value:

• Formula for determining the condition basis as an alternative to the standard.
• It is again a Routine that is written by ABAP Consultant.
• It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
• Ex.: Freight - KF00.
• Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
• In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
• During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
• Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.

AcyKy - Account Key/ Accrls - Accruals:

• The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
• In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
  • ERB Rebate sales deduct.
  • ERF Freight revenue
  • ERL Revenue
  • ERS Sales deductions
  • ERU Rebate accruals
• For Ex.,
  • For all Price condition types like PR00 etc. we assign ERL - Revenue.
  • For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
  • For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
  • For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
• This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
• This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

SD-- SAP定义的几个标准Cost Condition的说明和科目配置 zz

http://blog.csdn.net/lqq417/archive/2009/01/16/3793520.aspx

VRPS:
n In the standard version, condition type VPRS is used to retrieve the standard cost of the material.
n It is used as a statistical value by the pricing procedure.
n Using condition category G, VPRS accesses the valuation segment of the material master locating either the standard cost or the moving average cost, as specified in the material master.
n Condition category S will always access the standard cost, while condition category T will always access the moving average cost.
n The profit margin is calculated using formula 11 in the pricing procedure. This formula subtracts the cost from the net value 2 subtotal.

SKTO:
n In the standard system, condition type SKTO is used to retrieve the cash discount rate.
n It is used as a statistical value by the pricing procedure.
n Table T052 is accessed using condition category E and an amount is calculated from the first percentage rate of the item payment terms.

EDI1 & EDI2:
n The customer expected price can either be entered manually in the order, or retrieved from the incoming IDoc in an EDI environment.
n Condition type EDI1 is used to compare the net price for each item. Condition type EDI2 is used to compare the overall item value (net price * quantity).
n Calculation formula 9 is assigned to condition type EDI1 in the pricing procedure. This formula tests for a maximum deviation of 0,05 currency units.
n Calculation formula 8 is assigned to condition type EDI2 in the pricing procedure. This formula tests for a maximum deviation of 1.0 currency units.
n If the customer expected price differs from the automatically determined price or value by more that the maximum difference allowed, the system will regard this order as incomplete when it is saved.
n You may process lists of orders having differences in prices, allowing the system to use or correct the price it determined.

What is the difference between VPRS (cost) and EK01 ( actual cost) and where these are used?
VPRS
VPRS cost is mainly used to determine weather the material is having the standard price or moving average price
The condition type VPRS is labeled as a statistical condition in the pricing procedure.
in this ,Using the condition category G, the condition type VPRS goes into the valuation segment of the material master and determines from here the standard or average price.
The condition category S always accesses the standard price whereas condition category T always accesses the average price.

EK01

1)EK01 can be used as a basis for determining a price for the make-to-order item.
2) EK02 is a statistical condition which can used instead of VPRS to calculate the profit margin for the assembly item.
3)Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
4)Condition type EK01 is selected for sales document type TA (standard order). This means that the value from the cost estimate goes directly into pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated.

1）销售订单肯定有pricing procedure，否则在销售订单阶段就该出错了。

2) pricing procedure项下有各种condition type，诸如销售单价（PR01/PR00）、税收（MWSI/MWST）、折扣（K004/K005/K007）等等。

3）上述三类condition type，在pricing procedure后肯定有一个account key，售价类ERL表示收入、流转税类MWS表示销项流转税、折扣类ERB表示sales deduction。

4）VKOA，将SD模块中的两大功能组件“价格条件”和“收入账户”连接起来：顾客主数据中（对于发票而言，应该是payer）有 customer account group，物料主数据中sales data 2有material account group，销售区域三要素是从销售订单带过来的。这样001表中可以写入科目，从而实现自动找到会计科目。

5）同样是VKOA，4.6C标准配置应该是1-->2--->3---->5---->4的顺序，如果表001～005 中，相同的Account key各自对应一个不同的G/L号码，则系统将严格按照“1-->2-->3-->5-->4”的有限顺序（这个叫作 access sequence）来读取G/L科目并采取它。

在有折扣的情况下，第一行记录应收账款，对应顾客；第二行记录销售净收入，对应销售科目；第三行记录折扣科目，对应VKOA项下的ERS所确定的会 计科目；第四行记录销项税收，对应流转税科目。因为在pricing procedure中，折扣类（K00X）放在流转税的前面（税前折扣，除非脑袋进水，一般不会给买主以税后折扣的），所以会计凭证中折扣的行目排在税收 之前。

FI/SD通过tcode VKOA为billing设置过帐科目，用户可以创建自己的科目定义数据表。 科目是做到COA级的，通过KOFI/KOFK这两个condition type确定分别过帐到FI和CO凭证中。 由于PricingProc.是同SalesOrg.相关联的，所以科目在Organization上首先要做到SalesOrg. 级，其后的AccountKey是在PricingProc.中和不同的PriceConditionType相关联的，决定着最终销售收入、折扣、附加 费用、预提等过到不同科目上。

在condition中显示discount的condition type

怎么在sales order的condition中显示某个condition type，但是数值为空？这样操作人员就可以手工输入折扣值。

1.在pricing procedure中，把该condition type设置为Manual+Required
2.VK11去maintain这个condition type的折扣值，设置为零
3. 创建order的时候，就可以看到该condition type出现，但是数值是空 ，需要手工输入

Down Payment Processing

Invoicing a Project with Down Payment Processing
http://help.sap.com/saphelp_46c/helpdata/en/e6/4a6dc89e0311d189b70000e829fbbd/frameset.htm

Make-To-Order Production of Elevators
http://help.sap.com/saphelp_46c/helpdata/en/51/582a6ea44c11d189bf0000e829fbbd/frameset.htm