SAP ALE_RE_RO_ADVPAY_EXT_CREATE Function Module for









ALE_RE_RO_ADVPAY_EXT_CREATE is a standard ale re ro advpay ext create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for ale re ro advpay ext create FM, simply by entering the name ALE_RE_RO_ADVPAY_EXT_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RERA_BAPI_ADVPAY_EXT
Program Name: SAPLRERA_BAPI_ADVPAY_EXT
Main Program: SAPLRERA_BAPI_ADVPAY_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ALE_RE_RO_ADVPAY_EXT_CREATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'ALE_RE_RO_ADVPAY_EXT_CREATE'"
EXPORTING
COMPCODE = "
BUSINESSENTITYNUMBER = "
RENTALOBJECTNUMBER = "
* TESTRUN = ' ' "
* OBJ_TYPE = 'BUS1504' "
* SERIAL_ID = '0' "

TABLES
* ADVPAYEXT = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "

EXCEPTIONS
ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for ALE_RE_RO_ADVPAY_EXT_CREATE

COMPCODE -

Data type: BAPI_RE_RENTAL_OBJECT_KEY-COMP_CODE
Optional: No
Call by Reference: No ( called with pass by value option)

BUSINESSENTITYNUMBER -

Data type: BAPI_RE_RENTAL_OBJECT_KEY-BUSINESS_ENTITY
Optional: No
Call by Reference: No ( called with pass by value option)

RENTALOBJECTNUMBER -

Data type: BAPI_RE_RENTAL_OBJECT_KEY-RENTAL_OBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

TESTRUN -

Data type: BAPI_RE_ADDITIONAL_FIELDS-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS1504'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_RE_RO_ADVPAY_EXT_CREATE

ADVPAYEXT -

Data type: BAPI_RE_ADVPAY_EXT_DAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

RECEIVERS -

Data type: BDI_LOGSYS
Optional: No
Call by Reference: No ( called with pass by value option)

COMMUNICATION_DOCUMENTS -

Data type: SWOTOBJID
Optional: Yes
Call by Reference: No ( called with pass by value option)

APPLICATION_OBJECTS -

Data type: SWOTOBJID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_CREATING_IDOCS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ALE_RE_RO_ADVPAY_EXT_CREATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_compcode  TYPE BAPI_RE_RENTAL_OBJECT_KEY-COMP_CODE, "   
lt_advpayext  TYPE STANDARD TABLE OF BAPI_RE_ADVPAY_EXT_DAT, "   
lv_error_creating_idocs  TYPE BAPI_RE_ADVPAY_EXT_DAT, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_businessentitynumber  TYPE BAPI_RE_RENTAL_OBJECT_KEY-BUSINESS_ENTITY, "   
lv_rentalobjectnumber  TYPE BAPI_RE_RENTAL_OBJECT_KEY-RENTAL_OBJECT, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_testrun  TYPE BAPI_RE_ADDITIONAL_FIELDS-TESTRUN, "   SPACE
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS1504'
lv_serial_id  TYPE SERIAL-CHNUM. "   '0'

  CALL FUNCTION 'ALE_RE_RO_ADVPAY_EXT_CREATE'  "
    EXPORTING
         COMPCODE = lv_compcode
         BUSINESSENTITYNUMBER = lv_businessentitynumber
         RENTALOBJECTNUMBER = lv_rentalobjectnumber
         TESTRUN = lv_testrun
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         ADVPAYEXT = lt_advpayext
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_RE_RO_ADVPAY_EXT_CREATE




ABAP code using 7.40 inline data declarations to call FM ALE_RE_RO_ADVPAY_EXT_CREATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single COMP_CODE FROM BAPI_RE_RENTAL_OBJECT_KEY INTO @DATA(ld_compcode).
 
 
 
 
"SELECT single BUSINESS_ENTITY FROM BAPI_RE_RENTAL_OBJECT_KEY INTO @DATA(ld_businessentitynumber).
 
"SELECT single RENTAL_OBJECT FROM BAPI_RE_RENTAL_OBJECT_KEY INTO @DATA(ld_rentalobjectnumber).
 
 
"SELECT single TESTRUN FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS1504'.
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!