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

Function OIJ_NOM_GENERATE_LOC_DEMAND 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_GENERATE_LOC_DEMAND'"Generate Nomination for location demand data - internal.
EXPORTING
* IV_USAGEIND = "OIL-TSW: Usage Indicator
* IV_EXTEND_EXISTING = 'X' "boolean variable (X=true, -=false, space=unknown)
IMPORTING
ET_NOM_HEADER = "Nomination Header Communcation Table Type
ET_NOM_ITEM = "Nomination Item Communication
ET_RETURN = "Return parameter table
TABLES
IT_DEMAND = "Location Demand structure
EXCEPTIONS
OIJLOCMAT_SINGLE_READ = 1
IMPORTING Parameters details for OIJ_NOM_GENERATE_LOC_DEMAND
IV_USAGEIND - OIL-TSW: Usage Indicator
Data type: OIJ_USAGEINDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_EXTEND_EXISTING - boolean variable (X=true, -=false, space=unknown)
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIJ_NOM_GENERATE_LOC_DEMAND
ET_NOM_HEADER - Nomination Header Communcation Table Type
Data type: ROIJNOMHIO_TOptional: No
Call by Reference: Yes
ET_NOM_ITEM - Nomination Item Communication
Data type: ROIJNOMIIO_TOptional: No
Call by Reference: Yes
ET_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
TABLES Parameters details for OIJ_NOM_GENERATE_LOC_DEMAND
IT_DEMAND - Location Demand structure
Data type: ROIJ_NOM_LOC_DEMANDOptional: No
Call by Reference: Yes
EXCEPTIONS details
OIJLOCMAT_SINGLE_READ - Error in module OIJLOCMAT_SINGLE_READ
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJ_NOM_GENERATE_LOC_DEMAND 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_it_demand | TYPE STANDARD TABLE OF ROIJ_NOM_LOC_DEMAND, " | |||
| lv_iv_usageind | TYPE OIJ_USAGEIND, " | |||
| lv_et_nom_header | TYPE ROIJNOMHIO_T, " | |||
| lv_oijlocmat_single_read | TYPE ROIJNOMHIO_T, " | |||
| lv_et_nom_item | TYPE ROIJNOMIIO_T, " | |||
| lv_iv_extend_existing | TYPE BOOLEAN, " 'X' | |||
| lv_et_return | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'OIJ_NOM_GENERATE_LOC_DEMAND' "Generate Nomination for location demand data - internal |
| EXPORTING | ||
| IV_USAGEIND | = lv_iv_usageind | |
| IV_EXTEND_EXISTING | = lv_iv_extend_existing | |
| IMPORTING | ||
| ET_NOM_HEADER | = lv_et_nom_header | |
| ET_NOM_ITEM | = lv_et_nom_item | |
| ET_RETURN | = lv_et_return | |
| TABLES | ||
| IT_DEMAND | = lt_it_demand | |
| EXCEPTIONS | ||
| OIJLOCMAT_SINGLE_READ = 1 | ||
| . " OIJ_NOM_GENERATE_LOC_DEMAND | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_NOM_GENERATE_LOC_DEMAND
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_iv_extend_existing) | = 'X'. | |||
Search for further information about these or an SAP related objects