SAP OIJ_NOM_BPD_PROCESS_SEND Function Module for Nomination Business Process Dialog send / output determination
OIJ_NOM_BPD_PROCESS_SEND is a standard oij nom bpd process send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Nomination Business Process Dialog send / output determination 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 bpd process send FM, simply by entering the name OIJ_NOM_BPD_PROCESS_SEND into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJ_NOM_COMM
Program Name: SAPLOIJ_NOM_COMM
Main Program: SAPLOIJ_NOM_COMM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJ_NOM_BPD_PROCESS_SEND 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_BPD_PROCESS_SEND'"Nomination Business Process Dialog send / output determination.
EXPORTING
IS_NOM_HEADER = "TSW Nomination Header Communication Structure
IS_NOM_ITEM = "TSW Nomination Item Communication Structure
IV_RTYPE = "OIL-TSW: Role type
* IV_SIMULATION = "no update - only check
IMPORTING
ET_RETURN = "Return parameter table
ES_OIJNOMCOMM = "Nomination Partner Communication
EXCEPTIONS
PROCESS_FAILED = 1 PROCESS_NOT_ALLOWED = 2 NO_SEND_REQUIRED = 3 ITEM_INCOMPLETE = 4
IMPORTING Parameters details for OIJ_NOM_BPD_PROCESS_SEND
IS_NOM_HEADER - TSW Nomination Header Communication Structure
Data type: ROIJNOMHIOOptional: No
Call by Reference: No ( called with pass by value option)
IS_NOM_ITEM - TSW Nomination Item Communication Structure
Data type: ROIJNOMIIOOptional: No
Call by Reference: No ( called with pass by value option)
IV_RTYPE - OIL-TSW: Role type
Data type: OIJ_RTYPEOptional: No
Call by Reference: No ( called with pass by value option)
IV_SIMULATION - no update - only check
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIJ_NOM_BPD_PROCESS_SEND
ET_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
ES_OIJNOMCOMM - Nomination Partner Communication
Data type: OIJNOMCOMMOptional: No
Call by Reference: Yes
EXCEPTIONS details
PROCESS_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROCESS_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: Yes
NO_SEND_REQUIRED -
Data type:Optional: No
Call by Reference: Yes
ITEM_INCOMPLETE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJ_NOM_BPD_PROCESS_SEND 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_return | TYPE BAPIRET2_T, " | |||
| lv_is_nom_header | TYPE ROIJNOMHIO, " | |||
| lv_process_failed | TYPE ROIJNOMHIO, " | |||
| lv_is_nom_item | TYPE ROIJNOMIIO, " | |||
| lv_es_oijnomcomm | TYPE OIJNOMCOMM, " | |||
| lv_process_not_allowed | TYPE OIJNOMCOMM, " | |||
| lv_iv_rtype | TYPE OIJ_RTYPE, " | |||
| lv_no_send_required | TYPE OIJ_RTYPE, " | |||
| lv_iv_simulation | TYPE BOOLEAN, " | |||
| lv_item_incomplete | TYPE BOOLEAN. " |
|   CALL FUNCTION 'OIJ_NOM_BPD_PROCESS_SEND' "Nomination Business Process Dialog send / output determination |
| EXPORTING | ||
| IS_NOM_HEADER | = lv_is_nom_header | |
| IS_NOM_ITEM | = lv_is_nom_item | |
| IV_RTYPE | = lv_iv_rtype | |
| IV_SIMULATION | = lv_iv_simulation | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| ES_OIJNOMCOMM | = lv_es_oijnomcomm | |
| EXCEPTIONS | ||
| PROCESS_FAILED = 1 | ||
| PROCESS_NOT_ALLOWED = 2 | ||
| NO_SEND_REQUIRED = 3 | ||
| ITEM_INCOMPLETE = 4 | ||
| . " OIJ_NOM_BPD_PROCESS_SEND | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_NOM_BPD_PROCESS_SEND
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