SAP GJVA_SL_TO_FI_POST Function Module for Convert SL postings to FI postings
GJVA_SL_TO_FI_POST is a standard gjva sl to fi post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert SL postings to FI postings 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 gjva sl to fi post FM, simply by entering the name GJVA_SL_TO_FI_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJVA_FAGL_SFWS
Program Name: SAPLGJVA_FAGL_SFWS
Main Program: SAPLGJVA_FAGL_SFWS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function GJVA_SL_TO_FI_POST 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 'GJVA_SL_TO_FI_POST'"Convert SL postings to FI postings.
EXPORTING
P_BUKRS = "Company Code
* P_POPER = "Posting period
* P_BLDAT = "Document Date in Document
P_BUDAT = "Posting Date in the Document
* P_GLVOR = "Business Transaction
P_TESTFLG = "JV flag: Testmode
* P_EQGNEW = "Equity group new
* P_PMODE = "Processing mode - 1=reverse or suspense,2=rebook ,3=reverse+rebook,4=unsuspens
IMPORTING
I_DOCNR = "Accounting Document Number
I_BLDAT = "Document Date in Document
TABLES
* I_JVTO1 = "JV Summary Table with Objects
* I_JVSO1 = "JV LI Table with Objects for JVTO1
* I_GLU1 = "G/L user table 1
* I_JVAH = "Joint Venture Header
* I_JVAP = "Joint venture item
* T_T8J_JVEC = "JVA equity change document relationship
EXCEPTIONS
ERROR_OCCURED = 1
IMPORTING Parameters details for GJVA_SL_TO_FI_POST
P_BUKRS - Company Code
Data type: T8JZ-BUKRSOptional: No
Call by Reference: Yes
P_POPER - Posting period
Data type: MONATOptional: Yes
Call by Reference: Yes
P_BLDAT - Document Date in Document
Data type: BLDATOptional: Yes
Call by Reference: Yes
P_BUDAT - Posting Date in the Document
Data type: BUDATOptional: No
Call by Reference: Yes
P_GLVOR - Business Transaction
Data type: GLVOROptional: Yes
Call by Reference: Yes
P_TESTFLG - JV flag: Testmode
Data type: JV_CB_TESTOptional: No
Call by Reference: Yes
P_EQGNEW - Equity group new
Data type: JV_EGROUP_NEWOptional: Yes
Call by Reference: Yes
P_PMODE - Processing mode - 1=reverse or suspense,2=rebook ,3=reverse+rebook,4=unsuspens
Data type: COptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for GJVA_SL_TO_FI_POST
I_DOCNR - Accounting Document Number
Data type: BELNR_DOptional: No
Call by Reference: Yes
I_BLDAT - Document Date in Document
Data type: BLDATOptional: No
Call by Reference: Yes
TABLES Parameters details for GJVA_SL_TO_FI_POST
I_JVTO1 - JV Summary Table with Objects
Data type: JVTO1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_JVSO1 - JV LI Table with Objects for JVTO1
Data type: JVSO1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_GLU1 - G/L user table 1
Data type: GLU1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_JVAH - Joint Venture Header
Data type: JVAHOptional: Yes
Call by Reference: No ( called with pass by value option)
I_JVAP - Joint venture item
Data type: JVAPOptional: Yes
Call by Reference: No ( called with pass by value option)
T_T8J_JVEC - JVA equity change document relationship
Data type: T8J_JVECOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURED - error occured
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GJVA_SL_TO_FI_POST 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_i_docnr | TYPE BELNR_D, " | |||
lt_i_jvto1 | TYPE STANDARD TABLE OF JVTO1, " | |||
lv_p_bukrs | TYPE T8JZ-BUKRS, " | |||
lv_error_occured | TYPE T8JZ, " | |||
lv_i_bldat | TYPE BLDAT, " | |||
lt_i_jvso1 | TYPE STANDARD TABLE OF JVSO1, " | |||
lv_p_poper | TYPE MONAT, " | |||
lt_i_glu1 | TYPE STANDARD TABLE OF GLU1, " | |||
lv_p_bldat | TYPE BLDAT, " | |||
lt_i_jvah | TYPE STANDARD TABLE OF JVAH, " | |||
lv_p_budat | TYPE BUDAT, " | |||
lt_i_jvap | TYPE STANDARD TABLE OF JVAP, " | |||
lv_p_glvor | TYPE GLVOR, " | |||
lv_p_testflg | TYPE JV_CB_TEST, " | |||
lt_t_t8j_jvec | TYPE STANDARD TABLE OF T8J_JVEC, " | |||
lv_p_eqgnew | TYPE JV_EGROUP_NEW, " | |||
lv_p_pmode | TYPE C. " |
  CALL FUNCTION 'GJVA_SL_TO_FI_POST' "Convert SL postings to FI postings |
EXPORTING | ||
P_BUKRS | = lv_p_bukrs | |
P_POPER | = lv_p_poper | |
P_BLDAT | = lv_p_bldat | |
P_BUDAT | = lv_p_budat | |
P_GLVOR | = lv_p_glvor | |
P_TESTFLG | = lv_p_testflg | |
P_EQGNEW | = lv_p_eqgnew | |
P_PMODE | = lv_p_pmode | |
IMPORTING | ||
I_DOCNR | = lv_i_docnr | |
I_BLDAT | = lv_i_bldat | |
TABLES | ||
I_JVTO1 | = lt_i_jvto1 | |
I_JVSO1 | = lt_i_jvso1 | |
I_GLU1 | = lt_i_glu1 | |
I_JVAH | = lt_i_jvah | |
I_JVAP | = lt_i_jvap | |
T_T8J_JVEC | = lt_t_t8j_jvec | |
EXCEPTIONS | ||
ERROR_OCCURED = 1 | ||
. " GJVA_SL_TO_FI_POST |
ABAP code using 7.40 inline data declarations to call FM GJVA_SL_TO_FI_POST
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 BUKRS FROM T8JZ INTO @DATA(ld_p_bukrs). | ||||
Search for further information about these or an SAP related objects