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

Function FMCA_PSOB_TREE_MAINTAIN 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_PSOB_TREE_MAINTAIN'"Edit Contract Object.
EXPORTING
I_PSOBKEY = "ID Key for Contract Object
* I_DPSOB = "General Data for Contract Object
* I_DPSOB_BP_ACC = "Partner-Dependent Data on Contract Object
* I_START_VIEW = "Start view
* I_PSOBTYP = "Contract Object Type
* I_VALDT = SY-DATLO "Validity Date
* I_AKTYP = '03' "Activity category
* I_DISPLAY_ONLY = ' ' "Only Display Allowed?
* I_SHOW_OBSOLETE = ' ' "Display Obsolete Entries Also?
* I_PARTNER = "Business Partner Number
* I_PARTNERACCTYP = "Contract Account Category
* I_PARTNERACC = "Contract Account Number
IMPORTING
E_CHANGED = "Data Changed?
IMPORTING Parameters details for FMCA_PSOB_TREE_MAINTAIN
I_PSOBKEY - ID Key for Contract Object
Data type: PSOBKEY_PSOptional: No
Call by Reference: No ( called with pass by value option)
I_DPSOB - General Data for Contract Object
Data type: DPSOBOptional: Yes
Call by Reference: Yes
I_DPSOB_BP_ACC - Partner-Dependent Data on Contract Object
Data type: DPSOB_BP_ACCOptional: Yes
Call by Reference: Yes
I_START_VIEW - Start view
Data type: TBZ3E-SICHTOptional: Yes
Call by Reference: Yes
I_PSOBTYP - Contract Object Type
Data type: PSOBTYP_PSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VALDT - Validity Date
Data type: SY-DATLODefault: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AKTYP - Activity category
Data type: TBZ0K-AKTYPDefault: '03'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DISPLAY_ONLY - Only Display Allowed?
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SHOW_OBSOLETE - Display Obsolete Entries Also?
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNERACCTYP - Contract Account Category
Data type: VKTYP_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNERACC - Contract Account Number
Data type: VKONT_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMCA_PSOB_TREE_MAINTAIN
E_CHANGED - Data Changed?
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FMCA_PSOB_TREE_MAINTAIN 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_e_changed | TYPE BOOLE-BOOLE, " | |||
| lv_i_psobkey | TYPE PSOBKEY_PS, " | |||
| lv_i_dpsob | TYPE DPSOB, " | |||
| lv_i_dpsob_bp_acc | TYPE DPSOB_BP_ACC, " | |||
| lv_i_start_view | TYPE TBZ3E-SICHT, " | |||
| lv_i_psobtyp | TYPE PSOBTYP_PS, " | |||
| lv_i_valdt | TYPE SY-DATLO, " SY-DATLO | |||
| lv_i_aktyp | TYPE TBZ0K-AKTYP, " '03' | |||
| lv_i_display_only | TYPE XFELD, " SPACE | |||
| lv_i_show_obsolete | TYPE XFELD, " SPACE | |||
| lv_i_partner | TYPE BU_PARTNER, " | |||
| lv_i_partneracctyp | TYPE VKTYP_KK, " | |||
| lv_i_partneracc | TYPE VKONT_KK. " |
|   CALL FUNCTION 'FMCA_PSOB_TREE_MAINTAIN' "Edit Contract Object |
| EXPORTING | ||
| I_PSOBKEY | = lv_i_psobkey | |
| I_DPSOB | = lv_i_dpsob | |
| I_DPSOB_BP_ACC | = lv_i_dpsob_bp_acc | |
| I_START_VIEW | = lv_i_start_view | |
| I_PSOBTYP | = lv_i_psobtyp | |
| I_VALDT | = lv_i_valdt | |
| I_AKTYP | = lv_i_aktyp | |
| I_DISPLAY_ONLY | = lv_i_display_only | |
| I_SHOW_OBSOLETE | = lv_i_show_obsolete | |
| I_PARTNER | = lv_i_partner | |
| I_PARTNERACCTYP | = lv_i_partneracctyp | |
| I_PARTNERACC | = lv_i_partneracc | |
| IMPORTING | ||
| E_CHANGED | = lv_e_changed | |
| . " FMCA_PSOB_TREE_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_PSOB_TREE_MAINTAIN
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_changed). | ||||
| "SELECT single SICHT FROM TBZ3E INTO @DATA(ld_i_start_view). | ||||
| "SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt). | ||||
| DATA(ld_i_valdt) | = SY-DATLO. | |||
| "SELECT single AKTYP FROM TBZ0K INTO @DATA(ld_i_aktyp). | ||||
| DATA(ld_i_aktyp) | = '03'. | |||
| DATA(ld_i_display_only) | = ' '. | |||
| DATA(ld_i_show_obsolete) | = ' '. | |||
Search for further information about these or an SAP related objects