SAP Function Modules

Share |

HR_INFOTYPE_OPERATION SAP Function module - HR INFOTYPE OPERATION

Pattern for FM HR_INFOTYPE_OPERATION - HR INFOTYPE OPERATION
Associated Function Group: HRMM
Released Date: Not Released
CALL FUNCTION 'HR_INFOTYPE_OPERATION' "
  EXPORTING
    infty =                     " prelp-infty
    number =                    " p0001-pernr
*   subtype =                   " p0001-subty
*   objectid =                  " p0001-objps
*   lockindicator =             " p0001-sprps
*   validityend =               " p0001-endda
*   validitybegin =             " p0001-begda
*   recordnumber =              " p0001-seqnr
    record =                    "
    operation =                 " pspar-actio
*   tclas = 'A'                 " pspar-tclas
*   dialog_mode = '0'           " c
*   nocommit =                  " bapi_stand-no_commit
*   view_identifier =           " p0003-viekn
*   secondary_record =          "
  IMPORTING
    return =                    " bapireturn1
    key =                       " bapipakey
    .  "  HR_INFOTYPE_OPERATION

SAP Documentation for FM HR_INFOTYPE_OPERATION


FUNCTIONALITY

This function module enables you to maintain master data for employees and applicants. You can transfer one data record. All validation checks take place that would take place in the individual maintenance screens in the dialog. If necessary, the module returns an error message. The error messages are the same as the error messages in the dialog, that is, the individual maintenance screen error messages are transferred rather than interpreted by this module.


EXAMPLE


HINTS
The update takes place using a 'Call dialog' from the module pool infotypes. For this reason, some restrictions apply for the infotypes that are to be handled in this way.
  • The screens for individual infotypes can not overwrite the transferred data for PBO.

  • No essential checks that are programmed 'on request' will be included in the module, as these will not run.

  • No messages can be processed for PBO. This will lead to error message 428(PG).

  • No 'leave screens' may be programmed, unless 'set screen 0' has been set previously. This also leads to error message 428(PG).

  • If you receive error messages of type 'Required field not filled...', you can not specify the field any more precisely. In this case, you must try to transfer the data into the system using the dialog transaction.
    Documentation extract taken from SAP system, Copyright (c) SAP AG






    Share |