SAP RP_PNP_MATCHCODE Function Module for
RP_PNP_MATCHCODE is a standard rp pnp matchcode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rp pnp matchcode FM, simply by entering the name RP_PNP_MATCHCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPPN
Program Name: SAPLRPPN
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RP_PNP_MATCHCODE 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 'RP_PNP_MATCHCODE'".
EXPORTING
* MATCHCODE_OBJECT = 'PREM' "
CHANGING
MATCHCODE_ID = "
TABLES
SELECTIONS = "
EXCEPTIONS
INTERNAL_ERROR = 1
IMPORTING Parameters details for RP_PNP_MATCHCODE
MATCHCODE_OBJECT -
Data type: DD23L-MCONAMEDefault: 'PREM'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for RP_PNP_MATCHCODE
MATCHCODE_ID -
Data type: DD23L-MCIDOptional: No
Call by Reference: Yes
TABLES Parameters details for RP_PNP_MATCHCODE
SELECTIONS -
Data type: DDSHSELOPTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RP_PNP_MATCHCODE 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_selections | TYPE STANDARD TABLE OF DDSHSELOPT, " | |||
| lv_matchcode_id | TYPE DD23L-MCID, " | |||
| lv_internal_error | TYPE DD23L, " | |||
| lv_matchcode_object | TYPE DD23L-MCONAME. " 'PREM' |
|   CALL FUNCTION 'RP_PNP_MATCHCODE' " |
| EXPORTING | ||
| MATCHCODE_OBJECT | = lv_matchcode_object | |
| CHANGING | ||
| MATCHCODE_ID | = lv_matchcode_id | |
| TABLES | ||
| SELECTIONS | = lt_selections | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| . " RP_PNP_MATCHCODE | ||
ABAP code using 7.40 inline data declarations to call FM RP_PNP_MATCHCODE
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 MCID FROM DD23L INTO @DATA(ld_matchcode_id). | ||||
| "SELECT single MCONAME FROM DD23L INTO @DATA(ld_matchcode_object). | ||||
| DATA(ld_matchcode_object) | = 'PREM'. | |||
Search for further information about these or an SAP related objects