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

Function MM_CUSTOMS_PREFERENCE_DBUPDATE 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 'MM_CUSTOMS_PREFERENCE_DBUPDATE'"Update Function Module.
TABLES
* LFEI_DB_I = "Vendor Master: Preference for Import and Export
* LFEI_DB_U = "Vendor Master: Preference for Import and Export
* LFEI_DB_D = "Vendor Master: Preference for Import and Export
TABLES Parameters details for MM_CUSTOMS_PREFERENCE_DBUPDATE
LFEI_DB_I - Vendor Master: Preference for Import and Export
Data type: LFEIOptional: Yes
Call by Reference: No ( called with pass by value option)
LFEI_DB_U - Vendor Master: Preference for Import and Export
Data type: LFEIOptional: Yes
Call by Reference: No ( called with pass by value option)
LFEI_DB_D - Vendor Master: Preference for Import and Export
Data type: LFEIOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MM_CUSTOMS_PREFERENCE_DBUPDATE 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_lfei_db_i | TYPE STANDARD TABLE OF LFEI, " | |||
| lt_lfei_db_u | TYPE STANDARD TABLE OF LFEI, " | |||
| lt_lfei_db_d | TYPE STANDARD TABLE OF LFEI. " |
|   CALL FUNCTION 'MM_CUSTOMS_PREFERENCE_DBUPDATE' "Update Function Module |
| TABLES | ||
| LFEI_DB_I | = lt_lfei_db_i | |
| LFEI_DB_U | = lt_lfei_db_u | |
| LFEI_DB_D | = lt_lfei_db_d | |
| . " MM_CUSTOMS_PREFERENCE_DBUPDATE | ||
ABAP code using 7.40 inline data declarations to call FM MM_CUSTOMS_PREFERENCE_DBUPDATE
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