SAP ALE_MATPHYSINV_POSTDIFF Function Module for NOTRANSL: BAPI -> IDoc: ALE_MATPHYSINV_POSTDIFF

Search SAP Function Modules

ALE_MATPHYSINV_POSTDIFF is a standard ale matphysinv postdiff SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: BAPI -> IDoc: ALE_MATPHYSINV_POSTDIFF 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 ale matphysinv postdiff FM, simply by entering the name ALE_MATPHYSINV_POSTDIFF into the relevant SAP transaction such as SE37 or SE38.

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

Function ALE_MATPHYSINV_POSTDIFF 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_MATPHYSINV_POSTDIFF'"NOTRANSL: BAPI -> IDoc: ALE_MATPHYSINV_POSTDIFF
  EXPORTING
   PHYSINVENTORY =  "Physical Inventory Document
   FISCALYEAR =  "Fiscal Year
*  PSTNGDATE =  "Posting Date in the Document
*  THRESHOLDVALUE =  "Currency amount in BAPI interfaces
*  OBJ_TYPE = 'BUS2028' "Object Type
*  SERIAL_ID = '0' "ALE channel number

TABLES
*  ITEMS =  "Items of Physical Inventory Document That Are To Be Posted
   RECEIVERS =  "Transfer structure for logical systems
*  COMMUNICATION_DOCUMENTS =  "Structure for Object ID
*  APPLICATION_OBJECTS =  "Structure for Object ID

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1 

.

IMPORTING Parameters details for ALE_MATPHYSINV_POSTDIFF

PHYSINVENTORY - Physical Inventory Document

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

FISCALYEAR - Fiscal Year

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

PSTNGDATE - Posting Date in the Document

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

THRESHOLDVALUE - Currency amount in BAPI interfaces

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

OBJ_TYPE - Object Type

Data type: SERIAL-OBJ_TYPE
Default: 'BUS2028'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID - ALE channel number

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_MATPHYSINV_POSTDIFF

ITEMS - Items of Physical Inventory Document That Are To Be Posted

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

RECEIVERS - Transfer structure for logical systems

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

COMMUNICATION_DOCUMENTS - Structure for Object ID

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

APPLICATION_OBJECTS - Structure for Object ID

Data type: SWOTOBJID
Optional: 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_MATPHYSINV_POSTDIFF 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.

ABAP code using 7.40 inline data declarations to call FM ALE_MATPHYSINV_POSTDIFF

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