BBP_PDORG_GETDETAIL SAP Function module

BBP_PDORG_GETDETAIL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BBP_PDORG_GETDETAIL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BBP_PDORG
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BBP_PDORG_GETDETAIL - BBP PDORG GETDETAIL

CALL FUNCTION 'BBP_PDORG_GETDETAIL' "
  EXPORTING
    i_p_guid =                  " crmd_orderadm_h-guid
    i_p_kind =                  " crmt_object_kind
    i_object_type =             " crmd_orderadm_h-object_type
*   i_read_texts =              " xfeld
*   i_with_itemdata =           " xfeld
  TABLES
    e_orgdata =                 " bbp_pds_org
    .  "  BBP_PDORG_GETDETAIL

ABAP code example for Function Module BBP_PDORG_GETDETAIL

The ABAP code below is a full code listing to execute function module BBP_PDORG_GETDETAIL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_e_orgdata  
 
 TYPE STANDARD TABLE OF BBP_PDS_ORG,"TABLES PARAM
wa_e_orgdata
 
 LIKE LINE OF it_e_orgdata
.

 

SELECT single GUID 
  FROM CRMD_ORDERADM_H 
  INTO @DATA(ld_i_p_guid).


DATA(ld_i_p_kind) = 'Check type of data required'.
 

SELECT single OBJECT_TYPE 
  FROM CRMD_ORDERADM_H 
  INTO @DATA(ld_i_object_type).


DATA(ld_i_read_texts) = 'Check type of data required'.

DATA(ld_i_with_itemdata) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_e_orgdata to it_e_orgdata.
.

CALL FUNCTION 'BBP_PDORG_GETDETAIL'
  EXPORTING
    i_p_guid =                   ld_i_p_guid
    i_p_kind =                   ld_i_p_kind
    i_object_type =              ld_i_object_type
*   i_read_texts =               ld_i_read_texts
*   i_with_itemdata =            ld_i_with_itemdata
  TABLES
    e_orgdata =                  it_e_orgdata
    .  "  BBP_PDORG_GETDETAIL

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_i_p_guid
 
 TYPE CRMD_ORDERADM_H-GUID ,
it_e_orgdata
 
 TYPE STANDARD TABLE OF BBP_PDS_ORG ,
wa_e_orgdata
 
 LIKE LINE OF it_e_orgdata,
ld_i_p_kind
 
 TYPE CRMT_OBJECT_KIND ,
ld_i_object_type
 
 TYPE CRMD_ORDERADM_H-OBJECT_TYPE ,
ld_i_read_texts
 
 TYPE XFELD ,
ld_i_with_itemdata
 
 TYPE XFELD .



SELECT single GUID 
  FROM CRMD_ORDERADM_H 
  INTO ld_i_p_guid.
 

"populate fields of struture and append to itab
append wa_e_orgdata to it_e_orgdata.
ld_i_p_kind = 'Check type of data required'.

SELECT single OBJECT_TYPE 
  FROM CRMD_ORDERADM_H 
  INTO ld_i_object_type.

ld_i_read_texts = 'Check type of data required'.
ld_i_with_itemdata = 'Check type of data required'.