SAP J_1I4_COPY_MIGO_DATA Function Module for Export excise invoice details to j1i4 global variables
J_1I4_COPY_MIGO_DATA is a standard j 1i4 copy migo data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export excise invoice details to j1i4 global variables 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 1i4 copy migo data FM, simply by entering the name J_1I4_COPY_MIGO_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1I4
Program Name: SAPLJ1I4
Main Program: SAPLJ1I4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1I4_COPY_MIGO_DATA 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_1I4_COPY_MIGO_DATA'"Export excise invoice details to j1i4 global variables.
EXPORTING
EXC_INV = "Excise Document Number
EXCISE_YEAR = "Excise Year
LIFNR = "Account number of vendor or creditor
IMPORTING Parameters details for J_1I4_COPY_MIGO_DATA
EXC_INV - Excise Document Number
Data type: J_1IEXCHDR-EXNUMOptional: No
Call by Reference: Yes
EXCISE_YEAR - Excise Year
Data type: J_1IEXCHDR-EXYEAROptional: No
Call by Reference: Yes
LIFNR - Account number of vendor or creditor
Data type: J_1IEXCHDR-LIFNROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1I4_COPY_MIGO_DATA 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_exc_inv | TYPE J_1IEXCHDR-EXNUM, " | |||
| lv_excise_year | TYPE J_1IEXCHDR-EXYEAR, " | |||
| lv_lifnr | TYPE J_1IEXCHDR-LIFNR. " |
|   CALL FUNCTION 'J_1I4_COPY_MIGO_DATA' "Export excise invoice details to j1i4 global variables |
| EXPORTING | ||
| EXC_INV | = lv_exc_inv | |
| EXCISE_YEAR | = lv_excise_year | |
| LIFNR | = lv_lifnr | |
| . " J_1I4_COPY_MIGO_DATA | ||
ABAP code using 7.40 inline data declarations to call FM J_1I4_COPY_MIGO_DATA
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 EXNUM FROM J_1IEXCHDR INTO @DATA(ld_exc_inv). | ||||
| "SELECT single EXYEAR FROM J_1IEXCHDR INTO @DATA(ld_excise_year). | ||||
| "SELECT single LIFNR FROM J_1IEXCHDR INTO @DATA(ld_lifnr). | ||||
Search for further information about these or an SAP related objects