PTManagerExtAttAbs

The Business Object Manager for External Attendances/Absences
takes evaluated time data from an external system and transfers it to the Attendances (2002) or Absences
infotypes (2001) in SAP HR Time Management.

Structure

Time data is first stored in the interface table for Attendances/Absences 2001/2002 (PTEX2000) and the interface table for
infotypes (directory table) (PTEXDIR). Here the time data is posted to the Attendances (2002) and Absences (2001) infotypes.

Information on cost assignment and activity allocation can be provided along with the time data.

Integration

If time data from external time recording systems is to be posted to the EE Remuneration Info infotype (2010) in
SAP HR Time Management, use the Business Object BUS 2012 Manager for External Employee Remuneration Specifications
.

Available Methods

• Check : Check attendance/absence w/o acct assgmnt [ BAPI_PTMGREXTATTABS_CHECK ]
  
• CheckCollision : Collision check [ BAPI_PTMGREXTATTABS_CHECKCOLLI ]
  
• CheckQuota : Check quota deduction [ BAPI_PTMGREXTATTABS_CHECKQUOTA ]
  
• CheckWithActivityAllocation : Check attendance/absence with activity allocation [ BAPI_PTMGREXTATTABS_CHECKWACT ]
  
• CheckWithCostAssignment : Check attendance/absence with cost allocation [ BAPI_PTMGREXTATTABS_CHECKWCOST ]
  
• Insert : Insert attendance/absence w/o acct assgmnt [ BAPI_PTMGREXTATTABS_INSERT ]
  
• InsertWithActivityAllocation : Insert attendance/absence with activity allocation [ BAPI_PTMGREXTATTABS_INSERTWACT ]
  
• InsertWithCostAssignment : Insert attendance/absence with cost allocation [ BAPI_PTMGREXTATTABS_INSWCOST ]
  

Check

This method performs a plausibility check on evaluated time data from external time management systems in the Absences (2001) and Attendances (2002) infotypes.

Notes

Executing this method is option. It is carried out when transferring data to the SAP R/3 System.

This method also checks any information on different (alternative) payment.

No cost assignment or activity allocation is supported for this method.

CheckCollision

This method checks if the time data records from an external timemanagement system will collide with the time data records in the R/3 System.

The R/3 System is checked to see if a time data record exists in thesame time period. This checks both the time-related records created, as well as the records created for full days.

Notes

The data to be checked is stored in the EXTERNALRECORDS parameter. Thedata records for which a collision occurs in the R/3 System are returned in the COLLISIONRECORDS parameter.

If values exist in the EXTSYSTEM and EXTAPPLICATION fields then the infotype records are not included with this external key.

Records for full-days and multiple days must have the ALL_DAY_FLAG selected in EXTERNALRECORDS.

The message type determines the type of error messages.

CheckQuota

This method can simulate quota deduction. In this way, you can check ifthe remaining quotas in the R/3 System is sufficient prior to posting an absence from an external time management system.

The actual deduction occurs when the attendance/absence is posted in the R/3 System.

CheckWithActivityAllocation

This method performs a plausibility check on the evaluated time data from external time management systems in the infotypes Absences (2001) and Attendances (2002). The data related to activity allocation is also checked.

Notes

Executing this method is optional. It is carried out when transferring data to the SAP R/3 System.

method

BAPI: Inserts External Attendance/Absence in Interface Table (with Activity Allocation) and
then stored in the interface tables PTEX2000 and PTEXDIR.

Notes

This method checks information on different payment.

No cost assignment is checked with this method.

CheckWithCostAssignment

1

Functionality

This method performs a plausibility check on the evaluated time data from external time management systems in the infotypes Absences (2001) and Attendances (2002). Data related to cost assignment is also checked.

Notes

Executing this method is optional. It is carried out when transferring data to the SAP R/3 System.

This method checks information on different (alternative) payment.

This method does not support activity allocation.

1

Example

1

Notes

Insert

This method transfers evaluated time data from external time managementsystems to the SAP R/3 System. The time data is then stored as attendance or absences.

Information on different payment is also transferred.

Notes

This method stores the data records in the interface tables PTEX2000 and PTEXDIR. Then, the report RPTEXTPT (External
Transfer -> Time Management reads the data from PTEX2000 and stores it as Attendances in infotype 2002 or asAbsences in infotype 2001.

Neither cost assignment nor activity allocation is supported with this method.

The method

BAPI: Checks External Attendances/ Absences (without Account Assignment) and can check the data priorto transferring it for plausibility checks.

InsertWithActivityAllocation

This method transfers evaluated time data from external time management systems to the SAP R/3 System.

Information on different payment and activity allocation is also transferred.

Notes

This method stores the data records in the interface tables PTEX2000 and PTEXDIR. Then, the report RPTEXTPT (External
Transfer -> Time Management reads the data from PTEX2000 and stores it as Attendances in infotype 2002 or as Absences in infotype 2001.

No cost assignment is supported with this method.

The method

BAPI: Checks External Attendances/Absences in Interface Table (with Cost Assignment) and
check the data prior to transferring it for plausibility checks.

InsertWithCostAssignment

This method transfers evaluated time data from external time managemensystems to the SAP R/3 System. The time data is then stored as attendance or absences.

Information on different payment and cost assignment is also transferred.

Notes

This method stores the data records in the interface tables PTEX2000 and PTEXDIR. Then, the report RPTEXTPT (ExternalTransfer -> Time Management reads the data from PTEX2000 and stores it as Attendances in infotype 2002 or asAbsences in infotype 2001.

This method does not support activity allocation.

The method BAPI: Checks External Attendances/Absences (with Cost Assignment) and can check the dataprior to transferring to perform a plausibility check.