Process in SM66

Hi,
I see BW process chain showing a process node in Yellow, SM37 for the same says job is finished.
I want to see corresponding job in R/3.
How to find the corresponding job in tcode SM66.

go to sm37, double click on your job and then choose job details; the next popup will give you all the info to find the corresponding process in sm66. however, if the job has finished you will not find any corresponding process. you might want to check SM58. maybe you have LUW stuck. if this is the case execute them manually. you can also check BD87 to see if any idoc is still in status 64. these idocs are hanging and need to be reprocessed.
M.

Similar Messages

How to find process in SM66

Hi,
I am searching process in SM66 which is corresponding to BW process.
But dont know how to find it, process id seems to be different in both BW and R/3.

With this SM37 I guess you mean that in BW system all jobs related to process chain have ended.
I don't think it's possible to tell on R3 side what job corresponds to BW process chains. You can try by name in SM37 or as you said in SM66/SM50 looking at background type work processes, but without information how process chain creates name of job on R3 side you won't be able to tell for sure. How job name is created is question rather to BW expert, not "ABAP Performance and Tuning".
Best regards
Marcin Cholewczuk

Process cancel question in sm66

HI gurus,
In tcode DB02, my mistake i pressed DBCC CheckDB button and the process started for database check.
i went to SM66 --> Edit --> Process --> Cancel --> without core.
it says process cancelled message.... but the process is still there and running from last 3 days..
can any body tell how to stop this?
what happens if i press SM66 --> Edit --> Process --> Cancel --> with Core?
or is there any method to stop this process?
any suggestions?
Giri

go to sm37, double click on your job and then choose job details; the next popup will give you all the info to find the corresponding process in sm66. however, if the job has finished you will not find any corresponding process. you might want to check SM58. maybe you have LUW stuck. if this is the case execute them manually. you can also check BD87 to see if any idoc is still in status 64. these idocs are hanging and need to be reprocessed.
M.

Debugging not possible in SM66 t-code

Dear All,
I created infinite loop in the program.
I executed the program in 2 ways:
1. Direct execute the program (SE38).
   I can see the process in SM66.
   I choose that record and click the debugging button, ABAP Debugger is come out and i can debug my code.
2. I call that program in background or from other system using RFC.
    I Can see the process in SM66.
    I choose that record and click the debugging button, it said ABAP debugger started.. but nothing come out and i can't debug my program.
Pls suggest why the 2nd way can't debug.
Best Regards,
Victor.

okay.
But is it possible to debug the program if the program is executed from other systems?
i'm not sure about this.but we may debug by just putting endless loop(i tried this only when prg ran by my system only)

How can we speed up delta Process?

Hi All,
As per control parameter settings we have max. no processes as 6 and 10 data packages for one Info doc and its the same for that particular infosource settings.
but when we schedule the delta info package( R/3 - BW ODS) it is using only one process and one (data package per Idoc.
But when the data is being updated from ODS to cube its using 6 processes ( in SM66) and almost 6-10 data packages( details tab in scheduler page).
How can we speed up the delta load from R/3 to ODS, and make it use upto 6 processes.
Where can I check these settings?
Thanks in advance.
Robyn.

hi
one of the method to improove the performance in loading to ODS.
Go for PSA partintioning through RSCUSTV6
and u can partition the ODS object also RACUSTA2
then whole data set will split in to the several data packets in PSA and in ODS.
hope it helps
bhaskar.

Action 'Load CUA ' in SM66

All,
We are havin gissues with our some long running processes. When I go to monitor the process in SM66 to see what they are doing in the action column it says 'Load CUA'. This only appear to be happening with the program that is having problems.
Can anyone provide an explanation of what this means?
Thanks,
Paul

Hi,
You may need to increase CUA buffer size parameter on the profile. "Loading CUA" means that the system is loading dynpros into the memory.
Best regards,

Webservice call timing out in ECC 5.0

Hi
When I make a call to a webservice exposed out of ECC 5.0 from a SOAP client - I see the call being taken up by a work process in SM66 - staying alive for a few seconds and then it disappears from SM66 and at the same time I get a error on the SOAP client
Error reading server response: The underlying connection was closed: The request was canceled.
If I run the same method ( sync implementation ) from within R3 - ( SPROXY and then test interface - by submitting an xml payload ) - the query runs for around 25 seconds and comes back with a result payload.
Have anyone experienced this problem ? What ICM timeout parameter needs to be changed - here to solve this problem ?

Hi,
perhaps the PROCTIMEOUT expires, the timeout parameters of the ICM are configured individualy for euch icm/server_port_<x>, you will find more details in the documentation:
[http://help.sap.com/saphelp_nw70/helpdata/EN/25/7e153a1a5b4c2de10000000a114084/content.htm]
But befor increasing timeouts at random you should find out the actual cause of this error.
Did the ICM actualy close the connection due a timeout or was it closed from the communication partner?
If you increase the trace level of the ICM (transaction smicm) and reproduce the error, the trace file of the ICM (dev_icm) should show the exact error message.
Regards,
Stefan

Dead lock error while updating data into cube

We have a scenario of daily truncate and upload of data into cube and volumes arrive @ 2 million per day.We have Parallel process setting (psa and data targets in parallel) in infopackage setting to speed up the data load process.This entire process runs thru process chain.
We are facing dead lock issue everyday.How to avoid this ?
In general dead lock occurs because of degenerated indexes if the volumes are very high. so my question is does deletion of Indexes of the cube everyday along with 'deletion of data target content' process help to avoiding dead lock ?
Also observed is updation of values into one infoobject is taking longer time approx 3 mins for each data packet.That infoobject is placed in dimension and defined it as line item as the volumes are very high for that specific object.
so this is over all scenario !!
two things :
1) will deletion of indexes and recreation help to avoid dead lock ?
2) any idea why the insertion into the infoobject is taking longer time (there is a direct read on sid table of that object while observed in sql statement).
Regards.

hello,
1) will deletion of indexes and recreation help to avoid dead lock ?
Ans:
To avoid this problem, we need to drop the indexes of the cube before uploading the data.and rebuild the indexes...
Also,
just find out in SM12 which is the process which is causing lock.... Delete that.
find out the process in SM66 which is running for a very long time.Stop this process.
Check the transaction SM50 for the number of processes available in the system. If they are not adequate, you have to increase them with the help of basis team
2) any idea why the insertion into the infoobject is taking longer time (there is a direct read on sid table of that object while observed in sql statement).
Ans:
Lie item dimension is one of the ways to improve data load as well as query performance by eliminationg the need for dimensin table. So while loading/reading, one less table to deal with..
Check in the transformation mapping of that chs, it any rouitne/formula is written.If so, this can lead to more time for processing that IO.
Storing mass data in InfoCubes at document level is generally not recommended because when data is loaded, a huge SID table is created for the document number line-item dimension.
check if your IO is similar to doc no...
Regards,
Dhanya

BTE 2040 is triggering during F110 run.

Hi,
2040 BTE is not triggering during F110 run. I have copied the SAMPLE*2040 FM and kept infinite loo to catch switch the debugger in background process at SM66. But the BTE is not at all triggering after I run F110.
Any other way to fix it?
all my settings @FIBF is fine and I have cheked few threads all process is fine.
Is it any configuration issue?
Regards
Kasturi

Hi Kasturi,
See SAP Note 556924 - RFFOD__V - Alternative payment advice form.
See in tcode FBZP what RFFO* report you call when you run F110 (check it in F110). The BTE is triggered by this RFFO* report, that it can be triggered by F110.
I hope this helps you
Regards
Eduardo
PD: see also SAP Note 836169 - Consulting: Payment advice notes by email or fax
Edited by: E_Hinojosa on Sep 12, 2011 6:07 PM

Identifying the BW report behind a long-running DIA wp

Hello - if you see a long running work process in sm66/50...then i can correlate it to the oracle session w/ st04...and then i can see the actual query and explain plan, etc.
however, i am having trouble tying this back to the BW "report" which the user launched. i know it's a web report, and all i could find in st03 was RFC time.
i looked in se16 at RSDDSTAT for the timeframe in question, but couldn't find a record that correlated to what i saw running actively in sm66/50/st04. any other way to do this? (other than calling the end-user directly)
thanks

Hi Ben,
I believe now I understand your issue... and I only see two possible options:
1. Activate trace for the user that is getting the long-running process (you can do it from RSRTRACE, and those logs are not very big). If you see queries that have a very big time on CMD_PROCESS WAIT, then those are candidates to review.
The main problem with this option is that you can't catch the user instantly, cause user should log out and log in in order to activate the trace, and you'll need to constantly analyze his logs to catch the annoying query.
2. Debug the dialog process and find the WRITEQUERY execution (by using F7). There, on g_s_repkey you'll find query technical name on compid. The problem here is to get the authorization from your basis team to perform debugging on a production system (it is not recommended).
Maybe you can also try to analyze BW Statistics... let's see other opinions.
Hope this helps,
David.

Urgent :conversion lock problem

Hi All,
I tried to change the existing info object.while activating it again .It is showing a conversion lock infront of teh tecnical name of teh info object with status one.
Kindly tell me the way to release that lock.
regards,
Sonika

it may be normal to wait a bit if your object has many records...
When deleting an attribute, the system needs to adjust the underlying tables.
In reality the DB move the original table to a temp table, delete the fileds on the original table and move the data from the temp table back to the original...
The more data your have, the more it will take time.
You can check your system processes in SM66 in order to verify that.
If nothing is running then try the following:
in RSD1 tab master data / texts
double click in the master data tab (/BIC/P% or /BI0/P% table)
Menu Utilities / database utilities
Check the status of the table: is it active or not?
-If not then click on Activate and adjust database (with SAVE DATA!!!!)
-if yes then go back and perform the same with the SID table attr (/BIC/X% or /BI0/X% table)
Let me know how it goes
Olivier.

Job is in suspened state

Dear SDNers,
How do we know a job is in suspended state.
because some of my ECC jobs are in Released\ from last 2 days and scheduled time as 2 days back only..it runs for every 3 hrs .
Thanks,Swathi

Hi,
Well here's what you need to do.
If the job is in 'Released' state in ECC, that implies that it has received no background work process (WP) to start the activity.
Please check the background work processes with SM66 or SM51 (here choose the server and check the work process status).
Check how many BGD (background) work processes are in 'Waiting' state.
Here the work processes will most probably be either 'On hold' or 'running' state. Go inside the work process and see what activity was being done last after which it got stuck and then inform the basis team to end the work process forcefully.
This will solve your issue.

RBDAPP01 going into SLEEP Mode and Idocs still in 64 status

Hey all,
I have a Inbound Idoc interface which is being processed using RBDAPP01 Program. The Issue I am facing is that the job running the rbdapp01 program goes into sleep mode even though there are idocs present in 64 status. I tried to debug the work process using SM66 but it does not open any debugging window although it says debugging started. If I cancel the Job and run it again it processes those Idocs Any input on how one can resolve this issue?
Thanks.

Hi Aparna,
Here is extract from SAP material on running RBDAPP01 transaction and possible reasons for delay in processing. HOpe this can help you.
To automate the treatment of IDocs, you must run the ABAP program RBDAPP01 (transaction BD20) in job. This program has a very good option for parallel processing which can reduce a lot the time required for treatment. However use it carefully and make sure you set a packetsize high enough to avoid that your SAP system be overwhelm by demands for available dialog tasks (don't forget one dialog task is monopolized per IDocs packed to treat).
Best Regards,
Krishna

Trasanction Codes used in Sales & Marketing Modules

Hi All,
Please provide important Transaction codes (T Codes) that is been using in Sales & Marketing modules for solving the
Support It Ticket for CRM.
Please let me know which are the area's that are using into.
eg: Sa38 is ABAP reporting
Sm37 : background jobs.
Please do reply so that i would be helpful for me,
Thanks in advance
Prajith P

Hi Prajith
Hope the below transaction codes in CRM will be helpful.
Transaction Code - Description
SE19 Badi implementation
SE93 Transaction code check
smw01 workflow
Crm_Erms_mailforms Forms
SWDD ERMS Rule modler workflow
SE 18 BADi creation
SE19 Badi implementation
se11 tables
SE38 Functional module reports/fields display
se11 crmd_orderadm_h
SE16 TC
TSTC
SE93 Application Component - get there displayed all transaction codes for example crm-md-bp
CRMD_ORDER - creating marketing sales and service transactions
BP - BP
CRM_MKTPL FOR search campaigns deals
sost-transmissionRequest forms
scot -administration system status
CRM_UI_FRAME: Access BSP WD work bench
BP -Business Partner (Creation/View/Modification)
CIC0 -Customer Interaction Centre
CRMD_ORDER - CRM Transaction (Create/View/Modify)
SPRO - Configuration related settings
CRMD_CALL_LIST-Create/ Maintain Call list
IB51 / IB52 / IB53-Ibase Creation / Change / View
COMMPR01-Maintain Products
PPOSA_CRM-Display Organizational Model
SBDM-Bdoc maintenance
SMOEAC- Administration console u2013 CRM Middleware
SMQ1,SMQ2 Queue monitoring transactions for inbound and outbound queues.
SMW01 Transaction for monitoring bdocs.
MIddleware t-code
Transactions Transaction Codes
Work process overview SM66
CPU and memory consumption ST06
SAP memory and buffers ST02
Database performance counters ST04
Memory consumption per user SM04 (on each application server)
Table call statistics ST10
CPU & Memory Consumption on IPC Server OS07
CRM Inbound Queue SMQ2
CRM Outbound Queue SMQ
Monitor Load R3AM1
Define Request R3AR2
Run Request R3AR4
Request Business Partner CRMM_BUPA_MAP
Send Business Partner CRMM_BUPA_SEND
RFC statistics (client and server) ST03
Errors in transactional RFCs SM58
BDOC Statistics SMWMFLOW
Response time statistics ST03 & STAD
Error Tracking SMWP
Q-Out Scheduler SMQS
Q-In Scheduler SMQR
Bdoc Error Tracking SMW01 & SMW02
Short Dumps ST22
Admin Console SMOEAC
Process Overview SM50
User List AL08
Data Integrity Manager SDIMA

BDLS cancelled in the midaway - urgent help needed

Hello All,
After refresh from production into test system, we ran BDLS in the test system for logical system name coneversion in background.
But the job got aborted throwing some database error (as some other activity was going on and due to which rollback segments were not sufficient)
Now when we try to execute the BDLS again, it is giving error telling that a conversion is already going on!!!( even after 3 days from the cancellation of BDLS job)
The error is :
Another Process is Running for Conversion LOG500 -> TRICLNT500
Message no. B1668
Diagnosis
While a conversion is running, you cannot start any further processes for the test run. Depending on the size of the dataset in the system, this process can last a long time.
Procedure
Check whether all the conversion processes in the corresponding system are complete (online or background processing), or whether they have terminated due to a program error. If a process has terminated abnormally, first solve the error and delete the conversion log, then restart the process
Please let me know in case of any pointers? Can we rerun the BDLS? What needs to be done for that?? Any notes??
Best Regards,
Arun

Hi
Please check in SM37 if the status is changed to cancelled
If the process was aborted 3 days back then there should not be any running processes in SM66 , and sm37 should show status CANCELLED.
If not then in SM37 , select job , and do an Job --> check status.
Also check for any locks and updates in sm12,SM13 related to this job
Then Retsart it in the same client
Hope this helps
Ravinder

Process in SM66

Similar Messages

Maybe you are looking for