Configuration for Taking Over UI Texts into the ABAP Back End 

Use

To ensure that UI texts from the Enterprise Services Repository are adopted into the ABAP back end, you need to schedule a report as a periodic background job. This may have already taken place through CTC programs. If this is the case and your system requirements for this task are met, you do not need to undertake any further steps.

Procedure

Perform the following steps in order to check whether the job has already been scheduled through CTC programs:

...

       1.      Check whether the ESR logical port exists for the proxy class CO_TXV_WSC_REPOSITORY_APIOUT. To do this, use the report TXV_API_LOGICAL_PORT.

                            a.      In the Logical Port field, choose the name ESR.

                            b.      Choose Display and execute the report.

If the ESR logical port exists, the system will display the properties of this port. Otherwise, you receive an error message.

       2.      Check whether the job TXV_LOAD_DELTA_OF_ESR_UI_TEXTS exists.
In the Job Name field, choose the job TXV*.

                            a.      Call transaction SM37.

                            b.      In the User Name field, choose *.

                            c.      Mark the required checkboxes in the screen section called Job status.

                            d.      Under Job Start Conditions, enter a suitable time interval.

                            e.      Execute the transaction and, in the following overview, search for the job TXV_LOAD_DELTA_OF_ESR_UI_TEXTS.

                              f.      Double-click the entry in order to check the definition of the job. The job must have the following properties:

                                                  i.       The job is planned periodically and runs daily at 2 o’clock.

                                                ii.       The job contains a step in which the report TXV_LOAD_ESR_UI_TEXTS is called with the variant SAP&LOAD_DELTA. This variant has the effect that all texts that were changed since the last loading process are loaded (across all installed software component versions and for all installed languages).

If the job scheduling has already taken place and the requirements of your system are met, you do not need to perform any further steps.
If the job is already scheduled but you require different parameters for the job, you need to remove the existing job schedule. To do this, remove the job in question in the job overview. Afterwards, you need to reschedule the job (see item 6 below).
If the job is not already scheduled, perform the following steps:

...

       1.      Define the logical port ESR for the proxy class CO_TXV_WSC_REPOSITORY_APIOUT.
To set up the logical port, use the report TXV_API_LOGICAL_PORT.
For more information on setting up logical ports, refer to the chapter Configuring a Consumer Proxy.

...

                            a.      In the Logical Port field, choose the name ESR.

                            b.      Choose Create.

                            c.      Enter a host name and a port number.

                            d.      Choose User Name and Password under Security.
In the exchange profile (refer to: Exchange Profile Maintenance), you will find the user name and the password for applications that access the Enterprise Services Repository.

User Name: key com.sap.aii.applicationsystem.serviceuser.name
Password: key com.sap.aii.applicationsystem.serviceuser.pwd

Enter the values maintained in the exchange profile into the corresponding fields.

                            e.      Execute the report.

       2.      Plan a periodic job for the report TXV_LOAD_ESR_UI_TEXTS.

                            a.      Create a variant for the report TXV_LOAD_ESR_UI_TEXTS that contains your requirements for periodic loading.

                                                  i.       Start the report TXV_LOAD_ESR_UI_TEXTS.

                                                ii.       In the Logical Port field, choose the name ESR.

                                               iii.       If the system contains test components that are loaded periodically, choose All Test Components.

                                               iv.       Leave all the other settings unchanged if you wish to periodically read all texts that were changed since the last loading process.

                                                 v.       Save the variant under any arbitrary name.

                                               vi.       There are system variants available that you can also use. Periodic loading of changed texts is described by the variant SAP&LOAD_DELTA.

                            b.      Plan the report TXV_LOAD_ESR_UI_TEXTS as a periodic background job. Use a suitable variant of this job and enter the conditions that will trigger the job start.
Execution frequency of the job should depend on the frequency of text changes. Every time the report is run, it loads all texts that have been changed since the last run from the Enterprise Services Repository.

...

                                                  i.       Call transaction SM36 to schedule the job.
(For more information about background jobs, refer to Scheduling Background Jobs).

                                                ii.       For simple scheduling, use the report TXV_SCHEDULE_LOAD_ESR_TEXTS.

1.       Start the report.

2.       In the Variant field, choose a suitable variant.

3.       Enter a job name in the Job Name field.

4.       In the User Name field, enter the name of the user who will be processing the job.

5.       Set the time for the first job start and for the frequency of the job execution.