Regenerating Objects

Use

You need to regenerate objects, if their object statuses are not up to date. This can occur in the following situations:

• When the project context data of your project has changed and you have adjusted this data. This can be necessary for any service creation type (API- and proxy-based).

• When the underlying configuration has changed.

• When the underlying model has changed in the ES Repository for proxy-based services and those changes have an effect on objects already generated of your service implementation.

• When, for API-based services, you have adjusted the mapping and those changes have an effect of already generated objects of your service implementation.

• When you need to change the data of single objects that you have already generated in the backend.

• When you have renamed your project after generating objects.

Prerequisites

Generated objects must already exist in the system to be able to regenerate them.

Procedure

If you want to regenerate objects or projects, proceed as described in Generating Service Implementations.

For regeneration, you must also decide about and enter into the system how the system should handle language conflicts. You can either choose to Skip objects that cannot be regenerated due to a language conflict or to Stop regeneration if language conflict occurs. A language conflict can occur if your current log on language does not correspond to the log on language that you have used when you started generation of an object for the first time.

Result

The system updates the service implementation in the backend system. After generation, you should check the objects in the To-Do Browser (see Completing Coding (To-Do Browser)) and complete and activate the coding if required. To test the service implementation, choose the Go to Proxy pushbutton and use the test function of the SPROXY transaction.