SAP PC_CHECK_EXTENSION Function Module for Checks the name extension of a PC file name for correctness









PC_CHECK_EXTENSION is a standard pc check extension SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks the name extension of a PC file name for correctness 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 pc check extension FM, simply by entering the name PC_CHECK_EXTENSION into the relevant SAP transaction such as SE37 or SE38.

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



Function PC_CHECK_EXTENSION 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 'PC_CHECK_EXTENSION'"Checks the name extension of a PC file name for correctness
EXPORTING
IEXT = "Extension to be checked
* CHECK_DOS_FORMAT = "

IMPORTING
EEXT = "Checked extension

EXCEPTIONS
INVALID_EXTENSION = 1
.



IMPORTING Parameters details for PC_CHECK_EXTENSION

IEXT - Extension to be checked

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

CHECK_DOS_FORMAT -

Data type: RC27X-FLG_SEL
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for PC_CHECK_EXTENSION

EEXT - Checked extension

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

EXCEPTIONS details

INVALID_EXTENSION - Incorrect extension

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

Copy and paste ABAP code example for PC_CHECK_EXTENSION 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_eext  TYPE STRING, "   
lv_iext  TYPE STRING, "   
lv_invalid_extension  TYPE STRING, "   
lv_check_dos_format  TYPE RC27X-FLG_SEL. "   

  CALL FUNCTION 'PC_CHECK_EXTENSION'  "Checks the name extension of a PC file name for correctness
    EXPORTING
         IEXT = lv_iext
         CHECK_DOS_FORMAT = lv_check_dos_format
    IMPORTING
         EEXT = lv_eext
    EXCEPTIONS
        INVALID_EXTENSION = 1
. " PC_CHECK_EXTENSION




ABAP code using 7.40 inline data declarations to call FM PC_CHECK_EXTENSION

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 FLG_SEL FROM RC27X INTO @DATA(ld_check_dos_format).
 


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!