Naming Proxy Objects 

Use

The length of names of interfaces, messages types, and data types is unlimited in the Integration Repository. Also, unlike ABAP, the system differentiates between uppercase and lowercase text; this is normally used to distinguish between words within a name (for example: FlightBooking).

• When the text switches from lower to uppercase, the generation function inserts an underscore to make the change more clear (for example: FLIGHT_BOOKING).
• The system shortens names that are longer than 30 characters.
• If a naming conflict occurs, the generation function appends a number to the new name to make a distinction.

After the system has indicated the changes that you need to make to the original name, you can adjust the names to make them clearer using the tab page Problems.

You can also change the names of proxy objects that did not need to be changed during generation. It is a good idea, for example, if you have had to make changes to the tab page Problems, to adjust the remaining names of parameters of the same interface in the same way. To do this, switch to the tab page Structure after you have adjusted all the names on the tab page Problems. Provided that the proxy objects have not been used in other proxy objects, you can also change these names by choosing Change Name/Short Text in the context menu.

When you are happy with your changes, to create the objects in the system, choose Activate. In addition to the generated objects, proxy generation also saves meta data with information about assigning it to an interface in the Integration Repository. This meta data is transported together with the proxies.