Hello, i have a question regarding the extensibility of standard RAP Business Objects.
So a Customer wants to add some customer specific fields to the standard table aufk, which has so far been solved via a customer include. However, as part of the transformation, this is obsolete and should be made cloud ready. Therefore my idea was to create an Adaption Project of the required standard Fiori Application and extend it via a custoper specific CDS model with an underlying dtab to make the values for the custom fields persistent.
This is where the extensibility of the standard behavior definition for said Application comes in. Since it does not have the 'extensable' feature enabled, i need a workaround. So the question is, if i now create my own behavior definition, is there a way to include the standard behavior to keep it safe for SAP updates and to keep it managing the part which writes into the aufk table?
Many thanks in advance.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.