SAP PRC_INT_MAP_ITEM_ABAP_TO_JAVA Function Module for Map Item ABAP structure to Java
PRC_INT_MAP_ITEM_ABAP_TO_JAVA is a standard prc int map item abap to java SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Map Item ABAP structure to Java 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 prc int map item abap to java FM, simply by entering the name PRC_INT_MAP_ITEM_ABAP_TO_JAVA into the relevant SAP transaction such as SE37 or SE38.
Function Group: PRC_INT
Program Name: SAPLPRC_INT
Main Program: SAPLPRC_INT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRC_INT_MAP_ITEM_ABAP_TO_JAVA 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 'PRC_INT_MAP_ITEM_ABAP_TO_JAVA'"Map Item ABAP structure to Java.
EXPORTING
IS_HEAD = "
IS_ITEM_COM = "Communication Fields from Pricing Item incl. Variants
* IS_ACS_ITEM = "Data reference
IMPORTING
ET_ITEM_VMC = "Pricing Item With Marked Fields
ES_ITEM = "
ET_ITEM_WRK_DATA = "Table Type for Pricing Item Main Part
ET_ITEM_ITAB_INFO = "Table Type for Pricing Item (SPCT_ITEMX) Complex Structures
ET_ORDER_ATTRIBUTES = "Table Type for Pricing Item Attributes Part
ET_ORDER_TIMESTAMPS = "Table Type for Pricing Item Timestamp Parts
IMPORTING Parameters details for PRC_INT_MAP_ITEM_ABAP_TO_JAVA
IS_HEAD -
Data type: IF_PRC_INT_MAPPING_ABAP_JAVA=>TY_GS_HEAD_DATAOptional: No
Call by Reference: Yes
IS_ITEM_COM - Communication Fields from Pricing Item incl. Variants
Data type: PRCT_ITEM_COM_VAROptional: No
Call by Reference: Yes
IS_ACS_ITEM - Data reference
Data type: ANYOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PRC_INT_MAP_ITEM_ABAP_TO_JAVA
ET_ITEM_VMC - Pricing Item With Marked Fields
Data type: SPCT_ITEMX_TOptional: No
Call by Reference: Yes
ES_ITEM -
Data type:Optional: No
Call by Reference: Yes
ET_ITEM_WRK_DATA - Table Type for Pricing Item Main Part
Data type: SPCT_ITEM_WRK_DATA_TOptional: No
Call by Reference: Yes
ET_ITEM_ITAB_INFO - Table Type for Pricing Item (SPCT_ITEMX) Complex Structures
Data type: SPCT_ITEM_ITAB_INFO_TOptional: No
Call by Reference: Yes
ET_ORDER_ATTRIBUTES - Table Type for Pricing Item Attributes Part
Data type: SPCT_ITEM_ATTRIBUTES_TOptional: No
Call by Reference: Yes
ET_ORDER_TIMESTAMPS - Table Type for Pricing Item Timestamp Parts
Data type: SPCT_ITEM_TIMESTAMPS_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRC_INT_MAP_ITEM_ABAP_TO_JAVA 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_head | TYPE IF_PRC_INT_MAPPING_ABAP_JAVA=>TY_GS_HEAD_DATA, " | |||
| lv_et_item_vmc | TYPE SPCT_ITEMX_T, " | |||
| lv_es_item | TYPE SPCT_ITEMX_T, " | |||
| lv_is_item_com | TYPE PRCT_ITEM_COM_VAR, " | |||
| lv_is_acs_item | TYPE ANY, " | |||
| lv_et_item_wrk_data | TYPE SPCT_ITEM_WRK_DATA_T, " | |||
| lv_et_item_itab_info | TYPE SPCT_ITEM_ITAB_INFO_T, " | |||
| lv_et_order_attributes | TYPE SPCT_ITEM_ATTRIBUTES_T, " | |||
| lv_et_order_timestamps | TYPE SPCT_ITEM_TIMESTAMPS_T. " |
|   CALL FUNCTION 'PRC_INT_MAP_ITEM_ABAP_TO_JAVA' "Map Item ABAP structure to Java |
| EXPORTING | ||
| IS_HEAD | = lv_is_head | |
| IS_ITEM_COM | = lv_is_item_com | |
| IS_ACS_ITEM | = lv_is_acs_item | |
| IMPORTING | ||
| ET_ITEM_VMC | = lv_et_item_vmc | |
| ES_ITEM | = lv_es_item | |
| ET_ITEM_WRK_DATA | = lv_et_item_wrk_data | |
| ET_ITEM_ITAB_INFO | = lv_et_item_itab_info | |
| ET_ORDER_ATTRIBUTES | = lv_et_order_attributes | |
| ET_ORDER_TIMESTAMPS | = lv_et_order_timestamps | |
| . " PRC_INT_MAP_ITEM_ABAP_TO_JAVA | ||
ABAP code using 7.40 inline data declarations to call FM PRC_INT_MAP_ITEM_ABAP_TO_JAVA
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