Release Strategy-Pricing

When we enter PR00 in the condition record VK11 , one of the options that we see is Material with Release strategy. What is this release strategy?

Meaning of "FORM KOBED_002" and "FORM KOBEV_002

Hi Jennifer...Here's is the Functional Perspective of your question.

FORM KOBED and FORM KOBEV are just the two FORMs under which the formula is encapsulated for picking the price which I have already explained in http://sapdude-sapsd.blogspot.com/2007/06/pricing-procedure-under-requiremnt.html

Whenever a coding is done or a formula is written we do it by using FORMS. The purpose of encapsulating the code under a FORM is because we should have an option to call the same Form in the some other requirement. So instead of writing the program all over again we justcall the Form with its name.
KOBED_002 and KOBEV_002 are just the name given under which the Formula is written.
Being a Functional consultant we do not have to worry about the coding part but these FORMand ENDFORM contains the relevant formulaes for the specific business requirement.
In the above case FORM KOBED_002 the formula written under it means that system would first check whether the item category attached for an item in that condition item number in SO is relevant for pricing or not.

Do not bother about FORM KOBEV_002 as it does not holdany meaning particularly for this program.
Do revert for further clarifications.

Alternative Calcultation Type

Hi Burning Soul : Here's the explanation to AltCalType

Alternative Calculation Type, Requirement, Cond Base values are used in Pricing to meet the not so common business requirement. The normal prcing requirements can be mapped without using them .

Coming to the AltCalType, we have to use routines which stores the business logic and can be used against the relevant condition type as per the business requirment. The routines , in other words are the formulas that are defined in Tcode- VOFM by the abapers based on the logic given by the functional consultants.

Remember: The routine is applied against a condition type in the pricing procedure

Some of the standard Altcaltype routines are as below

Routine /Formula :- 15

A company has defined minimum prices for materials.
When a material is sold, it should not be sold for a price below the predefined minimum price. When pricing is done for a sales document line item, if the net price of the item falls below the minimum, the system should automatically compute a surcharge to bring the price up to the minimum price. To accomplish this, the user would define the minimum prices using the condition type PMIN. PMIN would be defined in the pricing procedure and condition value formula '15' would be assigned. Using the formula, the system compares the minimum price with the net price calculated to that point in the pricing procedure. If the minimum price is not met, the system computes the necessary surcharge and assigns it to the PMIN condition line.

Routine /Formula :- 48

Formula '48' was delivered to ensure that the down payment amount the user offsets in a billing document does not exceed the actual down payment value. Condition value formula '48' is assigned to the condition type in the pricing procedure representing down payments (R/3 delivered condition type AZWR).

Let me know for any further clarifications.

Note: All, please do not copy and paste my posts into your blogs to avoid blog frauds and legal actions.

Interview Question (Pricing)

Guyz. ..Here are some interesting pricing questions often asked in interviews.

1. What is condition supplement and why is it used , also how is it configured.

2. If there are two customers, for one customer 10 condition types are mandatory and for the other only two. How would we configure this if we have to map it with one pricing procedure.

3. Order types, why do we need to create our order types and not use the standard ones during implementation.

4. What is group conditions used in condition type/s

5. What is the pricing header and item table name

If you know the answers post them through the form of comments.

Standard Pricing Procedure

Following is the link to the Standard Pricing Procedure used in SAP, just check out if you have worked on each condition type and do you understand the formulas attached to each condition type.

http://spreadsheets.google.com/pub?key=phixAHJ6iFNOBn91F1vkFHg .

In addition to this we tend to lack concept and fall apart when we go into detail. Do we really know how pricing works: Let us discuss the following points, each one of them, just to know do we understand the concept used behind pricing in SAP:

1 What is the concept behind condition technique, why do we have a determination concept, what benefit do we get using this concept?

2 Why do we determine pricing be assigning it to the Sales Area , OR type and CPP

3 Can one pricing procedure control the pricing of an entire enterprise , if yes/no why ?

These are just the basic conceptual questions which many of us might be knowing, but whats more important here is how we express , do we know how to express what we know , if u do pl let all of us know through your comments.

Routine "2" : Requiremnt colum in Pricing Procedure

Hey Deepak...Here's your answer

Requirement: Denoted by numbers and maintained in VOFM, this is a condition required for a particular condition type.
E.g. PR00: req. 2 i.e. item relevant for pricing or not.
* Pricing is turned on in item category configuration

FORM KOBED_002.
SY-SUBRC = 4.
IF KOMP-KPOSN NE 0 (KOMP- Pricing Communication Item KPOSN -Condition item no. in SO)
CHECK: KOMP-PRSFD CA 'BX'. (PRSFD - PRSFD Carry out pricing)
CHECK: KOMP-KZNEP = SPACE. (KZNEP -Condition exclusion indicator)
ENDIF
SY-SUBRC = 0.
ENDFORM.
* Prestep
FORM KOBEV_002.
SY-SUBRC = 0.
ENDFORM.
For techi’s above program is self explanatory
Explanation:
The above routine “2” is included under Req column in Pricing Procedure. It means that system would first check whether the item category attached for an item in that condition item number in SO is relevant for pricing or not.
If the Item category is pricing relevant only then system will go to VK11 and fetch the price. On the contrary if req. column does not contain 2 as routine against a condition type system will not consider this parameter and would directly jump to VK11.
This routine improves system performance
Note: If an item category marked as NOT relevant for pricing system will not fetch price in the Sales order even if the condition records for the condition types are maintained.

Please let me know in the form of comments should you have any query.