SAP BAPI_ACC_GOODS_MOVEMENT_POST Function Module for Accounting: Post Goods Movement (OAG: POST JOURNAL)









BAPI_ACC_GOODS_MOVEMENT_POST is a standard bapi acc goods movement 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 Accounting: Post Goods Movement (OAG: POST JOURNAL) 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 acc goods movement post FM, simply by entering the name BAPI_ACC_GOODS_MOVEMENT_POST into the relevant SAP transaction such as SE37 or SE38.

Function Group: ACC4
Program Name: SAPLACC4
Main Program: SAPLACC4
Appliation area:
Release date: 17-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_ACC_GOODS_MOVEMENT_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_ACC_GOODS_MOVEMENT_POST'"Accounting: Post Goods Movement (OAG: POST JOURNAL)
  EXPORTING
   DOCUMENTHEADER =  "Document Header

 IMPORTING
   OBJ_TYPE =  "Reference Transaction
   OBJ_KEY =  "Reference Key
   OBJ_SYS =  "Reference System

TABLES
   ACCOUNTGL =  "G/L Account Line Items
   CURRENCYAMOUNT =  "Line Item Currency Fields
*  PURCHASEORDER =  "Purchase Order Line Items
*  PURCHASEAMOUNT =  "Purchase Order Currency Fields
   RETURN =  "Return Parameter
*  CRITERIA =  "CO-PA Characteristics
*  VALUEFIELD =  "CO-PA Value Components
*  EXTENSION1 =  "Table for Customer Enhancement
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLACC4_001 Accounting: User Exit for Posting BAPI

IMPORTING Parameters details for BAPI_ACC_GOODS_MOVEMENT_POST

DOCUMENTHEADER - Document Header

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

EXPORTING Parameters details for BAPI_ACC_GOODS_MOVEMENT_POST

OBJ_TYPE - Reference Transaction

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

OBJ_KEY - Reference Key

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

OBJ_SYS - Reference System

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

TABLES Parameters details for BAPI_ACC_GOODS_MOVEMENT_POST

ACCOUNTGL - G/L Account Line Items

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

CURRENCYAMOUNT - Line Item Currency Fields

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

PURCHASEORDER - Purchase Order Line Items

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

PURCHASEAMOUNT - Purchase Order Currency Fields

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

RETURN - Return Parameter

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

CRITERIA - CO-PA Characteristics

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

VALUEFIELD - CO-PA Value Components

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

EXTENSION1 - Table for Customer Enhancement

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

Copy and paste ABAP code example for BAPI_ACC_GOODS_MOVEMENT_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:
lv_obj_type  TYPE BAPIACHE02-OBJ_TYPE, "   
lt_accountgl  TYPE STANDARD TABLE OF BAPIACGL02, "   
lv_documentheader  TYPE BAPIACHE02, "   
lv_obj_key  TYPE BAPIACHE02-OBJ_KEY, "   
lt_currencyamount  TYPE STANDARD TABLE OF BAPIACCR01, "   
lv_obj_sys  TYPE BAPIACHE02-OBJ_SYS, "   
lt_purchaseorder  TYPE STANDARD TABLE OF BAPIACPO00, "   
lt_purchaseamount  TYPE STANDARD TABLE OF BAPIACCRPO, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_criteria  TYPE STANDARD TABLE OF BAPIACKECR, "   
lt_valuefield  TYPE STANDARD TABLE OF BAPIACKEVA, "   
lt_extension1  TYPE STANDARD TABLE OF BAPIEXTC. "   

  CALL FUNCTION 'BAPI_ACC_GOODS_MOVEMENT_POST'  "Accounting: Post Goods Movement (OAG: POST JOURNAL)
    EXPORTING
         DOCUMENTHEADER = lv_documentheader
    IMPORTING
         OBJ_TYPE = lv_obj_type
         OBJ_KEY = lv_obj_key
         OBJ_SYS = lv_obj_sys
    TABLES
         ACCOUNTGL = lt_accountgl
         CURRENCYAMOUNT = lt_currencyamount
         PURCHASEORDER = lt_purchaseorder
         PURCHASEAMOUNT = lt_purchaseamount
         RETURN = lt_return
         CRITERIA = lt_criteria
         VALUEFIELD = lt_valuefield
         EXTENSION1 = lt_extension1
. " BAPI_ACC_GOODS_MOVEMENT_POST




ABAP code using 7.40 inline data declarations to call FM BAPI_ACC_GOODS_MOVEMENT_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.

"SELECT single OBJ_TYPE FROM BAPIACHE02 INTO @DATA(ld_obj_type).
 
 
 
"SELECT single OBJ_KEY FROM BAPIACHE02 INTO @DATA(ld_obj_key).
 
 
"SELECT single OBJ_SYS FROM BAPIACHE02 INTO @DATA(ld_obj_sys).
 
 
 
 
 
 
 


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!