SAP DD_INT_FIELDMATCH_PROPOSAL Function Module for DD: Create a proposal for matching fields
DD_INT_FIELDMATCH_PROPOSAL is a standard dd int fieldmatch proposal SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DD: Create a proposal for matching fields 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 dd int fieldmatch proposal FM, simply by entering the name DD_INT_FIELDMATCH_PROPOSAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SINT
Program Name: SAPLSINT
Main Program: SAPLSINT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_INT_FIELDMATCH_PROPOSAL 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 'DD_INT_FIELDMATCH_PROPOSAL'"DD: Create a proposal for matching fields.
EXPORTING
* DOUBLEMIN = '10' "
* FORBIDDEN = ' ' "
IMPORTING
MAXUNMATCHED = "
UNUSED = "
TABLES
FIELDLIST1 = "
FIELDLIST2 = "
PROPOSAL = "
EXCEPTIONS
ILLEGAL_INPUT = 1
IMPORTING Parameters details for DD_INT_FIELDMATCH_PROPOSAL
DOUBLEMIN -
Data type: DCMATCHCTR-DOUBLEDefault: '10'
Optional: Yes
Call by Reference: No ( called with pass by value option)
FORBIDDEN -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DD_INT_FIELDMATCH_PROPOSAL
MAXUNMATCHED -
Data type: DCMATCHCTR-REQUIREDOptional: No
Call by Reference: No ( called with pass by value option)
UNUSED -
Data type: DDREFSTRUC-BOOLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DD_INT_FIELDMATCH_PROPOSAL
FIELDLIST1 -
Data type: DCMATCHCTROptional: No
Call by Reference: No ( called with pass by value option)
FIELDLIST2 -
Data type: DCMATCHCTROptional: No
Call by Reference: No ( called with pass by value option)
PROPOSAL -
Data type: DCMATCHRESOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_INT_FIELDMATCH_PROPOSAL 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_doublemin | TYPE DCMATCHCTR-DOUBLE, " '10' | |||
| lt_fieldlist1 | TYPE STANDARD TABLE OF DCMATCHCTR, " | |||
| lv_maxunmatched | TYPE DCMATCHCTR-REQUIRED, " | |||
| lv_illegal_input | TYPE DCMATCHCTR, " | |||
| lv_unused | TYPE DDREFSTRUC-BOOL, " | |||
| lv_forbidden | TYPE C, " ' ' | |||
| lt_fieldlist2 | TYPE STANDARD TABLE OF DCMATCHCTR, " | |||
| lt_proposal | TYPE STANDARD TABLE OF DCMATCHRES. " |
|   CALL FUNCTION 'DD_INT_FIELDMATCH_PROPOSAL' "DD: Create a proposal for matching fields |
| EXPORTING | ||
| DOUBLEMIN | = lv_doublemin | |
| FORBIDDEN | = lv_forbidden | |
| IMPORTING | ||
| MAXUNMATCHED | = lv_maxunmatched | |
| UNUSED | = lv_unused | |
| TABLES | ||
| FIELDLIST1 | = lt_fieldlist1 | |
| FIELDLIST2 | = lt_fieldlist2 | |
| PROPOSAL | = lt_proposal | |
| EXCEPTIONS | ||
| ILLEGAL_INPUT = 1 | ||
| . " DD_INT_FIELDMATCH_PROPOSAL | ||
ABAP code using 7.40 inline data declarations to call FM DD_INT_FIELDMATCH_PROPOSAL
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 DOUBLE FROM DCMATCHCTR INTO @DATA(ld_doublemin). | ||||
| DATA(ld_doublemin) | = '10'. | |||
| "SELECT single REQUIRED FROM DCMATCHCTR INTO @DATA(ld_maxunmatched). | ||||
| "SELECT single BOOL FROM DDREFSTRUC INTO @DATA(ld_unused). | ||||
| DATA(ld_forbidden) | = ' '. | |||
Search for further information about these or an SAP related objects