SAP GLE_MCA_FX_POS_UPDATE_DOCREF Function Module for Update Document References

Search SAP Function Modules

GLE_MCA_FX_POS_UPDATE_DOCREF is a standard gle mca fx pos update docref 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 Document References 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 gle mca fx pos update docref FM, simply by entering the name GLE_MCA_FX_POS_UPDATE_DOCREF into the relevant SAP transaction such as SE37 or SE38.

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

Function GLE_MCA_FX_POS_UPDATE_DOCREF 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 'GLE_MCA_FX_POS_UPDATE_DOCREF'"Update Document References
  EXPORTING
   I_PRCCAT =  "MCA Process Category
   I_RUNID =  "Run Administration Run ID
   I_MCA_DOCNO =  "MCA Document Number
*  I_DOCCAT = ' ' "Document Category to distinguish between FI and S/L document
   I_TAB_BKPF =  "Posted FI Documents
*  I_UPD_FDOCREF = ' ' "Update FDOCREF: TRUE (='X') and FALSE (=' ')
*  I_UPD_DOC = ' ' "Update DOC: TRUE (='X') and FALSE (=' ')

EXCEPTIONS
   INSERT_ERROR = 1    CREATE_NUMBER_FAILED = 2 

.

IMPORTING Parameters details for GLE_MCA_FX_POS_UPDATE_DOCREF

I_PRCCAT - MCA Process Category

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

I_RUNID - Run Administration Run ID

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

I_MCA_DOCNO - MCA Document Number

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

I_DOCCAT - Document Category to distinguish between FI and S/L document

Data type: GLE_MCA_DTE_DOC_CAT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TAB_BKPF - Posted FI Documents

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

I_UPD_FDOCREF - Update FDOCREF: TRUE (='X') and FALSE (=' ')

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

I_UPD_DOC - Update DOC: TRUE (='X') and FALSE (=' ')

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

EXCEPTIONS details

INSERT_ERROR - Insert error

Data type:
Optional: No
Call by Reference: Yes

CREATE_NUMBER_FAILED - Number not created

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GLE_MCA_FX_POS_UPDATE_DOCREF 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.

ABAP code using 7.40 inline data declarations to call FM GLE_MCA_FX_POS_UPDATE_DOCREF

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