SAP Function Modules

PCA_DOCUMENT_NUMBER_GET SAP Function module







PCA_DOCUMENT_NUMBER_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name PCA_DOCUMENT_NUMBER_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: PCPO
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM PCA_DOCUMENT_NUMBER_GET - PCA DOCUMENT NUMBER GET





CALL FUNCTION 'PCA_DOCUMENT_NUMBER_GET' "
  EXPORTING
    i_docty =                   " t889-docty
    i_plact =                   " t889-plact
    i_rbukrs =                  " glpca-rbukrs
    i_ryear =                   " glpca-ryear
*   i_docnr = SPACE             " glpca-docnr
*   i_popup = 'X'               "
*   i_display = SPACE           "
  IMPORTING
    e_docnr =                   " glpca-docnr
    e_action =                  "
  EXCEPTIONS
    NOT_VALID = 1               "
    MISSING_PARAMETER = 2       "
    PARAMETER_MISMATCH = 3      "
    .  "  PCA_DOCUMENT_NUMBER_GET

ABAP code example for Function Module PCA_DOCUMENT_NUMBER_GET





The ABAP code below is a full code listing to execute function module PCA_DOCUMENT_NUMBER_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_docnr  TYPE GLPCA-DOCNR ,
ld_e_action  TYPE STRING .


SELECT single DOCTY
FROM T889
INTO @DATA(ld_i_docty).


SELECT single PLACT
FROM T889
INTO @DATA(ld_i_plact).


SELECT single RBUKRS
FROM GLPCA
INTO @DATA(ld_i_rbukrs).


SELECT single RYEAR
FROM GLPCA
INTO @DATA(ld_i_ryear).


SELECT single DOCNR
FROM GLPCA
INTO @DATA(ld_i_docnr).

DATA(ld_i_popup) = 'some text here'.
DATA(ld_i_display) = 'some text here'. . CALL FUNCTION 'PCA_DOCUMENT_NUMBER_GET' EXPORTING i_docty = ld_i_docty i_plact = ld_i_plact i_rbukrs = ld_i_rbukrs i_ryear = ld_i_ryear * i_docnr = ld_i_docnr * i_popup = ld_i_popup * i_display = ld_i_display IMPORTING e_docnr = ld_e_docnr e_action = ld_e_action EXCEPTIONS NOT_VALID = 1 MISSING_PARAMETER = 2 PARAMETER_MISMATCH = 3 . " PCA_DOCUMENT_NUMBER_GET
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_e_docnr  TYPE GLPCA-DOCNR ,
ld_i_docty  TYPE T889-DOCTY ,
ld_e_action  TYPE STRING ,
ld_i_plact  TYPE T889-PLACT ,
ld_i_rbukrs  TYPE GLPCA-RBUKRS ,
ld_i_ryear  TYPE GLPCA-RYEAR ,
ld_i_docnr  TYPE GLPCA-DOCNR ,
ld_i_popup  TYPE STRING ,
ld_i_display  TYPE STRING .


SELECT single DOCTY
FROM T889
INTO ld_i_docty.


SELECT single PLACT
FROM T889
INTO ld_i_plact.


SELECT single RBUKRS
FROM GLPCA
INTO ld_i_rbukrs.


SELECT single RYEAR
FROM GLPCA
INTO ld_i_ryear.


SELECT single DOCNR
FROM GLPCA
INTO ld_i_docnr.

ld_i_popup = 'some text here'.
ld_i_display = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name PCA_DOCUMENT_NUMBER_GET or its description.