Pricing Fundamentals of SAP SD configuration (Pricing Configuration)

Pricing Fundamentals of SAP SD configuration (Pricing Configuration)

 

Configure sales pricing strategy, mainly through the following configuration menu is complete,

 

 

 

First, the condition table (Condition table) the configuration of the pricing

Condition table contains the condition table can be used to create a record Keys corresponding conditions, for example: Condition table: Material; Customer / Material. We can according to business needs, add the condition table custom number range 501 --- 999

 

Condition table Condition Tables, mainly for storing recording conditions. Condition records are usually created with a specific key, a group table to help define Condition record keys. In fact, with the header and Item level pricing of the most important fields in the standard system already available. From 4.5 version, you may be added to the non-key fields condition table, e.g. Condition table144 (for price catalog, Condition type PBUD).

 

Further, the condition table key fields must be at the beginning of the table.

 

Second, the configuration of the access order price (Access Sequence)

Access sequence by one or more condition tables. The system has many predefined standard access sequence, but the project practice, custom access order is always there. Create access order, we can define different levels of prices, discounts and additional costs. Each level can be a field or combination of fields defined in the condition table, using access sequence, the order can be defined at different levels. The system will be determined according to the defined sequence condition records.

 

For access sequence for each access, you can define access credentials required to perform a specific field (source fields);

E.g:

Material or pricing material;

Document currency or Local currency;

Sold-to party or Ship-to party;

 

 

另外,我们可以设置访问先决条件(Access Requirements),设置access依赖于requirements可避免不必要的access,这样减轻系统负荷。

 

 

三,定价配置之条件类型(Condition Type)

创建access sequence之后,被分配给condition type。

项目实践中,常常需要根据业务需求创建自定义的condition types,此时我们需要为每个condition type设置相关参数。例如,该条件类型是用于surcharges还是discounts以及是应该依赖于values还是quantities等等。

 

四,定价配置之:维护定价策略(Pricing Procedure).

将相关的Condition types 按照需要的顺序组合到pricing procedure中。

 

 

五,定价配置之:定价策略确定(Assign procedure determination)

最后,你需要为定价程序维护procedure determination table;pricing procedure 根据以下三个组合信息确定:

1)销售区域Sales area

2)客户主记录中'Customer pricing procedure'field

3)销售凭证类型的'Document pricing procedure'field

 

 

六,实施定价策略1 - 满足特定的定价需求

满足特定的定价需求可能需要1个或多个新定价元素,理解每个元素的目的和能力,以及定价元素之间的关系是关键的。

解决特定的问题需要创造性地构建和结合如下所有的定价元素:

条件表condition table:定义条件记录的关键字;

访问次序Access sequence:包含访问条件记录的层次;

条件类型Condition type:描绘定价条件的属性;

定价程序Pricing procedure:定义条件类型是怎样联系在一起的;

程序确定Procedure determination:选择正确的定价程序。

 

七,实施定价策略2 - 实施复杂的情景

下面的元素对于实施复杂的情景可能是必要的:

为定价添加新的字段 adding new fields for pricing –为了符合所有客户的需要;

必要条件Requirements—定义依赖条件和改善性能;

公式Formulas—扩展标准配置的限制;

 

Requirement routines and formulas 提供了修改标准定价逻辑的方法来满足独特的用户需求;

 

- 完 -

 

2020-02-08 写于苏州市。

发布了440 篇原创文章 · 获赞 684 · 访问量 141万+

Guess you like

Origin blog.csdn.net/weixin_42137700/article/details/104240000