SAP CPE_TEST_JAVA_API_FA_PROC_INFO Function Module for Test Java API of CPE for Formula Assembly Procedure Info
CPE_TEST_JAVA_API_FA_PROC_INFO is a standard cpe test java api fa proc info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Test Java API of CPE for Formula Assembly Procedure Info 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 cpe test java api fa proc info FM, simply by entering the name CPE_TEST_JAVA_API_FA_PROC_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPE_TEST_JAVA_API
Program Name: SAPLCPE_TEST_JAVA_API
Main Program: SAPLCPE_TEST_JAVA_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function CPE_TEST_JAVA_API_FA_PROC_INFO 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 'CPE_TEST_JAVA_API_FA_PROC_INFO'"Test Java API of CPE for Formula Assembly Procedure Info.
EXPORTING
* IV_LOGSYS = '' "Logical system
* IV_APPLICATION = 'CRM' "CPE Caller - Application using CPE
* IV_FA_PROCEDURE = '0CPEF2' "CPE Caller - Formula Assembly Procedure
* IV_LOG_PRIORITY = 5 "CPE - Priority of Log Entry
* IV_IPC_VMC_DEST = '' '' "Logical Destination (Specified in Function Call)
IMPORTING
ET_HEAD_ATTR_NAMES = "CPE Caller - Table Type for Attribute Names (L=30)
ET_ITEM_ATTR_NAMES = "CPE Caller - Table Type for Attribute Names (L=30)
ET_LOG = "CPE - Table for Log Data in Documents
EV_TEST_ERROR_OCCURRED = "Single-Character Flag
IMPORTING Parameters details for CPE_TEST_JAVA_API_FA_PROC_INFO
IV_LOGSYS - Logical system
Data type: LOGSYSDefault: ''
Optional: No
Call by Reference: No ( called with pass by value option)
IV_APPLICATION - CPE Caller - Application using CPE
Data type: CPET_APPLICATIONDefault: 'CRM'
Optional: No
Call by Reference: No ( called with pass by value option)
IV_FA_PROCEDURE - CPE Caller - Formula Assembly Procedure
Data type: CPET_FA_PROCEDUREDefault: '0CPEF2'
Optional: No
Call by Reference: No ( called with pass by value option)
IV_LOG_PRIORITY - CPE - Priority of Log Entry
Data type: CPET_LOG_PRIORITYDefault: 5
Optional: No
Call by Reference: No ( called with pass by value option)
IV_IPC_VMC_DEST - Logical Destination (Specified in Function Call)
Data type: RFCDESTDefault: 'SPACE'
Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CPE_TEST_JAVA_API_FA_PROC_INFO
ET_HEAD_ATTR_NAMES - CPE Caller - Table Type for Attribute Names (L=30)
Data type: CPET_NAME_ATTR_30_TABOptional: No
Call by Reference: No ( called with pass by value option)
ET_ITEM_ATTR_NAMES - CPE Caller - Table Type for Attribute Names (L=30)
Data type: CPET_NAME_ATTR_30_TABOptional: No
Call by Reference: No ( called with pass by value option)
ET_LOG - CPE - Table for Log Data in Documents
Data type: CPET_LOG_TABOptional: No
Call by Reference: No ( called with pass by value option)
EV_TEST_ERROR_OCCURRED - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CPE_TEST_JAVA_API_FA_PROC_INFO 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_iv_logsys | TYPE LOGSYS, " '' | |||
| lv_et_head_attr_names | TYPE CPET_NAME_ATTR_30_TAB, " | |||
| lv_iv_application | TYPE CPET_APPLICATION, " 'CRM' | |||
| lv_et_item_attr_names | TYPE CPET_NAME_ATTR_30_TAB, " | |||
| lv_et_log | TYPE CPET_LOG_TAB, " | |||
| lv_iv_fa_procedure | TYPE CPET_FA_PROCEDURE, " '0CPEF2' | |||
| lv_iv_log_priority | TYPE CPET_LOG_PRIORITY, " 5 | |||
| lv_ev_test_error_occurred | TYPE CHAR1, " | |||
| lv_iv_ipc_vmc_dest | TYPE RFCDEST. " 'SPACE' |
| CALL FUNCTION 'CPE_TEST_JAVA_API_FA_PROC_INFO' "Test Java API of CPE for Formula Assembly Procedure Info |
| EXPORTING | ||
| IV_LOGSYS | = lv_iv_logsys | |
| IV_APPLICATION | = lv_iv_application | |
| IV_FA_PROCEDURE | = lv_iv_fa_procedure | |
| IV_LOG_PRIORITY | = lv_iv_log_priority | |
| IV_IPC_VMC_DEST | = lv_iv_ipc_vmc_dest | |
| IMPORTING | ||
| ET_HEAD_ATTR_NAMES | = lv_et_head_attr_names | |
| ET_ITEM_ATTR_NAMES | = lv_et_item_attr_names | |
| ET_LOG | = lv_et_log | |
| EV_TEST_ERROR_OCCURRED | = lv_ev_test_error_occurred | |
| . " CPE_TEST_JAVA_API_FA_PROC_INFO | ||
ABAP code using 7.40 inline data declarations to call FM CPE_TEST_JAVA_API_FA_PROC_INFO
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_iv_logsys) | = ''. | |||
| DATA(ld_iv_application) | = 'CRM'. | |||
| DATA(ld_iv_fa_procedure) | = '0CPEF2'. | |||
| DATA(ld_iv_log_priority) | = 5. | |||
| DATA(ld_iv_ipc_vmc_dest) | = '' ''. | |||
Search for further information about these or an SAP related objects