SAP Function Modules

ALE_RE_PG_CHANGE SAP Function module







ALE_RE_PG_CHANGE 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 ALE_RE_PG_CHANGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RESC_BAPI_PARTICIP_GRP
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ALE_RE_PG_CHANGE - ALE RE PG CHANGE





CALL FUNCTION 'ALE_RE_PG_CHANGE' "
  EXPORTING
    compcode =                  " bapi_re_particip_grp_key-comp_code
    businessentitynumber =      " bapi_re_particip_grp_key-business_entity
    participgroupnumber =       " bapi_re_particip_grp_key-particip_group
*   participgrp =               " bapi_re_particip_grp_dat
*   participgrpx =              " bapi_re_particip_grp_datx
*   trans =                     " bapi_re_additional_fields-trans
*   testrun = SPACE             " bapi_re_additional_fields-testrun
*   obj_type = 'BUS1507'        " serial-obj_type
*   serial_id = '0'             " serial-chnum
  TABLES
*   participobj =               " bapi_re_particip_obj_datc
*   resubmrule =                " bapi_re_resubm_rule_datc
*   resubmdate =                " bapi_re_resubm_date_datc
*   status =                    " bapi_re_status_datc
*   extensionin =               " bapiparex
    receivers =                 " bdi_logsys
*   communication_documents =   " swotobjid
*   application_objects =       " swotobjid
  EXCEPTIONS
    ERROR_CREATING_IDOCS = 1    "
    .  "  ALE_RE_PG_CHANGE

ABAP code example for Function Module ALE_RE_PG_CHANGE





The ABAP code below is a full code listing to execute function module ALE_RE_PG_CHANGE 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:
it_participobj  TYPE STANDARD TABLE OF BAPI_RE_PARTICIP_OBJ_DATC,"TABLES PARAM
wa_participobj  LIKE LINE OF it_participobj ,
it_resubmrule  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE_DATC,"TABLES PARAM
wa_resubmrule  LIKE LINE OF it_resubmrule ,
it_resubmdate  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE_DATC,"TABLES PARAM
wa_resubmdate  LIKE LINE OF it_resubmdate ,
it_status  TYPE STANDARD TABLE OF BAPI_RE_STATUS_DATC,"TABLES PARAM
wa_status  LIKE LINE OF it_status ,
it_extensionin  TYPE STANDARD TABLE OF BAPIPAREX,"TABLES PARAM
wa_extensionin  LIKE LINE OF it_extensionin ,
it_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS,"TABLES PARAM
wa_receivers  LIKE LINE OF it_receivers ,
it_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_communication_documents  LIKE LINE OF it_communication_documents ,
it_application_objects  TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_application_objects  LIKE LINE OF it_application_objects .


DATA(ld_compcode) = some text here

DATA(ld_businessentitynumber) = some text here

DATA(ld_participgroupnumber) = some text here
DATA(ld_participgrp) = 'Check type of data required'.
DATA(ld_participgrpx) = 'Check type of data required'.

DATA(ld_trans) = some text here

DATA(ld_testrun) = some text here

DATA(ld_obj_type) = some text here

DATA(ld_serial_id) = Check type of data required

"populate fields of struture and append to itab
append wa_participobj to it_participobj.

"populate fields of struture and append to itab
append wa_resubmrule to it_resubmrule.

"populate fields of struture and append to itab
append wa_resubmdate to it_resubmdate.

"populate fields of struture and append to itab
append wa_status to it_status.

"populate fields of struture and append to itab
append wa_extensionin to it_extensionin.

"populate fields of struture and append to itab
append wa_receivers to it_receivers.

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects. . CALL FUNCTION 'ALE_RE_PG_CHANGE' EXPORTING compcode = ld_compcode businessentitynumber = ld_businessentitynumber participgroupnumber = ld_participgroupnumber * participgrp = ld_participgrp * participgrpx = ld_participgrpx * trans = ld_trans * testrun = ld_testrun * obj_type = ld_obj_type * serial_id = ld_serial_id TABLES * participobj = it_participobj * resubmrule = it_resubmrule * resubmdate = it_resubmdate * status = it_status * extensionin = it_extensionin receivers = it_receivers * communication_documents = it_communication_documents * application_objects = it_application_objects EXCEPTIONS ERROR_CREATING_IDOCS = 1 . " ALE_RE_PG_CHANGE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here 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_compcode  TYPE BAPI_RE_PARTICIP_GRP_KEY-COMP_CODE ,
it_participobj  TYPE STANDARD TABLE OF BAPI_RE_PARTICIP_OBJ_DATC ,
wa_participobj  LIKE LINE OF it_participobj,
ld_businessentitynumber  TYPE BAPI_RE_PARTICIP_GRP_KEY-BUSINESS_ENTITY ,
it_resubmrule  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE_DATC ,
wa_resubmrule  LIKE LINE OF it_resubmrule,
ld_participgroupnumber  TYPE BAPI_RE_PARTICIP_GRP_KEY-PARTICIP_GROUP ,
it_resubmdate  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE_DATC ,
wa_resubmdate  LIKE LINE OF it_resubmdate,
ld_participgrp  TYPE BAPI_RE_PARTICIP_GRP_DAT ,
it_status  TYPE STANDARD TABLE OF BAPI_RE_STATUS_DATC ,
wa_status  LIKE LINE OF it_status,
ld_participgrpx  TYPE BAPI_RE_PARTICIP_GRP_DATX ,
it_extensionin  TYPE STANDARD TABLE OF BAPIPAREX ,
wa_extensionin  LIKE LINE OF it_extensionin,
ld_trans  TYPE BAPI_RE_ADDITIONAL_FIELDS-TRANS ,
it_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS ,
wa_receivers  LIKE LINE OF it_receivers,
ld_testrun  TYPE BAPI_RE_ADDITIONAL_FIELDS-TESTRUN ,
it_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID ,
wa_communication_documents  LIKE LINE OF it_communication_documents,
ld_obj_type  TYPE SERIAL-OBJ_TYPE ,
it_application_objects  TYPE STANDARD TABLE OF SWOTOBJID ,
wa_application_objects  LIKE LINE OF it_application_objects,
ld_serial_id  TYPE SERIAL-CHNUM .


ld_compcode = some text here

"populate fields of struture and append to itab
append wa_participobj to it_participobj.

ld_businessentitynumber = some text here

"populate fields of struture and append to itab
append wa_resubmrule to it_resubmrule.

ld_participgroupnumber = some text here

"populate fields of struture and append to itab
append wa_resubmdate to it_resubmdate.
ld_participgrp = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_status to it_status.
ld_participgrpx = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_extensionin to it_extensionin.

ld_trans = some text here

"populate fields of struture and append to itab
append wa_receivers to it_receivers.

ld_testrun = some text here

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.

ld_obj_type = some text here

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects.

ld_serial_id = 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 ALE_RE_PG_CHANGE or its description.