Hierarchy

⤷

⤷

Attribute
Message class | ![]() |
SPRX | |
Short Description | ![]() |
Proxy Generation | |
Message Number | ![]() |
103 | |
Documentation status | ![]() |
||
Authorization check Error Message | |||
Changed On | ![]() |
20130531 |
Message Text
Help Document
When defining an interface in namespace "A", you can also use messages from another namespace "B".
Since this message in turn comprises type definitions from namespace "B", the interface from namespace "A" indirectly uses a number of type definitions from namespace "B".
If namespace "B" is in the same component or is in a subcomponent of "A" (for example, the component SAP_BASIS is a subcomponent of SAP_ABA), then the proxy objects from "B" can be reused in generation in "A" safely..
However, if the two components are completely independent (for example, CRM and APO), then you must create separate proxy objects since you cannot ensure that the required objects from "B" are available in the current system.
Therefore, in this case namespace "A" must have its own proxies for the message and the type definitions from namespace "B".
History
Last changed on/by | ![]() |
20140121 | SAP |
SAP Release Created in | 620 |