The Service Management Experts
Menu

Basis

Home / SAP / Archive by category "Basis" (Page 2)

Basis – Can’t get your Email out of Waiting in SCOT?

Well, in one of my latest development activities I needed to send an email from my web application.  Now this isn’t as hard as I thought.  I’ll talk about that in another post.  What I have been having a hell of time doing is getting the email to send from my system.  Like everything Basis related, it’s always a challenge for me 🙂  Today is no different.  I’ve got emails that were getting into the SAPConnect queue, but were stuck in waiting status in SCOT.

Well, thanks for other pioneers that have gone before me, I was able to learn that there is a simple fix for this.  It all has to do withe time zone of the system.  Another little piece of data that I never thought about.  The time zone of your SAP system defaults to CET, while this doesn’t seem like a big deal, if your user has a different time zone set, then SCOT could take hours before the system clock reaches your time zone.

You have two options.  One, you can change your user timezone to match the system timezone.  Depending on what you have control over, this is certainly the easiest option.  Option 2 is to change the time zone of the system.  Since I control the system, I went for option 2.  If you’re curious, go to SPRO –> SAP Netweaver –> General Settings –>Time Zones –> Maintain System Settings.

So, if you find that your email messages are stuck in SCOT, check your time zone.  It could be a simple fix to an annoying problem.

Thanks for reading.

Basis – Getting Support Packs

Well, I had to move back into the world of Basis again.  SAP sent out a message a couple months ago basically saying you have to implement a bunch of OSS notes, or move your system up to a certain support pack level.  Well, needless to say, I’m way behind on support pack for my systems anyways.  This is partly intentional and partly just a lack of time.  The intentional part helps keep me accessible no matter what version of SAP support packs my potential customers have.  Well, since I have to contractually do this, it was a good opportunity to update my systems.  This posts talks about my challenges of getting support packs for my SAP system.

Well, support packs, in theory, are very easy to implement.  Transaction SPAM does everything for you.  Well, the challenge for me came in to get the actual support packs to implement.  As it turns out, anything after a certain date can only be acquired using Solution Manager (there’s a way around this that I found).  Now my problem is that I have a solution manager system, but it’s not really connected to anything.  I’ve used SOLMAN purely to get the access codes for system installation.  Now I know that SAP keeps hyping up SOLMAN, but to be honest for my purposes it has no value add.  So I went through and started to manually download all of the support packs I needed.

Even the download was tougher than I expected.  I dug around service.sap.com until I finally found the support “stack” table of contents to find out what packages are required.  Initially, I did it the hard way of downloading the packs I thought I needed, tried to implement, and found out it had more pre-requisites.  Well, I finally found everything I needed, but in my SAP Download manager, it showed everything under needing approval.

Well, I can only guess that if I had a fully functioning SOLMAN, I could do this, but instead, I went out and posted an OSS message to approve the packs.  Be sure to set the area as:  SV-SMG-MAI-APR  As it turns out, SAP will quickly approve these and let you just download them (Thank goodness for that…).  I did make a very brief effort to get the SOLMAN component working to allow me to do it from there, but I had no success, and no time to investigate it.

Anyway, I wanted to pass along these little tidbits.  My EHP4 system is still running after 36 hours, so who knows how long it will take to finish, but it’s rolling =)  Thanks for reading.

 

Network – Changing Internet Providers

Well, I discovered a whole new challenge recently.  We changed cable providers, and upgraded our internet.  It all seemed so easy.  A couple of minor tweaks, and everything would just keep working, right???  not so much.  Here’s what I discovered you need to remember when changing internet providers and still keep your SAP system exposed to the outside world…

Even if you don’t change providers, they might change the box for your signal.  In my head, that meant nothing.  When I went to connect to my SAP systems, it meant everything.  Here’s what I found.

1.  Changing providers or even changing modems can change your IP address.  So, if you’re changing things,  make sure you check this right away.  My previous post on this stuff talks about some of the steps.  www.whatismyip.com is your quick check.

2.  Now, a changed IP address unfortunately means that if you are using subdomains (like I am), you need to go to your host provider and change the IP address they are pointing to.  I hate this part because it can take up to 24 for the changes to circulate through the internet.

3.  Next up, I lost all of my expections.  So I needed to go into my router configuration and create/add the firewall expections (80XX & 32XX) for the web and for the gui connections.

4.  While you are in there, double check that the static IP addresses are still connected to your machines.  If you lost those too, re-add them.

Now, if you’re lucky, everything will be back to normal in a day.  For me, it took 2, because I didn’t catch that the IP address changed until a day later.  Short story, be sure to test right away from outside of your network to make sure everything is still working.  Good luck, and try not to change your internet provider if you can avoid.  ha ha ha

Basis – Debug Authorization

Here’s another chance for me to add to my notebook.  Adding debug authorization is a trick I often have to do in my development projects.

When you have your own system, one of the first things to figure out is how can I get the authorization to debug a program, or in my case a Web Dynpro application.  Now, you can certainly assign yourself the role of SAP_ALL.  But what happens when you want to test with a real user???  Well, you need to narrow down that Authorization.

So, simply add this authorization:
S_DEVELOP
Then fill in the following attributes…
OBJTYP: DEBUG
ACTIVITY: 1 & 2 & 3

I know, not really exciting, but I never know if it might help you…  it certainly is something I’ve used multiple times.

 

Basis – System License

I just discovered a very important, but very subtle thing.  SAP Hardware keys are case specific.  In order to use the system license, you need to enter it in correctly.

While to most of you, this doesn’t mean anything.  I just spent the last hour trying to get into the system I’ve spent the last month building.  I finally discovered that the license I created for the system had a lower case ‘W’.  The Hardware key used an upper case ‘W’.  UGH!!!  Anyway, as soon as I requested a new key, used the SAP* user to get back into the system, then used txn:  SLICENSE, installed the new file from SAP…  everything was great.  So, learn from me, hardware keys are case specific 🙂

I know this is a simple one, but take it from me, it can be important,

Thanks for reading,

Mike

SAP Basis – Generating a System Key from Solution Manager

Hey Everybody, I’m trying my hardest to simply change the instance number on my ERP 6.0 system (I’ll talk more about that in another post), but one of the things I tried was doing a system copy (unfortunately that also is causing me headaches), but it reminded me of another little tip.  How do you get the system key from solution manager.  Obviously, step one is to have solution manager, or access to someone else that does (a solution manager system key doesn’t need to be connected to your system.  You can call up any Basis friend, give them a little info and get a key that will work).

Now, on with the show:

After executing T-code SMSY in Solution Manager system, you need to do the following steps:

Create a system by right clicking on System entry and select Create new system.
Enter the System Name i.e., SID (3 chars)
Product = SAP ECC (select from the list)
Product Version= ECC 5.0 (select from the list)
Save the entries.
Select Menu Item “System—>Other Configuration” and enter the SID which you have created earlier.
Enter the Server Name(hostname)
Finally click on Generate “Installation/Upgrade Key Button ”

The system generates a system Key ,copy that system Key and paste it in the SAPINST screen when it prompts for Sol man Key.

That’s it.  Pretty easy, but still required…

Have a great new years eve, and remember as the new budget cycle opens up, if you need help with anything, or have use for one of our SAP Easy Button’s please let us know.

Thanks,

MIke

Variant Configuration Performance Tuning

This lesson is timely because I’m dealing with this issue right now at my current client.  Their model uses class nodes in the bill of material VERY heavily, so we’ve been noticing awful performance in CU50.  SAP does provide some solutions for variant configuration performance, take a look at the following note to get some additional ideas:

Note 917987 – General performance in variant configuration

Now, we have done a few things in an attempt to improve the performance.  First, we were using class type 200 with a reference characteristic.  I learned, for class nodes this is actually a no no, unless you check a box in configuration to redundantly store the characteristic value.  Here’s what SAP’s help says about it:

Class Maintenance

Using Reference Characteristics Only

This constellation cannot access the database directly to read the assignment records. All classified objects are processed sequentially.

In order to change it, you must check that little box up top for redundant storage.  Now the drawback of this approach is twice as many table entries.  For that reason, we chose to move the characteristic to be NOT a reference cstic.  The only issue this causes is that value for material number (in our case) will not be populated automatically.  Not a huge deal.

Now, we changed all of that stuff, and still no change.  this was disappointing.  After some debugging, we (using transaction SE30 for performance tuning) we found that the issue was with table KSSK.  Surprise, Surprise, it holds the class connections.  So we handed it off to basis.  They began by running statistics on all of the tables listed in the above OSS note.  Still no help…  finally, we needed basis to reorganize the tables and indexes for KSSK & INOB.  This may sound like a lot of mumbo jumbo, but if you ask your basis person it will make sense to them =)

Short story is that sometimes you can get performance without changing your model.  Now I don’t regret the changes we did, they will still be beneficial, but don’t forget about the technical aspects.

As always, if you need further help in variant configuration, please press the contact us button above and let us know how we can help,

thanks for reading,

Mike

Basis – Changing the Instance Number of an Installed SAP system

I’m back in basis land yet again. What I discovered is that in order to connect to multiple systems existing on the same server, they must have a unique instance number. After all these years, I finally understand what the instance number does =) Since several of my SAP systems exist in the same server name, I had to make a change. I installed everything in 00, not know any better.
Well after some internet research, I discovered how to do this (at least for the ERP systems).
1. Go to the profiles directory. For me it was: C:\usr\sap\<SID>\sys\profile\
2. There are 3 files in this directory that you need to visit. (keep in mind, depending on the parameters, you may or may not have things to update).
a.<SID>_DVEBMGS<NR>_<Server name>
b. START_DVEBMGS<NR>_<server name>
c. DEFAULT.PFL
For the 3 files, replace every instance of DVEBMGS<old NR> with DVEBMGS<new NR>, sapgw with sapgw, and SAPSYSTEM = <Old NR> with <new NR>.
3. Next rename the directory DVEBMGS<old NR> with DVEBMGS<new NR>
4. open up the command prompt cmd.exe
5. Execute the following command: C:\usr\sap\<SID>\sys\exe\uc\ntamd64\sapstartsrv.exe -r -s <system> -n <NR> -p C:\usr\sap\<SID>\SYS\profile\START_DVEBMGS<NR>_<server> -U .\SAPService<SID> -P <password> -q
6. Execute: C:\usr\sap\<SID>\sys\exe\uc\ntamd64\ntenv2reg Select the new service.
7. Now restart the server, and you should be able to start the system with the new instance number.
8. Don’t forget to update your logon pad to the new instance for the system.

Now, I tried these same steps on my 4.7 system, and I couldn’t get it to work. I’ll try it again later, and if I get it working, I’ll let you know.
Good luck,
Mike

SAP Data Loading… Still going

Wow… what can I say? I didn’t expect to still be loading data into my EHP4 system.  I’m working really hard to get a good baseline of data to cover the major areas.  last night, I spent my time trying to get materials to cost, so the cost will show properly on the service/production orders.  let me tell you, I’m not cut out to be a FICO consultant.  I’ve been digging for what feels like hours, and still can’t over come my error.  Tonight, I’ll take another pass.  I have to say, couldn’t have accomplished this much without GUI script, but I’ll be very glad to get the last of the data loaded into the system tonight (provided the material costing errors finally get resolved).
otherwise, getting geared up to start Web Dynpro is pretty excited.

SAP Transports – reusing dev and config between non-connected systems

For small shops, like me, it’s a lot of infrastructure to to have a bunch of systems mapped to each other.  In addition, I have multiple active versions of SAP in order to allow me to test for different customers.  In that case, it’s even more complicated.  So, if you’ve read any of my earlier posts, you know that I use virtual-box to maintain my different systems.  Infrastructure – Setting up SAP on a budget  Now, that leaves me to either add all of my configuration over and over every time I create a new system.  I don’t like that idea 🙂  So I found out that you can grab two files and place them in a new system and import them, and magically you’re configuration has moved.   Here’s what you need to do to use SAP transports to handle this for you:

In the source system, as long as you properly configured STMS and do not use local objects, simple release the transport you want to move.  You will find the files you need in 2 directories:
C:\usr\sap\trans\cofiles

C:\usr\sap\trans\data

the files are the transport #.  So grab those 2 files.  I use dropbox to move these files from virtual systems.  But you can use any method you choose to get the files where you need them.
next is to put the files back into the same directories in the target system.

Now, go to STMS, drill into the main system (not the virtual system)
go to the Import Overview, and double click into the main system
Use the menu:  extras–>other requests–>add

now type in the transport name from the source system.  <SID>k<num>.

if everything is configured properly, if will import it just like any other transport.

Hope you find this useful,

Mike