cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Proper way to extend standard Fiori app F2180

patrick_weber11
Participant
0 Likes
2,357

Hello community,

I recently received the requirement to add a custom field to standard Fiori App 2180 (Inspection Lots). It's the first time we need to extend such an app.

I read through so many blogs and found so many information about how to extend an app. But I'm lost and need help to judge what's the proper way these days-

F2180 is an app to manage inspection lots. I need to add a custom columns representing the user status (JEST, JSTO) for each inspection lot. I don't need to add this field to database table QALS as information already is available by default in JEST etc.

For a previous requirement, I already defined a custom CDS view which collects user status for any kind of object. This view ZI_USERSTATUS follows VDM idea, so it is basically only an interface view to JEST, JSTO Text and so on.

So now I'm looking for a proper way to add a column of ZI_USERSTATUS to F2180 app. We're running S/4 2023 FP1 on-premise.

Should I:

- add this as extension to VDM I_InspectionLot
- use Custom Field and logic app
- create an extension project using VSCode?

I tried to use custom field and logic app. First I note it is flagged as deprecated but I wasn't able to find its successor. Nontheless I first tried to create a custom field. As a result, I see changes to database table QALS for my new field. But this is not necessary imo as I don't want to add this field to database but to app only.
BTW: the system didn't ask for a transport request but instead added the changes to a temporary package. This feels not right to me.

Then I tried Datasource Extension as to my understanding, I can use this to add existing information. But I don't see how to add fields to InspectionLot. I can add fields or logic to associated objects but not to inspection lot itself.

patrick_weber11_0-1721651098588.png

 

Any tips how to solve this?


EDIT:
I was now able to extend I_InspectionLot by extending E_InspectionLot. My new field is now available in I_InspectionLot. Also I see it is available in SEGW of corresponding standard app

patrick_weber11_0-1721732571817.png



However it is still not available in "Custom Field and Logic" app. My assumption was to find it available in data source extensions. But there is no change in entity _insplot

patrick_weber11_1-1721732654502.png

What am I missing?
The app is based on consumption view C_Insplotmng, which contains E_INSPECTIONLOT. I might can go ahead and extend this view as well but then I don't understand what "Custom Fields and Logic" is good for.



Accepted Solutions (0)

Answers (1)

Answers (1)

patrick_weber11
Participant
0 Likes

Hello,

I was not able to find a better way than don't use "Custom Fields and Logic" app. Instead I had to enhance any related CDS view (like E_InspectionLot). Also I had to enhance consumption views (C_) as well as define Metadata Extensions.

I still don't feel comfortable with this solution but I was not able to find anything else.