SmartChange Daily/Weekly Import Scheduling (/RTC/TM_DAY_SCH)

Overview

The customizing table /RTC/TM_DAY_SCH enables daily and weekly import scheduling for SAP Transport Management. It allows you to control on which weekday imports are executed for specific projects and transport levels.

This provides fine-grained control over when transports are imported into specific SAP system landscapes, enabling scenarios such as restricting production imports to weekends or separating project import windows across the week.

Important: Once any entry is made in this table, imports will only be executed according to the defined schedule. All projects and transport levels must be fully maintained — any project or target path not listed in the table will not receive imports.

Table fields

WEEKDAY

The day of the week on which the import should be executed.

Value	Day
1	Monday (Mo.)
2	Tuesday (Di.)
3	Wednesday (Mi.)
4	Thursday (Do.)
5	Friday (Fr.)
6	Saturday (Sa.)
7	Sunday (So.)

LEVEL_NAME

The name of the TM transport level for which the import rule applies.

Examples: Development, Quality, Production

PJ_NAME

The name of the TM project for which the import rule applies.

Examples: Project A, Project B, Project C

Use case example

In this example, three projects (Project A, Project B, Project C) are maintained across three transport levels (Development, Quality, Production).

Scenario:

Monday through Saturday (Days 1–6): Imports to Production are executed only for Project A (not on Sunday).
Sunday only (Day 7): Imports to Production are executed for Project B and Project C.
Development and Quality imports run for all three projects every day of the week.

Resulting table entries

The highlighted rows show the Production-level entries. On days 1–6, only Project A is imported to Production. On day 7 (Sunday), Project B and Project C are imported to Production instead.

WEEKDAY	LEVEL_NAME	PJ_NAME
1	Development	Project A
1	Development	Project B
1	Development	Project C
1	Quality	Project A
1	Quality	Project B
1	Quality	Project C
1	Production	Project A
2	Development	Project A
2	Development	Project B
2	Development	Project C
2	Quality	Project A
2	Quality	Project B
2	Quality	Project C
2	Production	Project A
3	Development	Project A
3	Development	Project B
3	Development	Project C
3	Quality	Project A
3	Quality	Project B
3	Quality	Project C
3	Production	Project A
4	Development	Project A
4	Development	Project B
4	Development	Project C
4	Quality	Project A
4	Quality	Project B
4	Quality	Project C
4	Production	Project A
5	Development	Project A
5	Development	Project B
5	Development	Project C
5	Quality	Project A
5	Quality	Project B
5	Quality	Project C
5	Production	Project A
6	Development	Project A
6	Development	Project B
6	Development	Project C
6	Quality	Project A
6	Quality	Project B
6	Quality	Project C
6	Production	Project A
7	Development	Project A
7	Development	Project B
7	Development	Project C
7	Quality	Project A
7	Quality	Project B
7	Quality	Project C
7	Production	Project B
7	Production	Project C

Best practices

Maintain all combinations: Once you add any entry to the table, you must define entries for every project and transport level you want active. Missing combinations will not be imported.
Multiple imports per day: The table controls which days imports may occur — it does not restrict the number of import runs per day. If the import job runs multiple times on a given day, it will execute for all matching entries.
Use with existing import jobs: This table works in conjunction with your existing scheduled import jobs (e.g. /RTC/TM_IMPORT_SYSTEM_QUEUE). The table adds a weekday filter on top of the regular import logic.
Testing: After initial setup, verify the schedule by checking import logs across multiple days to confirm that imports are only executing for the expected project/level/day combinations.

Related resources

/RTC/TM_DAY_SCH — Internal table documentation: https://rtcom.atlassian.net/wiki/spaces/TEAM/pages/312311861/Tabellen#%2FRTC%2FTM_DAY_SCH

How to schedule Daily/Weekly Imports for specific Projects/Levels (/RTC/TM_DAY_SCH)