SAP COM_PARTNER_TYPES_INFO_GET Function Module for









COM_PARTNER_TYPES_INFO_GET is a standard com partner types info get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 types info get FM, simply by entering the name COM_PARTNER_TYPES_INFO_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function COM_PARTNER_TYPES_INFO_GET 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_TYPES_INFO_GET'"
EXPORTING
* IV_PARTNER_PFT = "Partner function category
* IV_PFT_SUBTYPE = "Partner Function Sub-Type

IMPORTING
EV_PFT_DESCRIPTION = "Text (30 Characters)
EV_SUBTYPE_DESCRIPTION = "Text (30 Characters)

EXCEPTIONS
TYPE_UNKOWN = 1 SUBTYPE_UNKOWN = 2
.



IMPORTING Parameters details for COM_PARTNER_TYPES_INFO_GET

IV_PARTNER_PFT - Partner function category

Data type: COMT_PARTNER_PFT
Optional: Yes
Call by Reference: Yes

IV_PFT_SUBTYPE - Partner Function Sub-Type

Data type: COMT_PARTNER_SUBTYPE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for COM_PARTNER_TYPES_INFO_GET

EV_PFT_DESCRIPTION - Text (30 Characters)

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

EV_SUBTYPE_DESCRIPTION - Text (30 Characters)

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

EXCEPTIONS details

TYPE_UNKOWN -

Data type:
Optional: No
Call by Reference: Yes

SUBTYPE_UNKOWN -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COM_PARTNER_TYPES_INFO_GET 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_type_unkown  TYPE STRING, "   
lv_iv_partner_pft  TYPE COMT_PARTNER_PFT, "   
lv_ev_pft_description  TYPE TEXT30, "   
lv_iv_pft_subtype  TYPE COMT_PARTNER_SUBTYPE, "   
lv_subtype_unkown  TYPE COMT_PARTNER_SUBTYPE, "   
lv_ev_subtype_description  TYPE TEXT30. "   

  CALL FUNCTION 'COM_PARTNER_TYPES_INFO_GET'  "
    EXPORTING
         IV_PARTNER_PFT = lv_iv_partner_pft
         IV_PFT_SUBTYPE = lv_iv_pft_subtype
    IMPORTING
         EV_PFT_DESCRIPTION = lv_ev_pft_description
         EV_SUBTYPE_DESCRIPTION = lv_ev_subtype_description
    EXCEPTIONS
        TYPE_UNKOWN = 1
        SUBTYPE_UNKOWN = 2
. " COM_PARTNER_TYPES_INFO_GET




ABAP code using 7.40 inline data declarations to call FM COM_PARTNER_TYPES_INFO_GET

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!