SAP ACEPS_NEW_RUNID_GET_R3 Function Module for Issue a Unique Run ID (R3)









ACEPS_NEW_RUNID_GET_R3 is a standard aceps new runid get r3 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Issue a Unique Run ID (R3) processing and below is the pattern details for this FM, 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 aceps new runid get r3 FM, simply by entering the name ACEPS_NEW_RUNID_GET_R3 into the relevant SAP transaction such as SE37 or SE38.

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



Function ACEPS_NEW_RUNID_GET_R3 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 'ACEPS_NEW_RUNID_GET_R3'"Issue a Unique Run ID (R3)
EXPORTING
ID_COMP = "Application Component for Accrual
ID_ACE_BUKRS = "Company Code
ID_NRRANGENR = "Number Range Interval Number
ID_TESTRUN = "Test Run

IMPORTING
ED_RUNID = "Reference Document Number

EXCEPTIONS
ERROR_OCCURRED = 1
.



IMPORTING Parameters details for ACEPS_NEW_RUNID_GET_R3

ID_COMP - Application Component for Accrual

Data type: ACE_COMP
Optional: No
Call by Reference: Yes

ID_ACE_BUKRS - Company Code

Data type: ACE_BUKRS
Optional: No
Call by Reference: Yes

ID_NRRANGENR - Number Range Interval Number

Data type: ACE_NRNR
Optional: No
Call by Reference: Yes

ID_TESTRUN - Test Run

Data type: ACE_TESTRUN
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ACEPS_NEW_RUNID_GET_R3

ED_RUNID - Reference Document Number

Data type: ACEPS_RUNID
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_OCCURRED -

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

Copy and paste ABAP code example for ACEPS_NEW_RUNID_GET_R3 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_id_comp  TYPE ACE_COMP, "   
lv_ed_runid  TYPE ACEPS_RUNID, "   
lv_error_occurred  TYPE ACEPS_RUNID, "   
lv_id_ace_bukrs  TYPE ACE_BUKRS, "   
lv_id_nrrangenr  TYPE ACE_NRNR, "   
lv_id_testrun  TYPE ACE_TESTRUN. "   

  CALL FUNCTION 'ACEPS_NEW_RUNID_GET_R3'  "Issue a Unique Run ID (R3)
    EXPORTING
         ID_COMP = lv_id_comp
         ID_ACE_BUKRS = lv_id_ace_bukrs
         ID_NRRANGENR = lv_id_nrrangenr
         ID_TESTRUN = lv_id_testrun
    IMPORTING
         ED_RUNID = lv_ed_runid
    EXCEPTIONS
        ERROR_OCCURRED = 1
. " ACEPS_NEW_RUNID_GET_R3




ABAP code using 7.40 inline data declarations to call FM ACEPS_NEW_RUNID_GET_R3

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.

 
 
 
 
 
 


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!