Live Import Scenarios

We know that imports to live systems is a critical step for many companies.

Out of the box, Safe TMS provides different scenarios to execute imports to live systems.


Scenario: Single user does everything

In this scenario, you want a single user to execute all the transport steps (including live import).

Configuration

YTSAFETMS_SAPSY:

  • ACTION_BUILDER_CLASS needs to be YCL_SAFETMS_ACTION_BUILDER_TAR for the live system (and probably other target systems, such as QA)
  • (Optionally) empty the field FDG_EXPIRE_HOURS, as this field won't be used at all.

YTSAFETMS_FDGREC: (Optionally) delete all records here, as the entries here won't be used at all.

YTSAFETMS_SYDEF: (Optionally) empty the field FDG_DEL_AFTER_DAYS, as this field won't be used at all.

Usage

Transport process is initiated and executed over YSAFETMS001 or YSAFETMS002 by a single user.


Scenario: Live transport delegation

In this scenario, your regular users will initiate the transport, check for dependencies, do the QA import. However, live import (and steps after) will be executed by another user; probably from the basis team.

Configuration

YTSAFETMS_SAPSY:

  • ACTION_BUILDER_CLASS needs to be YCL_SAFETMS_ACTION_BUILDER_FDG for the live system, and YCL_SAFETMS_ACTION_BUILDER_TAR for other target systems (such as QA)
  • FDG_EXPIRE_HOURS should contain a value in hours; in which a live transport demand will be obsolete. If you don't want the demands to expire, leave this field empty.

YTSAFETMS_FDGREC: (Optionally) enter the users which should be notified for live import demands.

YTSAFETMS_SYDEF: (Optionally) enter a value into the field FDG_DEL_AFTER_DAYS. Completed live import demands will be deleted from Safe TMS tables after so many days. Leave empty if you want to keep the records forever.

Usage

Users can use YSAFETMS001 or YSAFETMS002 freely (as authorized) for development / test systems.

When a transport request is about to be transported to the live system, it doesn't get transported immediately. Instead; the demand is stored in Y* tables, and delegatees in YTSAFETMS_FDGREC get an e-mail notification. (Exception: If the transporter is already a delegatee, he/she can transport via YSAFETMS001 immediately.)

Delegatees enter YSAFETMS008 and see the list of demands. They select the demands they want to process, and execute live transport step & any step after that.

Safe TMS automatically include an additional automatic step for delegatees to mark the demand as completed so it doesn't appear in YSAFETMS008 again.


Hints

If you have custom actions, they should be in harmony with your live import scenario. If you ever change your live import scenario, it is recommended that you test your custom actions with the new scenario.