SAP FMCA_SAMPLE_P590 Function Module for Example P590: PSCD Contract Object Navigation Check
FMCA_SAMPLE_P590 is a standard fmca sample p590 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Example P590: PSCD Contract Object Navigation Check 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 fmca sample p590 FM, simply by entering the name FMCA_SAMPLE_P590 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_PSOB_EVENTS
Program Name: SAPLFMCA_PSOB_EVENTS
Main Program: SAPLFMCA_PSOB_EVENTS
Appliation area:
Release date: 25-Nov-2002
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_SAMPLE_P590 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 'FMCA_SAMPLE_P590'"Example P590: PSCD Contract Object Navigation Check.
EXPORTING
I_DYNID = "BDT: Screen
IMPORTING
E_SAVE_NAVIGATION = "Security Navigation?
CHANGING
* C_SCREEN_TYPE = "BDT: Screen Type
* C_POSNR_REL = "BDT: Item Number
* C_VARTP = "BDT: Screen Sequence Category
* C_VARNR = "BDT: Screen Sequence
IMPORTING Parameters details for FMCA_SAMPLE_P590
I_DYNID - BDT: Screen
Data type: BU_DYNIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMCA_SAMPLE_P590
E_SAVE_NAVIGATION - Security Navigation?
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FMCA_SAMPLE_P590
C_SCREEN_TYPE - BDT: Screen Type
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
C_POSNR_REL - BDT: Item Number
Data type: BU_POSNROptional: Yes
Call by Reference: No ( called with pass by value option)
C_VARTP - BDT: Screen Sequence Category
Data type: BU_VARTPOptional: Yes
Call by Reference: No ( called with pass by value option)
C_VARNR - BDT: Screen Sequence
Data type: BU_VARNROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FMCA_SAMPLE_P590 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_i_dynid | TYPE BU_DYNID, " | |||
| lv_c_screen_type | TYPE C, " | |||
| lv_e_save_navigation | TYPE BOOLE-BOOLE, " | |||
| lv_c_posnr_rel | TYPE BU_POSNR, " | |||
| lv_c_vartp | TYPE BU_VARTP, " | |||
| lv_c_varnr | TYPE BU_VARNR. " |
|   CALL FUNCTION 'FMCA_SAMPLE_P590' "Example P590: PSCD Contract Object Navigation Check |
| EXPORTING | ||
| I_DYNID | = lv_i_dynid | |
| IMPORTING | ||
| E_SAVE_NAVIGATION | = lv_e_save_navigation | |
| CHANGING | ||
| C_SCREEN_TYPE | = lv_c_screen_type | |
| C_POSNR_REL | = lv_c_posnr_rel | |
| C_VARTP | = lv_c_vartp | |
| C_VARNR | = lv_c_varnr | |
| . " FMCA_SAMPLE_P590 | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_SAMPLE_P590
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 BOOLE FROM BOOLE INTO @DATA(ld_e_save_navigation). | ||||
Search for further information about these or an SAP related objects