SAP BAPO30A_DPO_TRANSFER Function Module for Transfer DPO to APO system









BAPO30A_DPO_TRANSFER is a standard bapo30a dpo transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transfer DPO to APO system 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 bapo30a dpo transfer FM, simply by entering the name BAPO30A_DPO_TRANSFER into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPO30A_DPO_TRANSFER 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 'BAPO30A_DPO_TRANSFER'"Transfer DPO to APO system
EXPORTING
I_HEADER = "Header Data Purchase Order GetDetail-Case Interface
I_LOGICAL_SYSTEM = "Logical system
IT_ATTACH = "KW-Anlagen inkl. Dokument

TABLES
I_ITEM = "Item Data Purchase Order GetDetail-Case Interface
I_ACC_ACTVAL = "Actual Value and Amount
I_HEADER_REL = "Header Links Procurement Document
I_ITMLIM_REL = "Item-/Limit Link, Header Link Procurement Document
I_STATUS = "Status
E_MESSAGES = "Fehlermeldungen zu einer PD-Methode
CONTROL_RECORD = "Control Record for META BAPI control
* I_TOLERANCE = "Toleranzen
I_ACCOUNT = "Account Assignment
I_PARTNER = "Business Partner
I_CONFIRM = "Purchase Order Confirmation (Confirmation)
I_LONGTEXT = "Long Texts for Procurement Document
I_LIMIT = "Value Limit
I_ORGDATA = "Organizational Data
I_TAX = "Steuern
I_ACTVAL = "Actual Value and Amount
.



IMPORTING Parameters details for BAPO30A_DPO_TRANSFER

I_HEADER - Header Data Purchase Order GetDetail-Case Interface

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

I_LOGICAL_SYSTEM - Logical system

Data type: BBP_BACKEND_DEST-LOG_SYS
Optional: No
Call by Reference: No ( called with pass by value option)

IT_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 BAPO30A_DPO_TRANSFER

I_ITEM - Item Data Purchase Order GetDetail-Case Interface

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

I_ACC_ACTVAL - Actual Value and Amount

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

I_HEADER_REL - Header Links Procurement Document

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

I_ITMLIM_REL - Item-/Limit Link, Header Link Procurement Document

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

I_STATUS - Status

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

E_MESSAGES - Fehlermeldungen zu einer PD-Methode

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

CONTROL_RECORD - Control Record for META BAPI control

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

I_TOLERANCE - Toleranzen

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

I_ACCOUNT - Account Assignment

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

I_PARTNER - Business Partner

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

I_CONFIRM - Purchase Order Confirmation (Confirmation)

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

I_LONGTEXT - Long Texts for Procurement Document

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

I_LIMIT - Value Limit

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

I_ORGDATA - Organizational Data

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

I_TAX - Steuern

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

I_ACTVAL - Actual Value and Amount

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

Copy and paste ABAP code example for BAPO30A_DPO_TRANSFER 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_i_item  TYPE STANDARD TABLE OF BBP_PDS_PO_ITEM_D, "   
lv_i_header  TYPE BBP_PDS_PO_HEADER_D, "   
lt_i_acc_actval  TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, "   
lt_i_header_rel  TYPE STANDARD TABLE OF BBP_PDS_HREL, "   
lt_i_itmlim_rel  TYPE STANDARD TABLE OF BBP_PDS_ILREL, "   
lt_i_status  TYPE STANDARD TABLE OF BBP_PDS_STATUS, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lt_control_record  TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, "   
lt_i_tolerance  TYPE STANDARD TABLE OF BBP_PDS_TOL, "   
lt_i_account  TYPE STANDARD TABLE OF BBP_PDS_ACC, "   
lv_i_logical_system  TYPE BBP_BACKEND_DEST-LOG_SYS, "   
lv_it_attach  TYPE BBPT_PDS_ATT_T, "   
lt_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lt_i_confirm  TYPE STANDARD TABLE OF BBP_PDS_CON, "   
lt_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lt_i_limit  TYPE STANDARD TABLE OF BBP_PDS_LIMIT, "   
lt_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lt_i_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX, "   
lt_i_actval  TYPE STANDARD TABLE OF BBP_PDS_ACTVAL. "   

  CALL FUNCTION 'BAPO30A_DPO_TRANSFER'  "Transfer DPO to APO system
    EXPORTING
         I_HEADER = lv_i_header
         I_LOGICAL_SYSTEM = lv_i_logical_system
         IT_ATTACH = lv_it_attach
    TABLES
         I_ITEM = lt_i_item
         I_ACC_ACTVAL = lt_i_acc_actval
         I_HEADER_REL = lt_i_header_rel
         I_ITMLIM_REL = lt_i_itmlim_rel
         I_STATUS = lt_i_status
         E_MESSAGES = lt_e_messages
         CONTROL_RECORD = lt_control_record
         I_TOLERANCE = lt_i_tolerance
         I_ACCOUNT = lt_i_account
         I_PARTNER = lt_i_partner
         I_CONFIRM = lt_i_confirm
         I_LONGTEXT = lt_i_longtext
         I_LIMIT = lt_i_limit
         I_ORGDATA = lt_i_orgdata
         I_TAX = lt_i_tax
         I_ACTVAL = lt_i_actval
. " BAPO30A_DPO_TRANSFER




ABAP code using 7.40 inline data declarations to call FM BAPO30A_DPO_TRANSFER

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 LOG_SYS FROM BBP_BACKEND_DEST INTO @DATA(ld_i_logical_system).
 
 
 
 
 
 
 
 
 


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!