SAP FMCA_PARTNER_MAINTAIN_NEW_UI Function Module for

Search SAP Function Modules

FMCA_PARTNER_MAINTAIN_NEW_UI is a standard fmca partner maintain new ui SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 partner maintain new ui FM, simply by entering the name FMCA_PARTNER_MAINTAIN_NEW_UI into the relevant SAP transaction such as SE37 or SE38.

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

Function FMCA_PARTNER_MAINTAIN_NEW_UI 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_PARTNER_MAINTAIN_NEW_UI'"
  EXPORTING
*  IV_PARTNER =  "Business Partner Number
*  IT_FIELD_VALUES =  "
*  IV_NO_NAVIGATION = ' ' "
*  IV_NO_ROLE_SWITCH = ' ' "
*  IV_NO_ACTIVITY_SWITCH = ' ' "
*  IV_NO_DIALOG = ' ' "
*  IV_GROUP_SELECTION = 'X' "
*  IV_LOCATOR_VISIBLE = 'X' "
*  IV_ROLE = 'MKK' "Business Partner Role
*  IV_TYPE =  "Business Partner Category
*  IV_GROUP =  "Business Partner Grouping
*  IV_ACTIVITY = '01' "Activity Category
*  IV_SAVE_MODE = 'X' "Indicator: Business partner safeguards himself
*  IV_DIALOG_MODE = ' ' "Dialog Mode
*  IV_SUB_HEADER_ID = 'BUP001' "Key of Additional Header Data
*  IV_DYNID =  "Screen

 IMPORTING
   EV_DATA_CHANGED =  "Were Data Changed?
   EV_PARTNER_HANDLE =  "Business Partner Number

EXCEPTIONS
   ERROR_OCCURRED = 1 

.

IMPORTING Parameters details for FMCA_PARTNER_MAINTAIN_NEW_UI

IV_PARTNER - Business Partner Number

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

IT_FIELD_VALUES -

Data type: BU_BUS0FLDVAL_T
Optional: Yes
Call by Reference: Yes

IV_NO_NAVIGATION -

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

IV_NO_ROLE_SWITCH -

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

IV_NO_ACTIVITY_SWITCH -

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

IV_NO_DIALOG -

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

IV_GROUP_SELECTION -

Data type: BU_BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LOCATOR_VISIBLE -

Data type: BU_BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ROLE - Business Partner Role

Data type: BUS_ROLES
Default: 'MKK'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TYPE - Business Partner Category

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

IV_GROUP - Business Partner Grouping

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

IV_ACTIVITY - Activity Category

Data type: BU_AKTYP
Default: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SAVE_MODE - Indicator: Business partner safeguards himself

Data type: BU_XSAVE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DIALOG_MODE - Dialog Mode

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

IV_SUB_HEADER_ID - Key of Additional Header Data

Data type: BU_SUB_HEADER_ID
Default: 'BUP001'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DYNID - Screen

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

EXPORTING Parameters details for FMCA_PARTNER_MAINTAIN_NEW_UI

EV_DATA_CHANGED - Were Data Changed?

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

EV_PARTNER_HANDLE - Business Partner Number

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

EXCEPTIONS details

ERROR_OCCURRED - An error has occurred

Data type:
Optional: No
Call by Reference: Yes

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

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