Which scheduled job to which process chain on SM37

Hi all ,
I'm checking scheduled jobs on SM37 screen. I see many BI_PROCESS_TRIGGER jobs scheduled and realesed . But I don't know which process chain is the owner of these jobs. Does anyone knows how to check whic job belongs to which process chain ?
Thanks in advance

Hi,
By using BI_PROCESS_TRIGGER job we can find the chain name..
Below is the procedure..
1.Double click on the job BI_PROCESS_TRIGGER
2.Then goto "STEP"
3. In "STEP"---goto 'GOTO' tab in the MENU....select "maiatain variants"
Then it will take to SE38 screen---Click the DISPLAY
It will give the Chain name and all the details.
If u have any doubts plz let me know...
i think this will clear...
Mohan

Similar Messages

Run/Schedule HANA Procedure via Process Chain or Similar - BW on HANA

Hello Experts,
We have BW 7.4 on HANA database(rev 74). We are working on mixed scenario approach.
We have few of the stored procedure in HANA. We want to schedule it.
Is there any way to schedule it via BW process chain or any similar thing?
Thanks in advance.
Regards
Rakesh

Hi Rakesh,
there is already a nice blog post which describes one way to integrate your stored procedures in a process chain: How to schedule SAP HANA procedures by using SAP BW Process Chains
As Lars said. If you do not need the process chain integration you can use the XS Jobs: Scheduling XS Jobs - SAP HANA Developer Guide for SAP HANA Studio - SAP Library
Best regards,
Florian

How to check the scheduled process chain in SM37

Hi Experts,
Can anyone tell me how do I check whether my process chain has been scheduled or not.
I checked in sm37 all the jobs that are under released status. Im getting about 10 jobs.
I dont know which one is belogs to my process chain as they do not have the process chain names.
Can anyone please let me know how do I confirm whether one of the released jobs below to my process chain.
Thanks in advance.

Hi,
To find this out, in sm37, select the job and click on step button in toolbar. You would find the program name RSPROCESS.
Click on this job and then go to menu bar and select goto-> variant.
In the variant, you can see the process chain that has been used for this job.

Can not delete job for BW process chain.

I can't kill or cancel this job.
this job status keeping "Killing" during 2 days.
sub-job was completed.
How can I force delete this job?
Job 29006 - CCMS job BI_PROCESS_ODSACTIVAT (GBD/100) Actions
Description CCMS job BI_PROCESS_ODSACTIVAT (GBD/100)
Job Id 29006
Parent Job 29005 - BW Process X0DMMB52_ACTIVATE (GBD/100)
Definition SAP_CcmsJob
Comment This job represents a monitored SAP batch job. The SAP batch job runs under control of the SAP batch system.
Owner Subject Redwood System
Status Killing
Files
Name Size
log 23895 Details u2026
Queue GBD_Queue
Process Server GBD_ProcessServer
Forced Process Server GBD_ProcessServer
Priority 50
Start time Requested: Sep 12, 1:43:19 PM, Actual: Sep 12, 1:43:19 PM (0:00:00:000 difference)
Requested Start Time Type User Set
Next Submit Base Time Sep 12, 1:43:19 PM
Scheduled Start Sep 12, 1:43:19 PM
Run time Sep 12, 1:43:19 PM - Sep 12, 1:43:43 PM (0:00:24 elapsed)
Remote Information
Remote System SAP GBD 100
Remote Status Finished
Remote Id J/RFCUSER/BI_PROCESS_ODSACTIVAT/13430000
Remote Event RSPROCESS
Remote Creation Time Sep 12, 1:43:00 PM
Remote Run Start Sep 12, 1:43:19 PM
Remote Run End Sep 12, 1:43:43 PM
Parameters
Job Definition Parameter In Value Out Value
JOBNAME BI_PROCESS_ODSACTIVAT Details u2026
JOBCOUNT 13430000 Details u2026
CLIENT 100 Details u2026
SAP_USER_NAME RFCUSER Details u2026
SHOWLOG Y Details u2026
SHOWSPOOL Y Details u2026
DELETE_JOB N Details u2026
Creation Time Sep 12, 1:44:01 PM
Last Modification Time 9:48:41 PM
Edited by: Park Jeonghwan on Sep 19, 2008 3:02 PM

Hi Park,
From what you describe I am assuming that the you had a BW Process Chain running from CPS and then decided to kill it. This autoamtically created a child job that's supposed to stop the Process Chan in SAP that should have, once complete, updated the parent job from it's 'Killing' status to 'Killed'. Now you find that the BW Process Chain in SAP is/was stopped, the CPS child job has also completed and yet your Process Chain job in CPS still has a 'killing' status. Because it is stuck in this status you cannot do anything with it, i.e. none of the scheduling options in the Redwood Explorer are active.
Assuming the above interpretation is correct then you probably have only one option and that is to force an update in the Repository itself. I also assume you're using either v6.x or v7.x.
To confirm the status of the current job in preparation for the update you can do the following query in the Redwood Shell when logged in as SYSJCS:
select status from rws_job$ where job# = <the job number of the job currently in a 'killing' status>;
This should return 1 row and the value for status should be 'G'.
To update the status you can use the following command from the Redwood Shell when logged in as SYSJCS:
update rws_job$ set status = 'K' where job# = <the job number of the job currently in a 'killing' status>;
To confirm your update was successful before finally committing use the first query again..
select status from rws_job$ where job# = <the job number of the job which previously was in a 'killing' status>;
This should return 1 row and the value for status should be 'K'.
You can now commit the change or rollback if you've made a mistake
commit;
Normally it is not recommended that CPS users modify any of the underlying tables so you may want to check with support that they are ok with you executing this command.
You may also want to check that you have the latest Service Pack for CPS as this may mitigate this kind of issue from appearing again.
Regards,
Simon

Jobs in a Process Chain

Hi All,
I have a scenario where 5 jobs needs to be executed one after the other in a PC.
3 are getting executed correctly. 4th job is failing and due to this PC is shows failed status.
If i restart the Process chain. I dont want the first 3 jobs to execute again. It should start with 4th job .
Do i need to goto SM37 and cancell the first 3 jobs after scheduling the PC or is it something to do with Proces type maintenece?
Regards
Satish

Hi,
Iam wondering why you wnat to start the process chain all over again. If your first 3 steps have run successfully, and your 4th step faield for some reason, you can just fix the issue and then continure the process chain from there as provided by the above link.
If that is what you want and all the processes are IP's then you need to create a IP group and then re reun the IP group by de selecting the first 3 IP's to run the 4th onwards.
Regards,
Srini

Error related to scheduling of dependencies in process chain

Hi gurus,
2 process chain is dependent on the 1 process chain,unfortunately i was scheduled the 2 pc before the end of 1 pc.
after a while i was realiased that 1 pc was still running,immediately i killed the job related to 2 pc(that job is DELETE INDEXES )
finally i was rescheduled the 2 process chain after the completion of 1 process chain.
1 & 2 are finished successfully.
thx
mahi &naren
because of this ,is there any problem to database (production server )

Mahesh,
every body will cancel jobs. It won't problem. may be you are thinking in that process is DELETE INDEXES point of view, this won't be problem. create the indexes again. after the load check DB02 for missing indexes.
check the data consistency for the load(no duplicate recrods).
All the best.
Regards,
Nagesh Ganisetti.

ABAP process job ( BI_PROCESS_ABAP ) in process chain running for long time

Dear Experts,
We have an ABAP process job BI_PROCESS_ABAP in a process chain. This job is running for a very long time than previous run time.
Recently we had an ORACLE database upgrade from 9.2 to 10g.
From the very next day , we are having this problem.
And also previously this process-chain was under control of BASIS guys . they were using a tool called CRONACLE to schedule it. At the time of upgrade this tool was crashed and they asked us to schedule it in BW system instead.
Underlying program is using two custom tables.
one is having both primary & secondary indexes but the other table is having only primary index.
I am not sure whether we have secondary indexes on other table prior to upgrade or not.
Where must be the problem?...
At the time of upgrade BASIS has re-organized the table space along with database upgrade.
please help me...
Regards,
SRIKANTH

Please ask yr basis consultant to check the system parms.
Below i have listed down SAP recommneded system parms .
abap/heap_area_total 4000000000
abap/heap_area_dia 2000000000
abap/heap_area_nondia 2000000000
Also check in SM37 if any other jobs are running for long time, peventing the your job running.
Check the SM12 for locks or SM58

Can I run job PROGRAMs in process chain under my user-id?

Hi! I have a following problem. When schedule PROCESS CHAIN, then all JOBs are created with my user-id, but programs in STEPs are running with default system user-id (in our case - it's BWADM).
Is it possible to make a setup that programs (i.e. steps) in particular process chain will be running with my user id, not system user id?
The issue is that system-id BWADM has not all my authorizations, so cannot get proper results out of my process chain.
Thank you!
Vitaliy
http://www.hp.com/go/sap -> BI

Hi,
You need to save those jobs while logged in as your user id. Example, in Infopackage, save it then it will contain your user id. When that infopackage is executed, then it will have your user id.

Scheduling a part of process chain

Hi!
I have a process chain that is a combination of local chains.
The main chain is running daily, but now I want to run the latest local chain weekly only.
Any hints how to get it working by this way?

If you are on BI 7.0 and say if you want to run your local chain on a friday only then :-
You can use a decision maker process type (process type is called as "Decision between multiple alternatives") and use a formulae with boolean return like
"DATE_WEEKDAY1( Current Date ) = 5" inside this decison maker process to check whether the current day was a friday
based on the output you would have multiple options i.e. to link the flow to your local chain in case of option 1 (value true being rturned by the boolean formulae) or option 2 (Value false being returned by the bollean formulae"

What are process types in process chain

hi any one tell me what are process types in Process chains

Hi,
In the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
1. Choose the Process Chain Maintenance pushbutton and create a process variant.
2. Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
3. Confirm your entries.
The Add Start Process dialog window appears.
4. Create a variant for a start process.
1. a. On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
2. b. If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
3. c. Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
5. Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
6. When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process Function Information
Maintain Variants With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message You can also send messages to an application process of the chain, depending on the success or failure of the process.
1. 1. From the context menu of a process, create an additional process variant of the Send Message type.
2. 2. If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3. 3. You arrive at a window, in which you can select an existing process variant or create a new one.
4. 4. If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5. 5. Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process You use this function to remove a process from a process chain.
Manage Data Target You use this function in connection with the following types of process variants
1. constructing indexes
2. deleting indexes
3. constructing database statistics
4. rolling up filled aggregates
5. compressing InfoCubes
6. activating ODS object data
to call up the administration for each of the data targets.
7. Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
8. If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
9. Under Attributes ®Display Components assign a display component to the process chain.
10. Maintain additional process chain attributes if necessary.
11. Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
12. Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.
Hope it helps.
Regards,
Amith

Steps for Creating Process chain!

Hi All,
I want to create process chain which can schedule IP and run the concern job to fill infocubes/ODS?Can someone please guide me stepwise how to proceed.Some sort of doc will eb appreciated.

Hi,
   You can either create a process chain directly in the process chain maintenance screen, or by using a maintenance dialog for a process
Creating a Process Chain Directly in the Process Chain Maintenance Screen
In the BW Administrator Workbench
1.      Choose the Process Chain Maintenance icon from the AWB toolbar.
2.      Choose Create.
3.      Enter the technical name and a description of the chain, and confirm your entry.
   4.      Create a variant for a start process.
       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
       If you choose to schedule the chain directly, enter the start date value for a chain under Change Selections and save your entries.
       Save your entries, go back to the previous screen and confirm your entries in the Add Start Process dialog box.
The Plan View of the process chain maintenance screen appears.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
       5.      Use Drag&Drop or double-click to add the relevant processes to your process chain.
Choose Process Types to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
               If you insert a process into the chain that is linked to additional processes by default, the respective process variants are generated and automatically inserted into the process chain. These variants are suggestions and can be changed, replaced or removed from the chain as required. Variant maintenance is called when the change run performs automatic insert.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, go back to the previous screen and confirm your entries in the Add Start Process dialog box.
The Plan View of the process chain maintenance screen appears.
               The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
                  If the process that you used to create a chain is linked to additional processes by default, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain as required. Variant maintenance is called when the change run performs automatic insert.
                  Choose Process Types to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and   Data Targets navigation trees.
        When you add a process, you need to select a process variant or create a new variant. For collection processes, the system uniquely determines the variants.
        Various functions for editing the process are available from the context menu
Maintain variants With the exception of the variants in the collection processes OR and EXOR, you can use this function to change all process variants.
Exchange variants
You can exchange the variants for an existing variant or a variant that is to be created.
    You can use this function to link a process to a successor process. You can choose from the processes that are not yet linked to the current process. They are grouped according to process type in submenus.
      Display scheduled jobs
Once the process chain is active, you can use this function to display the jobs that have been scheduled.
       After at least one process chain run, you can display all of the scheduled jobs for a specific process and all of the jobs with which this process was run. The Job Overview appears and you can call the relevant job log.
Create message
    You can also send messages to an application process of the chain, depending on the success or failure of the process.
1.       To do this, using the context menu for a process, create another process variant of type Send Message.
2.       If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3.       A dialog box appears, in which you can select an existing process variant or create a new one.
4.       If you create a new process variant, edit the document that is going to be sent and maintain a list of recipients.
5.       Save your process variant and go back.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log are also sent.
Only use this function to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process in the debugger by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove process
You use this function to remove a process from a process chain.
Manage data target
You use this function to call the data target administration for the following types of process variants:
         Construct index
         Delete index
         Construct database statistics
         Roll up filled aggregates
         Compress InfoCube
         Activate DataStore object data
       7.      Hold down the left mouse button to connect the processes with events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link. To do this, select the link and right-click with the mouse.
       8.      If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully, or whether you want the event to be triggered independently of the outcome of the process that precedes it. If the process that triggers the event has more than one option, choose the option after which the successor process is to be run
       9.      Assign a display component to the process chain using Attributes
     10.      Maintain additional process chain attributes if necessary.
     11.      Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
During the check, the system calculates the number of parallel processes according to the structure of the chain . The result is compared with the number of background processes on the chosen server (or the total of all available servers if no server is specified in the attributes of the process chain). If the number of parallel processes is greater than the number of available background processes, the system highlights every level of the process chain where the number of processes is too high. The system produces a warning for these levels.
   12.      Save your process chain if it does not contain any errors.
You can activate and schedule your process chain. After scheduling, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after scheduling. In the Log View, you can display the reports for the chain runs.
If ie helps assign points

Details about Process chain

Details about Process chain

Hi Vijay,
            Well the major components of Process chain is mentioned as under:-
A process Chain is a sequence of processes in BI system that executes in the Background.
Commonly Used Process Types
1. Start
2. Execute InfoPackage
3. DTP
4. Attribute Change Run
5. Save Hierarchy
6. Delete Index
7. Generate Index
8. Activate DSO data
9. Update DSO data
10. Complete Deletion of Data Target Content
11. Delete Entire Content of Linked Transactional DSO/ODS
12. Initial Fill of New Aggregates
13. Roll up of Filled Aggregates/BIA indexes
14. Compression of InfoCubes
15. Read PSA and Update Data Target
16. AND
17. OR
18. XOR
If you want to include a load process in the process chain, you need to have already created an InfoPackage.
You cannot load flat file data from a client workstation in the background. For this reason, you have stored your data on an application server.
Creating Process Chains
You have the option of creating a process chain in the process chain maintenance screen directly or by using a maintenance dialog for a process:
Creating a Process Chain Directly in the Process Chain Maintenance Screen
You are in the BW Administrator Workbench.
       1.      Click on the Process Chain Maintenance icon in the AWB toolbar.
The Process Chain Selection dialog window appears.
       2.      Choose Create.
       3.      Enter the technical name and a description of the chain, and confirm your entry.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
       5.      Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
       1.      Choose the Process Chain Maintenance pushbutton and create a process variant.
       2.      Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
       3.      Confirm your entries.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
       5.      Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
       6.      When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process
Function Information
Maintain Variants
With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants
You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs
Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs
After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message
You can also send messages to an application process of the chain, depending on the success or failure of the process.
1.       From the context menu of a process, create an additional process variant of the Send Message type.
2.       If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3.       You arrive at a window, in which you can select an existing process variant or create a new one.
4.       If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5.       Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process
You use this function to remove a process from a process chain.
Manage Data Target
You use this function in connection with the following types of process variants
·         constructing indexes
·         deleting indexes
·         constructing database statistics
·         rolling up filled aggregates
·         compressing InfoCubes
·         activating ODS object data
to call up the administration for each of the data targets.
       7.      Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
       8.      If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
       9.      Under Attributes ®Display Components assign a display component to the process chain.
   10.      Maintain additional process chain attributes if necessary.
   11.      Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
   12.      Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.

Two buttons "Activate" and "Activate and Schedul" in Process Chain

What are the functionalities of the two picture buttons "Activate" and "Activate and Schedule" in process chain. In which case the "Activate" button should be used and in which case, the "Activate and Schedule" button should be used? If we click the Start variant of a process chain, then click "Change Selections" button which bring up the window "Start Time" where the buttons "Immediate", "Date/Time", "After job", and "After event" are listed at the top. If we modify at any of the above buttons, then after save this modification, we will have to click "Activate and Schedule" button to make it work, right?
Thanks a lot and everyone's idea is greatly appreciated!

Hi Kevin,
Simply activating ur PC wont trigger ur PC. U have to use the other option Activate and Schedule then only the process chain trigger as per the scheduled option.
U can give the Date/Time option and if it is a periodic job then u can specify the periodicity, later save all the things and when u come back to RSPC screen then click the 'Activate and Schedule' Button which looks like a clock.
When u do this then ur process chain will be in released status.
When ever if u activate ur chain will be with the Green color it means that its in Active status. But if u choose the second button then only ur chain will gets trigger..
Regards-
MM
Assign points if it helps
Message was edited by: vishnuC

Background Jobs - Process Chains

Hello,
I want to schedule a background job for a process chain so that it triggers the process type and start executing...
Can anyone please let me know how i can do it?

HI,
The background control options are available to directly schedule the start process. You can start the process chain immediately (when activating the process chain), at a specified time, or after a particular event. When you activate the process chain the start process is scheduled in the background, as defined in your selections.
If there are not sufficient options available, you can trigger the start of the process chain using API. You can use the SAP NetWeaver Scheduling Framework to start the chain and to have more extensive scheduling options.
You can also trigger the start of a process chain using a metachain. A metachain is a process chain, for which you determine this start condition, that is fixed to another process chain. The process chain is started directly by this metachain.
Tarak

Scheduling process chain 3 specific times a day

Hi ,
my requirement is to schedule a process chain 3 times a day.
i have gone through the forum and got the solution EVENTS.
please provide me how to do this in detail like step by step.
how to create a event in SM64 and how we will define the time there.
and creating a ZPROGRAM with the function module (please provide step bystep).
thanks
Sridhar

You create user events in SM62. In SM62, next to "User even names", click on Maintain and press Enter. Click on the Create icon to create a new event (let's call it ZEVENT).
Next, in your process chain, change the Start variant to be scheduled "After event", and put in ZEVENT for the event name. Also, click on the "Periodic job" at the bottom. This will automatically reschedule the jobs for the process chain after it executes.
Next, create an ABAP program (let's call it Z_EVENT_RAISE) to call the function module BP_EVENT_RAISE. You're code can look like this:
REPORT Z_EVENT_RAISE.
PARAMETERS: P_EVENT LIKE TBTCO-EVENTID.
CALL FUNCTION 'BP_EVENT_RAISE'
EXPORTING
EVENTID = P_EVENT.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
This ABAP program will prompt for an event name, so you will need to create a variant (let's call it ZEVENT) which will save the value of the event name (also ZEVENT). You will need the variant name to be able to trigger the event in a batch job.
Now all you need is the batch job. Use tcode SM36 to create a batch job where you call the ABAP program (Z_EVENT_RAISE) using the variant (ZEVENT).
Note, SM64 only triggers an event manually.
Does this help?
Oh, and you can copy this job to schedule it three times a day.
Message was edited by:
Geo

Which scheduled job to which process chain on SM37

Similar Messages

Maybe you are looking for