Professional Documents
Culture Documents
Not severe problem. Routine errors. Mostly handled by Service desk arrangement
of the company (if have one).
Eg: a) Say Credit limit block in working on certain documents?
b) Pricing Condition Record not found even though conditions are maintained?
c) Unable to print a delivery document or Packing list?
PS: In the 4th phase of ASAP Implementation Methodology( i.e Final Preparations
for GO-LIVE) SAP has clearly specified that a Service desk needs to be arranged
for any sort of Implementation for better handling of Production errors.
Service desk lies with in the client.
2)
Some sort of serious problems. Those Could not be solved by Service Desk.
Should be referred to the Service Company (or may be company as prescribed in
SLA).
Eg: a) Credit Exposure (especially open values) doesn't update perfectly to KNKK
Table.
b) Inter company Billing is taking a wrong value of the Bill.
c) Need a new order type to handle reservation process
d) New product has been added to our selling range. Need to include this into
SAP. (Material Masters, Division attachements, Stock Handling etc.)
3)
Problems could not be solved by both of the above, are referred to Online Service
Support (OSS) of SAP Itself. SAP tries to solve the Problem, sometimes by
providing the perfect OSS Notes, fits to the error and rarely SAP logs into our
Servers (via remote log-on)for post mortem the problem. (The Medical check-up
client, connections, Login id and Passwords stuff are to be provided to SAP
whenever they need or at the time of opening OSS Message.)
There are lots of OSS Notes on each issue, SAP Top Notes and Notes explaining
about the process of raising a OSS Message.
Sometimes SAP Charges to the client / Service company depending on the
Agreement made at the time of buying License from SAP.
Eg: 1) Business Transation for the Currency 'EUR' is not possible. Check OSS
Note - This comes at the time of making Billing.
2) Transaction MMPI- Periods cannot be opened See OSS Note.
There are many other examples on the issue.
4)
Here the Condition Type is very important like PB00, PBXX,RA01 etc.
In the background every Condition Type has its own defition means the purpose of
the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual
Feilds etc is to be defined to work this functions. Normally we use the existing
ones without any risk. But some cases, we have to Create a New Condition Types
as per the organisation requirement.
The Pricing Schema is useful to minimise condition types while mention prices for
Vendor on the basis of Pricing Schema which we defined according to organisation
requirement.
The Pricing Schema means the calculations procedure of Condition Type.
Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means
RA01 is based on PB00 like that we have to define in the Pricing Schema
which makes easy to use in real time.
Here PB00 has the Access Sequence - 0002.
But RA01 does not have the Access Sequence.Why because it is a dependent on
PB00. But both are Condition Types.
In the system, by default some standard Scheme will be there at Vendor Schema
Group in the Vendor Master Screen means the standard one is assigned which is
very lengthy which may fullfil our requirement. But some cases which may not
fullfil our requirement, in such we have to define.
For the configuration, I may not able to explain properly through here but will give
some idea.
Configuration: SPRO - IMG - Material Management - Purchasing - Conditions Define Price Deternmination Process:
1. Define Access Sequence
2. Define Condition Type
3. Defince Calculation Schema:- Here you have to define the Schema - Define
Schema group
1. Define Schema Group vendor
2. Define Pricing Schema group
3. Schema group for Purchase Organisation
4. Assign Schema group to Purchase Organisation - Define Schema determination
1.define calculation schema for Standard purchase organisation
After completion of the Schema Group, we have to assign it to Vendors.
Then whenever we use any transaction with this Vendor, the concerned Schema
will work as configured by us.
The Pricing in MM is vast because each Condition have its own importance and
each Access Sequence have its own importance. So you need not bother about this.
First you learn how to define the Calculation Schema through the above.
Company (FI)
Plant
Storage Location
Purchase Organisation
(the red crosses indicate links that are not allowed -- see notes below)
Q: Why do we set up SAP Organisational Structures (or SAP Hierarchy)?
To keep it simple you want minimum amount of SAP Hierarchy objects (companies, plants,
storage locations, ...). Example: Don't just create a lot of plants -- always ask why, why, why?
Company Code
Set up on the FI side of SAP.
Required if we need to do external financial reporting.
All companys must have different codes (company code is 4 characters)
Questions to ask business:
What are the legal entities of the business?
Plant
Used by all Logistics modules (MM, PM, PP, QM, PS,...)
Must be link to a company code. (only one)
All plants must have different numbers (plant number is 4 characters)
Questions to ask business:
Where are the physical places (storage locations, distibution centres, ..) where materials
are handled?
If using SAP PP, where are all the factories?
How does the valuation (prices) of material differ between all these places?
Storage Locations
Used by Inventory Management (and Warehouse Management)
Part of one Plant.
Storage locations within the same plant must have unique number (4 characters)
Questions to ask:
Where are all the physical storage places (warehouses, tanks, ...)
Purchase Organisation
A plant must have a purchase organisation (one or more)
The link to company code is optional. If a Purchase Organisation is link to a company code, it can
only be used by plants within that one company code.
Contracts / Pricing are done in the purchase organisation.
It consists of people (purchasing groups) that manage the purchasing function.
Purchasing views in vendor master is per Purchasing Organisation
Questions to ask:
Plants can also be linked to a default Purchase Organisation. This is used for example in "Auto
PO create (when doing GR)" functionality, so that the system knows what P.Org to use. This link
is only required if these functionalies are used.
CONFIGURATION IN SAP
Creating and Assigning (linking) Plants
First create a plant by copying an existing plant:
IMG: Enterprise Structure > Definition > Logistics > Define, copy, check Plant
Select Activity: Copy, delete, check plant
It can also be link to a company code (this only takes place if the P.Org will be used plants linked
to this company code).
Firstly, I used version &(6 as temporary version you could use any other name.
1.
Delete version &(6 ofr S031, S032, S033, S034, S035 (if they exists) -- tcode
olix
2.
Get material documents data for &(6 again S031, S032, S033, S034, S035 -tcode oli1
3.
Get invoices data for &(6 again S031, S032, S033, S034, S035 -- tcode oliz
4.
Stock values for &(6 again S031, S032, S033, S034, S035 -- tcode oli2
5.
Delete version 000 (the main version) of S031, S032, S033, S034, S035 -- tcode
6.
olix
Copy data in version &(6 to version 000 for S031, S032, S033, S034,
S035 -- tcode olix
No screen shots about CL02 and CT04 -; you should be be able to get that right.
Material characteristic values can be viewed from a few places:
CL24N Specify class name and class type (001 in this case)
This data was loaded with attached LSMW and following input file (cl20_1.txt)
If the material numbers is numeric (example '123') then add leading zero's (as in my sample input
file). This is not required for alpha material numbers (example if material number is 'A123C').
This is how the data look in UltraEdit [ultraedit.com]
See how the leading zero's are chopped off in Excel, this is one of the main reasons to use Excel
only to display data. Do not save from Excel, as you may alter the input data.
The last line can be deleted -; it was added to show a deliberate error when all the data was
loaded.
So in this case
Running LSMW
If no error, you will see the deliberate error (that was added in last line)
The GL account itself is link to the Valuation class in T030 (tcode omwb)
If the Entry Aids (default valuation class per material group) are not found, one can also set a
default GL account in T030 by leaving the Valuation class blank. (First row in above example).