SAP /BA1/F4_MAPI_SEC_MODIFY Function Module for MAPI Interface: Create or Change Security Prices

Search SAP Function Modules

/BA1/F4_MAPI_SEC_MODIFY is a standard /ba1/f4 mapi sec modify SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MAPI Interface: Create or Change Security Prices 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 /ba1/f4 mapi sec modify FM, simply by entering the name /BA1/F4_MAPI_SEC_MODIFY into the relevant SAP transaction such as SE37 or SE38.

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

Function /BA1/F4_MAPI_SEC_MODIFY 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 '/BA1/F4_MAPI_SEC_MODIFY'"MAPI Interface: Create or Change Security Prices
  EXPORTING
   MDCODE =  "Market Data Area
*  STATUS = ' ' "Market Date Status
*  TESTRUN = ' ' "Import Data as a Test Run
*  CORRECTIONSERVERACTIV = '0' "Correction Activity for Automatic Corrections
*  CUSTOMIZINGSETTINGS =  "Structure for Overriding Customizing Settings in Mass Correction
   EXTNUMBER =  "External Number
   EXCHANGE =  "Exchange
   PRTYPE =  "Exchange Rate Category
   VALIDDATE =  "Date
*  ADDON =  "Price Symbol
   UNIT =  "Unit
*  PRICE =  "Exchange Rate
   DIRTYFLAG =  "Boolean Values TRUE (='X') and FALSE (= ' ')

TABLES
*  RETURN =  "Table with BAPI Return Information

.

IMPORTING Parameters details for /BA1/F4_MAPI_SEC_MODIFY

MDCODE - Market Data Area

Data type: /BA1/F4_STR_SEC_MAPIPARA-MDCODE
Optional: No
Call by Reference: Yes

STATUS - Market Date Status

Data type: /BA1/F4_STR_SEC_MAPIPARA-STATUS
Default: SPACE
Optional: Yes
Call by Reference: Yes

TESTRUN - Import Data as a Test Run

Data type: /BA1/F4_STR_SEC_MAPIPARA-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: Yes

CORRECTIONSERVERACTIV - Correction Activity for Automatic Corrections

Data type: /BA1/F4_STR_SEC_MAPIPARA-CORRECTIONSERVERACTIV
Default: '0'
Optional: Yes
Call by Reference: Yes

CUSTOMIZINGSETTINGS - Structure for Overriding Customizing Settings in Mass Correction

Data type: /BA1/F4_STR_CUST_SETTING
Optional: Yes
Call by Reference: Yes

EXTNUMBER - External Number

Data type: /BA1/F4_STR_SEC_MAPIPARA-EXTNUMBER
Optional: No
Call by Reference: Yes

EXCHANGE - Exchange

Data type: /BA1/F4_STR_SEC_MAPIPARA-EXCHANGE
Optional: No
Call by Reference: Yes

PRTYPE - Exchange Rate Category

Data type: /BA1/F4_STR_SEC_MAPIPARA-PRTYPE
Optional: No
Call by Reference: Yes

VALIDDATE - Date

Data type: /BA1/F4_STR_SEC_MAPIPARA-VALIDDATE
Optional: No
Call by Reference: Yes

ADDON - Price Symbol

Data type: /BA1/F4_STR_SEC_MAPIPARA-ADDON
Optional: Yes
Call by Reference: Yes

UNIT - Unit

Data type: /BA1/F4_STR_SEC_MAPIPARA-UNIT
Optional: No
Call by Reference: Yes

PRICE - Exchange Rate

Data type: /BA1/F4_STR_SEC_MAPIPARA-PRICE
Optional: Yes
Call by Reference: Yes

DIRTYFLAG - Boolean Values TRUE (='X') and FALSE (= ' ')

Data type: /BA1/F4_STR_SEC_MAPIPARA-DIRTYFLAG
Optional: No
Call by Reference: Yes

TABLES Parameters details for /BA1/F4_MAPI_SEC_MODIFY

RETURN - Table with BAPI Return Information

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

Copy and paste ABAP code example for /BA1/F4_MAPI_SEC_MODIFY 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 /BA1/F4_MAPI_SEC_MODIFY

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