SAP BBP_PD_CATEGORY_MAP Function Module for









BBP_PD_CATEGORY_MAP is a standard bbp pd category map 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 bbp pd category map FM, simply by entering the name BBP_PD_CATEGORY_MAP into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_PD_CATEGORY_MAP 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 'BBP_PD_CATEGORY_MAP'"
EXPORTING
* I_SCHEMA_TYPE = "
I_CATEGORY_ID = "

TABLES
* ET_CATEGORY = "

EXCEPTIONS
CATEGORY_NOT_FOUND = 1 SCHEMATYPE_NOT_FOUND = 2 MAPPING_NOT_POSSIBLE = 3
.



IMPORTING Parameters details for BBP_PD_CATEGORY_MAP

I_SCHEMA_TYPE -

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

I_CATEGORY_ID -

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

TABLES Parameters details for BBP_PD_CATEGORY_MAP

ET_CATEGORY -

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

EXCEPTIONS details

CATEGORY_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

SCHEMATYPE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

MAPPING_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_PD_CATEGORY_MAP 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:
lt_et_category  TYPE STANDARD TABLE OF BBP_CT_CATEGORY_MAP, "   
lv_i_schema_type  TYPE SCHEMA_TYPE, "   
lv_category_not_found  TYPE SCHEMA_TYPE, "   
lv_i_category_id  TYPE BBPT_CT_CATEGORY_ID_SELLER, "   
lv_schematype_not_found  TYPE BBPT_CT_CATEGORY_ID_SELLER, "   
lv_mapping_not_possible  TYPE BBPT_CT_CATEGORY_ID_SELLER. "   

  CALL FUNCTION 'BBP_PD_CATEGORY_MAP'  "
    EXPORTING
         I_SCHEMA_TYPE = lv_i_schema_type
         I_CATEGORY_ID = lv_i_category_id
    TABLES
         ET_CATEGORY = lt_et_category
    EXCEPTIONS
        CATEGORY_NOT_FOUND = 1
        SCHEMATYPE_NOT_FOUND = 2
        MAPPING_NOT_POSSIBLE = 3
. " BBP_PD_CATEGORY_MAP




ABAP code using 7.40 inline data declarations to call FM BBP_PD_CATEGORY_MAP

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!