Versions Compared

Old Version 2

changes.mady.by.user Felicity Borrelli

Saved on

compared with

New Version 3

changes.mady.by.user Felicity Borrelli

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The CTS+

...

The export is handled in CTS+ using the “loose coupling” approachintegration in MediationZone uses a "loose coupling" approach for handling exports. This means you first perform the export as usual in the source system, then manually make it that the export process is performed within MediationZone, and then the exported file is manually made available to CTS+ for transport and import into target systems.

  1. Verify Export Compatability: Ensure that your the export can be imported into other systems :by verifying that the export source system’s name must be added to the import system’s ‘System Property’, is included in the target system's mz.sourcesystems. Please system property. For more information, refer to https://infozone.atlassian.net/wiki/x/8BVCD

  2. Create your the System Export: Use the System Export UI or command line interface commandstools like mxsh or mzcli to generate the export file in MediationZone.

  3. Make the System Export available to CTS+: See Once the export file is created, follow the steps outlined in the SAP CTS+ documentation at on thehttps://help.sap.com/ for more information. Once the export to upload the file to CTS+. After it is made available to CTS+, it the export can be used for importing imported into target systems via the CTS+ API.

Note!
When setting up your configurations and system exports, remember keep in mind that the entire export content of an export will be imported into the target system. Therefore To ensure smooth integration we recommend the following:

  • Use External References when configuring variables that are local for a system, see for system-specific variables. This ensures configurations are valid for both the source and target systems, with only the External References being system-specific. For more details, refer to https://infozone.atlassian.net/wiki/x/7AozD. This way, configurations will be valid for both source and target systems, and only the External References will be system-specific.Restrict the exports to contain

  • Limit your exports to include only the use cases you want intend to import into other systems.