Ansicht
Dokumentation
ESH_MAINT_MO_TRANS - Maintain Transport of Models
BAL Application Log Documentation General Material DataThis documentation is copyright by SAP AG.
Transporting Search Models
Search models are organized into search software components, which, among other things, serve as a transport vehicle. These software components have to be transported between systems to deliver new or corrected SAP models to customers, or to transfer customer-specific models from development systems to test or productive systems.
Delivering SAP Models
SAP delivers new and enhanced search models with product releases, enhancement packages (EHP), or support package stacks (SPS). The new model versions are available immediately after an upgrade or update, and also in customer-specific models that include an SAP model.
Caution- Do not transport SAP software components between customer systems. The SAP models must be updated by an update, upgrade, or SAP Note only.
SAP provides urgent corrections to models in SAP Notes, which you can import using the Note Assistant (transaction SNOTE). When you open the administration cockpit for the first time after importing a note, a background job starts, which updates the models. A corresponding message is displayed in the Search and Analytics Modeler (not in the administration cockpit).
Note- If a model has been updated, you have to manually update the existing connectors that are based on this model. You can see which connectors are affected in the administration cockpit, where they are marked in the Changed column. To update these connectors, select the line or lines and choose Actions --> Update.
After an upgrade, update, or correction by SAP Note, take a look in version management for modeling (Actions --> Version Management). If software components are marked in red, open a customer message on the support component of the transported model. You can find the component name in step 1 of modeling under Properties --> Application Component.
Transporting Customer-Specific Models
There is a transport connection in modeling for transporting customer-specific models between development, test, and productive systems. If you make changes during modeling and save them, you have to create or select a transport request for the software component in question. These are standard SAP transport requests, which you can manage and send in the Transport Organizer (transaction SE09).
Note the following when transporting search software components:
Never create transport requests for search models outside the modeler. Enterprise Search uses the special transport object R3TR SEST; the correct request can only be created in the modeler.
The first time you save, the transport object is assigned to the request. Further changes in the same software component do not change the request. The software component is not transported in full until the request is released. Therefore, the system does not notify you if an open transport request exists. If several people are modeling in the same software component, they should consult with each other.
Once the transport request has been imported, the target client in the target system has the same status as the source client at the time the request was released. Any existing local changes in the transported software component in the target client are lost.
If the target client in the target system is not client 000, you must set up an RFC connection to the different client before the import. More information:
- 1790318 Importing software components directly into target client
After the transport to the target system, take a look at the log in the Transport Organizer (select request and choose Transport Logs). If errors are displayed under Target System --> Method Execution and you cannot correct them, open a customer message on the support component of the transported model. You can find the component name in step 1 of modeling under --> Application Component.
In the Modeler of Enterprise Search you can view the transport request for a software component. Select the software component and choose Software Component --> View Transport Requests.
General Data in Customer Master Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 4395 Date: 20240523 Time: 195114 sap01-206 ( 97 ms )
