SAP BBP_PDDYN_GET_DIFF Function Module for









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

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



Function BBP_PDDYN_GET_DIFF 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_PDDYN_GET_DIFF'"
EXPORTING
IV_GUID_A = "
IV_GUID_B = "
IV_KIND = "
IV_COMP_METHOD = "
IV_GET_DIFF_FIELDS_TAB = "
* IV_OBJECT_TYPE = "
* IV_GET_ALL_SETLINES = "

IMPORTING
ET_DYNATTRIBUTE_DIFF_A = "
ET_DYNATTRIBUTE_DIFF_B = "
EV_SETS_DIFFER = "
ET_DYNATTRIBUTE_A = "
ET_DYNATTRIBUTE_B = "

TABLES
* ET_DIFF_FIELDS = "
.



IMPORTING Parameters details for BBP_PDDYN_GET_DIFF

IV_GUID_A -

Data type: CRMD_ORDERADM_H-GUID
Optional: No
Call by Reference: Yes

IV_GUID_B -

Data type: CRMD_ORDERADM_H-GUID
Optional: No
Call by Reference: Yes

IV_KIND -

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

IV_COMP_METHOD -

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

IV_GET_DIFF_FIELDS_TAB -

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

IV_OBJECT_TYPE -

Data type: CRMD_ORDERADM_H-OBJECT_TYPE
Optional: Yes
Call by Reference: Yes

IV_GET_ALL_SETLINES -

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

EXPORTING Parameters details for BBP_PDDYN_GET_DIFF

ET_DYNATTRIBUTE_DIFF_A -

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

ET_DYNATTRIBUTE_DIFF_B -

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

EV_SETS_DIFFER -

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

ET_DYNATTRIBUTE_A -

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

ET_DYNATTRIBUTE_B -

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

TABLES Parameters details for BBP_PDDYN_GET_DIFF

ET_DIFF_FIELDS -

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

Copy and paste ABAP code example for BBP_PDDYN_GET_DIFF 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_iv_guid_a  TYPE CRMD_ORDERADM_H-GUID, "   
lt_et_diff_fields  TYPE STANDARD TABLE OF BBP_PDS_DIFF_FIELDS, "   
lv_et_dynattribute_diff_a  TYPE BBPT_PDS_DYNATTR_DIFF, "   
lv_iv_guid_b  TYPE CRMD_ORDERADM_H-GUID, "   
lv_et_dynattribute_diff_b  TYPE BBPT_PDS_DYNATTR_DIFF, "   
lv_iv_kind  TYPE CRMT_OBJECT_KIND, "   
lv_ev_sets_differ  TYPE XFELD, "   
lv_iv_comp_method  TYPE BBP_COMPARE_METHOD, "   
lv_et_dynattribute_a  TYPE BBPT_PDS_DYNATTR_IC, "   
lv_et_dynattribute_b  TYPE BBPT_PDS_DYNATTR_IC, "   
lv_iv_get_diff_fields_tab  TYPE XFELD, "   
lv_iv_object_type  TYPE CRMD_ORDERADM_H-OBJECT_TYPE, "   
lv_iv_get_all_setlines  TYPE XFELD. "   

  CALL FUNCTION 'BBP_PDDYN_GET_DIFF'  "
    EXPORTING
         IV_GUID_A = lv_iv_guid_a
         IV_GUID_B = lv_iv_guid_b
         IV_KIND = lv_iv_kind
         IV_COMP_METHOD = lv_iv_comp_method
         IV_GET_DIFF_FIELDS_TAB = lv_iv_get_diff_fields_tab
         IV_OBJECT_TYPE = lv_iv_object_type
         IV_GET_ALL_SETLINES = lv_iv_get_all_setlines
    IMPORTING
         ET_DYNATTRIBUTE_DIFF_A = lv_et_dynattribute_diff_a
         ET_DYNATTRIBUTE_DIFF_B = lv_et_dynattribute_diff_b
         EV_SETS_DIFFER = lv_ev_sets_differ
         ET_DYNATTRIBUTE_A = lv_et_dynattribute_a
         ET_DYNATTRIBUTE_B = lv_et_dynattribute_b
    TABLES
         ET_DIFF_FIELDS = lt_et_diff_fields
. " BBP_PDDYN_GET_DIFF




ABAP code using 7.40 inline data declarations to call FM BBP_PDDYN_GET_DIFF

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.

"SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_guid_a).
 
 
 
"SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_guid_b).
 
 
 
 
 
 
 
 
"SELECT single OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_type).
 
 


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!