SAP BBP_GET_ORDERING_PARTY_MAPV Function Module for









BBP_GET_ORDERING_PARTY_MAPV is a standard bbp get ordering party mapv 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 get ordering party mapv FM, simply by entering the name BBP_GET_ORDERING_PARTY_MAPV into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_GET_ORDERING_PARTY_MAPV 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_GET_ORDERING_PARTY_MAPV'"
EXPORTING
IV_FROM_PFT = "

CHANGING
CT_PARTNER = "

EXCEPTIONS
BASE_NOT_FOUND = 1 COMPANY_NOT_FOUND = 2 ADDRESS_NOT_FOUND = 3
.



IMPORTING Parameters details for BBP_GET_ORDERING_PARTY_MAPV

IV_FROM_PFT -

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

CHANGING Parameters details for BBP_GET_ORDERING_PARTY_MAPV

CT_PARTNER -

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

EXCEPTIONS details

BASE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

COMPANY_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ADDRESS_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_GET_ORDERING_PARTY_MAPV 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_ct_partner  TYPE BBPT_PD_PARTNER, "   
lv_iv_from_pft  TYPE BBP_PARTNER_FTYP, "   
lv_base_not_found  TYPE BBP_PARTNER_FTYP, "   
lv_company_not_found  TYPE BBP_PARTNER_FTYP, "   
lv_address_not_found  TYPE BBP_PARTNER_FTYP. "   

  CALL FUNCTION 'BBP_GET_ORDERING_PARTY_MAPV'  "
    EXPORTING
         IV_FROM_PFT = lv_iv_from_pft
    CHANGING
         CT_PARTNER = lv_ct_partner
    EXCEPTIONS
        BASE_NOT_FOUND = 1
        COMPANY_NOT_FOUND = 2
        ADDRESS_NOT_FOUND = 3
. " BBP_GET_ORDERING_PARTY_MAPV




ABAP code using 7.40 inline data declarations to call FM BBP_GET_ORDERING_PARTY_MAPV

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!