SAP Function Modules

comments icon Comments

HR_CC1_TIMEEVENT_POST SAP Function module







HR_CC1_TIMEEVENT_POST is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name HR_CC1_TIMEEVENT_POST into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RPBD
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM HR_CC1_TIMEEVENT_POST - HR CC1 TIMEEVENT POST 





CALL FUNCTION 'HR_CC1_TIMEEVENT_POST' "
* EXPORTING
*   verbu =                     " hrsverbu
*   update = 'X'                " rptxxxxx-kr_feld1
*   update_uname_aedtm = SPACE  " char1
  IMPORTING
    posted_timeevents =         " sy-dbcnt
    faulty_timeevents =         " sy-dbcnt
    locked_timeevents =         " sy-dbcnt
    skipped_timeevents =        " sy-dbcnt
    .  "  HR_CC1_TIMEEVENT_POST

ABAP code example for Function Module HR_CC1_TIMEEVENT_POST





The ABAP code below is a full code listing to execute function module HR_CC1_TIMEEVENT_POST including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_posted_timeevents    TYPE SY-DBCNT
,
ld_faulty_timeevents    TYPE SY-DBCNT
,
ld_locked_timeevents    TYPE SY-DBCNT
,
ld_skipped_timeevents    TYPE SY-DBCNT
.




DATA(ld_verbu) = 'Check type of data required'.


DATA(ld_update) = some text here

DATA(ld_update_uname_aedtm) = 'Check type of data required'.
.

CALL FUNCTION 'HR_CC1_TIMEEVENT_POST'
* EXPORTING
*   verbu =                      ld_verbu
*   update =                     ld_update
*   update_uname_aedtm =         ld_update_uname_aedtm
  IMPORTING
    posted_timeevents =          ld_posted_timeevents
    faulty_timeevents =          ld_faulty_timeevents
    locked_timeevents =          ld_locked_timeevents
    skipped_timeevents =         ld_skipped_timeevents
    .  "  HR_CC1_TIMEEVENT_POST

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_posted_timeevents  TYPE SY-DBCNT ,
ld_verbu  TYPE HRSVERBU ,
ld_faulty_timeevents  TYPE SY-DBCNT ,
ld_update  TYPE RPTXXXXX-KR_FELD1 ,
ld_locked_timeevents  TYPE SY-DBCNT ,
ld_update_uname_aedtm  TYPE CHAR1 ,
ld_skipped_timeevents  TYPE SY-DBCNT .




ld_verbu = 'Check type of data required'.

ld_update = some text here
ld_update_uname_aedtm = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name HR_CC1_TIMEEVENT_POST or its description.


   
 

HR_CC1_TIMEEVENT_POST - 
HR_CC1_TIMEEVENT_INSERT - 
HR_CC1_TIMEEVENT_GETDETAIL - 
HR_CC1_SET_TIMESTAMP - 
HR_CC1_SEND_MAIL - 
HR_CC1_EXTERNWAGE_INSERT -