Requirement, alt conditiion base value,alt .caluculatin type

Hai,
Suppose a business requirment in pricing is to develop a routine.How can i come to a decision that i need to write a routine in
"REQUIREMENT"
"ALT CAL TYPE"
"ALT CONDITION BASE VALUE" fields.
Plz suggest me;

hi,
Hope this can help you,
Pricing requirements are typically used to define when an access should be made in pricing. They
can be assigned to a condition type in a pricing procedure or to an individual access in an access
sequence. An access will only be made if the requirement is met. Using requirements can improve
performance by eliminating unnecessary accesses to the database.
When pricing is carried out for a sales document, the system processes the pricing procedure one step
at a time. For example, the user may have listed condition type PR00 first to determine the price. If
a requirement has been assigned to PR00 in the pricing procedure, the system will check to see if it is
met. If it is met, the system continues to look for prices using the assigned access sequence. If it is
not met, the system skips that condition type and goes to the next level of the pricing procedure. The
same holds true for the individual levels of the access sequence. If a requirement is assigned, the
access is only made if the requirement is met.
Condition base value formulas can be used to influence the condition basis to which the pricing condition rate will be applied. In standard pricing, the system will apply the condition rate to the quantity in the sales document. For example, the price determined by the system is $45 per case for Product A. 100 cases of Product A have been ordered. The system would then multiply $45 times the number of cases of Product A ordered. Using a condition base value formula, it is possible to alter the condition base, in our example 100, prior to the calculation taking place. A condition base value formula is commonly used to determine the base for distributing header discounts / surcharges to the sales document line items. A condition base value formula is assigned to a condition type in the pricing procedure.
Condition value formulas are available to influence the condition value that is displayed for a particular condition type or value line in the pricing procedure. In standard pricing, the system will calculate the condition value by multiplying the condition rate by the quantity. For example, 100 cases times $45 per case equals $4,500. Using a condition value formula, it is possible to alter the condition value, in our example $4,500. Condition value formulas can also be used to compute values that should appear as value lines in the pricing procedure. As an example, standard delivered condition value formulas can be used to compute profit margin and item net value. A condition value formula is assigned to a condition type in the pricing procedure.
Regards,
Shekhar

Similar Messages

Alt cal type, alt cond base value

Hi SAP Gurrus,
If the interviewer asks, what is alt calc type, alt cond base value , what i have to tell
Plz tell the def and with small example for
1.alt calc type ,
2. alt cond base value ,
3. Subtotal.
which is in Pricing procedure.
2. What is Replenishment Lead time.

Hello,
What prashant told in that i will add something like.
alt calc type u acn give example like rutine no 11 which is used for calculating profit magin.
base cal type u can give example is 12 or 13 that we use to cal fright. like we cal frieght on wt basis we take base cal type as wt from mmr.
some detailed info as follows i hope this will help u lot for understanding the same
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.
Replenishment Lead time
Time needed for production & procurment of item.
like for ex u mainatin rlt as 10 days when u put sales order u do avail.check if stock is not there then system cosider RLT for giving confirmed delivery date in future.
u can maintain it in mmr or even in sales doc type.
Regards
nitin

CONDITION BASE VALUE / ALT CALCULATION TYPE Pricing

Dear All,
I have a scenario where in I want the condition base value for calculating the value for a condition type to be based on
Gross weight - Net weight value of a material.
Is it possible and if yse how do I acheive the same.
Deepak

Deepak,
Alternative Calculation Type:
Normally if you want to calculate a value you have to use a calculation type for determinating the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based.
Here what happens is suppose if you define Your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10 % in the condition record. Then this percentage is taken as the calculation type and the condition value is determined.
In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition.
Alternative Condition Base value :
If you have to calculate any value then you have to have a base value for it. For ex if you want to calculate the discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the condition value of the base price of the material to calculate the value.
Now you don't want to take the base value and take other values as base value which are derived on some formulae. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type.
Reward poitns if u finds this helpful....
Regds
MM

Tax Requirement - with different base value

Hi,
We have material (Service) for which the tax calculation should be as follows:
If the quantity is 6, say the per unit value is 100 $. Then the first 4 will have tax calculation of 15 % (GST) on 100 $ and the rest of 2 will have 60 % of total value = 60 (X). And the tax value will be 15 % 0n X = 9.
So the total value will be - 100 (Basic Price) + 15 (tax for qty 4) + 9 (for qty - 2) = 124 $.
Is it possible in standard ? Also, the above is for Newzealand government , is there any specific requirement for that ?
Please Help !
Regards

Hi Chidambaram,
Can you please give me more details on how we achieve this requirement.
Any document on this would be more helpful to me. Removed by Moderator
Please help !!!
Regards
Edited by: Lakshmipathi on Sep 3, 2010 7:02 PM
Please dont deviate the forum rules by asking to share any SAP related information to personal mail through this forum

Pricing - Requirment / calculation type / base value

Dear Friends,
Thnaks for the support and guidance provided by you for my previous posts
In Pricing Procedure we give Requirment, Calculation type and Alternative formula for condition base value, I would like to know where do we exctly define all this?
Or are they standard? If standards where we can see how they works?
Regards
Vishal

Hi,
go through the below Examples for better understanding ..
Example: 1
Condition Type: PR00
Requirement 2 Item with Pricing
Purpose:
This is an example of a pricing requirement. This requirement is met if the document item category is relevant for pricing and no previous condition in the pricing procedure has set the condition exclusion flag. This requirement can be assigned to condition types in the pricing procedure to avoid unnecessary accesses to the database when an item is not relevant for pricing or a condition exclusion indicator has been set.
Example: 2
Condition Type: Net value
Calculation Type: 2 Net value
Purpose:
This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure.
Formula '2' sets the value equal to net value that has been calculated so far for the item in the pricing procedure. It contains the amount excluding taxes.
Example: 3
Condition Type: R100
Alt.Condition Base Value: 28 (100% Discount)
Purpose:
This is an example of a condition base value formula. A condition base value formula can be used to influence the basis the system uses when computing a pricing value. A condition base formula is assigned to a condition type in the pricing procedure.
Formula '28' sets the rate of the condition to a 100% discount. This formula was delivered with condition type R100 to support free goods functionality.
Reward if it is useful,
Chandramohan

Alternate calculation type and alternate base value

hi all,
please guide me the concept of alternate calculation type and alternate base value

Hi,
ALTERNATE CALCULATION TYPE:
      This function allows you use a formula as an alternative in finding the value of the condition type,
instead of standard condition technique. this can be used to calculate complex tax structures.
ALTERNATE CONDITION BASE VALUE:
      The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
And Refer this link.
http://sapsdforum.com/2007/09/05/pricing-alternate-calculation-type-alt-condition-base-value-and-requirements/
Hope it helps you,
Regards,
Ravindra.

Alternative calculation type and alternative condition base value

In pricing procedure what is the difference between alternative calculation type and alternative condition base value?Kindly help

Hi,
Please check the forum before you post your questions as this question was answered a number of times earlier.
Please check the below link which discusses in detail regarding the same.
[Alt Cal Type and Cond Base Value|Alternative calculation type and alterantive condition base value in pricin;
Regards,
Phani Prasad

Condition Type JSRT not picking Condition Base Value in Pricing Procedure

Hi Friends,
In a procedure System is not picking condition base value for condition type JSRT. I have checked the tax procedure and found alternative Cal Type is 17 and is working fine for Domestic vendors.
Friends i need your help in sorting out this issue. Pls suggest what I can check in order to sort out this issue.
Rgds, Krishan Raheja

Hello!
In TAXINN the base value for the condition JSRT is picked up from step 100.
I suggest that you change the "From" value to 100 instead of whatever you may be using
Then test the transaction once again.This will not affect your normal service tax calculation either. So please make this change & try using S1 for planned delivery cost.
Hope this helps !
Cheers!
Plauto
Edited by: Plauto Abreu on Feb 11, 2011 9:03 PM

Base value in tax code

from where does the system pick the base value for condition type BSAB in tax code as we are not maintaining any condition records.

Hi,
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries.
The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
While configuring in calculation procedure v wil tel the system to calculate tax on base amount by giving the from level and to level so it will calculate from there directly depending on the levels v mention.

Abt pricing (Alt Cal & Base cal type

Hi gurus,
I want to know more abt alt cal type & base cal type.
I know that we use base cal type for frieght cond.
Want to know more abt the same.
Thanks in advance
regards
nitin

The alternate base value is used as the calculation basis only, while the alternate calculation is used to modify the final value.
*For example *
imagine you have a condition type ZZ01, with a condition record maintained (master data) for $100. Now, condition ZZ02 also exists lower in the schema, but with a rate of 10%. The standard calculation would result in a final value of $110.
The alternate base value could say, "don't use $100 as the basis -- use the original price PR00 only, which was $90." Then, the final value would be $100 + (10% of $90) = $109.
The alternate calculation routine says, "ignore the 10% altogether. Instead, use an externally calculated 20%." Then, you end up with a final value of $100 + (20% of $100) = $120.
Put them both together, and you could end up with $100 + (20% of $90) = $118.
Now once again,
Alternative Calculation Type
Normally if you want to calculate a value you have to use a calculation type for determinating the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based.
Here what happens is suppose if you define Your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10 % in the condition record. Then this percentage is taken as the calculation type and the condition value is determined.
In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition.
Base calc. type:
I think it is available in the V/06 screen for each condition type. This is the standard calc. type followed for any condition type.
Hope it is useful
Reward points if helpful...

Alternative calculaton type/ condition base value/requirement

Hi
What is the role of alternative calculaton type, condition base value,requirement in pricing procedure.?
2) Where do we define value for alternative condition base value and alternative calculation type so that system picks up different value,when the value for alternative condition base value and alternative calculation type is mention in pricing procedure.

Dear,
*Alternative Calculation Type:*
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
Alternative condition base value
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
Example
An absolute header discount is, for example, distributed in the standard system according to the cumulative value of the items.
If the system distributes the absolute header discount according to volume based on the Alternative formula for condition base value , a header discount of $30 results in the following discounts:
Item Value Volume .
1 $1000 2 cbm
2 $500 4 cbm
Stand. disc. Volume disc.(With Formula)
$20 $10
$10 $20
Condition formula for alternative calculation type
Alternative formula to the formula in the standard system that determines a condition.
Requirement
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
with regards

Requirement type, alternative calculation type and alternative base value?

Hi guys pls can any body experts in pricing
Can u pls explain requirement type, alternative calculation type and alternative base value?
Not theory Any of Ur real time experience

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.
Regards
AK

Change the Condition base value in a Condition type.

Hi Experts,
I have a problem because I need to change the condition base value for a condition type. This condition base is calculated as a result of other condition types in the list of pricing Elements. I would need to change the base in order to solve the problem.
Thank you and best regards.

Hi Alberto
if i get it correctly , this is your scenario
condition 1--- price x
condition 1--- price Y
condition 1--- price z
now you want a fourth conddition with base value total of the above 3
if so , you maybe define all the above 3 as statistical ,
in another row , create a total of the above 3,
assign a sub total this ,
create new conditon type and in its alt base value , give the formalue for the sub total
for eg 5 for sub toal 1, 6 for sub total 2
and then you would get the right base value
Hope this helps
Thanks
Akasha

Data type of the base attribute or the base value does not match...

...the assigned expression.
Hello all,
I always get the Error
+<ERROR+
TEXT="'DWH.CUB_REGISTRATIONS_AW.REGISTRATIONS': XOQ-02517: Der Datentyp des Basisattributs oder der Basisgröße stimmt nicht mit dem zugeordneten Ausdruck überein.
XOQ-01400: Ungültige Metadatenobjekte"/>
The English message must be something like this:
The data type of the base attribute or the base value does not match the assigned expression.
when I run my mapping. The attribute REGISTRATIONS is NUMERIC (12,2) in the Cube and I map a NUMERIC(12,2) constant in it.
I use a simple OWB-Mapping for loading, but I don't understand why it doesn't function. Other mappings where the attributes are out of a
table I put in a cube are running well.
I tried different things, but nothing fixed my problem. Any idea ?
Thanks a lot for help
Michael

Technically this is a 'warning' from the server, not an 'error'. This means that the change you made should have been submitted, but you get an warning message on the client. AWM would suppress this warning, but evidently OWB does not. Can you switch to use AWM?
Here is the definition of the warning along with 'cause' and 'action' sections. (Unfortunately these sections are not translated into German for some reason.)
>
02517, 0, "The data type \"%(1)s\" of the base attribute or base measure is different from the mapped expression \"%(2)s\"."
// *Cause: Either the base attribute or base measure with the mapped expression was set to an inconsistent data type, or it was mapped to an expression of a different data type from its fixed data type.
// *Action: When changing a mapped expression for a base attribute or base measure, ensure that the expression has the same data type; otherwise, set the data type of the base attribute or base measure to NULL first. When a base attribute or a base measure has an existing mapped expression, do not set it to a different data type.
>
It is probably safe to ignore this warning, but if you can post the relevant XML for the cube, then will probably be able to spot the problem. I assume that REGISTRATIONS is a measure in the cube CUB_REGISTRATIONS_AW, so this is what you can look for in the XML:
(1) The definition of the base measure along with the datatype. It should be something like this
<Measure>
<BaseMeasure
 SQLDataType="NUMBER(12,2)"
 ETMeasureColumnName="REGISTRATIONS"
 Name="REGISTRATIONS">(2) The mapping info for the measure, which should looks something like this:
<MeasureMap
Name="REGISTRATIONS"
Expression="...">
<Measure Name="REGISTRATIONS"/>
</MeasureMap>I don't know if you can get the XML directly from OWB. If not, then DBMS_CUBE.EXPORT_XML should work (assuming you are in 11.2). You could also attach AWM and save the cube to an XML template.

Different base value reference steps for same condition type

Dear Gurus
I have a scenario where I have single pricing procedure for normal sale and Intercompany billing.
Condition type GRWR should take the base value from step 350 in standard scenario
But in Inter company billing it should take the base value from a different step.
Want to check the possible way to determine these.
Regards,
Neeraj Srivastava

In the pricing procedure, in the step that you're interested in intercompany billing put in the subtotal field the indicator "carry over value to KOMP-KZWI". Make sure that the KOMP-KZWI field that you'll choose is not used in any other step.
Then with the help of an ABAPer you should maintain a routine (Tc VOFM -> Formulas -> condition base value) that in the case of intercompany billing (if billing-type is XXX ... etc) will take the KOMP-KZWI* value that you chose previously.
Then back in the pricing procedure, assign your new routine in the field "Alternative formula for condition base value" (BasType).
Agis

Requirement, alt conditiion base value,alt .caluculatin type

Similar Messages

Maybe you are looking for