SAP J_1IEXGM_CHECK_CENVAT_UTIL Function Module for prepares all internal tables after save was requested









J_1IEXGM_CHECK_CENVAT_UTIL is a standard j 1iexgm check cenvat util SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for prepares all internal tables after save was requested 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 j 1iexgm check cenvat util FM, simply by entering the name J_1IEXGM_CHECK_CENVAT_UTIL into the relevant SAP transaction such as SE37 or SE38.

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



Function J_1IEXGM_CHECK_CENVAT_UTIL 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 'J_1IEXGM_CHECK_CENVAT_UTIL'"prepares all internal tables after save was requested
EXPORTING
IS_EXHEAD = "Incoming Excise Invoice: CIN40A : Header Data

IMPORTING
RETURN = "Return Value, Return Value After ABAP Statements

CHANGING
* CS_BAPIRET2 = "Return Parameter

TABLES
CT_ACCOUNT = "Structure for storing account no and balance
.



IMPORTING Parameters details for J_1IEXGM_CHECK_CENVAT_UTIL

IS_EXHEAD - Incoming Excise Invoice: CIN40A : Header Data

Data type: J_1IEXHEAD
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for J_1IEXGM_CHECK_CENVAT_UTIL

RETURN - Return Value, Return Value After ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

CHANGING Parameters details for J_1IEXGM_CHECK_CENVAT_UTIL

CS_BAPIRET2 - Return Parameter

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

TABLES Parameters details for J_1IEXGM_CHECK_CENVAT_UTIL

CT_ACCOUNT - Structure for storing account no and balance

Data type: J_1IACCBAL
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for J_1IEXGM_CHECK_CENVAT_UTIL 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_return  TYPE SY-SUBRC, "   
lv_is_exhead  TYPE J_1IEXHEAD, "   
lt_ct_account  TYPE STANDARD TABLE OF J_1IACCBAL, "   
lv_cs_bapiret2  TYPE BAPIRET2. "   

  CALL FUNCTION 'J_1IEXGM_CHECK_CENVAT_UTIL'  "prepares all internal tables after save was requested
    EXPORTING
         IS_EXHEAD = lv_is_exhead
    IMPORTING
         RETURN = lv_return
    CHANGING
         CS_BAPIRET2 = lv_cs_bapiret2
    TABLES
         CT_ACCOUNT = lt_ct_account
. " J_1IEXGM_CHECK_CENVAT_UTIL




ABAP code using 7.40 inline data declarations to call FM J_1IEXGM_CHECK_CENVAT_UTIL

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 SUBRC FROM SY INTO @DATA(ld_return).
 
 
 
 


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!