SAP WM Tables Process Flow

Warehouse Management in SAP (WM) :

Transfer requirement
LTBK Transfer requirement - header
LTBP Transfer requirement - item

Transfer order
LTAK Transfer order - header
LTAP Transfer order - item
Master data - stock positions
LQUA Quants

Inventory documents in WM
LINK Inventory document header
LINP Inventory document item
LINV Inventory data per quant

The easiest way to determine all WM tables is via the data dictionary.
Transaction SE11
Press F4 in field tables.
On the popup for the table search, enter LVS in field development class and execute

Some of the mostly used tables for WM:

Inventory document
IKPF Header: Physical Inventory Document
ISEG Physical Inventory Document Items
LINK Inventory document header in WM
LINP Inventory document item in WM
LINV Inventory data per quant

Storage locations and stocks
LAGP Storage bins
LEIN Storage unit header records
LQUA Quants
LQUAB Total quant counts for certain strategies
MEIK Make-to-Order Stock for Customer Order
MSCA Sales Orders on Hand with Vendor
MSKA Sales Order Stock
MBPR Stock at Production Storage Bin
MLGN Material Data per Warehouse Number
MLGT Material Data per Storage Type

Transaction Codes For WM Physical Inventory

How to configure physical inventory in WM?

No need to do any configuration settings for Phy-Inv

LI01 - Create record
LI11n - inventory count
LI20 - clear differences(WM)
LI21 - Clear inventory (IM)

T.codes regarding warehouse management manual physical inventory process.

The Perform Physical Inventory process includes the activities listed below:

- Generate Count Documents
- Distribute Count Sheets
- Perform Count
- Perform Re-Count
- Enter Count
- Compare Count Results with System
- Clear Differences in WM
- Clear Differences IM

T Codes:

- Select range of locations to be counted – LX15
- Print Physical Inventory Document – LI04
- Enter Stock Take Quantity – LI11
- List & Select Recount bins – LI14
- Print Recount Inventory Document – LI04
- Enter Stock Take Quantity – LI11
- Clear Discrepancies in WM – LI20
- Clear Discrepancies in IM – LI21

T codes

LCO1 Set Up Warehouse Co/Material Docs.
LCO2 Set Up Warehouse Co/Transport Orders
LL01 Warehouse Activity Monitor
LS01 Create Warehouse Master Record LS01N Create Warehouse Master Record
LS02 Change Warehouse Master Record
LS02N Change Warehouse Master Record
LS03 Display Warehouse Master Record
LS03N Display Warehouse Master Record
LS26 Warehouse stocks per material
MB52 List of Warehouse Stocks on Hand OLML

Important T-Codes in SAP Warehouse Management

Some important t-codes in WM:

Reports
LX02 (~MB52 in IM)
LS24 (~MMBE)
LT22 (~MB51 in IM)

WH activity monitor
LL01

TR
LB10 - list of TRs
LB01 – Create

LB02 – Change

LB03 - Delete

TO
create:
LT01 (LT21 display, you cannot change in standard system)
LT10
(from LB10 you can also process TRs)
LT03 (for delivery)

Cancel
LT15

Confirm
LT22 (e.g.)

Post change
LU04 - list
LU01/02/03
LQ01/02/03

Inventory
LI01N - create document & activate (LI02N-create, LI03N-change, LX22-overview)
LI11N - enter count result
LI20 - clear difference in WM
LI21 - clear difference in IM

Apply Support Packs To My SAP SYSTEM

How can I apply support packs to my 4.7 IDES SYSTEM?
SAP"- SAP R3 4.7EE,
DATABASE : ORACLE 8.1.7
OS : WINDOWS 2003 SERVER
What is the step by step procedure and how to apply in r/3?

You have various issues with your setup:

- Oracle 8.1.7 is not supported under Windows 2003
- Oracle 8.1.7 is out of maintenance since three years

During SP application you will maybe run into problems that can't be
fixed since your installation is just too old and unsupported. *-- Markus

As mentioned, it's true that it won't get supported on Oracle 8. The best combination would be with 9i

Any How I have mentioned the steps below to apply for patches.

To Apply Support packs first up all you need to download the patches. When you have the downloaded the file i.e.. (*.car ) patch file then you can extract and apply it in two ways.

1. Go to command prompt through cmd (if you are using windows) and go to the folder where you have download these files ( could be in \downloaded folder\ ) type this command on command prompt without quotes "sapcar -xvf .sar". Now it will create a folder called EPS and a folder called IN inside EPS. Go to this folder and it will show two extracted files with extension " .att " and " .pat ". Copy this two files into yours trans\eps\in folder which could be something like \usr\sap\trans\eps\in folder.Then type spam on your session and navigate to Support Package\Load Package\From Application Server and it will ask for Path confirm it Say " YES"Select the patch imported and double click on it and then click on small truck Icon and it start Import.

2. Type Spam on session then navigate to Support Package\Load Package\From FrontEnd \ and Navigate to path where you have downloaded the *.SAR file of Support Pack.Now it will open a popup window and then click on decompress button ( It is front-End process for extracting or decompressing .sar file in .pat and .att extension ) After that click on Display-Define button on right hand side.) Select the BASIS or ABAP patch ( whichever you are applying *) what ever you are after and import it in queue. After that click on Small truck Icon in menu i.e.. (import Queue) and it Starts importing.

Reporting a Problem to SAP

When I tried to report a problem to SAP using
http://service.sap.com/message url it provided 4 steps to follow:

1) Choose system
2) Prepare Solution Search
3) Find Solution
4) Enter Message

I could do the step 1 but dont know what to do at steps 2, 3 and 4.

SAP changed the customer message screens so you now have to navigate through a search of the SAP Notes before being able to create a message.

We usually search the Notes extensively before we create a message, so we just enter a blank search and then go on to create the message.

Follow the steps, It may solve your problem:

1. Copy following url into web browser : http://service.sap.com/message

It will ask you for your OSS ID and password .
A Screen which contain a push Button Select System displayed .

2. Push the Button Select System .
It will open a sub screen in which there will be a hierarchical structue which looks like

-
-

+
+

Here + indicate that you have a sub tree .
Specific product like SAP R/3 T for Services , SCM , CRM , ERP etc

3. Select the system for which you need to log a message
It will take you to message screen screen.

4. Select you domain for problem for example Basis problem with Database where dataBASE IS oracle then Message type will be BC-DB-ORA
* .
5 Select priority of Message

6 . Write Message and send it to SAP

SAP Transaction code to pre-compile all system program

If I have to run SGEN and have to recycle the server as well for clearing out memory, does it make sense to run SGEN first and recycle afterwards, because SGEN will sort of litter the memory or is it inconsequential what runs first.

SGEN is ued to "compile" ABAP programs. Results are put in database.

So, if you restart SAP, compiled results will still be in the database, so, no need to run SGEN again.

Make use of the transaction 'SGEN' to re-generate all the SAP programs after you change version of your SAP kernel, upgrade SAP system or apply support packages.

Do take care of the table spaces and use SAPDBA to observe them.

Do it during a weekend which is the best or a period of time with very very low users activity.

It will takes about 5 to 8 hours depending on the type of hardware configuration you are using.

Details Description Of SPAU & SPDD

Describe SPAU and SPDD.

When you apply a package, a large number of objects are changed.

If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.

SPDD is used to identify dictionary objects

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.

You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.

If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note. You must check the OSSs note and see if SAP have fixed that note in a hot package.

If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code.

If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.

You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.

What objects will come in SPAU and SPDD?

All the objects which are modified, after tansporting to the current system, will be listed in SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, like tables, dataelements, domains,view...etc. The rest of all the modified repository objects will be listed in SPAU.

What happens to the modifications done in the older version when we upgrade the version? (with Modification assistant and w/o)

After the initial upgrade happens, we have to do adjustments from SPAU/SPDD to maintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have to either carry forward the changes to the new version, by choosing the option ADOPT CHANGES (available on right click) or RESET TO ORIGINAL (available on right click).

Will they come in these transactions?

Yes, they will be listed in these transactions, after the BASIS updgrade activity.

And what if we apply some patches(Notes) to the system? What is the impact of these patches to the SPAU transaction?
Patches will be supported by the version upgrade. In case of notes, we have to verify whether these notes are supported by the new version (you can go into http://www.service.sap.com/notes to verify this. Also, we have to analyze whther the code in the note is already incorporated in the new version. In this case you can ignore the chanes choosing RESET TO ORIGINAL option

Applying SP4 to Windows 2000 Server

You need to download a newer SAP kernel. You will need an OSS ID and password to access http://service.sap.com/patches. And you will need to know what R/3 version, database, and OS you currently use.

Once you are at the patches website, you will need to click in the navigation tree:
R/3 -> R/3 + ?Release number? -> Binary patches ->
SAP Kernel + ?Release number? + 32-Bit -> NT/I386.

Download everything from the database section and everything from the database independent section.

One of the files you downloaded should start with SAPCAR and end with a *.exe.
Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory.
Go to \usr\sap\\SYS\exe\run and backup the entire directory to some other directory -
I usually create a \usr\sap\\SYS\exe\backup_run directory. Make sure SAP is down, the database is down, the TNS listener is down, and the SAPOSCOL is down before you do this.

Uncompress all the files you downloaded by opening a DOS box and typing:

SAPCAR -xvf .CAR

All files ending with .SAR or .CAR must be uncompressed. All the extracted files need to be moved to the \usr\sap\\SYS\exe\run AFTER that directory has been completely backed up.

Once everything has been downloaded, uncompressed, and moved into the exe\run directory, you can start the SAPOSCOL, the listener and the database services again. And then you should be able to start SAP. If there are any application servers for this database instance, the SAP software will update those kernels on startup.

If the SAP instance STILL does not come back up, you can take down everything again and restore the exe\run directory with your backup copy. Nothing will have been damaged.

Upgrading SAP Kernel, Hotpatches and Database Startup

Kernel upgrade is an easy process.

Go to the SAP OSS Site :-

http://service.sap.com/SWCenter-Main
SAP R/3
SAP R/3 4.6C
Binary Patches
SAP KERNEL 4.6D

Download the kernel programs in a temporary folder.

Create a folder and copy the executables /exe/run/ then uncar the downloaded files and replace the executables.

It is recommended to shutdown the R/3 database and all services including saposcol.

Then restart your system.


A couple of important points to remember are :-.

a) Always make a copy of the files you're going to replace. For e.g. Create a directory (oldkern) and copy all the old files
before replacing them (this helps when sometimes the new Kernel has problems, and you can revert it)

b) You have to shutdown SAP and the Database using the OLD kernel file. Again it is good practice to shutdown everything
first.


Refer to this OSS note which is pretty useful :-

102461 - Installation of 4.0B/40B_COM kernel with 4.0A/40B


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

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

Manually Applying OSS note on SAP Standard Program

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.