Modifiying, Transporting and Scheduling Process Chain

Question

Hello ALL,
i have to create a new process chain for a delta Load and put this process chain in a big existing Meta Chain, after i have to transport to Quality System.
if i control the difference between Dev and Quality system to have an idea i see that the Infopackages in Dev have the execution tab: Load Data Immediately without job: BI_BTCH
in Quality some Infopackages have execution tab: run successively in batch with job like this:
BI_BTCH LX6CW08S1ICM04I4O06KOPL
can you tell me please in detail how should i complete this activity:
- wich type of control should i do before creating and modifiying process chain in DEV and Quality
- how should i do to control in Quality the scheduling of a process chain
- if i modify a process chain in DEV and after i will transport in Quality what will be the affect in Scheduling, the scheduling will be the same without problem or i have to schedule again
- in generale how can i schedule a process chain, wich transaction and how in detail
Thanks a lot for your help
Bilal

Answer 1

Hi Bilal,
1) EVENT: When you want to have a process chain 'A' to be started after completion of a process chain 'B' or any process in process chain 'B' we can use this event.  These two chains can also be from different BI systems.  Like Chain 'A' could be from one production system and Chain 'B' could be from different production system.  As soon as the chain A finished an event will be triggered and this event will trigger the chain B.  The start time of chain B might differ because it depends on the completion of chain A. To schedule a process chain using an event, Go to Tcode: RSPC look for your chain. Switch to change mode. Right click on the start variant and select maintain variant. Click on "change selections. click on "after event," give the event name in the slot and select the periodic job.
2) RUN JOB PERIODICALLY: When you want to have the chain run for more than once periodically we select this option.  Suppose, chain B has to run after completion of chain A periodically we have to use this option.  If you do not check this option, your chain B will run only once when the event is triggered after completion of Chain A.  From the next time onwards, it not run even the event is triggered.
3) JOB: For every process when it runs a job will be created assainging it to a work process in the system.  Similarly, when the chain starts a job will be created containing the log of the run.  Also, in the scheduling options of a process chain, you can have your process chain started after completion of a particular job in the system (ex: an attribute change).  For this, Go to Tcode: RSPC look for your chain. Switch to change mode. Right click on the start variant and select maintain variant. Click on "change selections. click on "after job" give the job name in the slot and save the settings.
4) SCHEDULING PROCESS CHAIN: Means to make settings to a process chain so that it will run on a periodic basis at a certain time.  If you want to start a chain immediately, you will choose the option immediately and trigger it.  It will run for only once.  But, if you want to have your chain run everyday at 7:00 am in the morning, you have to schedule it using the scheduling options as below:
In Tcode: RSPC look for your chain. Switch to change mode. Right click on the start variant and select maintain variant. Click on "change selections." Click on Date/Time button. Give the start date and time in the Scheduled Start slots. (Ex: 09-04-2009, 7:00, to have the chain run at 7:00 everyday starting from tomorrow). Tick the check box Periodic job in the bottom and click on "periodic values" button and select the option as daily and save it. Then click on "Restrictions" button to specify the factory calander. The Tcode for calander is SCAL, where you can see all the factory calanders in the system and you can choose that suits your requirement. Save the changes and navigate back to process chain maintaince screen and click on "Schedule" button.
Now your chain is automated for trigger