SAP BASIS

Monday, March 15, 2010

BASIS MATERIAL

1) Basis (BC)
2) Basis
3) Batch Management (LO-BM)
4) BC - ABAP Dictionary
5) BC ABAP Workbench Tools
6) BC ABAP Workbench Tutorial
7) ABAP Programming (BC-ABA)
8) BC Basis Programming Interfaces
9) BC - Business Workplace
10) BC - Central Maintenance and Transport Objects
11) BC Data Modeler
12) BC Documentation of System Objects
13) BC Extended Applications Function Library
14) BC - Namespaces and Naming Conventions (BC-CTS-NAM)
15) BC R/3 Database Guide:DB2/400
16) BC R/3 Database Guide: DB2 Universal Database for UNIX & Windows
17) BC R/3 Database Guide: Informix
18) BC SAPconnect
19) BC SAP Graphics: Programming Interfaces
20) BC SAP Graphics: User's Guide
21) BC - SAP Printing Guide
22) BC SAPscript Raw Data Interface
23) BC SAPscript: Printing with Forms
24) BC - SAP Style Guide
25) BC Style and Form Maintenance
26) BC System Services
27) BC The SAP Communications Server
28) BC - Word-Processing in the SAPscript Editor
29) Desktop Office Integration (BC-CI)
30) SQL Studio (BC)
31) Reference Manual 7.2 (BC)
32) Messages 6.2 (BC)
33) Messages 7.2 (BC)
34) Network Integration Guide (BC-NET)
35) Updates in the R/3 System (BC-CST-UP)
36) Users and Roles (BC-CCM-USR)
37) The SAP Lock Concept (BC-CST-EQ)
38) The Test Workbench in the SAP System (BC-CAT-PLN)
39) The Appointment Calendar (BC-SRV-GBT)
40) The BAPI Gateway Component (BC-FES-AIT)
41) Terminology and Glossary in SAPterm (BC-DOC-TER)
42) Business Configuration Sets (BC-CUS)
43) Business Document Service (BC-SRV-BDS)
44) Central Adress Management (BC-SRV-ADR)
45) Change and Transport System - Overview (BC-CST)
46) Changing the SAP Standard (BC)
47) Computing Center Management System (BC-CCM)
48) Controls Tutorial (BC-CI)
49) Repository Service Component (BC-FES-AIT)
50) Generic Object Service (BC-SRV-GBT)
51) Hypertext Structure Maintenance (BC-DOC-DTL)
52) Generic Business Tools for Application Developers (BC-SRV-GBT)

Friday, November 23, 2007

Sending faxes from SAP

Some guidelines how to you can setup faxing from SAP :-

You will need an additional software to be installed.

The best way to do this is to get a standard desktop PC with a modem attached. Buy a
copy of Winfax 10 (its only about $100 to buy.)

When you have Winfax setup and working locally, install SAPLPD (put it in the startup group so its loads on startup).

WinFax will create a shared fax on the PC (For e.g. IFAX).

When this is done create a printer/Fax in transaction SPAD.

Device type = SAPWIN Rel.4.x/SAPlpd
Device class = Fax
Host Spool access method = S;print using SAP protocol
Dest. host = PC IP address
Host printer = Shared fax name on PC(i.e IFAX)

Make sure you have all the lasted SAPLPD + dll's

After that is done create the locations in transaction SCOM, they are self explainitory from there.

Printing ABAP Report over LAN and WAN

For the LAN setup for local printer you can defined it as device LOCL

Device type: SAPWIN
Host printer: __DEFAULT
Host spool access method: F (Printing on front end computer)

This printer will works fine on your LAN.

For the WAN, assuming that you have 2 office connected over the internet and they work fine with the printer LOCL.

Now, you need to have a Print Server where you have installed many of the printer, some of them over WAN and they will work fine if you do this :-

The server must have SAPLPD installed.

Output device: LPFP
Device type: SAPWIN
Destination host: sapdev
Host printer: HP_HP1 (printer name on the Printer Server)
Host spool access method: S (Print on LPDHOST via SAP protocol)

Auto convert SAP spool output to PDF file

As of Release 4.6D, PDF format (Adobe Acrobat data format) can be created via the SAP spooler by using the device type "PDF1".

As a workaround, a report (RSTXPDFT4) is made available for the missing "direct PDF printing", which can read spool requests, convert to PDF and perform a frontend download.

Read OSS Note 317851 - Printing PDF files in 4.6C/4.6B/4.5B

Note the restrictions specified in Note 323736 with the print output with PDF.

Caution when modifying device type ZPDF1, see Note 437696.

Version - 4.6D

If you are in version less than 4.6D, you can configure an output type to convert the spool automatically into a PDF format into your local harddisk but not do a "direct PDF printing".

When you print to this PDF output type, it will prompt you to enter the file name of your PDF file to be stored into your local harddisk.

First you have to add a printer using

Windows -> Start -> Settings -> Printers -> Generic / Text Only -> Port : Print to File

Next create a new device type e.g. ZPDF -> Select device type ZPDF1

Options for HostSpoolAccMethod

-> Host spool access method : F : Printing on Frontend Computer
Host Printer : __DEFAULT or Generic / Text Only

Save your entries.

When you print to the device type ZPDF, choose Generic / Text Only for the Frontend Computer if it is not the default type.

A user prompt Print to File will appear to let you specify the Output File Name.

Delete multiple spool request

The program are RSPO0041 or RSPO1041.

This is handy whenever you encounter a user who managed to create a lot of spool requests which are choking your system.

Deleting them with SP01 will be too slow and you will get time out if it exceed the online time limit specify by your basis people.

How can I print A3 format in SAP

My printer is HP LaserJet 5100

Note I can print ms word document in A3 format but I can't print A3 format in SAP

My output device setting are:

DeviceAttributes:
Device Type = THSAPWIN: MS-Windows-Printer via SAPLPD
Device Class = Standard printer
Access Method:
Host Spool Access Method = S: Print Using SAP Protocol

When I print SM50 output and select format X_65_255, it can print successfully but its format is A4.

What may I do wrong? Please help me how to set up for A3 printing in SAP.

Ps. Do I need to assign A3 format to be default format in that printer?

Is this task for BASIS or ABAP?

In printer settings - SPAD - tray info - you can give the Page format for that tray .
did you try setting that ? Try setting DINA3.

Go to START --> SETTINGS ---> Printers

Right click on HP LaserJet 5100 ... Properties..
General Tab --> Printing Preferences --> Advanced --> Paper Size -->
Change it to 14x11 or A3

and

hplaserjet 5100 --> Properties --> Advanced Tab
Printing Defaults --> Advanced --> Paper Size -> change it to 14x11
or A3

hplaserjet 5100 --> Properties --> Device Settings tab -> Autoselect -
-> A3 or 14x11...

Our ABAPer already changed some attributes(ex. font name & size) in print control of SPAD followed by SAP Notes 21738.

Like this ->

# THSAPWIN Z_65_255

# SAPWIN indicatior makes it possible to send via berkeley protocol
\e%SAPWIN%
# change WinCharSet to 222 (Thai)
\eW222;
# set orientation(LANDSCAPE)
#\ePL
# set font name
\eFAngsana New;
# set font size(5.5ponits)->8p->5.5
\eS220
# set vertical spacing(8.7LPI)
#\el3.0;
# set horizontal spacing(24.0CPI)->20->18 (255/11) ->23
#\ec5.0;
# set top/left margin(1.0cm=568.5)
#\eMT567;
#\eML567;

However, it take moderately time to change font size and test report printing for A3 format.

Thank you for your recommend.

I follow by your instruction. It's work well.

Note It doesn't need to setup these config at all.

Tab "Output Attributes"
Paper tray = "Paper tray 3"

Tab "Tray Info"
Tray 3 = "DINA3"

Key points of this solution, If the SAP spool server and the Microsoft Windows spool system are not on the same host, you must create a remote PC connection to the printer and force paper size to be A3 (Prakash's instruction)

By the way, I also adjust HP Laserjet 5100 from "EXEC" to "A3" in Tray 3 physically too. After that I can print ABAP List in A3 Format successfully.

Thank you again for the solution.

Parallel printing to all the SAP device printers

If you have a situation where reports need to be send to multiple printers, you can configure a pool device type. A pool device type contain a list of SAP printers which the reports will be directed to.

Do this in transaction code SPAD for spool administration.

For example, in SPAD, type ZXXX next to the field 'Output devices',

Click the button Output devices.

In change mode, click the Create button.

Specify the Device type of your printer.

Click the tabstrips 'HostSpoolAccMethod'.

In the field "Host spool access method" set to "P: Device Pool".

Click the tabstrips 'DevicePool'

Click the options "Send to all devices in pool".

Type in the list of the SAP printers device you want the report to go to in this pool under the section 'Pool Device List'.

Now, when the users send a print to the new device for e.g. ZXXX, it will print to all the spool device you have specify.

The above step is done using SAP 4.6c

Print to an USB printer from SAP

Is printing to a USB-printer using LOCL from SAP possible?

Yes, as long as this printer is defined on local workstation, it will work.

SAPLPD doesn't care on how the printer is connected, as long as Windows can print to it, SAPLPD will do its work.

Define one new device, also consider giving :

Device type as SAPWIN

Host Printer __default (yes, two underscores default)

Access Method : F

Make sure your desktop/PC Windows default printer is set to this USB printer.

Mass Lock All Printers with SPAD

If you have lots of printers (50 or more) and need to lock them for maintenance, you can used this mass locked printers tips to locked or unlocked all the SAP printers at one go.

To mass Lock all the printer in SAP:

Go to transaction code SPAD

On top of the screen menu click Utilities -> For output devices -> Export devices

On the screen Import and Export of Device Descriptions:

Export/Import file name: c:\temp\printer.txt

Frontend computer: Tick

Export: Tick

Export Export: Tick

Output device: Choose the Selection options Pattern and type a *

(* for all or a* for all printers starting with a)

Click the Execute button

Open the text file do a replace all of PADISABLED = "" to PADISABLED = "X"

Then import the same file.

Another way is to go through each output device in SPAD and click on 'Lock Printer in SAP System' which is in the DeviceAttributes tab.

Troubleshooting SAP Performance Issues

Is there a document that will help me troubleshoot system performance? What are the steps on how to troubleshoot?

Troubleshooting is a BIG task of itself, there is no single reference document because there are too many reasons why a system can appear "slow" to the user:

- Different Databases

Every database has its own mechanism for optimizing access, even more, each database has BOOKS on performance optimization. This can start from parameters to database layout to operating system configuration, used filesystems, mount parameters...

- Different Operating System

The same goes for operating systems, a standard Windows 2000 (or 2003) isn´t configured for optimal throughput, there is a LOT to tune, e. g. enable "background process priorities", stop non-needed services, network configurations (TCP window sizes) etc. Also the connection between application and database servers can be an issue

- SAP Itself

Almost for each and every long running program there are optimizations, be it on ABAP layer or on selection layer. Out of my experience, most self developed programs (Z*-programs) are the main issue, because developers program "quick-and-dirty"
doing "select *" and other things.

For e.g.:

If CPU is 100% Busy, what action should be taken to keep CPU idle?

This can't be answered generally. One need to check what process is using so much CPU - then one can start digging deeper. To add info regarding this issue, you may use:

st06->details analysis menu->snapshot analysis->top CPU from there, start to narrow down.

Tuning Summary In Transaction ST02

My current system is SAP R/3 Enterprise 4.70. I have some questions about tuning summary in transaction ST02 :

To the best of my knowledge I am answering your questions. Ok

1. Do we have to increase every profile parameter value which is displayed in red alert in transaction ST02 ?

Ans: Of course it should be, since each buffer holds different values, wherever the red alert is there change the parameter value.

2. Why do the swapped objects always increase after a few days of tuning (in RZ10) & system restart?

Ans: Since more data had been fed into the server, it needs more space to hold in buffer while retrieving the data.

Since buffer is shot in space, swap memory will be used. It is not enough to increase the buffer and that does not mean tuning, tuning in the sense full analysis of the problem and working in that particular area to resolve the issue.

For example, creation of index, data archival, availability of statistics, aloting of no. of work process, etc.

3. Is there any standard in tuning ST02 to hold up the increasing value of swapped objects?

Ans: No. It depends on requirement.

4. After analysing ST02, how can we calculate the value of the parameter profile to be increased (in RZ10) ?

Ans: yes, use the command:

sappfpar check pf=\\usr\sap\trans\tpparam

(or)

sappfpar check pf=\\usr\sap\trans\tp_domain_sid

SAP System Performance Issues

My server becomes slow when more users login.
What could be the reason? Is it because of less hardware resource?

Server configuration is 104GB HDD, 2GB Ram.
OS:Win 2003 server.
Database:Oracle.

I manage SAP R/3 4.6C systems on Risc 6000 machines, under Oracle 9.2.

The overall performance problem for me is to know if SAP response time is acceptable ; if not, do this :

- at AIX level : utilities are topas, to catch what's wrong : Disk I/O ? CPU bottleneck ? Too much swap ?

- at Oracle level : tkprof but don't know much about this.

- at SAP level : you can manage SAP memory, Oracle and OS too.

If SAP response time is acceptable, then try this :

Try to have a look at OS response time : ST06 : look at CPU, Memory, Swap, Disk and Lan response time.

Try to have a look at buffer quality : ST02, if many fields are red, investigate each fields dependant parameters.

Try to have a look at DB response time : ST04N, databuffer quality (SGA zone), how much physical reads / logical reads Ratio, wait times, number of user calls, Shared Pool cache hit ratio should be >96%, Sort usage, Redo logging.

I use this kind of procedure to manage my systems.

It depends how much you allocated for SGA (database buffers, shared pool buffer, redo log buffers), how much you allocated for SAP buffers esp. Program buffers and whether the server have any other external processes/programs running.

How many Dialog Work Processes you allocated…I think your problem most likely is you don’t have enough of these Dialog processes. Also maybe users running inefficient reports/programs which are holding the Dialog processes, goto SM50 & check all DIA (Dialog) with status “waiting”…if ALL are “running” then you have wait time (problems !) for other users wanting to process transactions .

To troubleshoot performance, you need these tcode tools:-

ST04 – Database ß in here, check especially for Expensive SQLs (Detail Analysis à SQL Request)

ST02 – SAP buffers

ST06 – OS stats

ST05 – SQL trace

SE30 – Abap runtime analysis

A few step which you can exercise to sort/identify performance issues.

* ST03, ST02, ST04 are the tcode for workload, tuning and DB Performance Monitoring codes.

* ST06 FOR Operation System Monitoring.

** SM51 OR SM50 is process overview which tells you the workprocess sequence. ( Ideally 10-15 process with OLTP and batch process scheduled at peak and off peak times respectively) say 8-17 hrs and 17-8 hrs for Batch Process)

Operation Mode can be configured in RZ04 tcode.

** Check for top CPU in ST06 tcode. CPU should not exceed more than 60% for long time for any process.

** Based of No. of instances ( Application Servers ) should have adequately sized.

** Most resources intensive process have to be scheduled in Batch Process ( in Background in Non Peak Hours )

** Look for unnecessary Jobs Active During Prime Time
** Look for Parameters Set To Your Business Process.
( RZ10, RZ11 ) Check Snote:0124361

** Refer Early Watch Alert Periodically for Overall System Performance.. ( Tcode SDCC )

SAP Load Balancing and Work Processes Troubleshoot

The benefit of segregating user groups by line-of-business (using logon groups) is related to the point that groups of users (like SD users or HR users, for example) tend to use the same sets of data. They (generally) work with the same groups of tables and hit the same indexes using the same programs (transactions).

So, if you can group all of the users hitting the same tables, onto (or one set of) App server(s), then you can tune the App server buffers to a much greater extent. If the FI users (generally) never hit against the HR tables then the App servers in the FI group don't (generally) have to buffer any HR data. That leaves you free to make memory and buffer adjustments to a more drastic extent, because you don't have to worry (as much) about screwing the HR users (as an example), when you're adjusting the FI server group.

So, (in opinion only) you should start with a buffer hit ratio analysis / DB table & index access analysis (by user group) to see where you would get the best benefit from this kind of setup. If you don't have this kind of info, then creating logon groups by line-of-business may have no benefit (or worst case, may make performance degrade for the group with the highest load %). You need some historical information to base your decision on, for how to best split the users up.

You may find that 50% of the load is from the SD users and so you may need one group for them (with 3 App servers in it) and one other group for everyone else (with the other 3).

The logon group(s) will have to be referenced by SAP GUI, so SAP GUI (or saplogon.ini + maybe the services file, only) will have to change to accomodate any new groups you create in SMLG. Also consider that there's variables for time-of-day (load varies by time-of-day) and op-mode switches (resources vary by op-mode).

All Work process are running? What will be our action?

Are all the work processes (dia,btc,enq,upd,up2,spo) running or just all the dialog work processes?

If all the work processes are running, then you may want to look at SM12 (or is SM13?) and see if updates are disabled. If they are, look at the alert log (if it's an Oracle database) and see if you have any space related errors (e.g. ORA-01653 or ORA-01654). If you do, add a datafile or raw device file to the applicable tablespace and then, re-enable updates in SM12.

If only all the dialog work processes are running, there are several possible causes. First, look to see if there's a number in the Semaphore column in SM50 or dpmon. If there is, click once on one of the numbers in the Semaphore column to select it and then, press F1 (help) to get a list of Semaphores. Then, search OSS notes and, hopefully, you'll find a note that will tell you how to fix the problem.

If it's not a semaphore (or sometimes if it is), use vmstat on UNIX or task manager on Windows to see if the operating system is running short on memory which would cause it to swap. In vmstat, the free column (which is in 4k pages on most UNIX derivatives) will be consistently 5MB or so and the pi and/or po columns will have a non- zero value. The %idle column in the cpu or proc section will be 0 or a very low single digit while the sys column will be a very high double-digit number because the operating system is having to swap programs out to disk and in from disk before it can execute them.

In task manager, look at free memory in the physical memory section under the performance tab. If it's 10MB or 15MB (I think), then the operating system will be swapping.

Usually, when all the dialog work processes are running, you won't be able to log in via SAPgui and will need to execute the dpmon utility at the commandline level. The procedure is basically the same on UNIX and Windows.

On UNIX:

telnet to server and login as sidadm user.
cd to /sapmnt/SID/profile directory
execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_hercules_DVEGMS00) select option "m" and then, option "l"

On Windows:

Click on START, then RUN
Type "cmd" and press enter
change to drive where profile directory resides (e.g. f:)
cd to \sapmnt\SID\profile
execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_zeus_DVEGMS00) select option "m" and then, option "l"

On both operating systems, you'll see a screen that looks like what you see in SM50. Depending on what you see here, will depend on what you do next, but checking the developer trace files (e.g. dev_disp) in the work directory (e.g. /usr/sap/SID/DVEGMS00/work) is never a bad idea.

SAP Load Balancing and Work Processes Troubleshoot

You may find that 50% of the load is from the SD users and so you may need one group for them (with 3 App servers in it) and one other group for everyone else (with the other 3).

All Work process are running? What will be our action?

Are all the work processes (dia,btc,enq,upd,up2,spo) running or just all the dialog work processes?

In task manager, look at free memory in the physical memory section under the performance tab. If it's 10MB or 15MB (I think), then the operating system will be swapping.

On UNIX:

telnet to server and login as sidadm user.
cd to /sapmnt/SID/profile directory
execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_hercules_DVEGMS00) select option "m" and then, option "l"

On Windows:

Saturday, October 13, 2007

Post Installation Steps For ECC 5.0

What are the post installation steps after I have installed the Central Instance and Database instance?

Initial Consistency Check

SM28

1. Logon to the newly refreshed SAP system and run transaction SM28

2. Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.

Edit Batch Jobs

1. Set the fields as follows

Job name: RDDIMPDP*

User name: *

Job Status: Released and Ready checked off, all others unchecked

Fr: 01/01/0001

To: 12/31/9999

Or after event: *

2. Press F8 to execute the query

3. Highlight the first job in the list and press the CTRL+F11 to change the job.

4. Examine the Exec Target field.

a. If the box is empty, press F3 to exit

b. If the box is not empty, then clear out the contents so the field is blank and press CTRL+S to save

5. Repeat Steps 3 and 4 *for* each additonal job listed.

Workbench Organizer Reconfiguration

1. Logon on to client 000 of the newly refreshed system with DDIC.

SE06

1. Select the Database Copy or migration option

2. Press the Post-installation Processing button.

3. When prompted Do you want to re-install the CTS?, press the Yes button

4. When prompted *for* the Source System of Database Copy?, make sure that the SID of the production system is selected. Press the checkmark button to continue.

5. When prompted Change originals from PRD to QUA?, press the Yes button

6. When prompted Delete TMS Configuration?, press the Yes button

7. When prompted Delete old TMS configuration?, press the Yes button

8. When prompted Delete Old Versions of transport routes?, press the No button

TMS Configuration

1. Logon on to client 000 of the newly refreshed system.

STMS

1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed

2. The information on *this* screen is automatically filled out from information provided during the SAP installation and should be correct. If it correct, then enter a description *for* the system and press CTRL+S to save. Otherwise, press the Other configuration button and manually configure.

3. From the Overview menu, select Transport Routes

4. From the Configuration menu, select Adjust with Controller

5. Press the Yes button when prompted *if* you want copy the transport routes from the controller.

Import Printers

1. Logon on to the production client of the newly refreshed system.

STMS

2. Press F5 to go to the *import* Overview.

3. Double click on the SID of the newly refresh system

4. From the Extras menu select Other Requests, then Add.

5. In the Transp. Request box, enter the transport number containing the printer definitions that was exported. Press Enter to save.

6. Select the transport that was just added to the queue and press CTRL+F11 to start the import.

7. In the Target client box, enter the productive client of the newly created system. Press Enter to save.

8. Press the Yes button to start the transport.

Client Configuration

SCC4

1. From the Table view menu, select Display -> Change

2. When warned that the table is cross-client, press the checkmark button.

3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)

4. Define client as follows:

Client role: Test

Changes and transports *for* client-specific object: Changes without automatic recording

Client-independent object changes: Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

5. Press CTRL+S to save.

6. Repeat steps 4 through 6 *for* any additional clients

Set System Change Option
SE06

1. Press the System Change Option button.

2. Set the global setting to Modifiable

3. From the Edit menu, select Software Components Modifiable

4. From the Edit menu, select Namespaces Modifiable

5. Press CTRL+S to save.

Import Users
STMS

1. Press F5 to go to the Import overview

2. Double click on the SID of the newly refreshed system.

3. Press F5 to refresh the list of transports

4. Locate the transport in the list containing the user exports done before the start of the refresh. If the transport is NOT in the list, then from the Extras menu, select Other requests then Add. Enter the transport number and press Enter. Then press the Yes button to add the transport.

5. Highlight the transport and press the Import request icon.

6. At the client *import* screen, enter the target client and then press the Import button.

7. Press Enter to confirm that the *import* will proceed.

SCC7

1. Run the Post Client Import Processing.

2. The transport number should be the same as that of the transport started in STMS.

3. Schedule the job to run in the background. Do NOT schedule it to run immediately. We need to modify the job before it can be released.

4. Press CTRL+S to save.

SM37

1. Set the fields as follows

Job name: CLIENTIMPORT*

User name: *

Job Status: All options checked

Fr: 01/01/0001

To: 12/31/9999

Or after event: *

2. Highlight the job that was created by SCC7 and press CTRL+F11 to modify the job.

3. Press the Step button.

4. Select the RSCLXCOP line and press CTRL+SHIFT+F7 to modify that step.

5. In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).

6. Press CTRL+S to save the changes

7. Press F3 to go back to the main job screen.

8. Press the Start condition button.

9. Press the Immediate button.

10. Press CTRL+S to save the changes

11. Press CTRL+S again to save all the changes to the job.

12. Job will start immediately once saved. Press F8 to refresh the list of jobs

13. Continue to press F8 every once in a *while* to update the status of the job. Do not *continue* until the job is completed sucessfully.

SCC4

1. From the Table view menu, select Display -> Change

2. When warned that the table is cross-client, press the checkmark button.

3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)

4. Set the Protection to Protection level 1

5. Press CTRL+S to save.

6. Repeat steps 3 through 5 *for* any additional clients

Deleting Source System Profiles
RZ10

1. From the Utilities menu, select Import Profiles then Of Active Servers.

(Note: All application servers of the target system must be started)

2. If the Display Profile Check Log screen is displayed, press F3 to leave *this* screen.

3. Select the Profile field and press F4 to bring up a list of profiles.

4. From the list select one of the profiles associated with the source production system.

5. From the Profile menu, select Delete, then All versions, then of a profile.

6. When prompted, press the Yes button to delete all version of the profile

7. When prompted to delete the file at the operating system level, press the No button.

8. Repeat steps 3 through 7 *for* all additional profiles associated with the source system

Reconfigure Operation Modes
RZ04

1. From the Operation Mode menu, select Timetable

2. Select Normal Operation and press the Change button.

3. Highlight 00:00 in the left hand column and press the Delete Assignment button

4. If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.

5. Once all the assignments are deleted, press CTRL+S to save.

6. If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.

7. Press F3 to go back to the main RZ04 screen.

8. Right click on one of the listed Operation modes and select Delete

9. Press the Yes button to confirm the deletion.

10. Repeat steps 8 through 9 *for* any additional operation modes

11. Press F5 to create a *new* operation mode.

12. Enter a name and *short* description *for* the operation mode

13. Press CTRL+S to save.

14. Press F6 to create a *new* Instance

15. From the Settings menu, select Based on current settings, then New Instances, then Set

16. Press F3 to go back to the main RZ04 screen.

17. Press the Yes button to save

18. From the Operation Mode menu, select Timetable

19. Select Normal Operation and press the Change button.

20. Highlight the 00:00 at the top and press F2

21. Highlight the 00:00 at the bottom and press F2

22. Press the Assign button.

23. Press F4 to select the operation mode created above.

24. Press CTRL+S to save.

Delete Update Failures
SM13

1. Set the fields as follows

Client: *

User: *

From data: 01/01/0001

From time: 00:00:00

2. Press Enter to display the list of outstanding update requests

3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing F5 to select all records, then selecting the Update Records menu, then Delete.

4. Press the Continue button to confirm the deletion.

Delete Batch Input Sessions
SM35

1. From the Edit menu, select Select All

2. Press Shift+F2 to delete all the batch input sessions.

3. Press the checkmark button to confirm

4. Press the Yes button to start the delete.

Reorganize Spool
SPAD

1. From the Administration menu select Clean-up Spool

2. Check all check boxes and enter 0 *for* minimum age

3. Press the Execute button

4. Once complete, press F3 twice to get back to the main SPAD screen

5. From the Administration menu select Check Consistency

6. Press the Delete All button.

SP12

1. From the TemSe database menu, select Consistency check

2. When the check is complete, press the Delete All button.

Delete Invalid Background Control Objects
SM61

1. Press F8 to *switch* in to change mode

2. Press the Cleanup List button.

Restrict Outgoing Email and Faxes
SCOT

1. Double click on the green Fax entry

2. From the Supported Address Types area, press the Set button that is beside Fax

3. In the Address area, ADJUST AS NECESSARY

4. Double click on the green SMTP entry

5. From the Supported Address Types area, press the Set button that is beside Internet

6. In the Address area, ADJUST AS NECESSARY

Adjust RFC connections.
SM59

1. Expand the TCP/IP connections section

2. Double click on the first entry listed

3. Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system. Make changes as necessary.

4. Press the Test Connection button to test the connection

5. Press CTRL+S and then F3 to save and *return* to the list of RFCs.

6. Repeat steps 1 through 5 *for* each additional RFC connection

Convert Logical Systems

Under no circumstances perform *this* procedure on a Production system

BDLS

1. When warned to read the documentation, press the checkmark button.

2. In the Old logical system name box, press F4

3. Select one of the production Logical System names that needs be changed (i.e.WIIPRD400)

4. In the New logical system name, enter what that logical system name should be called on *this* newly refreshed system (i.e.WIITRN400)

Note: Ignore Error/Warning about duplicate system by clicking on the check mark.

5. De-select the Test Run and Existence check on *new* names in tables options

6. From the Program menu, select Execute in background

7. Press the checkmark button when asked to select a spool device

8. Press the Immediate button when asked *for* the schedule

9. Press Ctrl+S to save

10. Use SM37 to monitor the job

11. When job is complete, repeat steps 2 through 10 *for* any additional logical system names that need to be changed.

Adjust Logical Systems names

SALE

1. Expand Sending and Receiving Systems, then Logical Systems

2. Click on the execute icon beside Define Logical System

3. Press the checkmark button to confirm that the change is cross client

4. …

Allow Certains Settings to be modifiable

(Refer to Note 356483 *for* more Details)

SM54

1. Enter V_T001B in the Table/View box.

2. Select the Generated Objects option.

3. Press the Create/Change button.

4. Enter any access keys *if* requested

5. Change the Recording routine to no, or user, recording routine.

6. Press Ctrl+S to save

7. Press Enter *if* warned that you are changing a function group that doesn't belong to you.

8. You are prompted *for* transport. Create a *new* local transport.

9. Repeat steps 1 through 8 *for* the following objects. You can specify the same transport you created above.

V_T001B_GL

V_T093B_01

V_T093B_02

BSI Configuration (R3 HR Systems only)

SM59

1. Expand TCP/IP Connections

2. Highlight BSI70-US-TAX and press the Change button

3. Change the program field to

\\<hostname>\sapmnt\<sid>\SYS\EXE\RUN\TF60SERVER.EXE

4. Double check the target host and gateway point to the correct server

5. Press CTRL+S to save

6. Press the Test connection button to test. If the connect is not successful, take the
necessary steps to resolve the issue.

SE38

1. In the Program field, enter RPUBTCU0

2. Press F8 to execute

3. Select option BSI version 7.0

4. Press F8 to execute

5. BSI should *return* tax calculations. If there are errors, take the necessary steps to
resolve.

Reconfigure DB13 schedule
DB13

1.Using the printout created before the refresh, recreate the DB13 calendar.

Client Configuration
SCC4

1. From the Table view menu, select Display -> Change

2. When warned that the table is cross-client, press the checkmark button.

3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)

4. Define clients as follows depending on client role

Development

Client role: Customizing

Changes and transports *for* client-specific object: Automatic recording of changes

Client-independent object changes: Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

Quality Assurance

Client role: Test

Changes and transports *for* client-specific object: No changes allowed

Client-independent object changes: No Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

Training

Client role: Education

Changes and transports *for* client-specific object: No changes allowed

Client-independent object changes: No Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

Sandbox

Client role: Test

Changes and transports *for* client-specific object: Changes without automatic recording

Client-independent object changes: Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

5. Press CTRL+S to save.

6. Repeat steps 4 through 6 *for* any additional clients

Set System Change Option

Skip *this* section of the system is a Development or Sandbox System.

SE06

1. Press the System Change Option button.

2. Set the global setting to Not Modifiable

3. Press +S to save.

Release Background Jobs

Currently, all background jobs, except *for* system standard jobs have been placed on hold (status scheduled).

How To Do the TMS Configuration?

We have two systems with version ECC 5.0

The SID is

XY1 - Development & Quality

XY6 - Production

Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems?

How can I make through it?

First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure

------------------

1. Login to the system with sap* in client 000

2. Goto SE06.

3. Click Post installation activities

4. Goto STMS

5. It will ask for Domain controller name.

6. Enter DOMAIN_ as domain controller name and enter the description.

7. Click Save button

Steps to add the other system with Domain controller

----------------------------------------------------

1. Login to system with sap* in client 000

2. Goto SE06

3. Click Post installation activities

4. Goto STMS

5. It will ask for Domain controller name.

6. Enter System ID of the Domain controller

7. Enter DOMAIN_ as domain controller name and enter the description.

8. Click Save button

9. Login to Domain controller system

10. Approve the added system.

Information on how the OPS$ Users Work

Does anyone have information or a good understanding of how the OPS$ users work and operate under an Oracle SAP environment.

I would greatly appreciate some assistance as I have problems with my Brconnect and Brbackup within DB13 due to the OPS$ users.

I need info on how to permanently delete the OPS$ users and then recreate it, due to the fact that I have incorrect OPS$ users in some of the tables affected by the OPS$ users.

Below is the document I have prepared on recreating the OPS$ machanism. It helped me solve all my problem on DB13 and also on Schema owner connecting to database.

Hope this could help you.

Also refer to the following sapnotes:

1. 400241 : Problem withe ops$ or sapr3 connect to oracle

2. 134592 : Importing the SAPDBA role (sapdba_role.sql)

3. 361641 : Creating OPS$ users on UNIX

4. 50088 : Creating OPS$ users on Windows NT/Oracle

5. 437648 : DB13: External program terminated with exit code 1/2

----------

select owner from dba_tables where table_name='SAPUSER';

## If owner is not the sid you require, then drop the table SAPUSER

Drop table "".SAPUSER;

#or#

Drop table "domain\OPS$SIDadm".SAPUSER;

## IF THE ANSWER IS 0 ROWS SELECTED THEN CREATE THE TABLE SAPUSER

# Check whether OPS$adm user exist, if no then create it

create user OPS$SIDadm default tablespace psapuser1d temporary tablespace psaptemp identified

externally;

# if exist then drop it;

DROP USER OPS$SIDADM;

# Grant connect & resource roll to OPS$ADM;

grant connect, resource to OPS$SIDADM;

# Creat table SAPUSER

create table "OPS$SIDADM".SAPUSER ( USERID VARCHAR2(256), PASSWD VARCHAR2 (256));

# update "OPS$ADM.SAPUSER with the follwoing command

insert into "OPS$SIDADM".SAPUSER values ('SAPR3', 'sap'); #sap =

# Under NT it is required that user sapservice can also access the SAPUSER table. In order to avoid problems with the data consistency, it does not make sense to create an additional

SAPUSER table having the same contents. You should rather define a synonym. Check if a suitable

Synonym exists by using the following call:

SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME = 'SAPUSER';

# IF NOT THEN CREAT IT

create public synonym sapuser for OPS$SIDADM.SAPSUER;

# if synonym already exists drop the existing synonym by the following command

drop public synonym sapuser;

#If another name is returned as first value:

DROP SYNONYM "".SAPUSER;

# AND CREAT it again with above command

# To allow access to the synonym (or the associated table), a grant needs to be executed.

The authorization for this has only the ops$ user who is the owner of the actual table - that is ops$adm.

Therefore, you need to log on with the corresponding operating system user (adm) and execute the following commands:

CONNECT /
GRANT SELECT, UPDATE ON SAPUSER TO "OPS$SAPSERVICE";

# Now you can recreate the synonym (not PUBLIC, if possible):

CREATE SYNONYM "OPS$SAPSERVICESID".SAPUSER FOR "OPS$SIDADM".SAPUSER;

CREATE SYNONYM OPS$SAPSERVICESID.SAPUSER for OPS$SIDADM.SAPUSER;

# COMMIT AFTER COMPLETION of the activity & restart the DB

SAP Language Error when logging in after Upgrade to 40B

we have recently upgraded our system from 3.1H/Oracle 7.3.3/HP-UX 10.20/CIN 2.1A to 4.0B/Oracle 8.0.4/HP-UX 10.20/CIN 2.2A.

Upgrade went fine without any major hassles.

After upgrade when I am logging in it is giving a message in an information dialogue box "Specified Language has not been installed completely".

How to correct the error ? Everything is fine other than this.

I also got the same error for the same situation.

Here is the solution:

The reason for this is that table TCPDB was not maintained in your system before the upgrade and the upgrade process was unable to import the special texts as it couldn/t find the correct codepage ( in TCPDB ).

This can be rectified by the following:

Logon to 000 client

1) Run program rscp0004 in transaction se38 and this will give u options to insert a codepage. Look for codepage 1100 in the list and press F2 on this line as suggested, to insert the codepage.

2) In transaction SMLT check the 'status' of the installed languages. You will probably find that its the 'special texts' that were not imported successfully ( because the codepage could not be found in TCPDB at the time of the upgrade )

3) Schedule a 'full' import of the 'special texts' for the languages that are affected. Plsease note that when scheduling these imports, the options for Customizing and Documentation are automatically ticked for selection. Please remove these to leave only the Special Text selected.

You can observe the progress of the imports with sm37. After successful completion, you can logon again and there should no longer be an error.

Comparing two SAP clients

Compares Customizing objects in two logical systems with transaction SCU0.

(clients in either the same R/3 System or different ones).

To compare objects, start the Customizing Cross-System Viewer in the logon client (client of the system in which you are logged on) and then logon in the compare client (client to be compared).

The Customizing Cross-System Viewer compares Customizing objects by the following criteria:

- Project IMG

This option shows changes in your project.

- Application components

This option compares Customizing objects in specified application areas.

- Business Configuration Sets

This option concentrates on Customizing settings which are of particular importance for the processes in your company.

- Transport requests

This option shows the objects which would be overwritten by a transport.

- Manual selection

In this option, you specify which objects are compared.

The compare client security level must be:

0 (unrestricted), or 1 (no overwriting)

You can set this in the client maintenance SCC4.

You must also create a Remote Function Call link in SM59.

Find Your SAP Transport Request Number Even If You Forgot

If you happend to be one of those who forgot the transport request number of your abap program.

You can easily find it via the Versions Management.

Steps :-

Transaction SE38

Filled in your ABAP program name.

Then click Utilities -> Versions -> Version Management

SAP system will display this sample list :-

Versions: Report source ZPROGRAM

Version Cat Fla SAP Rel. Arch Request Date Time Author

Version(s) in the development database:

activ

46X

01.08.9999

15:21:56

SAP

Version(s) in the version database:

00002

00001

46X

ABCD123456

01.08.9999

00.00.0000

15:52:43

00:00:00

SAP

SAP BASIS

Click Below

Monday, March 15, 2010

BASIS MATERIAL

Friday, November 23, 2007

Saturday, October 13, 2007

Blog Archive