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

Similar Messages

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

HR schema and rule function overview

Hello, is there any HR schema and rule function overview there ? I mean for example function VARST, ADDDB, HRS, PCY etc., which are under PE01 and PE02 available to use.
Thanks.

Schemas can be viewed and modified through pe01. Schemas use functions and Personnel Calculation Rules (PCR).
PCRs can be viewed and modified through pe02. Time Evaluation PCRs use operations such as HRS, VARST, ADDDB and OUTWP. Payroll Calculation PCRs use operations such as RTE, NUM, AMT, VARGB, ADDWT and OUTWP.
Functions and Operations can be viewed through pe04, along with their parameters.
Documentation on Functions and Operations can be viewed either in the schema or rule by selecting the object + F1 (or the ? icon), or through pe04.

Simultaneous development on PY schemes and rules

Dear Colleagues,
I'm working for a big company in the IT department and I'm responsible for the process payroll. We have a lot of developers, who are working on payroll schemes and rules simultaneously for different demands and different go live dates.
The problem we are faced with is, that after go live of a demand or a project, in which a scheme or a calculation rule is included, sometimes an error occurs because of transported statements in schemes or rules, which are not already finished within another demand.
Example:
Project A and Project B is working on the same payroll scheme. Project A has been finished and went live (including the statements of project B), but project B has not finished the development and some new calculation rules or operations are missing on the productive system. Because of this, an error occurs when running the payroll.
Question:
Is it possible to deal with payroll schemes and rules similar like workbench objects? That means, is there any functionality availiable to block those objects for editing, when it is already included in a transport request?
Thanks in advance for any idea or help!
Kindly Regards
Adem Demir

No problem. At some point you will have taken a copy of iteration one's project and added that to CVS as iteration two. From that point onwards your iteration two index would be the same as iteration one. If you added keywords to it, it would be the index to use for iteration two. The index for iteration one would be unaffected as it would still be in CVS in a separate project.
Things only get a little more complicated if you are working on two different iterations of the project at the same time. If this is the case it may be better to finish one iteration first and copy the <projectname>.hhk file into the other project. Provided you haven't rrenamed or deleted any topics all references will be fine.

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.

Help on Time type 0903, Identifying Schema and Rule configuration?

Can you please help me with the following:
1. What is time type 0903?
2. How to identify schema and rule configuration?
3. How do I identify the number of employees affected in case I have to make a configuration change?
Thanks

Hello,
1) Time type is identified according to what purpose it is used. Check table T555A for details on why it is used in your configuration.
2) There is no configuration in schema and rule. Schema and rules has the programs in them.
3)What configuration changes you are planning to do? Depending on this we can then try to identify who is affected.
Hope this answers your questions.
Let me know if you need more info on how to configure time management and write schema and rules.

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.

What are schemas and rules in HR?How it will use in HR?

Hi HR Proff,
What are schemas and rules in HR?How it will use in HR?
Give some documentation on this?
Early reply is highely appriciable.
Regards,
Chow.

Refer this link -
http://www.sd-solutions.com/documents/SDS_Payroll_Schemas.html
Regards,
Amit

Undigesting XML with Schema and Rules

We currently use a Digester with schema and rules files to digest an input XML and automatically build our Java objects. What I'd like to know is if there is a REVERSE process? Is there any class or utility that can take those Java objects and build an XML file?
Thanks,
Rich

Ask Microsoft why IE6 does not validate. Normally server-side developers do
not rely on a browser to validate XML against schema or DTD but validate XML
on the server. The same is true for XSLT transformations...
"Benoit Degreve" <[email protected]> wrote in message
news:aqnihv$l75$[email protected]..
Hi everybody,
I'm trying to validate an XML file with a schema but it doesn't seem to
work.
I open the XML file (that doesn't match the rules that are in the schema)
with a IE6, and there is no errors...
I have the same problem with a DTD (its reference is in the XML file like
shown in my book)...
Does the validation process have to be done by a specific application ?For
the schema ? For the DTD ? In other words, does IE6 make the validation
process automatically ?
Could someone help me ?

Need help in Time Evaluation schema and rules

Hi Gurus,
1)Can anyone help me with Time Evaluation schemas and rules with some example?
2)Where can I find good documentation on Time Schemas and rules?
3)what are the practical Interview questions I can expect on Time management?
I would really appreciate If you could guide me on this..
Thanks
Avy

https://forums.sdn.sap.com/click.jspa?searchID=15025266&messageID=5372783
https://forums.sdn.sap.com/click.jspa?searchID=15025266&messageID=5903057

Schemas and PCRs

hi, experts.
i need help in learning schemas and writing PCRs. please suggest me any book or send me any document that will help.
regards,
madhu

hai..
How to read rules and Schemas
1.Structure of relationship in Rules and Schemas:
a)Schemas consist of Functions and Sub-schemas
b)Some functions have the rules attached to it as one of its parameter
c)Rules consist of a set of operations to perform some actions
d)Operations and Functions are the executable components
As per the diagram Set of Operations make a Rule which in turn attached to some functions and those functions embedded in Schemas or Sub-schemas (Inside the main schemas) to decide the flow of the payroll program.
Structure of a Schema:
Func:
This column is used to give a function name.
Par1, Par2, Par3, Par4:
1. Function has maximum four parameters.
2. The function can have zero to four parameters as per the definition of the function.
3. Pressing F4 we can get the list of all the values which can be used as parameters.
4. For some functions in the first parameter is the name of the rule created.
5. These parameter values are predefined the function is being created.
D:
1. This column is used to comment and uncomment a function.
2. If (*) is being put then the line is commented and will not be executed in Payroll processing.
3. If nothing is given then the line would be executable.
Desc
1. In this column description for the function is being used.
Functions:
Functions are used for;
Performing some payroll computations (E.g. INEPF function calculates the PF amount of an employee during payroll run)
Calling rules (E.g. P0045 function calls a rule INLN to compute the loan details of a personnel number).
Getting data from Infotypes (E.g. P0581 will get the data from Infotype-581 for payroll processing).
For some decisions. (E.g. IF & ENDIF function is used to execute as per the true and false decisions) etc.
Rules:
Rules are used for holding a set of operations for a particular requirement to be accomplished.
Attributes:
1. Program Class.
a. There are two program classes to be assigned to the rule while creating.
i. Payroll (C).
ii. Time (T).
2. Country Grouping.
a. For Payroll program class the country grouping should be mentioned. (E.g. 40 for India).
b. For Time management rule the country grouping should be (*).
3. Employee Sub-grouping.
a. All the wagetypes have an attribute of employee sub-grouping.
b. It varies client to client.
c. Value 3 means EE sub-grouping is 3.
d. Value * means all EE Sun-groupings.
4. Wagetypes.
a. The wagetype in the internal table which is meant to be processed by the rule.
b. If a value for Wagetype is being given then the particular wagetype is being queried for processing.
c. If **** has been given then all the wagetypes present in the particular internal table will be processed.
Structure of the Rule.
Frequently Used Internal Tables in PY Processing:
The Payroll driver uses lots of internal tables used for storing data temporarily in the program for processing. Some of the important internal tables are:
The structure of internal tables:
EE Sub-grouping:
1. The Wagetype is assigned to a particular Employee sub-group.
2. 3 is a particular employee subgroup for basic pay wagetype.
3. * value means for all EE sub-grouping.
Wagetype Code:
1. The Wagetype code number is the number assigned to a particular pay component.
Wagetype Description:
1. The description for the wagetype code.
NUM:
1. If there is a split for the wagetypes then this NUM field will make them different.
2. If A persons basic salary is changed in the mid of the month then the wagetype will be split in two amounts with NUM = 01 and NUM = 02.
RTE:
1. The RTE column stores a value for;
a. Rate of interest.
b. Number of leave days.
c. Projection factor. Etc.
2. E.g. In the above diagram /401 wagetype has RTE value 10 which is the projection factor used for different calculations.
AMT:
1. This column possesses the amount of the particular wagetype.
Use of the internal tables:
1. The internal tables are being used for calculations on the NUM, RTE & AMT fields.
2. These internal tables are being read by the rules row by row.
3. The Calculation rule would be only processed for those wagetypes which are specified in the rules source code.
4. The row in the internal table containing the wagetype which has been defined in rule attributes will be placed in the header of the internal table for processing.
5. The processing would be as per the operations used in the rule.
Some important Operations & Functions:
The editor for Operations and Functions is PE04.
While the payroll driver encounters a function and operation it would call a subroutine written in the payroll driver.
The subroutine name for the operation will be OP****, Where **** will be the name of the operation.
For E.g. for Operation AMT the subroutine name would be OPAMT.
The code written for the function will be found as a subroutine in payroll driver as FU****, where **** will be the name of the function.
For E.g. for function INEPF the subroutine name would be FUINEPF.
Operations:
AMT:
1. This Operation would fetch the Amount of the wagetype queried in the rule, in the Variable AMT for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> AMT.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (AMT= 1000) will fetch the Amount of Wagetype 1000 into AMT.
7. Pressing F1 on the AMT Operation will provide the documentation.
RTE:
1. This Operation would fetch the Rate of the wagetype queried in the rule, in the Variable RTE for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> RTE.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (RTE= /401) will fetch the Rate of Wagetype /401 into RTE.
7. Pressing F1 on the RTE Operation will provide the documentation.
NUM:
1. This Operation would fetch the Split indicator of the wagetype queried in the rule, in the Variable NUM for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> NUM.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (NUM= 1000) will fetch the Split indicator of Wagetype 1000 into NUM.
7. Pressing F1 on the NUM Operation will provide the documentation.
ADDWT:
1. This Operation will append one more row in the internal table (Processed by the rule).
2. After calculating an amount from a particular wagetype the amount can be assigned to another wagetype and append to the internal table.
3. For E.g. ADDWT 2050 will add the NUM, RTE, AMT calculated to the NUM, RTE & AMT of the wagetype 2050.
4. If the Wagetype 2050 is not there before in the internal table then NUM, RTE & AMT would be 0.
5. If any value of these three variables are present before then they will be added to the calculated ones.
Functions:
PIT:
1. This function will read the internal table IT (Input table).
2. The function will hold a rule as first parameter.
PRT:
1. This function will read the internal table RT (Results table).
2. The function will hold a rule as first parameter.
PDT:
1. This function will read the internal table IT (Input table).
2. The function will hold a rule as first parameter.
PORT:
1. This function will read the internal table ORT (Old results table).
2. The function will hold a rule as first parameter.
P0014:
1. This function will read the Infotype 0014 for processing.
2. The function will hold a rule as first parameter.

Regarding schemas and pcrs

Hi gurus,
Though i know about schemas and pcrs..i ahve a small confusion..can anybody clarify me these questions?
1)why we use schema and functionality of the schema?
2)why we use subschema and functionality of subschema?
3)what are the parameters1,2,3,4.
   why do we use these paremters?
   and how it helps... where can we get the documentation for parameters?
4) what an Function does for schema and subschema?
5)what an operation does?
//jack//
Edited by: michael jack on May 22, 2008 8:47 AM
Edited by: michael jack on May 22, 2008 8:57 AM

In simple words schema guides Payroll driver that following path will follow for processing of info types in system. for example if u see the payroll log just think that why infotype 0001 read at start whey system creates bank payment after reading all data? this is all schema
Second part is subschema help schema if you have little know how of programming you can take it as conditional loop sort of things. :).
Technical detail is as under (From sapexpert.com)
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, in Canada RPCALCK0 and for international RPCALCX0. 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, and rules
with PE02. Functions and operations are maintained with transaction PE04. To view payroll results,
use transaction pc_payresult (or in earlier R/3 releases go to Tools>Payroll result>Display in the Payroll menu). (See Figure 1.)The standard payroll schema for a country can be derived from table T500L (see the screen blow). If the country in table T500L has an X in the Old Naming Conv field, then the schema is HR Country Indicator plus 000. Otherwise, it is the ISO Code plus 00. So the U.S. has schema U000, for Mexico it is MX00 and for international its X000.
Good Luck
Syed

URGENT : Pls help on Personnel Calculation Rules

Hello Gurus,
I am creating new rule to change the attendance type depending on the holiday.
What is the operation/function should I use.
Senaio: There is a 'Holiday Hrs Worked' attendance type and this has to be used ONLY when an emp is working on a public holiday (defined in public holiday calender). But technically this attendance type can be used anyday.
Problem: The 'Holiday Hrs Worked' has different OT calculation rules than regular hrs. So if am emp uses this attendance type for regular day, he gets more OT.
I am able to differentiate using VARSTHOLCL, but then I want to change the attendance type in the schema.
Please help me as this is URGENT.
Thanks in Advance and Max points will given to very helpful answer.

Fixed on my own by changeing all the PCR underneeth

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

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

Schema and calculation rules in Payroll

Similar Messages

Maybe you are looking for