cancel
Showing results for 
Search instead for 
Did you mean: 

Loading Reuse S1 Component from Manage Material coverage app gives errors

archit_wahi
Participant
0 Kudos

Hi folks,

I have deployed pp_mrp_reuses1(F0844) component as a custom library into abap repo. my aim is to run the extended version of app Manage Material Coverage(F0251) which should use a fragment of my custom library where i have extended my fields for the table.. To open Manage material i already have extended Monitor Material coverage app(F0247A).  all three apps are deployed onto the repository.

 
Problem i am facing is when i navigate from monitor materials to manage materials app i am getting an error from the library files of the standard reuse component pp_mrp_reuses1.
I am able to load my custom Reuse Library that i can see from sources but error comes up in the standard part of the library somehow. Random errors in S3parent of standard reuse component come-up.
I see all three extended/adapted apps running in the sources.
For navigation i am using 
sap.ushell.Container.getService("CrossApplicationNavigation")  
toExternal method. with my semantic object action and parameters opening my extended version of the manage materials app.
So confused as to what piece of this puzzle is a miss??
 
 
archit_wahi_0-1713194408589.png

 

 

junwu
Active Contributor
0 Kudos
are you sure you can extend the lib? never heard that.
archit_wahi
Participant
0 Kudos

you can using the yo commands for reference https://learning.sap.com/learning-journeys/develop-sapui5-applications/developing-a-reusable-ui-libr...

and that is what is mentioned in the app extensibility for manage material coverage app the table in this app is part of the pp_mrp_reuses1 component which we have deployed as a customized library and referenced it inside the manage material app.

archit_wahi_0-1713253542895.png

 

junwu
Active Contributor
0 Kudos
how you did it? in my memory, it is not like this. usually we create extension project for Manage Material Coverage and do all the extension there.

Accepted Solutions (0)

Answers (0)