SAP ALE_ACC_GOODS_MOVEMENT_POST Function Module for
ALE_ACC_GOODS_MOVEMENT_POST is a standard ale 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 to perform a specific ABAP function and below is the pattern details, 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 ale acc goods movement post FM, simply by entering the name ALE_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: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ALE_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 'ALE_ACC_GOODS_MOVEMENT_POST'".
EXPORTING
DOCUMENTHEADER = "Document header
* OBJ_TYPE = 'BUS6002' "Reference Transaction
* SERIAL_ID = '0' "
TABLES
ACCOUNTGL = "G/L Account Line Items
* APPLICATION_OBJECTS = "
CURRENCYAMOUNT = "Line item currency fields
* PURCHASEORDER = "Purchase Order Line Items
* PURCHASEAMOUNT = "Purchase Order Currency Fields
* CRITERIA = "CO-PA Characteristics
* VALUEFIELD = "CO-PA value components
* EXTENSION1 = "Table for Customer Enhancement
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
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 ALE_ACC_GOODS_MOVEMENT_POST
DOCUMENTHEADER - Document header
Data type: BAPIACHE02Optional: No
Call by Reference: No ( called with pass by value option)
OBJ_TYPE - Reference Transaction
Data type: SERIAL-OBJ_TYPEDefault: 'BUS6002'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_ACC_GOODS_MOVEMENT_POST
ACCOUNTGL - G/L Account Line Items
Data type: BAPIACGL02Optional: No
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
CURRENCYAMOUNT - Line item currency fields
Data type: BAPIACCR01Optional: No
Call by Reference: No ( called with pass by value option)
PURCHASEORDER - Purchase Order Line Items
Data type: BAPIACPO00Optional: Yes
Call by Reference: No ( called with pass by value option)
PURCHASEAMOUNT - Purchase Order Currency Fields
Data type: BAPIACCRPOOptional: Yes
Call by Reference: No ( called with pass by value option)
CRITERIA - CO-PA Characteristics
Data type: BAPIACKECROptional: Yes
Call by Reference: No ( called with pass by value option)
VALUEFIELD - CO-PA value components
Data type: BAPIACKEVAOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSION1 - Table for Customer Enhancement
Data type: BAPIEXTCOptional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_CREATING_IDOCS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ALE_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: | ||||
lt_accountgl | TYPE STANDARD TABLE OF BAPIACGL02, " | |||
lv_documentheader | TYPE BAPIACHE02, " | |||
lv_error_creating_idocs | TYPE BAPIACHE02, " | |||
lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS6002' | |||
lt_currencyamount | TYPE STANDARD TABLE OF BAPIACCR01, " | |||
lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
lt_purchaseorder | TYPE STANDARD TABLE OF BAPIACPO00, " | |||
lt_purchaseamount | TYPE STANDARD TABLE OF BAPIACCRPO, " | |||
lt_criteria | TYPE STANDARD TABLE OF BAPIACKECR, " | |||
lt_valuefield | TYPE STANDARD TABLE OF BAPIACKEVA, " | |||
lt_extension1 | TYPE STANDARD TABLE OF BAPIEXTC, " | |||
lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID. " |
  CALL FUNCTION 'ALE_ACC_GOODS_MOVEMENT_POST' " |
EXPORTING | ||
DOCUMENTHEADER | = lv_documentheader | |
OBJ_TYPE | = lv_obj_type | |
SERIAL_ID | = lv_serial_id | |
TABLES | ||
ACCOUNTGL | = lt_accountgl | |
APPLICATION_OBJECTS | = lt_application_objects | |
CURRENCYAMOUNT | = lt_currencyamount | |
PURCHASEORDER | = lt_purchaseorder | |
PURCHASEAMOUNT | = lt_purchaseamount | |
CRITERIA | = lt_criteria | |
VALUEFIELD | = lt_valuefield | |
EXTENSION1 | = lt_extension1 | |
RECEIVERS | = lt_receivers | |
COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
EXCEPTIONS | ||
ERROR_CREATING_IDOCS = 1 | ||
. " ALE_ACC_GOODS_MOVEMENT_POST |
ABAP code using 7.40 inline data declarations to call FM ALE_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 SERIAL INTO @DATA(ld_obj_type). | ||||
DATA(ld_obj_type) | = 'BUS6002'. | |||
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
DATA(ld_serial_id) | = '0'. | |||
Search for further information about these or an SAP related objects