SAP Function Modules
ALE_ACC_GOODS_MOVEMENT_POST SAP Function module
ALE_ACC_GOODS_MOVEMENT_POST is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name ALE_ACC_GOODS_MOVEMENT_POST into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
ACC4
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM ALE_ACC_GOODS_MOVEMENT_POST - ALE ACC GOODS MOVEMENT POST
CALL FUNCTION 'ALE_ACC_GOODS_MOVEMENT_POST' "
EXPORTING
documentheader = " bapiache02 Document header
* obj_type = 'BUS6002' " serial-obj_type Reference Transaction
* serial_id = '0' " serial-chnum
TABLES
accountgl = " bapiacgl02 G/L Account Line Items
currencyamount = " bapiaccr01 Line item currency fields
* purchaseorder = " bapiacpo00 Purchase Order Line Items
* purchaseamount = " bapiaccrpo Purchase Order Currency Fields
* criteria = " bapiackecr CO-PA Characteristics
* valuefield = " bapiackeva CO-PA value components
* extension1 = " bapiextc Table for Customer Enhancement
receivers = " bdi_logsys
* communication_documents = " swotobjid
* application_objects = " swotobjid
EXCEPTIONS
ERROR_CREATING_IDOCS = 1 "
. " ALE_ACC_GOODS_MOVEMENT_POST
ABAP code example for Function Module ALE_ACC_GOODS_MOVEMENT_POST
The ABAP code below is a full code listing to execute function module ALE_ACC_GOODS_MOVEMENT_POST including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| it_accountgl | TYPE STANDARD TABLE OF BAPIACGL02,"TABLES PARAM |
| wa_accountgl | LIKE LINE OF it_accountgl , |
| it_currencyamount | TYPE STANDARD TABLE OF BAPIACCR01,"TABLES PARAM |
| wa_currencyamount | LIKE LINE OF it_currencyamount , |
| it_purchaseorder | TYPE STANDARD TABLE OF BAPIACPO00,"TABLES PARAM |
| wa_purchaseorder | LIKE LINE OF it_purchaseorder , |
| it_purchaseamount | TYPE STANDARD TABLE OF BAPIACCRPO,"TABLES PARAM |
| wa_purchaseamount | LIKE LINE OF it_purchaseamount , |
| it_criteria | TYPE STANDARD TABLE OF BAPIACKECR,"TABLES PARAM |
| wa_criteria | LIKE LINE OF it_criteria , |
| it_valuefield | TYPE STANDARD TABLE OF BAPIACKEVA,"TABLES PARAM |
| wa_valuefield | LIKE LINE OF it_valuefield , |
| it_extension1 | TYPE STANDARD TABLE OF BAPIEXTC,"TABLES PARAM |
| wa_extension1 | LIKE LINE OF it_extension1 , |
| it_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS,"TABLES PARAM |
| wa_receivers | LIKE LINE OF it_receivers , |
| it_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM |
| wa_communication_documents | LIKE LINE OF it_communication_documents , |
| it_application_objects | TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM |
| wa_application_objects | LIKE LINE OF it_application_objects . |
DATA(ld_documentheader) = 'Check type of data required'.
DATA(ld_obj_type) = some text here
DATA(ld_serial_id) = Check type of data required
"populate fields of struture and append to itab
append wa_accountgl to it_accountgl.
"populate fields of struture and append to itab
append wa_currencyamount to it_currencyamount.
"populate fields of struture and append to itab
append wa_purchaseorder to it_purchaseorder.
"populate fields of struture and append to itab
append wa_purchaseamount to it_purchaseamount.
"populate fields of struture and append to itab
append wa_criteria to it_criteria.
"populate fields of struture and append to itab
append wa_valuefield to it_valuefield.
"populate fields of struture and append to itab
append wa_extension1 to it_extension1.
"populate fields of struture and append to itab
append wa_receivers to it_receivers.
"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.
"populate fields of struture and append to itab
append wa_application_objects to it_application_objects. . CALL FUNCTION 'ALE_ACC_GOODS_MOVEMENT_POST' EXPORTING documentheader = ld_documentheader * obj_type = ld_obj_type * serial_id = ld_serial_id TABLES accountgl = it_accountgl currencyamount = it_currencyamount * purchaseorder = it_purchaseorder * purchaseamount = it_purchaseamount * criteria = it_criteria * valuefield = it_valuefield * extension1 = it_extension1 receivers = it_receivers * communication_documents = it_communication_documents * application_objects = it_application_objects EXCEPTIONS ERROR_CREATING_IDOCS = 1 . " ALE_ACC_GOODS_MOVEMENT_POST
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_documentheader | TYPE BAPIACHE02 , |
| it_accountgl | TYPE STANDARD TABLE OF BAPIACGL02 , |
| wa_accountgl | LIKE LINE OF it_accountgl, |
| ld_obj_type | TYPE SERIAL-OBJ_TYPE , |
| it_currencyamount | TYPE STANDARD TABLE OF BAPIACCR01 , |
| wa_currencyamount | LIKE LINE OF it_currencyamount, |
| ld_serial_id | TYPE SERIAL-CHNUM , |
| it_purchaseorder | TYPE STANDARD TABLE OF BAPIACPO00 , |
| wa_purchaseorder | LIKE LINE OF it_purchaseorder, |
| it_purchaseamount | TYPE STANDARD TABLE OF BAPIACCRPO , |
| wa_purchaseamount | LIKE LINE OF it_purchaseamount, |
| it_criteria | TYPE STANDARD TABLE OF BAPIACKECR , |
| wa_criteria | LIKE LINE OF it_criteria, |
| it_valuefield | TYPE STANDARD TABLE OF BAPIACKEVA , |
| wa_valuefield | LIKE LINE OF it_valuefield, |
| it_extension1 | TYPE STANDARD TABLE OF BAPIEXTC , |
| wa_extension1 | LIKE LINE OF it_extension1, |
| it_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS , |
| wa_receivers | LIKE LINE OF it_receivers, |
| it_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID , |
| wa_communication_documents | LIKE LINE OF it_communication_documents, |
| it_application_objects | TYPE STANDARD TABLE OF SWOTOBJID , |
| wa_application_objects | LIKE LINE OF it_application_objects. |
ld_documentheader = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_accountgl to it_accountgl.
ld_obj_type = some text here
"populate fields of struture and append to itab
append wa_currencyamount to it_currencyamount.
ld_serial_id = Check type of data required
"populate fields of struture and append to itab
append wa_purchaseorder to it_purchaseorder.
"populate fields of struture and append to itab
append wa_purchaseamount to it_purchaseamount.
"populate fields of struture and append to itab
append wa_criteria to it_criteria.
"populate fields of struture and append to itab
append wa_valuefield to it_valuefield.
"populate fields of struture and append to itab
append wa_extension1 to it_extension1.
"populate fields of struture and append to itab
append wa_receivers to it_receivers.
"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.
"populate fields of struture and append to itab
append wa_application_objects to it_application_objects.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ALE_ACC_GOODS_MOVEMENT_POST or its description.