on 05-31-2017 11:03 AM
Dear Experts,
I created a customer-specific solution. There is another Solution running on the tenant. Therein, an XBO on the Material BO is defined. It adds 3 new elements / extension fields to the Material.Common node.
I am not able to access these fields from within my Solution. Is there a similar component like "References to Customer-specific fields.ref" (used to access extension fields defined via Adaptation Mode) to access XBO-extension fields?
Thanks,
Pablo
Just read a post by another SAP-Developer. Having this cross-solution barrier in mind - his advice is to basically put all extension components into one single solution.
To me, this feels like a capitulation to given, unneccessary restrictions of the software architecture.
Why is it not possible to import the namespace of another custom solution?
Wouldn't that be the most reasonable approach to deal with this issue?
Best,
Pablo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pablo,
the only way I know is to use a Webservice. The Webservice contains the extension fields of all solution. So you may use a Material-Webservice inside your solution to read or update the extension fields from the other solution.
Kind regards,
Frank Pohlmann
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there,
I don't think it's possible.
I'm always creating fields via KUT to avoid situations like that.
Here there's a problem like yours: https://answers.sap.com/questions/210141/communication-between-solutions-copy-extension-fie.html
Best regards.
Alexandre.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Alexandre.
I also thought about creating KUT extension fields, but this implies cumbersome lifecycle management. For instance, every time you want to deploy the Solution to another tenant, you would have to re-create the KUT-fields (using the same technical names) before you can deploy your solution. I prefer to ship all app components wrapped in one package.
Regarding my current issue, I will re-implement the functionality of the other Solution in my solution and delete the other one. But I can imagine scenarios where this might cause a lot of effort, especially if the other solution is already productive.
Best,
Pablo
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.