Material created in MM01 but showing locked in MM02

Material created in MM01 but showing locked in MM02

The problem could be that the update task is running very slowly, or stopped altogether.

Remember that SAP updates don't really happen immediately, they are queued for update, although with everything working well this should be invisible.

If there is a problem, the update task can stop and so queue ALL updates behind it until someone resolves the problem.

Speak to your Basis people and ask them to the update task. (you can have a quick look by using SM13 and selecting "to be updated" this should be empty or nearly empty).












Material created in MM01 but showing locked in MM02

Unit KG is not Created in language EN (Error in transaction MMBE)

Unit KG is not Created in language EN (Error in transaction MMBE)

Problem:

When running MMBE to verify the stock, system showing the stock as per the given parameters for Unit of Measurement (e.g., EA). After executing the report, at header level, when changing the Unit of Measure (to E.g.,KG), the system is throwing the message "Unit KG is not Created in language EN".

But if the same MMBE is executed by providing the Unit of Measure as KG, the report execution is fine.

Solution:

• Go to transaction CUNI.
• Select the Unit of Measure for "MASS" from the drop down list and check the entries for UoM's.
• Check for the entry "KG" with an English description.
• If the above entry is available, then check for the case sensitivity of UoM.
  

Unit KG is not Created in language EN (Error in transaction MMBE)

Difference between MM01 and MMH1

Difference between MM01 and MMH1

By Madhu

The idea is that if you want to have a transaction that will only create HAWA materials then you can use MMH1. The end result is EXACTLY the same but in MM01 you have to specify the material type you want to use, in MMH1 it is already assumed.

There are other transactions for other material types and you can configure the material type you want used by each, so you can use your own material types instead of the standard SAP ones.





Difference between MM01 and MMH1

Consolidate the same line item quantity from different Purchase Requisitions and create one line item with consolidated quantity (instead of having mu

Consolidate the same line item quantity from different Purchase Requisitions and create one line item with consolidated quantity (instead of having multiple times same line item with different quantities)

By Madhu

Follow these steps to achieve the functionality:

• Go to ME21N
• Click on "Document Overview On" (Mostly it will get open by default)
• Click on "Selection Variant"
• In Pull down list select "Purchase Requisitions"
• New screen will get open, enter your material number and execute.
• All PRs will be listed in ME21N Screen.
• Drag and drop the first PR in the header level shopping cart. (shopping trolley symbol)
• Item will get updated.
• Now go to item details and click on "Delivery Schedule" Tab.
• Here also you can see a shopping cart.
• Now drag and drop all the PRs in this shopping cart.
• Now all the PRs qty. will get updated in single PO line.

Consolidate the same line item quantity from different Purchase Requisitions and create one line item with consolidated quantity (instead of having multiple times same line item with different quantities)

Difference between purchase organization, reference purchase organization and standard purchase organization

Difference between purchase organization, reference purchase organization and standard purchase organization

By Madhu

Normal Purchase organization is to procure either for the plant/entire company code/cross company level based upon assignment settings in SPRO.

For Reference Purchase organization, it will be simply assigned to other normal Purchase organizations only but neither assigned to any plant or company code. This is useful to enjoy the corporate contracts and their price benefits.

Regarding Standard Purchase organization, it is to handle procurement of special stocks








Difference between purchase organization, reference purchase organization and standard purchase organization

Inventory Vs Warehouse

Inventory Vs Warehouse

Warehouse management is the management of stock that is placed in very specific storage areas such as shelves, bins, racks etc.

SAP WM (Warehouse management) has full functionality including the ability to suggest the placement of the stock received into specific bins in tne warehouse, taking into consideration things like the weight and volume of the stock that the bin can hold and special considerations like keeping apart certain types of materials.

in inventory management the stock is only managed down to a storage location level.

So if you have stock that is managed in bins, shelves and racks etc. and you want SAP to manage the placement and removal of that stock then you need Warehouse Management, if not then you simply use SAP inventory management.



Inventory Vs Warehouse

Creating one GR document for multiple POs

Creating one GR document for multiple POs

Creation of one GR document for multiple POs can be achieved using the transaction MIGO / MB01, provided all POs belong to one vendor.

In MIGO transaction, Enter the PO's one by one. Once you enter a PO, the line items would get copied and the PO field would become blank. This way, we can enter multiple PO's belonging to a single vendor.


Creating one GR document for multiple POs

Calculating total quantity supplied by a vendor in a particular period

Calculating total quantity supplied by a vendor in a particular period

• Go to Transaction MB51.
• Enter the vendor number and the also the period for which we need to calculate the quantity.
• Specify the Movement Types for only Goods Receipts (E.g., 101, 103, 105 and others). Do NOT specify the movement type 122.
• The output is the total quantity supplied by a vendor in a particular period.

Calculating total quantity supplied by a vendor in a particular period

Deactivation/Deleting a Movement Type

Deactivation/Deleting a Movement Type

Solution 1 (Preferred):

• Go to Transaction OMJJ
• Select the Movement type to be activated
• Remove all the transaction codes mentioned against this movement type under allow transaction tab.

Solution 2:

Consider this solution only if the above solution doesn't work.

Delete the movement type from the standard table. Ensure that you really don't want to use this movement type before deleting the entry or would never want to recreate the movement type.

It is possible to recreate the deleted movement type, but needs to be imported either from the client 000 or from the client this movement type is not deleted. You can not manually create/recreate the movement types in the standard SAP number range by creating them again.







Deactivation/Deleting a Movement Type

Difference between the transactions ME25 and ME21N

Difference between the transactions ME25 and ME21N

ME25 is useful when you want to create a PO but you are unsure if there is a valid source or if there is, which one to use.

With ME21N you have to specify the Vendor before you can do anything and so you must know the vendor when you start.

With ME25 you can enter all of the details and leave the vendor until last and use auto source determination if you want. Then if you still cannot find a source you can save it as a requisition instead and find and allocate a source later.

So if you KNOW the vendor that you are going to use, then create the PO via ME21N.

If you DON'T KNOW (or are not sure) of the vendor to be used (and if your company allow the use of this transaction), use ME25 instead.


Difference between the transactions ME25 and ME21N

MM Tables Link

MM Tables Link

MM Tables Link

MM Process Flow

MM Process Flow

The typical procurement cycle for a service or material consists of the following phases:

1. Determination of Requirements

Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

2. Source Determination

The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

3. Vendor Selection and Comparison of Quotations

The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

4. Purchase Order Processing

The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

5. Purchase Order Follow-Up

The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

6. Goods Receiving and Inventory Management

Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods.

7. Invoice Verification

The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.


MM Process Flow

Configuring the communication types as per Account groups in Vendor Master

Configuring the communication types as per Account groups in Vendor Master

By Madhavi

Background of the requirement:

1. Go to transaction XK02

2. Enter the vendor number and the company code. Select the “Address” check box from the “General Data” and press ENTER.

3. Click on “Other communication..”

4. Following communication methods are displayed in a pop-up box.

5. Our requirement here is to have “Internet email address” as a communication method and also we are not interested in communication type “Teletax”. So we need to add “internet email” and remove “teletex”.

Following is the procedure to achieve the same:

1. Go to SPRO à Financial Accounting àAccounts Receivable and Accounts Payable à Vendor Accounts à Master Records à Preparations for Creating Vendor Master Records à Define Account Groups with Screen Layout (Vendors)

2. Double click on your “Vendor Account Group”.

3. Double-click on “General data”.

2. Select “Communication”

3. Now in this screen, you can select the communication types you want to suppress, make an optional entry, required entry or display.

4. Since the “Internet mail address” is suppressed, this did not appear in our vendor master change transaction. Now let us make “Internet mail address” as optional and “Teletex” as suppressed.

5. Save and close this transaction.

Now execute “Vendor Master” change transaction again. This time you would observe that the internet email is appearing in your list and Teletex has disappeared.

Configuring the communication types as per Account groups in Vendor Master

Marking Material Master fields Mandatory/Optional

Marking Material Master fields Mandatory/Optional

By Sujatha

In this demo, we would try marking the field "Material Group" in MM01 as Mandatory. Please see the screenshot below from MM01. Here the field "Material Group" is not mandatory.

Get the technical details of the field "Material Group" by clicking on F1 and then "Technical help". Note the value in the field "Screen Field". Here it is MARA-MATKL.

Now go to Transaction SPRO -> IMG --> Logistics - General -> Material Master -> Field Selection -> Maintain Field Selection for Data Screens

Following screen appears:

Now using F4 help on "Field Sel. group", select the value MARA-MATKL.

Now scroll down the list to find the value MM01. i.e., we are trying to modify the properties of the field MARA-MATKL in the transaction MM01. Now click on the radio button "Reqd Entry" to mark the field as mandatory. Similarly, we can mark any field as optional or only as display field or hide the field.

Save your entries and check the field "Material Group" in the transaction MM01. See the screenshot below:

You can observe that the Material Group is set to Mandatory now.

Marking Material Master fields Mandatory/Optional

Tracking Changes made to the Vendor Master records

Tracking Changes made to the Vendor Master records

To track the changes made to the Vendor Master Records, use the transaction MK04.

Go to transaction MK04.

Enter the required Vendor number and press ENTER.

Screen similar to the following would appear:

The list of fields would vary depending upon the number of fields modified.

Double-click on any of the fields you want to track. Let us click on “Name”.

The old name and the new name are displayed here.

On double-clicking on the above record, a pop-up screen with more info is displayed:

Tracking Changes made to the Vendor Master records

Configuring stock transfer from one storage location to another within a Plant

Configuring stock transfer from one storage location to another within a Plant

By Shankar

Sometimes there might be a requirement for transferring stock from one storage location to another storage location within a Plant. This tutorial would detail the setting required in doing the same:

Go to Transaction SPRO.

Click on IMG -> Material Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Set up Stock Transfer between Storage Locations -> Activate Stock Transfer between Storage Locations

Following screen appears:

Check the above check box to make the stock transfer between storage locations active.

Configuring stock transfer from one storage location to another within a Plant

Marking reference field as mandatory when posting a document (Customer invoice, Vendor invoice, Customer Credit Memo and others)

Marking reference field as mandatory when posting a document (Customer invoice, Vendor invoice, Customer Credit Memo and others)

By Chandra Teja

This document details the procedure in marking the reference field as mandatory while posting a document like Customer invoice, Vendor invoice, Customer Credit Memo and others.

Go to transaction OBF4.

Click on the document type you require. For this demo, let us consider the document type DG (Customer credit memo). Select the document and click on Details.

Following screen appears:

From the above screen shot (the one highlighted), there is an option to mark whether the reference number should be made mandatory or not. Check the check box adjacent to "Reference number".

Now let us try to post a document (Customer credit memo) using the transaction FB01.

Without entering the Reference number, enter the other mandatory information and press ENTER. Following message would appear:

Mass Maintenance of Vendor Master Changes

Mass Maintenance of Vendor Master Changes

Scenario: In this scenario, we would set the deletion indicator for a set of vendor master records.

Go to transaction MASS

Enter the value LFA1 in the Object Type and click on Execute.

Select the record “Vendor Master (General Section)” (As shown in above screenshot) and click on tab “Fields”.

Scroll down the list and select the field “Deletion flag” (LFA1-LOEVM). Click on Execute.

In this screen, you can mention the list of Vendors we want to modify. For our demo purpose, let us mention A* (All vendors starting with A).

Click on Execute again.

All vendors starting with A are listed here. You can also observe a single character field at the end of each record, which is the deletion indicator. Here you can check this field to make it as marked for deletion.

If you want all the records to be marked for deletion, then check the checkbox in the table control shown below and click on “Carry Out a Mass Change”. (See the screenshot below and observe the highlighted ones).

On clicking the “Carry Out a Mass Change”, all the vendor records displayed on the screen are also checked for Deletion. Now click on SAVE.

You can verify the changes by looking at the table entries (Transaction SE11/SE16):

Mass Maintenance of Vendor Master Changes

Use of MRP indicator for capturing excise duties from dealer

Use of MRP indicator for capturing excise duties from dealer

By Anil Verma, KPIT Cummins

Scenario

While procuring from dealers, the dealer's invoicing amount is known but the excise duties amount are not known at the time of PO creation. The invoice price is taken as the PO price and the excise duties aren't calculated in the PO.

To capture the excise invoice corresponding to the incoming goods and to take credit for the excise duty component in the dealer's price, it is required to split the PO price into its two components - the excise base value and the excise duties amount.

In the transaction J1IEX or the transaction MIGO (in the excise item tab), the PO price defaults as the excise base value. The excise duty components are displayed as zero since this is computed as zero. If the excise duty value is manually changed and enter is pressed, the inserted value disappears.

Solution

In order to change the excise duty value and the excise base value in J1IEX or in the transaction MIGO (in the excise item tab), we must make use of the MRP indicator.

Capturing excise invoice through MIGO transaction -

The MRP indicator can be found by clicking on the 'More documents' button on the Excise invoice tab at the header level. This pops up a screen containing the 'Miscellaneous' tab. This tab contains a check box for MRP indicator. This MRP indicator checkbox must be ticked and then the excise base value and the excise duty values can be changed. Please note - the sum of the excise base and the excise duty values must always equal to the PO price. This is because in this step, the PO price is being divided into two components - the excise base value and the excise duty value.

The goods valuation will change accordingly. The material account will be debited with the excise base amount and not the total PO price amount.

Capturing excise invoice through J1IEX transaction -

The MRP indicator can be found on the ‘Miscellaneous’ [tab at the header level in J1IEX transaction. There is a checkbox for the MRP indicator on this tab. This MRP indicator checkbox must be ticked and then the excise base value and the excise duty values can be changed. Please note - the sum of the excise base and the excise duty values must always equal to the PO price. This is because in this step, the PO price is being divided into two components - the excise base value and the excise duty value.

At the time of invoice verification, the base amount must be entered as the changed excise base amount at the time of capturing the excise invoice, either thought J1IEX or MIGO. Then the tax can be calculated on this amount. This will sum to the PO price, which is the dealer's invoicing amount.

1. Create purchase order and enter net price (inclusive of base value and excise duties)

2. Excise duties not computed. (Excise duties = 0)

3. Capture of excise invoice

-Capturing excise invoice together with goods receipt through transaction MIGO.

MRP indicator found in the Miscellaneous TAB popped up when you click on more data button on Excise invoice tab at the header level in MIGO

The excise base value is defaulted as the PO price and the excise duties are zero. The excise base is changed such that the sum of the excise base value and the excise duties remain the same as the PO price. The excise base is reduced by the excise duty value and the differential amount is split amongst the relevant excise duty components.

Changed value.

Hence the material valuation also takes place correctly with the changed amount put as the excise base value. Otherwise the excise duty value would incorrectly inflate this also.

3. Invoice verification process through MIRO

Accounting Entries during MIRO.

Use of MRP indicator for capturing excise duties from dealer

Converting a Warning message to Error message and vice versa

Converting a Warning message to Error message and vice versa

By PC Teja, Ascent

Consider the following scenario:

Try creating a Purchase Order with the delivery date in the past (see the screenshot below):

Click on Save. You would get the following warning message:

Since the above is just a warning message, the end user can just press ENTER and save his document. To restrict the end user from doing this, we need to issue an error message instead of a warning message. Following is the procedure to convert this warning message to error message:

Go to transaction SPRO.

Click on Purchasing à Purchasing à Environment Data à Define Attributes of System Messages (See the screenshot below)

Following screen appears:

Click on ‘System messages’.

Following screen with the list of all System messages appears.

Now search for the message “Delivery date is in the past”.

Change W (Warning) to E (Error).

Save your entries.

Now run the purchase order transaction again and provide the delivery date somewhere in the past. Click on Save. Following error message appears:

Converting a Warning message to Error message and vice versa