SAP Function Modules
BAPI_BUS1240_REPLICATE SAP Function module - EHS: Request to Replicate Incident/Accident Log Entries
BAPI_BUS1240_REPLICATE 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 BAPI_BUS1240_REPLICATE into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
1240
Released Date:
Not Released
Processing type: Remote-Enabled
Pattern for FM BAPI_BUS1240_REPLICATE - BAPI BUS1240 REPLICATE
CALL FUNCTION 'BAPI_BUS1240_REPLICATE' "EHS: Request to Replicate Incident/Accident Log Entries
* EXPORTING
* key_date = SY-DATUM " rcgaddinf-valdat Validity Date
* incident = " bapi1240_ialh-incident Accident No.
* incidenttype = " bapi1240_ialh-type Accident Type
* plant = " bapi1240_ialh-plant Plant
* status = " bapi1240_ialh-status Object status
* person = " bapi1240_ip-person_involved Personnel Number
* personrole = " bapi1240_ip-person_role Person's Role
* incident_selopt = " bapi1240_iasel Selection Conditions for Incident/Accident Log Header
* workarea_selopt = " bapi1240_wasel Selection Conditions for Work Area for Incident/Accident Log
* injury_selopt = " bapi1240_injsel Selection Conditions for Injuries to Persons in an Accident
TABLES
return = " bapiret2 Error Messages
* incidentlist = " bapi1240_iallist Incident/accident log header data
* savereplicarecipients = " bapi1240_logsys Recipients of Accident Data (Logical Systems)
. " BAPI_BUS1240_REPLICATE
ABAP code example for Function Module BAPI_BUS1240_REPLICATE
The ABAP code below is a full code listing to execute function module BAPI_BUS1240_REPLICATE 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).
| it_return | TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM |
| wa_return | LIKE LINE OF it_return , |
| it_incidentlist | TYPE STANDARD TABLE OF BAPI1240_IALLIST,"TABLES PARAM |
| wa_incidentlist | LIKE LINE OF it_incidentlist , |
| it_savereplicarecipients | TYPE STANDARD TABLE OF BAPI1240_LOGSYS,"TABLES PARAM |
| wa_savereplicarecipients | LIKE LINE OF it_savereplicarecipients . |
DATA(ld_key_date) = 20210129
DATA(ld_incident) = some text here
DATA(ld_incidenttype) = some text here
DATA(ld_plant) = some text here
DATA(ld_status) = some text here
DATA(ld_person) = some text here
DATA(ld_personrole) = some text here
DATA(ld_incident_selopt) = 'Check type of data required'.
DATA(ld_workarea_selopt) = 'Check type of data required'.
DATA(ld_injury_selopt) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_return to it_return.
"populate fields of struture and append to itab
append wa_incidentlist to it_incidentlist.
"populate fields of struture and append to itab
append wa_savereplicarecipients to it_savereplicarecipients. . CALL FUNCTION 'BAPI_BUS1240_REPLICATE' * EXPORTING * key_date = ld_key_date * incident = ld_incident * incidenttype = ld_incidenttype * plant = ld_plant * status = ld_status * person = ld_person * personrole = ld_personrole * incident_selopt = ld_incident_selopt * workarea_selopt = ld_workarea_selopt * injury_selopt = ld_injury_selopt TABLES return = it_return * incidentlist = it_incidentlist * savereplicarecipients = it_savereplicarecipients . " BAPI_BUS1240_REPLICATE
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_key_date | TYPE RCGADDINF-VALDAT , |
| it_return | TYPE STANDARD TABLE OF BAPIRET2 , |
| wa_return | LIKE LINE OF it_return, |
| ld_incident | TYPE BAPI1240_IALH-INCIDENT , |
| it_incidentlist | TYPE STANDARD TABLE OF BAPI1240_IALLIST , |
| wa_incidentlist | LIKE LINE OF it_incidentlist, |
| ld_incidenttype | TYPE BAPI1240_IALH-TYPE , |
| it_savereplicarecipients | TYPE STANDARD TABLE OF BAPI1240_LOGSYS , |
| wa_savereplicarecipients | LIKE LINE OF it_savereplicarecipients, |
| ld_plant | TYPE BAPI1240_IALH-PLANT , |
| ld_status | TYPE BAPI1240_IALH-STATUS , |
| ld_person | TYPE BAPI1240_IP-PERSON_INVOLVED , |
| ld_personrole | TYPE BAPI1240_IP-PERSON_ROLE , |
| ld_incident_selopt | TYPE BAPI1240_IASEL , |
| ld_workarea_selopt | TYPE BAPI1240_WASEL , |
| ld_injury_selopt | TYPE BAPI1240_INJSEL . |
ld_key_date = 20210129
"populate fields of struture and append to itab
append wa_return to it_return.
ld_incident = some text here
"populate fields of struture and append to itab
append wa_incidentlist to it_incidentlist.
ld_incidenttype = some text here
"populate fields of struture and append to itab
append wa_savereplicarecipients to it_savereplicarecipients.
ld_plant = some text here
ld_status = some text here
ld_person = some text here
ld_personrole = some text here
ld_incident_selopt = 'Check type of data required'.
ld_workarea_selopt = 'Check type of data required'.
ld_injury_selopt = '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 BAPI_BUS1240_REPLICATE or its description.