SAP FMCA_SAMPLE_P231 Function Module for EVENT for TaxObjectERPCheckQueryResponse_In(Outbound)

Search SAP Function Modules

FMCA_SAMPLE_P231 is a standard fmca sample p231 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 TaxObjectERPCheckQueryResponse_In(Outbound) 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 p231 FM, simply by entering the name FMCA_SAMPLE_P231 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_P231 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_P231'"EVENT for TaxObjectERPCheckQueryResponse_In(Outbound)
  EXPORTING
   IM_T_RETURN =  "
   I_PSOBJECTKEYOUT =  "Identification Key for Contract Object
   IM_LOG =  "protocol message issued by an application
   I_PSOBJECTFACTS =  "
   I_PSOBJECTDETAIL =  "BAPI Basic Data for Contract Object (Input)
   I_PSOBJECTOBLGN_ASSGMNT =  "
   I_PSOBJECT_TYPE =  "BAPI Basic Data for Contract Object

CHANGING
   C_OUTPUT =  "Response to query for check of a tax object

.

IMPORTING Parameters details for FMCA_SAMPLE_P231

IM_T_RETURN -

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

I_PSOBJECTKEYOUT - Identification Key for Contract Object

Data type: BAPI_CTRACPSOBJECT_HEAD-PSOBJECTKEY
Optional: No
Call by Reference: Yes

IM_LOG - protocol message issued by an application

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

I_PSOBJECTFACTS -

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

I_PSOBJECTDETAIL - BAPI Basic Data for Contract Object (Input)

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

I_PSOBJECTOBLGN_ASSGMNT -

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

I_PSOBJECT_TYPE - BAPI Basic Data for Contract Object

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

CHANGING Parameters details for FMCA_SAMPLE_P231

C_OUTPUT - Response to query for check of a tax object

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

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

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