SAP CRM_ACE_EVENT_AC_AS_GET Function Module for
CRM_ACE_EVENT_AC_AS_GET is a standard crm ace event ac as get 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 crm ace event ac as get FM, simply by entering the name CRM_ACE_EVENT_AC_AS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_ACE_POSTING
Program Name: SAPLCRM_ACE_POSTING
Main Program: SAPLCRM_ACE_POSTING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_ACE_EVENT_AC_AS_GET 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 'CRM_ACE_EVENT_AC_AS_GET'".
EXPORTING
ID_ITEMNO_ACC = "
IS_PREITEM = "
IS_CURRINFO = "
CHANGING
CS_HEADER = "
CS_PAY_ITEM = "
CS_CON_ITEM = "
CS_REAL_ITEM = "
CS_COPA_ATTR = "
CS_COPA_VAL = "
CS_GL_ITEM = "
CS_AR_ITEM = "
CS_AP_ITEM = "
CS_TAX_ITEM = "
* CT_COPA_ATTR = "
* CT_COPA_VAL = "
CS_EXT1_ITEM = "
CS_EXT2_ITEM = "
EXCEPTIONS
ERROR_OCCURED = 1
IMPORTING Parameters details for CRM_ACE_EVENT_AC_AS_GET
ID_ITEMNO_ACC -
Data type: POSNR_ACCOptional: No
Call by Reference: Yes
IS_PREITEM -
Data type: ACEPS_BAPI_PRELINEITEMOptional: No
Call by Reference: Yes
IS_CURRINFO -
Data type: BAPIACCR09Optional: No
Call by Reference: Yes
CHANGING Parameters details for CRM_ACE_EVENT_AC_AS_GET
CS_HEADER -
Data type: BAPIACHE09Optional: No
Call by Reference: Yes
CS_PAY_ITEM -
Data type: BAPIACPC09Optional: No
Call by Reference: Yes
CS_CON_ITEM -
Data type: BAPIACCAITOptional: No
Call by Reference: Yes
CS_REAL_ITEM -
Data type: BAPIACRE09Optional: No
Call by Reference: Yes
CS_COPA_ATTR -
Data type: BAPIACKEC9Optional: No
Call by Reference: Yes
CS_COPA_VAL -
Data type: BAPIACKEV9Optional: No
Call by Reference: Yes
CS_GL_ITEM -
Data type: BAPIACGL09Optional: No
Call by Reference: Yes
CS_AR_ITEM -
Data type: BAPIACAR09Optional: No
Call by Reference: Yes
CS_AP_ITEM -
Data type: BAPIACAP09Optional: No
Call by Reference: Yes
CS_TAX_ITEM -
Data type: BAPIACTX09Optional: No
Call by Reference: Yes
CT_COPA_ATTR -
Data type: BAPIACKEC9_TABOptional: Yes
Call by Reference: Yes
CT_COPA_VAL -
Data type: BAPIACKEV9_TABOptional: Yes
Call by Reference: Yes
CS_EXT1_ITEM -
Data type: BAPIACEXTCOptional: No
Call by Reference: Yes
CS_EXT2_ITEM -
Data type: BAPIPAREXOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_ACE_EVENT_AC_AS_GET 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_cs_header | TYPE BAPIACHE09, " | |||
| lv_error_occured | TYPE BAPIACHE09, " | |||
| lv_id_itemno_acc | TYPE POSNR_ACC, " | |||
| lv_cs_pay_item | TYPE BAPIACPC09, " | |||
| lv_cs_con_item | TYPE BAPIACCAIT, " | |||
| lv_cs_real_item | TYPE BAPIACRE09, " | |||
| lv_cs_copa_attr | TYPE BAPIACKEC9, " | |||
| lv_cs_copa_val | TYPE BAPIACKEV9, " | |||
| lv_cs_gl_item | TYPE BAPIACGL09, " | |||
| lv_is_preitem | TYPE ACEPS_BAPI_PRELINEITEM, " | |||
| lv_cs_ar_item | TYPE BAPIACAR09, " | |||
| lv_is_currinfo | TYPE BAPIACCR09, " | |||
| lv_cs_ap_item | TYPE BAPIACAP09, " | |||
| lv_cs_tax_item | TYPE BAPIACTX09, " | |||
| lv_ct_copa_attr | TYPE BAPIACKEC9_TAB, " | |||
| lv_ct_copa_val | TYPE BAPIACKEV9_TAB, " | |||
| lv_cs_ext1_item | TYPE BAPIACEXTC, " | |||
| lv_cs_ext2_item | TYPE BAPIPAREX. " |
|   CALL FUNCTION 'CRM_ACE_EVENT_AC_AS_GET' " |
| EXPORTING | ||
| ID_ITEMNO_ACC | = lv_id_itemno_acc | |
| IS_PREITEM | = lv_is_preitem | |
| IS_CURRINFO | = lv_is_currinfo | |
| CHANGING | ||
| CS_HEADER | = lv_cs_header | |
| CS_PAY_ITEM | = lv_cs_pay_item | |
| CS_CON_ITEM | = lv_cs_con_item | |
| CS_REAL_ITEM | = lv_cs_real_item | |
| CS_COPA_ATTR | = lv_cs_copa_attr | |
| CS_COPA_VAL | = lv_cs_copa_val | |
| CS_GL_ITEM | = lv_cs_gl_item | |
| CS_AR_ITEM | = lv_cs_ar_item | |
| CS_AP_ITEM | = lv_cs_ap_item | |
| CS_TAX_ITEM | = lv_cs_tax_item | |
| CT_COPA_ATTR | = lv_ct_copa_attr | |
| CT_COPA_VAL | = lv_ct_copa_val | |
| CS_EXT1_ITEM | = lv_cs_ext1_item | |
| CS_EXT2_ITEM | = lv_cs_ext2_item | |
| EXCEPTIONS | ||
| ERROR_OCCURED = 1 | ||
| . " CRM_ACE_EVENT_AC_AS_GET | ||
ABAP code using 7.40 inline data declarations to call FM CRM_ACE_EVENT_AC_AS_GET
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