SAP FMCA_SAMPLE_P259 Function Module for Event for service TaxReturnERPByBPQR









FMCA_SAMPLE_P259 is a standard fmca sample p259 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Event for service TaxReturnERPByBPQR 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 p259 FM, simply by entering the name FMCA_SAMPLE_P259 into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCA_SAMPLE_P259 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_P259'"Event for service TaxReturnERPByBPQR
EXPORTING
IS_INPUT = "Query for a tax return by business partner

CHANGING
CT_RANGE = "
.



IMPORTING Parameters details for FMCA_SAMPLE_P259

IS_INPUT - Query for a tax return by business partner

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

CHANGING Parameters details for FMCA_SAMPLE_P259

CT_RANGE -

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

Copy and paste ABAP code example for FMCA_SAMPLE_P259 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_ct_range  TYPE FMCA3_TRANGE, "   
lv_is_input  TYPE FMCA_TAX_RETURN_ERPBY_BUSINES2. "   

  CALL FUNCTION 'FMCA_SAMPLE_P259'  "Event for service TaxReturnERPByBPQR
    EXPORTING
         IS_INPUT = lv_is_input
    CHANGING
         CT_RANGE = lv_ct_range
. " FMCA_SAMPLE_P259




ABAP code using 7.40 inline data declarations to call FM FMCA_SAMPLE_P259

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!