Overview of SM50
Hi Friends,
Could u provide me with a complete overview of the T-Code SM50..I mean the technicality behind it and how to analyse the schedules from it.
The T-code SM50 gives process overview.
Steps to know which is our work process by PID
1) Double click on the process-->go to Backg Tab-->click on Batch monitor-->double click on the job name-->click on Job details In which the last column would show the WP number/PID-->Copy the PID and search for your job in sm50, It gives pid no, and other details.
2) Using that pid no Go to process option and select cancel with core(IF you want to kill the JOB)
DIA - Work process for executing dialog steps in user transactions
UPD - Update process for executing update requests
ENQ - Process for executing enqueue requests
BTC - Process for executing batch requests
SPO - Process for executing spool requests
UP2 - Process for executing V2 update requests
Assign points if useful
Similar Messages
-
Dear all,
Our DB Instance always run very slowly and update process
responding time is very long during month end.
I think this maybe due to it runs the database and application.
So I want to delete the DB Instance from Logon Group, and then users
will just access other else three Dialog Instances, is it Ok or what
impact will have ?
How to check PI system connected to SAP ECC Logon Group's IP , but not only
connected to the DB Instance ?
Users always need run many Background Jobs at the day,but I heard other
company almost only allow users run Background Jobs at the night.
Generally, how many background jobs running on one Instance is normal?
Do we have any good ways to control or limit users' background job
setting at the day ?
The dialog and update process numbers of DB Instance are respectively 80 and 6(Update & Update2) , other Dialog Instance is 50:4(Batch:Update)
How is the general ratio between dialog and update process numbers ?
what's the difference between update and update2 process ?
Thanks,
MichaelHi Michael,
Your company basis team searching why SAP system run slowly.
But don't have your company basis team check your system transactions.
ST01 - Operating system monitor
ST02 - Tune Summary
ST04 - SQL Server performance analysis
SM21 - System Log
SM50 - Process Overview
SM13 - Update Requests.
SM12 - Lock Entries
Maybe long time background working process see u overview tcode SM50 and SM12 kill procees after system speed normaly.
Regards.
Cem ATES -
Short dump while executing info package in 3.5 data flow?
Hi,
i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
Please find attached short dump.
ThanksHi,
When you load transaction data I think there is a deadlock.
Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
The program SAPLSENA is the lock handler tool.
Also check if ACR is running on this target while your load is happening.
Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
Try reloading after deleting the locks manually.
Regards. -
Taking more time for job execution
Hi experts,
there is one job executing on daily.
generally it takes around 5 min.
but yesterday it took 50 min.
can anybody tell why it is happened on that particular dayhi,
u cannot tell exactly y it happened.
it depends on several reasons like
1. the server may be down
2. the data may be large
also somtimes even the data is same the time taken will be different.it depends on the load on work process also.if workprocess is free it may finish quickly or it may delay.
u can check workprocess overview in sm50.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Jun 12, 2008 4:12 PM -
Hello All,
I configured scenario which use SOAP as sender and XI Adpter as receiver.
It is syncrnous call. I can see different message status...
intiatially it came as black triangle --> scheduled for outbound processing.
Now, It is showing Green flag which is just sceduled......
What is wrong and how to troubleshoot further....
Thanks,
SriniSee below SAP Note 1118297:
Liang
=====Note 1118297===========
Symptom
You are using the Exchange Infrastructure and you are processing asynchronous messages. These messages are scheduled in queues that are no longer processed. The inbound queue of the qRFC Monitor (transaction SMQ2), for example, contains entries with the status "Running". However, you recognize in the process overview (transaction SM50) that there is no active work process.
Other terms
QRFC, SXMS_ASYNC_EXEC, inbound, running, resource
Reason and Prerequisites
You are using the Exchange Infrastructure and you are processing asynchronous messages. These message are scheduled in the QRFC and are only processed slowly or not at all.
Solution
The asynchronous messages are scheduled in the queues.
Check the following points of your middleware.
Queue configuration:
If the QRFC Inbound Scheduler is configured, see Note
369007.qRFC: Configuration for the QIN Scheduler
Are the XI queues registered and active? In transaction SXMB_ADMIN->Administration->Manage Queues, you can register the queues for the XI runtime.
If the resources are configured for TRFC/QRFC, note the common usage of system resources. For further details, see Notes
74141 Resource management for tRFC and aRFC
527481 tRFC or qRFC calls are not processed
For the qRFC resources see Note
1051445 qRFC scheduler does not use all available
resources
For further information see Unit 3.1 of the "SAP Exchange Infrastructure Tuning Guide", which you can download from the marketplace.
In the XI configuration you can set locks for the processing of XI messages. Note that for many parallel queues there are also sufficient resources for lock objects. At least one enqueue entry is required for each queue, depending on the configuration. For further information see Notes
552289 FAQ: Lock management R/3
654328 Enqueue: System log message GE9
Queue status:
Transaction SMQ2 contains queue entries with the following status
"Running"
If the J2EE engine is downloaded in production mode with the mapping engine or recipient Adapter Framework, processing QRFC entries may not recognize this and remain in the "Running" status. A symptom can be, for example, that the RFC destination "AI_RUNTIME_JCOSERVER" is no longer registered. You can find this information in the Gateway Monitor (transaction SMGW).
Otherwise, the system may reach this status if the application server is downloaded in a controlled manner, and long-running processes can no longer terminate.
The system no longer processes any message. In transaction SMQR, you can activate the queues manually again. You can also schedule the report RSQIWKEX, which automatically restarts the queues. For further information see Notes
620633 Status RUNNING in SMQ2 with XI queues
864333 RSQOWKEX & RSQIWKEX start Running(Executed) queues
"Sysfail"
A queue entry with the status "Sysfail" can have two possible causes.
1. Further processing cannot be carried out on the process for technical reasons (for example, the program terminates with a dump or a system (mapping or recipient system cannot be reached).
2. Queue processing should be stopped, as the message cannot be processed, due to a configuration error. Processing is not permitted for the subsequent messages, as the queue sequence displays the message sequence. You can use the report RSXMB_RESTART_MESSAGES to restart the message processing again. See Note
813029 Automatic processing of failed XI messages
XI-QRFC and IDoc-TRFC processing:
Note that when you use the IDoc adapter this uses the RFC/TRFC resources, which are used together with the QRFC resources. This means an intensive usage of the TRFC can influence the performance of the XI queue message processing. When possible always use the package processing of the IDoc adapter (transport of several IDocs with an RFC call to the recipient system):
1. Package created from an IDoc XML payload with several IDocs
2. Packaging, package created with IDoc package filter
3. Package created with message packaging (queue message package)
(as of NW2004s)
For more information about acknowledgements, see also Note:
1111968 IDoc adapter: Parallel processing of acknowledgements
to reduce the number of acknowledgement queues.
Tuning Balancing parameter :
The BALANCING parameter activates the entries for the parameters B_EO_IN_PARALLEL_SENDER, B_EO_OUT_PARALLEL and B_EO_IN_PARALLEL.
They are used if the number of parallel queues is changed and the messages are distributed to the new queues. A balancing procedure is already used in the Standard System to distribute the messages equally to the queues. If the Balancing parameter is continually active, it has a negative impact on performance (as queue entries are constantly distributed between the queues and this means they cannot be processed). This can cause problems during queue processing.
Its use in the Tuning Guide is not described clearly.
Oracle database:
When using an Oracle database see Note
742950 Performance affected on Oracle DB with supplement 11
if you discover performance problems when processing queue entries. This improves the scheduling process only, and not the processing time of a queue entry.
See also Note
1020260 Delivering Oracle statistics
EO (exactly once) handling of XI-Messages when you restart QRFC entries:
The XI log guarantees the uniqueness of the transfer between the client and server. A restart does not trigger a double execution of messages. Note that a synchronization of the reorganization between client and server is guaranteed. The EO recognition is executed with the message ID. The retention time determines the amount of time this information is retained in the system for.
The individual messages are saved to the database in the system with a key from the message ID and version. This prevents a parallel execution of the same message. A queue entry can be executed in parallel using the report RSQIWKEX or by carrying out a manual start from the queue. We recommend to set the parameter LOCK_MESSAGE (default value is active "1") of the category "RUNTIME" in the XI configuration to the value '0'. More information is contained in Note
1058915 Outbound queue remains in status 'SYSFAIL'
=====End of Note 1118297=========== -
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 -
Dear All,
I am facing a problem while executing F110. The system posts some of the vendor and leave out other vendor e.g. if I have 500 line items, the system picks only 40 or 50 and the remaining is shown as running. When I check the status of the system in F110 it shows as Payment Run is running, Generated 40 Posted 40, but the total line item was 500.
When I check the Process Overview in SM50 it shows the program is running even after two days or one weak or more.
This type of error I am getting from the past 10 days.
If any one has an idea about this issue kindly share/suggest me, how to over come this issue.
We are in 4.6c.
Regards
Praveenhi,
You can check the following:
1.In parameters have you given all the vendors.
2.In Free selection have you given any coditions.
3.Are the other 450 Vendor line items blocked for payment.
4.In the parameters have you activated the logs.
5.When you run the proposal do you get all the 500 line items. if yes then check and log and you will know exactly which all line items are not selected for payment and why?
Award points if useful.
Rgds
Prasad -
Hi Gurus,
can anyone explain me in detail what is really a variant in process chains with any example if possible.
ThanksHi Apo,
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.
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.
Regards,
Yokesh. -
Hi All,
I need some help to interpret the below job log.
A considerable amount of time i.e. 4 hours is being spent in calling the customer enhancement EXIT_SAPLRSAP_001.
Previously this activity didnot consume such huge time.
We tried checking the TRFCs and short dumps also.
When we checked the process overview in sm50 - the sequential read was working fine.
Not able to interpret where exactly the time is being spent.
Appreciate your help on this.
Date Time Message
03.02.2011 02:20:58 Job started
03.02.2011 02:20:58 Step 001 started (program SBIE0001, variant &0000000010155, user ID BIRFC)
03.02.2011 02:20:58 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
03.02.2011 02:20:58 DATASOURCE = 0PA_ER_2
03.02.2011 02:20:58 RLOGSYS = BICLNT100
03.02.2011 02:20:58 REQUNR = REQU_EMKACN0684E0YS8255NDE5PWP
03.02.2011 02:20:58 UPDMODE = F
03.02.2011 02:20:58 LANGUAGES = *
03.02.2011 02:20:58 *************************************************************************
03.02.2011 02:20:58 * Current Values for Selected Profile Parameters *
03.02.2011 02:20:58 *************************************************************************
03.02.2011 02:20:58 * abap/heap_area_nondia......... 4000000000 *
03.02.2011 02:20:58 * abap/heap_area_total.......... 0 *
03.02.2011 02:20:58 * abap/heaplimit................ 40000000 *
03.02.2011 02:20:58 * zcsa/installed_languages...... DE *
03.02.2011 02:20:58 * zcsa/system_language.......... E *
03.02.2011 02:20:58 * ztta/max_memreq_MB............ 2047 *
03.02.2011 02:20:58 * ztta/roll_area................ 6500000 *
03.02.2011 02:20:58 * ztta/roll_extension........... 4000000000 *
03.02.2011 02:20:58 *************************************************************************
03.02.2011 06:32:26 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 439,405 records
03.02.2011 06:32:26 Result of customer enhancement: 439,405 records
03.02.2011 06:32:29 PSA=0 USING & STARTING SAPI SCHEDULER
03.02.2011 06:32:29 Asynchronous send of data package 1 in task 0002 (1 parallel tasks)
03.02.2011 06:32:35 IDOC: Info IDoc 2, IDoc No. 746127, Duration 00:00:00
03.02.2011 06:32:35 IDoc: Start = 03.02.2011 02:20:58, End = 03.02.2011 02:20:58
03.02.2011 06:32:36 Asynchronous transmission of info IDoc 3 in task 0003 (1 parallel tasks)
03.02.2011 06:32:36 IDOC: Info IDoc 3, IDoc No. 746133, Duration 00:00:00
03.02.2011 06:32:36 IDoc: Start = 03.02.2011 06:32:36, End = 03.02.2011 06:32:36
03.02.2011 06:34:31 tRFC: Data Package = 1, TID = 0AD3E46709EA4D4A4C030CEA, Duration = 00:01:37, ARFCSTATE =
03.02.2011 06:34:31 tRFC: Start = 03.02.2011 06:32:54, End = 03.02.2011 06:34:31
03.02.2011 06:34:31 Synchronized transmission of info IDoc 4 (0 parallel tasks)
03.02.2011 06:34:32 IDOC: Info IDoc 4, IDoc No. 746134, Duration 00:00:01
03.02.2011 06:34:32 IDoc: Start = 03.02.2011 06:34:31, End = 03.02.2011 06:34:32
03.02.2011 06:34:32 Job finished
Regards,
ShravaniActually this is just a job log. You need to provide code of your extractor extension / customer enhancement.
Better to do SQL trace in TA ST05 to see what SQL statement are the most contributing to bottleneck. -
Printer is not working spool processor shows error
Dear Experts,
Please solve my query, here one printer is not taking any print at sap level and the same printer takes the print at windows level
For that I checked in spad configuration but that configuration is ok
I did not get why its getting
Please solve me if you know about this
Regardshi Francisco Javier Hernanz
thanks for your adivce and just now i found Error in sm50 (processors overview)
in sm50 processors i found one error at opposite of one spool processor
i selected that error and display file and it opens trace data ( dev_w28) file
in that
ERROR => RFC-GUI: ThSendAndWait in read returned: 18 [abrfcsys.c 6920]
ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcsys.c : 6925
please give me solution if you know
regards -
Hi,
This is related to NW04 on AIX and Oracle 10.2.
I want to find out that how often the WP is restarting. It is based on either disp/wp_auto_restart or heaplimit parameter. The help.sap.com link as follows -
To determine how many work processes are restarted, use the Computing Center Management System (CCMS) (transaction RZ20). Note that the column Err in the Work Process Overview (transaction SM50) does not refer to work processes that are restarted.
I could not find it on RZ20 or RZ03.
Please let me know if anybody has an indea about it.
I will appreciate your help.
Thank you.
SumeHello Sume,
You will find information in the help page below:
http://help.sap.com/saphelp_nw2004s/helpdata/en/9c/f78b3ba19dfe47e10000000a11402f/frameset.htm
Please do following steps:
- Access transaction RZ20
- Expand the node SAP CCMS Monitor Templates
- Double-click on Entire System
- Expand the node <SID>
- Expand the R/3 Services node
- Expand the Work process type node that you want. For example: Dialog
- Expand the <instance name> node
There you will see the MTE EndedWpDIA.
Please check the help page for more information about each MTE.
Best regards,
Rafael Toshiaki -
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
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. -
Buffering of the table T429i table
Hello,
system: 4.6c
The mrp jobs are getting completed beyond the schedule.We are trying to get a better executuon time for these jobs.
Wanted to know if the buffering of this table T429i will help is is faster completion of these MRPs?
Thanks.
PrasannaDear,
MRP transactions the flag to buffer the table need to set to improve the performance.
table MDBT GRPGV.
In the process overview (Transaction SM50), you can see permanent accesses to program SAPLCOIT
Reason and Prerequisites performance
Type of the planning run: Net change or regenerative planning (intensive)
Planning mode: Reactivate or reset planning dates (intensive)
Planning horizon
lead time scheduling
Technical
Database
Buffering SAP number ranges
Please refer the OSS Note 23278 - MD01, MDBT: Performance during MRP run for details. and Note 204517 - MRP: Performance problems - typical causes
Regards,
R.Brahmankar -
Hi
I came across certain object ID's that keeps timing out under my agent inbox when being selected, either in edit or interact but it keeps timing out
Whe i view process overview in SM50, the time of this report CL_CRM_GENIL_DATA_CONTAINER===CP keeps running for over 360 to 400 seconds and eventually times out
Can someone please advise what is causing this performance optimization in the GenIL data container? How to improve or correct?
RaviHi Ravi,
Please consider the following SAP note:
Note 1055562 - Performance optimization in the GenIL data container
I hope it helps!
Kind Regards,
Gabriel Santana
Maybe you are looking for
-
I am wondering how to use a cfif statement to set the background color of a table cell based on the percentage number that is outputted from a db.
-
Stop it from using photo black ink for black text printing and where has the color ink gone?
My HP Photosmart Prem C310 series all in one is using the Black Photo ink cartridge for text printing instead of the XL Black that I put in it for text printing. How can I get it to use the right cartridge for printing? Also, even though I have NOT p
-
Hi All, I am writing a report (not a dynpro UI) using following code selection-screen begin of block b1 with frame title block1. select-options: swcv for p_string. select-options: namespce for p_string. selection-screen end of block b1. parameters: s
-
Hello, I got my self a new SSD and installed Lion in it from the internet. I tried copy pasting the itunes library from the most current backup in the TM drive that was used to backup the old hdd. I keep on getting "not enough permission" error for e
-
Hi guys, I will shortly have to copy an appset between two servers, and the data also. Please could someone give me a definitive list (Warning: newbie alert!) of what exactly I need to move? I know I need to backup the appset using Server Manager fro