SAP BAPI_ASSET_TRANSFER_POST Function Module for Assets: Post Intracompany Transfer









BAPI_ASSET_TRANSFER_POST is a standard bapi asset transfer post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Assets: Post Intracompany Transfer 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 bapi asset transfer post FM, simply by entering the name BAPI_ASSET_TRANSFER_POST into the relevant SAP transaction such as SE37 or SE38.

Function Group: AMFA
Program Name: SAPLAMFA
Main Program: SAPLAMFA
Appliation area: A
Release date: 11-Jun-2013
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_ASSET_TRANSFER_POST 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 'BAPI_ASSET_TRANSFER_POST'"Assets: Post Intracompany Transfer
  EXPORTING
*  ORIGINDOCREFERENCE =  "Reference to original document
   GENERALPOSTINGDATA =  "Generally necessary posting specifications
   TRANSFERTODATA =  "Post Assets: Transfer To
   TRANSFERPOSTINGDATA =  "Post Assets: Transfer of Revenue/Distribution
*  ACCOUNTASSIGNMENTS =  "Possible addit. account assignments
*  FURTHERPOSTINGDATA =  "Additional posting specifications

 IMPORTING
   DOCUMENTREFERENCE =  "Referencing information to created FI/CO documents
   RETURN =  "Confirmations

TABLES
*  RETURN_ALL =  "Return Parameter(s)
.



IMPORTING Parameters details for BAPI_ASSET_TRANSFER_POST

ORIGINDOCREFERENCE - Reference to original document

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

GENERALPOSTINGDATA - Generally necessary posting specifications

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

TRANSFERTODATA - Post Assets: Transfer To

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

TRANSFERPOSTINGDATA - Post Assets: Transfer of Revenue/Distribution

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

ACCOUNTASSIGNMENTS - Possible addit. account assignments

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

FURTHERPOSTINGDATA - Additional posting specifications

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

EXPORTING Parameters details for BAPI_ASSET_TRANSFER_POST

DOCUMENTREFERENCE - Referencing information to created FI/CO documents

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

RETURN - Confirmations

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

TABLES Parameters details for BAPI_ASSET_TRANSFER_POST

RETURN_ALL - Return Parameter(s)

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

Copy and paste ABAP code example for BAPI_ASSET_TRANSFER_POST 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_return_all  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_documentreference  TYPE BAPIFAPO_DOC_REF, "   
lv_origindocreference  TYPE BAPIFAPO_DOC_REF, "   
lv_return  TYPE BAPIRET2, "   
lv_generalpostingdata  TYPE BAPIFAPO_GEN_INFO, "   
lv_transfertodata  TYPE BAPIFAPO_TRANSFER_TO, "   
lv_transferpostingdata  TYPE BAPIFAPO_TRANSFER_REV_DISTR, "   
lv_accountassignments  TYPE BAPIFAPO_ACC_ASS, "   
lv_furtherpostingdata  TYPE BAPIFAPO_ADD_INFO. "   

  CALL FUNCTION 'BAPI_ASSET_TRANSFER_POST'  "Assets: Post Intracompany Transfer
    EXPORTING
         ORIGINDOCREFERENCE = lv_origindocreference
         GENERALPOSTINGDATA = lv_generalpostingdata
         TRANSFERTODATA = lv_transfertodata
         TRANSFERPOSTINGDATA = lv_transferpostingdata
         ACCOUNTASSIGNMENTS = lv_accountassignments
         FURTHERPOSTINGDATA = lv_furtherpostingdata
    IMPORTING
         DOCUMENTREFERENCE = lv_documentreference
         RETURN = lv_return
    TABLES
         RETURN_ALL = lt_return_all
. " BAPI_ASSET_TRANSFER_POST




ABAP code using 7.40 inline data declarations to call FM BAPI_ASSET_TRANSFER_POST

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!