Kontakt

Ansicht
Dokumentation

OXT_TRANSPORT_R3 - OXT_TRANSPORT_R3

OXT_TRANSPORT_R3 - OXT_TRANSPORT_R3

Fill RESBD Structure from EBP Component Structure   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

How to transport meta data of Easy Enhancement WB

Abstract: This short documentation describes, how meta data (means project and extension definitions) can be transported to other systems. Afterwards the projects and extensions can be changed in the target system and regenerated.

Note:

  • This process is not the supported standard process. Use it at your own risk.
  • This process is not necessary in normal EEW usage (generating in development system and running in test or productive system)
  • Target system must not be another client on the same system
  • Cross system extensions (e.g. Sales Order in CRM and R/3) cannot be transported with this process.

Preparation

Before you move the EEW extension data, the following things must be considered:

  • Generation of the extensions must be finished and have no errors. You might check this either by displaying status in EEWB (correctly generated) or more deeply with report OXT_METADATA_CHECK. Extensions which are checked successfully can be transported, other extensions not.
  • Generated objects must have been transported to the target system and not been changed afterwards. This is realized with the normal EEW Workbench Transport (called TGEN,WB in this document) and optionally an EEW Customizing Transport (called TGEN,CUST in this document) - both assigned to the EEW project of the extension. Please be sure that you have one transport TGEN,WB containing one or more extensions completely, same for TGEN,CUST.
  • The original system (by means of TADIR object catalog) of the generated objects must be adjusted in the target system by setting the target system as the original system. Either do this by transporting a Relocation transport from source to target system (best solution) or by running report RDDTADI7 or RDDIT200 in target system providing the transport request TGEN,WB. Alternatively you can use the toolbox of transaction SE03 to move objects.

If these steps are not performed, the transport of EEW metadata might not fail, but generating or changing of extensions in the target system will not work.

Make sure that the package (development class) and the namespace of the extension is available in the target system and identical as in the source system.

Maintain EEW system settings (transaction EEWC) in the target system in the same way as in the source system - especially name spaces. Logical system and RFC destinations can be adapted to the target system landscape. See not 649336 for further information.

Transport Process

To move the extensions, you need a new workbench transport (called TMETA,WB here) and a new customizing transport request(called TMETA,CUST here). Do not use TGEN,WB or TGEN,CUST for this purpose. Also you must take care that system settings allow the transport (in table T000 CCNOCLIIND must be initial and CCCORACTIV must be '1').

Run report OXT_TRANSPORT in the source system and provide the two transports T(META,WB) and T(META,CUST) and the extension name.

Perform this step for all extensions you want to transport. T(META,WB) and T(META,CUST) can be used for several extensions. Afterwards release the transports T(META,WB) and T(META,CUST) and import them in the target system.

If this is done, run report OXT_AFTER_IMPORT in the target system for each transported extension to adjust it.

To check whether the extensions have been transported and adjusted correctly use report OXT_METADATA_CHECK. This report checks the extension status and consistency.

Afterwards the extensions can be generated or changed again with the following restrictions:

  • New transport requests must be assigned to the project of the extensions (in EEWB transaction mark the project and select "Transport Requests" in the context menu).
  • Documentation of extensions and projects is deleted.
  • Error log entries for tasks and extensions are refreshed.

Usage in 2 system landscape

A 2 system landscape is a specific system landscape making EEW meta data transports necessary. The normal development process of 2 system landscapes is:

  • Develop in DEV system and test
  • Transport to PROD system
  • Destroy the DEV system
  • Build a new DEV system if necessary by copying the PROD system.

According to this process, the handling of EEW should be:

  • Create and change extensions in DEV system and test them
  • Transport all generated objects and all EEW meta data to PROD system like described in this document and adjust it. Test whether the transport was successful with report OXT_METADATA_CHECK.
  • Destroy the DEV system like planned by your IT management.
  • Build a new DEV system if necessary by copying the PROD system. The new DEV system will contain the generated objects and the EEW metadata, so you do not need transports from PROD to DEV.
  • Set the original system of all generated EEW objects to the new DEV system. Set EEWC data correctly like described above. Run Report OXT_AFTER_IMPORT for each extension (although you did not transport in this case). Also run report OXT_METADATA_CHECK for each extension to check whether it's correct.

Riscs and problems

The transport process described above is intended for complete moves of a system landscape, e.g. due to upgrade or changing to support mode. Distributed development will very probably lead to problems.

To avoid this, you should consider the following things:

  • Do not have a particular extension (or develop it) in several systems or clients.
  • If extensions are transported "by accident" (e.g. by client copy), you might remove all EEW metadata of a client by a report provided by SAP support.
  • In general do not develop extensions with EEW in several systems/clients transporting to the same target system. Reason: extensions might exist using the same technical names for generated objects leading to clashes in the target system.

So if all extensions of a source system are correctly moved, and the source system remains an active development system, all EEW metadata should be removed from it. Ask SAP support for further information. This avoids errors by working in two systems in parallel. Take care that this step is not reversible and affects all extensions, transported or not.

In any case, do not continue to work with EEW extensions in the source system after a transport.






CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 7480 Date: 20240531 Time: 113230     sap01-206 ( 128 ms )