Wednesday, 6 June 2012

What Is ESS and MSS?
Explain briefly the process/functionality and the distinction between ESS and MSS.
ESS - Employee Self Service is an web enabled tool used to update their own datas by the employee itself.
MSS- Manager Self Service is an web enabled tool used for Managers to take report or update the datas of subordinate.
This will give you a comprehensive idea:
To implement LEAVE REQUEST &APPROVAKL, both ESS and MSS are not mandatory. But ESS is required.However this functionality is developed to be avaialable in MSS also if a client wants have both ESS and MSS.  Without MSS, the business flow of Leave request would be in ESS  is like this:
1. An employee wants to take two weeks of leave. He or she accesses the Leave Request Web application. He or she sees in the Team Calendar that other team members also have leave at the same time. Nonetheless, he or she requests leave for the planned period.
2. The leave requires approval. The system automatically determines the approver responsible and lists the name in the Web application. If required, the employee can overwrite the name of the approver.
1. The employee's request is stored in the database of leave requestswith the status Sent.
2. Once a day, the RPTARQEMAIL report (Leave Requests: Send E-Mails) is run in the background. The system sends an e-mail to the appropriate approver for the requests with status Sent that require approval. The e-mail notifies the approver of the steps required.
3. The approver accesses the Approve Leave Requests Web application from the Universal Work list.. The application provides the approver with a list of all the leave requests that require his or her approval.
4. The approver selects the employee's leave request. After checking the Team Calendar, the approver realizes that the employee's leave request cannot be approved since it would mean there would not be enough team members at work for the period in question.
5. The approver writes a note in which he or she states why the request has been rejected. He or she then rejects the request.
6. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her that the request was rejected. The employee accesses the Leave Request Web application. He or she selects the request in the Absence Overview. He or she sees in the note the reason why the request was rejected.
7. The employee looks at the Team Calendar and finds a period in which no other team members are on vacation. He or she changes the period of the request. The employee specifies the change in period in the note.
8. The RPTARQEMAIL notifies the approver of the request by e-mail.  This time the approver can approve the request.
9. The request receives the status Approved in the database. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her that the request was approved.
10. The system processes the requests further according to their status:
11. The RPTARQPOST report (Leave Requests: Post) writes all requests in the database that have the status Approved to the Absences (2001) or Attendances (2002) infotype.
12. The system may not be able to post the requests to the infotypes if, for example, they collide with other infotype records. These requests are given the status With Errors.
13. The RPTARQEMAIL report sends an e-mail to the relevant time administrator to notify him or her that the requests were unable to be posted.
14. The time administrator accesses the RPTARQERR report (Leave Request: Process Posting Errors). It lists the requests with errors.
15. The time administrator analyzes the error situation in the backend system.
16. If he or she can solve the cause of the problem and save the data record in the infotype, he or she uses the RPTARQERR report to set the request to Posted.
17. If the problem cannot be solved, because the employee has other commitments at the time, for example, the time administrator rejects the request.
18. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her of the change in status of the request (in ESS)
MSS:  it is a web based application  designed for the people who carry out management tasks.  Here is the brief description.
This Manager Self Service is designed for all employees who perform management tasks at an operational level, for example:
i.   Line managers
ii.  Team leaders with project management tasks
iii.  Department heads
In particular, the business package supports managers perform the following:
1    Tasks related to the personnel responsibility for their team
- Controlling tasks within their budgeting responsibilities
- Planning tasks
- Project management tasks
* Budget* -- Supports managers in fulfilling their cost and budget responsibilities, including annual budget planning, budget monitoring, cost analysis, and correction of postings. Managers can check critical variances, monitor travel expenses, and track budget consumption on projects.
*Staffing* -- Supports managers in their HR-related administrative and planning tasks. The application supports HR processes relevant to a manager's particular tasks -- from recruitment to the annual employee review and compensation planning. It allows a manager to display attendance information, as well as to change data for employees who have no access to PCs. SAP Manager Self-Service supports flexible reporting on data from different data sources, and a quota planning function enables managers to plan future staffing quotas.
In the latest release there some additional functionalities (iViews) are added.
ESS:  Allows employees to create, display, and change their own data in the company's intranet. In Personnel Administration, for example, employees can use the Personal Data service to create and edit their own personal data. In this way, employees can keep their own data up-to-date, while simultaneously reducing the number of time-consuming and expensive activities performed by the Human Resources Department.
Employee Self-Service of mySAP ERP enables employees to create, display, and change their own HR-related data in the Enterprise Portal. It covers data from various business areas:
- Working Time
- Career and Job
- Employee Search
- Personal Data
- Benefits and Payment
- Travel Management
- Corporate Information
- Life and Work Events
- Training related details
- Qualifications 
- Appraisals 

Tuesday, 5 June 2012

sap hcm tables


  • T000: To create and maintain SAP system clients.
  • T001: Company codes
  • T001P: Personnel Areas/Subareas
  • T012: House banks
  • T012K: House bank accounts
  • T012T: House bank account names
  • T500L: Personnel Country Grouping
  • T500P: Personnel Areas
  • T500T: Personnel Country Groupings
  • T501: Employee Group
  • T501T: Employee Group Names
  • T502T: Marital Status Designators
  • T503: Employee Groups / Subgroups
  • T503K: Employee subgroup
  • T503T: Employee Subgroup Names
  • T504A: Benefits – Default Values (NA)
  • T504B: Benefit Option Texts (North America)
  • T504C: Benefit Type (NA)
  • T504D: Benefit Credit Group Amount
  • T504E: Benefit Amount
  • T504F: Benefit Costs
  • T508A: Work Schedule Rules
  • T508T: Texts for Employee Subgroup Groupings for Work Schedules
  • T510: Pay Scale Groups
  • T510A: Pay Scale Types
  • T510F: Assign Pay Scale > Time Unit, Currency
  • T510G: Pay Scale Areas
  • T510H: Payroll Constants with Regard to Time Unit
  • T510I: Standard Working Hours
  • T510J: Constant Valuations
  • T510L:Levels
  • T510M: Valuation of pay scale groups acc. to hiring date
  • T510N: Pay Scales for Annual Salaries (NA)
  • T510S: Time Wage Type Selection Rule
  • T510U: Pay Scale Groups
  • T510Y: Special Rules for Wage Type Generation
  • T511: Wage Types
  • T512R: Cumulation Wage Types in Forms
  • T512S: Texts for Cumulation Wage Types in Forms
  • T512T: Wage Type Texts
  • T512W: Wage Type Valuation
  • T512Z: Permissibility of Wage Types per Infotype
  • T513: Jobs
  • T514S: Table Name Texts
  • T514T: Field Name Texts
  • T51D2: Wage Type Classes
  • T51D3: Reduction Rules
  • T51D4: Cumulation Rules
  • T527X: Organizational Units
  • T528B: Positions – Work Centers
  • T528C: Wage Type Catalog
  • T528T: Position Texts
  • T529A: Personnel Event
  • T529F: Fast Data Entry for Events
  • T529T: Personnel Event Texts
  • T52BT: Texts for HR Objects
  • T52C0: Payroll Schemas
  • T52C1: Payroll Schemas
  • T52C2: Texts for Personnel Calculation Schemas
  • T52C3: Texts for Personnel Calculation Schemas
  • T52C5: Personnel Calculation Rules
  • T52CC: Schema Directory
  • T52CD: Schema Directory
  • T52CE: Directory of Personnel Calculation Rules
  • T52CT: Text Elements
  • T52CX: Cross References via Generated Schemas
  • T52D1: Valid Processing Classes
  • T52D2: Valid Values for Processing Classes
  • T52D3: Valid Evaluation Classes
  • T52D4: Permitted Values for Evaluation Classes
  • T52D5: Wage Type Groups
  • T52D6: Wage Type Group Texts
  • T52D7: Assign Wage Types to Wage Type Groups
  • T52D8: Valid Processing Classes – Texts
  • T52D9: Valid Values for Processing Classes – Texts
  • T530: Reasons for Events
  • T530E: Reasons for Changes
  • T530F: Reasons for Changes
  • T530L: Wage Types for Special Payments
  • T530T: Event Reason Texts
  • T531: Deadline Types
  • T531S: Deadline Type Texts
  • T533: Leave Types
  • T533T: Leave Type Texts
  • T539A: Default Wage Types for Basic Pay
  • T539J: Base Wage Type Valuation
  • T539R: Events for Standard Wage Maintenance
  • T539S: Wage Types for Standard Wage Maintenance
  • T548: Date Types
  • T548S: Date Conversion
  • T548T: Date Types
  • T548Y: Date Types
  • T549A: Payroll Areas
  • T549B: Company Features
  • T549C: Decision Trees for Features (Customers)
  • T549D: Feature Directory
  • T549L: Date modifiers
  • T549M: Monthly Assignment: Payroll Period
  • T549N: Period Modifiers
  • T549O: Text for date modifier
  • T549P: Valid Time Units for Payroll Accounting
  • T549Q: Payroll Periods
  • T549R: Period Parameters
  • T549S: Payroll date types
  • T549T: Payroll Areas
  • T549M: Monthly Assignment: Payroll Period
  • T549N: Period Modifiers
  • T549O: Text for date modifier
  • T549P: Valid Time Units for Payroll Accounting
  • T549Q: Payroll Periods
  • T549R: Period Parameters
  • T549S: Payroll date types
  • T549T: Payroll Areas
  • T554S: Absence and Attendance Types
  • T554T: Absence and Attendance Texts
  • T554V: Defaults for Absence Types
  • T554Y: Time Constraints in HR TIME
  • T555A: Time Types
  • T555B: Time Type Designations
  • T559A: Working Weeks
  • T559B: Name of Working Week
  • T572F: Event Texts
  • T572G: Allowed Values for Events
  • T572H: Event Value Texts
  • T582A: Infotypes
  • T582B: Infotypes Which Are Created Automatically
  • T582S: Infotype Texts
  • T582V: Assignment of Infotypes to Views
  • T582W: Assigns Infotype View to Primary Infotype
  • T582Z: Control Table for PA Time Management
  • T584A: Checking Procedures – Infotype Assignment
  • T588A: Transaction Codes
  • T588B: Infotype Menus
  • T588C: Infotype Menus/Info Groups
  • T588D: Infogroups for Events
  • T588J: Screen Header Definition
  • T588M: Infotype Screen Control
  • T588N: Screen Modification for Account Assignment Block
  • T588O: Screen Modification for Assignment Data
  • T588Q: Screen types for fast entry
  • T588R: Selection Reports for Fast Data Entry
  • T588S: Screen Types for Fast Entry
  • T588T: Menu and Infogroup Designations
  • T588V: Business object type
  • T588W: Event types for infotype operations
  • T588X: Cust. Composite definition of event types for IT operations
  • T588Z: Dynamic Events
  • T591A: Subtype Characteristics
  • T591B: Time Constraints for Wage Types
  • T591S: Subtype Texts
  • T596F: HR Subroutines
  • T596G: Cumulation wage types
  • T596H: Cumulation wage type texts
  • T596I: Calculation rule for cumulation wage types
  • T596U: Conversion Table
  • T599B: Report Classes
  • T599C: Report Classes
  • T599D: Report Categories
  • T599F: Report Classes – Select Options
  • T777A: Building Addresses
  • T777T: Infotypes
  • T777Z: Infotype Time Constraints
  • T778T: Infotypes
  • T778U: Subtypes

Monday, 4 June 2012

Various operations used in pcr


Commonly used operations in payroll configuration
OperationDescription
*This covers all the remaining entries not already specified. If you leave the line blank for the operation then the WT is dropped. Remember you always have to have an option for * in your PCR.
ADDCUCumulates the wage type into the relevant cumulation (/101...) and valuation(/201...) wage types
ADDNA *From the IT, Number and Amt are cumulated into the OT. Blank is OT whilst E refers to the RT.
ADDNA 4067Current Num and Amt are added in to wage type 4067.
ADDWSE9N03This operation is very similar to ADDWT. The only difference is that it writes the value to table V0 as well
ADDWSI*Store the current wage type in the IT.
ADDWT *Store wage type in IT/OT
ADDWT 1103All the current values for amt, num and rte are added to the values that are currently held in wt 1103
ADDWT&TAdds the current wage type to the variable table as T - which can be used at a later stage
ADDWTA*The values in the wage type are copied to the previous employer table VAG - called in the rules XDPI, XDPR & XDPT
ADDWTC*The values in the current wage type are added into the CRT
ADDWTC/101The values in the current wage type are added into the CRT for the technical wage type /101
ADDWTD*The values in the current wage type are added into the Difference table DT
ADDWTD/551The values in the current wage type are added into the difference table DT for the technical wage type /551
ADDWTD/APOAdd the current wage type to the difference table (DT)
ADDWTEStore amount in Results Table (RT) - difference with line below
ADDWTE*Add the current wage type to the results table RT
ADDWTE/101Add the current wage type to the results table as /101
ADDWTH/201Add the current wage type to the old results table (ORT) as wage type /201
ADDWTI*Add the current wage type to the input table IT
ADDWTI/101The values in the current wage type are added into the input table IT for the technical wage type /101
ADDWTL*Add the current wage type to the results table last payroll (LRT)
ADDWTNUsed in XLON
ADDWTN/LRP(Loans - XLON)
ADDWTWAdd the current wage type to the wage maintenance table
AMT- 9023Subtract amount field from wage type 9023 from Table IT (if wage type 9023 is available.)
AMT%33.33Multiply the amount by 33.33%
AMT%KSAPROMultiply the amount by the value SAPRO held in table T511k
AMT-& TAmount minus the value held in variable T
AMT*-1Amount multiplied by negative 1
AMT*12Multiply amount by 12
AMT*KGENAUMultiply the amount by the constant GENAU held in table T511k. GENAU is used to factor up by 4 or 5 factors of 10 to avoid the issue of errors caused by rounding.
AMT-.04Subtract 0.4 from the amount field
AMT/2Divide the amount by 2
AMT/KGENAUDivide the amount by the factor GENAU held in the constants table T511k
AMT/KPKWPRAmount divided by the constant PKWRP held in table T511K
AMT/KZF001Amount is divided by constant ZF001 from table T511K
AMT? *Compare the value held in the amount field for all wage types
AMT? /GPYCompare the value held in the amount field for wage type /GPY
AMT?& ZAPRCompare the value held in the amount field against the constant ZAPR
AMT?0Compare the value held in the amount field against 0
AMT?E /167Compare the amount against the value of the amount held in the results table RT for wage type /167
AMT?IGRUEBCompare the current amount against the limit held for the bank transfer
AMT+ /564Add the amount from wage type /564 from the IT
AMT+ 0001Add amount field from wage type 0001 from Table IT (if wage type 0001 is available.)
AMT+ 9013Add amount field from wage type 9013 from Table IT (if wage type 9013 is available.)
AMT+& ZSAPAdd the value held in the variable ZSAP to the amount for the current wage type being processed
AMT+E 910BAdd the current amount to the RT and place in wage type 910B
AMT+O /ZPOAdd Amt from wage type /ZPO into VORT (Summarised ORT)
AMT< /562Checks whether the currently held amount is less that that held in the wage type /562
AMT= *This sets the amount = zero for the wage type in question
AMT= /111Store the value in the amount field of wage type /111 in the amount field of wage type 2110
AMT= 1000Store the value in the amount field of wage type 1000 in the amount field of wage type 2110
AMT= BETRGLet the amount equal the value held in the BETRG (amount) field for the wage type in question
AMT= PKWWRReset the amount on wage type xxxx to that held in the value for KWWR held in T511K
AMT= PLANSSets the amount = position number
AMT=& /426Set the amt = amt held on technical WT /426
AMT=& TASAReset the amount on wage type xxxx to that held in the temporary wage type TASA
AMT=0Let the amount equal zero
AMT=A *The amount is set to the value held in the table VAG - previous employee data
AMT=E *Lets the Amt = the Amt held for the current wage type in the RT
AMT=E /167Lets the Amt = the Amt held for technical wage type /167 in the RT
AMT=KSAPLRSet the amount = the value SAPLR held in table T511k
AMT=L *Lets the Amt = the Amt held for the current wage type in the LRT - last result table
AMT=L /561Lets the Amt = the Amt held for the wage type /561 in the LRT - last result table
AMT=N /LBBAdd the amount value in technical loan wage type /LBB (loan balance) to specific loan balance wage type
AMT=N /LOPAdd the amount value in technical loan wage type /LOP (loan payment) to specific loan payment wage type
AMT=N /LRPAdd the amount value in technical loan wage type /LRP (loan repayment) to specific loan repayment wage type
AMT=Q /GPYLets the Amt = the Amt held for the wage type /561 in the OCRT - old cumulative result table
AMT=ZEROReduce the value in the amount field to zero
AMT>*"Maximum formation: The greater value of * and the current value of the AMT field

is determined and written to the current AMT field."
AMT-1Multiply the amount by -1 - I think this should be subtract 1 from the amt
AMT50If the amount field value is smaller than 50, it is retained. Otherwise it is set at 50 (forming a minimum amount).
AMT-E /167Subtract the Amt value held in the RT for /167 from the currently stored amount
AMT-K43301Take the value held against payroll constant 43301 from the annual salary
AMT-O /167Subtract the Amt value held in the ORT for /167 from the currently stored amount
AMT-R 9019Amt for the current wage type less the value held in the RT for 9019 (Results wage types using exact splits)
AMTS /564Subtraction to zero - the value cannot be less than zero.
AMTS*Subtraction to 0 (not negative) for the current wage type
AMTS* 9013Subtraction to 0 (not negative). Current wage type less 9013
AMTSE 9043Subtraction to 0 (not negative). Current wage type less Amt held in the RT for wage type 9043
BTREC /558"Sets the recipient data for bank transfers. Can only be run after bank transfer data has been read from

an infotype. Data on wage type and amount are transferred from the current fields (OT) and retained in the transfer table together with data on the recipient of the record last read."
CMPER 0510Compares the current amount with that held for period 10 in year 05.
DExpect a decision in this line
D AMT?0The amount field value is compared with 0, and the result ('>', '=' or '<') is placed in the variable key.
D VWTCL 01Make a decision on processing class 01
DIVID ANRDivide the amount by the number and store the result in the rate field
DIVID ARADivide the value in amount field by the value in the rate field and put the result in the amount field
DIVID ARRDivide the amount by the rate and store the answer in the rate for the wagetype
DIVID NRNDivide the number by the rate and store the answer in the number field
ELIMI *Eliminate all splits
ELIMI AEliminate splits - work center period (WPBP)
ELIMI KEliminate splits - cost accounting
ELIMI KTXEliminate the splits for cost accounting, alternative payments and variable assignment
ELIMI REliminate splits - employee sub-group grouping for PCRs
ELIMI TEliminate splits - alternative payments (ALP)
ELIMI UEliminate splits - bank transfer (BT)
ELIMI XEliminate splits - variable assignment
ELIMI YEliminate splits - absence assignment
ELIMI ZEliminate splits - time unit
ERRORProcessing terminates for the current employee
FILLF ARestore the original values for the amount - i.e. The values that were held for the amount field in the WT before any processing in this rule
FILLF NRestore the original values for the number - i.e. The values that were held for the number field in the WT before any processing in this rule
FILLF NRARestore the original values for the number, rate and amount - i.e. The values that were held for the number, rate and amount fields in the WT before any processing in this rule
FILLF RRestore the original values for the rate - i.e. The values that were held in the WT before any processing in this rule
GBVRT"GB specific processing of AWE operation

GB specific operation to overwrite the average RATE of wage type /MAE in table RT in case of a retro calculation."
GCY ZUM2Call PCR ZUM2
GCYGXALQCalls PCR XALQ for all wage types - sets wage type to ****
GEWRTElimination of WPBP split in the RT
GSXP2New Changes Across End of Year solution active for GBSXP phase 2
GSXPDCheck on Implementation Date of AVERA for SxP AWE. Called in GG70 and ensures that the old and new technical wage types for averages don't both exist.
LRTST YEvaluates the status of the LRT table. Processing is only continued if the previous month falls in the current year.
MEANV 01Calculation of averages for 01 (from table T511A)
MEANVG03Calcualation of averages for 03 (from table T511A) - not sure what the G implies
MESSGxxxxxCan use a 5 character message. Comes up whether the log is turned on or off. Can be used as a customised error message.
MODIF 1=02Sets the modifier for Wage type generation (T510S) to 02 as the employee grouping
MODIF 2=01Sets the modifier for Constant valuations (T510J) to 01 as the employee grouping
MODIF A=01Sets the modifier for the absence valuation rule (T544C) to 01
MULTI ANNMultiply the amount by the number and store as the number field for the wage type
MULTI NRAMultiply the value in number field by the value in the rate field and put the result in the amount field
NEXTRProcess the next line. Placing an * in the last column in the operation column has the same effect as "nextr". Remember to put a letter or number in the next line under the NL column.
NEXTR AContinuation line. A...Z followed by 0...9 Don't forget to put in the letter following the NEXTR in the continuation line of the next line.
NEXTR BContinuation line. A...Z followed by 0...9 Don't forget to put in the letter following the NEXTR in the continuation line of the next line.
NUM* BSGRDMultiply the value in the number field by the value held against the capacity utilization level on infotype 0008
NUM*1.5Multiply the value in the number field by 1.5
NUM/100Divide the value in the number field by 100
NUM?0Test the value in the number field against 0
NUM+ 3710Add the value in the number field of wage type 3710 to the number field in the WT being processed
NUM+& ZNILAdds the number held in the temporary variable ZNIL to the currently held value for the number
NUM+39Add a value of 39 to the number field
NUM+C 3000Add to the NUM value from wage type 3000 held in the CRT table - to the NUM value of the WT being processed
NUM+E /852Adds the number held in technical wage type /852 to the currently held value for the number
NUM+TSAP**Adds the number from the partial period parameter for the paid absence measured in working hours for xx is the sum of all paid absences (totalled over all classes)
NUM= 3000Set the current NUM to the value held in wage type 3000
NUM= ANZHLTransfers the value of the ANZHL field to the number field.
NUM= BWGRLSets the number equal to the valuation basis per hour
NUM= EMPCTNUM = Capacity utilization level from P0007 (called record layout fields in SAP Help)
NUM= PLANSSets the number equal to the position number of the employee
NUM= STDAZSets the number equal to the number of hours taken from IT 0007
NUM=& ZSHFSets the number equal to the number held in the temporary variable ZSHF
NUM=0Set the number field to zero
NUM=39Store 39 in the number field
NUM=BJRSTDSets the number equal to the position number of the employee
NUM=BTGSTDSets the number equal to the daily hours worked by the employee
NUM=BWOSTDSets the number equal to the weekly hours worked by the employee
NUM=E /SSPSet the NUM = the value of /SSP held in the results table
NUM=GSDIVPSets the number equal to the working hours for the employee for the entire payroll period
NUM=GSSOLLSet the number = planned working time measured in working hours taken from the work schedule rule
NUM=TSAU**See part period parameter help (function PARTT)
NUM=TSAX**See part period parameter help (function PARTT)
NUM=TSDIVISee part period parameter help (function PARTT)
NUM=WOSTDSee part period parameter help (function PARTT)
NUM=YCURPPSet the NUM = current payroll period (?)
NUM-51Reduce the hours held in the number field by 51
NUM-E /845Take away the number for technical wage type /845 held in the RT from the currently held number
NUM-TSDIVPCurrent value in the number field less the total working time measured in working hours taken from the total working time in payroll accounting period
OPINDEvaluates operation indicator - used immediately after a database record has been read. Multiplies by -1.
OUTWPABARTLoad Work Center and Basic Pay Data - payroll area
OUTWPCTYMOLoad Work Center and Basic Pay Data - country modifier
OUTWPPAYSBDecide which payroll accounting area the employee is in
OUTWPPERSBLoad Work Center and Basic Pay Data - employee sub-group
OUTWPPERSGLoad Work Center and Basic Pay Data - employee group
OUTWPPLANTLoad Work Center and Basic Pay Data - personnel area
OUTWPPLTSCLoad Work Center and Basic Pay Data - personnel sub-area
OUTWPSHIFTLoad Work Center and Basic Pay Data - shift indicator
OUTWPTRFARLoad Work Center and Basic Pay Data - pay scale type
OUTWPWWEEKLoad Work Center and Basic Pay Data - working week from IT 0007
PCY X05D*Runs PCR X05D for all employee subgroup groupings
PCY X93BRuns PCR X93B
PPPAR AReads part period parameters: leavers during payroll period
PPPAR BReads part period parameters: paid absences during payroll period
PPPAR EReads part period parameters: new joiners during payroll period
PPPAR FReads part period parameters: leavers on the first day of the next payroll period
PPPAR PReads part period parameters: if the time unit for the payroll area is different to the time unit for the pay scale type and area
PPPAR RReads part period parameters: is the employee is in an active work centre?
PPPAR SReads part period parameters: basic pay changes during payroll period
PPPAR UReads part period parameters: for unpaid absences in the period
PRINTPrints the IT
PRINT& WTGPrints WTG from the variable table
PRINTCPrints the contents of the CRT
PRINTEPrints the contents of the RT
PRINTLPrints out the contents of the old results table (LRT)
PRINTOPrints the summarised ORT (VORT)
REmployee work centre is inactive, therefore do nothing
R51P1?10NYou want to know if there is an entry in table T51P1 with indicator 10 for the current IT wage type. If an entry is found, processing should be continued.
R51P1=01RYou want to read the entry in table T51P1 with indicator 01 for the current IT wage type, and store it in the OT table. If an entry is found it should be rejected
R51P6A"Operation R51P6 reads an entry from table T51P6. This table determines the characteristics of the deduction wage types.

The value of the arrears characteristic should be placed in the variable

key."
RE510TRead Pay Scale Table - group and level
RESET *Sets the splits back up again - has the opposite effect to the ELIMI * operation.
RESET 1Resets the first national split (/SI)
RESET ARResets the amount and the rate - is the opposite of ELIMI. Reset * - resets all the split indicators. Give the meaning of all the other variables elsewhere in the document.
RESET KRResets the cost accounting and employee subgroup grouping values
RESET RResets R - is the opposite of ELIMI - resets the employee subgroup groupings for the employee
RETROChecks if the payroll run is a retroactive accounting run
ROUNDRounds off the AMT field - see SAP help for specifics
ROUND 005Rounds the AMT field up so that it is divisible by 005
ROUND +100Rounds the AMT field to the next available number
ROUNDARounds off the NUM field - see SAP help for specifics
ROUNDBRounds off the RTE field - see SAP help for specifics
ROUNDGRounds off the AMT field - see SAP help for specifics
RTE%33.33Multiply the value held in the rate by 33.33% - so effectively multiply by .3333
RTE-& HALFSubtract the value held in the constant HALF from the rate
RTE* BSGRDMultiply the value held in the rate by the capacity utilization level field on infotype 0008
RTE*-1Multiply the rate by negative 1 - effectively switch the sign for the value
RTE*100Multiply percentage held in rate field by 100
RTE*KGENAUMultiply the rate by the constant GENAU held in table T511k
RTE*KGENAUMultiply the value in the rate field by the payroll constant GENAU (10,000).
RTE/100Rate divide by 100
RTE/GKDIVIRTE/ total working time in calendar days
RTE/TADIVIRTE/ total working time in working days
RTE/TASOLLRTE/ planned working time measured in work days
RTE/TKDIVIRTE/ Total working time measured in calendar days
RTE/TSDIVIDivide the value in the rate field by the worked hours for pay period being processed.
RTE/TSDIVPRTE/ total working time measured in working hours
RTE?& VLBSCheck to see how the current rate compares against the value held in the temporary variable VLBS
RTE?0Check to see how the current rate compares against a value of zero
RTE+ 1001Adds the rate held in wage type 1001 to the currently held rate
RTE+& MMAdds the rate held in the variable MM to the currently held rate
RTE+*Adds the current rate to the IT
RTE+100.00Adds a value of 100 to the currently held rate
RTE+BBETRGAdd the amount from table to the currently held rate
RTE+TKAU10Add the unpaid absences measured in calendar days for counting class 10 from table T554C
RTE= 1001Set the rate equal to the value held in the rate field for wage type 1001
RTE= BETRGSet the rate equal to the amount
RTE= BSGRDSet the rate equal to the capacity utilization level held on infotype 0008
RTE= BWGRLSets the rate equal to the valuation basis per hour
RTE=& ABSets the rate equal to the value held in the temporary variable AB
RTE=0Set the rate field to zero
RTE=10000Store 10000 in the rate field of wage type xxxx
RTE=BBETRGSet the rate equal to the amount pulled from the table
RTE=BWOSTDSets the RTE equal to the weekly hours worked by the employee
RTE=GKSOLLSet the rate as the planned calendar days
RTE=K30551Store the value held against payroll constant 30551 in table T511 in the rate field of wage type xxxx
RTE=KGENAURTE set to the value of GENAU from table T511K (default set at 10 000)
RTE=TADIVPRTE = Total working time measured in working days
RTE=TASOLLRTE = planned working time measured in work days
RTE=TKDIVIRTE = Total working time measured in calendar days
RTE=TKSOLLStore the planned calendar days in the rate field of the wage type being processed
RTE=TSAU07RTE = unpaid absence measured in working hours for counting class 07
RTE=TSDIVPRTE = total working time measured in working hours
RTE=TSSOLLRTE = planned working time measured in working hours
RTE=ZEROReduce the value in the amount field to zero
RTE-GKAU**Rate subtract the part period unpaid absences in calendar days for all unpaid absences (totalled over all absence counting classes)
RTE-TAAU**Rate subtract the part period unpaid absences in working days for all unpaid absences (totalled over all absence counting classes)
RTE-TKAU**Take away any unpaid absence, in calendar days, from the current rate (totalled over all absence counting classes)
RTE-TKAU20Take away any unpaid absence, in calendar days, from the current rate (for absence counting class 20)
RTE-TSAU**Take away any unpaid absence, in worked hours, from the currently held rate (totalled over all absence counting classes)
SCOND=F IFThe condition for function IF is false
SCOND=T ALSet condition for Function LPBEG when the condition is true
SCOND=T IFThe condition for function IF is true
SCOND=T IFThe condition for function IF is true
SETIN A=01Set the work center - basic pay split for the wage type as 01
SETIN R=1Set the ESG for PCR as 1
SETIN X=NXYou want to set X with number 01 as a variable split; the number of the split is to be increased by 1 by every call.
STATU 2PStatus field 2 which is valid at the start of the in-period is entered in the variable key.
SUBRC?SETThe return code set in the second example must be evaluated.
SUBRC=0The internal return code is set to the value 0
SUBWT *Subtracts the current wage type - effectively changing the sign of the NRA.
SUBWT 1025Subtracts the current wage type (signs change) and stores it as 1025.
SUBWT&ZREGSubtracts the current wage type and stores it as a temporary variable ZREG.
SUBWTD*Subtracts the current wage type (sign change) of the NRA in the difference table (DT)
SUBWTD/551Subtracts the current wage type and stores it in the difference table (DT) as a temporary variable ZREG.
SUBWTEFlicks the sign for NRA of the currently processed wage type and stores it in the RT
SUBWTE*Subtracts the current wage type (sign change) of the NRA and stores in the results table (RT)
SUBWTE/121Flicks the sign for NRA of the currently processed wage type and stores it in the RT as technical wage type /121
SUBWTI*Flicks the sign for NRA of the currently processed wage type and stores it in the input table (IT)
SUBWTI/101Flicks the sign for NRA of the currently processed wage type and stores it in the input table (IT) as technical wage type /101
TABLE 503Table query on employee groupings / areas
TABLE 508ATable query on shifts / time groups
TABLE 510PTable query on premium table
TABLE 512WTable query on valuation of wage types
TABLE 528BTable query on positions table in PA
TABLEALPTable query on the Alternative Payments table
TABLEP0014Table query on data held in infotype 0014 - recurring payments and deductions
TABLEP0015Table query on data held in infotype 0015 - additional payments
VAKEYALZNRPlace in the variable key - Y/N alternative payment
VAKEYAUFKZPlace in the variable key - extra pay indicator for overtime
VAKEYBNKSAPlace in the variable key - variable keys are held in a certain table
VAKEYBNKSAPlace in the variable key - type of bank details P0009
VAKEYLGARTStore in the variable key the wage type
VAKEYLNCLSPlace in the variable key - loan type
VAKEYLNTPYPlace in the variable key - loan type P0045
VAKEYLNTYPPlace in the variable key - loan type P0045
VAKEYPAYTYPlace in the variable key - payroll type
VAKEYPRAKNPlace in the variable key - premium indicator time ITs
VAKEYTGRLEPlace in the variable key - variable key is filled out based on the values in the TRFGR and TRFST fields from the current PZ record
VAKEYVERSLPlace in the variable key - clearing key for overtime
VAKEYZEINHPlace in the variable key - time unit
VAKEYZLSCHPlace in the variable key - payment key for bank transfers
VALBS?The system checks to see whether a valuation base exists
VALBS?0The system checks if a valuation basis is for the current wage type in table T512W. (That the "0" line of view V_T512_B is read).
VALBS0The current wage type is evaluated with the valuation basis that is entered for the current wage type itself. (That is, the "0" line of view V_512W_B).
VALBS0 *The system multiplies an entry that already exists in the RTE field for the current wage type with the percentage rate from a line 0 of view V_512W and then replaces the wage type names of the current wage type with the name of the wage type from the same line in V_512W.
VALBS0 BSame as VALBS0 * with the exception that the data from infotype 2010 is used.
VALBS1Replaces the current wage type with the statement wage type that is entered in table T512W for the second wage type derived from the current wage type, and then you want to valuate this using the corresponding valuation basis.
VALEN 2Sets the length of the variable key to 2
VALEN 3Sets the length of the variable key to 3
VAOFF 2Variable offset - set here to 2. The system with then ignores the first 2 digits.
VARGBINDBWPlace the table field "indicator for indirect valuation" in the variable key
VARGBPRAKNPlace the table field "premium number" in the variable key
VARGBTRFKZPlace the table field "ES grouping for collective agreement provision" in the variable key
VWTCL 64Interrogate processing class 64
WGTYP?Usually part of a decision - where the wage type is queried
WGTYP=*Passes through the wage type as unchanged
WPALL?LASTDecide if employee has had a pay change in pay period & if the one being processed is the last
WPBPCOperation WPBPC distributes the amount of the current wage type to the active WPBP periods in the payroll period.
WPBPCWThis operation splits the amounts but does not distribute them to the different periods
ZExpect to call another PCR in this line
ZERO= ANSets the AMT and NUM to zero
ZERO= RNASet the values for the rate, number and amount equal to zero
ZERO=& ABCDInitialises the variable ABCD
ZERO=NRASets the NUM RTE and AMT to zero

Wednesday, 30 May 2012

INAL SUB SCHEMA

THIS SUB SCHEMA IS IMPORTANT
SO TRY TO UNDERSTAND ITS BEHAVIOUR IN  PAYROLL


Friday, 18 May 2012

OM questions

1.what is organizational plan
2.what is plan version
3.what is organizational structure
4.how many objects have you created
5.what are the Om info types did you maintain
6.what are the relationships have you maintained
7.what is the t.code to see relationships
8.what is the  t.code to see Om info types
9.what is the t.code to see objects
10.what are the interfaces do you use to create org.structure
11.what is evaluation path
12.what is the difference between evaluation path to reporting structure
13.how do we wind up a department
14.what is delimit
15.what is the t.code to create plan version
16.what is the t.code to set plan version
17.do we transport om objects
18.in which method do we create work centre
19.what are om table names do you know
20.What is A012
21.what is the t.code to copy objects from one plan version to another plan version
22.what are Rhinte00,10,20 and 30
==================================

1 ) What is the Difference between "Evaluation Paths and relationships "

An evaluation path describes a relationship chain that exist in a hierarchical structure between the objects (eg: O-S-P ). Relationship(1001) is an infotype generally applicable between two objects.
2) How many cost centers can we assign to a org unit ?
Generally we can assign only one cost center. It always refers to parent cost center.
3) What is difference between - Simple maintainence and Expert Mode?
Both the interfaces are used to create Org structure. If the company needs to create a huge structure, we will use Simple maintenance, because it is user friendly that is it is easy to create a structure, the system automatically relationship between the objects. Using Infotypes we can create Objects in Expert mode and we have to use different transactions to create various types of objects.
4) What could be a possible structure of a org unit, exg - if a organisation has branches in 34 countries and head quarters being in london, and having a work center or branch in bangalore, how do we relate sitting in banglaore to London mother company?
This can be done by Enterprise structure that is Personnel Area and Various Personnel Sub areas.
5) How many Company codes can a company can have at a time?
Any number.
6) How can one know if a position is vacant or occupied in a company?
We can identify the vacancy position in IT1007.
7) Can a junior employee report to 4 different supervisors, if yes, how?
There will be only one supervisor for a employee to report. In case of concurrent employement the employee can report to corresponding Administrator.
8) What is the difference between " Job and Position"?
Job is not a concrete, it is General holding various task to perform.(Eg: Manager, GM).
Position is concrete and specific which are occupied by Persons. (Eg: Manager - Hr, GM - Hr).
9) What are the infotypes in OM - Please this is important
From 1000 to 1999.
10) What can a end user do in OM - if he can face a problem where can he face a problem ?? In regular intervals?
Creation of various objects like O,S,P,C,A. Creation of Org Structure.
11) How do you assign a single person for two roles, Can we assign or not?
Roles is the combination of transactions, reports and other files. We can assign any number of roles to a person.
12) How do you report level 4 person to level 1 person?
By creating relationship between the objects.
13) What do you mean my a Task and where do you assign and How?
Task are the work to be peroformed by the employee. We can assign task to job or position which finally inherit to the holder that is employee.
14) What is an Org's assignment and Org'l Plan, what is the diff between them?
Org assig defines the PA,PSA,EE group, EE subgroup, Cost Center, Payroll area all the default assignment of the person.
Org plan is the structure of the Org.
15) How many structures are there in OM?
Be specific, if you want to know the various structures in HR, it is Org Structure, Enterprise Struc., Personnel Structure. If it is OM, We can create Org structure by using Org and Staffing interface, Expert mode, Simple Maintenance. We can create General Structure, Matrix.
16) What do you mean by reporting Structure?
Reporting structure is to view the reporting objects, that is who is reporting to whom.
17) What is the difff between Simple Maintenance and Detailed Maintenance? and which one you used in your project?
As already explained. Usage depends on the Company.
18) What are the buliding blocks in OM and where do you assign them?
There are totally five objects in building blocks of OM, that is O,C,S,P and Cost center. Using relationship we can assign them.
19) What do you mean by work centre and Cost center? Where do you assign them. And how many Cost centres can we assign? 
Cost center which controls and maintain the cost relevant activities of the company. It is controlled by FICO peoples. Work centers are the exact work location of the employee where the company doing the daily transactions.
20) How do you transfer Org'l Assignment from PA to PD(Answer for this is a bit diff, try it) you can maintain Org Assign using the IT0001.
21) What are the infotypes you used in OM?
As already explained from 1000 to 1999.
22) What is the Tcode to maintain the Standard roles?
Tcode: PFCG
23) What is the Tcode to Change the Standard roles?
Same Tcode : PFCG
24)What is the Tcode to Manintain the Org'l Plan.
It is depend on the interface you are using that is PPOME,PO10,PPOC_OLD, PP01. 

Thursday, 17 May 2012

info type number ranges


info type number ranges
0000--0999====>personnel administration or   HR master data
1000--1999===> Organizational management and planning  
2000--2999==> Time management  
4000--4999===> Recruitment  
5000--5999===>Web enabled  ---i.e. E recruitment, E-com,E-benefits
9000--9999===>Custome specific abap hr--(pm01)  
             

Organizational Management info types



OM INFOTYPES
1000 Object
1001 Relationships
1002 Description
1003 Department/Staff
1007 Vacancy T.code==>ooit
1008 Acct. Assignment Features Table==>T778T
1018 Cost Distribution
1019 Quota planning
1050 Job Evaluation Results
1051 Survey Results