SAP COM_PRDXI_CATEGORY_EXTRACT Function Module for

Search SAP Function Modules

COM_PRDXI_CATEGORY_EXTRACT is a standard com prdxi category extract 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 prdxi category extract FM, simply by entering the name COM_PRDXI_CATEGORY_EXTRACT into the relevant SAP transaction such as SE37 or SE38.

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

Function COM_PRDXI_CATEGORY_EXTRACT 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_PRDXI_CATEGORY_EXTRACT'"
  EXPORTING
   I_DISTMODE =  "Modus der Verteilung
   I_BLOCKSIZE =  "Anzahl der selektierten Objektinstanzen pro Datenpaket
   I_INITMODE =  "Checkbox
*  I_MESSENGERID =  "Name of target host

TABLES
   I_T_SELECT =  "
   I_T_TRANSFER =  "
*  E_T_IDOCNUM =  "
*  E_T_MESSNUM =  "
   E_T_MESSAGES =  "Anwendungs-Log: Schnittstelle für APPL_LOG_WRITE_MESSAGES

EXCEPTIONS
   EXTRACTION_FAILED = 1    NO_MORE_DATA = 2    WRONG_CALL = 3 

.

IMPORTING Parameters details for COM_PRDXI_CATEGORY_EXTRACT

I_DISTMODE - Modus der Verteilung

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

I_BLOCKSIZE - Anzahl der selektierten Objektinstanzen pro Datenpaket

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

I_INITMODE - Checkbox

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

I_MESSENGERID - Name of target host

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

TABLES Parameters details for COM_PRDXI_CATEGORY_EXTRACT

I_T_SELECT -

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

I_T_TRANSFER -

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

E_T_IDOCNUM -

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

E_T_MESSNUM -

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

E_T_MESSAGES - Anwendungs-Log: Schnittstelle für APPL_LOG_WRITE_MESSAGES

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

EXCEPTIONS details

EXTRACTION_FAILED -

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

NO_MORE_DATA -

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

WRONG_CALL -

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

Copy and paste ABAP code example for COM_PRDXI_CATEGORY_EXTRACT 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.

ABAP code using 7.40 inline data declarations to call FM COM_PRDXI_CATEGORY_EXTRACT

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