SAP ACE_RUN_PROCESS_POST_PACKAGE Function Module for Process Package
ACE_RUN_PROCESS_POST_PACKAGE is a standard ace run process post package SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Process Package 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 ace run process post package FM, simply by entering the name ACE_RUN_PROCESS_POST_PACKAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACE_RUN_PACKAGE_PROCESS
Program Name: SAPLACE_RUN_PACKAGE_PROCESS
Main Program: SAPLSUGZ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ACE_RUN_PROCESS_POST_PACKAGE 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 'ACE_RUN_PROCESS_POST_PACKAGE'"Process Package.
EXPORTING
ID_TCODE = "ABAP System Field: Current Transaction Code
IT_ITEMTYPE_RANGE = "Accrual Item Type
ID_EFFDATE = "Period Determination Date
ID_TESTRUN = "Single-Character Flag
* ID_PKGID = "Package ID for Accrual Posting Run
IT_SUBOBJ_KEY = "Key for Accrual Subobject
IT_LDGRP_RANGE = "Ledger Group
* IS_ARCHIVE_PARAM = "accrual object archive parameter
IMPORTING
ET_RESULT_LIST = "Single-Character Flag
ET_MESSAGE_HANDLER = "ACE: Message collector table
IMPORTING Parameters details for ACE_RUN_PROCESS_POST_PACKAGE
ID_TCODE - ABAP System Field: Current Transaction Code
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
IT_ITEMTYPE_RANGE - Accrual Item Type
Data type: ACE_ITEMTYPE_RANGE_TOptional: No
Call by Reference: No ( called with pass by value option)
ID_EFFDATE - Period Determination Date
Data type: ACE_DS_PERIOD_DETERMINATN_DATEOptional: No
Call by Reference: No ( called with pass by value option)
ID_TESTRUN - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
ID_PKGID - Package ID for Accrual Posting Run
Data type: ACE_PKGIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SUBOBJ_KEY - Key for Accrual Subobject
Data type: ACESOBJ_KEY_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_LDGRP_RANGE - Ledger Group
Data type: FAGL_RANGE_T_LDGRPOptional: No
Call by Reference: No ( called with pass by value option)
IS_ARCHIVE_PARAM - accrual object archive parameter
Data type: ACE_ARCHIVE_PARAMOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ACE_RUN_PROCESS_POST_PACKAGE
ET_RESULT_LIST - Single-Character Flag
Data type: ACE_POSTING_RESULT_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGE_HANDLER - ACE: Message collector table
Data type: ACE_MESSAGE_HANDLER_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ACE_RUN_PROCESS_POST_PACKAGE 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_tcode | TYPE SY-TCODE, " | |||
| lv_et_result_list | TYPE ACE_POSTING_RESULT_T, " | |||
| lv_it_itemtype_range | TYPE ACE_ITEMTYPE_RANGE_T, " | |||
| lv_et_message_handler | TYPE ACE_MESSAGE_HANDLER_T, " | |||
| lv_id_effdate | TYPE ACE_DS_PERIOD_DETERMINATN_DATE, " | |||
| lv_id_testrun | TYPE CHAR1, " | |||
| lv_id_pkgid | TYPE ACE_PKGID, " | |||
| lv_it_subobj_key | TYPE ACESOBJ_KEY_T, " | |||
| lv_it_ldgrp_range | TYPE FAGL_RANGE_T_LDGRP, " | |||
| lv_is_archive_param | TYPE ACE_ARCHIVE_PARAM. " |
|   CALL FUNCTION 'ACE_RUN_PROCESS_POST_PACKAGE' "Process Package |
| EXPORTING | ||
| ID_TCODE | = lv_id_tcode | |
| IT_ITEMTYPE_RANGE | = lv_it_itemtype_range | |
| ID_EFFDATE | = lv_id_effdate | |
| ID_TESTRUN | = lv_id_testrun | |
| ID_PKGID | = lv_id_pkgid | |
| IT_SUBOBJ_KEY | = lv_it_subobj_key | |
| IT_LDGRP_RANGE | = lv_it_ldgrp_range | |
| IS_ARCHIVE_PARAM | = lv_is_archive_param | |
| IMPORTING | ||
| ET_RESULT_LIST | = lv_et_result_list | |
| ET_MESSAGE_HANDLER | = lv_et_message_handler | |
| . " ACE_RUN_PROCESS_POST_PACKAGE | ||
ABAP code using 7.40 inline data declarations to call FM ACE_RUN_PROCESS_POST_PACKAGE
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 TCODE FROM SY INTO @DATA(ld_id_tcode). | ||||
Search for further information about these or an SAP related objects