Launch Process Chain in dialog mode using WAD

Hi,
I check that I can associate the process chain launch using a button in WAD. Does someone know if there is a way to launch this in dialog and NOT in batch mode? My main issue is that I'd like to know who launch this process chain, and in batch mode the user is BIWREMOTE.
I tried to change the flag "wait till the end" available with the EXECUTE_PROCESS_CHAIN action, but I see no changes.
Thanks a lot!

Hi,
A way around this would be to change the execution user of the Process Chain to be the user who clicks the WAD Button. This can be achieved in RSPC by selecting the process chain, then Process Chain -> Attributes -> Execution User.
This gives you the option of either the default BW Background user (BIWREMOTE), Current User or Special User. If you select Current User it will show the user you are after. However, you will need to ensure that whoever is clicking the button has the relevant authorisations to execute process chains in BW otherwise the job will fail.
Regards,
Nick

Similar Messages

Start InfoPackage in dialog mode using BAPI

Hi all,
I need to start an InfoPackage in the dialog mode using ABAP coding report. The InfoPackage has to load data from a csv-file from the Client-Substation, therefore it can be started only in dialog mode (Start Data Load Immediately is chosen in Schedule tab).
I use BAPI_IPAK_START functional module for this purpose. But I receive an error An upload from the client workstation in the background is not possible, and a message InfoPackage ZPAK_EUSCSC3BAGELE4JAI3HRM5PHJ could not be started by Bapi_ipak_start.
It seems that BAPI_IPAK_START tries to start InfoPackage in the background, regardless of choosing Start Data Load Immediately option.
It is possible to start InfoPackage in the dialog using BAPI?
Thank you.

Your problem is, that an Infopackage can only use local files, while it is attached to a running dialog. It has to access your local disc to get the data. If you want to use the Infopackage in a process chain you have to transfer your file to a location where the application server has access. The BAPI_IPAK_START just starts the Infopackage. It does not know where your local environment is, so it cannot find your local disc and cannot access the file.
You have to options:
1. Use your local file and start the infopackage by hand. No automation possible.
2. Put the file somewhere where you can find it via transaction AL11. Then you can access this file without trouble.
Kind regards,
Jürgen

How to create process chains,and how to use process like and or xor

Hi,
How to create process chains,and how to use process like and or xor.
can any one please give me a example in each.
Thanks,
cheta.

Hi Cheta,
Here is step by step procedure to create process chains
Process chain is nothing but executing a process ..(or) loading the data any process we can do in background.. that means.. automatically we can execute our process based on Time or any event..
Creating Process Chains
Prerequisites
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.
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.
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.
Hope this helps
Regards
Karthik

Trigger Process chains through ABAP program using selection screens

Hi All
I am loading flat files through process chains. My requirment is such that i need to create a ABAP selection screen so that user can load the flat file from his PC. when the user is loading the flat file i have to copy the file onto the application server folder and then display him the monitor errors/warnings (if any). when my data load is complete i need to archive the file with time stamp onto the application server folder.
Please help me in this regard....
thanks and regards
sairam phani

Hi sairam
can you check this link hope this might help you out
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
Going thru your query hope i get the right solution
Thanks=points in SDN
Sanjeev kumar hamsala

Which Process Chain or DATA Source uses Queue MCEX02

Hi plz tell me which pc or data source uses Queue name - MCEX02,MCEX04,MCEX05,MCEX05_1,MCEX08,MCEX11,MCEX12,MCEX13,
Actually these queues entries are blocked in ECC Environment.
Also provide any document on running jobs thorough LBWE.
Thanks
Nilesh

Hi,
MCEX02,MCEX04,MCEX05,MCEX05_1,MCEX08,MCEX11,MCEX12,MCEX13 these are the extract structure names of the datasource for the applicaitons Sales, Billing, Delivery, Purchasing....etc.
If you goto LBWE based on the application component number you can find the datasouurces like 11, 12, 13 are for sales, delivery, billing repectively.
Check the below link for LO extraction process steps.
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Hope this helps.
Veerendra.

How to Update Infoobject Masterdata using Process Chain

Hello,
I am trying to update the Master Data in Infoobjects (text and Attr) by using Process chain.
The steps used are
1. Delete data from PSA
2. Execute Infopackage
3. Execute DTP for Attr
4. Run Attr Change
5. Execute DTP for TEXT
While updating Text, I am receiving error for duplicate entry.
I am trying understand the correct process to update Infoobject Master Data in BI7 (SCM5/5.1). Please adivse.
Thanks,
Sanju

HI Narendra,
In process chain functions, you can use the process type with the name Trigger Event Data Change (for BEx Broadcaster)
The above process type must be used to determine which InfoProviders should be checked for data changes. You can specify multiple InfoProviders within this process type either directly (by simply entering the names of the InfoProviders) or indirectly by specifying the name of the variant based on one of the following process types:
Execute InfoPackage (LOADING)
Activate DataStore Object Data
Update DataStore Object Data (Further Updating)
Read PSA and Update Data Target
Hope this helps
Regards,
Sathya

How to execute process chains using planning function

hi, i need to execute process chains from web. i know the steps to that needs to be followed for accomplishing the task.
1) RSPC_CHAIN_START ( function module) into which process chain has to be passed
2) create a planning function to invoke the said function module
3) create a function button on web and assign the planning function.
Now the thing is how to create the planning function in BPS. plz provide me a solution with steps. And how to pass the process chain into the function module and handle it.
Thnaks

Hi Anand
RSPC_CHAIN_START is the standard function module to run a process chain which i want use. Now, how to use the said FM in planning function to achive my task. Do i need to maintain any parameter in planning function inorder to execute the FM. If you know the solution plz explain in detail.
I am very new to BPS..bare me plz
Thank you

Interview questions in process chain

hi
cany any one send me possible interview questions in process chain and errors with answer.
thanks in advance
pradeep

Hi Pradeep
1.Procedure for repeat delta?
You need to make the request status to Red in monitor screen and then delete it from ODS/Cube. Then when you open infopackage again, system will prompt you for repeat delta.
also.....
Goto RSA7->F2->Update Mode--->Delta Repetation
Delta repeation is done based on type of upload you are carrying on.
1. if you are loading masterdata then most of the time you will change the QM status to red and then repeat the delta for the repeat of delta. the delta is allowed only if you make the changes.
and some times you need to do the RnD if the repeat of delta is not allowed even after the qm status id made to red. here you have to change the QM status to red.
If this is not the case, the source system and therefore also the extractor, have not yet received any information regarding the last delta and you must set the request to GREEN in the monitor using a QM action.
The system then requests a delta again since the last delta request has not yet occurred for the extractor.
Afterwards, you must reset the old request that you previously set to GREEN to RED since it was incorrect and it would otherwise be requested as a data target by an ODS.
Caution: If the termianted request was a REPEAT request itself, always set this to RED so that the system tries to carry out a repeat again.
To determine whether a delta or a repeat are to be requested, the system ONLY uses the status of the monitor.
It is irrelevant whether the request is updated in a data target somewhere.
When activating requests in an ODS, the system checks delta repeat requests for completeness and the correct sequence.
Each green delta/repeat request in the monitor that came from the same DataSource/source system combination must be updated in the ODS before activation, which means that in this case, you must set them back to RED in the monitor using a QM action when using the solution described above.
If the source of the data is a DataMart, it is not just the DELTARNR field that is relevant (in the roosprmsc table in the system in which the source DataMart is, which is usually your BW system since it is a Myself extraction in this case), rather the status of the request tabstrip control is relevant as well.
Therefore, after the last delta request has terminated, go to the administration of your data source and check whether the DataMart indicator is set for the request that you wanted to update last.
If this is NOT the case, you must NOT request a repeat since the system would also retransfer the data of the last delta but one.
This means, you must NOT start a delta InfoPackage which then would request a repeat because the monitor is still RED. For information about how to correct this problem, refer to the following section.
For more information about this, see also Note 873401.
Proceed as follows:
Delete the rest of this request from ALL updated data targets, set the terminated request to GREEN IN THE MONITOR and request a new DELTA.
Only if the DataMart indicator is set does the system carry out a repeat correctly and transfers only this data again.
This means, that only in this case can you leave the monitor status as it is and restart the delta InfoPackage. Then this creates a repeat request
In addition, you can generally also reset the DATAMART indicator and then work using a delta request after you have set the incorrect request to GREEN in the monitor.
Simply start the delta InfoPackage after you have reset the DATAMART indicator AND after you have set the last request that was terminated to GREEN in the monitor.
After the delta request has been carried out successfully, remember to reset the old incorrect request to RED since otherwise the problems mentioned above will occur when you activate the data in a target ODS.
What is process chain and how you used it?
A) Process chains are tool available in BW for Automation of upload of master data and transaction data while taking care of dependency between each processes.
B) In one of our scenario we wanted to upload wholesale price infoobject which will have wholesale price for all the material. Then we wanted to load transaction data. While loading transaction data to populate wholesale price, there was a look up in the update rule on this InfoObject masterdata table. This dependency of first uploading masterdata and then uploading transaction data was done through the process chain.
What is process chain and how you used it?
A) We have used process chains to automate the delta loading process. Once you are finished with your design and testing you can automate the processes listed in RSPC. I have a real time example in the attachment.
for more detail
Collecting Process Chain Statistics
/thread/235805 [original link is broken]
Advice regarding process chains
creation of process chains
Message was edited by:
Kalpana M

Reg. process chains

Hi
Will any one send step by step to do process chain. I am getting stuck in middle.
Please help.
Thanks.
regards
Sridhar
[email protected]

Hi Sridhar,
What exactly you mean by saying "to do process chain". If you want to know the steps to create a process chain, here are the guidelines:
In the BW Administrator Workbench:
 1. Choose the Process Chain Maintenance icon from the AWB toolbar.
The Process Chain Selection dialog box appears.
 2. Choose Create.
 3. Enter the technical name and a description of the chain, and confirm your entry.
The Add Start Process dialog box 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, 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.
Note: 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.
You can turn this system response off using Settings Default Chains.
5. Use Drag&Drop or a double-click to insert any additional relevant processes into 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.
6. 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:
7. Hold down the left mouse button to connect the processes with events.
Note: 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 -> Display Components.
 10. Maintain additional process chain attributes if necessary.
 11. Check your process chain in the Check View and make any necessary corrections.
Note: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 (subchains are recursively taken into account here). 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.
Result:
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.

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

Errors transporting process chains

Hi,
we got some problems while transporting process chains.
The error occurs in the method execution. The transport log says:
Start of the after-import method for object type R3TR RSPC (Activation Mode).
Version 'M' of chain <name of the chain> was saved without checking.
0 Chains Were Selected.
Message no. RSPC031
Specifying process chain ID <name of the chain>, type V2&', and variant '' has resulted in the selection of 0 process chains. The selection has been called without confirmation by the user. This means that the user was unable to make a selection.
The function is terminated.
There is probably an error in the program. Look for corresponding notes.
We can't find any notes for this error message. The whole thing is confusing, because sometimes we find the chain in the target system, sometimes not.
Has anybody experiences with this kind of problem and how to solve it?
Thanks.
Knut

Hi,
Did you make sure that you transported all the process variants that the chain is using?
Please, check that by going to transport connection and transporting your process chain.
We always use that method to transport process chains: first getting all variants from the chain on transport connection and putting them on a transport request. Second establishing the start time of the PC and finally activating and scheduling the PC. You then release and transport that order.
Which version is your system? 3.0B?
Regards,
David.
Message was edited by: David Sirvent

Modifiying, Transporting and Scheduling Process Chain

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

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

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.

InfoSpoke and Process Chain

Hi Everybody,
I would like to create my first Process chain..
I would like to start the loading in a InfoCube ( InfoPackage )and after that when this loading ready is I want to export its Information in a File on the application Server (InfoSpoke)....
Does somebody can help me in achieving this first sample..
Thanks
FedeX

Hi Fedex,
Process chain docs:
1. Using Process Chains in SAP BW (pdf)
https://websmp207.sap-ag.de/~sapidb/011000358700000402012004
2. Operating BW 3.0 using Process Chains (ppt)
https://websmp207.sap-ag.de/~sapidb/011000358700001670182002
3. Modelling aspects in process chains - Transcript (doc)
https://websmp207.sap-ag.de/~sapidb/011000358700002459342003
4. Modelling aspects in process chains (ppt)
https://websmp207.sap-ag.de/~sapidb/011000358700002337702003
5. How to... Integrate an ABAP program into a process chain 3.x (pdf)
https://websmp207.sap-ag.de/~sapidb/011000358700002895002003
Hope it Helps
Srini

Process Chain changing start time?

hi guysm i have 76 process chains that run every day in BWD system, so i removed all the timings from the start variant and in the infopackages, but it seems some process chains are still running, i did do the following steps on chnaging the time from a particular time to immediate, Save, Check and activate, i didnt schedule it as i dont want it to load right away .
do i have to hit check , save , schedule once i change the time from a particular time to immediate load or activate will work as well.?
what else could be the cause of process chains still loading even there are no events, or time given to any process chains at all.
i went to sm 37 and i can see the bi process are all running at the time they were orignially set up on.
so any suggestions would help,
is there any way from sm 37 i can tell which process chain is triggered off?
thanks
Dante(devils never cry)

Dante, the start conditions on the infopackages do not affect when they run in process chains. The process chains have their own start job. If you want to change the start time of a process chain, then you need to go to maintain the process chain, right-click on the Start process and select Displaying Scheduled Job(s)... . Here you will see a job called BI_PROCESS_TRIGGER. Change the start conditions of this job.
The start job for all process chains is BI_PROCESS_TRIGGER, so using SM37 may be difficult to identify which BI_PROCESS_TRIGGER job is associated to a particular chain.
Also, to let you know, each process in a process chain has an associated job. All jobs called BI_PROCESS_xxxxx are jobs associated with a process chain.
Eg.
BI_PROCESS_LOADING is an infopackage.
BI_PROCESS_TRIGGER is the start job
Does this help?

Launch Process Chain in dialog mode using WAD

Similar Messages

Maybe you are looking for