afterModify in BusinessPartner is only firing on save press.

[ixdse]

Hello,

the afterModify event of Root should fire when you change a field in BusinessPartner but it is firing only when I use the save button. Why?

My Problem is I want to rise a Message in afterModify wenn a new Tax Number is entered.

In the AfterModify event of TaxNumber the event is firing correctly but you can't rise messages there because it is not extensible (why? Why are so many Nodes not extensible?).

How can I get the afterModify event and rise a messagewhen I enter a new TaxNumber?

Regards,

David

[former_member601949]

Hi David,

Can you please bit more elaborate your question?

Set Requires Roundtrip = True in properties tab of that field in DataModel. It will call your scripts.

Rgs,

Chandra

[ixdse]

Hello Chandra Gajula,

Thanks for the fast reply.

I found the property you mentioned but the screens of Business Object Extentions (OIF of BusinessParner) are read-only. How can I change this value in the Business Partner Extention?

Here my problem in detail:

Business Partner Extension:

AfterModify-Root:

This only fires when you click on the Save Button of the Create BusinessPartner Work Center and not when you change any field (for example: Tax Number)

AfterModify-TaxNumber:

Fires correctly if you changes the TaxNumber but messages are not allowed here.

The Question is: How can I fire my message after I change the Tax Number.

[VVancalbergh]

Fact is that some parts of a standard SAP BO are not extensible (yet). I assume because they want to retain the freedom to change as many parts of the application as possible, since, once it's part of the PSM, it's very hard for them to do breaking changes on it. Anything outside of the PSM is liable to change per patch (but unlikely). SAP calls it the "PSM" (Public Solution Model). You can request a part of the standard application to be included into the PSM.

More information here: https://blogs.sap.com/2017/10/02/sap-bydesign-public-solution-model/

As for the "Roundtrip" property: Standard UI components are all set to readonly. The only influence we have is through the Extensibility Explorer which is pretty limited to non-existant when it comes to changing the pre-existing elements.