SAP BBP_PDH_TRANSFORM_LOCATION Function Module for Umsetzung von Altbelegen auf Standorte









BBP_PDH_TRANSFORM_LOCATION is a standard bbp pdh transform location SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Umsetzung von Altbelegen auf Standorte 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 bbp pdh transform location FM, simply by entering the name BBP_PDH_TRANSFORM_LOCATION into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_PDH_TRANSFORM_LOCATION 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_PDH_TRANSFORM_LOCATION'"Umsetzung von Altbelegen auf Standorte
  EXPORTING
*  IV_TESTMODE =  "neue Eingabewerte
*  IV_WRITE_MESSAGES =  "neue Eingabewerte

 IMPORTING
   EV_SUCCESS =  "Numerisches Characterfeld der Länge 10
   EV_FAILURE =  "Numerisches Characterfeld der Länge 10

CHANGING
   CT_BACKEND =  "Logische Systeme

TABLES
*  IT_RANGE_OBJECT_ID =  "Interface Struktur für Ranges der Objekt-ID
*  IT_RANGE_OBJECT_TYPE =  "Interface Struktur für Ranges der Objekt-Types
*  ET_MESSAGES =  "Fehlermeldungen zu einer PD-Methode
.



IMPORTING Parameters details for BBP_PDH_TRANSFORM_LOCATION

IV_TESTMODE - neue Eingabewerte

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

IV_WRITE_MESSAGES - neue Eingabewerte

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

EXPORTING Parameters details for BBP_PDH_TRANSFORM_LOCATION

EV_SUCCESS - Numerisches Characterfeld der Länge 10

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

EV_FAILURE - Numerisches Characterfeld der Länge 10

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

CHANGING Parameters details for BBP_PDH_TRANSFORM_LOCATION

CT_BACKEND - Logische Systeme

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

TABLES Parameters details for BBP_PDH_TRANSFORM_LOCATION

IT_RANGE_OBJECT_ID - Interface Struktur für Ranges der Objekt-ID

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

IT_RANGE_OBJECT_TYPE - Interface Struktur für Ranges der Objekt-Types

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

ET_MESSAGES - Fehlermeldungen zu einer PD-Methode

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

Copy and paste ABAP code example for BBP_PDH_TRANSFORM_LOCATION 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_backend  TYPE BBPT_LOGICAL_SYSTEM, "   
lv_ev_success  TYPE NUMC10, "   
lv_iv_testmode  TYPE XFLAG, "   
lt_it_range_object_id  TYPE STANDARD TABLE OF BBP_PDS_RANGE_OBJECT_ID, "   
lv_ev_failure  TYPE NUMC10, "   
lv_iv_write_messages  TYPE XFLAG, "   
lt_it_range_object_type  TYPE STANDARD TABLE OF BBP_PDS_RANGE_OBJECT_TYPE, "   
lt_et_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES. "   

  CALL FUNCTION 'BBP_PDH_TRANSFORM_LOCATION'  "Umsetzung von Altbelegen auf Standorte
    EXPORTING
         IV_TESTMODE = lv_iv_testmode
         IV_WRITE_MESSAGES = lv_iv_write_messages
    IMPORTING
         EV_SUCCESS = lv_ev_success
         EV_FAILURE = lv_ev_failure
    CHANGING
         CT_BACKEND = lv_ct_backend
    TABLES
         IT_RANGE_OBJECT_ID = lt_it_range_object_id
         IT_RANGE_OBJECT_TYPE = lt_it_range_object_type
         ET_MESSAGES = lt_et_messages
. " BBP_PDH_TRANSFORM_LOCATION




ABAP code using 7.40 inline data declarations to call FM BBP_PDH_TRANSFORM_LOCATION

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!