Ansicht
Dokumentation
/TMWFLOW/SCHEDULE_IMPORT - Program /TMWFLOW/SM36_IMPORT
RFUMSV00 - Advance Return for Tax on Sales/Purchases ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Purpose
You can use this report to schedule imports of transport requests into managed systems, using specified intervals. The generated job triggers an import into a specified system of the task list that you define on the selection screen.
Integration
This report complements the import scheduling function in the task list whose shortest interval for scheduling is daily. You can use this report to schedule imports more frequently, for example, every hour or every 15 minutes.
The import triggered by this report is logged in the task list, like the imports triggered by the standard import scheduling function.
Prerequisites
Features
Selection
Standard Variants
Output
Activities
- On the selection screen, enter the following data:
- The task list which you want to use to trigger the import. This can be the task list of an implementation project, a maintenance project, or any other project type.
- The system and the client into which the transport requests are to be imported. They must be in the task list.
- If the target system occurs more than once in the task list, specify the development system and client of the track, to ensure the correct calculation of the system/task in the task list.
- Select the applicable import options:
- Select for Later Import: The requests remain in the import queue after the import and can be imported, for example, into another client. This is only useful if you have not switched on extended transport control, but you want to provide several clients with requests.
- Overwrite Originals: The transport control program also imports objects if the objects are the originals in the target system. The object directory entry determines the SAP system where the original version of an object is located.
- Overwrite Unconfirmed Repairs: The transport control program also imports objects if they were repaired in the target system and the repair is not yet confirmed.
- Ignore Predecessor Relations: You can choose this option if you want to import all the requests for one or several projects, but additional requests from other projects exist for which there are dependencies. This option is switched off by default, which means the predecessor's relationships are checked before the import. The import only occurs if the predecessor's relationships will not be damaged.
- Ignore Component Versions: This import option means that transport requests can be imported even if their component version does not match the current component version (including Support Package Level) of the system. This is the case if the component version of the system is either new (the Support Package Level is higher than that of the export system) or too old (you first have to have imported the Support Packages before you can import the request). You should only use this option if you are sure that the content of the transport request is independent from the component version.
- Choose Saveto save your settings as a variant for a job to be scheduled regularly.
- In transaction SM36, schedule the job for your variant.
Notes:
- The time interval should not be less than 15 minutes. If you schedule jobs more frequently, the task list log will contain a lot of import log entries, which makes it difficult to find specific entries in case of errors.
- If you need to schedule multiple imports (for example, for several test systems), you can define one job containing multiple steps which are executed using multiple variants. By doing so, you do not have to schedule, maintain and document multiple jobs at the same time.
- To create new task lists or complete an existing one, you should modify the existing jobs.
Example
Fill RESBD Structure from EBP Component Structure BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 4797 Date: 20240423 Time: 140146 sap01-206 ( 87 ms )
