SAP Netweaver XI Components - What are the Components of EXchange Infrastructure

You can find the basics of SAP Netweaver XI Exchange Infrastructure here. As mentioned earlier, SAP NW XI is helpful in connecting different vendor systems SAP or Non SAP systems which have been implemented on different platforms such as ABAP, JAVA, .NET etc. The SAP Netweaver Xchange Infrastructure (XI) has many components. Lets have a brief look at the components of the SAP XI and how these are used in the XI Integration process:

1. At the outset, the user needs to define the SAP systems in the systems landscape in 'SLD'. Once this is completed, one needs to define the interfaces in the XI Integration Repository at the design stage. It is important to note that the data in these different systems may not be in the same format. This description of the data will need to be defined in the data mapping.

2. The components, interfaces and mappings are defined in the 'Integration Repository' during the configuration phase of SAP XI, which determines the integration processes in the system landscape called logical routing. This is stored in the XI Integration Directory.

3. The next step in the XI Integration process is to transfer application specific content. This can be achieved using XML Schema for transferring messages between sender and receiver. IDOCs, files etc are used to determine the data structure.

4. So how does the entire process of SAP NW XI Integration work once it is setup? When an inbound message is received at run time, the integration engine of the integration server checks the configuration of the integration directory. The configuration data defined earlier is used to determine the receiver of the message. In that sense, the integration server acts as the central point of communication and distribution of XML messages.

5. Lastly, SAP XI 3.0 works in conjunction with the SAP Web AS Server 6.40. SAP now uses JAVA as a standard and Java administration tools need to be used to manage the Integration Directory and Repository.

I will discuss another important topic of connecting different systems to SAP Netweaver XI tomorrow.

SAP Message : TP_CANNOT_CONNECT_SYSTEM

Using spam, trying to import SPAM UPDATE, I get the above message together with TP_INTERFACE_FAILURE.
1. tp works fine when I am doing transports (tp import devk90000 qas client=400 u1 or addtobuffer).
2. niping -t SELFTEST works fine

I worked through notes 44946 and 96907, but could not resolve the issue.

The support packages have been uploaded from the DEV box into the QAS queue. The DEV and QAS boxes are in the same centre on the network, by fibre. I am working on QAS.

I get this message in QAS:-
"SAP system is waiting for the inclus. in transport domain"

When trying to update the config from DEV client 000, I get this message:-

System DEV is unknown in the Transport Management System

Diagnosis
An error occurred in the TMS communication layer.

System: QAS.DOMAIN_DEV(000)
Function: TMS_CI_CHECK_ACCESSTOKEN
Error: UNKNOWN_SYSTEM (DEV)

System Response
The function terminates.

Procedure
Log this system on to the Transport Management System.

If this error occurs in the function TMS_CI_CHECK_ACCESSTOKEN, then the TMS configuration was deleted in the R/3 System QAS.DOMAIN_DEV(000).

Configure the TMS in this R/3 System again.

You need to:

1. logon to the transport domain controller with admin user in client 000.
2. Run STMS
3. System overview
4. select QAS
5. Menu line option "SAP system" --> "Approve"
6. Distribute configuration

When you are logged on the transport domain server and run STMS --> System Overview. Is QAS listed? If so, select it and perform the checks under "SAP Systems" in menu line.

If they are not successful you might want to try the following to configure the TMS on QAS from scratch.

First delete QAS from system overview on the domain server.

Then do the following steps...

In your QAS system in client 000.
Run tcode SE06 --> Database copy or Database migration --> Perform post-installation actions.
Then confirm that you want to delete all old CTS/TMS config and type in QAS as source system for the database copy.

Then run STMS again and type in the correct data for the transport domain controller.
Logon to the transport domain controller in client 000. Run STMS. Open system overview.
Choose the SID of the QAS system and click on "SAP System" in the menu and choose Approve.
This will add the QAS system to your TMS config again.
Perform the checks from menu line "SAP Systems" again.

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 thro 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.

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 to execute the query
3. Highlight the first job in the list and press the + to change the job.
4. Examine the Exec Target field.
a. If the box is empty, press to exit
b. If the box is not empty, then clear out the contents so the field is blank and press + 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 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 +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 to go to the *import* Overview.
3. Double click on the 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 to save.
6. Select the transport that was just added to the queue and press + to start the import.
7. In the Target client box, enter the productive client of the newly created system. Press to save.
8. Press the 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 +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 +S to save.

Import Users
STMS
1. Press to go to the Import overview
2. Double click on the of the newly refreshed system.
3. Press 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 . 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 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 +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 + to modify the job.
3. Press the Step button.
4. Select the RSCLXCOP line and press ++ to modify that step.
5. In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
6. Press +S to save the changes
7. Press to go back to the main job screen.
8. Press the Start condition button.
9. Press the Immediate button.
10. Press +S to save the changes
11. Press +S again to save all the changes to the job.
12. Job will start immediately once saved. Press to refresh the list of jobs
13. Continue to press 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 +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 to leave *this* screen.
3. Select the Profile field and press 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 +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 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 to create a *new* operation mode.
12. Enter a name and *short* description *for* the operation mode
13. Press +S to save.
14. Press to create a *new* Instance
15. From the Settings menu, select Based on current settings, then New Instances, then Set
16. Press 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
21. Highlight the 00:00 at the bottom and press
22. Press the Assign button.
23. Press to select the operation mode created above.
24. Press +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 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 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 + 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 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 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 Press +S and then 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 .
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 +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 +S to save
7. Press *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 \\\sapmnt\\SYS\EXE\RUN\TF60SERVER.EXE
4. Double check the target host and gateway point to the correct server
5. Press +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 to execute
3. Select option BSI version 7.0
4. Press 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 print out 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 +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).

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)

---

What are user groups and how can we use them?

Transaction SUGR - have a look. Purpose for example is to give certain system admin rights to unlock / change password only to a given user group. You assign user group to an user id via SU01.

User group can be used for different reasons and in different way.

In the latest versions of SAP, actually two types of usergroup exist, the authorization user group and the general user groups.

Naturally the main reason of user groups is to categorize user into a common denominator.

The authorization user group is used in conjunction with S_USER_GROUP authorization object. It allows to create security management authorization by user group. e.g. you can have a local security administrator only able to manage users in his groups, Help-Desk to reset password for all users except users in group SUPER, etc...

The general user group can be used in conjunction with SUIM and SU10, to select all the users in a specific group. User can only be member of one authorization user group but several general user group.

One of the Primary uses of user groups is to sort users into logical groups.

This allows users to be categorised in a method that is not dependent on roles/AG's/Responsibilities/Profiles etc.

User Groups also allow segregation of user maintenance, this is especially useful in a large organisation as you can control who your user admin team can maintain - an example would be giving a team leader the authority to change passwords for users in their team.

The most important factor identified is that the lack of user groups is an indication that there may be problems with the user build process. This is very "fuzzy" but is a bit of a warning flag.

The Auditors job is to provide assurance that SAP is set up and administered in a way that minimises risks to the financial data produced. If the only thing they have picked up on is the lack of usergroups then you will be fine.

If you are in any doubt whatsoever ASK THE AUDITOR. They would have produced a report listing why they feel there is a risk by not having User Groups implemented. If you feel that the risk is mitigated by other measures then let them know. It works best as a 2 way process and both parties can learn something.

How to delete expired roles?

Here are 3 notes you may want to review to see if there is any helpful info, plus some documentation that may be helpful for others....we are going from 40B to 47 and have had a few issues with role deletion

Notes: 312943 504412 & 313587

Additional info

First, the report PFCG_TIME_DEPENDENCY is functioning as designed. It was not designed to remove activity groups.

Second, in transaction SU10 you must have the valid from and valid to fields filled in with the actual dates, 04/08/2002, in order to remove the invalid activity group. You need to be sure that the remove user radio button set in the role tab. But in the profile tab, the add user radio button is selected by default. What you have to do is go to profile tab and select the remove user radio button. You have to make sure both role and profile has the same radio button selected, i.e. remove from users. Only then when you click save, it will allow you to delete the role from user.

In transaction SU10, you need to complete the following steps:

1. Click on the Authorization data button.
2. Entry the users name, latimerc
3. Click on the execute button.
4. Put a check in front of the users name.
5. Click on the transfer button.
6. Now highlight the user.
7. Click on the pencil button.
8. Click on the Activity Groups tab.
9. Enter the profile name (PM_NOTIFICATION_PROCESSOR).
10. Enter the valid from and valid to dates (04/08/2002).
11. Change the radio buttons to remove user from both the Activity Group and Profile Tabs.
12. Click on the trash can.

Transport Tables between Clients

Use report RSCLCCOP to transport user master records, profiles and authorizatons between clients in an R/3 system.

Start RSCLCCOP from the target client which the users and authorizations should be copied.

Do not use this report if the target client contains some users and authorizations you want to preserve.

Copying table entries from client 000

I need to copy table entries from client 000.
I have identified which entries I need to copy through running RPULCP00 but I don't know how to move the entries.

The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields

You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.

Transport Tables between Clients

Use report RSCLCCOP to transport user master records, profiles and authorizatons between clients in an R/3 system.

Start RSCLCCOP from the target client which the users and authorizations should be copied.

Do not use this report if the target client contains some users and authorizations you want to preserve.

Copying table entries from client 000

I need to copy table entries from client 000.
I have identified which entries I need to copy through running RPULCP00 but I don't know how to move the entries.

The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields

You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.

Mass Maintenance of Users Profiles

Goto transaction code SU10

Select your SAP User by Address data or Authorization data.

With the users you want to change selected, click :-

User -> Change -> Profiles

Filled in the Profiles and click save.

How can I create multiple User Id at Random

We usually created Id though SU01, it only one by one.
Can I create multiple user id having same profile at once.

Yes you can, use tcode SCAT. First, make sure your client setting (SCC4) is enabled with ' X eCATT and CATT allowed'. Just in case your Production disabled this.

- Then, you need to create a simulation (test case) of creating new user id by calling tcode
SU01 later.
- Test case must start with Z, example ZCREATE_NEW_USER. Create this case, put title and
choose component as BC (basis components).
- Save and choose Local if you dont want to transport it or choose a dev. class (example ZDEV)
if you want to transport it later.
- Go back and click Change button. Then key -in Object as example SU01, and choose Record
button on top. When it prompts to enter Transaction code, key in SU01 (if for roles,
key-in PFCG) and begin recording. As usual in SU01 create 1 user id, dept field, password,
roles, group and so on.
- Make sure you press Enter on each field because we want to capture the value/object and
SCAT is a bit stupid if you become familiar later....but still useful...indeed.
- You will see a clock on the bottom which means the recording process is on going.
Once done, click Back button and press End button to end the recording.

Note - I noticed you said the profiles are all the same. Then this is much easier...no need to enter the roles/profiles, just duplicate this ID and change the name, dept and password only.

Okay..first stage has finished. Then double click the Object to begin inserting parameters. Then you will see an object for each fields that you run from SU01. Choose the right field example user id (BNAME) and choose button 'Insert Import Parameter (F6)' and you may click Next Screen to 'watch' what have been recorded and proceed to choose several other objects like password field (PASSWORD1, PASSWORD2), roles field (AGR_NAME), group field etc. If you happen to choose the wrong object, then you can reset back (Edit -> Reset Parameterization). You may see so many junk fields captured and this is because SCAT records every steps/dialogs.

Once done, choose Back and save this case. Then you need to click 'Goto -> Variant -> Export' and save it. After that use Ms Excel to open it and begin inserting all other user ids. Save and close. Remember to close this file because SCAT will use it.

Then last one, get back to SCAT and click button execute, processing mode chose Background, choose external file 'the one you created with Excel' and execute. At this moment don't use tcode SU01 bcoz you may interrupt the simulation. Wait for the logs. If you see reds then error was
happening.

Hoping this will help you. I have done (Sap 4.6C) this to create thousands of user ids and also thousands of roles/profiles (pfcg). I heard with Sap 4.7, the SCAT has so many extra features...

Changing the default password for sap* user

You are trying to change the password for sap* user, however when you go into su01 and enter sap* as the user name, the following message is displayed, user sap* does not exist.

You can delete the SAP* user using ABAP code :-
Delete from usr02 where bname = 'SAP*' and mandt = '***';

Where '***' means your client no.

Then login to your client using password SAP* and password PASS

However, if you delete it, then it will automatically created once again with password PASS

The userid, SAP*, is delivered with SAP and is available in clients 000 and 001 after the initial installation. In these 2 clients, the default password is 07061992 (which is, by the way, the initial date when R/3 came into being...). It is given the SAP_ALL user profile and is assigned to the Super user group. When I say it is "delivered" with SAP, I mean that the userid resides in the SAP database; there are actually rows in the user tables used to define userids.

If you delete the userid, SAP*, from the database, SAP has this userid defined in its kernel (the SAP executable code that sits at the operating system level, i.e., disp+work). When this situation exists, the password defined in the SAP code for SAP* is PASS. This is necessary when you are performing client copies for example, as the user information is copied at the end of the process. You can sign into the client you are creating while a client copy is processing using SAP* with password PASS (but you should have a good reason to do this - don't change anything while it's running).

Anyway, if the SAP* userid is missing, you can sign in to the client you want and simply define it using transaction SU01 and, as I stated above, assign it to the SUPER user group and give it the SAP_ALL profile. You define its initial password at this point. If you've forgotten its password and don't have a userid with sufficient authorization to create/change/delete userid,
then you can use the SQL statements to delete it from the database and then you can use SAP* with PASS to sign back into the client you want to define it in and recreate it.

There is also a profile parameter which can override the use of SAP* with PASS to close this security hole in SAP (login/no_automatic_user_sapstar). When this parameter is defined either in your DEFAULT.PFL profile or the instance-specific profile and is set to a value of '1', then the automatic use of SAP* is deactivated. The only way to reactivate the kernel-defined SAP* userid at this point would be to stop SAP, change this parameter to a value of 0 (zero), and then
restart SAP.

The default password for SAP* is 06071992. (DDIC has 19920706)

How to apply OSS notes to my R/3 system?

In order to fix one of the problem in R/3 system, SAP will asked you to download an OSS notes which is a ".car" file.

To work with a CAR File do the following at OS Level:

Get into OS as adm

Copy the .CAR file to a Temporary Directory.

Uncompress the file with SAPCAR

Copy the the data file generated in the data transport directory
( ej: = /usr/Sap/trans/data).

Copy the the cofile file generated in the cofiles transport directory
( = ej: /usr/Sap/trans/cofiles).

Run transaction STMS

Upload the support package with SPAM transaction and the support package will show "New support packages".

**********

Examples of CAR command :-

1) UNIX only:

Log on as user adm.
cd /usr/sap/trans
CAR -xvf tmp/.CAR -V

2) Windows NT only:

Log on as user ADM.
cd \USR\SAP\TRANS
CAR -xvf TMP\.CAR

This Will create two(2) FILES

After you run SPAM you MUST run STMS and check the transport queues

**********

As per 315963 note you can direct made the changes in the program or you can apply the support pack.

a) If you want to apply correction then first you need to register the object in SAP, so that you will get the Access key and then you can make the changes.

b) If you want to import the support pack then you need to down load from SAP market-place. and this is in CAR file. and then you need extract the same using CAR utility.
ex: CAR -xvf abc.car

or

you can directly apply the patch from SAPGUI, login to 000 client and then you can load the patch from Presentation server.

Also check what is your current basis patch level?

For example if you want to apply patch 07 and you are having 05 then you need to apply 06 and then apply 07.

What is mean by OSS how to work on that?

OSS are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.

In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.

For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.

Access the SAP Support Portal:

http://service.sap.com/

- Keys and Requests

-- Request license key

--- Follow the Steps 1 to 5 of the License keys for SAP Business Suite

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

Follow this step to obtain the Program Access key:

Menu Path: System -> Services -> SAP Service (Transaction code OSS1)

Login in with your OSS ID and Password

Click the Registration button

Click Register Object

Double click R/3 Value Contract

Fill in the Object Registration for Installation:

For e.g.
PGMID/Object/Name: R3TR FUGR MIGO
SAP release: 46C

Finished, click the Register button

Select the Key number and use the Copy and Paste short key to copy the Access key

You are now able to modify the SAP standard program.

Finished the modification, do remember to transport it to the production system after all the necessary testing.

How do I find out the current patch level in SAP R/3 4.7

ou can use either of these two methods:

1: Follow the path

System --> Status --> Component Information (The Magnifying glass button in the SAP System Data section)

2: Use the Transaction code ---- spam

spam(Support package manager) --> package level

Steps to Start Your Database After Kernel Upgrade

Do these steps to start your database:

1. Open command prompt

2. Give command: SQLPLUS "/as sysdba"
If its giving message connected to idle instance then proceed:

3. Give command: startup open
If its giving error that database is already open, shut it down first. Then first check what database process is up and running.

4. Try stopping the database: shutdown immediate.

5. Follow step 3 again after shut down the database.

6. Exit from SQLPLUS

7. Run command on command prompt: R3trans -d
Check the results whether its still giving error or if it completed with 000 return code, then try starting SAP.

Follow the above steps.