SAP COM_PARTNER_READ_DB Function Module for Lesen eines Eintrags aus dem Datenbankpuffer bzw. von der Datenbank









COM_PARTNER_READ_DB is a standard com partner read db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lesen eines Eintrags aus dem Datenbankpuffer bzw. von der Datenbank 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 read db FM, simply by entering the name COM_PARTNER_READ_DB into the relevant SAP transaction such as SE37 or SE38.

Function Group: COM_PARTNER_DB
Program Name: SAPLCOM_PARTNER_DB
Main Program: SAPLCOM_PARTNER_DB
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function COM_PARTNER_READ_DB 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_READ_DB'"Lesen eines Eintrags aus dem Datenbankpuffer bzw. von der Datenbank
  EXPORTING
*  IV_PARTNERSET_GUID =  "GUID for a Partner Set (Partner Quantity)
*  IT_PARTNERSET_GUIDS =  "List of Partner Set GUIDs

 IMPORTING
   ET_PARTNER_DB =  "Partnersets der angegebenen GUID
   ET_ATTRIBUTES =  "Attribute der Partner im Partnerset
   ET_CUST_ATTRIBUTES =  "Database Entries for COMD_PARTNER_ATT
   ET_CUST_RELATIONS =  "Database Entries for COMD_PARTNER_REL
   ET_COMP_PRDS =  "Database Entries for COMD_PARCOMP_PRD

EXCEPTIONS
   PARAMETER_ERROR = 1    RECORD_NOT_FOUND = 2    AT_LEAST_ONE_RECORD_NOT_FOUND = 3
.



IMPORTING Parameters details for COM_PARTNER_READ_DB

IV_PARTNERSET_GUID - GUID for a Partner Set (Partner Quantity)

Data type: COMT_PARTNERSET_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_PARTNERSET_GUIDS - List of Partner Set GUIDs

Data type: COMT_PARTNERSET_GUID_TAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for COM_PARTNER_READ_DB

ET_PARTNER_DB - Partnersets der angegebenen GUID

Data type: COMT_PARTNER_DB_TAB
Optional: No
Call by Reference: Yes

ET_ATTRIBUTES - Attribute der Partner im Partnerset

Data type: COMT_PARTNER_ATTR_TAB
Optional: No
Call by Reference: Yes

ET_CUST_ATTRIBUTES - Database Entries for COMD_PARTNER_ATT

Data type: COMT_PARTNER_CUST_ATTRIBUTE_DB
Optional: No
Call by Reference: Yes

ET_CUST_RELATIONS - Database Entries for COMD_PARTNER_REL

Data type: COMT_PARTNER_CUST_RELATIONS_DB
Optional: No
Call by Reference: Yes

ET_COMP_PRDS - Database Entries for COMD_PARCOMP_PRD

Data type: COMT_PARTNER_COMP_PRD_DB_T
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PARAMETER_ERROR - Error in Parameter Transfer

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RECORD_NOT_FOUND - Eintrag konnte nicht gefunden werden

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

AT_LEAST_ONE_RECORD_NOT_FOUND - Mindestens ein Eintrag konnte nicht gefunden werden

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for COM_PARTNER_READ_DB 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_et_partner_db  TYPE COMT_PARTNER_DB_TAB, "   
lv_parameter_error  TYPE COMT_PARTNER_DB_TAB, "   
lv_iv_partnerset_guid  TYPE COMT_PARTNERSET_GUID, "   
lv_et_attributes  TYPE COMT_PARTNER_ATTR_TAB, "   
lv_record_not_found  TYPE COMT_PARTNER_ATTR_TAB, "   
lv_it_partnerset_guids  TYPE COMT_PARTNERSET_GUID_TAB, "   
lv_et_cust_attributes  TYPE COMT_PARTNER_CUST_ATTRIBUTE_DB, "   
lv_at_least_one_record_not_found  TYPE COMT_PARTNER_CUST_ATTRIBUTE_DB, "   
lv_et_cust_relations  TYPE COMT_PARTNER_CUST_RELATIONS_DB, "   
lv_et_comp_prds  TYPE COMT_PARTNER_COMP_PRD_DB_T. "   

  CALL FUNCTION 'COM_PARTNER_READ_DB'  "Lesen eines Eintrags aus dem Datenbankpuffer bzw. von der Datenbank
    EXPORTING
         IV_PARTNERSET_GUID = lv_iv_partnerset_guid
         IT_PARTNERSET_GUIDS = lv_it_partnerset_guids
    IMPORTING
         ET_PARTNER_DB = lv_et_partner_db
         ET_ATTRIBUTES = lv_et_attributes
         ET_CUST_ATTRIBUTES = lv_et_cust_attributes
         ET_CUST_RELATIONS = lv_et_cust_relations
         ET_COMP_PRDS = lv_et_comp_prds
    EXCEPTIONS
        PARAMETER_ERROR = 1
        RECORD_NOT_FOUND = 2
        AT_LEAST_ONE_RECORD_NOT_FOUND = 3
. " COM_PARTNER_READ_DB




ABAP code using 7.40 inline data declarations to call FM COM_PARTNER_READ_DB

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!