SAP OIJ_NOM_DATA_GET Function Module for Gets temp. global nomination data
OIJ_NOM_DATA_GET is a standard oij nom data get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets temp. global nomination data 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 oij nom data get FM, simply by entering the name OIJ_NOM_DATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJ_TEMP_BUFFER
Program Name: SAPLOIJ_TEMP_BUFFER
Main Program: SAPLOIJ_TEMP_BUFFER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJ_NOM_DATA_GET 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 'OIJ_NOM_DATA_GET'"Gets temp. global nomination data.
IMPORTING
ET_NOM_HEADER = "Nomination Header Communcation Table Type
ET_NOM_REF = "Nomination Reference Documents IO Table Type
ET_NOM_PEGGING = "TSW: Table type - Pegging of scheduled movements
ET_NOM_ITEM = "Nomination Item Communication
ET_NOM_HEADER_TEXT = "TSW: table type to roij_txt
ET_NOM_ITEM_TEXT = "TSW: table type to roij_txt
ET_NOM_EVENTS = "Nomination Events Communication Table
ET_NOM_EVENTS_TEXT = "TSW: table type to roij_txt
ET_NOM_BALANCE = "Nomination Material Balance Table Type
ET_NOM_STAGES = "TSW (&TD) STages IO
ET_NOM_COMM = "Nomination Partner Communication Table Type
EXPORTING Parameters details for OIJ_NOM_DATA_GET
ET_NOM_HEADER - Nomination Header Communcation Table Type
Data type: ROIJNOMHIO_TOptional: No
Call by Reference: Yes
ET_NOM_REF - Nomination Reference Documents IO Table Type
Data type: ROIJNOMRIO_TOptional: No
Call by Reference: Yes
ET_NOM_PEGGING - TSW: Table type - Pegging of scheduled movements
Data type: ROIJ_PEG_TOptional: No
Call by Reference: Yes
ET_NOM_ITEM - Nomination Item Communication
Data type: ROIJNOMIIO_TOptional: No
Call by Reference: Yes
ET_NOM_HEADER_TEXT - TSW: table type to roij_txt
Data type: OIJ_TXTOptional: No
Call by Reference: Yes
ET_NOM_ITEM_TEXT - TSW: table type to roij_txt
Data type: OIJ_TXTOptional: No
Call by Reference: Yes
ET_NOM_EVENTS - Nomination Events Communication Table
Data type: ROIJNEIO_TOptional: No
Call by Reference: Yes
ET_NOM_EVENTS_TEXT - TSW: table type to roij_txt
Data type: OIJ_TXTOptional: No
Call by Reference: Yes
ET_NOM_BALANCE - Nomination Material Balance Table Type
Data type: OIJNOMM_TOptional: No
Call by Reference: Yes
ET_NOM_STAGES - TSW (&TD) STages IO
Data type: ROIJ_STAGESIO_TOptional: No
Call by Reference: Yes
ET_NOM_COMM - Nomination Partner Communication Table Type
Data type: OIJNOMCOMM_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJ_NOM_DATA_GET 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_et_nom_header | TYPE ROIJNOMHIO_T, " | |||
| lv_et_nom_ref | TYPE ROIJNOMRIO_T, " | |||
| lv_et_nom_pegging | TYPE ROIJ_PEG_T, " | |||
| lv_et_nom_item | TYPE ROIJNOMIIO_T, " | |||
| lv_et_nom_header_text | TYPE OIJ_TXT, " | |||
| lv_et_nom_item_text | TYPE OIJ_TXT, " | |||
| lv_et_nom_events | TYPE ROIJNEIO_T, " | |||
| lv_et_nom_events_text | TYPE OIJ_TXT, " | |||
| lv_et_nom_balance | TYPE OIJNOMM_T, " | |||
| lv_et_nom_stages | TYPE ROIJ_STAGESIO_T, " | |||
| lv_et_nom_comm | TYPE OIJNOMCOMM_T. " |
|   CALL FUNCTION 'OIJ_NOM_DATA_GET' "Gets temp. global nomination data |
| IMPORTING | ||
| ET_NOM_HEADER | = lv_et_nom_header | |
| ET_NOM_REF | = lv_et_nom_ref | |
| ET_NOM_PEGGING | = lv_et_nom_pegging | |
| ET_NOM_ITEM | = lv_et_nom_item | |
| ET_NOM_HEADER_TEXT | = lv_et_nom_header_text | |
| ET_NOM_ITEM_TEXT | = lv_et_nom_item_text | |
| ET_NOM_EVENTS | = lv_et_nom_events | |
| ET_NOM_EVENTS_TEXT | = lv_et_nom_events_text | |
| ET_NOM_BALANCE | = lv_et_nom_balance | |
| ET_NOM_STAGES | = lv_et_nom_stages | |
| ET_NOM_COMM | = lv_et_nom_comm | |
| . " OIJ_NOM_DATA_GET | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_NOM_DATA_GET
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.Search for further information about these or an SAP related objects