Infotype 2010 Cost Assignment System

PA2010 is a SAP table coming under PT module and SAP_HRRXX component.View details, Fields & related tables of PA2010.

  • Table description : HR Time Record: Infotype 2010 (Employee Remuneration Info.)
  • Module : PT
  • Parent Module : PT
  • Package : PTIM
  • Software Component : SAP_HRRXX

PA2010 Fields structure

FieldNoteData ElementDomain
MANDTClientMANDTMANDT
.INCLUDEKey for HR Master Data
PERNRPersonnel numberPERSNOPERSNO
SUBTYSubtypeSUBTYSUBTY
OBJPSObject IdentificationOBJPSOBJPS
SPRPSLock Indicator for HR Master Data RecordSPRPSSPRPS
ENDDAEnd DateENDDADATUM
BEGDAStart DateBEGDADATUM
SEQNRNumber of Infotype Record With Same KeySEQNRNUM03
.INCLUDEHR Master Record: Control Field
AEDTMLast Changed OnAEDATDATUM
UNAMEName of Person Who Changed ObjectAENAMUSNAM
HISTOHistorical Record FlagHISTOCHAR1
ITXEXText Exists for InfotypeITXEXXFELD
REFEXReference Fields Exist (Primary/Secondary Costs)PRFEXXFELD
ORDEXConfirmation Fields ExistORDEXXFELD
ITBLDInfotype Screen ControlITBLDCHAR2
PREASReason for Changing Master DataPREASPREAS
FLAG1Reserved Field/Unused FieldNUSEDNUSED
FLAG2Reserved Field/Unused FieldNUSEDNUSED
FLAG3Reserved Field/Unused FieldNUSEDNUSED
FLAG4Reserved Field/Unused FieldNUSEDNUSED
RESE1Reserved Field/Unused Field of Length 2NUSED2NUSED2
RESE2Reserved Field/Unused Field of Length 2NUSED2NUSED2
GRPVLGrouping Value for Personnel AssignmentsPCCE_GPVALPCCE_GPVAL
.INCLUDEHR Time Record: Infotype 2010 (Employee Remuneration Info.)
BEGUZStart TimeBEGTIUZEIT
ENDUZEnd TimeENDTIUZEIT
VTKENPrevious Day IndicatorVTKENXFELD
STDAZNo.of hours for remuneration info.ENSTDJRSTD
LGARTWage TypeLGARTLGART
ANZHLNumber per Time Unit for EE Remuneration InfoENANZANZHL
ZEINHTime/Measurement UnitPT_ZEINHRPMSH
BWGRLValuation Basis for Different PaymentPTM_VBAS7SP_AMT07V
AUFKZExtra Pay IndicatorAUFKNAUFKN
BETRGWage Type Amount for PaymentsPAD_AMT7SP_AMT07V
ENDOFIndicator for final confirmationENDOFRFERTL
UFLD1User fieldUSFLDCHAR1
UFLD2User fieldUSFLDCHAR1
UFLD3User fieldUSFLDCHAR1
KEYPRNumber of Infotype Record with Identical KeyKEYPRSEQNO
TRFGRPay Scale GroupTRFGRTRFGR
TRFSTPay Scale LevelTRFSTTRFST
PRAKNPremium NumberPRAKNPRAKN
PRAKZPremium IndicatorPRAKZPRAKZ
OTYPEObject TypeOTYPEOTYPE
PLANSPositionPLANSPLANS
VERSLOvertime Compensation TypeVRSCHVRSCH
EXBELExternal Document NumberEXBELCHAR08
WAERSCurrency KeyWAERSWAERS
LOGSYSLogical systemLOGSYSLOGSYS
AWTYPReference procedureAWTYPAWTYP
AWREFReference document numberAWREFAWREF
AWORGReference organisational unitsAWORGAWORG
WTARTWork tax areaWTARTWRKAR
.INCLUDEInfotype Fields Relevant for Short Descriptions
TDLANGUDefinition Set for IDsTMW_TDLANGUTMW_TDLANGU
TDSUBLADefinition Subset for IDsTMW_TDSUBLATMW_TDSUBLA
TDTYPETime Data ID TypeTDTYPETDKENN

PA2010 related tables

TableNote
AFRUHROrder Confirmations for HR
ASSHRAssignment of HR to AFRU/ASSOB
ASSOBAssignment Objects
CC1ERHIncorrect Time Events from CC1, Header Information
CC1ERMIncorrect Time Events from CC1, Error Messages
CC1ERPIncorrect Time Events from CC1, Postings
CC1PARCommunication Parameters
CC1TEVTemporary Buffer for Time Events from CC1
CC2TIMTable of Planned Changes: HR Actual Times for CC2 Available
COIFTInterface to Activity Allocation
HRAAERRError Table for Activity Allocation Documents in HR
HRAAHDRHR Interface Table: Document Header for Activity Allocation
HRAAITMHR Interface Table: Document Item for Activity Allocation
HRCCE_T_QR_PAIRSCE Shared Quotas : Grouping Rules for Different Quota Types
HRESSAPPROVERStore Last Approver to be Chosen
P0ASBAssignment Subsystem -> PDC Group
PA0005HR Master Record: Infotype 0005 (Leave Entitlement)
PA0007HR Master Record: Infotype 0007 (Planned Working Time)
PA0050HR Master Record: Infotype 0050 (Time Recording)
PA0080HR Master Record: Infotype 0080 (Maternity Protection)
PA0081HR Master Record: Infotype 0081 (Military Service)
PA0082HR Master Record: Infotype 0082 (Additional Absence Data)
PA0083HR Master Record: Infotype 0083 (Leave Compensation)
PA0416Time Quota Compensation Infotype: Database Table
PA2001HR Time Record: Infotype 2001 (Absences)
PA2002HR Time Record: Infotype 2002 (Attendances)
PA2003HR Time Record: Infotype 2003 (Substitutions)
PA2004HR Time Record: Infotype 2004 (Availability)
PA2005HR Time Record: Infotype 2005 (Overtime)
PA2006HR Time Record: Infotype 2006 (Absence Quotas)
PA2007HR Time Record: Infotype 2007 (Attendance Quotas)
PA2010HR Time Record: Infotype 2010 (Employee Remuneration Info.)
PA2012HR Time Record: Infotype 2012 (Time Transfer Specifications)
PA2013HR Time Record: Infotype 2013 (Quota Corrections)
PA2500HR Master Record for Infotype 2500
PA2501HR Master Record for Infotype 2501
PA2502HR Master Record for Infotype 2502
PA3355HR Master Record Infotype 3355
PTEX2000Interface Table for Attendances/Absences Infotype(2001/2002)
PTEX2003GENInterface Table for IT 2003: General Information
PTEX2003SPECInterface Table for IT 2003: Interval Information
PTEX2010Interface Table for EE Remuneration Info. Infotype (2010)
PTEXDIRInterface Table for Infotypes (Directory Table)
PTIMEOV1Overview of an Employee's Time Data, Part 1
PTIMEOV2Overview of an Employee's Time Data, Part 2
PTMLEACONVAssignment Table IT0005 - IT2006 (RPTLEACONV Report)
PTQUODEDDeduction of Time Quotas
T508AWork Schedule Rules
T508SText Table for Work Schedule Rules (T508A)
T508TTexts for Employee Subgroup Groupings for Work Schedules
T508ZAssignment of PS Grouping for Work Schedules to Daily WS
T510IStandard Working Hours
T510PPremium Table
T510STime Wage Type Selection
T510TPremium Texts
T510VCheck Table For Processing Types in T510S (WT Generation)
T510XWTs Permitted for Transfer from Time Evaluation to MMS
T510ZTexts for Time Wage Type Selection Rules
T533Leave Types
T533TLeave Type Texts
T550ADaily Work Schedule
T550PBreak Schedules
T550SDaily Work Schedule Texts
T550XDaily Work Schedule Selection Rules
T551APeriod Work Schedules
T551CPeriod Work Schedule Valuation
T551SPeriod Work Schedule Texts
T552AMonthly Work Schedule
T552VDynamic Daily Work Schedule Assignment
T552WDynamic Daily WS Assignment: Planned/Actual Overlap
T553ADefinition Rules for Day Types
T553SDay Types for Special Days
T553TDay Type Texts
T554ABreakdown of Absences After Quota Deduction
T554CAbsence Valuation
T554DMilitary Service Ranks
T554ECounting Classes for Absence Valuation
T554FCounting Classes for Absence Valuation
T554GTypes of Birth
T554HEvaluation Type for Attendances/Absences
T554HTEvaluation Type for Attendances/Absences: Texts (for T554H)
T554LAbsence Valuation Rules
T554MAbsences for Maternity Protection: Rule Table
T554NTexts for Day Rules
T554OValuation Classes
T554PSymbols for Attendances and Absences (Calendar)
T554QAssignment of Valuation of Absences
T554RDay Rules for Absence Valuation
T554SAttendance and Absence Types
T554S_ESSEXESS: Deactivation of Attendance/Absence types
T554TAbsence and Attendance Texts
T554VDefaults for Absence Types
T554WPeriods of Military Service
T554XRules for Attendance/Absence Counting and Leave Deduction
T554YTime Constraints in HR TIME
T5550[OBSOLETE; NOW USE T705Q] Ext. Wage Types from Subsystem Txt
T555ATime Types
T555BTime Type Texts
T555CPermitted PDC PIN Codes
T555D[OBSOLETE; NOW USE T705A] Abs./Attendance Reasons Subsystem
T555ETime Evaluation Messages
T555FTime Evaluation Error Texts
T555G[OBSOLETE; NOW USE T705H] Att./Absence Reasons Subssys. Text
T555HSite-Restricted Access Control Groups
T555IPDC Master Record Information
T555JTransfer to Time Types
T555KTransfer to Time Wage Types
T555LTransfer to Absence Quotas
T555MPDC Accounting Types
T555NEmployee Grouping for the Time Evaluation Rule
T555OAccess Control Groups (time-restricted)
T555PEmployee Time Transfer Type
T555QTexts for Time Transfer Type
T555ROvertime Compensation Types
T555TOvertime Compensation Type Texts
T555UEmployee Time Management status
T555VEmployee Status for Time Management: Texts
T555W[OBSOLETE; NOW USE T705K] Ext. Wages Types from Subsystem
T555XTexts for Access Control Groups (time-restricted)
T555YProcessing Type/Time Type According to Att./Absence Class
T555ZTime Type Determination
T556Substitution Types
T556AAbsence Quota Types
T556BAbsence Quota Type Texts
T556CCounting Rule for Attendances and Absences
T556DAbsence Counting With/Without Quotas Texts
T556ERule Group (Coverage Package)
T556FTexts for Rule Group (Coverage Package)
T556GRule for Day Markers in Coverage History
T556HTexts for Rule on Determining the Coverage History
T556MProcess Partial-Day Absences Using XNAB Function
T556PAttendance Quotas
T556QAttendance Quota Type Texts
T556RRules for Deduction Sequence for Absence Quotas
T556STexts for Deduction Sequence Rules for Absence Quotas
T556TSubstitution Type Texts
T556UAttendance/Absence Quota Compensation Types
T556VTexts for Attendance/Absence Quota Compensation Types
T556WWage Type Assignment for Att./Absence Quota Compensations
T557Availability Types
T557TAvailability Types Texts
T559AWorking Weeks
T559BWorking Week Texts
T559DValidity/Deduction Interval for Absence Quotas
T559EBase Entitlement for Leave Accrual
T559FProcessing of Absence Quota Remainders
T559GQuota Generation: Rule for Transfer Times
T559HQuota Generation: Text for Transfer Times Rule
T559JConvert Leave Types to Quota Types
T559LAutomatic Absence Quota Generation
T559MReduction Rules for Absence Quota Generation
T559NTexts for Reduction Rules for Leave Accrual
T559PLimits for Time Balances
T559QTexts for Time Balance Limits
T559QTTransfer Remaining Quota to New Quotas
T559RRounding Rules
T559STexts for Rounding Rules
T559TTexts for Leave Accrual Rule
T559UOvertime rules
T559VValidity Period: Absence Quotas for Default Values
T559WText Table for Time Evaluation Classes
T559XEvaluation Classes for Times (Internal Table TIP)
T559YText Table for Conditions for Employee Times
T559ZConditions for Employee Times in Time Evaluation
T569BArchiving Information for Cluster B2
T569REarliest Recalculation Dates for Time Management
T569WTexts for Recalculation Categories
T572BIllness Texts
T572EControl table for additional absence data
T572FEvent Texts
T572GPermitted Values for Events
T572HEvent Value Texts
T582ZControl Table for PA Time Management
T588NScreen Modification for Account Assignment Block
T588OScreen Modification for Assignment Data
T589ZF Status of Each Module Pool and Screen
T599YConvert External Wage Types
T599ZTime Wage Types to Third-Party Systems
T7050Time Management: Communication Times
T705AAttendance/Absence Reasons for Subsystem
T705BPDC Processing Statuses
T705EReaction to Error Transaction
T705FWork Time Event Type Groups
T705GTexts for Work Time Event Type Groups
T705HAttendance/Absence Reason Texts for Subsystem
T705IAbsence/Attendance Reason Grouping
T705JGrouping for External Wage Types
T705KExternal Wage Types for Subsystem
T705LIndicator: Attendance/Absence Reason
T705MIndicator: External Wage Types Grouping
T705PWork Time Event Type Groups
T705QExternal Wage Types Long Texts from Subsystem
T77TIM_AQGRPAbsence Quota Groups
T77TIM_AQGRPTAbsence Quota Groups Description
TEVENTime Events
TEVEN_MOREAdditional Data for Time Events
TEXLGAEmployee Expenditures
TOBAETransfer Times: Control Station Communication
TOPRKLog Messages
TPTEXTAPPExternal Application
TPTEXTAPPTText Table for External Applications
TPT_EVENTATTRPair Formation: Characteristics of Time Event Types
TPT_PAIRSTAT2Pair Formation: Status Table
TPT_SLIPSTATETime Ticket Generation: Status Table

PA2010 related transaction codes

TcodeNote

If you have only ever worked with one SAP system, you may not realize that there are some basic settings/switches that underscore and drive how SAP behaves.  I recently worked with a client that had been jumping through hoops to make SAP behave differently for years.  A simple switch in Table T77S0 was able to fundamental change SAP to simply work as required preventing hours of repeated manual work and customizations.

Below are the most common switches in table T77S0 that I have found handy in my experience in Organizational Management and Personnel Administration, along with the SAP definitions and my personal recommendations. 
By no means is this a comprehensive list, however hopefully at least one on here there that will challenge the way you think about how SAP can work.

PPOM Switches

PPOM CCODE

Maintain Cost Distribution (IT1018) Using Company Code

In infotype 1018 (Cost Distribution), cost centers are maintained as standard by entering the cost center and controlling area. However, restrictions may arise if cost accounting is activated in Controlling for multiple company codes. If this is the case, the system only allows data to be posted to the cost center’s company code. You cannot post data to any company code for the controlling area.

Switch PPOM CCODE allows you to change the standard behavior:

  • If the switch is set (PPOM CCODE = X), the cost center is maintained in infotype 1018 according to the company code and controlling area entered. In the case of cost accounting for multiple company codes, you can enter any company code (that belongs to the cost center’s controlling area).
  • If the switch is not set (PPOM CCODE 0 ‘ ‘), the standard behavior applies.

PPOM EXTCK

In the Simple maintenance view, you can use the entry PPOM EXTCK to determine, when delimiting or deleting an organizational unit or a position, whether:

  • the system should generate an error message pointing out that the subordinate objects must first be moved, deleted or delimited
    • For this option, enter the value ‘X’.
    • direct modification of the assignment of subordinate objects should  be possible
      • For this option, enter the value ‘ ‘.

This setting affects the following relationships:

  • Organizational unit
    • Organizational unit
    • Position
    • Cost center
    • Position
      • Person
      • User
      • Business partner

PPOM INHIC

Obligatory Inheritance of Company Code

This entry enables you to determine if a company code must be passed from organizational units to lower-level positions.

  • If the inheritance should be obligatory, enter the value ‘X’.
  • If the inheritance should not be obligatory (meaning it can be assigned at the positions level if different) enter the value ‘ ‘.

NOTE: It is not recommended to set obligatory inheritance of Company Code unless only 1 Company Code will be used for all positions.

PPOM   INHIH

PPOM: Obligatory Inheritance of Contr. Area

This entry enables you to determine if a controlling area must be passed from organizational units to lower-level positions.

  • If the inheritance should be obligatory, enter the value ‘X’.
  • If the inheritance should not be obligatory (meaning it can be assigned at the positions level if different) enter the value ‘ ‘.

Note: It is not recommended to set obligatory inheritance of Controlling Area unless only 1 Controlling Area will be used for all positions.

PPOM INHS

This entry enables you to determine that account assignment features   (controlling area, company code, and business area) are passed from organizational units to lower-level positions.

  • In the standard system, inheritance is deactivated (value ‘ ‘).
  • If you want to activate inheritance, enter the value ‘X’.

It is recommended to activate inheritance.

PPOM LEPER

In the Simple maintenance view, you can use the entry PPOM LEPER to specify:

  • that all chiefs in an organizational unit should be displayed.
    • For this option, enter the value ‘X’.
    •   that only the current (key date) chief or the next future chief of  an organizational unit should be displayed
      • For this option, enter the value ‘ ‘.

PLOGI Switches

PLOGI BSPAY

Integration switch for planned compensation – basic pay

The “PLOGI BSPAY” entry activates integration between planned compensation and basic pay.

If integration is active, planned compensation data (type, area, group, level) is transferred as defaults to the appropriate infotype field when a basic pay record is created.

Input values:

  • ‘X’ Integration active
  • ‘ ‘ Integration deactivated

PLOGI COSTD

The PLOGI COSTD entry enables you to activate integration between Organizational Management and Personnel Administration for cost distribution.

To activate integration, enter the value “X”.

PLOGI COSTI

Integration switch for cost center accounting

The entry “PLOGI COSTI” activates integration between cost planning and cost center accounting. If integration is active, a check is carried out to see if the G/L accounts and cost types exist in CO. A plan scenario can only be released if integration is active.

Input values:

  • ‘X’ Integration active
  • ‘ ‘ Integration not active

PLOGI EVCCC

Master Data Action for Change of Company Code

This entry enables you to determine the action that is executed next for all of the employees who have changed company code and are flagged in table T77INT.  See the documentation on ‘PLOGI EVENB’.

PLOGI EVENB

Enhanced Integration (‘X’=on, Space=off)

Setting the ‘PLOGI EVENB’ switch to ‘X’ enables you to move a person, position or organizational unit within an organizational structure, when these changes lead to a change in company code for the person(s) concerned.

The personnel numbers of the person(s) concerned are locked in Personnel Administration. The only personnel action you can now carry out for these personnel numbers is “Organizational Change”. You must carry out this action before you can make further changes to the infotypes for the person(s) concerned. Technically, the lock is caused by an entry in table T77INT.    Note that this switch only works when the ‘PLOGI ORGA’ switch is switched to ‘X’.

Further notes:  If you do not set the ‘PLOGI EVENB’ switch, you cannot move a person when the move involves a change of company code, and an error message appears.

PLOGI ORGA

Integration Switch: Organizational Management/HR Master Data

The entry PLOGI ORGA activates integration between Organizational Management and Personnel Administration using the “Organizational Assignment” infotype (0001).

Active Integration allows you to:

  • transfer changes made to Organizational Management objects (organizational units, jobs, positions, cost centers), that are relevant to integration, to Personnel Administration
  •  transfer changes made to the organizational assignment of employees  (IT 0001) from Personnel Administration to Organizational Management
  • Options are
    •   ‘X’ for ON
    •  ‘ ‘ for OFF

In addition, you must specify the integration plan version in the entry  PLOGI PLOGI.

PLOGI PLOGI

Integration Plan Version

Using this entry you determine the active integrated plan version for the Organizational Management, Personnel Development, Personnel Cost   Planning, Personnel Shift Planning, and Training and Event Management components.

If this entry is ‘ ‘ (switch = “off”), integration is deactivated. When you determine a plan version, integration is activated within this plan  version for all persons that correspond to the ‘PLOGI’ feature.

Note: To activate integration between Organizational Management and Personnel Administration using the “Organizational Assignment” infotype (0001), you must enter ‘X’ in “PLOGI ORGA”.

PLOGI PRELU

Integration: Update Online or Batch Input

If the value entered here is ‘BTCI’ and integration has been activated (see PLOGI PLOGI), you prevent changes made in Organizational Management from being written directly to Personnel Administration (“Organizational Assignment” infotype 0001). The personnel numbers affected by the change are simply collected so that they can be written to the batch input at a later stage. See also the documentation on report RHINTE30.

  • If the value entered here is ‘ ‘ or ‘0’, the change will be transferred immediately.
  •  If the value entered here is a numeric value, the system checks to find  out how many personnel numbers are affected by a change made in Organizational Management. If the number of personnel numbers is larger than the numeric value entered, the system proceeds as for the entry  ‘BTCI’, otherwise as for ‘ ‘ or ‘0’.

PLOGI SPLIT

Integration: New Infotype 0001 Record When Description Is Changed

If the value entered is ‘X’ and you change the description of positions, jobs or organizational units, new infotype 0001 records for the personnel numbers concerned are created on the date of the change(s).

This means that the system will always display the up-to-date descriptions of named objects, both in Personnel Administration transactions and in reports on persons.

If the description of an object is changed on a particular date (as of Release 4.5, this is done in Organizational Management by copying a record from infotype 1000, “object”), the system first establishes which personnel numbers are affected by this, and marks them internally. Then, you should use report RHINTE30 (parameter “Open Personnel Numbers Only”) to create a batch input session. After this session has been processed, new infotype 0001 records for the person(s) concerned are created.  If the field PLOGI SPLIT is blank, the system only creates new infotype 0001 records if the assignment itself (that is, the number of the position, job or organizational unit) changes.

PLOGI TEXTC

Integration: Transfer Short Text of Job

This entry specifies whether the short text or the long text of a job should be transferred from Personnel Planning to Personnel Administration.

  • ‘X’:  Transfer short text of job to Personnel Administration
  • ‘ ‘:  Transfer long text of job to Personnel Administration

A text that has been transferred to Personnel Administration in this way is displayed in the Organizational Assignment infotype (0001) of the  affected persons.

If Personnel Administration and Personnel Planning are integrated, the switch has the following meaning:

When these switches are active (value = ‘X’), the text of the PA object is transferred to the Object ID field of the PD object when report  RHINTE00 is run and, if necessary, the text is shortened to 12 characters. If these switches are not activated (value = ‘ ‘), the object ID of the PD object is transferred to the Object ID field when report RHINTE00 is run.   See RHINTE00.

PLOGI TEXTO

Integration: Transfer Short Text of Organizational Unit

This entry specifies whether the short text or the long text of an organizational unit is to be transferred from Personnel Planning to Personnel Administration.

  • ‘X’:  Transfer short text of org.unit to Personnel Administration
  • ‘ ‘:  Transfer long text of org.unit to Personnel Administration

A text that has been transferred to Personnel Administration in this way  is displayed in the Organizational Assignment infotype (0001) of the affected persons.

If Personnel Administration and Personnel Planning are integrated, the switch has the following meaning:

When these switches are active (value = ‘X’), the text of the PA object is transferred to the Object ID field of the PD object when RHINTE00 is run. If necessary, the text is shortened to 12 characters. If these switches are not active (value = ‘ ‘), the object ID of the PD object is transferred to the Object ID field when RHINTE00 is run.  See RHINTE00.

PLOGI TEXTS

Integration: Transfer Short Text of Position

This entry specifies whether the short text or the long text of a position should be transferred from Personnel Planning to Personnel Administration.

  • ‘X’:  Transfer short text of position to Personnel Administration
  •  ‘ ‘: Transfer long text of position to Personnel Administration

A text that has been transferred to Personnel Administration in this way is displayed in the Organizational Assignment infotype (0001) of the affected persons.

If Personnel Administration and Personnel Planning are integrated, the switch has the following meaning:

When these switches are active (value = ‘X’), the text of the PA object is transferred to the Object ID field of the PD object when RHINTE00 is run. If necessary, the text is shortened to 12 characters. If these switches are not active (value = ‘ ‘), the object ID of the PD object is transferred to the Object ID field when RHINTE00 is run.  See RHINTE00.

Like this:

LikeLoading...

This entry was posted in Talk Techie to Me. Bookmark the permalink.

One thought on “Infotype 2010 Cost Assignment System

Leave a Reply

Your email address will not be published. Required fields are marked *