SAP BAPI_LIA_CREATE Function Module for BAPI for creating Logical Inventory Adjustment (LIA)

Search SAP Function Modules

BAPI_LIA_CREATE is a standard bapi lia create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI for creating Logical Inventory Adjustment (LIA) 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 lia create FM, simply by entering the name BAPI_LIA_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIA_LIA_BAPI
Program Name: SAPLOIA_LIA_BAPI
Main Program: SAPLOIA_LIA_BAPI
Appliation area:
Release date: 22-Oct-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_LIA_CREATE 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_LIA_CREATE'"BAPI for creating Logical Inventory Adjustment (LIA)
  EXPORTING
*  EXG_PTR =  "Exchange Partner
   LIA_DOC_TYPE =  "LIA document type
*  DOC_DATE = SY-DATUM "Document date in document
*  PSTNG_DATE = SY-DATUM "Posting date in the document

 IMPORTING
   LIA_KEY =  "LIA header data for BAPI

TABLES
*  RETURN =  "Return parameter
*  NEGPAYMENT =  "Negotiated payments for BAPI
*  BALADJUSTMENT =  "Balance adjustments for BAPI
*  EXTENSIONIN =  "Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
*  EXTENSIONOUT =  "Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT

.

IMPORTING Parameters details for BAPI_LIA_CREATE

EXG_PTR - Exchange Partner

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

LIA_DOC_TYPE - LIA document type

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

DOC_DATE - Document date in document

Data type: BAPI_OIA_LIA_HEADER-DOC_DATE
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

PSTNG_DATE - Posting date in the document

Data type: BAPI_OIA_LIA_HEADER-PSTNG_DATE
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_LIA_CREATE

LIA_KEY - LIA header data for BAPI

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

TABLES Parameters details for BAPI_LIA_CREATE

RETURN - Return parameter

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

NEGPAYMENT - Negotiated payments for BAPI

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

BALADJUSTMENT - Balance adjustments for BAPI

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

EXTENSIONIN - Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT

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

EXTENSIONOUT - Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT

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

Copy and paste ABAP code example for BAPI_LIA_CREATE 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 BAPI_LIA_CREATE

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