If you’ve ever encountered the following error message, check the following.
1. It’s a known issue and SAP is providing a solution with 7.01 SP6 release. (check sap note 1386141)
2. In order to have workaround for below SP versions, You have to deploy the par file. (“objbased.par for 7.01 SP5″).
3. First, please backup the old “com.sap.portal.navigation.objbased.par” PAR file, from the file system directory:
…\j2ee\cluster\serverX\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp (you will find it with a .bak suffix…)
4. Deploy the par file into your portal using the “Archive Uploader tool:
- Navigate to ‘System Administration’ -> ‘Support’ -> ‘Portal Runtime’ -> in the “Portal Anywhere” Admin Tools section, navigate to ‘Administration Console’ -> use the ‘Archive Uploader’ to deploy it.
5. After deploying the file, please recheck the scenario.

1. Login/disable_multi_gui_login
Controls whether multiple logins are enabled or disabled. 0 = enable 1 = disable
2. Login/multi_login_users
Here a list [user IDs] can be deposited that would allow users a multiple login even though the multi login is generally disabled. The multiple login information are stored in the table URSR41_MLD.

You could use CCMS or RZ10 to change profile parameters. Refer here for detailed steps of configurations.

Refer here for details of other parameters in system profile.

SCU3 transaction is used to see the IMG change logs for modified objects.

If your table change log is not active, it will gives you a message that “table logging is switched off”.

This particular setting can be changed in the following path :-

IMG-> Basis Components -> System Administration -> Tables changes recording

You can log changes made to the following tables:
- Control tables (system logic control)
- Customizing tables

What is recorded is always in the form of complete “before” images, that is, all entries as they appear before the changes.

The recorded data is compressed without buffering, and this is not an appropriate method for recording and managing large amounts of data. Activating logging impacts on performance as it entails twice as many database updates as would otherwise be the case, and the database storage load is also increased substantially.

It is recommend that you use logging for your production clients and Customizing clients so that you can see exactly where Customizing tables have been changed. Other than the reasons above, it is not recommended that you use this tool for application tables.

Two conditions have to be met for a table to be logged:

1. The table has to be selected for logging in the Dictionary. Go to SE11.
(see Dictionary -> Table maintenance -> Technical configuration).

2. Logging also has to be set in the system profile. Use tcode RZ10 and Refer Procedures and Configurations below.
Set the rec/client (note the use of lowercase characters) profile parameter to one of the following values :-
- OFF: no logging at all (effectively a central system switch)
- nnn: logs client-specific tables in client nnn only
- mmm,nnn,ppp,…: logs client-specific tables in the named clients
- ALL: logs all client-specific tables in all clients.

Caution: Only in exceptional circumstances is it appropriate to use the ‘ALL’ setting. If, for example, the profile parameter is set to ‘ALL’ when you upgrade all test clients (including 000, the SAP client), these changes are recorded in the system log file. This reduces performance and requires a lot of database space.

The default setting is OFF (no changes are logged). If logging is set in the ABAP Dictionary, changes to client-indepedent tables are always logged unless rec/client is set to ‘OFF’.

Procedures and Configurations
1. Call the CCMS profile maintenance tool by choosing CCMS
2. ® Configuration ® Profile maintenance. Alternatively, call Transaction RZ10. Specify the name of the profile whose parameters you want to change in the Profile field.
3. If you want to change the name of the file in which the profile should be activated, check Administration data and choose Change. Once you have made the changes, choose Copy.
If SAP System profiles are imported automatically, the system creates administration data automatically.
4. Maintain the most important profile parameters by checking Basic maintenance and choosing Change. Once you have made the changes, choose Copy.
5. You can create, change or delete all parameters in a profile by choosing Extended maintenance. Once you have made the changes, choose Copy.

Note: You can switch between Basic and Extended maintenance at any time. Changes to profiles are adopted when you save them to the database.

You can subsequently change and switch SAP profile parameters for instance profiles without having to restart the system.

To switch profile parameters:
1. Enter the profile name in the input field of Transaction RZ10 and choose Profile
® Dyn. switching ® Display parameters.
The system displays a list of memory management parameters that can be switched.
2. Change the relevant profile parameters using basic maintenance (as described above) and save them.
3. On the profile maintenance main screen, choose Profile
4. ® Dyn. switching ® Execute.From the list of active application servers, choose an application server and confirm.

The profile is used immediately after the change; you do not have to restart the system. At the end, the system displays a log for parameter switching.

In standard SAP ESS application, the “Used Quota” field in ESS application is evaluated based on the Time Management Absence Quota Deduction rules configurations. One could also customize the quota deduction based on their own requirements in BADI PT_QUOTA_DEDUCTION if neccessary.

There are two important things to take note while configuring for quota deduction.
1) Configure a list of absence quota types for the leave types and set the deduction priority.
2) Check if the “Quota type sequence for further deduction” is set correctly.

• No further deduction – The system will only deduct from the list of quota types configured and show “not enough quota” in the ESS if the quota has exceeded.
• Sort All Other quota types in ascending orders – The system will deduct from the quota types configured If quota exceeded, the system will retrieve is there’s other quota left in user’s IT2006 in ascending order and deduct from there.
• Sort All Other quota types in descending orders – The system will deduct from the quota types configured. If quota exceeded, the system will retrieve is there’s other quota left in user’s IT2006 in descending order and deduct from there.

“Unable to perform request. Try again and if the problem persist. Inform your administrator”

There could be different reasons to hit the error above. As for my scenario, I actually checked their portal account and R/3 accounts validity and to find out that the R/3 userid is only valid till 30 Dec 2009 which caused the problems.

Since she’s making a copy of the role from standard MSS role, I’ve categorize the tasks to be carried out in the following.
1) R/3
a) A new R/3 role and authorization profile need to be created in R/3. One could just make a copy of the standard MSS one.
b) Configure homepage frameworks in the following IMG path to tell the systems what are the portal services allowed for this new MSS role.

Cross Application Components -> Homepage Frameworks

2) Portal
A new role need to be created in portal UME and mapped to the MSS group (if UME is connected to R/3 via ABAP link, the roles in R/3 would appear as a group in User Administration).
Make sure the Worksets, iView and Pages are linked correctly together to the new role.

2) Run easy access menu.
Easy access -> Payroll XXXXX (Country name) -> Info system -> Employee -> Payroll annual display

3) Write a custom program/reports to read payroll results from PCL1 and PCL2.

1) Open the services tree in Visual Administrator.
2) Go to “Log Configurator” service.
3) On the “Runtime” tab, in the right-hand pane, select the “Locations” sub-tab. Look at the “Log Controllers” tree.
4) Expand to: ROOT LOCATION/com/sap/netweaver/bc/uwl.
5) Click “uwl”.
6) Change the severity to level “All”.
7) Click the “Copy severity to subtree” button to update the change to all subcomponents.
8 ) Click the “Apply” button to save changes.

The UWL log files are located in the following directory: /usr/sap//JC/j2ee/cluster/server/log/applications/sap.com/uwl

1) Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the ‘Employee Infotype’ radio button.
4) Select the ‘PS Structure Infotype’.
5) Click on Create… A separate table maintenance window appears…
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8 ) Go back to the initial screen of PM01.
9) Click on ‘All’ push button. It takes a few moments.
10) Click on ‘Technical Characteristics’. Infotype list screen appears
11) Click on ‘Change’(pencil) button
12) Select your Infotype and click on ‘Detail’ (magnifying glass) button
13) Give ‘T591A’ as subtype table
14) Give ‘T591S’ as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on ‘Infotype Characteristics’ … Infotype list screen appears
18) Click on ‘Change’ (pencil) button
19) Click on ‘New Entries’
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype’s infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirement…
25) In the PM01 initial screen…Select ‘Screen’ radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select ‘Layout Editor’ and click ‘Change’.
27) Screen default layout appears…here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Don’t forget to ‘Activate at every level)