SAP COM_PARTNER_INIT_OB Function Module for Initialisierung des Objektpuffers
COM_PARTNER_INIT_OB is a standard com partner init ob SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialisierung des Objektpuffers 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 com partner init ob FM, simply by entering the name COM_PARTNER_INIT_OB into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_PARTNER_OB
Program Name: SAPLCOM_PARTNER_OB
Main Program: SAPLCOM_PARTNER_OB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_PARTNER_INIT_OB 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 'COM_PARTNER_INIT_OB'"Initialisierung des Objektpuffers.
EXPORTING
* IT_PARTNERSETS_TO_INIT = "List of Partner Set GUIDs
* IV_INIT_WHOLE_BUFFER = FALSE "SAPconnect: Selection
EXCEPTIONS
PARAMETER_ERROR = 1
IMPORTING Parameters details for COM_PARTNER_INIT_OB
IT_PARTNERSETS_TO_INIT - List of Partner Set GUIDs
Data type: COMT_PARTNERSET_GUID_TABOptional: Yes
Call by Reference: Yes
IV_INIT_WHOLE_BUFFER - SAPconnect: Selection
Data type: SX_BOOLEANDefault: FALSE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
PARAMETER_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for COM_PARTNER_INIT_OB 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_parameter_error | TYPE STRING, " | |||
| lv_it_partnersets_to_init | TYPE COMT_PARTNERSET_GUID_TAB, " | |||
| lv_iv_init_whole_buffer | TYPE SX_BOOLEAN. " FALSE |
|   CALL FUNCTION 'COM_PARTNER_INIT_OB' "Initialisierung des Objektpuffers |
| EXPORTING | ||
| IT_PARTNERSETS_TO_INIT | = lv_it_partnersets_to_init | |
| IV_INIT_WHOLE_BUFFER | = lv_iv_init_whole_buffer | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| . " COM_PARTNER_INIT_OB | ||
ABAP code using 7.40 inline data declarations to call FM COM_PARTNER_INIT_OB
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_init_whole_buffer) | = FALSE. | |||
Search for further information about these or an SAP related objects