PCR rules in Schemas

Any body help me How do we config PCR rules in SCHEMAS.can any body tell me in deep or with Screen shots.
Thanks & Regards
Srinivas

Hi Srini
I would be happy to share a useful doc that tell What Payroll Functions and Operations are doing and how to read rules and schemas..
it was posted by biswajit das What Payroll Functions and Operations are doing?
Biswajit Das
Business Card
Company: www.tcs.com
Posted on Oct. 20, 2006 09:09 AM in ABAP
i quite see yur contact mail in buss card..could u emal me and wil be happy to share it..
infact kndly igmore it ,its the document siki mate has sent you...i quite dint chk that..
No Worries
Karthik
Edited by: SAPenjoy:) on May 11, 2009 8:41 AM

Similar Messages

HR rules and schemas

Hi,
Anyone of you have a manual or instructions of HR rules and schemas?
Thanks

Hi,
if you hven't done yet please visit
rules
http://help.sap.com/erp2005_ehp_02/helpdata/en/4f/d51fb2575e11d189270000e8322f96/frameset.htm
schemas:
http://help.sap.com/erp2005_ehp_02/helpdata/en/4f/d51ca1575e11d189270000e8322f96/frameset.htm
Regards
Bernd

SAP 700 or writing PCR's and SCHEMAS.

What is SAP 700 ?
Actually we want to learn on writing PCR's and SCHEMAS.
Could any body please guide on this topic .
Thanks in advance...

I have a word document on PCRs & Schemas & its not copyrighted.. you can drop me an email for that.. the id is on my business card..
SAP 700? well haven't heard of it.. going by the naming convention, I guess ERP 2006 would be SAP ECC 7.0 as of now we have only ERP2005 ie SAP ECC 6.0 available for unrestricted shipment.. or are you refrerring to WAS700 the erstwhile BASIS.. then its part of ERP2005.
I would check service.sap.com for the Solution details..
~Suresh

Understanding of PCR Rule based on calendar days

I wrote below pcr 8000/31 days = 258 It should add 258 to wage type 1400 but it is throwing an error

Table
Rule
In XT00
This is what it shows

PCR RULE

HI,
I want to know the pcr for wage type ??
what is t code in pe02..
Regards,
pramod

Hi,
Decimal factor of Salary wage type.
Earlier I have the problem with rounding off of leave encashment for which u have suggested to maintain rule in inval in pe02,
the same thing i have incorported as suggested, but it get impact on other salary head like pt, hra retro cal...
Rounding off decimal has taken place , but it disturb to other salary head, unwanted entries appear in sal head...
Please advice...
Regards,
pramod

Rules and Schemas -

Dear Gurus,
Do you know any command so I can use inside a payroll rule, to find if the employee works for more or less than an year in the company?
A friend told me that this command should do that: NUM=F01C
But it returns a strange value...
Can anyone please help me?
Regards,
PC

Hi,
I am not sure about IT 0016, but F* operation using NUM you have following options. Maybe they will be helpful.
A, B First entry from infotype 0000
C    Last entry, or reentry
D Last change of individual   working time from infotype 0041. In table T530, if the field   KUNBZ (indicator for irregular   payments) is 05, then the start date of   the work center is taken for D.
E    Last change of capacity   utilization level from infotype 0008
F    Last change of weekly   working hours from infotype   0007. A comparison is carried out   with date type C for the date   types D, E and F. If the value determined   for C is greater than the   values determined for D, E or F (that   is, a later date), the value of C is used for D, E or F. Any changes in the capacity utilization   level or the like   before the last reentry are not   evaluated. The date of the last reentry is taken instead   of this date.
G    Birth date from infotype   0002
W    Reentry. The last reentry date is   entered in this date   specification. If no reentry data exists, the   initial entry date is used.   This date has the short name 'A' in the   evaluation.
X     Employee leaves after the end of the period in   accordance with infotype 0000. The system checks whether there is a record for infotype 0000 (Actions) has a record where   the   Stat2 field has the value 0 (= left). The start date (BEGDA)   of this record is the leaving   date. This date type always has an   entry. If an employee leaves   after the end of the period in question,   this date will be used. If no   leaving date exists, the date December   12, 9999 is used.
Z     Leaving before the end of the period in accordance with infotype 0000 The system checks whether there is a record for 0000 (Actions) where the   Stat2 field has the value 0 (=   left). The start date (BEGDA)   of this record is the leaving   date. This date type always has an   entry. If an employee leaves   before the period in question, this date   is used. If no date is given,   the date December 31, 9999 is used.
Cheers

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.

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.

Rules & Schema in Payroll

Team,
Can anyone please let me know how to learn about Rules & Schema in Payroll.Plrase provide me some link or Document.
Thanks
Soni

hey sonia,
go through this link ...
http://www.insightcp.com/res_19.htm
http://www.insightcp.com/res_20.htm
this website explained basics of payroll process, rules and schema..
reward points if helpful.
regards,
salman

Query Hire date in a PCR

Hi,
Could you help me in querrying hire date in a PCR.
I need to differentiate b/w EEs who joined from 1st-15th of a month to the ones who joined in the later part of the month.
Any help is highly appreciated.

Hi,
what about this quick idea - use VARSTREDAY in PCR rule and make 01, 02, . . . .31 as a result from query. Continue with wtriting the rows and choose some time type. Store the value 1 into the time type. Then put a HRS query with the chosen time type before the VARST - it will prevent the rule to check itself over again. Store the time type into SALDO. If you generate qoutas according to some time types, then the time type can also be stored in the PCR rule with Varst. Then you need to solve roll-over if the qouta needs to be generated the next year.
ex.
HRS=BZZZ1
HRS?1
= nothing
VARSTREDAY
01 HRS=1
01 ADDDBZZZ1
01 HRS=1
01 ADDDBQBAS (time type for qouta base)
It is not some smooth solution but it should work.
Cheers
xDracula

RELAX NG or Schematron schemas for Pages XML file format?

Hey, I have been following with interest for over a year - more like two years - the whole "where are the XML schemas" for Keynote 1, and then Pages and Keynote 2.
Apparently there is some difficulty obtaining them and I would guess that means defining them. Because if Apple had their hands on them, they would be out - and up to date - by now.
XML Schema (.xsd) files are pretty painful to generate. There is a much simpler and and yet even more powerful schema format called "Relax NG". Assuming someone knows what the grammar is that Pages will willingly/successfully slurp up - they could probably create a .rnc file from scratch pretty quickly. The learning curve is pretty short for basic stuff and the amount of typing required is at least 40% less than when you create a .xsd file.
Some things do not lend themselves to grammar based schemas like XSD, RNG, or RNC.
Instead, a rule based schema language works better. Schematron is very good for this. The suffix for this file type is ".sch". The web site is easy to get to - just type schematron in your web browser's address field and press enter. Specs are all there.
There is a program called Examplotron that creates a Schematron schema for you, given an XML file that is a sample. Of course, making rules from one example is not the same as knowing all the rules. The more different kinds of stuff you have in the file though, the better your chances are of getting a decent start going. Examplotron lives on the web at examplotron.org in case you are curious.
OxygenXML is a very, very good XML editor and schema development environment. I have used it and a bunch of others. It is my favorite, by far.
Someone at Apple should get on this. If it is too hard to create an XML Schema file - then please, please - try to create an RNG, RNC, or SCH file.
If Apple cannot do it, then perhaps the user community could take a crack at it. However, it is a little bit like trying to document the laws of a country by watching what the government people do, what people do who do not get arrested, and what people do who do get arrested.
You are not certain to see an example of every law being broken - for starters, so you will miss some. (One hopes you will not see every law that exists broken!)
You are also not going to be able to tell what laws have influenced behavior that is lawful.
So, for both reasons, you might unwittingly "break the laws" of this hypothetical land. In that case, you might be executed, fined, imprisoned, or as is the case still in some countries - have your hand chopped off!
In the case of feeding a file based on mistaken assuptions to Pages, it certainly will not do what you want it do do. In theory, it might even crash, lose some data, pop up an error - or worse maybe not pop up an error, or corrupt its internal structures and become unstable. Or seem to work but fail to write the whole file out again. Or write out something that it cannot read in again - or does not reconstitute into the document that you used to have.
Granted, there is a brute force technique that can be employed. You can write an AppleScript that gets pages to create a document that exercises every possible style and feature and logical ordering and nesting of things.
Then you can study the XML that generates, or even feed to to Examplotron or a DTD generator.
Doing so would probably be a way to get a good start going.
Without any schema, there is no way to know if a complex program-generated Pages document will work right with pages.
Granted, such program-generated documents can be generated with Applescripts. But if one already has some XML that one wants to blend in, for example - then it would be better to do it with XSLT. Or Java. Or whatever.
Unfortunately, you really have to know what XML is legal in pages - and you have to know the grammar or rules for what Pages expects.
So, any XSD coming from Apple in the near future - or any interest at Apple in completing a .rnc or .rng schema if it gets mostly done by customer(s) and then handed off to Apple to finish?

XML converter (an add on to Inbound Refinery) could be used to display the contents with your XSLT choices but analyzing the file to prevent checkin would take data validation that would be custom. The CS does not care the file format or file type for checkin. Others have looked for analysis of file extension to stop checkin of certain extensions. This has been custom. I think there may be enhancement requests from customers for this kind of validation for the CS but it does not exist in the core yet.

Rule in PTM

Gurus,
   I have a requirement, to process if the Company code is 0001 then crdit 1 days to quota 01. How to write in rule.
Also let me know where to insert the rule in schema TM04
Edited by: kumar.Durai on Mar 9, 2009 6:14 AM

Gurus,
         I found under which line i need to enter the rule.
         but i want to know in which coloumn to enter func,para1, para2,para3
because i am getting the following errror.
Schema SM04 is incorrect
Call the schema editor to analyze errors
Check the syntax of the incorrect schema
Solved the issue myself.
Edited by: kumar.Durai on Mar 12, 2009 8:58 AM

Encoding Rules in JWSDP1.3

Hi,
In Basic Profile 1.0, SOAP encoding is explicitly disallowed in section 5.8. However, in JWSDP 1.3 which is BP1.0 compliant, a 'java.lang.Integer' object is represented by an 'int' data type using the schema "http://schemas.xmlsoap.org/soap/encoding/" rather than an integer data type using the schema "http://www.w3.org/2001/XMLSchema". Can this be considered as BP 1.0 compliant?
Hope someone can help to enlighten.
Thanks
Jason

Sorry, I'm a novice in this area so I don't quite understand your reply. But what I'm trying to understand is why two different schemas are used to represent a 'int' and a 'java.lang.Integer' in JWSDP1.3. When I edit the WSDL document to point to the same schema (either one of them), the client that is generated as a result alway contains 1 incorrect conversion. (schema data type to java data type)
In short, is there is mapping rule for schema to java conversion that all vendors(BEA, Oracle ...) must follow? Initially, I thought BP1.0 section 5.8 helps to alleviate this by restricting to only one schema ("http://www.w3.org/2001/XMLSchema") for serialization and deserialization of simple data types. Apparently I'm wrong and I'm still very confuse. Appreciate if you can help to aid my understanding in this area. Thanks
Cheers
Jason

List the count of each schema objects.. schema wise sql query needed

Hi Friends,
i need a sql query which has to list the schema name along with the count of schema objects like tables,views,triggers.... order by schemaname
Regards,
DB

Hi
You can try this option if you use 11g .
Get all the object types in your db.
SELECT DISTINCT object_type
             FROM dba_objects;Then include all the object types in to the below query.
select *
from (select owner, object_type, 1 CNT
          from dba_objects ) e
        pivot( sum(CNT) for object_type in
          ( 'INDEX','TYPE','VIEW','LIBRARY','TRIGGER','DIRECTORY','PACKAGE','QUEUE','PACKAGE BODY','TABLE PARTITION','PROCEDURE',
            'WINDOW','CLUSTER','LOB','FUNCTION','CONSUMER GROUP','CONTEXT','RULE','XML SCHEMA','SEQUENCE','INDEX PARTITION','OPERATOR',
            'EVALUATION CONTEXT','SCHEDULE','JOB','SCHEDULER GROUP','LOB PARTITION','JOB CLASS','INDEXTYPE','TABLE','TYPE BODY','RESOURCE PLAN',
            'TABLE SUBPARTITION','UNDEFINED','DESTINATION','SYNONYM','EDITION','PROGRAM','RULE SET' ) )
order by owner;Cheers
Kanchana

Writing PCRs....

Dear Vivek Sir,
Can you give some hints or tips how to analyze the requirement before writing a PCR. How to select the functions and operations.
Basically an idea about how to start with. I know to read a PCR analyze a schema.
Need your inputs to start writing PCR.
Thanks,
Prathibha

Thank you very much Vivek Sir. This was really helpfull. I will follow the same.
Thanks Again
Prathibha

PCR rules in Schemas

Similar Messages

Maybe you are looking for