SAP BBP_PD_CONF_GETDETAIL Function Module for Holen Daten zu eine Rückmeldung









BBP_PD_CONF_GETDETAIL is a standard bbp pd conf getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Holen Daten zu eine Rückmeldung 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 pd conf getdetail FM, simply by entering the name BBP_PD_CONF_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_PD_CONF_GETDETAIL 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_CONF_GETDETAIL'"Holen Daten zu eine Rückmeldung
EXPORTING
* I_GUID = "Globally Unique Identifier
* I_OBJECT_ID = "Vorgangsnummer
* I_REF_DOC_NO = "Referenz-Belegnummer
* I_PARTNER_NO = "Partnernummer
* I_WITH_ITEMDATA = 'X' "Mit Itemdaten
* I_ATTACH_WITH_DOC = ' ' "Attachments incl. Dokument
* I_ITEM_SORTED_BY_HIERARCHY = 'X' "Soll E_ITEM nach Hierarchien sortiert werden?
* I_READ_FROM_ARCHIVE = ' ' "Soll das Beleg-Objekt vom Archiv gelesen werden?

IMPORTING
E_HEADER = "Schnittstelle Kopf-Daten Bestellung GetDetail-Fa
ET_ATTACH = "KW-Anlagen inkl. Dokument

TABLES
* E_ITEM = "Schnittstelle Positions-Daten Beschaffungs-Beleg
* E_ICF = "Tabellenartige Kunden- und Solutionfelder an der Position
* E_ACTVAL = "Ist-Werte und Mengen
* E_ACC_ACTVAL = "Ist-Werte und Mengen
* E_HEADER_REL = "Belegfluß auf Kopfebene
* E_ITM_REL = "Belegfluß auf Positionenebene
* E_OVE_REL = "Verknüpfungen zur Online-Lieferantenbewertung
* E_PRIDOC = "Belegkonditionen
* E_HISTORY_ARCH = "
* E_ACCOUNT = "Kontierungs-Set
* E_PARTNER = "Geschäftspartner-Set
* E_LONGTEXT = "Langtexte zum Procurement Document
* E_ORGDATA = "Org-Daten
* E_STATUS = "Einzelstatus
* E_MESSAGES = "Fehlermeldungen zu einer PD-Methode
* E_TAX = "Steuern
* E_HCF = "Tabellenartige Kunden- und Solutionfelder am Kopf
.



IMPORTING Parameters details for BBP_PD_CONF_GETDETAIL

I_GUID - Globally Unique Identifier

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

I_OBJECT_ID - Vorgangsnummer

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

I_REF_DOC_NO - Referenz-Belegnummer

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

I_PARTNER_NO - Partnernummer

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

I_WITH_ITEMDATA - Mit Itemdaten

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ATTACH_WITH_DOC - Attachments incl. Dokument

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

I_ITEM_SORTED_BY_HIERARCHY - Soll E_ITEM nach Hierarchien sortiert werden?

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_READ_FROM_ARCHIVE - Soll das Beleg-Objekt vom Archiv gelesen werden?

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

EXPORTING Parameters details for BBP_PD_CONF_GETDETAIL

E_HEADER - Schnittstelle Kopf-Daten Bestellung GetDetail-Fa

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

ET_ATTACH - KW-Anlagen inkl. Dokument

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

TABLES Parameters details for BBP_PD_CONF_GETDETAIL

E_ITEM - Schnittstelle Positions-Daten Beschaffungs-Beleg

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

E_ICF - Tabellenartige Kunden- und Solutionfelder an der Position

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

E_ACTVAL - Ist-Werte und Mengen

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

E_ACC_ACTVAL - Ist-Werte und Mengen

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

E_HEADER_REL - Belegfluß auf Kopfebene

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

E_ITM_REL - Belegfluß auf Positionenebene

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

E_OVE_REL - Verknüpfungen zur Online-Lieferantenbewertung

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

E_PRIDOC - Belegkonditionen

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

E_HISTORY_ARCH -

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

E_ACCOUNT - Kontierungs-Set

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

E_PARTNER - Geschäftspartner-Set

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

E_LONGTEXT - Langtexte zum Procurement Document

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

E_ORGDATA - Org-Daten

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

E_STATUS - Einzelstatus

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

E_MESSAGES - Fehlermeldungen zu einer PD-Methode

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

E_TAX - Steuern

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

E_HCF - Tabellenartige Kunden- und Solutionfelder am Kopf

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

Copy and paste ABAP code example for BBP_PD_CONF_GETDETAIL 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_e_item  TYPE STANDARD TABLE OF BBP_PDS_CONF_ITEM_D, "   
lv_i_guid  TYPE CRMD_ORDERADM_H-GUID, "   
lv_e_header  TYPE BBP_PDS_CONF_HEADER_D, "   
lt_e_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_CONF, "   
lt_e_actval  TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, "   
lt_e_acc_actval  TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, "   
lt_e_header_rel  TYPE STANDARD TABLE OF BBP_PDS_HREL, "   
lt_e_itm_rel  TYPE STANDARD TABLE OF BBP_PDS_ILREL, "   
lt_e_ove_rel  TYPE STANDARD TABLE OF BBP_PDS_OVE_REL, "   
lt_e_pridoc  TYPE STANDARD TABLE OF BBP_PDS_PRC, "   
lt_e_history_arch  TYPE STANDARD TABLE OF BBP_PDS_HISTORY_ARCH, "   
lv_et_attach  TYPE BBPT_PDS_ATT_T, "   
lt_e_account  TYPE STANDARD TABLE OF BBP_PDS_ACC, "   
lv_i_object_id  TYPE CRMD_ORDERADM_H-OBJECT_ID, "   
lt_e_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lv_i_ref_doc_no  TYPE BBP_PDHGP-REF_DOC_NO, "   
lt_e_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lv_i_partner_no  TYPE CRMD_PARTNER-PARTNER_NO, "   
lt_e_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lv_i_with_itemdata  TYPE XFELD, "   'X'
lt_e_status  TYPE STANDARD TABLE OF BBP_PDS_STATUS, "   
lv_i_attach_with_doc  TYPE XFELD, "   SPACE
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_i_item_sorted_by_hierarchy  TYPE XFELD, "   'X'
lt_e_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX, "   
lv_i_read_from_archive  TYPE XFELD, "   SPACE
lt_e_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_CONF. "   

  CALL FUNCTION 'BBP_PD_CONF_GETDETAIL'  "Holen Daten zu eine Rückmeldung
    EXPORTING
         I_GUID = lv_i_guid
         I_OBJECT_ID = lv_i_object_id
         I_REF_DOC_NO = lv_i_ref_doc_no
         I_PARTNER_NO = lv_i_partner_no
         I_WITH_ITEMDATA = lv_i_with_itemdata
         I_ATTACH_WITH_DOC = lv_i_attach_with_doc
         I_ITEM_SORTED_BY_HIERARCHY = lv_i_item_sorted_by_hierarchy
         I_READ_FROM_ARCHIVE = lv_i_read_from_archive
    IMPORTING
         E_HEADER = lv_e_header
         ET_ATTACH = lv_et_attach
    TABLES
         E_ITEM = lt_e_item
         E_ICF = lt_e_icf
         E_ACTVAL = lt_e_actval
         E_ACC_ACTVAL = lt_e_acc_actval
         E_HEADER_REL = lt_e_header_rel
         E_ITM_REL = lt_e_itm_rel
         E_OVE_REL = lt_e_ove_rel
         E_PRIDOC = lt_e_pridoc
         E_HISTORY_ARCH = lt_e_history_arch
         E_ACCOUNT = lt_e_account
         E_PARTNER = lt_e_partner
         E_LONGTEXT = lt_e_longtext
         E_ORGDATA = lt_e_orgdata
         E_STATUS = lt_e_status
         E_MESSAGES = lt_e_messages
         E_TAX = lt_e_tax
         E_HCF = lt_e_hcf
. " BBP_PD_CONF_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM BBP_PD_CONF_GETDETAIL

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_i_guid).
 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_i_object_id).
 
 
"SELECT single REF_DOC_NO FROM BBP_PDHGP INTO @DATA(ld_i_ref_doc_no).
 
 
"SELECT single PARTNER_NO FROM CRMD_PARTNER INTO @DATA(ld_i_partner_no).
 
 
DATA(ld_i_with_itemdata) = 'X'.
 
 
DATA(ld_i_attach_with_doc) = ' '.
 
 
DATA(ld_i_item_sorted_by_hierarchy) = 'X'.
 
 
DATA(ld_i_read_from_archive) = ' '.
 
 


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!