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

How to achieve SAP SD pricing strategy, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Implementation of SAP SD pricing strategy, including condition type, access order, etc.

1, test data

Custom condition type: Z007

Custom condition table: 904

Custom access order: Z007

Custom pricing policy: Z00001

Customer master data: 10000010

Material master data; T-AS110

SO Type:ZNOR

Range of sales: C999/Z1/Z1

The 'Customer Group' field of customer master data: 01

Customer Pricing Procedure' field of customer master data:'B'

2, customize a condition type Z007

You can copy the condition type K007 and rename it Z007, as shown in the following figure.

Next

Next

3. Add a field to the field directory

Next

Next

Next

Locate the ABC identifier with the following button

Next

Double-click it

Keep it.

4, customize the condition table

= =

In our example, we have our first access order query containing the condition table of the sales organization / customer group / material, while the second access order lookup is based only on the condition of the material. First, let's check the condition table to see if the two tables we need are in the system.

When creating the condition table [Vamp 05], you may need fields other than the existing fields in the standard system field directory. As an example, we assume that a business no longer needs a sales discount based on the sales organization / customer group / item; it decides that the discount should be based on the sales organization / customer group / ABC identifier. (ABC is a field of the material master record. Obviously, ABC is not a particularly good grouping field for discounts; there are other better grouping criteria in the system, such as material groups. However, if you just want to show you how to add new fields to the field directory, then the ABC identifier is a good choice for our examples. We then examine the field directory for the specific field ABC identifier field MAABC. If it is not in the field directory, it may be in the list of fields that are allowed to be added to the directory. We can see the list of allowed fields by selecting the down arrow or pressing F4 in the available properties. The requested field is in the list of available fields that can be added to the directory.

= =

TCode: Vmax 05, enter the condition table 904 (because the condition table is already available on IDES! )

Next

Use the following methods to find the sales organization, customer group, and item ABC tag fields

Click the page button above

Select the 'Sales Organization' field, and then click the' Select Field' 'button, and the sales organization field is selected into the' Selected Fields' 'from the field directory, as shown below:

Use the same method to select both the customer group and the ABC identifier field:

Create it

Next

Next

Click the Save button

Condition table 904 was created successfully!

5. Define the access order

Next

Next

Click 'Accesses''

Add 2 entries, and the condition tables are 904 and 4, respectively, as shown below:

6, assign access order Z007 to condition type Z007.

Next

Keep it.

Once the condition table is created successfully, you can no longer add key fields to it. The DEMO is as follows.

For example, enter the modification interface of the condition table 904.

Want to add field Catalog to the list of key fields

Select the field and double-click it, and the system reports an error:

8. Maintain the pricing process

Next, maintain the pricing process Z00001, as shown below

Look at the control data.

Now the control data is blank.

=

Select the New entry button and enter step 10: pricing condition type PR00. Because this is the pricing of the project, it should be necessary, so identify this condition type as a mandatory entry. Because there are likely to be items in the actual business that have nothing to do with pricing, I recommend assigning a request that identifies that this condition type is not required for items that have nothing to do with pricing. This is achieved by entering requirement 02 in the requirements column. You can also assign the account code ERL to the account code column so that the value of the condition type is posted to the revenue account.

If you don't want to add any other value, you may want to add the total value; add step 2, 40. In step 40, no condition type is assigned; in the description field, you can specify the description "Gross value". It is quite possible that the customer wants to print this value in his document; therefore, identify "X" in the print column. The total value will be used later, so assign the subtotal value "1" in the subtotal column.

=

After completing the above two steps, your pricing process is roughly shown in figure 4-20.

=

After the pricing process, you may want to add a surcharge to the total value and subtract the discount. It should be noted that when we give customers a discount, it is not based on the sum of the total value and the surcharge; it is directly based on the total value, and the surcharge is calculated later. For this reason, now let's go on to add the discount condition type.

Step 50 of creation assigns the newly created discount condition type Z007. Then create step 60 and assign another discount condition type, such as K005 (based on customer and material).

It is possible that there is a negotiated discount between your company's salesperson and the seller when creating a sales order; for this reason, you may need a manual discount condition, so assign the condition type RB00 to step 70. The customer may want to see all the discounts clearly, so identify all of these steps as related to printing. It is important to note that for each discount step, it should be indicated that the discount is calculated from that step; therefore, we enter 40 in the from column. Obviously, these three discounts are valid only if the items in the sales order are related to the price, so please identify the demand "002" in the demand column. The general ledger code ERS is then assigned to each condition type. Don't forget that the condition type RB00 is entered manually, and you should then identify the corresponding "manual" column during the pricing process. Finally, we specify a "Total Discount" value at step 100 (leaving a gap between 70 and 100 to facilitate further additions and changes later).

=

Now, your pricing type is roughly as shown in the following figure

=

Now you can decide whether the customer needs to pay additional fees, such as shipping costs. In step 110, the condition type KF00; is added. In step 120, the condition type HD00 is added. Because HD00 is a human condition type, it should be identified during the pricing process. The value represented by the transportation cost should be updated into subtotal field 4 and the subtotal column of the two conditional types should be assigned "004". Both accounts are specific benefit accounts posted to the general ledger and related to freight, so they are assigned the account code ERF.

Now, we need a net worth; therefore, create a new step 130 and assign the description "net value". The net worth should use the calculation type 002, subtotal 002; again, it should be related to printing.

=

At this point, the pricing process is roughly shown in the following figure:

=

Now we should consider all kinds of related taxes. In our example, we will use the conditional type MWST to represent our taxes. Add the condition type MWST to step 140; the condition type is entered manually, so identify the "manual" identifier. Because the tax is based on the delivery factory, in order to obtain the country in which the delivery was sent, I recommend using the demand check to see if the factory is maintained in the sales order. Therefore, the requirement "010" is assigned to step 140. The calculation class of MWST in the standard system is 16. Since the tax proceeds should be posted to a separate general ledger account, the account code MWS is assigned to step 140.

Now that the tax has been added to the net worth, the project can be summed up. Create step 150, enter the description "Total". Enter "A" in the subtotal column to indicate that its value is transferred to the credit price. The total value can also be calculated using class 004, which is net plus tax.

You may want to consider the cost price in the pricing process. If so, let's create step 160 and assign it the condition type VPRS; but don't forget to assign the Statistics identifier to this condition type. The value of VPRS is transferred to subtotal column "B", which represents the cost price. In the standard system, the demand for cost price is "004".

Now, it's time for us to think about profit. Add the description "Profit Margin" in step 170 and assign it only the computing class "011". This calculation class obtains the profit value by subtracting the cost price from the net value.

=

At this point, our pricing process looks roughly like the figure below.

We have completed the creation of the pricing process.

9, assign the pricing process and prepare for the test

1. Define customer pricing group

Next

Add a new entry: B (YiNing Pricing).

2. Increase the document pricing strategy.

Next

Add a new entry: D.

3. Maintain a new SO Type (ZNOR, copied from ZYOR) dedicated to this test.

4. Assign pricing strategy to Document Type YNOR

Next, add a new entry

5. Assign pricing strategy to facilitate follow-up testing.

Next, maintain new entries:

Keep it.

5. Ensure that the related values of Customer master data are well maintained.

'The Customer Group' field is maintained as 01; 'Cust.pric.proc.' The field is maintained as'B'.

6, material master data

The 'ABC Indicator' field is maintained as' A'.

Create a sales order to test the pricing strategy.

1 > create SO,Type ZNOR,C999/Z1/Z1

SO#9209.

2 > read the whole diary.

The system reported an error 'Pricing error: Mandatory condition PR00 is missing', because there is no Condition Record. Look at the specific analysis

Next

The pricing strategy found by the system is indeed Z00001, and the condition types under the name are shown here, but all are recorded unconditionally.

3 > maintain condition records

PR00: price 1500

Z007: 5% discount

K005: discount 5 RMB

RB00: 2% discount

KF00: freight 30 RMB

HD00: 5% freight

MWST: consumption tax 17%

VK11 maintains condition records.

PR00

Z007

K005

RB00, which needs to be entered manually, so VK11 reported an error:

You don't have to maintain condition records for it!

KF00, 30 RMB

HD00, manual input, no need to maintain condition records

MWST,17%

4 > go to see SO#9209 again

For SO to re-implement pricing, it can only be done through the following methods:

Execute option B

Next

Keep it.

5 > the question is, why is there no price information for the conditional type Z007? The analysis results are as follows:

VK11, to maintain the condition record of another combination of Z007

Re-implement the pricing of SO 9209, the price of Z007 still does not come out! As shown below:

What is the problem?

Check the configuration of access order Z007

Select 904, then double-click 'Fields',' to display the following interface

Keep it. (because this operation was not done in the previous configuration of the access order). Re-execute the pricing for SO#, and the following interface appears, and the price information of the conditional type Z007 is displayed:

Keep it.

Another problem, however, is that the MWST condition type never shows up.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

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.