SAP J_3RSTRANSFEXPVAT_J3RSSEPVAT Function Module for Transfer Incoming VAT Linked to Export Invoice
J_3RSTRANSFEXPVAT_J3RSSEPVAT is a standard j 3rstransfexpvat j3rssepvat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transfer Incoming VAT Linked to Export Invoice 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 3rstransfexpvat j3rssepvat FM, simply by entering the name J_3RSTRANSFEXPVAT_J3RSSEPVAT into the relevant SAP transaction such as SE37 or SE38.
Function Group: J3RSSEPVAT
Program Name: SAPLJ3RSSEPVAT
Main Program: SAPLJ3RSSEPVAT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_3RSTRANSFEXPVAT_J3RSSEPVAT 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_3RSTRANSFEXPVAT_J3RSSEPVAT'"Transfer Incoming VAT Linked to Export Invoice.
EXPORTING
BLART = "Document Type
EVENT = "Secondary Event Type
PROD_RUN = "Indicator: Productive Run
* CLEAR = ' ' "
* VATDATE = "Tax Reporting Date
SPLITTING = "X-splitting is active in cc
* BUDAT = SY-DATUM "Posting Date in the Document
* BLDAT = SY-DATUM "Document Date in Document
DUE_TO_DATE = "Date to which paper originals should be received
BUKRS = "Company Code
BELNR = "Accounting Document Number
GJAHR = "Fiscal Year
BUZEI = "Number of Line Item Within Accounting Document
TRANS_FWBAS = "Part of Tax base amount in document currency
CHANGING
INC_INV = "Linked Incoming Invoices
IMPORTING Parameters details for J_3RSTRANSFEXPVAT_J3RSSEPVAT
BLART - Document Type
Data type: BLARTOptional: No
Call by Reference: Yes
EVENT - Secondary Event Type
Data type: J_3RNKSEVENTOptional: No
Call by Reference: Yes
PROD_RUN - Indicator: Productive Run
Data type: J_3RSPRODRUNOptional: No
Call by Reference: Yes
CLEAR -
Data type:Default: SPACE
Optional: No
Call by Reference: Yes
VATDATE - Tax Reporting Date
Data type: VATDATEOptional: Yes
Call by Reference: Yes
SPLITTING - X-splitting is active in cc
Data type: CHAR1Optional: No
Call by Reference: Yes
BUDAT - Posting Date in the Document
Data type: BUDATDefault: SY-DATUM
Optional: No
Call by Reference: Yes
BLDAT - Document Date in Document
Data type: BLDATDefault: SY-DATUM
Optional: No
Call by Reference: Yes
DUE_TO_DATE - Date to which paper originals should be received
Data type: J_3RSDUETODATEOptional: No
Call by Reference: Yes
BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
BELNR - Accounting Document Number
Data type: BELNR_DOptional: No
Call by Reference: Yes
GJAHR - Fiscal Year
Data type: GJAHROptional: No
Call by Reference: Yes
BUZEI - Number of Line Item Within Accounting Document
Data type: BUZEIOptional: No
Call by Reference: Yes
TRANS_FWBAS - Part of Tax base amount in document currency
Data type: J_3RSFWBASPARTOptional: No
Call by Reference: Yes
CHANGING Parameters details for J_3RSTRANSFEXPVAT_J3RSSEPVAT
INC_INV - Linked Incoming Invoices
Data type: J_3RS_INVLNKOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_3RSTRANSFEXPVAT_J3RSSEPVAT 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_blart | TYPE BLART, " | |||
| lv_inc_inv | TYPE J_3RS_INVLNK, " | |||
| lv_event | TYPE J_3RNKSEVENT, " | |||
| lv_prod_run | TYPE J_3RSPRODRUN, " | |||
| lv_clear | TYPE J_3RSPRODRUN, " SPACE | |||
| lv_vatdate | TYPE VATDATE, " | |||
| lv_splitting | TYPE CHAR1, " | |||
| lv_budat | TYPE BUDAT, " SY-DATUM | |||
| lv_bldat | TYPE BLDAT, " SY-DATUM | |||
| lv_due_to_date | TYPE J_3RSDUETODATE, " | |||
| lv_bukrs | TYPE BUKRS, " | |||
| lv_belnr | TYPE BELNR_D, " | |||
| lv_gjahr | TYPE GJAHR, " | |||
| lv_buzei | TYPE BUZEI, " | |||
| lv_trans_fwbas | TYPE J_3RSFWBASPART. " |
|   CALL FUNCTION 'J_3RSTRANSFEXPVAT_J3RSSEPVAT' "Transfer Incoming VAT Linked to Export Invoice |
| EXPORTING | ||
| BLART | = lv_blart | |
| EVENT | = lv_event | |
| PROD_RUN | = lv_prod_run | |
| CLEAR | = lv_clear | |
| VATDATE | = lv_vatdate | |
| SPLITTING | = lv_splitting | |
| BUDAT | = lv_budat | |
| BLDAT | = lv_bldat | |
| DUE_TO_DATE | = lv_due_to_date | |
| BUKRS | = lv_bukrs | |
| BELNR | = lv_belnr | |
| GJAHR | = lv_gjahr | |
| BUZEI | = lv_buzei | |
| TRANS_FWBAS | = lv_trans_fwbas | |
| CHANGING | ||
| INC_INV | = lv_inc_inv | |
| . " J_3RSTRANSFEXPVAT_J3RSSEPVAT | ||
ABAP code using 7.40 inline data declarations to call FM J_3RSTRANSFEXPVAT_J3RSSEPVAT
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.| DATA(ld_clear) | = ' '. | |||
| DATA(ld_budat) | = SY-DATUM. | |||
| DATA(ld_bldat) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects