SAP REQUIREMENT_REFERENCE_READ Function Module for NOTRANSL: Vorlagen einlesen
REQUIREMENT_REFERENCE_READ is a standard requirement reference read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Vorlagen einlesen 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 requirement reference read FM, simply by entering the name REQUIREMENT_REFERENCE_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: M60R
Program Name: SAPLM60R
Main Program: SAPLM60R
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REQUIREMENT_REFERENCE_READ 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 'REQUIREMENT_REFERENCE_READ'"NOTRANSL: Vorlagen einlesen.
EXPORTING
ERM60V = "
* PL_START = 00000000 "Start of Planning Period
* PL_ENDE = 99991231 "End of Planning Period
* EXPBPT = "
TCODE = "Transaction Code
* DIALOG_KZ = ' ' "
* SELECT_KZ = ' ' "
* OKCODE = ' ' "Function Code
* XRUNDEN = ' ' "
IMPORTING
KONFDA = "
TABLES
IREFRBPT = "
IREFRBET = "
* IREFXBET = "
IPROTO = "Log file
EXCEPTIONS
ABORT_DIALOG = 1 NO_REFERENCE = 2 E_MESSAGE = 3
IMPORTING Parameters details for REQUIREMENT_REFERENCE_READ
ERM60V -
Data type: RM60VOptional: No
Call by Reference: No ( called with pass by value option)
PL_START - Start of Planning Period
Data type: CM60A-DATVIDefault: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
PL_ENDE - End of Planning Period
Data type: CM60A-DATBIDefault: 99991231
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPBPT -
Data type: PBPTOptional: Yes
Call by Reference: No ( called with pass by value option)
TCODE - Transaction Code
Data type: T450P-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
DIALOG_KZ -
Data type: RM60V-DIALOGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SELECT_KZ -
Data type: RM60V-DIALOGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OKCODE - Function Code
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
XRUNDEN -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for REQUIREMENT_REFERENCE_READ
KONFDA -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for REQUIREMENT_REFERENCE_READ
IREFRBPT -
Data type: RBPTOptional: No
Call by Reference: No ( called with pass by value option)
IREFRBET -
Data type: RBETOptional: No
Call by Reference: No ( called with pass by value option)
IREFXBET -
Data type: PBETOptional: Yes
Call by Reference: No ( called with pass by value option)
IPROTO - Log file
Data type: PBMSGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ABORT_DIALOG - Dialog Cancelled
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_REFERENCE - No Reference Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_MESSAGE - Error Message Exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for REQUIREMENT_REFERENCE_READ 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_erm60v | TYPE RM60V, " | |||
| lv_konfda | TYPE C, " | |||
| lt_irefrbpt | TYPE STANDARD TABLE OF RBPT, " | |||
| lv_abort_dialog | TYPE RBPT, " | |||
| lt_irefrbet | TYPE STANDARD TABLE OF RBET, " | |||
| lv_pl_start | TYPE CM60A-DATVI, " 00000000 | |||
| lv_no_reference | TYPE CM60A, " | |||
| lv_pl_ende | TYPE CM60A-DATBI, " 99991231 | |||
| lt_irefxbet | TYPE STANDARD TABLE OF PBET, " | |||
| lv_e_message | TYPE PBET, " | |||
| lv_expbpt | TYPE PBPT, " | |||
| lt_iproto | TYPE STANDARD TABLE OF PBMSG, " | |||
| lv_tcode | TYPE T450P-TCODE, " | |||
| lv_dialog_kz | TYPE RM60V-DIALOG, " SPACE | |||
| lv_select_kz | TYPE RM60V-DIALOG, " SPACE | |||
| lv_okcode | TYPE C, " SPACE | |||
| lv_xrunden | TYPE C. " SPACE |
|   CALL FUNCTION 'REQUIREMENT_REFERENCE_READ' "NOTRANSL: Vorlagen einlesen |
| EXPORTING | ||
| ERM60V | = lv_erm60v | |
| PL_START | = lv_pl_start | |
| PL_ENDE | = lv_pl_ende | |
| EXPBPT | = lv_expbpt | |
| TCODE | = lv_tcode | |
| DIALOG_KZ | = lv_dialog_kz | |
| SELECT_KZ | = lv_select_kz | |
| OKCODE | = lv_okcode | |
| XRUNDEN | = lv_xrunden | |
| IMPORTING | ||
| KONFDA | = lv_konfda | |
| TABLES | ||
| IREFRBPT | = lt_irefrbpt | |
| IREFRBET | = lt_irefrbet | |
| IREFXBET | = lt_irefxbet | |
| IPROTO | = lt_iproto | |
| EXCEPTIONS | ||
| ABORT_DIALOG = 1 | ||
| NO_REFERENCE = 2 | ||
| E_MESSAGE = 3 | ||
| . " REQUIREMENT_REFERENCE_READ | ||
ABAP code using 7.40 inline data declarations to call FM REQUIREMENT_REFERENCE_READ
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 DATVI FROM CM60A INTO @DATA(ld_pl_start). | ||||
| DATA(ld_pl_start) | = 00000000. | |||
| "SELECT single DATBI FROM CM60A INTO @DATA(ld_pl_ende). | ||||
| DATA(ld_pl_ende) | = 99991231. | |||
| "SELECT single TCODE FROM T450P INTO @DATA(ld_tcode). | ||||
| "SELECT single DIALOG FROM RM60V INTO @DATA(ld_dialog_kz). | ||||
| DATA(ld_dialog_kz) | = ' '. | |||
| "SELECT single DIALOG FROM RM60V INTO @DATA(ld_select_kz). | ||||
| DATA(ld_select_kz) | = ' '. | |||
| DATA(ld_okcode) | = ' '. | |||
| DATA(ld_xrunden) | = ' '. | |||
Search for further information about these or an SAP related objects