"Type of processing step WHM"

Hi everybody,
I would like to analyze the loading process from DataSource       to infoprovider.
With the table RSDDSTATWHM I found a very useful table. It is presenting me for every request how long certain "WHM steps" took.
I was also able to get information about the single steps listed:
900       Total Process
010       Processing in the Source System
011      Data Transmission .....
BUT i don't really understand what these single steps mean because the titles are so "unspecific".
I would like to now which number is representing exactly what kind of time span.
For example somewhere stood the "900" is exclusive of waiting periods, but what is included?
Is there anybody who knows exactly what the numbers mean?
Maybe somebody found a graphical representation of the single time spans.
Hopefully somebody can help me here.
Cheers
Mark
Edited by: Mark Moeller on Feb 7, 2008 5:01 PM

Similar Messages

Use of Execution Type in Workflow process step.

Hi Kiran,
The Execution Type is relevant for the process step of the workflow.
MDM workflow steps can be assigned either to one or more users or to one or more roles, as follows:
u2022 Users. User-based assignments allow you to explicitly specify which user or users should be responsible for performing the step.
u2022 Roles. Role-based assignments allow you to specify roles rather than users, with the actual users determined by MDM at runtime.
The Execution Type defines the relation between these assigned users/ roles if there are more than one:
1. All Concurrent- All assignees must perform the step. Each assignee can do so at the same time.
2. All Sequential Random- All assignees must perform the step. Each assignee can do so one at a time in any order.
3. All Sequential Ordered- All assignees must perform the step. Each assignee can do so one at a time in the order listed in the step.
1. Any Single- Any single assignee can perform the step. The step can be pushed to or pulled by any assignee.
You can also find this documented in the Data Manager Reference Guide under MDM Workflows-> Execution Type (page 292)
Regards,
Hedda Cohen.

_Thanks Hedda_

Assignment of Step type and CR step for MDG_S

Hi
This is in continuaton for thread MDG_S workflow.
I original issue which is for MDGS when I assigned WS543000005 to CR type and sumitted CR goes no where,
As as per SWEL it shows No Reciver Found enen though GET_AGENT table is maintained.
In another system I found that WS531000044 is assigned ti CR Type Then I tested it and found that CR creates Work Items also upto final processing.
as per below
Before CR Submission : CR status is 02: Changes to be executed
After CR Submission : CR status is 01:To be considered and Approved
After CR Reviewer approves : CR status is 09: Dependant Data to be processed /Approved
After Purchase reviewer Finalize processing :CR status is 09: Dependant Data to be processed /Approved
After Finainace reviewer Finalixe processing :CR status is 09: Dependant Data to be processed /Approved
Now I can not see CR any where even though CR step 04 and 04 assigned to my user ID
I have some questions as Description in Define Change Request Steps is not Mataching with description in GET_AGENT desesion table.
Also it is observed that step 80 is not assigned to WS531000044 in IMG node Define Change Request Steps but it can be seen in GET_AGENT decesion table and step no 06 and 07 does not appears in GET_AGENT decesion table ( In edit mode).
Can you explain from where assignment of CR steps to CR type in desion table are taken ino accout ?
Why description is not matched for steps under IMG and in decesion table?
Can you explain me releationship between CR step and step type,CR Status and where they \maintained in IMG and how proceeses modelling is diffenent t for determination of Next CR step in case of WS531000044 ?

Please keep in mind that "hard-wired" workflow templates are just that: hard-wired. This means that a specific workflow template (for example WS53100044) will always have the same number of steps, each step will always have the same type and number, agents will always be assigned in the same way, and those can't be altered by configurations. To understand each workflow template's behavior, you can either open that template in transaction PFTC or SWDD, or alternatively, read the exact behavior in SAP Help documentation. You basically need to google the workflow template number and you should be able to find the description of each template's behavior (by the way, the number you type has an extra zero so if you can't find a match on Google, you will know why ).
Now, the assignment of CR steps to CR type is done in the workflow template itself and NOT in the decision table. See the first screenshot:
The step number above "should" correspond to what is in the configuration table (for readability and consistency of documentation purposes). However, if for some reason, it does not, the hard-coded value is the value that will actually be considered. So, in technical terms, the assignment of step numbers in MDGIMG has no influence on how the workflow template will behave. Again, the main purpose is for the corresponding description in the step number configuration table to show on the CR window.
The other thing is the step type. A step type purpose is mainly to indicate what set of buttons will show at the top of the CR window. The fact that step types are represented by numbers confuse a lot of people with step numbers. I would have personally preferred if step types were a 2-char field so that a clear distinction can be made between step types and step numbers. In any case, buttons on the CR correspond to actions and you can see in MDGIMG that you can assign step types to actions. SAP delivers a pre-defined set of step types and associated actions. Those must NOT be altered because they could break the standard workflow templates. However, you can create your own custom step types and link them with as many actions (standard or custom actions) as you like. But again, you can't assign those custom step types to hard-wired workflow templates. You can only use them in your custom workflow templates or in the rule-based workflow.
Now, the question is how does the hard-wired workflow know what step type to use. The answer is easy: you can either find that in the SAP Help documentation or in the workflow template definition in transaction SWDD. For the above screenshot, the step type is 2. You can find that if you double-click the task ID TS75707980 (or display it using transaction PFTC) and look in the "Cntainer" tab. In this case, this task will ALWAYS have type 2. Other tasks are assigned different step types or are more dynamic in the sense that they expect the step type to be passed from the main workflow template calling them. For example TS53200002 will always have type 7, TS60808005 will always have type 5, and TS60807954 accepts the step type dynamically. This last one is the one used in the rule-based workflow (hence it has to read the step type configured in the decision table).
I hope this answers you question. You definitely need some level of workflow design/build knowledge in order to be able to completely understand all of this. Hopefully, this gives you a good starting point.

Handling unit process step by step

Dear All,
We intend to use handling unit functionality.
Our FG let's say FG001 gets packed in container.
I have mapped this as following.
I have created 'Container' as code with material type VERP- Packaging Material. Maintained the required data in Sales org. tab page.
I have created packing instruction in POP1 with container as packing material & FG001 as material.
I have maintained the determination record in POF1 (Frankly I didn't understand the relevance of this step, but did cos has been suggested in several threads.)
Now I have to perform the packing process of FG001 in HU02.
But system is throwing me an error as 'No packing instruction could be found for material FG001', message no. VHUPD002.
I have stuck up there. Kind request you to help me in this, regarding any configuration & processing step, if I am missing.
Also I am few questions to get clear.
1. How to maintain the batch no. of packing material 'Container' while creating/ generating HU as my packing material is batch managed, and need to have information in which HU the batch of packing material is utilized.
2. What happens to the stock statement (MMBE)of both the materials i.e. FG001 & Container when those are get packed i.e. HU created/ generated.
Please respond urgently.
Timely answers will be rewarded.
Mimiri

VS,
Thanks once again.
You got it right. I was confused as I was unable to understand why packing material is not moving along with the FG material.
Moreover our packing material is container. Once it is packed container moves from plant to plant & then to final destination.
As we have to track the movement of the container, it was necessary for us to the have stock statement.
I am still surprised why standard SAP doesn't support the movement of the packing material along with the contents i.e. FG?
Now to tackle this, we have thought of a way out.
We have maintained two material codes for container. one is dummy container and second is main container for which we have to track the goods movement. Both will be having same material type as VERP but only difference is later won't be having packing material type in sales view. So it will act as normal material.
While creating HU with HU02, both the materials with quantities will be entered in pack material section. Dummy packing material serve as packing material. Here my question is what is HU creation & HU generation? Because system is throwing me an error while generation as 'no packing instruction are there for the material although I have defined determination source in POF1 but when I save the HU with out generating it, system doesn't throw this error
The HU is getting created but I am unable to enter that HU number in VL01N while creating the delivery. How to do that?
MImiri

Post Processing Steps after Support Package Stack Application

I'm curious if anyone has any guidelines for post processing steps (or pre-processing) when applying Support Package Stacks to their Development Infrastructure (Developmend Workplace and the Central NWDI Server). We have just upgraded a couple of developers local engines and developer studio to SP stack 19 from SP stack 14 and are experiencing some problems. We also applied the J2EE stack and appropriate SCA files to the NWDI server.
After the support packs it looks like our DTR files are gone (when reimporting configuration via Developer Studio the SC's are there but there are no DC's inside of them). Additionally, it looks like we have to manually reimport the newest versions of SAP_BUILDT, SAP_JTECHS, and SAP-JEE. Another thing is that old Local Web Dynpro DC's are now complaining about class path problems and different versions of files. We followed the documentation for applying SP19 exactly as the documentation says for a Java Development Usage type. Is there a checklist or something that anyone has for steps to perform after the application of the support packs?

I think I'm missing something. Now I see the code and DC's inside the DTR. However, when I try to import into NWDS no DC's come in (the software components exist, but no DC's in them). Additionally, the CBS web ui reports that my software components do not contain any DC's even though I see them in the DTR. What things can I look at to determine what I'm missing here?
Thought I'd add some more info..after applying the support packs, we imported the new SAPBUILD, SAP_JTECH, and SAP_jee SCA'S into our track as we required some functionality from the newer build SCA. We also reimported our old archives back into the system by manually checking them in assuming this would fix the problem with us not seeing the source in the NWDS or the DTR. After the import, the CBS no longer sees our custom DC's, but the DTR does (both in active and inactive ws). When importing the dev configuration into the NWDS our custom DC's no longer appear, but SAP's standard SCA's do.
Message was edited by:
Eric Vota

No repeat option available for the process step in process chain

If the process chain failed at the ODS activation level, generally the repeat option will be available for activation and to continue the next step. But in some cases the repeat option will not be available for the process step.
Is there any process to get the repeat option in the process chain?

You can change this in RSPC > Settings > Maintain process types > Loading (or process of your interest) > put the check mark for Repeatable.

Sequence of process types in process chains

Hi all,
Can any one help me in listing down the sequence of process types we must have when we are using process chains. Like If I am loading data from R/3 to ODS and to cube then what all things should be included (creating indexex, deleting indexes..)and most importantly what sequence they should be in. ?
Also what are the types you need to include in master data load process chain, where does the change run fit in the process chain.?
Thanks alot in advance,

Hi KM,
The steps would be as follows:
1. Start Process
2. Load any master data - attributes.
3. Change run .
4. Text load.
5. Load the ODS.
6. Activation of ODS data.
7. Delete indexes of Cube.
8. Further processingof ODS data to Cube.
9. Create indexes.
10. Refresh Statistics.
The delete index can be after the "further processing step" also.
Bye
Dinesh

DataPackage1:arrived in BW, Processing 2nd processing step not yet finished

Hi BI-experts!
I would like to load e.g. transaction data from SAP ECC system into SAP BI system.
The Loading process is hanging in processing step u201CSERVICE APIu201D.
The process in hanging in status "yellow" and then changed after a while to status u201Credu201D.
[0FI_AR_4 |http://www.file-upload.net/view-1447743/0FI_AR_4.jpg.html ]
The following steps within Load process are yellow and then red:
Extraction (messages): Missing messages
Missing message: Request received
Missing message: Number of sent records
Missing message: Selection completed
Transfer (IDocs and TRFC): Missing messages or warnings
Request IDoc : Application document posted (is green)
Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished
Info IDoc 1 : sent, not arrived ; Data passed to port OK
Info IDoc 2 : sent, not arrived ; Data passed to port OK
Info IDoc 3 : sent, not arrived ; Data passed to port OK
Info IDoc 4 : sent, not arrived ; Data passed to port OK
Subseq. processing (messages) : Missing messages
Missing message: Subseq. processing completed
DataStore Activation (Change Log) : not yet activated
Question:
Can some one tell me whether my distribution model or other settings are wrong?
I created 2 distribution model (BD64), one from SAP BW system and other from SAP BI system with message types RSRQST, RSINFO, RSSEND
Thank you very much!
Holger

Hi!
Many thanks for your response.
The tcode WE05 on source system showing the following:
Inbox IDoc's: RSQRST (amount: 1)
Outbound IDoc's: RSINFO (amount: 4)
When I go to SAP BW System (tcode WE05) i cannot detect any Inbound IDOC's of message type RSINFO.
What is wrong in my configuration?
Thank you very much!

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

GP-The next process step still continue when current step has terminated

Hi,
I'm using CE7.1 SP3. I have created a business process flow using the Guided Procedure. Each step in the process is done by different role.
I have an approval step in the process. When the user clicks approve, the next step will get executed. When the user clicks reject, the whole process should be terminated. However during testing, it is found that the next step can still be executed even though a rejection is specified. The process is not ended.
I have specified in GP that if reject is selected, it should go to terminal state.
Can anyone help?
Thanks.
Regards,
Fui Voon

Hi James, Hi Maarten,
I also tested this step property in TestStand 2.0.1. and as result of my tests I can say the followings:
- If you set the CancelCurrentExecution property from a defined PreSubstep for a step type, than the step is not further executed (e.g. behaves normal)
- If you set the CancelCurrentExecution property from any other place (e.g. engine callbacks, sequencefile callbacks, post substep aso), then the step is executed normally (e.g. behaves abnormal)
The attached sequence file contains a modified MessagePopup step which has an additional PreSubstep that will set the Step.CancelCurrentExecution to the value of the Step.CancelExecution step sub-property.
When this sub-property is set to TRUE then
the message window is not shown anymore.
James, you're right, and Maarten, if you need this functionality for a limited set of steps then you can use this feature as a PreSubstep too.
Regards,
Silvius
Silvius Iancu
Attachments:
Example.seq ‏24 KB

Survey Suite process steps

Hi
Can you post the process steps involved in configuring survey suite.
Thx

Hi ,
The below are the steps for the Survey Suite process .
> Open transaction CRM_SURVEY_SUITE
> Left side you get to see the Application Areas like Leads , Opportuities , Activities , Marketing , Contract , Examples etc.... Click on the Application that you would like to create the Survey .
> You get to see the Popup displayed on your screen . Enter the name of your Survey .
Then you get the Popup saying 'Survey does not exist new Templete will be created ' .
The control will be taken to new screen .
> Left side of the screen the first option you see is the 'Title of the Survey ' . Right hand side screen you can type the Survey Title and Save it .
> The option you find ' Maintain Text and Attributes ' . Right Click on this and select ' Insert Question ' .
> Right hand side you need to fill the ' Attributes for the Question ' like
Question Text and the Rating Factor .
> Right Click on the ' Question ' and select the ' Insert Answer ' option . And Right hand side you get the different Answer types and select accordingly and also enter the Rating Factor .
This is the procedure to create the Survey Questionnire . And based on the Rating Factor qualification of the Survey depends .
Hope it helps you in the Survey Creation process .
Regards,
Nagaraju D

CKMLCPAVR there is no any process steps in Processing tab

Hi,
I would like to execute CKMLCPAVR. My SAP version is ECC6.3 and no this transaction in menu tree but I still can type the transaction code to execute it.
My problem is that there is no any process steps show out in Processing tab after I gave the plant and settings.
I can't execute these steps such as CKMLCP, My posting period is 10/2011, and initial period is 01/2011.
Could you tell me my version is too old? So the CKMLCPAVR can't work, or not?
thank you very much.

I have activated the EA-FIN and CKMLCPAVR has been shown up at menu tree but the process steps are still empty.
I choosed the posting period 10/2011 and initial period 01/2011 and checked Posting Run, Revaluate Consumption, Relevant for Costing, Provisional Price = L price for the last cumulation period, Price = Actual price for the period, Legal = 0.
After I set up all these parameter, I turned to the Process Tab and found there is no any prcess steps in this tab.
Do you know what happen?

Solar01 - manual process steps

Hello,
We have some manual process steps defined in solar01. As transaction codes are not available for them, what is normally done for manual processes under transaction tab in solar01
Are they left blank under transaction tab in solar01 or how manual process steps are taken care in solman - where ?
Thanks.
Anirudh,

It sounds like you created created a logical component called Z_Manual_Step for product type Z_Manual_Step and added this logical component to your project and assigned it to the manual steps in the business process structure.
They won't have an SAP transaction, however, they may involve a web site address, which can be added to the transactions tab.
They are really there to document the process better for anyone that looks at the system. You can load documentation, track status, assign responsibility, etc.. to the manual step.
regards,
Jason

How to repeat sucessfull process step

I want execute an abap program program again to make the next process step to be sucessfull, how can i do that.
when i right click--process monitor on sucessfull process step i am getting set status to red, yellow, if i select yellow
will it run again

Hi,
Method when it fails in a step/request
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
How is it possible to restart a process chain at a failed step/request?
Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
Of course you can also set the state of a specific step in the chain to any other possible value like 'R' = ended with errors, 'F' = finished, 'X' = cancelled ....
Check out the value help on field rspcprocesslog-state in transaction se16 for the possible values.
You can try this to change the status of the predecessor process to R or X so that repeat is available for the successor step.
Thanks,
JituK
Edited by: Jitu Krishna on Apr 25, 2008 7:11 PM

Solar01 - Business Scenarios/Process/Process steps out of alignment

Hello Folks,
We have a situation where the business process that are now in BPH in Solar01 in Solman should have been business scenario
and same with process step should be process.... Is there any quick way to fix that like going into tables and fixing the
data? If so, Can you please let me know what are the tables in which the Business scenarios, processes and steps or the hierarchy is stored?
Or is there any other way to fix this?
Appreciate your kind response.
Cheers,
Venky

Hi Venky,
Unfortunately, there is no way to do it, because the nodes have different types, and it would be like trying to transform one thing in other totally different. You can only recreate the hierarchy manually.
kind regards,
Fabricius

"Type of processing step WHM"

Similar Messages

Maybe you are looking for