Simplify SAP R/3 development with Excel VBA/VB RFC  
Home> Bapi>PTMgrExtWorkSched




The business object manager for external operative planned working time
manages the planned working times of an external system and enters them in the Substitutions
infotype (2003) in HR Time Management.

When external time data enters the SAP System, it first supplies the interface tables for the Substitutions
infotype (2003). The time data is posted to the Substitutions infotype (2003) from the interface tables.



Available Methods

  • InsertWithCostAssignment : Insert operative planned time (with cost assignment) [ BAPI_PTMGREXTWOSCHED_INSWCOST ]




You can use this method to transfer data on an employee's operative planned working time from external systems to the SAP System.

You can use WORKSCHEDULE_GENERAL_INFO to enter the general data on aplanned working time in the SAP System's interface tables. You can use
parameter WORKSCHEDULE_INTERVALS to supply the SAP System with explicit planned working time intervals and breaks.

The following fields represent a unique document key for an operative planned working time:


  • If you have entered several clock-time intervals as operative plannedworking time for an employee on one day, the system uses the documentkey (EXTSYSTEM, EXTAPPLICATION, EXTDOCUMENTNO) to establish the link between the data.

    You can specify an operative planned working time for one day and a personnel number by specifying a line in parameter
    WORKSCHEDULE_GENERAL_INFO and by entering one or more lines in parameter WORKSCHEDULE_INTERVALS; the entries must match the line ofstructure WORKSCHEDULE_GENERAL_INFO in fields EXTSYSTEM, EXTAPPLICATION, and EXTDOCUMENTNO. All of this data is referred tocollectively in the following as a data block (for the operative planned working time).

    If you want to cancel a data block, field REVERSED of parameterWORKSCHEDULE_GENERAL_INFO must have the value "X". The system also automatically cancels all related data of parameterWORKSCHEDULE_INTERVALS, since the data is linked by means of the unique document key.

    The data block is the unit that can be cancelled as a whole. Forthe data block to be cancelled, the current method must be accessed;parameter WORKSCHEDULE_GENERAL_INFO must be filled with the fields that determine the data block, EXTSYSTEM, EXTAPPLICATION, and EXTDOCUMENTNO and field REVERSED of the same parameter must have the
    value "X". The system also cancels the related data for the data block that was specified in parameter WORKSCHEDULE_INTERVALS, that is, explicit planned working time intervals and breaks.

    You can transfer several data blocks to the system for each day
    and personnel number, that is, data records that have different entriesin at least one of the fields EXTSYSTEM, EXTAPPLICATION, and EXTDOCUMENTNO, but that relate to the same day and the same personnelnumber. In this case, the two data blocks must be compatible. This means that:

  • Fields DWS_GROUPING of parameter WORKSCHEDULE_GENERAL_INFO either haveidentical planned working times, or the field is initial for at least one planned working time. The same applies to field DAY_TYPE.
  • The field DAILYWORKSCHEDULE is not filled for either data block
    in structure WORKSCHEDULE_GENERAL_INFO, and the explicit plannedworking time intervals specified in parameter WORKSCHEDULE_INTERVALS do not overlap.
  • Several data blocks are entered in the interface table withoutbeing validated, for each day and personnel number; in the transfer process, data blocks
    that are not compatible with the existing records (including those that have already been transferred) receive anerror status and are not transferred.

    You can also transfer data on a different payment and cost assignment.


    This method stores the data records in the interface tables PTEX2003GEN, PTEX2003SPEC, and PTEXDIR. The data is then read from
    files PTEX2003GEN and PTEX2003SPEC by report RPTEXTPT (Transfer External Data -> Human Resources) andcreated as records of the Substitutions infotype (2003).