SAP CPE_TEST_CONVERT_DOCNUMBER Function Module for CPE: Test conversion of document number to GUID









CPE_TEST_CONVERT_DOCNUMBER is a standard cpe test convert docnumber SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CPE: Test conversion of document number to GUID 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 cpe test convert docnumber FM, simply by entering the name CPE_TEST_CONVERT_DOCNUMBER into the relevant SAP transaction such as SE37 or SE38.

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



Function CPE_TEST_CONVERT_DOCNUMBER 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 'CPE_TEST_CONVERT_DOCNUMBER'"CPE: Test conversion of document number to GUID
EXPORTING
IV_DOCNO = "Character Field Length = 10
IV_DOCITEMNO = "Character Field Length = 10

IMPORTING
EV_DOC_GUID = "CPE Caller - GUID of Document Header
EV_DOCITEM_GUID = "CPE Caller - GUID of Document Item

EXCEPTIONS
DOCUMENT_NOT_FOUND = 1
.



IMPORTING Parameters details for CPE_TEST_CONVERT_DOCNUMBER

IV_DOCNO - Character Field Length = 10

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

IV_DOCITEMNO - Character Field Length = 10

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

EXPORTING Parameters details for CPE_TEST_CONVERT_DOCNUMBER

EV_DOC_GUID - CPE Caller - GUID of Document Header

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

EV_DOCITEM_GUID - CPE Caller - GUID of Document Item

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

EXCEPTIONS details

DOCUMENT_NOT_FOUND - Document not found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CPE_TEST_CONVERT_DOCNUMBER 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_iv_docno  TYPE CHAR10, "   
lv_ev_doc_guid  TYPE CPET_DOC_GUID, "   
lv_document_not_found  TYPE CPET_DOC_GUID, "   
lv_iv_docitemno  TYPE CHAR10, "   
lv_ev_docitem_guid  TYPE CPET_DOCITEM_GUID. "   

  CALL FUNCTION 'CPE_TEST_CONVERT_DOCNUMBER'  "CPE: Test conversion of document number to GUID
    EXPORTING
         IV_DOCNO = lv_iv_docno
         IV_DOCITEMNO = lv_iv_docitemno
    IMPORTING
         EV_DOC_GUID = lv_ev_doc_guid
         EV_DOCITEM_GUID = lv_ev_docitem_guid
    EXCEPTIONS
        DOCUMENT_NOT_FOUND = 1
. " CPE_TEST_CONVERT_DOCNUMBER




ABAP code using 7.40 inline data declarations to call FM CPE_TEST_CONVERT_DOCNUMBER

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!