RC 6 or RC 14 While Implementing Enhancement Package 3...

Just a note to you guys out there implementing Enhancement Package 3.
Basically this applies to anything imported using SPAM/SAINT.
If you run in to errors that stop the import process in any of the phases, just restart the import. Most of these are timing problems or miscellaneous quirks that are corrected automatically when you retry.

Hope this helps...

Syntax error in program SAPFGIDB in step XPRA Enhancement Package 3...

When performing the Enhancement Package 3 for ERP 6.0 upgrade, during step XPRA we ran into the following error message:

Error in the ABAP Application ProgramThe current ABAP program "RGICGLU1" had to be terminated because it has come across a statement that unfortunately cannot be executed.The following syntax error occurred in program "SAPFGIDB " in include "FGIDBF26" inline 240:"No component exists with the name "WRITE_SI_FOR_BCF". ."

After doing a lot of digging I found a reference to "WRITE_SI_FOR_BCF" in SAP Note 1153947.
The problem is, all of the changes listed in the note had already been applied to our system through support package 14 for SAP_APPL. It seems the upgrade will cause these changes, particularly steps 4 and 5 in the solution in Note 1153947.

After manually re-implementing steps 4 and 5, the upgrade finished successfully.

I hope this helps...

Error during Upgrade to Enhancement Pack 3 for ERP 6.0...

When Upgrading to Enhancement Package 3 for ERP 6.0, you may run into an error during the DD Activation Phase for EA_APPL. The objects that my upgrade kept failing on were the table EMMA_BPC and the view V_EMMA_BPC. The problem is that the view is built with a field that no longer exists in the source table. A quick consistency check in SE11 will tell you that.

The solution is to register V_EMMA_BPC, remove the erroneous field (CLASSJOB), and activate both the view and the table.

Then just restart your upgrade from where you left off.

You have no idea how much of a headache this was causing me the past few days.

UPDATE: This may occur on several different views on tables changed by Enhancement Pack 3. I recently ran into this same problem with view J_1AVEBRCH which had 2 erroneous fields.

Hope this helps...

ASP.NET v2.0.50727 is not present in Web Services Extension in IIS manager...

ASP.NET v2.0.50727 is not present in Web Services Extension in IIS manager.
How do you make it appear and set it as an “allowed” service?
Open up a DOS command prompt and run teh following command:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe – i

or for 64 bit

C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe – i

ASP.NET will register itself and show up in Web Service Extensions

Hope this helps...

Juniper VPN Timeout Issues / iTunes Conflict

If you have iTunes installed on your laptop it is possible that it may have a conflict with the Juniper VPN client.
Typically this will manifest itself by killing your connection within 30 seconds to a minute after connecting.
The problem is that the ‘Bonjour’ music sharing service (an add-on to iTunes) changes settings with DNS (techie geek stuff) and causes the connection to drop with the VPN.

To resolve this, the ‘Bonjour’ service needs to be turned off and disabled.
Don’t worry, you will still be able to use iTunes to listen to music and copy over to your MP3 player, etc.
Steps to turn off and disable ‘Bonjour’:
1. Go to Start->Run
2. Input ‘services.msc /s’ into the command line (without the tic marks)
3. In the new window that opens up, scroll down the selection list to the right to find the ‘Bonjour’ service
4. Right-click on the ‘Bonjour’ service and select ‘Properties’
5. In the ‘Startup Type’ drop-down, select ‘Disabled’
6. If the service status is ‘Running’ or ‘Started’ select the ‘Stop’ button
7. Click the ‘Okay’ button
8. Close the services window

After doing this, attempt to connect to the VPN again, and you should have more success.

Some Memory Settings to Help with Swaps...

If you are running a Central Instance on a server that is also hosting the database, you may run into a problem with high swaps as seen in transaction ST02. The problem is that typically when SAP is installed, the default settings will allocate all of the system memory to SAP, leaving nothing for the database or other applications that may be running on the server. This will mean your page file will need to be very large (sometimes 3x the amount of system memory) in order for SAP to even start up.
If you are in this situation, try the following:

First, you will want to dictate to the database how much memory to use.
With SQL Server 2005, I prefer to allocate 6 GB of system memory as long as the system has 16 GB or more installed. SQL Server Management Studio is the tool to use to do this. Check with your RDBS guidelines to see how much your database host is required to have available and do not go under that.

Secondly, you will need to decide how much memory to assign to SAP.
You can assign the balance of the system memory to SAP, but if you have other applications that run on the system you will want to take that into consideration as well. In a system with 16 GB of memory that has 6 GB dedicated to the DB, I assign 10 GB of memory to SAP. This is done so by setting the PHYS_MEMSIZE parameter (MB) in the Instance Profile. I have a few systems with two Central Instances installed on the same 16 GB server, so I assign 6 GB to SQL Server, and 5 GB to each SAP instance.

Third, if you are still getting high swaps in ST02, you will want to look at the settings of each buffer parameter.
Inside ST02 under the "Current Parameters" button you will find what parameter settings you are running with. the defaults are supposed to be a good starting point for the typical SAP install, but here are the parameters I like to set:

rsdb/ntab/ftabsize = 60000
rsdb/ntab/entrycount = 40000
rsdb/ntab/irbdsize = 12000
rsdb/cua/buffersize = 6000
rsdb/obj/buffersize = 8192
abap/buffersize = 600000
zcsa/table_buffer_area = 60000000
zcsa/presentation_buffer_area = 8800000

Using these settings I rarely get high swaps in my SAP systems, but you will need to study each parameter and tweak them for your specific install.

I hope this helps...

ADS RFC Test Results: Forbidden

We recently ran into another issue with ADS on a different client site.
When running the Connection Test from SM59 for the ADS RFC, we came up with the result "Forbidden."

This will happen if you also get prompted for credentials when you call http://wsnavigator.
If this is the case, you will need to alter the security settings for the application/service.
Open your Visual Admin tool and to go Services>Security Provider.
Choose Policy Configuration > sap.com/com.sap.engine.services.webservices.tool~wsnavigator
Select the tab Security Roles. The applied security role for WSNavigatorRole needs to be "all."
The ADS RFC Connection in transaction SM59 should work now.

Hope this helps...