SAP CHECK_SPEC_PARTNER Function Module for Spec check using partner profile EDP13
CHECK_SPEC_PARTNER is a standard check spec partner SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Spec check using partner profile EDP13 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 check spec partner FM, simply by entering the name CHECK_SPEC_PARTNER into the relevant SAP transaction such as SE37 or SE38.
Function Group: ADSPC40
Program Name: SAPLADSPC40
Main Program: SAPLADSPC40
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHECK_SPEC_PARTNER 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 'CHECK_SPEC_PARTNER'"Spec check using partner profile EDP13.
EXPORTING
RCVPRN = "Partner number of receiver
MESTYP = "Message Type
IMPORTING
SPEC_FLAG = "M=AECMA | A=ATA | N=No spec partner
EXCEPTIONS
NOT_UNIQUE = 1 NO_PARTNER_PROFILE = 2
IMPORTING Parameters details for CHECK_SPEC_PARTNER
RCVPRN - Partner number of receiver
Data type: EDP13-RCVPRNOptional: No
Call by Reference: Yes
MESTYP - Message Type
Data type: EDP13-MESTYPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CHECK_SPEC_PARTNER
SPEC_FLAG - M=AECMA | A=ATA | N=No spec partner
Data type: COptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_UNIQUE - Select using RCVPRN and MESTYP is not unique
Data type:Optional: No
Call by Reference: Yes
NO_PARTNER_PROFILE - Select using EDP13 was not successful
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CHECK_SPEC_PARTNER 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_rcvprn | TYPE EDP13-RCVPRN, " | |||
| lv_spec_flag | TYPE C, " | |||
| lv_not_unique | TYPE C, " | |||
| lv_mestyp | TYPE EDP13-MESTYP, " | |||
| lv_no_partner_profile | TYPE EDP13. " |
|   CALL FUNCTION 'CHECK_SPEC_PARTNER' "Spec check using partner profile EDP13 |
| EXPORTING | ||
| RCVPRN | = lv_rcvprn | |
| MESTYP | = lv_mestyp | |
| IMPORTING | ||
| SPEC_FLAG | = lv_spec_flag | |
| EXCEPTIONS | ||
| NOT_UNIQUE = 1 | ||
| NO_PARTNER_PROFILE = 2 | ||
| . " CHECK_SPEC_PARTNER | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_SPEC_PARTNER
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 RCVPRN FROM EDP13 INTO @DATA(ld_rcvprn). | ||||
| "SELECT single MESTYP FROM EDP13 INTO @DATA(ld_mestyp). | ||||
Search for further information about these or an SAP related objects