Wednesday, 28 August 2013

Background Jobs to Be Scheduled Regularly

Background Jobs to Be Scheduled Regularly 
There are a range of background jobs that must run regularly in a production system, to, for example, delete obsolete jobs or spool objects. You should schedule the following jobs periodically in the job definition transaction SM36, so that they are automatically started at the specified frequency:
Program Name / Job Name
Repetition Frequency
Description
RSBTCDEL2 /
SAP_REORG_JOBS

Daily
Deletes old background jobs
RSBDCREO /
SAP_REORG_BATCHINPUT
Daily
Deletes old batch input folders
RSSNAPDL /
SAP_REORG_ABAPDUMPS

Daily
Deletes old ABAP dumps
RSBPSTDE /
SAP_REORG_JOBSTATISTIC

Monthly
Deletes old job statistics
RSBPCOLL /
SAP_COLLECTOR_FOR_JOBSTATISTIC

Daily
Creates job statistics
RSCOLL00 /
SAP_COLLECTOR_FOR_PERFMONITOR

Hourly
Starts data collectors for ABAP statistics records
RSN3_STAT_COLLECTOR/
SAP_COLLECTOR_FOR_NONE_R3_STAT
Hourly
Starts data collectors for non-ABAP statistics records (Distributed Statistics Records, DSRs)
RSXMILOGREORG /
SAP_REORG_XMILOG

weekly
Deletes obsolete entries in the XMI log
RSAL_BATCH_TOOL_DISPATCHING/
SAP_CCMS_MONI_BATCH_DP

Hourly
Starts long-running data collectors that report application-specific values to the monitoring architecture
RSPO0041/1041
SAP_REORG_SPOOL

Daily
Deletes obsolete spool requests to reduce system load
RSPO1043

Daily
Checks the consistency of the spooler and of the TemSe and evaluates the results if necessary
RSBTCPRIDEL/
SAP_REORG_PRIPARAMS

Monthly
Reorganizes the print parameters across clients

Friday, 23 August 2013

Enable Multiple RDP sessions via the registry

Enable Multiple RDP sessions via the registry

1. Start > in the search/run box type regedit {enter} > Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

Locate the fSingleSessionPerUser value > Set it to 0 (Multiple sessions allowed), or 1 (Multiple sessions NOT allowed).
multiple rdp

Monday, 12 August 2013

Local Client Copy

You have created a new SAP client and want to copy data from other client.
You do local SAP client copy for the following:
- to fill initial data (usually copy from 000)
- to do SAP System refresh (in your QA)

1. Login to your newly created/empty client as SAP* and Go to Tools -> Administration -> Administration -> Client Administration -> Local Copy or Directly Go to transaction SCCL.

SAP Local Client Copy
SAP Local Client Copy
 2. Choose the copy profile

Profile for SAP Local Client Copy
Profile for SAP Client Copy
 3. Use Parallel Processing to speed up the process.

Use Parallel Processing for Client Copy
Use Parallel Processing
 4. Enter the Parallel Processing Group

RFC Group for Parallel Processing
RFC Group
 5. You can schedule in background or start immediately

Background server for Client Copy
 6. Choose Background Server and click immediately

Choosing Background Server for SAP Client Copy
Choosing Background Server for Client Copy
 7. Background Job scheduled

Choose Background Server for Client Copy
Scheduling Client Copy
 8. Summary of your SAP Client Copy

Summary of SAP Client Copy
Summary of your SAP Client Copy
 9. SAP Client Copy is being processed and you can see the log from SCC3.

Log of Client Copy
10. Double click to see the progress.

Progress of SAP Client Copy
11. Make sure your client copy is successfully completed .

SAP Client copy successfully completed
SAP Client copy successfully completed
From Solution Manager Component Approval:
Goto Transaction  SE37--> 


give the program name /TMWFLOW/MO_UI_BASKET_AUTHORIZ

Click on Execute and again click on Execute-->


then you can find the components list for download-->
click on confirm download..



After that files will be appear in Download basket for download..