SAP MM Forum

IDOC

2007-12-09T20:03:00.000-08:00

What is IDOC

• IDOC = Intermediate Document

• IDOC is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.

• When we execute an outbound ALE or EDI Process, an IDOC is created

• In an inbound ALE or EDI process, an IDOC serves as input to create an application document.

• In the SAP System, IDOCs are stored in database.

• Every IDOC has an unique number(within a client).

• IDOCs are independent of the sending and receiving systems.(SAP-to-SAP as well as Non-SAP)

• IDOCs are based on EDI standards, ANSI ASC X12 and EDIFACT. In case of any conflict in data size, it adopts one with greater length

• IDOCs are independent of the direction of data exchange e.g. ORDERS01: Purchasing module : Inbound and Outbound

• IDOCs can be viewed in a text editor. Data is stored in character format instead of binary format.

IDOC Components

Basic IDOC Type (we30)

• Basic IDOC Type defines the structure and format of the business document that is to be exchanged.

• IDOC Type has a

– specific name

– list of permitted segments

– hierarchy of segments

– mandatory/optional segments

– minimum/maximum range of each segment.

Segments

• Segment defines the format and structure of a data record. Segments are reusable components.

• For each segment SAP creates

– Segment Type (version independent)

– Segment Definition (version dependent)

– Segment Documentation

• The last 3 characters is the version of the segment

• Definitions keep changing as per the version but the segment type remains the same

IDOC Run-Time Components

• An IDOC is an instance of an IDOC Type

• At run time the following events occur

– A unique IDOC no. is allocated by SAP

– One control record is attached to the IDOC

– Segments translate into data records

– Status records are attached

– Syntax rules are checked.

• Each IDOC has 3 parts

– Control Record

– Data Record

– Status Record

• We02 or We05

Control Record

• All control record data is stored in EDIDC table. The key to this table is the IDOC Number

• It contains information like IDOC number, sender, recipient information, channel it is using, which port it is using etc.

Data Record

• Data record contains application data like employee header info, weekly details, client details etc

• All data record data is stored in EDI_DD40 table and EDI_DD

Status Record

• Status record are attached to an IDOC at every milestone or when it encounter errors.

• All status record data is stored in EDID8 table.

Where and How IDOC is created

Where and How an IDOC is created?

• Lets take an example to understand this:

• Whenever a Purchase Order (PO) is created we want to send the IDOC to a vendor.

• The PO is sent in the form of an IDOC to the vendor (partner). That partner has to be EDI enabled in that system.. SAP should realize that it could send doc to this vendor electronically. (Creating a vendor is not sufficient). Partner Profile should be EDI enabled i.e. A partner profile should exist in the sap system.

• Quotation, RFQ, PO, SO, Invoice, delivery challan etc are some of the commonly exchanged documents through IDOCs

• We create only one profile for both inbound and outbound IDOCs.

• Partner profile should contain message type……to be able to exchange the IDOC.

• We define partner type, partner function and message type (it distinguish if an IDOC is being sent to same person in same function for different reason e.g. SO)

Process Code

Creating Outbound Process Code (WE41)

• What is Process Code?

Process of filling the IDOC with application data is done by Function Module. But, function module is not assigned to a Partner. It is encapsulated by a Process Code and this Process Code is assigned to a Partner in Partner Profile.

• Assigning Function Module to Process Code

- Go to Transaction WE41.

- Switch to “Change” Mode and click “New Entries”.

- Enter Process Code Name and assign the Function Module created.

Partner Profile

Creating Partner Profile (WE20)

• What is Partner Profile?

We must maintain the business partners with whom we communicate via IDocs, in Partner Profiles.

• Steps to create Partner Profile

- Goto Transaction WE20.

- Click on Create Button.

- Enter the Number of Vendor Created in Partner No. and ‘LI’ in Partner Type fields.

- Save the Data.

- For Outbound Partner Profile we have to create Outbound Parameters

- Specify Partner Function, Message type created, Port (create a port in WE21),Basic Type and Output Mode.

- Goto “Message Control” Tab and link the Message Type and Process Code created.

- Save.

Change Application Data to be transmitted

• Change Purchase Order Created using transaction ME22n for the Vendor to which partner profile has been created.

• Go to “Messages” , add the new “Message Type” to the list and Save the Purchase Order.

• An IDOC will be created for the purchase order and will be dispatched to PORT mentioned.

Check the status of IDOC (WE02)

• The IDOC status can be checked using transaction WE02

• If the status is ’03’, it implies that IDOC is passed to Port.

Summary: IDOC Workflow

The sequence:

1. Checks whether Partner profile exists or not

2. Whether that PP has a outbound parameter

3. Whether NEU message type is there or not (message control)

4. Checks the process code (gives the name of Function module)

5. Checks immediate transfer or batch transfer

6. Based on that it checks the receiver port

7. Then it will trigger the RFC destination

8. Then it triggers the event on subsystem/customer system

9. Transfer the IDOC to a port and transfer the Idoc in terms of file and it triggers the customer system

10. Customer knows from where it should pick up the file ….it picks up the file.

Extending an Existing IDOC Type

• Used in cases where some additional information is required in addition to that supplied by the Standard IDOC Type.

• In Transaction WE30 we create the IDOC as an Extension and specify the basic type for which it is an extension.

• We add the segments needed as children to existing ones.

• None of the Reference Segments can be deleted or changed.

Extension Child Segs

Basic Type (ORDERS01)

Cannot be modified

IDOC Views

• An IDOC type can be used for more than one message type, which results in IDOCs containing more fields than required for a particular message type.

• IDOC views are used to improve performance in generating IDOCs to ensure only the relevant segments are filled with data.

• IDOC Views are important only for Outbound Processing.

IDOC Type

Processing Logic

• The processing logic associated with the IDOC is the function module that is written to handle the inbound/outbound IDOC.

• Its written just like any function module but has to follow a standard interface (i.e. Import, Export, Changing & Tables) parameters and it is should be RFC enabled.

• In this function module we are effectively building up a table of type EDID4 (IDOC Data table) and change the control record.

User Exits In MM Area

2007-10-26T07:52:00.000-07:00

The following SAP enhancements are available for the Purchasing area:

AMPL0001 - User subscreen for additional AMPL data (manufacturer part number)

LMELA002 - Adoption of batch number from shipping notification at time of posting of a goods receipt

LMELA010 - Incoming shipping notification: adoption of item data from IDoc

LMEQR001 - User exit for source determination

M06B0001 - Role determination for release of requisitions

M06B0001 - Changes to communication structure for release of requisitions

M06B0003 - Number range and document number

M06B0004 - Number range and document number

M06B0005 - Changes to communication structure for overall release of purchase requisitions

M06E0004 - Changes to communication structure for release of purchasing document

M06E0005 - Role determination for release of purchasing documents

ME590001 - Grouping of requisitions for PO split in transaction ME59

MEETA001 - Determination of schedule line type (backlog, immediate requirement, forecast)

MEFLD004 - Determination of earliest delivery date for checking at time of goods receipt (PO only)

MELAB001 - Generation of forecast delivery schedule: realization via creation profile

MEQUERY1 - Enhancement for document overview ME21N / ME51N

MEVME001 - Calculation of default GR quantity and over/underdelivery tolerances

MM06E001 - User exits for inbound EDI messages and outbound purchasing documents

MM06E003 - Number range and document number

MM06E004 - Control of import data screens in purchase orders

MM06E005 - Customer fields in purchasing documents

MEREQ001 - Customer's own data in purchase requisitions

MM06E007 - Change document for requisitions when converting into POs

MM06E008 - Monitoring of contract target value in case of release orders

MM06E009 - Relevant texts for "Texts exist" indicator

MM06E010 - Field selection for vendor address

MM06E011 - Activation of requisition block

MM06L001 - Exits for determination of ratings in vendor evaluation

MMAL0001 - ALE source list distribution: outbound processing

MMAL0002 - ALE source list distribution: inbound processing

MMAL0003 - ALE purchasing info record distribution: outbound processing

MMAL0004 - ALE purchasing info record distribution: inbound processing

MMDA0001 - Default values for delivery addresses

MMFAB001 - User exit for generation of releases

MRFLB001 - Control items during release creation

LWBON001 - Enhancement of LIS update through extension of the communication structure MCKONA (business volumes and rebate income)

LWBON003 - Change settlement data for end-of-period rebate settlement before creation of settlement documents

LWSUS001 - Customer-specific source determination in Retail

LMEXF001 - Conditions in purchasing documents without invoice receipt

LMEKO002 - Enhance communication structure KOMP for price determination

MM Configuration help

2007-10-26T07:50:00.000-07:00

Maintain Plant

Plant 0001 is the SAP default.

OX14 - Define Valuation Area (Tick one only- Once your system go live, no more changes)
Most company take the SAP recommended choice - Value Material Stock at Plant level
Value Material Stock at Plant or Company Level

If you valuate material stocks at plant level, the plant is the valuation area.
If you valuate material stocks at company code level, the company code is the valuation area.
The decision you make applies to the whole client.

OX10 - Create / Change / View Plants

OVXB - Create / Change / View Division

OX18 - Assign Plant to company code
e.g. 0001 - 0001 - All Plants
Px1 - Plant Px1
Px2 - Plant Px2
OX19 - Assignment of company code to the Controlling Area

OB38 - Assign company code to Credit Control Area

OMJ7 - Assign business area to Plant/Valuation area and division
e.g. Plant Px1 - Business Area Bx1
Bx2
Assign Valuation area to the Business Area
.e.g. Valuation area Vx1 - Business Area Bx1
Business Area Bx2

OMS0 - Assign Factory Calendar to the Plant and Business Area

The plant plays an important role in the following areas:

Material Valuation - If the valuation level is the plant, the material stocks are valuated at plant level. Each plant can have its own material prices and account determination.
Inventory Management - The material stocks are managed within a plant.
MRP - Material requirements are planned for each plant. Each plant has its own MRP data. Analyses for materials planning can be made across plants.
Production - Each plant having they own production/planning.
Costing - In costing, valuation prices are defined only within a plant.
Plant Maintenance - If a plant performs plant maintenance planning tasks, it is defined as a maintenance planning plant. A maintenance planning plant can also carry out planning tasks for other plants (maintenance plants).

If you want to use the application PP (production planning) or product costing and job-order costing, you must set valuation at plant level.

The valuation level that you choose affects

the maintenance of material master records
the G/L accounts in which material stocks are managed
the G/L accounts to which transactions are posted in Materials Management

Effect on the maintenance of material master records:

Depending on the valuation level chosen,

you maintain accounting data in the material master record for each plant or for each company code
you define a valuation price for the material in each plant or in each company code

Effect on G/L accounts:

If material stocks are valuated at company code level, all plant stocks of a material are managed in a joint stock account for each company code.
If material stocks are valuated at plant level, you can manage the material stocks for each plant in different accounts. For each plant, you can define a separate determination.
If several plants are to use account determination, you can group these plants in "Valuation and Account Assignment" Customizing.

Material Master - Introduction

The material master is the starting point for the rest of the modules.

What Material Types are there?

The material types that you use are configured in Customizing for the Material Master under

Logistics Master Data : Material Master -> Material -> Control data -> Define material type attributes.

The following list shows you the material types contained, for example, in the standard SAP R/3 System, and what their different roles are:

DIEN (services)
Services are procured externally and cannot be stored. A material master record of this material type can always contain purchasing data.

FERT (finished products)
Finished products are produced by the company itself. Since they cannot be ordered by Purchasing, a material master record of this material type does not contain purchasing data.

FHMI (production resources/tools)
Production resources/tools are procured externally and used in the manufacture of products. A material master record of this material type can contain purchasing data, but no sales data. It is managed on a quantity basis. Examples of production resources/tools are apparatus, equipment, and measuring and testing devices.

HALB (semifinished products)
Semifinished products can be procured externally (sub-contracting) as well as manufactured in-house. They are then processed by the company. A material master record of this material type can contain both purchasing and work scheduling data.

HAWA (trading goods)
Trading goods are always procured externally and then sold. A material master record of this material type can contain purchasing and sales data.

HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A material master record of this material type can contain purchasing data but no sales data.

NLAG (non-stock material)
Non-stock material is material that is not held in stock because it is consumed immediately. (Office supplies such as stationary. You need to create purchase order and accounting document for payment but the stock balance is always zero as it is issued out immediately to the various department.)

ROH (raw materials)
Raw materials are always procured externally and then processed. Since raw materials cannot be sold, a material master record of this material type contains no sales data.

UNBW (non-valuated materials)
Non-valuated materials are managed on a quantity basis, but not by value.

VERP (packaging materials)
Packaging materials are used to transport goods and come with the goods free of charge. A material master record of this material type is managed both on a quantity basis and by value.

WETT (competitive products)
Competitive products have their own material master records created from the Basic Data view. The competitor's number, which is stored in the material master record, assigns the material to a particular competitor.

Maintain the Material Type

OMS2 - Material Type Maintenance - Create/Change/Display

Steps:-

transaction OMS2
click Change
key in the Material Type you want to change e.g. FERT then hit enter

The Views belows allows you to choose the Views for each Material Type.
(Press the Page up/Page Down keys to scroll the views)

If you tried to change from FERT to HAWA in 4.6x, you will receive an error message :-
The material type cannot be changed. This is not allowed if only external procurement is defined for the new material type, or if the new material type has a different account category reference than the old material type.

To overcome it, goto OMS2 and change the HAWA material type.
In the Internal/external purchase orders sections:
Original Changes
Ext. purchase orders 2 1
Int. purchase orders 0 1

Screens in Material Master

MM01 - Create, MM02 - Change, MM03 - Display and MM06 - Flag for deletion.
MM04 - Display the changes done to the material master.
MMAM - Change the Material Type. for e.g. from FERT to HALB

Configure the Material Master Screen MM01 / MM02 / MM03

OMSR - Assign the field to the field group
OMS9 - Maintain the data screen field

Unit of Measure

In the material master, there is a Units of measure button for users to store in the different conversion rate. This sample program (ZUNT) extract the data from the unit of measure conversion table.

In the Material Master the moving average price are affected by:-

Goods Receipt for Purchase Orders
Transfer from Plant to Plant
Invoice Receipt
Settlement
Price Change

Common configuration changes-

define new material group (OMSF)
define new valuation class (OMSK) and automatic posting (OBYC)
define new material account assignment group (transaction OVK5) and

Customer/Material/Account keys (transaction VKOA)

Block materials from inventory posting

After blocking, when the user do a inventory posting, they will get this error message :-

E: Material xxxxx has status Blocked for procmnt/whse

To activate the blocking :-

Goto transaction MM02 - Purchasing View

Type in 01 at the MM/PP status field and save it

Create Delivery Log - Material xxx is blocked

During the Create Delivery (VL01), SAP prompt you a log that Material xxx is blocked.

During the Sales Order Create/Change for that material, there might be some update termination that causes the locked of the material (Windows hanged or power failure).

You can check using transaction SM12 - type an "*" at the User name field.

Check whether the material is in the locked list.

If it is in the locked list, asked the user to log out before you delete it from the locked list.

Maintain Storage Location

MMSC - Collective entry of Storage Location for a material.

Insert new or delete un-used Storage Location.

Maintain whether the storage location was included or excluded from MRP run.

Block Storage Location from further posting

1. You can block the storage location of a material without affecting the rest of the location using the same material.
Create a Physical Inventory document for the storage location with transaction MI01

Select the Posting Block checkbox.
This would prevent transactions from occuring until you either post or delete the physical inventory document.
(There are no impact, unless you do a post difference for the physical inventory document.)

2. Another method is to rename the storage location name.

Go to transaction OX09
Edit -> Copy as (copy the original storage location to a new name, replacing the first character e.g. ZXXX)
Edit -> Delete (delete the original storage location)

Do the reverse if you want back the original storage location.

Accounting document number range for MM

Transaction OMW9

Document Type - Double click on desire transaction code to check the document type for number range.
(e.g. MR21 Document type - PR)

Financial accounting document type - Assign the document type to a number range and account type.
(e.g. PR - Account type allowed for posting will be MS)

Double click on the document type PR.
Assign an unique starting number range that was not used. e.g. 88
Choose the Account type for Material and G/L account (MS)
The rest of the fields are optional (you can leave it as blank)

SAP definitions for account type -

A - Assets
D - Customers
K - Vendors
M - Material
S - G/L accounts

Number ranges for financial accounting document type - Assign the number range to the running number range.

No. Year (till) From number To number Current number Ext (no tick internal or tick external)
88 9999 8800000000 8899999999 Track by SAP Blank

Accounting document will be generated if there are stocks during price change, if you don't have any stocks, no accounting document will be generated as there are no inventory to revaluate for price differences.

Valuation Class for Material Group

In 4.6x and 4.5b, you can assign valuation class to Material Group.

It is useful in the sense that user do not have to manually do an Account Assignments.

For stock items, valuation class cannot be changed whenever the stock on hand is not zero.

Valuation class are tied to a G/L account.

A change of valuation class means a change of G/L account.

In FI concept, you have to debit and credit to balance the G/L account. That is why your stock must be zero before the system allows you to changed the valuation class. If it is not zero, you have to either transfer it to another material or do a dummy issues. After changing the valuation class, do a reversal entries for the stocks which you have transfer out or you have done a dummy issues.

IMG - Material Management -> Purchasing -> Material Master -> Entry aids for items without a Material Master

G/L Accounts in MM Account Determination

The program RM07C030 check all the G/L account define in your Material Master valuation class.

Search is via Company code and Valuation area.

Compare fields status for movement types against General Ledger

Use SA38 then run RM07CUFA

Mass Change Material Group In Materials Master

2007-10-26T07:49:00.001-07:00

How I can move several materials belonging to one Material Group to another Material Group?

1. SE16 - MARA table find all the material with OLD_material_group.

2. MM17 - select TABLE as MARA and FIELDS as MATKL (material group), press execute.

3. In tab "Data Records to be changed", copy all the materials you have selected in step 1. Press execute.

4. In NEW VALUES field enter NEW_material_group. Press 'Carry out a mass change' button.

5. Press Save.

6. Check in MARA table for materials with new material group.

Change Base Unit of Measure

2007-10-26T07:48:00.000-07:00

One raw material we assigned base unit of measure as OZ, later add alternate unit of measure as ML.

Now I wanted to change the base unit to ML and alternaet to OZ. For that I deleted component from the BOM. Related PO's, Prd ord and demand are closed. Deleted the alternate unit from purchasing and plant/stock (Area were we assign the alternate unit), then try to change it giving message as Unit of measure ML used as alternate unit. (In additinal data screen still the alternate unit and conversion available)

You can do the following procedure (after deleting the material in all concerened documents):

1. Delete the uom from Unit of issue field (General Plant Data / Storage 1) in MM if you have mentioned it there.

2. Go to additional data , use delete line tab and delete the conversion factor by keeping the cursor on that line.

3. Come to main data, now change the base unit of measure to the required one.

4. Then give the alternative unit of measure, system will ask for conversion factor.

5. Then save

Changing the Material Valuation Types

2007-10-26T07:47:00.000-07:00

Assuming you have defined split valuation types in the sap img, you must remove all stock for the current period and one previous period before you can create the material with different valuation types.

The best method is to wait until the last day of a period, and then perform a physical inventory adjustment to remove the stock.

Then on the first day of the next period you can set up the material accounting views for each split valuation type.

After the material valuation types are set up for the material, you can do an inventory adjustment to put the stock back in.

Make sure you notify your accounting inventory control departments as to the quantities and values you are taking out at
the end of the period.

Price Control V or S in material type

2007-10-26T07:46:00.000-07:00

Standard price are used for products that do not fluctuated frequently. It is usually used for finished or semi finished products.

Moving average price are used mainly for raw materials that are purchased externally. The advantage of using moving average price for your raw materials is that your inventory costs will always reflect the current market cost.

SAP strongly recommends that you do not select price control V for semi-finished products and finished products, because doing so will very easily cause the calculation of unrealistic valuation prices. SAP recommends:
Price control V for raw materials and trading goods; price control S for semi-finished products and products.

If you nevertheless select price control V, take care in the following situations:

1. Unrealistic prices occur if materials are produced and also retire during one period (that is, the inventory at the end of the period is smaller than the total of aquisitions from production orders) and if, in addition, several production orders belonging to a material were finished in this period, and the production order settlement calculates variances at the end of the period. Every single production order carries out an inventory coverage check and may therefore cause the moving average price to be changed. However, the individual production orders do not check whether the inventory available at the end of the period has already been debited by another production order.

Example: on 20 workdays in the period, 1 piece of material xyz was produced for each day and delivered to the warehouse at a price of USD 1000. At the end of the period there is 1 piece at the warehouse. Since an activity price of a participating cost center was higher than planned , every single production order calculates cost of goods manufactured of USD 1100 during the settlement. Every single one carries out a inventory coverage check and finds out that the variance can be posted completely to the inventory. That is, the ending inventory of one piece is debited with USD 20 x 100 and it consequently receives a price of USD 3000.

1. A settlement is carried out although not all costs have yet been posted to the order. This can even result in a price of 0 for the delivered product.
2. No period check of the costs is carried out on the order, that is, costs from previous periods may be settled.
3. Settling orders is already possible in the 'Delivery completed' status.

Solution: Standard price for products together with possible manual price changes.
If you are required to valuate semi-finished and finished products with actual prices that correspond to the costs of the actual production, SAP recommends you use the function of the material ledger for this. Here, a periodic actual price is created that is calculated on a much more reliable basis than the moving average price. A so-called price limiter quantity is used which makes sure that in the above example price differences are proportionally taken into account (95% of the total price differences) when valuating the 19 pieces withdrawn from material xyz which results in a periodic actual price of 1100 USD. In addition, it is possible as of Release 4.5 to even take into account the variances of the actual prices of the raw materials in the valuation of the semi-finished and finished products that are manufactured from it.

If we select std price for any type of material or mav and then make po, it will pick from material master or what?

The Purchase Info Record have the FIRST priority. When no po info record is found, the Purchase Order will pick the user LAST enter price. The PO module do not pick up any price from material master.

SAP Split Valuation for Materials

2007-10-26T07:45:00.000-07:00

The SAP R/3 System allows you to valuate stocks of a material either together or separately, that is, according to different valuation criteria. Split valuation is necessary if, for example:

1. Stock from in-house production has a different valuation price than externally procured stock.

2. Stock obtained from one manufacturer is valuated at a different price than stock obtained from another manufacturer.

3. Different batch stocks of a material have different valuation prices.

4. Value damaged and repair part differently from a new part.

To used split valuation, you have to activate it using 'OMW0'.

To change split material valuation once it has been set, you must

1. first post out all stocks (for example, to a cost center or with movement type 562)
2. then change the control parameters
3. if necessary, change the automatic account determination
4. finally post the stocks back in again

In split valuation, you can distinguish between partial stocks of a material according to certain criteria and valuate them separately.

The material stock is divided according to valuation category and valuation type.

The valuation category determines how the partial stocks are divided, that is, according to which criteria.

The valuation type describes the characteristics of the individual stocks.

With the function "Setting" you can determine:

which valuation categories exist in your company (global categories)
which valuation types exist in your company (global types)
which valuation types belong to which valuation category
which valuation categories exist in a valuation area (local categories)

Your entries are only relevant if you set split valuation as active in the function "Global settings".

In the standard SAP R/3 System, the following valuation categories are default settings :

B procurement type

with the valuation types:

"EIGEN" for in-house production
"FREMD" for external procurement

H Origin

X automatic valuation (only for batch)

To select split valuation ('OMWC'), proceed as follows:

1. Determine the valuation categories and valuation types that are allowed for all valuation areas:
global valuation categories via menu "Goto --> Global Categories"
global valuation types via menu "Goto --> Global Types"

2. Allocate the valuation types to the valuation categories.
a) Select "Goto --> Global Categories".
b) Position the cursor on a valuation category and select
"Goto --> Global Categories --> Assignments --> 'Types->Category'".
c) Activate the valuation types you want.

3. Determine the local valuation categories for each valuation area.
a) Select "Goto --> Local definitions".
b) Position the cursor on a valuation area and select
"Goto --> Local Definitions --> Allocate Categoires->Org.units (button Cats->(OU)".
You obtain a list of the global valuation categories.
c) Activate the categories to be used in this valuation area.
The system creates the local valuation types based on the allocations under point 2.
Only now can you create a master record with split valuation.

Specifying Split Valuation by creating Material Subject to Split Valuation

1. Create a material master record, selecting the Accounting View 1.
2. Enter your data as required on the Accounting data screen, specifying a valuation category.
(If you can't find the valuation category field, it might be hidden, use OMSR to define the Field Groups.
Look for the field MBEW-BWTTY for Valuation category).
3. Be sure that the price control indicator is V for moving average price and enter a moving average price.
4. In the case of split valuation, you can create only one valuation header record with price control V because the
individual stock values are cumulated, and this total value is written to the valuation header record. This is where the
individual stocks of a material are managed cumulatively. To do this, fill in the Valuation category field on the accounting
screen when you create the material master record and leave the Valuation type field blank.
5. Save your data and the system creates the valuation header record.
6. The initial screen appears.
7. Extend the material by creating new material master records from the Accounting view 1. For the first material, specify a
valuation type in the Organizational Levels dialog box and enter the respective accounting data on the data screen.
Proceed likewise for the other materials, distinguishing between them by valuation type. To do this, call up the material in
creation mode again. Due to the fact that a valuation header record exists, the system requires you to enter a valuation
type for the valuation category.
8. Repeat step seven for every valuation type planned.

You want to valuate the stock of material XYZ that you obtain from manufacturer A in Los Angeles at a different price than the stock you obtain from manufacturer B in Detroit. In this case, the valuation category is H for origin. Your valuation types can be LOS ANGELES and DETROIT.

If a material is subject to split valuation, every quantity (sub-stock) of this material must be assigned to a valuation type (for example, country of origin).

For every valuation type, there are two types of data in the system, as follows:

Valuation data (for example, valuation price, total stock quantity, total stock value), which is defined for every valuation type at valuation-area level and applies to all dependent storage locations.

Stock data, which, like batch data, is managed separately for each storage location. If a material that is subject to split valuation is also subject to management in batches, its stock data is not managed by valuation type, but rather by batch. Every batch is assigned to a valuation type.

The stock quantity, stock value, and valuation price for all valuation types are managed cumulatively at valuation-area level.

Must the Valuation Type Exist Before the First Goods Receipt?

You can post the goods receipt of material of a certain valuation type only if the valuation data for this valuation type already exists, because the system valuates the goods receipt at the price defined in the valuation data. On the other hand, the stock data for the valuation type is created automatically during the first goods receipt into the storage location, if this is defined in Customizing for Inventory Management.

Goods Movements with Materials Subject to Split Valuation

If you want to enter goods movements for materials subject to split valuation, you must enter the valuation type in addition to the material number.

Enter the valuation type in the Batch field for MB01.

In MIGO, there is a valuation type field in Detail data -> Material.

Creation of same Material Code in Different Company Codes

2007-10-26T07:44:00.000-07:00

Our requirement : To create one material code (eg., A123) with different material type (HALB & UNBW) in two different company's plants. We have created A123 material code with HALB in 1000 company's 1100 plant. While creating A123 material with UNBW material type in 2000 company's 2100 plant, system is taking default material type as HALB, as already created for 1000 company's 1100 plant.

This requirement is due to the Job work process (non-valuated material) in 2000 company.

The basic data (like Matl. no., description, UOM etc.) in material master are maintain at client level. We can not maintain the same at company code level. So in your case you have to maintain two seperate code for different companies, with different matl type.

But you can for the same material type to define, that in some valuation areas it has update by value and quantity, but in another valuation areas only by quantity. Maybe you don't have to have two material types:)

Detail and what are the settings are required in customization:

tr.code OMS2
1)Select details of material type and on end of screen in part 'Quantity/Value update" select for Value update radiobutton "By Valuation Area"

2)After that on left side of screen select folder "Quantity/Value update" and set in which areas you need value update by setting indicator in column "Value update".

One Storage Location for Two Different Plant

2007-10-26T07:43:00.000-07:00

Can one storage location be extended to two different plants?

Eg plant PPL01-- storage loc 1) sc01 2)sc02.

Can another plant PPL02 have any of the storage locations of PPL01.

You can duplicate a storage location identifier at different plants but each of those is a unique storage location. For example Plant = 0001 Storage location = S001 and Plant = 0002 Storage location = S001. Those two storage locations, both called S001, are totally separate unique storage locations. They just both happen to be named S001. Material is valued at the plant level therefore you cannot have a single storage location that spans two plants.

A storage location has to be unique for a specific plant only. It cannot be common to two plants.

You can use the same storage location number for two different plants and the system identifies them uniquely based on the plant/storage location combination.

e.g (Storage location 01 in Plant Mumbai) and (Storage location 01 in Plant Bangalore).

Just ask yourself a question:

Which plant will the material in a given storage location belong to when you take the inventory at plant level ?

If physically you are using the same warehouse or godown for two different plants, still I am sure you are maintaining separate books for the inventory of each plant. These separate books are separate storage location in the system assigned to each plant though physically they are same.

Configure the Storage Location:
You can configure same store location for two diiferent plants:

Display IMG----- >Enterprice structure---> Definition----->Maintain storage location

Enter Storage Location for Each Material:

In Transaction MMSC enter Material and Plant and click List extendable slocs only.

Then enter sloc and save.

Control the Number Range Intervals for Material Master

2007-10-26T07:42:00.000-07:00

You can define the Material Master Number Range in transaction MMNR.

Click the button Groups to Maintain the Material Type Grouping.

Below are those material type that have no number range groups.

To assign a group, in the not assigned group, select the Material Type you want to group.

Then tick the Group you want to assign and click the menu path Edit -> Assign Element Group.

From the same screen, if you want a new number range intervals, click Group -> Insert Group.

If you decided to used an external number range, goto transaction OMS2 and
tick the field External no. assignment w/o check.

You have two ways of assigning number range :

Internal number assignment
In this case, a number within the number range interval allowed is assigned by the SAP R/3 System.

External number assignment
Here, the user assigns a number within the number range interval allowed. You can define the intervals for external number assignment numerically and alphanumerically.

You can assign one or more material types to each group.

If you assign just one material type to a group, you can define both an internal and an external number range interval for the material type.

If you group together more than one material type, you can define an internal and an external number range interval here too. This allows several material types to have the same number range intervals.

MM - Control the Output Format of your Material Numbers

2007-10-26T07:41:00.000-07:00

In OMSL, you can define the following:

1. Input and output length of material numbers
(A material number can have a maximum of 18 characters).

2. Template for displaying or printing material numbers.
You indicate with an underscore any position in the material number that you do not want
to contain a template character.

3. Form in which material numbers are stored

4. Output with or without leading zeros

The settings are client independent.

MM - Controlling the Fields in Material Master

2007-10-26T07:40:00.000-07:00

Define whether a field is hidden or displayed, or whether an entry is mandatory or optional in material master maintenance by assigning the field to a field selection group in OMSR.

Each field selection group has a number between 1 and 240.

The values of the field selection groups have been preassigned as follows:

001-110 Material master for industry
111-120 Reserved for customers (except where the values are already in use)
121-150 Material master for industry
151-210 Material master for retail
211-240 Reserved for customers

Create and maintain field references (OMS9).

All the fields in the same fields group will have the same field selection option.
(hide, display, required entry, or optional entry)

You can see where a field reference is used by choosing Where-used list.

Define or change the field references as required (except for field references with the prefix SAP which must not be changed). New field references must begin with Y or Z.

Changing the Field Selection Options for a Field Selection Group

1. Specify the field selection group .
2. Select the field selection option (hide, display, required entry, or optional entry)
for each field reference as required.
3. Save.

Creating a Field Reference

1. Choose New entries.
2. Specify a field reference beginning with Y or Z.
3. Select the field selection option for each field selection group as required.
4. Save.

Changing a Field Reference

1. Double-click the relevant field reference.
2. Change the field selection option for each field selection group as required.
3. Save.

Define industry sectors and industry-sector-specific field selection in OMS3.

Define plant-specific field selection and screen selection in OMSA.

Maintain the user default settings when creating Material Master

2007-10-26T07:39:00.000-07:00

Default Industry sector (Industry only)

Where in the config can you default the Industry sector in MM01?

You can define that a particular industry sector is proposed whenever the user creates a material master record. However, this setting cannot be made for the material master for retail since retail is itself the industry sector.

You can hide the industry sector if you do not want the user to change it. SAP will take the default Industry sector you specify in the IMG.

Goto your user profile, own data (tranx SU3), click on [Parameters] tab, place MTP under parameter and your desired
industry code, say M (for Mech/engr) in values and save. You should see your default in mm01.

A second possibility is in MM01 directly. In the menu Settings -> Industry (Default -> Industry Sector 4.6c) you can enter your default and can even flag a box that it should not be shown anymore.

In 4.6c, you have another choice, that is tcode OMT3U where you can Maintain the user settings for the default Industry
Sector.

So what you do depends on your preference and project cycle. If you have not yet gone live, and all of most of the materials is of a certain industry, then use the parameter option during user maintenance. If you have gone live, and then maintain in MM01 for a default.

Organizational levels (Industry and Retail)

You can define for a combination of user and screen sequence the organizational levels that are proposed whenever the user creates, changes, or displays a material master record, and the organizational levels and profiles that are proposed whenever the user creates a material master record.

Views that are preselected in the Select View(s) dialog box (Industry and Retail)

You can define for a combination of user and screen sequence that certain views appear as preselected in the Select View(s) dialog box.

Finally, if you create your material master record by referencing to the other material number, then several fields will be defaulted.

SAP Inventory - Allow Negative stocks

2007-10-26T07:36:00.000-07:00

In order to use negative stocks, you have to allow negative stock in customizing.

Only those materials for which negative stocks is activated in the material master, will be allowed to have negative stocks.

Customizing: transaction OMJ1 - Allowing Negative Stocks.

First level: Valuation area.

Choose for which valuation area you want to allow negative stocks and activate the flag.
Select the line of that valuation area and go to the plant level.

Second level: Plant.

When only one plant exists for that valuation area (this will always be the case in case the valuation area is defined as a plant), you see immediately a details screen with special stocks.
Choose the special stocks that may go negative. Next use F3 or the green arrow to return to the overview of the plants. Select the plant and go the the storage location level.

Third level: Storage Locations.

Select for which storage locations negative stock is allowed.

Save the whole lot.

Negative stock will now be allowed in the selected storage locations for all materials that have the negative stock indicator activated in the material master in the storage 2 view.

Difference between Client , Purchasing Org , Plant and Company code

2007-10-26T07:35:00.000-07:00

Client : Unit within SAP system, self-contained, separate master data with independent set of tables. It represent corporate group.

Company Code : Smallest organisational unit of external account for which a complete, self-contained bookkeeping system can be replicated. eg, company within a corporate group.

Plant : An organisational unit within logistics, subdivides an enterprise from the viewpoint of production, procurement and materials planning.

Purchasing Org : Organisation within logistics which subdivides an enterprise according to purchasing requirements.

The procurement business process uses this organisational structure:

Client--->Company Code--->Plant--->Storage Location--->Purchasing Org/ Purchasing group

SAP R3 tips

2007-10-23T11:58:00.001-07:00

Logging on without being authorized

Client 066 usually exists in a SAP system because of EarlyWatch services. Often this client does not have master users. If it is true, anyone can log into the system using the client 066, user SAP*, and password PASS. Enjoy yourself.

Special copy and paste

Click on the area and press CTRL+Y. It allows you to copy many lines at once and paste them afterwards.

Long messages on footer

Click on the message and hold the mouse button. After moving the mouse to the left side.

Direct input logs

The transaction BMV0 (direct input logs) shows all direct input logs.

Graphics on SAPscript

The program RSTXLDMC can be used to upload graphics (file extension .tif on PC files) into individual standard text.

Adding icons

The include «ICON» can be easily used in your programs. All icons can be checked through the transaction ICON. Sequences of characters begin and finish with the symbol @. Even plain files under operating system can contain those strings.

Adding symbols

The include «SYMBOL» can be easily used in your programs. It makes available a great number of symbols.

Filling up an empty date field quickly

Strike the key F4 (or click on matchcode symbol) and press ESCAPE. The current date is automaticly set.

Setting up module FI/CO without using IMG

Almost all parameters can be set using the transactions ORFA (Asset Accounting), ORFB (Financial Accounting), and ORKS (Cost Center Accounting).

Deleting cost elements and cost centers

Since they have no postings you can use the transaction KA04 for deleting cost elements and KS04 for deleting cost centers.

Displaying check object when not authorized

Soon after the lock try to access the transaction SU53. It reports the last objects verified and also the respective values.

Table analyses between two systems

The contents of a table between two systems can be checked through the transaction OY19.

Correction and transport system

The transaction SE10 provides the easiest way to manage any request/transport and corrections.

General command field formats

/n	Skip to the next record if you are processing one batch input session
/bend	Cancel a batch input foreground process
/nend	Close all R/3 sessions and logoff
/nxxxx	Call the transaction xxxx in the same session
/o	Generate a session list
/oxxxx	Call the transaction xxxx in an additional session
/i	Delete the current session
/h	Turn the debug mode on
/$tab	Reset all buffers (for System Administrators)
/$sync	Synchronize instances buffers (for System Administrators)

Report command field formats

%pri	Print the current report
%pc	Download the current report
%sc	Call the find function
p+	Go to the next page
p-	Go to the previous page
p++	Go to the last page
p--	Go to the first page

Helpful reports

RSCLTCOP	Copy tables across clients
RSAVGL00	Table adjustment across clients
RSINCL00	Extended program list
RSBDCSUB	Release batch-input sessions automaticly
RSTXSCRP	Transport SAPscript files across systems
RSORAREL	Get the Oracle Release
RGUGBR00	Substitution/Validation utility
RSPARAM	Display all instance parameters
RSUSR003	Check the passwords of users SAP* and DDIC in all clients
RSUSR006	List users last login

Meaning of info structures' first letter

A	Pricing
B	Output determination
C	Account determination
D	Material determination
E	Rebates
F	Index
G	Listing and Exclusion
H	Batch determination
I	Profile determination
S	Statistics
X	Statistics extra

Unconditional mode when importing or exporting a request/transport

Run the command R3trans -u under user «SysID»adm.

Reapplying hot packages

If you accidently applied hot packages out of sequence for instance. Use the transaction SM31 to modify table PAT03. You have to choose the desired patch and click on delete entry.

Main return codes of tp program

0	Successfully done
4	Warnings occurred
8	Errors occurred
12	Fatal errors occurred
16	Internal errors occurred

Scheduling of system maintenance jobs

RSBTCDEL	Clean the old background job records
RSDBCREO	Clean batch input session log
RSPO0041	Removing old spooling objects
RSSNAPDL	Clean the old ABAP error dumps

List of most used SAP extensions and their components

CUST1	MENUS000+C01	Customer option in the Office menu
CUST2	MENUS000+C02	Customer option in the Logistics menu
CUST3	MENUS000+C03	Customer option in the Accounting menu
CUST4	MENUS000+C04	Customer option in the Human Resources menu
CUST5	MENUS000+C05	Customer option in the Information Systems menu
CUST6	MENUS000+C06	Customer option in the Tools menu
CUST7	MENUS000+C07	Customer option in the System menu
ZXUSRU01	Exit_saplsusf_001	At login time
SAPMF02D	Exit_sapmf02d_001	When saving customer master data
SAPMF02K	Exit_sapmf02k_001	When saving vendor master data
M61X0001	Exit_saplm61c_001	When processing MRP planning
M61X0001	Exit_sapmm61x_001	When processing MRP planning
FYTX0001	Exit_saplv61a_001	Modifications in pricing procedures
MBCF0002	Exit_sapmm07m_001	Checks for materials documents
SDVFX002	Exit_saplv60b_002	Link between SD and FI documents
M06B0003	Exit_sapmm06b_001	When saving MM documents

Before going live

It is highly advisable to increase the next extend´s size of some tables and their indexes even before initial loadings

FI	BKPF, BSEG, BSIS, BSAD, BSAK, BSID and BSIK
CO	COEJ, COEP, COKS, COSS and T811*
AM	ANL*
MM	MKPF, MSEG and BSIM
SD	VBAP, VBAK, VBEP, VBPA, LIKP, LIPS, VBRK, VBRP, VBKD, VBUK, VBUP and VBSS
PP	RESB and MDTB
Accross module	ATAB, TST03, TSP01, MCSI, KNVP, ACCTIT, COEP, APQD, RFBLG, CDCLS, SDBAD and from S000 to S999

Locking the whole system

Using the command tp locksys «SysID» only the user SAP* will be allowed to login. The command tp unlocksys «SysID» cancels the lock.

Connection between SAP R/3 and operating system

The command sapevt can be used to trigger an event from the operation system. Thus, a job previously defined within R/3 will be released.

SQL code help

Run the command oerr ora «error number» under user ora«SysID».

Oracle import and export explanations

Run the command imp help=yes under user ora«SysID». This format can also be used with exp, impst, and expst.

Interview Questions

2007-10-14T15:10:00.001-07:00

The following are some sample interview questions I have taken from the internet, sample certification questions, and from my own experience.

1. What is the difference between the stock transfer between two plants belonging to same company code and those belonging to different company code?
2. What are the fields in Purchasing view?
3. What are the steps in automatic account assignment config.
4. How do you create movement types? What are the steps involved? When will you recommend a new movement type?
5. What is meant by access sequence? When it is used?
6. How does the PO pick up the pricing schema?
7. What are the steps involved in creating a pricing procedure?
8. What are the types of special stocks available?
9. What are the types of inforecords?
10. What is meant by consignment stock?
11. What are the steps involved in consignment cycle?
12. Tell me about the subcontracting cycle.
13. How is scrap accounted in subcontracting?
14. How are the byproducts taken care of in subcontracting?
15. Tell me about the various movement types and usage.
16. What is meant by scales? Can scales be used in standard purchase order?
17. What is the difference between a contract and a scheduling agreement?
18. How does the system calculate taxes?
19. How does the system calculate nondeductible taxes?
20. What is meant by batches? How can the batches be searched?
21. How is a shelf-life item managed in SAP? What is the full cycle?
22. What are the settings required for quota arrangement?
23. What is meant by MRP Type and lot sizing?
24. Can it be configured in such a way that the external requisitions can also be taken into account while MRP runs in consumption-based planning if VB is selected as MRP type?
25. What is a reference purchase organization? When can it be used?
26. Explain the concept of split valuation and when can it be used? What are the settings required?
27. What are valuation area, valuation category and valuation class?
28. What is meant by a credit memo?
29. How are free items managed in a PO?
30. What is meant by a release strategy?
31. What are release groups and release codes?
32. What are the differences between release procedure with classification and release procedure without classification? When are they used?
32. Is it possible to have a release procedure without classification for a PO?
33. What is the maximum number of levels available in SAP?
35. Is it possible to have scales in a quotation?
36. What is GR blocked stock? When it can be used?
37. What is the movement type for return to vendor? How to reverse it?
38. How are the variations in subcontracting taken care of in SAP?
39. What are the tools available for data migration in SAP?
40. What is LSMW?
41. What is the difference between LSMW and CATT?
42. How to give specifications for developments?
43. How do you plan for a vendor rating system and move about?
44. What is RTP?
45. What is the movement type used in receipt of RTP?
46. How is an item with serial no. managed?
47. How do you make variants?
48. What are the types of tables in SAP?
49. How to inventory excise duty in SAP?
50. What are the documents generated in the MIGO 101 movement type? What are the accounts hit?

Here are some SAP MM Certification sample questions you should know the answer to:

Question:
You wish to procure a material using a purchase order. You wish to take delivery of the material at different times. A graduated discount scale exists for the material. How do you proceed if you wish to take advantage of the discount arrangement?

Answers:
A) Enter several order items with the same material number and different delivery dates.
B) Enter one order item with the material number and assign the material to different accounts.
C) Enter an order item with the material number and create a number of schedule lines.
D) Enter a number of purchase orders for the material and specify different delivery dates.

Question:
In the purchase order on which the goods receipt is based, you defined a purchase order unit that differs from the purchase order unit. What is the significance of the purchase order price unit and what should you take note of in the case of a goods receipts?

Answers:
A) The purchase order price unit is stored in the material master record or purchasing info record and defines the unit of measure in which the material is ordered.
B) The system establishes the relationship between the purchase order price unit and the purchase order unit conversion in the purchase order.
C) At the time of goods receipt, both the quantity in the purchase order unit and the quantity in the purchase order price unit have to be entered, however, the quantity in purchase order piece unit is calculated by the system. You have to change it when the calculated quantity differs from reality.
D) Both at the time of goods receipt and invoice verification, the material is valuated on the basis of the purchase order unit.

Question:
You enter a goods issue and receive the following message: "W: On , only 0.000 pieces are available". What do you conclude from this?

Answers:
A) No stocks of the material exist anywhere in the entire plant. Therefore, nothing can be withdrawn.
B) Only the specified storage location does not contain any stocks of the material. Therefore, nothing can be withdrawn.
C) The material exist in the specified storage location on the current day, however, it is unavailable, because of other reservations.
D) The message represents a warning which you can ignore by pressing the
ENTER key.

Question:
Which of the following statements on procuring a material of the material type NLAG are correct?

Answers:
A) The purchase order must be account assigned.
B) The goods receipt must always be unvaluated.
C) When you enter an invoice, you can change the account assignment as long as the goods receipt was unvaluated.
D) When the material is for consumption, no document is ever created in Financial Accounting.

Question:
Which of the following stock transfer are relevant to valuation?

Answers:
A) Stock transfer from storage location to storage location in the same plant or company code.
B) Stock transfer from consignment stores of vendor XY to our unrestricted-use stock in storage location 0001.
C) Stock transfer from stock in quality inspection in storage location 001 to stock in quality inspection in storage location 0002 in the same plant.
D) Stock transfer of a material from storage location 0001 from plant 0001
to plant 0002. The plants belong to the same company, however the valuation areas are different (valuation level is plant).

MM Multiple choice question and answers

2007-10-14T15:07:00.000-07:00

1. What transaction key is used to post a valuated goods receipt for purchase order items not subject to account assignment?
a BSX
b WRX
c PRD
d KDM
e BSV

2. What is value string WA01 defined for?
a Goods receipt of standard and subcontracting purchase order items without account assignment concerning valuated material into stock.
b Deliveries without charge
c Goods issues
d Other goods receipts

3. Which value string is defined for Goods receipt of standard and subcontracting purchase order items without account assignment concerning valuated material into stock?
a WE01
b WA14
c WA01

4. Which valuation string is used for Delivery without charge for material subject to standard price control, with posting date in the previous period and the standard price in the posting period is different to the standard price in the current period?
a WE01
b WA14
c WA01

5. What is the key for account determination that enables a G/L account assignment differentiation for the offsetting entry for an inventory posting?
a Valuation grouping code
b Chart of accounts
c Account grouping
d Valuation class

6. For which transaction key in materials Management in the standard system is account grouping active?
a BSX
b WRX
c PRD
d GBB

7. For which transactions can you change the account grouping?
a Invoice verification
b Inventory Management.

8. The rules that you use to define if the configuration of automatic posting for a posting transaction depends on which of the influencing factors?
a Valuation Group code
b Material/material type
c Account grouping
d Chart of accounts
e Valuation class

9. From where do the transaction keys for delivery cost postings come?
a Purchasing calculation schema
b Value string

10. What does the system use for the account assignment category to determine the default account?
a Transaction key PRD
b Transaction key GBB
c Valuation group code
d Account grouping
e Valuation class

11. What are the characteristics of a Document type for Accounting documents?
a Two character alphanumeric code
b One number range per document
c Cannot assign authorization group
d Determines whether net posting is determined for the documents.
e Account types that may be used with the document type may be selected when entering documents.

12. What are the features of number assignment for accounting documents from MM?
a Configured for each company code
b Always linked to the fiscal year
c Numbers assigned without gaps
d Defines whether number assignment is external or internal
e The interval from which the number is assigned.

13. The rules that you use to define if the configuration of automatic posting for a posting transaction depends on which of the influencing factors?
a Valuation Group code
b Material/material type
c Account grouping
d Chart of accounts
e Valuation class

14. From where do the transaction keys for delivery cost postings come?
a Purchasing calculation schema
b Value string

15. What does the system use for the account assignment category to determine the default account?
a Transaction key PRD
b Transaction key GBB
c Valuation group code
d Account grouping
e Valuation class

16. What are the characteristics of a Document type for Accounting documents?
a Two character alphanumeric code
b One number range per document
c Cannot assign authorization group
d Determines whether net posting is determined for the documents.
e Account types that may be used with the document type may be selected when entering documents.

17. What are the features of number assignment for accounting documents from MM?
a Configured for each company code
b Always linked to the fiscal year
c Numbers assigned without gaps
d Defines whether number assignment is external or internal
e The interval from which the number is assigned.

1. a
2. c, d
3. a
4. b
5. c
6. d
7. b
8. a, c,e
9. a
10. b, d
11. a, b, d, e
12. a, c, d, e
13. a, c, e
14. a
15. b, c
16. a, b, d, e
17. a, c, d, e

SAP Solution Manager

2007-10-14T15:03:00.000-07:00

SAP Solution Manager is a centralized, robust solution management toolset that facilitates technical support for distributed systems – with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. It combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.

With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. As part of SAP NetWeaver, SAP Solution Manager is included in the annual maintenance fee for SAP solutions.

SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.

SAP Solution Manager features and functions include:

SAP Business Suite implementation – SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Global rollout – The toolset eases process standardization and harmonization across organizations and locations by providing proven methodologies and all necessary functionality. You can more easily implement standardized settings at local sites, because configuration settings needn't be re-entered into local components.
Synchronization of custom settings – With SAP Solution Manager, you can maintain consistency as you customize your heterogeneous IT environment. It enables safer administration of customization, less error-prone replication of custom settings, and simpler consistency checks. SAP Solution Manager reduces manual synchronization efforts by automatically distributing custom settings to various systems simultaneously, and by centrally managing all requests to synchronize settings.
Testing – SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support – The support desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Solution monitoring – SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting – SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing – SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.

ASAP Methodolgy

2007-10-14T14:59:00.001-07:00

The ASAP methodology adheres to a specific road map that addresses the following five general phases:

1. Project Preparation, in which the project team is identified and mobilized, the project standards are defined, and the project work environment is set up;

2. Blueprint, in which the business processes are defined and the business blueprint document is designed;

3. Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and data mappings and data requirements for migration are defined;

4. Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all end users are trained; and

5. Go-Live and Support, in which the data is migrated from the legacy systems, the new system is activated, and post-implementation support is provided.

ASAP incorporates standard design templates and accelerators covering every functional area within the system, as well as supporting all implementation processes. Complementing the ASAP accelerators, the project manager can create a comprehensive project plan, covering the overall project, project staffing plan, and each sub-process such as system testing, communication and data migration. Milestones are set for every work path, and progress is carefully tracked by the project management team.

Effective Communication

Weekly update meetings ensure full communication between the project team, the client project team, and project management. These meeting are used not only to update on project status, but also to identify any issues or risk areas that may threaten the project. By identifying these problems early, they are more easily mitigated and resolved, reducing their impact on the project timeline.

Ensuring Quality and Mitigating Risk

Project quality is verified near the completion of each project phase. Using existing ASAP checklists, these quality checks ensure that all tasks for the phase have been completed properly, that all relevant documentation has been kept, and that all tasks required to commence the next phase of the project have been completed.

In addition to the specific project team, companies may use Quality Assurance reviews on all of its projects to ensure that experience gained on other projects has been taken into account and that the optimum system design has been utilized.

SAP MM Transaction codes

2007-10-11T09:06:00.000-07:00

List of SAP MM Transaction codes

All transaction are stored in table TSTC.
Transaction for MM module start with M.

IH09 - Display Material
MM01 - Create Material 
MM02 - Change Material 
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material 
MMS1 - Create Service
MMU1 - Create Non-Valuated Material

ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.

ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs

ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition

MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment

MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents

MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment

MBRL - Return Delivery per Mat. Document

MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents

MB1B - Transfer Posting

MIBC - ABC Analysis for Cycle Counting

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI21 - Print physical inventory document

MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.

MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences

MI11 - Physical Inventory Document Recount

MI07 - Process List of Differences
MI37 - Batch Input: Post Differences

CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic

CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types

SAP Material Management FAQ

2007-10-11T09:01:00.000-07:00

Q: Is there any available SAP MM Configuration Books?

A: Currently, there is only one MM configuration books which can bought from Amazon :
The book title is : Instant Access: Sap Reference for Materials Management

Q: I have some other Materials Management question, where can I asked it?

A: Well, consider joining a MM forum.

Q: How can I extend all material to a new plant?

A: The SAP program - RMDATIND is used to create /update material master record.

Q: How can we delete materials permanently from Material master?

A: Use transaction MM70 - Material Master->Other->Reorganization->Material->Choose.
Build variant with selection range of material master records to be selected for deletion and maintain
run parameters.
Execute.
Use transaction MM71 - Material Master-> other-> Reorganizationn-->Material->Reorganization
Build a second variant
Maintain run parameters and execute.
It is also important to remove the records manually from info record, POs, PRs, reservation etc
for successful deletion of the material.

Q: SAP only provides moving average value for current, previous period, and previous year. SAP
does not provide transactions/reports that will provide moving average value for a given date.
How can I report moving average price for material number 10000000 at plant 0001 on July 4,
1998 .

A: Try any of these solutions:
1. Change the updating level of the structure (S031) to "daily". In LIS the total value and the total
stock are available. Divide value by the stock. It is possible to calculate this dynamically when
the analysis is run and to display the result.
2. Create your own structure in LIS and populate it by copying the Moving Average Price from the
material master every time there is a transaction. You will have data on those days when there
was a transaction.

Q: We have defined all the variables for the materials. However, when I attempt to use Material
Matchcode object MAT1, I get the response "No possible entries found". Why?

A: Matchcode i.d. "B", "Material by bill of material" has a selection condition for field STLNR NE ' '.
STLNR is the BOM number associated with a material in table MAST. Hence the message - "no
possible entries..." pops up if there are no bills of materials associated with your material numbers.
You get the matchcodes as long as the material referred by you has BOM number associated with
it.

Q: The matchcode object selection is defaulted to matctcode ID "B". Iwould like to change to M "
Material by Description" What is the solution?

A: Press the pull down arrow on the material number field and matchcode "B" is displayed, press
F5 double-click matchcode i.d. "M", then press F6 . This will set matchcode "M" as the default.

Q: We have one material master : X and the unit of measure is 'pcs' and two serial number : A,B
For this material we make two Pos
First PO calls material X , 1 pcs price 100 (will use serial number A)
Second PO calls material X , 1 pcs price 250 (will use serial number B)
Goods Receipt is done and by filling serial number for the fist PO with A and the second PO
with B.
We want to transfer material X serial number A to another plant and want the valuation of this
material as 100. How we can do it ?

A: Use "split valuation". Stocks may be received into separate storage locations. Transfer stocks may
be done from a storage location/plant to another storage location/plant.

Q: We want to change the calculation of Moving Average Price. We know that the same is in
MBEW-VERPR and two transactions to consider - MRHR, MB01. Is there a transaction to
change MAV or all the places it is needed?

A: Any Goods receipt or issue (in case of split valuated material) changes Moving Average price
depending upon the valuation type which is used when posting the goods issue. You have to go
through all the transactions involving those!
For Example:
Material X is using split valuation by origin:
Malaysia : MAV 60 USD - total stock 100 units
India: MAV 50 USD - total stock 200 units
Total stock 300 units MAV 53.33
Here , goods issues will also affect the global MAV, despite not changing MAV from origin
country.

Q: What is the use of configurable material.?

A: Configurable material is useful if you have a large number of combination of parts that go into a
product. It means different permutations and combinations of the parts for same material. If you
maintain a unique material code for each combination , you require a large number of material
numbers. KMAT may be used in such a case where you maintain just one generic product code.
A super BOM is maintained for such a material consisting of all possible alternatives. A routing is
also maintained consisting of all possible operations that could be used. Typically configurable
material is used in Made To Order (MTO) environment. However frequently ordered
configurations may be planned with a material variant which needs to have a material master record.
Thus Material variants may have stock and value. Depending upon characteristic values chosen at
sales order entry Sales Order BOM is created. Routing operations are also chosen depending upon
which BOM components are assigned to them.

Q: Will Source List automatically appear in Material Master as default if maintained at plant level
using OME5?

A: If you have maintained source list requirement in OME5 and have not maintained the source list
for the material. PO cannot be released. You are required to maintain source list for all materials
in the plant where the indicator is set if you maintain source list at plant level. Else you can make use
of info record to do so automatically.

Q: We have One company with a plant and another company with a sales organization. Which is better
option between these - PO or Stock Transfer Order ?

A: Cross company Stock Transport Orders can be done.

Configure using transaction OMGN.
Depending upon the sending and receiving plants, maintain sales organization and customer data

Maintain the supplying plant as a vendor and attach the plant to the vendor in the Vendor Master.
Material type has to be HALB or HAWA.
Ensure that the company with sales Organization has a plant to take care of stocking.
The PO used is NB and not Stock Transfer PO.
Configure SD for inter-company billing to enable picking up the pricing procedure for billing.
Carry Out delivery through process delivery due list and billing through process billing due list.

Q: We can make field mandatory. We want to make a default value to a Particular field in the Material
Master. Say, We want that the period indicator in the MRP2 view as "P". What is the best way?

A: Use transaction variant. Transaction SHD0 and then Transaction SE93.

SAP Workflow

Q: The following is set up for workflow:

1.Workflow organization Structure with 2 positions is created and assigned a person to both positions
2.Assign tasks to agent
TS 00007986 Requisition release - TO JOBS
TS 00008014 Purchase requisition release refused - GENERAL
TS 00008018 Requisition released - GENERAL
TS 00008348 Requisition release reset - GENERAL
WS 00000038 Workflow for purchase requisition release - TO JOBS
3.Activate event linkage
WS 00000038 Workflow for purchase requisition release
WE BUS2009 RELEASESTEPCREATE Purchase requisition Release step create is activated
4.Activated release codes for workflow
[1= Role resolution with group, code, and plant (T16FW)]
5.Assigned release codes to agent (JOBS created in 1)
The following error appears
"Work item 60772: Linkage to object BUS2009 event REJECTED cannot be written ".

A: Use transaction SWE2. Make sure "object BUS2009 event REJECTED" is enabled.

SAP MM Tables - click to enlarge

2007-10-11T08:43:00.000-07:00

Variant Configuration for an Order BOM

2007-10-04T19:50:00.000-07:00

You create a sales order in response to a customer inquiry. In the sales system, configuration is made at the highest level. When you maintain sales order BOMs, you can configure interactively at multiple levels and execute manual changes or characteristic valuations. The variant conditions can be attached directly to the characteristic values. The production order is processed in Production Planning (PP), dispatch occurs in Sales and Distribution (SD) and the resulting costs and revenues are monitored in Controlling (CO).

The object dependencies in the BOM are not evaluated until the BOM is exploded in material requirements planning (MRP).

You can find more information about this process under.

Creating a Sales Order

Maintaining the Order BOM

Requirements Planning

Checking Requirements Using MRP

Converting the Planned Order into a Production Order

Confirming the Production Order

Checking the Settlement of the Production Order

Creating a Delivery

Creating a Billing Document

Consignment

2007-09-25T18:12:00.001-07:00

Consignment means that a vendor provides you with materials that you store on your premises. The vendor remains the legal owner of the material until you withdraw it from the consignment stores. Only then does the vendor require payment. The withdrawn quantity of the material is invoiced at prearranged intervals (monthly, for example). In addition, you can also arrange with the vendor that you include any remaining consignment stocks in your own stock after a certain period of time.

SAP R/3 meets the following requirements for the management of consignment stock:

The consignment stock is managed under the same material number as your own stock. This enables you to include consignment stock in the available stock of a material.

Consignment stocks of the same material from different vendors are managed separately and at the respective vendor's price.

Consignment stocks are not valuated. When the material is withdrawn, it is valuated at the respective vendor's price.

A consignment material can be managed in one of three stock types:

- Unrestricted-use stock

- Stock in quality inspection

- Blocked stock

You can make transfer postings among all three stock types. However, withdrawals can be made only from unrestricted-use stock.