SAP PRC_INT_ITEM_CREATE_MULTI Function Module for Anlegen mehrerer neuen Positionen
PRC_INT_ITEM_CREATE_MULTI is a standard prc int item create multi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Anlegen mehrerer neuen Positionen 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 item create multi FM, simply by entering the name PRC_INT_ITEM_CREATE_MULTI 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_ITEM_CREATE_MULTI 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_ITEM_CREATE_MULTI'"Anlegen mehrerer neuen Positionen.
EXPORTING
IV_PD_HANDLE = "Handle eines Preisfindungslaufes
IV_BAL_LOG = "Anwendungs-Log: Handle eines Protokolls
IT_ITEM_COM = "interne Tabelle über Positions-Kommunikationsstruktur
IT_ITEM_COM_ACS = "Interne Tabelle über Positions-Zugriffsfelder
IV_SUPPRESS_PRICING = "keine Preisfindung durchführen
IV_REQ_ITEM_RET = "Daten werden vom Aufrufer angefordert
IMPORTING
ES_PROFILE = "Profil des API-Aufrufes
ES_HEAD_RET = "Return-Werte der Preisfindung auf Kopfebene
ET_ITEM_RET = "Return-Werte der Preisfindung auf Positionsebene
ET_ITEMS_FAULT = "Liste von Positionsnummern
EXCEPTIONS
NON_EXISTING_HANDLE = 1 WRONG_CALL = 2 IPC_ERROR = 3 NOT_ALLOWED = 4
IMPORTING Parameters details for PRC_INT_ITEM_CREATE_MULTI
IV_PD_HANDLE - Handle eines Preisfindungslaufes
Data type: PRCT_HANDLEOptional: No
Call by Reference: Yes
IV_BAL_LOG - Anwendungs-Log: Handle eines Protokolls
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
IT_ITEM_COM - interne Tabelle über Positions-Kommunikationsstruktur
Data type: PRCT_ITEM_COM_TOptional: No
Call by Reference: Yes
IT_ITEM_COM_ACS - Interne Tabelle über Positions-Zugriffsfelder
Data type: INDEX TABLEOptional: No
Call by Reference: Yes
IV_SUPPRESS_PRICING - keine Preisfindung durchführen
Data type: PRCT_SUPPRESS_PRICINGOptional: No
Call by Reference: Yes
IV_REQ_ITEM_RET - Daten werden vom Aufrufer angefordert
Data type: PRCT_FLAG_REQUESTEDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PRC_INT_ITEM_CREATE_MULTI
ES_PROFILE - Profil des API-Aufrufes
Data type: PRCT_PROFILEOptional: No
Call by Reference: Yes
ES_HEAD_RET - Return-Werte der Preisfindung auf Kopfebene
Data type: PRCT_HEAD_RETOptional: No
Call by Reference: Yes
ET_ITEM_RET - Return-Werte der Preisfindung auf Positionsebene
Data type: PRCT_ITEM_RET_TOptional: No
Call by Reference: Yes
ET_ITEMS_FAULT - Liste von Positionsnummern
Data type: PRCT_ITEM_NO_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
NON_EXISTING_HANDLE - Handle existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_CALL - Falscher Aufruf
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IPC_ERROR - Fehler beim Aufruf des IPC
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_ALLOWED - Gewünschte Funktion nicht erlaubt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PRC_INT_ITEM_CREATE_MULTI 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_es_profile | TYPE PRCT_PROFILE, " | |||
| lv_iv_pd_handle | TYPE PRCT_HANDLE, " | |||
| lv_non_existing_handle | TYPE PRCT_HANDLE, " | |||
| lv_iv_bal_log | TYPE BALLOGHNDL, " | |||
| lv_wrong_call | TYPE BALLOGHNDL, " | |||
| lv_es_head_ret | TYPE PRCT_HEAD_RET, " | |||
| lv_ipc_error | TYPE PRCT_HEAD_RET, " | |||
| lv_et_item_ret | TYPE PRCT_ITEM_RET_T, " | |||
| lv_it_item_com | TYPE PRCT_ITEM_COM_T, " | |||
| lv_not_allowed | TYPE PRCT_ITEM_COM_T, " | |||
| lv_et_items_fault | TYPE PRCT_ITEM_NO_T, " | |||
| lv_it_item_com_acs | TYPE INDEX TABLE, " | |||
| lv_iv_suppress_pricing | TYPE PRCT_SUPPRESS_PRICING, " | |||
| lv_iv_req_item_ret | TYPE PRCT_FLAG_REQUESTED. " |
|   CALL FUNCTION 'PRC_INT_ITEM_CREATE_MULTI' "Anlegen mehrerer neuen Positionen |
| EXPORTING | ||
| IV_PD_HANDLE | = lv_iv_pd_handle | |
| IV_BAL_LOG | = lv_iv_bal_log | |
| IT_ITEM_COM | = lv_it_item_com | |
| IT_ITEM_COM_ACS | = lv_it_item_com_acs | |
| IV_SUPPRESS_PRICING | = lv_iv_suppress_pricing | |
| IV_REQ_ITEM_RET | = lv_iv_req_item_ret | |
| IMPORTING | ||
| ES_PROFILE | = lv_es_profile | |
| ES_HEAD_RET | = lv_es_head_ret | |
| ET_ITEM_RET | = lv_et_item_ret | |
| ET_ITEMS_FAULT | = lv_et_items_fault | |
| EXCEPTIONS | ||
| NON_EXISTING_HANDLE = 1 | ||
| WRONG_CALL = 2 | ||
| IPC_ERROR = 3 | ||
| NOT_ALLOWED = 4 | ||
| . " PRC_INT_ITEM_CREATE_MULTI | ||
ABAP code using 7.40 inline data declarations to call FM PRC_INT_ITEM_CREATE_MULTI
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