pricing procedure.

[former_member949397]

Hi,

Please send me the total pricing procedure customization .

Thanks,

Rajendra.

[Former Member]

hi dear

There is five step for pricing procedure customization .

1) Define condition table .

2) Define Access Sequences .

3) Define Condition type .

4) Access Sequences link with Condition type .

5) Define and Assign Pricing Procedure and link with Condition Type.

Now i will tell u step by step in detail .

1) SPRO -

---

> Sales and Distribution -

---

>Basic Function -

---

>Pricing -

---

>Pricing Control -

---

>Define Condition Table .

( Here u will create pricing screen layout )

2) SPRO -

---

> Sales and Distribution -

---

>Basic Function -

---

>Pricing -

---

>Pricing Control -

---

> Define Access Sequences.

( Here u will create new Access Sequences.and put Z before whatever u create " don"t copy Access Sequences.create new " )

3) SPRO -

---

> Sales and Distribution -

---

>Basic Function -

---

>Pricing -

---

>Pricing Control -

---

> Define Condition Type .

(Here u will copy the Condition Type what ever u require Ex--if u require for pricing copy PR00 " like this what ever u want and then put Z before and change with new and then link with newly create Access Sequences )

4) SPRO -

---

> Sales and Distribution -

---

>Basic Function -

---

>Pricing -

---

>Pricing Control -

---

> Define and Assign Pricing Procedure -

---

>Maintain pricing Procedure

( Here u will copy sap define pricing procedure "RVA001" and then copy that and change by putting Z before . then press enter and one window pop up click on "copy to all " press 3 , 4 time enter . then select new pricing procedure and control data then u find out condition types there u should change "PR00" and put your newly created condition type then save and come out )

5) SPRO -

---

> Sales and Distribution -

---

>Basic Function -

---

>Pricing -

---

>Pricing Control -

---

>Define Pricing Procedure Determination .

( Here u will change your newly created Pricing Procedure with old Pricing Procedure (RVA001) and newly created Condition Type with old Condition Type ( PR00 ) then save and come out )

I think this will help u out dear

rohit kandwal

rohitrrr79@rediffmail.com

Edited by: rohit kandwal on Mar 7, 2008 12:44 PM

[Former Member]

Check the Pricing Procedure:

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.

Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.

Regards,

Rajesh Banka

[Former Member]

go to vok0 tran

go to envarment create condition table bet 501 to 999

select fields from fiels catlog see 555 select fiels customer material

generate

then create access seq (v/07) zr00

& assign cond table 555 to the same

then create condition type(v/06)

copy any present condition type like pr00 name it zr00

d\ouble click on it n assiegn access seq to the same

then create pricing pro v/08 zpp

in control

assign condition type zr00

after that determine p p in vok0

in menu path pricing procedure

determine p p

put u sales org- dist channel-division- dopp-cupp-pricing proc-cond type

xxxx xx xx a 1 zpp zr00

maintain condition rec

vk11

put cond type zr00

maintain rec

maintain cutomer p p in customer master sales view

put sales order & check

rewards points if help ful

regards

nitin

[Former Member]

Hi, Kindly check the following PDF on Pricing procedure: http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBFPR/SDBFPR.pdf You can also check, http://help.sap.com/saphelp_erp2005/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm

hope this helps

Regards

Subhajeet.

[Former Member]

Hi,

Pricing procedure is key element in the SD point of view

based on the pricing procedure the structure of the product price will takes place.

Pricing procedure is defined with set of condition types which are arranged in a sequence manner.

1. In SAP SD first and foremost thing is define the condition table, here you need to select the fields from the field ctalog,

based on this fields only you are going to maintain condition record.

T.Code V/03

2. Condition type is one of the pricing element like discount,Frieght,Price,Rebate,tax ...etc.

3. Access sequence is a searching activity, we will put condition tables in the access sequence.Access sequence will search from specif to general.

access sequence we need to assign to the condition type.

Ex; if you have two tables in access sequence one table is cintaining field Material second one having fields Material and Customer, in this situation access sequence will search condition record first for second table if not avail it will go for second table search.

T.code V/07

4.Pricing procedure will be determined at sales order based on these combinations Sales area Customer pricing procedureDocument pricing procedure+pricing procedure

T.code OVKK

Finally the logic involved in the pricing procedure is when you create sales order the pricing procedure will determine based on the Sales areaCustomerMaterial, after determining the procedure the system will find what are condition types available in that procedure then it will find the what are the access sequences those condition types are having, then based on the access sequences system will search the condition records, finlly system will fetch the data according to access sequence it will put in the Sales order.

I hope it will help you

regards,

kishore.

[Former Member]

Pricing Procedure

In SD, Pricing Procedure is determined based on

Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure (T.Code: OVKK).

Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows:

IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

[former_member949397]

Hi,

Please send me the how to do customiozation for rebate.

Thanks,

Rajendra.

[Former Member]

Hi Rajendra,

Rebates Processs in SAP is divided into three components

1) Configuring Rebates

2) Setting Up Rebates

3) Managing rebate agreeeements and payments

Pre-requsiistes- Check the following:

1.The payer partner needs toi have the rebate field checked in the customer master on the sales area-billing doc tab.

2.The Billing type must be marked as relevant for rebates.

3.The Sales Organisation must be marked as relevant for rebates.

Condition Technique :

Rebates, use the condition technique, but distinguish themselves from pricing in applying to transactions over time, versus on a transaction basis. Rebates have their wn field catalog and their own condition table naming convention.So you could have two condition table "001" one for pricing and one for rebates, which could have different key fields. You need to use the technical names A001 For pricing and KOTe001 for rebates when you use the query type using transaction SE 16..

Use create access sequence (AS). Enter 1 in field category for rebate specific. AS after going thru the right path of maintaining access sequence for rebates.

The big difference between the rebate and the pricing access sequence is that there is no exclsuion flag available for rebate related AS. This means multiple tables for an access sequence can be aplied at the same time.

Rebate related condition types are identified by codnition class -C.

After defining and creating condition types for rebated include them in the pricing proceedure. The requirement should be 24 here which implies that the accruals are calculated on the basis of invoice/bill.

The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also, remove the requiremnt 24, if u want to see reabtes at order time.

Now payment of rebates:

Payments can be maunal or in full settlement. When you do manual payments, it defines how much can be paid out during a partial settlemetn. You use partial settlement only when rebate agreement is defined for a full year but the paoyouts are supposed to happen on a monthly, quarterly or anyother specified period.

These accurals are based on sales volume and when they are posted billing is created int eh follwoing manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is created

Customer account/ is debited and

Accrual provision account is credited.

Hope this is clear.

Reward if helpful.

Thanks,

Praveen