I'm having a problem turning on CUA for a component client. So far I've made changes to the following transaction...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
in both clients: CUA DV1-100 and the component client QA1-220. WE20 Partner profiles SM59 RFC Destinations (Display/Maintain) BD64 Maintenance of Distribution Model If you have any ideas please let me know.
I'll need more information on this one. But the process for activating CUA is thoroughly documented in the "authorizaitons made easy" guide book. Additionally, there are a number (and I mean a lot) of OSS notes that speak to specific bugs and issues. The one thing that struck me in your listing is that you need to make sure that you distribute the model to the child systems, and generate partner profiles in both the client and the parent system. There have been a number of issues where the partner profile will default to a BAPI that does not work correctly in your Service Pack level, so you will need to check that in WE20. I realize this may be a stupid question, but... Did you ultimately run transaction SCUA, type in the name of your CUA model and hit save?
Dig Deeper on SAP Basis administration and NetWeaver administration
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.