Formula's and Calculation rules in Pricing.

Hi All,
Could anyone who is familiar with pricing please let me know if there is a mapping between the routines(Requirements/Formulas) that we have on the R/3 system and the CRM system, Requirements and Formulas.
We are trying to replicate the pricing procedures in the CRM 2007 system, but we are having a problem in replicating the formulas and requirements. Kindly help us, useful answers will be suitably rewarded.
Regards,
Thiru

Hi Das,
Schema is is set of rules means when ever you run the pay roll driver for eg: US driver RPCALCU0, in selection screen you have to mention the pay roll driver for US u000 in schema field.
when ever run the driver the set of rules executed and according the rules payroll is calculated.
OR
Each country payroll version supported by SAP has a program called the "payroll driver" that calculates payrolls. For example, in the U.S., the payroll driver is RPCALCU0, in Mexico it is HMXCALC0, and in Canada RPCALCK0. Each one is different, but they share a common core of functionality. The job of the payroll driver is to process payroll functions as specified in a payroll schema. These payroll functions each perform a specific job, for example - reading data from infotypes, calculating taxes, and processing wage types. Some functions process payroll rules. Rules are a collection of payroll operations. Each operation does a small unit of work, such as multiplying a wage typeu2019s number by a rate to get an amount.
Schemas are edited with transaction PE01
Schema rules PE02
Functions and operations are maintained with transaction PE04.
If anything require let me know
Regards
Sudheer

Similar Messages

Schema and calculation rules in Payroll

hi experts
what is schema ? what are the function of schema in payroll? How to set calculation rules for payroll? pls help in detail.
points will be awarded for useful answers.
Thanks

Hi Das,
Schema is is set of rules means when ever you run the pay roll driver for eg: US driver RPCALCU0, in selection screen you have to mention the pay roll driver for US u000 in schema field.
when ever run the driver the set of rules executed and according the rules payroll is calculated.
OR
Each country payroll version supported by SAP has a program called the "payroll driver" that calculates payrolls. For example, in the U.S., the payroll driver is RPCALCU0, in Mexico it is HMXCALC0, and in Canada RPCALCK0. Each one is different, but they share a common core of functionality. The job of the payroll driver is to process payroll functions as specified in a payroll schema. These payroll functions each perform a specific job, for example - reading data from infotypes, calculating taxes, and processing wage types. Some functions process payroll rules. Rules are a collection of payroll operations. Each operation does a small unit of work, such as multiplying a wage typeu2019s number by a rate to get an amount.
Schemas are edited with transaction PE01
Schema rules PE02
Functions and operations are maintained with transaction PE04.
If anything require let me know
Regards
Sudheer

OEE Report: KPI formulas and aggregation rules?

Hello,
is there documentation about the formulas and aggregation rules used in the OEE Report? Customers will only trust the KPIs in this report if they can verify them.
Formulas & Aggregation
How are the KPIs calculated?
How are the KPIs aggregated, if a work center or resource type is selected instead of a single resource?
Data & Variables
Which data is used? Where do the variables used in the formulas come from? E.g. which tables and columns or which SQL SELECT statements are used?
There is just very little information about the OEE Report in the online help or in the "SAP ME for Discrete Industries" document. And the MII "OEE Report Action", where obviously all the magic happens, is a black box.
Best Regards,
Martin

Hi Daniele,
Is Saichand correct in assuming that you have SUM setup in the BMM layer? If so, follow Saichand's recommendation.
If you are specifying the aggregation in the Answer Request itself, then try this.
Let's say this is your situation:
SELECT DIMENSION, MEASURE_1
FROM CRITERIA1
UNION ALL
SELECT DIMENSION, MEASURE_2
FROM CRITERIA2
UNION ALL
SELECT DIMENSION, MEASURE_3
FROM CRITERIA3
UNION ALL
SELECT DIMENSION, MEASURE_4
FROM CRITERIA4
Change it to this:
SELECT 'CRITERIA1' CRITERIA, DIMENSION, MEASURE_1 MEASURE
FROM CRITERIA1
UNION ALL
SELECT 'CRITERIA2' CRITERIA, DIMENSION, MEASURE_2 MEASURE
FROM CRITERIA2
UNION ALL
SELECT 'CRITERIA3' CRITERIA, DIMENSION, MEASURE_3 MEASURE
FROM CRITERIA3
UNION ALL
SELECT 'CRITERIA4' CRITERIA, DIMENSION, MEASURE_4 MEASURE
FROM CRITERIA4
Then in the combined criteria, add two new measures:
new_measnure1 = SUM(CASE WHEN CRITERIA in ('CRITIERA1','CRITIERA1') then MEASURE END
new_measnure2 = AVG(CASE WHEN CRITERIA in ('CRITIERA3','CRITIERA4') then MEASURE END
NOTE: The syntax for the new_measure* may need to reference the saw naming convention, ie. saw0 = CRITIERIA, saw1 = DIMENSION, saw2 = MEASURE.
That should work out for you.
Good luck and let me know if this helps.
-Joe

BEx Formula Use of 'Logical And' and Calculation for Gross Margin

HI Bex gurus.
Having an odd time with what should be a simple formula to handle the display of gross margin (GM). The goal here is to display GM% properly and the requirement is as follows
If GM <= 0 then 0.0
Else
If GM > 0 and Sell > 0 then ( ( sell - cost /sell ) * 100 )
Else
If GM >0 and Sell = 0 then 100
I am familiar with bex formulas and have referenced the help docs on booleans here -
Boolean Operators - SAP Business Explorer - SAP Library
But what is odd is that if I use a calculation or a CFK in the IF, THEN with a LOGICAL AND, the formula does not report correctly
If I put in a static value, like 77, the expected logic is followed. I have tried making sure have extra parentheses and changing the order of the statement, to no avail! I could use some extra brains on this puzzling matter, so you help is greatly appreciated and will award points!
Thanks
lee lewis
Here are the formulas in text and below screen shots. Wish could copy and past formulas to and from editor!
GM%77
( ( ( 'Order GM' >0 ) AND ( Order Sell > 0 ) ) == 1) * 77 + ( ( ( 'Order GM'> 0 ) AND ( Order Sell == 0 ) ) == 1) * 100 + ('Order GM' <= 0) *0.0
GM%
( ( ( 'Order GM' >0 ) AND ( Order Sell > 0 ) ) == 1) * 'REF GM%' + ( ( ( 'Order GM' > 0 ) AND ( Order Sell == 0 ) ) == 1) * 100 + ('Order GM' <= 0) *0.0
'REF GM%
(order sell - order cost /order sell ) * 100 )
GM%77
GM%

Shouldn't you change on of the brackets in your REF GM% ?
'REF GM%
(order sell - order cost /order sell ) * 100 )
I would put that as
'REF GM%
(order sell - order cost) /order sell * 100 )
Not sure what you mean with those red arrows... but in both cases you would be dividing by 0 (order sell = 0).

Business rules and calculation manager

Hi ,
Could anyone pls tell me the difference between the calculation manager and business rules?

Calculation manager is a web component that is designed to manage business rules from a web interface. It is enabled to build calculations also using a graphic interface, although this mode is more suitable for simple calculations than for complex ones. Calculation manager allows you also to use complex templates that you can customize with prompts in order to adapt them to each rule without being force to change the code. Basically it is an evolution of the essbase business rules macro function. Once a business rule is created it has to be deployed in order to be used with planning applications. The deploy activity copies the rule on the database, both in the calculation manager tables in and the planning tables.
Business rules are instead essbase artifacts. They aren't available any more from version 11.1.2.2 on.
In versions older than the 11.1.2.2 you were forced to use calculation manager for epma applications, while essbase business rules were used in classic applications. In terms of calculations there is no difference between the two technologies, they behave exactly in the same way. There is only a small difference in the prompts syntax, {} in calculation manager and [] in essbase business rules.
Although i find the calculation manager web editor quite slow and imprecise to use, I anyway advice to use it in order to make eventual release upgrades easier.

Difference between aggregation and calculation tab in BEx Query Designer

HI,
I am using BEx Query Designer for my report, for the key figures in the coloumn area i slected one numeric key figures, in the properties tab i found aggregation tab and calculation tab.
I need to sum up the total values for that particualar coloumn, when i used calculation tab i found to sum all the values for a particular coloumn, then what is the use the aggreagation tab?
I not able to used that Aggregation tab it is showing as a hidden fields...
can any one tell me whats the exact difference between these tabs and when we need to use which tab?
With Regards,
Thanesh Kumar.

Hi Thanesh Kumar,
I moved this thread from forum Data Warehousing to Business Explorer since it is a query related question (as SDN moderator).
I could explain to you the difference between these two tabs.
For "calculation" tab, it changes the display of result and does not change the calculation logic.
It means that, if this key figure is used further in formula, still the original number (without "calculation" tab setting) is used for further formula calculation.
For "aggregation" tab, it changes the real calculation logic.
The system takes the setting as the aggregation rule for records.
The most common aggregation rule is of course summation. If you set to e.g. Average here, the system does the
Average instead of summation when aggregating records. And the Average value will be taken for calculation
in further formulas or other calculations.
For "aggregation" tab, you could only use it for CKF (calculated key figure) or formula and you could not use it for
a basic key figure. That should be the reason why you see it greyed-out.
Regards,
Patricia

I followed the same procedure of reverse calculation from MRP pricing calcu

hi,
sap gurus,
i followed the same procedure of mrp calculation but
MRP Pricing Procedure:
Go through the following:
I will brief your requirement in short
MRP = 1012.5/-
VAT = (1012.5/1.125) = 900/-
so price before discount will be = 900/-
discount given at the rate of 10% = 100/-
Initial Price = 1000/-.
1. Create condition types as below:
ZR00 for price
Condition class = B
Calculation type = C
Plus/minus = A
ZSET for settlement (to knock off the effect of ZR00)
Condition class = A
Calculation type = C
Plus/minus = X
ZWST for tax
Condition class = A
Calculation type = H
Condition category = D
Plus/minus = X
Z007 for discount
Condition class = A
Calculation type = H
Plus/minus = A
ZDUM for net price
Condition class = A
Calculation type = A
Plus/minus = A
YWST for tax (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
YOO7 for discount (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
2. The following will be the pricing procedure configuration:
Step......No........Cond Type........... From.........to..........Man.........Req........Sta................Acc Key
10........0..............ZR00..................--..........--..........-...........-........---.................ZDU
20........0..............ZWST..................10............19...........----.............X............X...................
30........0.............text.......................10...........29...........---...........----.........X
40........0.............Z007.....................30...........39...........-----.............X............X
50........0..............text.....................30............49...........---...........-----.........X
60........0............ZSET.....................10...........19...........----............X............--.................ZDU
70........0............ZDUM....................50...........59...........----............X............---...............ERL
80........0............Y007.....................40...........49...........----.............X...........---...............ERS
90.......0..............YWST..................20...........29...........-----............X...........---................ZWS
ZDU - dummy account key for posting extra not required items.
ERL - account key for price
ERS - account key for discount
ZWS - account key for tax.
3. Condition records in VK11
Condition type----
Condition record.......
ZR00........................................1012.5.....................INR will be positive (1012.50 +)
ZSET.......................................100%...............................will be negative (100 -)
ZWST.......................................10%................................will be negative (10% -)
Z007.........................................12.5%.............................will be positive (12.50 +)
ZDUM.......................................100%..............................will be positive (100% +)
Y007.........................................100%.............................will be negative (100% -)
YWST.......................................100%.............................will be negative (100% -)
Condition records for Z007 & ZWST will be decided as per the conversion required. You will first have to manually calculate the amount for the condition type.
4. I create a sales order for single quantity for an item & the pricing will be as under:
ZR00 = 1012.5 (dummy account) - positive
ZSET = 1012.5- (dummy account) - negative will knock off effect of ZR00
ZWST = 112.5- (negative & no posting)
Z007 = 100 (positive & no posting)
ZDUM = 1012.5 (positive & posting)
Y007 = 100-(negative & posting)
YWST = 112.5 (positive & posting)
but its not throwing any condition records for ZWST and YWST
can any body help me
plz
regrds,
balaji.t

HI,
Plz try Routin for Vat formula.
i am worked on MRP pricing but in our case formula is different.
eg.: If i want to calculate VAT for B=1000 Rs. it is like
A=1000 * ((100/100 + (12.5- VAT 5)))
= 889
VAT (Value) = B - A = 1000-889 = 111 which is passed to GL account.
For that we developed one Routine with the help of ABAP and assign to Pricing Procedure.
Regards,
PM

Calculation schema under pricing procedure

in pricing procedure under calculation schema what is <b>Condition formula for alternative calculation type</b> and <b>Alternative formula for condition base value</b>
what is the use of these functions?

in this field u can creat ur own formuls to calculat base price or condition type value
this are called routine.
eg if u want to calculate the cond value on some logic the u can write ur logic in this routine and change the valuer of ur base price or Condution type
simple eq will be rounding up the values of condition type 17 is the routien u can use
hope this helps
Reward if useful

ABAP code for calculation rule in transaction M/08

Hi,
In M/08 transaction, we need to do this:
When maintaining a PO, the user manually creates a condition like this:
ZXXX Value (+10 %) positive value.
However, in order to get the belonging negative condition (for accounting purpose), we need to automatically create that when the one above has been created:
Automatic at the same time:
ZYYY Value (- 10 %) negative value.
In transaction M/08 you can enter ABAP code to each condition in the calculation rule. How can I program that ZYYY is created at the same time as ZXXX, when created for a PO ?
Any help is appreciated.

Hi Peter,
This calculations rules are know as routines you can create with them using T code VOFM and then go the menu option -
> Formula---->Condition value.Double click on that and you will get the ABAP code.
Here you can amend the existing one or can create the way you like your logic to move and assign it to M/08 T code.
Hope this will help you.
Thanks,
Birender Agnihotri

Search for member name in WebForms and Business Rules - 11.1.2.1

Hi,
Client has a hierarchy with two parents (Owned and Managed) within a dimension. The 'Managed' parent is no longer valid. Thus they want to eliminate it and move it's children under the 'Owned' member. However there could be ramifications in Business Rules and/or WebForms. Is there a way to search all Business Rules and WebForms for 'Managed' to see which Business Rules and/or WebForms would be affected?
Or is best way to extract all the WebForms and Business Rules to xml files via LCM and then write custom script to search the files? Not sure if this functionality is already there or not.
They are on 11.1.2.1

I don't think "Show Usage" picks up Business Rules that are in the Calculation Manger.
Also check the Member Formulas - easiest to do in the EAS (view the Outline, and the member formulas are displayed. Otherwise, in Planning, you would need to go into each member individually, and that would take forever). And if you're using Partitions or MRAs, you should check them, too.
I'm assuming you're doing all of this in a copy of the application, and not on a "live" app, right? So you can make the change and then validate the Business Rules and Outline, and the error messages will tell you where "Managed" was being used.
-Matt Varner

Condition formula for alternative calculation type

Hi gurus,
we need to create some condition formulas to be applied in our pricing procedure.
Do you know where to program them in the system and what additional settings are required?
Thanks and best regards,
VL

Hi Victor,
For your query, you can create new alternative calculation or alternative condition base values in T-COde VOFM with the help of an ABAP.
Go to VOFM T-CODE
Then Click on Formulas then condition value or condition base value.
You need to take Acces key from basis team to create a new calculation type for that number should start from 900 to 999.
Tell you Abaper to take the values from internal table XKOMV, XKOMK, KONDI, XKONP there are many internal tables are there, from that you will get respective conditon type values.
In internal table KBETR field contains condition record value & KWERT contains the calculated value.
Read wrt condition tyep and calculate according that and pass the value.
Try this, which will help you in resolving your query.
If satisfied close the thread.
Regards,
Nagesh

Shiment Cost Calculation Rules

Hi Gurus
Can you please provide me details of configuring Shipment Cost Calculation Rules?
Thank You

Hi Brajesh,
Is the following rules you are expecting?
Determining the Calculation Basis
Use
The origin of the data upon which a condition type is based during shipment costing determines the calculation basis. During shipment costing, the system determines the shipment cost items from the different calculation bases for the condition types of a pricing procedure. Shipment costing itself is carried out for each sub-item.
Prerequisites
You must maintain a suitable calculation base in the definition for the condition type in Customizing.
If you select handling units as the calculation basis, you must also specify the packaging material type so that only the relevant handling units are used for shipment cost calculation.
Features
The calculation bases are determined during shipment costing for a shipment cost item on the basis of the settings made in the condition type.
During pricing, the calculation base influences
The condition types to be considered for each sub-item
The information available for determination of the conditions
All condition bases contain information from the shipment header or shipment stage, as well as from the shipment cost item. This information includes service agents, geographical information (point of departure and destination) and shipping type, for example.
How the scale base types (gross weight, net weight and volume) are calculated
The following types of calculation bases are possible:
Deliveries
If condition types with this calculation base exist in the pricing procedure, then the system creates a shipment cost sub-item for every relevant delivery.
No information from the delivery items (such as materials) or the handling units is available.
The scale base types (gross weight, net weight, volume) refer to the corresponding information from the delivery headers.
Delivery items
If condition types with this calculation base exist in the pricing procedure, then the system creates shipment cost sub-items for every relevant delivery item.
Information from the delivery header and the relevant delivery item is available. There is no information from the handling units, however.
The scale base types (gross weight, net weight, volume) refer to the corresponding information from the delivery items.
Group of Handling Units
If condition types with this calculation base exist in the pricing procedure, then the system creates shipment cost sub-items for the sum of all identical handling units with the relevant packaging material type (also specified in the condition type).
There is no information from the deliveries or the delivery items available.
The scale base types (gross weight, net weight, volume) refer to the corresponding cumulated information from the relevant handling units.
Shipment cost item
If condition types with this calculation base exist in the pricing procedure, then the system creates exactly one shipment cost sub-item.
There is no information from the deliveries, the delivery items or the handling units.
The scale base types (gross weight, net weight, volume) refer to the corresponding information from the relevant delivery headers.
Per handling unit
This calculation basis corresponds to the calculation basis handling units, with the only difference that each handling unit is calculated individually. This calculation base is necessary for shipping packages, for example.
Handling unit including delivery item
If condition types with this calculation basis exist in the pricing procedure, then the system creates a shipment cost sub-item for every packaged delivery item and handling unit (per combination of delivery item and handling unit). Shipment costs are therefore calculated with content depending on the handling unit.
All of the information from the handling units and delivery items is available.
The scale basis types (gross weight, net weight, volume) refer to the gross weight of a handling unit per delivery item.
All
You can use this calculation base if, for example, you want to define a discount that applies to both delivery-related and handling unit-related shipment prices. A condition type with this calculation base can be used for every shipment cost sub-item.
Several calculation bases may be used within a shipment cost item. In performing a shipment comparison, for example, the calculation could be performed using two calculation bases. You could then compare the results. See also Shipment Comparisons.
For system load and clarity reasons, we recommend selecting a calculation base that is only as detailed as absolutely necessary. For example, if only the total weight and the transportation leg are relevant, the calculation base for shipment cost items is sufficient. However, you can still distribute the costs in greater detail. The cost distribution is independent of the calculation base. For example, you can calculate shipment costs using the calculation basis for shipment cost items and distribute the costs at delivery item level. The system weights the costs and distributes them accordingly.
When defining the condition tables in Customizing (Logistics Execution ® Transportation ® Shipment Costs ® Pricing ® Pricing Control ® Define price dependencies (condition tables), you should make sure that information is not available for every field - depending upon calculation base. If, for example, you select the field Incoterms for a condition table when condition types with the calculation basis Handling units exist in the pricing procedure, there can be no information on Incoterms for the corresponding sub-item. This means that no condition records will be found for this key. For further information on the role of the condition table in pricing, see Condition Tables.
Please let me know your thoughts.
Thanks nand Regards,
Satheesh Durgi
Edited by: Satheesh on Jan 25, 2011 1:01 PM

IT0071 Dynamic Action does not overwrite Pension Scheme Calculation Rule

I am trying to write a dynamic action to create IT0071 with default values for the Employee contribution (0%) and Employer contribution (4%). However when IT0071 is created the default values from the associated Pension Scheme Calculation Rule (4% and 8%) are not being overwritten by the dynamic action. Is there a way to get the dynamic action to override the Pension Scheme Calculation Rule values?
This is the dynamic action u2026
0171              BENGR     06     10     P     T001P-MOLGA='08'
0171              BENGR     06     15     P     PSPAR-MASSN='01'/X
0171              BENGR     06     20     P     PSPAR-MASSN='12'/X
0171              BENGR     06     25     P     P0171-BENGR<>NOBN
0171              BENGR     06     30     P     P0171-BSTAT<>NOBN
0171              BENGR     06     300     I     INS,0071,SS7,,(P0171-BEGDA),(P0171-ENDDA)
0171              BENGR     06     315     W     P0071-PCTEE='0.0000'
0171              BENGR     06     320     W     P0071-PCTER='4.0000'
Any help much appreciated.
Regards,
Janet

Hi Brian,
              In standard SAP physical sample planning requires sample drawing procedure.
Link: [http://help.sap.com/erp2005_ehp_05/helpdata/EN/2d/3521b6448c11d189420000e829fbbd/frameset.htm]
              And drawing procedure is advised with partial sample numbers.
Link: [http://help.sap.com/erp2005_ehp_05/helpdata/EN/2d/3521b6448c11d189420000e829fbbd/frameset.htm]
             Generally when we use partial sample numbers, we also use a drawing procedure. And in that scenario SAP describes the calculation as shown in
Link: [http://help.sap.com/erp2005_ehp_05/helpdata/EN/2d/3521b6448c11d189420000e829fbbd/frameset.htm]
             What you have done (partial samples for MICs and not having for others, all without drawing procedure) is not generally done. I think our observations in this context should be confirmed only if we try more of such examples.
Regards
Sm.

VAT calculation in Import pricing in Africa

Dear Experts,
I'm configuring a Import Pricing procedure for my African client where the Scenario is as mentioned.
1.Cost(Base Price) = 100
2.Insurance = 10
3.Freight =10
4.Customs duty = 10
5. IDF Value = 10
6. Vat = 14% on (12345 i.e on 140)
How can this scenario be mapped? As in Import pricing, Tax code is Zero. And there is no Tax procedure defined in SAP for Africa. If I create a Tax code with 14%, it calculates Tax on the Base price & not on the Total of "Step 1 to 5" as per my requirement.
I have checked a similar scenario for VAT calculation in Import pricing in Thailand. Can it be used? if so with what changes or what are the steps involved to meet the above requirement.
Kindly reply, if any one has worked earlier on this scenario.
Regards
Chitra
Edited by: Chitra H P on Jul 29, 2010 3:22 PM

Hi Chitra
You are aware I take it that Africa is continent and not a country?
You won't find anything in SAP for "Africa" in the same way that you won't find anything for Asia.
James

VAT calculation in Import pricing in Tanzania

Dear Experts,
I'm configuring a Import Pricing procedure for my African client(Country - Tanzania) where the Scenario is as mentioned.
1.Cost(Base Price) = 100
2.Insurance = 10
3.Freight =10
4.Customs duty = 10
5. IDF Value = 10
6. Vat = 14% on (12345 i.e on 140)
How can this scenario be mapped? As in Import pricing, Tax code is Zero. And there is no Tax procedure defined in SAP for Africa. If I create a Tax code with 14%, it calculates Tax on the Base price & not on the Total of "Step 1 to 5" as per my requirement.
I have checked a similar scenario for VAT calculation in Import pricing in Thailand. Can it be used? if so with what changes or what are the steps involved to meet the above requirement.
Kindly reply, if any one has worked earlier on this scenario.
Regards
Chitra

Hi
1.Cost(Base Price) = 100
2.Insurance = 10
3.Freight =10
4.Customs duty = 10
5. IDF Value = 10
6. Vat = 14% on (12345 i.e on 140)
As per the above this can be done in Tax procedure of Africa check the conditions type which you are using in TAX Procedure for all these condition type and go to the subtotal column and enter key 4 then the value of these conditions maintained there will added to BASB condition type inTax procedure which is nothing but gross and the you can have your VAT conditio type if you are using TAX INN procedure then maintain the vat % condition in FV11 or if you are using TAXINJ procedure then you ca create tax code in FTXP & IN that tax code you add VAT conditio as per your requirement. Hope this can helps you.
Regards

Formula's and Calculation rules in Pricing.

Similar Messages

Maybe you are looking for