SAP J_1GCHECK_ACCOUNT Function Module for *!!! OBSOLETE !!!* Use J_1GGET_TYPE instead
J_1GCHECK_ACCOUNT is a standard j 1gcheck account SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for *!!! OBSOLETE !!!* Use J_1GGET_TYPE instead 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 1gcheck account FM, simply by entering the name J_1GCHECK_ACCOUNT into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1GFI_COA
Program Name: SAPLJ1GFI_COA
Main Program: SAPLJ1GFI_COA
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1GCHECK_ACCOUNT 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_1GCHECK_ACCOUNT'"*!!! OBSOLETE !!!* Use J_1GGET_TYPE instead.
EXPORTING
I_ACCOUNT = "GL Account
IMPORTING
E_TYPE = "T: Taxeos, G: G/L account, A: A/L account
TABLES
T_STR = "Chart of accounts structure
EXCEPTIONS
WRONG_INPUT = 1
IMPORTING Parameters details for J_1GCHECK_ACCOUNT
I_ACCOUNT - GL Account
Data type: SKA1-SAKNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_1GCHECK_ACCOUNT
E_TYPE - T: Taxeos, G: G/L account, A: A/L account
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for J_1GCHECK_ACCOUNT
T_STR - Chart of accounts structure
Data type: J_1GGSOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1GCHECK_ACCOUNT 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_t_str | TYPE STANDARD TABLE OF J_1GGS, " | |||
| lv_e_type | TYPE J_1GGS, " | |||
| lv_i_account | TYPE SKA1-SAKNR, " | |||
| lv_wrong_input | TYPE SKA1. " |
|   CALL FUNCTION 'J_1GCHECK_ACCOUNT' "*!!! OBSOLETE !!!* Use J_1GGET_TYPE instead |
| EXPORTING | ||
| I_ACCOUNT | = lv_i_account | |
| IMPORTING | ||
| E_TYPE | = lv_e_type | |
| TABLES | ||
| T_STR | = lt_t_str | |
| EXCEPTIONS | ||
| WRONG_INPUT = 1 | ||
| . " J_1GCHECK_ACCOUNT | ||
ABAP code using 7.40 inline data declarations to call FM J_1GCHECK_ACCOUNT
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 SAKNR FROM SKA1 INTO @DATA(ld_i_account). | ||||
Search for further information about these or an SAP related objects