cancel
Showing results for 
Search instead for 
Did you mean: 

How to trigger ~Modify_objects method of the Custom Genil Class created for a view for the Std EH_ONSAVE function to trap the transaction?

Former Member
0 Kudos

Hi ,

I have a BP Overview Screen - Component BP_HEAD.

Now there is an Address Edit View in the Overview Page- BP_ADDR where I have created a custom view with three checkbox fields.

For this Custom Table View we have created a Model and Genil Class with Key fields and the Attributes (Three Checkboxes) and these choices against the key fields are saved in a custom table created in CRM.

So the new choices are done in Component BP_ADDR and these choices are saved when clicked on Save Button in BP_HEAD Overview Page.

It works fine , these fields are editable when edited for the first time in one session and then saved. Requirement is even when Save is done successfully in the same session If we click on Edit , these fields in BP_ADDR should be editable .

We achieved this by changing the Get_I methods of each Attribute rv_diabled = 'FALSE'.

But the issue is when clicked on Back the Setter Methods of these Attributes aren't triggered due to which ~Modify_Objects of Custom Genil Class is not triggered and therefore when clicked on Save the standard EH_ONSAVE method doesn't trap the custom model transaction and no changes are made so forth.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sneha,

Implement P-getter method for those checkboxes and make them server events

CASE iv_property.

     WHEN IF_BSP_WD_MODEL_SETTER_GETTER=>fp_onclick.

       rv_value = 'dummy'.

ENDCASE.

0 Kudos

Hi Sagar/Sneha,

The same thing is happening in one of my views.

I implemented the above mentioned solutions but still the Modiy-Objects and other getter-setter methods dont get triggered.

Did you find any other solution.

Thanks And Regards,

Rohit Gugale

rohit.mansukh@accenture.com

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi All,

The issue was because developer had commented the call of  super class method - "WD_DESTROY_CONTEXT" while redefining .This led to creation of multiple instances of same model. After calling method of super class, setter methods are getting triggered.

Regards,

Sneha Bhosale

0 Kudos

Hi Sagar/Sneha,

The same thing is happening in one of my views.

I implemented the above mentioned solutions but still the Modiy-Objects and other getter-setter methods dont get triggered.

Did you find any other solution.

Thanks And Regards,

Rohit Gugale

rohit.mansukh@accenture.com