Blog – Page 93 – Paper Street Enterprises

OMWD – The key to material cost estimates

After lots of digging and some help from google, I finally found what I was missing to make material cost estimates. The following transaction all needed some tweaking in order to make my materials finally cost properly.

KA01 – needed to create a bunch of cost elements.
FS00 – needed to create some G/L accounts

the list of things to create, came from: OBYC & OKTZ. I had to dig through and use the error message to get to the right area, but for me, it was GBB, and my valuation area was empty, this finally led me to OMWD. the missing piece of my puzzle.

It’s a relief to finally have that working… now, on to posting some service order costs.

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.

Configuring the new SAP system – Enterprise Structure

Since I’ve spent so much time working getting my new EHP4 system up and running, I thought I’d talk a little about the configuration you need. Now if you read my last post, Transports in SAP – reusing dev and config between non-connected systems, you’ll see you can do this once and then move it around. But, you still have to do it once.
One of the biggest pieces is the enterprise structure. SAP provides you with one, but in general, you want a more robust structure, so you typically copy the existing one and then make changes. SAP has an entire menu in the SPRO configuration dedicated to this. they also have a group of transaction codes: EC01 – EC16 (I think). This is the shortcut.
Now to make the bare minimum, here’s what you should consider copying:
Company Code
Plant(usually do at least 2)
Sales Org
Distribution Channel
Division (usually do several of these)
Purchasing Org
Warehouse (if you use WM)
Shipping point (typically 1 or 2 per plant)
Storage Locations

Now keep in mind, even when you copy this stuff, you’ll still need to go into the assignments and make some changes. For example, when you create a new plant (I encourage you to copy), you’ll still need to go to the enterprise structure Assignment area, and connect the plant to the new company code (same goes for the sales org, purchasing org, etc.) Pretty much everything you need to worry about is in the enterprise structure configuration folder, but there are some exceptions.

1. If your company code is in a different country/currency than DE, you might need to maintain the tax classifications for the material and the customer. (this is in the Sales and Distribution–>basic functions–>tax area). You’ll also need to turn the company code on for materials management (otherwise you can’t extend a material to the plant if it’s in a new company code). It’s lots of effort, but when you’re done, it’s worth the work.

happy configuring..

Mike

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

Configuring Web Dynpro in SAP ERP

Well, since creating my new EHP4 system, I’ve had to do a lot of activities. For me, the most important was getting Web Dynpro working. I created this whole system with the intent of using it for webdynpro development. Anyway, again, no straightforward documentation that talks about what needs to happen. So, here’s my notes on configuring web dynpro in SAP.

First, you need to implement an OSS note:

Note 1461387 – Web Dynpro View Designer | Error in ICF node

After applying the note, go to transaction SICF and activate the following services.

/sap/public/myssocntl

/sap/bc/wdvd

/sap/public/bc/icons

/sap/public/bc/icons_rtl

/sap/public/bc/webicons

/sap/public/bc/webdynpro/*

/sap/public/bc/pictograms
/sap/bc/webdynpro

Now, you can use the layout designer for Web Dynpro. It’s that easy.

Hope this helps,

Mike

Installing SAP ERP 6.0 EHP4

Well, if have one complaint as a non-basis person, it’s that I wish SAP would just tell me what files I need to install something. For example, there were about 50GB worth of files that I copied off of DVD’s, just to find that I only needed about 1/2 of those. OH well, I get my system running. Now, if you care, here’s what you need for installing SAP ERP 6.0 EHP4 on a windows 64 bit operating system and Oracle database (I used 10.2.0.4).
Please note, the disks that I used may not be the most recent, however they work, and you can always upgrade your support packs/kernel later.

First thing you need is the installation master:
51038620 is the disk I used
51036902 – Installation Export
51036767 – UC Kernel (7.01)
51033272 – Oracle Client

Just a note on the oracle install, be sure that you use the sapserve.cmd to start the install, it does all the work for you. One things aobut this, the cmd file will only work if all the directories have NO spaces in the names. For example, oracle install won’t work, but oracle_install will. Just a little lesson learned.

Also, during the install, if you get the step about DB statistics, or anything related to the DB and you get a 1034 error, try this trick.

open up a cmd prompt.
type in the following:
sqlplus /nolog
connect /as sysdba
startup

when this finishes, try the step again. You may need to completely stop the installation, and restart the system, then do the sqlplus command.
Otherwise, it should go pretty smooth. With my system, I was able to finish the installation in about 12hrs + 2 hrs for oracle + 3 hrs for copying files. LOL

Anyway, hope you might find this helpful. For my basis friends, feel free to laugh at me… I know I stumble through this the hard way.
Mike

Configuring STMS – Transports you can collect

Anytime you create a new system for SAP development, you need to configure the transport management system (STSM). I’ve struggled with this in the past, but after enough trial and error I finally figured out what needs to happen. Please keep in mind, the system that I’ve configured is all about collecting the transport files so I can manually move them to other systems, I do NOT have a multiple system environment. Configuring STMS isn’t bad, just make sure you hit all the steps.

Start at transaction STMS
Menu: Overview–>System
Menu: System–>create–>virtual system

give your VS a name
green arrow back when you’re complete.

Menu: overview–>transport routes
Press Pencil to go into change mode
Drag the boxes of the actual system and virtual system into the big working window
Menu: edit–>transport layer–>create

Give your transport layer a name.
Menu: Edit–>transport route–>create

Enter in the Actual System, then the transport layer you just created, then the virtual system.

Finally save, and distribute the changes across all systems. That’s all there is to configuring STMS.

Good luck

Applying SAP Support Packs

I have had my basis hat on a lot lately, so I might as well cover another piece of the basis puzzle. For anyone like me, you don’t have a lot of time to figure out exactly how to upgrade the system, but you want the stability (at least usually) that comes with an updated system. For me, I was trying to upgrade my system to a point that my BSP application would be supported on the Mozilla Firefox browser. I’ll talk more about this at a later time (I’m still collecting details on that portion). Needless to say, I read an OSS message that said, get to support 19, and I was at 12. So today I thought I’d talk about applying SAP support packs.
Step 1. Figure out the components you’ll need to update, and what your current version is. If you go to system->status, and look at the detailed levels, you’ll see things like BASIS, ABAP, etc… based on the OSS message, you’ll what you need to update. Find the component, and then find the SAP naming convention. For example the BASIS stuff is KB700<XX>. This is important because it’s an easy shortcut to download exactly what you need.
Step 2. go to service.sap.com and head to the software area: and select the Search for Software Downloads. Take the naming convention from above and one by one, find the pieces you need. If you need a lot, it’s probably faster to go to the support section. Me, was only doing 6 files.
Step 3. Once everything is downloaded, log into SAP (your dev system/client) and go to transaction SPAM. Select the import and one by one, import each of the files you downloaded. Don’t apply the packs one by one… it’s a long enough process, so do the whole group at once.
Step 4. Once all the pieces have been imported, press the truck to start a new “installation”. you’ll have the options to select the area you want to update, for example BASIS. It will show you all the new imports and will lump them into a package. From here, just keep hitting OK. Give yourself plenty of time to be without the system. This could easily take several hours based on the power of your system.
*** Note: you might have to upgrade your SAINT as well. If this happens, you’ll get a message that support pack XXX must have SAINT version YY. Simply repeat step 2 & 3 for the SAINT update. There is another menu option to update the SAINT. run this, and wait for it to finish. It typically takes a while, and sometimes even shortdumps. If this happens, you can generally jsut log back in and restart the process. It will pick up where you left off and finish up the install. Then you can go back to step 4.
Step 5. Run SGEN. I’ll typically pick the software component to update, but feel free to select what works best for you. Short story, this will help compile the thousands of program that need it, and hopefully save you quite a bit of time for every transaction you visit for the first time.
If all goes well, your system is running better than ever after the update…
Good luck,

Mike

SAP Webgui – Turning it on

Well, now that I have someone else working with me, I needed to be able to get the system up and running so he can help with testing and data stuff. Since logging into SAP doesn’t always work behind a firewall, I figured I should get the SAP webgui turned on. Well, I stumbled upon a blog: (I just subscribed to his RSS, since I can always use extra basis help).

https://sapbasis.wordpress.com/

Anyway, here are the simple steps to turning on the SAP webgui (provided your server is available to the outside world. See my previous post: http://paperstreetenterprises.com/networking-sap…l-server-world/

Check if you have activated:
1) With transaction SICF and locate the services by path
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui

2)With Transaction SE80 locate from the menu, Utilities –> Settings–>Internet Transaction Server (Tab)–>Publish (Tab) and set “On Selected
Site” = INTERNAL.
This restricts the publication in the next step to the integrated (internal) ITS. Please note, on my ERP 6.0 SR3 system I didn’t need to do this. My system was already set to INTERNAL.

3)In SE80 only, Locate the Internet Services: SYSTEM and WEBGUI.
Publish these services with the Context Menu -> Publish -> Complete Service

4)Now Browse to http://<server>:<icmport>/sap/bc/gui/sap/its/webgui/! and login to the webgui.

Thanks for reading…

Creating the printer LOCL

I know this is an easy one for most basis folks, but I had to do some hunting to find it. So, maybe it’s useful for you too.
This is the guide to creating a local printer LOCL on your SAP system. Pretty easy. enjoy:

Follow the procedure below to create a device definition for frontend printing:
1.      Call transaction SPAD, and choose Output Devices.
2.      If you are not in change mode, switch to this mode by choosing This graphic is explained in the accompanying textChange.
3.      You can now do the following: Create a new entry
4.       Fill out the mandatory fields of the device definition as follows for frontend printing:

Device Attributes Tab Page

Output device

Enter a name for the output device that makes it clear to your users that this is the frontend printer, such as Locl.

Device Type

We recommend that you use the device type SWIN, SAPWIN, or a language-specific version for Microsoft Windows PCs. However, you can use any device type.

Use the device type pdf1 or a language-specific version for Frontend Printing Using SAP GUI for HTML.

Host Spool Access Method tab page

Access Method

Specify the access method F for frontend printing.

Host Printer

Enter the name __DEFAULT to use the default printer at a Microsoft Windows system.

If you specify __DEFAULT as the host printer, and the user enters the name of the output device, such as LOCL, in the print window and chooses enter, the system displays other printers defined on his or her work station PC. However, you can deactivate this list for users by selecting No Device Selection at Frontend on the Host Spool Access Method tab page.

4. Save your entries.
Result

When you save the device definition, it is available for your users’ use. To print documents using their frontend, users must enter the name of the output device that you have just created in the Output Device field of the print window.
Example

1 2 3 … 90 91 92 93 94 95 96 97 98

Posts navigation