SAP COM_PRODUCT_ID_DBFORMAT_CHECK Function Module for









COM_PRODUCT_ID_DBFORMAT_CHECK is a standard com product id dbformat check 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 com product id dbformat check FM, simply by entering the name COM_PRODUCT_ID_DBFORMAT_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: COM_PR_CONVERSION
Program Name: SAPLCOM_PR_CONVERSION
Main Program: SAPLCOM_PR_CONVERSION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function COM_PRODUCT_ID_DBFORMAT_CHECK 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 'COM_PRODUCT_ID_DBFORMAT_CHECK'"
EXPORTING
IV_PRODUCT_ID = "

EXCEPTIONS
LENGHT_ERROR = 1 CUSTOMIZING_ERROR = 2
.



IMPORTING Parameters details for COM_PRODUCT_ID_DBFORMAT_CHECK

IV_PRODUCT_ID -

Data type: COMT_PRODUCT_ID
Optional: No
Call by Reference: Yes

EXCEPTIONS details

LENGHT_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CUSTOMIZING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COM_PRODUCT_ID_DBFORMAT_CHECK 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_lenght_error  TYPE STRING, "   
lv_iv_product_id  TYPE COMT_PRODUCT_ID, "   
lv_customizing_error  TYPE COMT_PRODUCT_ID. "   

  CALL FUNCTION 'COM_PRODUCT_ID_DBFORMAT_CHECK'  "
    EXPORTING
         IV_PRODUCT_ID = lv_iv_product_id
    EXCEPTIONS
        LENGHT_ERROR = 1
        CUSTOMIZING_ERROR = 2
. " COM_PRODUCT_ID_DBFORMAT_CHECK




ABAP code using 7.40 inline data declarations to call FM COM_PRODUCT_ID_DBFORMAT_CHECK

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!