SAP ACEPS3_OBJ_PERIODIC_POST Function Module for Perform Periodic Accrual Posting
ACEPS3_OBJ_PERIODIC_POST is a standard aceps3 obj periodic post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Perform Periodic Accrual Posting 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 aceps3 obj periodic post FM, simply by entering the name ACEPS3_OBJ_PERIODIC_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACEPS3
Program Name: SAPLACEPS3
Main Program: SAPLACEPS3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ACEPS3_OBJ_PERIODIC_POST 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 'ACEPS3_OBJ_PERIODIC_POST'"Perform Periodic Accrual Posting.
EXPORTING
IS_ACE_OBJ = "Accrual Object Key
* ID_NO_POSTING = "
* ID_NO_POSTING_CHECK = "Flag: Do not Call Up RWIN for Test Runs
* ID_TESTRUN = "X = Test Run
* ID_SUBID = "Accrual Item
ID_EFFDATE = "Value Date
* IS_POST_PARAMS = "
ID_ACEDOCNR = "
* ID_RUNID = "Number (Run ID) of a Periodic Posting Run in Accrual Engine
* IR_ACCRULE = "Accounting Principles
* IR_ACRTYPE = "
* IT_COMP_SIMUPARAM_RANGES = "
IMPORTING
ET_DOCITEMS = "
ET_AMOUNTS = "
ET_RETURN = "Return Table
ET_ACEDOC_RETURN = "Table with Messages About Specific ACE Documents
ET_ACCDOC_RETURN = "
IMPORTING Parameters details for ACEPS3_OBJ_PERIODIC_POST
IS_ACE_OBJ - Accrual Object Key
Data type: ACE_OBJ_KEYOptional: No
Call by Reference: Yes
ID_NO_POSTING -
Data type: FLAGOptional: Yes
Call by Reference: Yes
ID_NO_POSTING_CHECK - Flag: Do not Call Up RWIN for Test Runs
Data type: ACE_PS_NO_RWIN_TESTOptional: Yes
Call by Reference: Yes
ID_TESTRUN - X = Test Run
Data type: ACE_TESTRUNOptional: Yes
Call by Reference: Yes
ID_SUBID - Accrual Item
Data type: ACE_SUBIDOptional: Yes
Call by Reference: Yes
ID_EFFDATE - Value Date
Data type: ACE_EFFDATEOptional: No
Call by Reference: Yes
IS_POST_PARAMS -
Data type: ACEPS_MANUAL_POSTING_PARAMSOptional: Yes
Call by Reference: Yes
ID_ACEDOCNR -
Data type: ACEPS_DOCNROptional: No
Call by Reference: Yes
ID_RUNID - Number (Run ID) of a Periodic Posting Run in Accrual Engine
Data type: ACEPS_RUNIDOptional: Yes
Call by Reference: Yes
IR_ACCRULE - Accounting Principles
Data type: ACE_ACCRULE_RANGE_TOptional: Yes
Call by Reference: Yes
IR_ACRTYPE -
Data type: ACE_ACRTYPE_RANGE_TOptional: Yes
Call by Reference: Yes
IT_COMP_SIMUPARAM_RANGES -
Data type: ACE_FIELD_RANGES_TOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ACEPS3_OBJ_PERIODIC_POST
ET_DOCITEMS -
Data type: ACEPS_ACE_DOC_EXTENDED_TOptional: No
Call by Reference: Yes
ET_AMOUNTS -
Data type: ACEDS_ACE_DOC_AMOUNTS_TOptional: No
Call by Reference: Yes
ET_RETURN - Return Table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
ET_ACEDOC_RETURN - Table with Messages About Specific ACE Documents
Data type: ACE_ACEDOC_RETURN_TOptional: No
Call by Reference: Yes
ET_ACCDOC_RETURN -
Data type: ACE_ACCDOC_RETURN_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ACEPS3_OBJ_PERIODIC_POST 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_is_ace_obj | TYPE ACE_OBJ_KEY, " | |||
| lv_et_docitems | TYPE ACEPS_ACE_DOC_EXTENDED_T, " | |||
| lv_id_no_posting | TYPE FLAG, " | |||
| lv_id_no_posting_check | TYPE ACE_PS_NO_RWIN_TEST, " | |||
| lv_id_testrun | TYPE ACE_TESTRUN, " | |||
| lv_id_subid | TYPE ACE_SUBID, " | |||
| lv_et_amounts | TYPE ACEDS_ACE_DOC_AMOUNTS_T, " | |||
| lv_et_return | TYPE BAPIRET2_T, " | |||
| lv_id_effdate | TYPE ACE_EFFDATE, " | |||
| lv_is_post_params | TYPE ACEPS_MANUAL_POSTING_PARAMS, " | |||
| lv_et_acedoc_return | TYPE ACE_ACEDOC_RETURN_T, " | |||
| lv_id_acedocnr | TYPE ACEPS_DOCNR, " | |||
| lv_et_accdoc_return | TYPE ACE_ACCDOC_RETURN_T, " | |||
| lv_id_runid | TYPE ACEPS_RUNID, " | |||
| lv_ir_accrule | TYPE ACE_ACCRULE_RANGE_T, " | |||
| lv_ir_acrtype | TYPE ACE_ACRTYPE_RANGE_T, " | |||
| lv_it_comp_simuparam_ranges | TYPE ACE_FIELD_RANGES_T. " |
|   CALL FUNCTION 'ACEPS3_OBJ_PERIODIC_POST' "Perform Periodic Accrual Posting |
| EXPORTING | ||
| IS_ACE_OBJ | = lv_is_ace_obj | |
| ID_NO_POSTING | = lv_id_no_posting | |
| ID_NO_POSTING_CHECK | = lv_id_no_posting_check | |
| ID_TESTRUN | = lv_id_testrun | |
| ID_SUBID | = lv_id_subid | |
| ID_EFFDATE | = lv_id_effdate | |
| IS_POST_PARAMS | = lv_is_post_params | |
| ID_ACEDOCNR | = lv_id_acedocnr | |
| ID_RUNID | = lv_id_runid | |
| IR_ACCRULE | = lv_ir_accrule | |
| IR_ACRTYPE | = lv_ir_acrtype | |
| IT_COMP_SIMUPARAM_RANGES | = lv_it_comp_simuparam_ranges | |
| IMPORTING | ||
| ET_DOCITEMS | = lv_et_docitems | |
| ET_AMOUNTS | = lv_et_amounts | |
| ET_RETURN | = lv_et_return | |
| ET_ACEDOC_RETURN | = lv_et_acedoc_return | |
| ET_ACCDOC_RETURN | = lv_et_accdoc_return | |
| . " ACEPS3_OBJ_PERIODIC_POST | ||
ABAP code using 7.40 inline data declarations to call FM ACEPS3_OBJ_PERIODIC_POST
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