SAP ACEPS_PERIODPOST_LIST_DISPLAY Function Module for Results List for Periodic Posting Run
ACEPS_PERIODPOST_LIST_DISPLAY is a standard aceps periodpost list display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Results List for Periodic Posting Run 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 periodpost list display FM, simply by entering the name ACEPS_PERIODPOST_LIST_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACEPS17
Program Name: SAPLACEPS17
Main Program: SAPLACEPS17
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ACEPS_PERIODPOST_LIST_DISPLAY 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_PERIODPOST_LIST_DISPLAY'"Results List for Periodic Posting Run.
EXPORTING
ID_COMP = "Accrual Engine Application Component
* ID_TESTRUN = 'X' "Test Run
ID_RUNTYPE = "Run Type of Periodic Accrual Program
ID_EFFDATE = "Key Date/Posting Date for Accruals
ID_RESULT_STRUC_NAME = "30 Characters
CHANGING
CT_DOCITEMS = "Accrual Engine Line Items with Error Handling
CT_AMOUNTS = "Calculated Accrual Values by Accrual Engine Document
CT_RETURN = "Return parameter table
CT_ACEDOC_RETURN = "Table with Messages About Specific ACE Documents
CT_ACCDOC_RETURN = "Table with Messages About Transferred Accounting Documents
CT_FINAL_POSTING_LIST = "Predefined Type
IMPORTING Parameters details for ACEPS_PERIODPOST_LIST_DISPLAY
ID_COMP - Accrual Engine Application Component
Data type: ACE_COMPOptional: No
Call by Reference: Yes
ID_TESTRUN - Test Run
Data type: ACE_TESTRUNDefault: 'X'
Optional: Yes
Call by Reference: Yes
ID_RUNTYPE - Run Type of Periodic Accrual Program
Data type: ACEPSPPLOG-RUNTYPEOptional: No
Call by Reference: Yes
ID_EFFDATE - Key Date/Posting Date for Accruals
Data type: ACE_EFFDATEOptional: No
Call by Reference: Yes
ID_RESULT_STRUC_NAME - 30 Characters
Data type: CHAR30Optional: No
Call by Reference: Yes
CHANGING Parameters details for ACEPS_PERIODPOST_LIST_DISPLAY
CT_DOCITEMS - Accrual Engine Line Items with Error Handling
Data type: ACEPS_ACE_DOC_EXTENDED_TOptional: No
Call by Reference: Yes
CT_AMOUNTS - Calculated Accrual Values by Accrual Engine Document
Data type: ACEDS_ACE_DOC_AMOUNTS_TOptional: No
Call by Reference: Yes
CT_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
CT_ACEDOC_RETURN - Table with Messages About Specific ACE Documents
Data type: ACE_ACEDOC_RETURN_TOptional: No
Call by Reference: Yes
CT_ACCDOC_RETURN - Table with Messages About Transferred Accounting Documents
Data type: ACE_ACCDOC_RETURN_TOptional: No
Call by Reference: Yes
CT_FINAL_POSTING_LIST - Predefined Type
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ACEPS_PERIODPOST_LIST_DISPLAY 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_ct_docitems | TYPE ACEPS_ACE_DOC_EXTENDED_T, " | |||
| lv_ct_amounts | TYPE ACEDS_ACE_DOC_AMOUNTS_T, " | |||
| lv_id_testrun | TYPE ACE_TESTRUN, " 'X' | |||
| lv_ct_return | TYPE BAPIRET2_T, " | |||
| lv_id_runtype | TYPE ACEPSPPLOG-RUNTYPE, " | |||
| lv_id_effdate | TYPE ACE_EFFDATE, " | |||
| lv_ct_acedoc_return | TYPE ACE_ACEDOC_RETURN_T, " | |||
| lv_ct_accdoc_return | TYPE ACE_ACCDOC_RETURN_T, " | |||
| lv_id_result_struc_name | TYPE CHAR30, " | |||
| lv_ct_final_posting_list | TYPE STANDARD TABLE. " |
|   CALL FUNCTION 'ACEPS_PERIODPOST_LIST_DISPLAY' "Results List for Periodic Posting Run |
| EXPORTING | ||
| ID_COMP | = lv_id_comp | |
| ID_TESTRUN | = lv_id_testrun | |
| ID_RUNTYPE | = lv_id_runtype | |
| ID_EFFDATE | = lv_id_effdate | |
| ID_RESULT_STRUC_NAME | = lv_id_result_struc_name | |
| CHANGING | ||
| CT_DOCITEMS | = lv_ct_docitems | |
| CT_AMOUNTS | = lv_ct_amounts | |
| CT_RETURN | = lv_ct_return | |
| CT_ACEDOC_RETURN | = lv_ct_acedoc_return | |
| CT_ACCDOC_RETURN | = lv_ct_accdoc_return | |
| CT_FINAL_POSTING_LIST | = lv_ct_final_posting_list | |
| . " ACEPS_PERIODPOST_LIST_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM ACEPS_PERIODPOST_LIST_DISPLAY
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.| DATA(ld_id_testrun) | = 'X'. | |||
| "SELECT single RUNTYPE FROM ACEPSPPLOG INTO @DATA(ld_id_runtype). | ||||
Search for further information about these or an SAP related objects