Purpose of the document: How to print multiple copies of ERS Invoices

Introduction

In standard SAP, you cannot print multiple copies of ERS invoices like other logistics Invoices. So from this document you shall be able to know how multiple copies of ERS invoices are printed in SAP.

1.    Requirements

1.1 STANDARD SAP ERS Process

ERS [Evaluated Receipt Settlement] as the name suggests it is used for settling the amount for Goods Receipts made, without invoice for the same not being received from vendor. So SAP shall automatically generate Vendor Invoices for Goods Receipts made and Amount in Invoice is calculated from Purchase Order and Quantity from Goods Receipt.

Prerequisites:

• In Vendor Master, “AutoevalGRsetm Del” and “AutoevalGRsetm Ret” need to be checked. Thus vendor will become ERS enabled vendor.
• In Purchase Info Record, “No ERS” should not be checked.

Process Flow

When a Goods Receipt is made in SAP, it creates an entry in “ERS”(EKRS) table and as per the input conditions selected by the user, ERS program (RMMR01RS)  determines all the documents satisfying input conditions and allows us to generates the invoice documents as per the selection.

ERS Invoice is generated through TCode MRRL with any of the following input selection criteria.

• Company Code
• Plant
• Posting Date of GR
• Purchase order and PO Item
• Goods Receipt document for GR based IV

SAP Path

1. SPRO ->Materials Management ->Logistic Invoice Verification -> Evaluated Receipt Settlement ->Specify Automatic Settlement of Planned delivery Costs.

We need to maintain company code / Purchase Organization / Freight Vendor is maintained with check so that planned delivery cost maintained in Purchase Order gets settled while running ERS

2)SPRO -> Materials Management -> Logistic Invoice Verification -> Evaluated Receipt Settlement ->ERS Invoice Numbering -> Create Number Group

3) SPRO -> Materials Management -> Logistic Invoice Verification -> Evaluated Receipt Settlement ->ERS Invoice Numbering -> Create ERS Number Range

4)SPRO -> Materials Management -> Logistic Invoice Verification -> Message Determination -> Maintain Message Type

Output Type used for Printing ERS invoice is “ERS” and the same is maintained here

5)TCode: MRRL | | Logistics-> Materials Management -> Logistic Invoice Verification -> Automatic Settlement ->Evaluated Receipt Settlement

1.1FUNCTIONAL REQUIREMENT

In Standard SAP, ERS Invoice can be printed through “ERS” output type through TCode:MR90

Already Processed ERS Invoice

Input Selection

Output type: ERS
Processing mode: 2   (Repeat Processing)
Invoice document no : XXXXXXXX
Fiscal Year: XXXX

Now using transaction MR90 we tried to repeat process the output

  On execution of above it gives below message:
“ NO MESSAGE FOR REPEAT PROCESSING EXIST”

So here, ERS Invoice cannot or not able to print the ERS Invoice which is already processed or Printed.

  Whereas other logistics invoices are enabled to Print multiple copies and now this requirement is to print already processed or printed ERS invoices (multiple copies) through ERS output type.

FUNCTIONAL CONFIGURATION

Config As-Is in Standard SAP :                              

Path>NACE> Application MR>ERS Output type

  “CannotBeChanged” check box is activated as per standard SAP Package.

Config Changed to fix the Requirement:

“CannotBeChanged” check box is De-activated.

Now ERS Invoice is printed through Tcode MR90

Output type: ERS
Processing mode: 2   (Repeat Processing)
Invoice document no : XXXXXXXXX

Fiscal Year: XXXX

Thus , Multiple copies of Invoice can be printed.

Introduction:

Very often we get issues like stock shown in Material Master record with Stock available in MMBE . At the same time, valuated stock will not match with codes/reports like MCBE, MC.9, MB53. It is very important in Inventory Management to check that the stocks are properly maintained for their correctness in terms of quantity and value. These type of inconsistencies cause instability of system in terms of incorrect reporting, false stock statements and incorrect decisions.

This document deals with possible causes of stock inconsistencies and the analysis required for finding the same and taking corrective measures.

Possible Reasons for Stock Inconsistency:

Prolonged usage of inventory management transactions like MIGO, MB1B for stock posting.

Archiving of documents.

Wrong postings with negative stock\

History tables MBEWH, MARDH, MSEG, MKPF not updated properly

Errors during Inventory Transactions:

Whatever may be the reason, system would become inconsistent which may provide error message like any of the following :

M7 308 'Stock value and qty are unrealistic: & / &

M7 309 'Stock value is negative: &

M7 310 'Valuated stock is negative: &

M314 'Valuated stock becomes negative: &

The possible reason is, there exist no actual stock in the system, though MMBE shows some stock. Most of the time this could be the reason for error messages.

Transactions where we can check the stocks:

Various transactions which are used to find stocks in SAP are :

MMBE - Stock Overview Report

MM03 -  Accounting view of material master fetches data from MBEW (table for valuated stock)

MB53 - Plant Stock Availability

MB52 - Warehouse Stock Availability

Possible causes of inconsistency and their solution:

1. Difference between storage location stock and batch stock

Sometimes, the sum of all batch stocks from MCHB table for a particular material differ from storage location stock available from table MARD. This is not applicable to spacial stock like Sales Order stock or Project Stock.

The possible reason for this inconsistency could be when you use a modification for batch number assignment. One batch is assigned several times (e.g. use of a dummy batch number or the actual date)

Solution:

Check your modification in batch number assignment, in particular in Function Module VB_NEXT_BATCH_NUMBER.

A second option to find whether the inconsistency is a result of such a modification is to call transaction MSC3N for the relevant batch and display the change documents. If there there several change documents with the content "Batch created", this usually hints to a modification in batch number assignment.

To avoid further inconsistencies, delete your modifications. Implement Notes 1035372 and 1062164 and set the parameter ALLOW_EXISTING_BATCH in the existing user exit EXIT_SAPLV01Z_002 to make postings to the existing batch. If the system now issues the error message M3 204 'Batch & already exissts in plant &' or M# 556 'Batch & already exists for material &' , you must repopulate the batch number in the user exit EXIT_SAPMM07M_010.

2. Wrong Goods Receipt

In your system, there is a GR for PO, in which an item in the material document contains the material number of the previous purchase order item.

3. A material has inconsistent data

The stock in Accounting View (Table MBEW) does not correspond to the stock in the Stock Overview. You have own programs which cary out an update on MBEW.

Cause and Prerequisites:

Table MBEW contains valuation data of material , for example the total stock and total value.  These fields are updated with every goods movement. With these frequent changes in the table, each updatem which doesnot lock the table correctly, can cause data inconsistency.

Solution:

Do not use your own programs to change fields LBKUM, SALK3, SALKV, VKSAL, STPRS, VERPR, VPRSV of table MBEW.

If you use own programs which changes other fields of table MBEW, always use the addition SET. Thus, on the database only, fields specified with command SET are changed. Stock postings which may be carried out at the same time remains unaffected.

4. Non-generation of Accounting Document in MIGO

When Goods Movement is posted, a material document is generated. However, no update on the dependent stock tables, such as MARD and MBEW are carried out. In addition, no accounting document gets generated.

Causes and Prerequisites

Following procedure causes incorrect update.

i. You post goods movement with transaction MB11 or MB1A

ii. You enter movement type, plant and storage location in initial screen and choose Enter

iii. You enter material number in the following overview screen and confirm your entry by choosing Enter.

iv. Since you did not fill the field quantity, you reach the detail field automatically. Your system generates warning message M7 129 'Enter a quantity'.

v. You display the movable quantity using Key combination Shift + F5, and exit the dialog box (F12).

vi. Enter the entry quantity in the following detail screen and confirm it by choosing Enter.

vii. Then press cancel (F12)

viii. You reach the Overview screen again and post goods movement (F11)

5. Due to Period Closing Issues

In period closing for material master (MMPV), goods movement are done during the interval between Last Day of the Old Period and First Day of the New Period.

It is recommended not to post any documents whilst the period closing programs are running. Before the period closing program runs, check in transaction SM13 whether outstanding update terminations of goods movement are still displayed. These must be cleared and closed before the period closing program runs.

Useful Reports to Analyze Inconsistencies:

RM07SHUP - Shows updates recorded in table mminkon_up.

MBANEKBE - Display of a purchase order history

MBCKBSEG - This report checks Materials having balance in FI with no entry in MBEW, Materials with wrong valuation class in MBEW as a result of which account determination gets different account as in BSEG , Materials which have a different actual value in MBEW as in BSEG, Manual Postings or with posting key not equal to BSX for stock accounts

MBCKBSIM - This report checks whether for all BSEG entries, a BSIM entry exists

MBTRAMEW - This report will try to find inconsistencies caused by Stock Transfer Orders with active ingredient batches. This report also allows posting the correction using transaction MWBE

RM07HIST - routine to read history stock from history tables.

MBUPDATE - This report allows modification of MM-IM table fields. Updated values are stored in table MMINKON_UP

MBLABST - Shows general information and Stocks for a specified material in a specified plant.

MBMSSQCR - Using this report, user may change the content of field MSSQ-KZBWS (special stock valuation indicator) when the special stock is 0.

Conclusion:

Although there are many reasons for stock inconsistencies, some of possible reasons and there solutions have been discussed. Finding out inconsistencies and their corrections will improve the stock management thereby, reducing the inventory costs.

Purpose:

The aim of this document is to provide an understanding of the Freight cost capture on KG basis with reference to Inbound Delivery / Advance Shipping Notification.

Process:

Material Master Settings:(Tcode - MM02)

The Gross weight has to be maintained at Basic Data 1 in material master along with weight unit, here the gross weight 30 KG taken for example.

Creation of Purchase Order: (Tcode - ME21N)

Purchase Order has to be created with Confirmation Control Key 0004 Inbound Delivery, here 100 KG taken for example.

Creation of Inbound Delivery / Advance Shipping Notification: (Tcode - VL31N)

Complete Purchase Order quantity taken for IBD and the total weight has been calculated based on Material Master and Delivery (30 KG X 100 KG = 3000 KG).

Creation of Condition Record: (Tcode - TK11)

Go to the transaction TK11 and pass the condition type FB00 for Weight basis, here the key combination take for Transporter, Shipment Type and Shipment Route. Here Rs.55 taken per KG for Route 1, Rs.60 for Route 2 and Rs.30 for Route 3 respectively.

Creation of Shipment: (Tcode - VT01N)

Use the shipment type 0010 Inbound Shipment with corresponding Transport Planning Point for Shipment Creation, pass the required Inbound Delivery number and execute.

Pass the Transporter name along with Shipment route and Type, system will calculate the freight cost automatically based on condition record.

Here Gross quantity is 3000 KG and net Value is 165000 (3000 X 55).

Creation of Shipment Cost: (Tcode – VI01)

Create shipment cost document with reference to shipment number.

Change Shipment Cost: (Tcode – VI02)

Pass the shipment cost number and tick Transfer check box for auto Purchase order creation.

Service Purchase Order has been created in background and you can see the Material Document Number and Service Entry Number in Purchase order history. 

Configuration:

OLML – Shipping - Basic Shipping Functions – Routes - Define Routes - Define Modes of Transport

We have to assign this mode of transport into shipping type and we can define the same as per business requirement, also it will be easy to monitor whether the material transfer by Road or Air.

OLML – Shipping - Basic Shipping Functions – Routes - Define Routes - Define Shipping Types.

We are using this Shipping Type is on of our key combination and we can set different prices based on shipping type through condition record.

OLML – Shipping - Basic Shipping Functions – Routes - Define Routes - Define Routes and Stages.

We can define the route and stages based on the distance where the vendor located and the transportation price will be differ based on the distance, we are using the route also on of our Key Combination in condition record.

OLML – Transportation – Shipments - Define Number Ranges for Shipments.

Set up new number ranges for Shipment document.

OLML – Transportation – Shipments - Shipments - Maintain Transportation Relevance - Maintain transportation relevance for delivery types.

Kindly activate the below check box then only the we can use delivery type "EL" for transportation process.

OLML – Transportation – Shipments - Maintain Transportation Relevance - Maintain transportation relevance for delivery item types.

Kindly activate the relevant Item category for the delivery type "EL" for transportation process.

OLML – Transportation – Shipments - Define Number Ranges for Shipments - Maintain Transportation Relevance - Maintain transportation relevance for routes.

The activation has to be done for relevant route then only the route can be used for shipment.

OLML – Transportation – Shipments - Define Shipment Types.

Shipment Type having various control for transportation process like Output determination procedure, number ranges etc... Below proposal screen we are using the weight unit is "KG" since we are calculating the transportation cost on KG basis.

OLML – Transportation – Shipments - Configuration of Transportation Processing for Forwarding Agents.

This configuration mainly using to identify the service agent who are involving into freight forwarding process, we are using this forward agent also on of our key combination in condition record.

In second screen you can come to know the assignment process of Transportation planning point with shipment type, when ever we use the transportation planning "CH" system will consider the shipment type "0010 Inbound shipment".

Shipment Cost:

OLML – Transportation - Shipment Costs - Shipment Cost Document - Define Number Ranges for Shipment Costs.

Here we can define own number ranges for shipment costs, when creating a shipment cost document, a unique number is generated as per this configuration.

OLML – Transportation - Shipment Costs - Shipment Cost Document - Shipment Cost Types and Item Categories.

Here we can define the shipment cost types and item categories that contain all important control features for the shipment cost document and also we can assign the valuation class makes it possible to post the values of services of the same service category to different accounts.

OLML – Transportation - Shipment Costs - Shipment Cost Document - Shipment Cost Relevance and Default for Shipment Cost Type.

Here we can assign the shipment cost types to the shipment types and set an indicator to show whether the cost type is relevant to shipment costing, this setting has to be done for every cost type in every shipment type.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define Price Dependencies (Condition Tables)

A table where the key fields are data combinations for which messages are triggered and there is a condition record for each data combination, here we craeted table by using the Service Agent, Shipment type and Route as a key combination.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define Condition Types.

Since we are looking this process to calculate transportation cost for Weight basis, here we have taken standard Condition type FB00 is using for Gross weight.

In second screen you can see the calculation base "A- Delivery" if it is A then the total weight will be consider from delivery header level.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define Access Sequences.

As you aware an access sequence is a search strategy which uses to search for condition records valid for a condition type, here we have taken MAKT and the table assign to the same.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define And Assign Pricing Procedures - Maintain pricing procedure.

We can set the pricing procedure as per the requirement by using above condition type.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define And Assign Pricing Procedures - Define pricing procedure determination for shipment costs.

All the shipment is allocated to a transportation planning point for transportation planning. It helps to determine responsibility for transportation processing during which it can be used as a selection criterion, in order to create a list of shipments to be processed, say for example one planing point can be used for Road and another for Air like wise.

Finally all Item determination procedure group, service agent procedure group and shipping type procedure group which has been done above configuration need to be assign with Pricing procedure. 

OLML – Transportation - Shipment Costs – Settlement - Assign Purchasing Data.

Finally we need to assign the Transportation planning point with shipment cost type, purchase organisation, purchasing group and plant for auto purchase order creation. 

Introduction

The below article is a short description on Flow of Data between

SAP Material Management (MM) and SAP Supplier Self Service (SUS) and some customizable features of SAP SUS.

In the Plan-Driven Procurement with Supplier Integration scenario the SAP SUS is installed and configured with SAP MM/SRM. Technically, in a classic scenario SAP SUS maybe connected with one or more MM and/or SRM back-end systems.

PO is sent to SAP SUS system, in which supplier can perform the follow-on procurement process, i.e. PO response, ASN, GR response and invoice response.

SAP Supplier Self-Services provides the following processes and functions:

• Vendor Maintenance in SAP Supplier Self-Services
• User Management
• Processing Purchase Orders
• Processing Confirmations
• Processing Shipping Notifications
• Processing Invoices
• Processing ERS Invoices
• Bid Invitations
• Analyses
• Integration of Internet Pricing and Configurator (IPC)

Two scenarios for SAP SUS:  SRM-XI-SUS and MM-XI-SUS.

In SRM-XI-SUS the PO is created in an SRM system locally and sent to SAP SUS. All communication will take place between these two systems via XML messages on both sides with a PI/XI system in between as a mandatory system.

In the MM-XI-SUS scenario the PO will be created in ECC and transferred to SAP SUS. Depending on ECC release there are two different possibilities for this, either the ECC system sends IDOCs or sends XML messages directly. IDOCs will be mapped to XML by PI/XI in all cases, as the SAP SUS system only receives and sends XML messages.

Below is the detailed description on SAP MM ECC sending PO as an IDOC to SUS.

SAP MM ECC sending PO as an IDOC to SUS

SRMSUS BSP Application

SRM SUS Portal or the Vendor Portal is a BSP Application.

The standard BSP application name is SRMSUS, which contains all the standard views provided by SAP.

This BSP Application can be viewed in the Object Navigator (SE80) of the SRM SUS system.

For implementing a customized SRM SUS Portal, this BSP Application is copied and enhanced.

The views are modified as per requirements in the Model View Controller. 

The view changes in ABAP code are done in these controllers.

To understand the flow of data from SAP MM to SAP SUS we shall follow the below mentioned steps:

Sending PO to SAP SUS

Configuring Message Output type

• Create a custom output type for PO to be transferred to SRM SUS.
• Steps to configure output control messages:

1. Condition Table

SPRO/ Material Management/Purchasing/Message/ Output Control/Condition Tables/Define Condition Table for Purchase Order

Select: Purchasing Doc. Type, Purchasing Organization, Vendor

2. Access Sequences

SPRO/ Material Management/Purchasing/ Message/Output Control/Access Sequences/Define Condition Table for Purchase Order

3. Message Type

SPRO /Material Management/ Purchasing/ Message/ Output Control/Message Types/Define Message Type for Purchase Order {NEU}

4. Message Determination Schemas

     4.1. Message Determination Schemas

SPRO/ Material Management/Purchasing/ Message/ Output Control/Message Schema/Define Message Schema for Purchase Order/ Maintain Message Determination Schema

     4.2. Assign Schema to Purchase Order

SPRO/ Material Management/Purchasing/Message/Output Control/Message ne Message Schema for Purchase Order/Assign Schema to Purchase Order

5. Partner Roles per Message Type

SPRO/Material Management/Purchasing/ Message /Output Control/Partner Roles per Message Type/Define Partner Role for Purchase Order

6. Condition Record

SAP Menu/Logistics/Material Management/Purchasing/Master data/Messages/Purchase Order/ MN04 (Create using medium EID Electronic Data Interchange '6')

Significance of Message Output Type

In the created EDI (Electronic Data Interchange) output type of the purchase order, the processing routine contains the program RSNASTED which is responsible for sending the document to the Partner as an IDOC.

The Program RSNASTED is the processing program for each output type, which depending on the definitions for the output mode maintained in the EDI partner profile, will generate and write only one Intermediate Document to a file.

RSNASTED processes entries in the NAST table, which stores an entry for each output record created from application document.

For the created PO, the IDOC created can be checked in IDOC List (WE02).

In case of issues in document transfer, this is the first place to be checked. Green status indicates successful transfer of data from the ECC system.

Creating PO in MM

• Purchase Order is created in SAP MM system and released.
• This is for the professional buying scenario. PO can also be created automatically with reference to shopping carts in the system.

• Assign the created Message Output type with the target system as Partner.
• It is crucial that the created EDI output message is assigned as it is responsible for transferring the PO details to the SUS system.

• Once the PO has been released, this output message type triggers the IDoc which takes the PO details to the SUS system.

SUS Portal

The vendor logs onto the SUS Portal using the User Id provided to them, to check the PO, GR, Invoice notifications, to create ASN, Invoice uploading and to see Payment details.

• New PO notification in Supplier portal

As soon as the PO is created against a Vendor in the ECC system and assigned the EID Output message type, the PO details should be available to the Vendor on his SUS Portal.

The PO details are sent as an outbound IDoc from the ECC system onto the XI/PI system.

In the XI/PI system, this IDoc is mapped into an xml file and sent to the SUS system. Thus, the PO details are visible to the Vendor in his SUS portal id.

• List of POs in SUS Portal

The Vendor will be able to see all the Purchase Orders made against him by the organization in this menu.

Here he can individually go and accept and view details of each of the purchase orders.

Current PO Status displays if it is a new PO or an already accepted/confirmed PO.

• Accepting a PO in Supplier Portal

New POs are to be accepted by the Vendor, confirming that the terms of the PO document are acceptable.

As seen in the screen shot below the Vendor is able to see the PO number, date, company code, Company name and Terms of Payment in the General information layer.

The item code, details, quantity, rate, gross value and delivery date are visible in the item Overview tab.

The fields in these tabs are customizable and the layout is modified as per business requirement.

After accepting the PO the Vendor can then view and update the progress with respect to this PO from the menu screen.

The acceptance of PO by the Vendor can be sent as a PO response to the ECC system via XI/PI.

This is reflected in the PO Confirmations tab in Item detail in ECC.

Advanced Shipping Notice in Supplier Portal

• Creating an ASN in Supplier Portal

Advanced Shipping Notification (ASN) is a notification that is sent by the vendor to the organization when the goods are dispatched.

It generally includes information about the means of transport of the goods and document reference against which it is created.

      Here is an ASN screen in the SUS portal.

    ASN is sent from the SUS to ECC system via the XI/PI system.

• The ASN no. should be displayed in PO conformation control as displayed below.

GR can be done in the system with reference to an ASN.

ASN should also be visible in transaction VL33N.

• Document Flow in Supplier Portal.

Sending GR to SAP SUS

• Goods Receipt is created against the PO in SAP MM

Once the goods are physically received at the storage location, Goods Reciept is done. The details of the GR are required for the vendor to get a confirmation of delivery.

• This Goods Receipt is reflected in SRM SUS Portal

Similar to PO, the GR details are visible

Program that sends GR to SAP SUS

RPODDELVRY is the program that sends the GR document to SRM SUS as an IDOC.

This report allows a synchronization of goods movements for PO and scheduling agreements. It selects all GRs corresponding to POs for vendors in SAP SRM SUS according to the selected vendor classes, including associated cancelations and return deliveries that have not been synchronized with SRM SUS.

The selected goods movements are transferred to the respective target system in SRM SUS using STPPOD.Delvry03-IDocs.
If you start the report as a background job, information can be written to a spool while the report is running.
You can only use this report if the summarization function of the PO history records is not active.
Note that this report is not suitable for the processing of mass movements. The report is suitable for periodic background processing. The system ensures that only one instance of the report is active in the background. The report is not designed to be carried out via batch input.
Synchronization is only possible when table EKBE (procurement document history) is NOT summarized. Batch input synchronization is not possible.

Customizations

Apart from these standard functionalities, Invoice uploading and Payment details can also be added.

Custom BSP pages need to be created for these in the invoice module, which is done in the controller view mentioned earlier.

Supplier can upload scanned copies of the physical invoice in the Invoice screen.

The Payment details of the payment made can be viewed in the Payment details screen.

Uploading Invoice to SAP SUS

The following is a customization, to illustrate the additional uses of the SUS system.

The Vendor can upload the invoice as a scanned copy on the SUS portal, against the PO raised to him. The Invoice amount and date is also entered and submitted as shown below.

Vendor also has the option to upload supporting documents.

Preview of the Invoice uploaded.The Invoice details have to be entered manually at the SAP ECC system in transaction MIRO. The uploaded Invoice is matched against MIGO for invoice verification.

View Payment Details from ECC

The payment details come to SUS sytem from ECC via RFC.

The vendor is able to view the payments made against an invoice raised by him.

The Vendor can view Payments made to him in the SUS portal as shown below.

There can be multiple payments made to the Vendor against the same invoice or have a single payment. This is based on the payment terms maintained against the vendor.

Hope you found this article informative. Please provide your inputs on the same.

Thank you for your time.

I have seen lot of queries regarding automatic stock transport orders generation with reference to stock transport requisitions. I have searched in SCN to find the related document. I am unable to find any document related to Automatic STO creation from STR. I was find the documents related to automatic PO generation but not STO's.

Introduction : Now a days Clients are looking more into Stock transfer from one plant another plant. Stock transport process is commonly used in most of the clients. There are many reasons why client looking into STO process 

1) Sales Order received in Depot plant or branch and manufacturing the goods happens in other plant.

2) Collecting the raw materials or FM CG goods components or packing materials in one plant and transferring to manufacturing plant.

3) Semi finished goods will be prepared at one plant and packing will be happens in another plant.

4) Collecting the perishable materials transferring to other cold storage plants.

Like there are business processes in different industries. Some times Requisitions will be generated through MRP and some times Requisitions created Manually. Some times,there was huge time will take to do huge  materials and some times it is to difficult to search supply plant and receiving plant wise to do STO's.

To avoid this, in SAP we have option to create Automatic STO's with reference to Stock transport requisitions.

Prerequisites :

1) Change default document type from NB to STO Document type in following path.

OLME--> Define default values for document type.

Here need to change default document type (sto document type) for ME21 and ME21N.

2) Configuration should properly maintain for set up STO in following path

OLME---> Purchase order --> set up STO. 

And you have to maintain assign document type, one step procedure, under delivery tolerance.

It is not required to maintain one step procedure. But you need to maintain supply plant and receiving plant with document type.

3) In Material Master, need to maintain automatic PO check in Purchasing view.

4) Source list need to maintain with combination of receiving plant and material and valid period and supply plant (Procurement plant)  and purchase organization.

5) Link should be maintain PR ( in case MRP generated - default document type) document type to PO document type in below path.

OLME--> Purchase order ---> Define document type.

Process :

Once generated the Stock Transport Requisitions ,

In ME59N, enter Purchase requisitions numbers and execute the transactions.

Based on supplying plant, system will generate the STO's.

See Below link , posted by Karoly Taragyia

Explained Trouble shooting on ME59N

ME59N trouble-shooting guide - ERP SCM - SCN Wiki

Sometimes we get these error message numbers: M3 022 - The group data for the material & is locked by &, M3 023 - Plant data is locked by the user &, M3 024- Valuation data for material & is locked by the user &,M3 897 -The plant data of the material & is locked by the user &. That does mean some other user is currently working on the same material. you can't make these messages as warning or you can't switch off these messages from customization. Lets explain how system works internally as the result of these messages externally and how to control these messages.

Exclusive Lock:

Exclusive block is quite like immediate block. When you use a material master during a goods movement transaction, then system will block the particular material master for any other goods movement transaction until you post or leave the current transaction. That means you only can able to post other movement or change master data if the material is not used in any other goods movement transaction. In that case, only one user can post a goods movement, another user can't use the material master for any goods movement transaction. It is used to post the all goods movement correctly, so that the valuation data are updated correctly in the material master and there are no inconsistent during update the quantity and value. But here is a disadvantage : Only one user can post a goods movement transaction at a time, hence this can be a big issue for these types of organizations where a huge of goods movements are posted per day.

In that case, system will issue these above messages as error.

Late Lock:

Late block does mean system will not block immediately or exclusively the material master when another user is using a goods movement transaction for the same material. It will try to block exclusively only when you will go to save the data, so that this material will be blocked for a certain point of time (short time). You need to enter a waiting time to use the late block (by default system will take 10) and it will be as second. Waiting time is a certain number of locking attempts which will created by system before the goods movement posted. It tries to lock the material master data before the posting goods movement, so that all posting would be consistent (correct). If any other user use a goods movement for the material master, then system will wait for a certain time and then again tries to set the block.

Shared Lock :

Shared lock does mean to share the locking activity between goods movement and material master. Suppose, an user is processing a goods movement transaction, then you can able to change the material master data without valuation related and inventory management related data (such as material price, valuation category, unit of measure, indicator for batch determination etc). If you go for change a material master and you have done some changes and before pressing save another user has posted a goods movement in the meantime, then system will refuse your entry and system will through a message "MM 628 - The field cannot be changed at the moment due to a goods movement", and you need to leave the transaction and do it again. If another user is posting a goods movement transaction and during the time you are trying to change some data related to the valuation or inventory management, then system will issue the message "M3 024 - Valuation data for material & is locked by the user &". But you can still able to save the changes of other data (like as material description, material group, division, tick option of automatic PO, source list. Anything not related to valuation or inventory management). The only disadvantage of the share lock, you can't change these fields whose are related to valuation and inventory management level.

Shared lock will work when you are using the late lock. System will refuse the share lock if you set the the locking activity as "Lock Exclusively" in customization.

Customization :

There are two customizations to use these above facilities. In one customization, you have to set the locking activity as either "Lock Exclusively" or "Late Lock", and in other customization you need to set the "Shared Lock".

In the IMG path SPRO - IMG - Materials Management - General Settings for Materials Management - Set material block for goods movements , you can set the locking activity for goods movement transaction or you can use the t-code OMJI. Here you can choose your desire option:

(Note: You may can see different screen for IMG path and transaction OMJI, but these both are same)

To use the shared lock function, you need to go to the IMG path SPRO- IMG - Logistics-General - Material Master - Basic Settings - Make Global Settings or you can use t-code OMT0. Here you can set the indicator as per your desire requirement :

Material block during Invoice posting :

You can also block material master record during invoice verification, you can use 3 methods for this blocking activity:

1. All materials will be blocked during invoice posting (Material is blocked at first read) :

In this activity, if you will choose a purchasing document for invoice posting with regards to some materials, then these materials will be blocked for any changes related to valuation data level.

Suppose, you are processing an invoice which contains a material, then this material will be blocked for valuation data level. You will receive an error message "M3 024 - Valuation data for material & is locked by the user &".

2. Particular material blocked during invoice posting (Material is blocked when invoice is simulated/posted) :

In this activity, only these materials will be blocked whose stocks to be updated (for the reason of any variance of GR value and invoice value).

Suppose, you are processing an invoice which contains a material, and during simulation, there are some value goes to the material account (inventory account), then system will block the material at valuation data level. System will issue the message "M3 024 - Valuation data for material & is locked by the user &".

3. Material block during direct posting :

In this case, when you will use the tab material in MIRO during posting the invoice, then system will block the material at valuation level immediately.

If you are using the invoice and goods movement transaction parallel, then you should choose the option "Material is blocked when invoice is simulated/posted".

Configuration can be controlled by the path SPRO - IMG - Materials Management - General Settings for Materials Management - Set Up Material Block for Invoice Verification :

Select you desire option from these 3 methods.

Reference help documents:

Late Exclusive Material Block (Enqueue) for Goods - Release notes for release 3.0D - SAP Library

Material Block (Material Enqueue) for Goods Movements - Inventory Management and Physical Inventory (MM-IM) - SAP Librar…

SAP Notes:

322989 - Late block: Number of blocking attempts

1166612 - Locking error for material during parallel goods movements

1985306 - Performance guide for goods movements

1766569 - VL02N locking issue: M3024 raised

KBA

1744780 - Error message M3024 during Invoice Verification process

Business Scenario:

We execute the report MB5B to check stock as on posting date along with we can check the stock analysis from the same transaction code. We choose the tick option of “Totals Only” to see the sum of these columns ‘Opening Stock, Total Receipt Quantities, Total Issue Quantities, Closing Stock. If we don’t select the totals only, then we can able to see all movement type’s line items with regards to our selection criteria. Here we can see all movement types which is related to all modules (MM SD QM etc.). To see line items for some specific movement type (e.g. how many quantity has posted with regards to the movement type 101,105,109 etc.), you need to choose the filter option. But with the help of movement type group, you can see selected line items by choosing the movement type group and you can see only these line items which have been grouped under the selected movement type group.

Suppose, you need to find line items for these movement types which are causes of goods issue. We know these movement types (suppose 201, 221, 333, 551 etc.) are used for goods issue. It may be able to achieve this by filtering these movement types from MB51 or MB5B. SAP has given the facility of movement type group, so that you do not have to choose the movement type manually, You just need to assign the movement type to movement type group, then you can able to see all line items with regards to movement type.

Assignment:

It’s a very simple configuration that you need to do in IMG activity. You just need to assign the movement type to movement type group in this IMG path SPRO - IMG - Materials Management - Inventory Management and Physical Inventory - Reporting - Group Movement Types for Stock Lists.

Here, choose your movement type and assign the movement type group as per your requirement. Movement type group is a free text field; you can enter any text in this field (as quite same like as account modifier for movement type). Do it for these movement types which you want to see in MB5B stock analysis report when you will choose the movement type group. You can also select your custom movement type (as per your business requirement). System read the table T156S for the movement type. You can’t able to create any entry here. All movement types are created from OMJJ transaction will be updated here with blank movement type group automatically.

(Note: You will be able to see a warning message as “Do not make any changes (SAP entry)”. Read the message carefully and do that accordingly which is explained in the procedure section.)

Result:

Run the report MB5B without choosing the option ‘Totals only’. You can see all line items for all movement types. Now choose the movement type group from the screen layout as below:

Here, the field name will be ‘Group f. Stock Anal.’ (As you can see the above screen shot)

Then you can see the field movement type group in the output list. Also here you can see a default value as ‘REST’ for those entries which haven’t assigned to any movement type group. That means if you will not assign any movement type group with regards to movement type in IMG, then you can see the value ‘REST’ for these line items in this output list. It is designed by system.

Now you can see your selected movement type’s line items by sorting or filtering the movement type group. Just filter the tab movement type group as per your assigned group.

Conclusion:

This is just an extra facility from SAP to check the stock analysis and it is only used for reporting purpose at the section inventory management. You can’t use this movement type group in selection screens. You can’t use this facility in MB51 transaction; it is only applicable for MB5B stock analysis transaction. You can keep the output layout by saving the adjusted layout, if you want to see the same later. The assigned value of movement type group is stored in table T156Q as per movement type. You can also select special stock wise movement type during the assignment of movement type group. You should not select specific movement type in MB5B in selection field as because of incorrect result. If you will select any specific movement type in MB5B, then system will through a warning message “If there are restrictions acc. to movement type, results may be incorrect”. So you need to run the report without selecting movement type and then use the movement type group to see the stock analysis with regards to your required movement type.

SAP help document : Group Movement Types for Stock Lists

This document consists of configuration steps and an example which is related with  'define mail to purchasing when price variances occur'. For me , it is an beneficial implementation to control LIV price differences. The root of reason can be quantity variances and price variances. Also , MM experts have to configure setting of tolerances for incoming invoices. It is a related document in incoming invoices --> http://scn.sap.com/docs/DOC-50915

Related oss notes :

301803 - MRM1: Mail to purchasing MLPP variable replacement

554029 - FAQ: SAPoffice - Forwarding/mail system group

552616 - FAQ: SAPoffice - Sending to external recipients

  MM Configuration Steps :

  Spro->MM->LIV->Incoming invoice->Define mail to purchasing when price variances occur

   This configuration step provides aoutomatically sending mail between purchasing&accounting departments.

   Activate based on company code :

   Procedures / Access sequences

   MR0002 procedure for MR1M Logistics invoice verification.

   What is the requirement 180 ?

   I explain this like belowed :

   Kobev is precondition. It is a control based on header level. In LV61B180 show that structure kompbmr has MLPP , result is successful.

  Kobed is This is a control on item level and it finally determines whether condition type or access is taken into account. This ABAP form has successful      everytime so sy-subrc = 0

   For more detail :

   Oss note : 156230 - Requirements: What is permitted, what is not?

   Output Types and Mail Concept :

   You can fill mail body in this step , you will get an example.

   You can use RBKP and RSEG table to create e-mail details. You can see an example in belowed.

   Partner : ME (Buyer) , Transmission Medium -> Simple Mail

   Condition record :

   You have to create condition records based on Company Code, Function Partner.

   Communication details :

   You have to create a dummy receipent.

   External mail tips :

   How can i redirect to mail to my e-mail address ?

  'Send to Home Addresses of Users' (transaction SO16, register 'Mail sy.grp'). If you use this option SAP Office will redirect the mail to the e-mail address     maintained in the user settings. As a precondition to use this kind of automatic transfer you also have to maintain the standard communication method in the   user settings (INT E-Mail).

   How can i get 'Confirmation of receipt' with e-mail ?

   SCOT tcode will be beneficial follow this path --> Settings / Confirmation of Receipt

   Finally , buyer and someonelse can get this e-mail.

   Best regards.

   M.Ozgur Unal

Business Scenario

Sometimes we need to give freight charges or discount to a particular vendor or a range of vendors. But as we know vendor send us bill with freight charges or discount charges, sometimes user forgot to enter the freight charges for these particular vendors. And after GR, it will create problem for invoice to giving freight charges.

Here, we can do some configurations, where we can set freight charges mandatory for some particular vendor or a range of vendors..

So system will not accept when user will try to create PO without freight charges.

Configuration steps

It's something related to pricing procedure settings.

For pricing procedure settings, you can look up to this blog Pricing procedure Steps and Details in SAP MM

Here you can learn all things about pricing procedure configuration steps and details.

For this document to make freight condition mandatory for particular vendor, we need to set some configurations as same like as to this pricing procedure document.

Step 1 : Define Condition Type

Here we have to do some changes to existing freight condition type (If you want to use customized condition type, then you can create and use here via this doc .

We have to set limit for this freight condition type, we have to set the limit 0.01 as lower, so user has to enter amount for this condition type in PO..

Go to path OLME-Conditions-Define Price Determination Process-Define Limits

Click on New Entries and enter the all details.

Enter the freight condition type, calculation type, currency and lower limit. Then press enter.

You can see the upper limit will automatically comes as 999,999,999.99.

Then save your entry.

Step 2 : Define Calculation Schema

In this step, we need to create a new calculation schema. We need to create new one just copy from existing one (which is used in regular case)

Go to OLME-Conditions-Define Price Determination Process-Define Calculation Schema

Just select the existing calculation schema (which is used for regular PO) and press Copy as..

Then just tick the these two options Manual and Required for the freight condition.

Rest of these two ticks, everything will be same as previous calculation schema.

Then save you entry.

Now you have two Calculation schemas.

One for regular vendors, you can enter freight charges or you can continue without enter freight charges.

Other one is for these vendors, here you have to enter freight charges, you can't continue without enter freight charges.

Step 3 : Define Schema Group for Vendor

Now we have to differentiate these vendor via schema group for vendor.

We have the existing schema group for regular vendor, which has the existing pricing procedure.

Now we have to create a new schema group.. Create a new schema group (t-code OMFN) and assign to these particular vendor (which you want to make the freight charges mandatory)(t-code XK02). I think I don't need to explain these steps for the above, because these steps are well explained in this document (step 5 and 8).

Change the existing schema group to new one for these vendors, which you want to make the freight condition mandatory.

You can use mass maintenance to change the Schema Grp Vndr, use table and field LFM1-KALSK.

Step 4 : Maintain Schema Determination

Here we have to assign the new calculation schema to the new schema group.. Well for the steps and details please see the document (step 7).

Here maintain like that, use same schema group for purchase organization, use different schema group for vendor and use different calculation schema for pricing procedure.

Save your entry.

Now our all settings are completed.. Now we are going to test the scenario.

Try to create PO for these vendors, whose freight charges will be mandatory.

Go to ME21N, enter the all details, you will see an error message :

Here system asking for the freight condition. You must have to enter manually the freight condition type.

Now try to enter the freight condition type in item condition tab.

Don't forget to enter amount. If you do not enter amount, system will shows the above error message.. So you have to enter the condition amount. Without entering condition and condition amount, you can't continue PO creation.. You have to enter the condition and condition amount. It will effect for these vendor which is under this calculation schema, which has the manual and required tick in calculation schema settings.

Now try to create PO for regular vendor.

Go to ME21N, enter the all details

Here you can well continue without enter the freight charges and it's for regular vendor for whom you don't want to enter the freight charges.

Sometimes business need to maintain the freight condition type in header condition. So we have to maintain the condition type in header condition. Set up the all settings for condition type (as above). The at the time of PO creation, when you will see the error "Please enter required condition". Then enter the condition type and amount in header condition manually.

But after entering the condition type in header level, your error will not get resolved. You can still see the error.

At that time you have to do one trick, that is, you have to enter the same condition type manually in item level once and you have to delete it immediately. Enter the condition type and amount at item level manually :

Then the error will be gone and you can able to see the condition type is appearing two time at item condition tab. Then, just select one condition type (which is in editable mode) and press delete.

Then save your PO and if you want to change the freight amount later, then you can change it manually from ME22N in header condition.

In this way you can set up the freight charges or any types of discount charges mandatory for a particular vendor or a particular vendor range..

Simple configurations, if you read and very much clear about the Pricing procedure Steps and Details, then it will take 15-20 min to do the configuration and test this document.

Some useful notes :

1021082 - Conditions for limit items in local PO.

449218 - ME21N error 06 209 even though condition exists

424478 - ME21N: Create consignment PO. Error with conditions.

KBA:

1995226 - Condition upper/lower limit not checked at PO item overview (VK 035 / VK 036 message)

This document consists of authorization problem in MM01/02/03 (Material master) for material types.

I add material authorization group (BEGRU field) to T134 table  so you can implement authorization for different material types in material masters.

I hope that it can be helpful...

Related Oss Notes :

545380 - FAQ: Authorizations material master

303483 - Authorization check enhancement

Related Authorization Objects :

M_MATE_MAR , M_MATE_MAN , M_MATE_MAT , M_MATE_STA , M_MATE_WGR

For example , i implement authorization for HAWA material type creation.

  -->  Go to SE54 tcode and create authorization group

  -->  Assign authorization group ---> determine work area  ---> Table name T134 , Authorization group HAWA

--> New entries .

--> Go to HAWA material type configurations and define authorization group...

-->  You can see T134 details with SE16 , BEGRU-HAWA

**Solution -- SU01 - Roles/ Authorizations / Add - M_MATE_MAR - Authorization Group HAWA and generate.

**Result: You can manage your authorizations in MM01/02/03 with material types.

     I hope that it can be beneficial for someone.

     Regards.

     M.Ozgur Unal

These days, I read documents related with M8 system messages , tolerances , invoice reduction etc.

In this document , i work on implementation and configuration SAP MM Logistic Invoice Verification. My example contains a example which it prevents different postings based on quantity and amount. We will get a problem that i want to post bigger amount, sap will not give permission with error messages finally invoice reduction will solve our this problem.

You can get details : MM-IV-LIV-CRE Set Tolerances for Incoming Invoice - ERP SCM - SCN Wiki

Related Oss notes&KBA :

1372102 - IMG documentation: Set Tolerance Limits

786810 - MM IV: Tolerance check when you enter invoices

313190 - MR1M: Tolerance groups not taken into account

963185 - MM IV: Tolerance check for entering and releasing invoices

791036 - Tolerance check on account assignment item

1674901 - MIRO shows error message M8083 and does not propose amount value when working with Invoicing Plan

608041 - Tolerance checks with service-related invoice verification

1598731 - No payment block if the lower limit is exceeded during invoice posting - MM-IV

2054815 - MR8M: Not able to cancel a credit memo due to tolerance limit error.

134976 - Tolerances for blanket purchase order

396095 - MRBR: Message M8215 for tolerance key 'DW'

610340 - No tolerance check for the credit memo

2004992 - MIRO/MIR7: System will not automatically propose "Amount" and "Quantity" after you have done GR 107.

1880413 - Duplicate Invoice Check functionality does not work

158611 - MR1M: Block of invoices for services

753286 - Moving average price becomes very low

90013 - Tolerance limits not converted to local currency

1890543 - Cannot set message "M8 082" as an error at company code level

1853807 - MIR4: Message M8 084 as error message stops posting

1919689 - MIRO: User tolerances are not taken into account

I have a PO , my person posted a material document 100 qty.

     In Miro , can you post more quantities and amounts ? Is it related your tolerances ? Not at all.

     If posting exceed your tolerances , you can post but it is blocked. If not, you can not prevent. Sometimes , you can not be aware of tolerances when you can post fastly. It is dangerous.

Examples :

1 - Amount is bigger than PO.

2- Quantity and amount are bigger than migo and po values.

     What can i do ?

     Firstly , check your LIV system messages.

     You can update your M8 / 81-82-83 messages with ERROR also if you get them.

     MM/Logistic Invoice Verification/Invoice Block/Set tolerance limits

     * Please check DQ and PP tolerance keys.

     However , it is not enough to prevent posting . You have to maintain your LIV system messages.

     * I configure M8 messages with ERROR.

     * When i post our invoices , sap will not give permission...

     ** Unfortunately , i have to post some like a weigher result , vendor errors invoices with variances , how can i solve this problem ?

     **Sometimes , you can post your invoices with tolerance even though you implement system messages. Invoice reduction can help you.

     *Select layout : Invoice reduction , Correction ID : 2 Vendor error - reduce invoice ,Invoice amount Acc to Vendor , however you can use similiar way for quantities. Sap will create one more fi record for differences.

     Results :

    ** Configurations :

     You have to configure your T030 table with RKA transaction (OBYC tcode) and invoice document types.

     I add RK document type for invoice reduction. (OMR4)

     However, if you want to update some datas to implement in your country like a tax rates ..

     You have to update records with enhancement implementation program LMRMCF07 .

     I hope that it can be benefical for your business life thoughts.

     Thanks a lot for spending times ...

     Regards.

     M.Ozgur Unal

This document consists of configuring the material master. However , an understanding of how to make changes to material master.

You can benefit from related Oss notes :

192798 - Problems copying and deleting logical screens

1088189 - Composite SAP Note for material master

545211 - FAQ: Material master Customizing

580227 - Material master: Subscreen staggered by one column

327936 - Classification subscreen in the material master

32139 - User-specific material master - default setting

41174 - Material Master Customizing

107404 - Missing Text in Material Master Views/Screen Sequences

955032 - Material Master: Additional fields for Service Parts Mgmnt

1038117 - ED: Maintaining new field in matrl master data at CC level

1304710 - Material Master: Add. fields on client level for SPM

1141122 - Material Fields for EWM not change document relevant

I try to explain configuration the material master settings for different users or everyone. When you run MM01 tcode , you will see datas for several departments like a purchasing , accounting , mrp , wm , qm ... If you want to prevent some views , you can configure material master dialog.

Logical screen and subscreen :

Bellowed print - screen have a Subscreen-General Data with screen number 2001 . Also , all of the datas of subscreens built a Logical screen-Basic data 1.

When designing your own logical screens, you can use either your own subscreens or standard sap subscreens.

Refer to Additional Fields on the Material Master ... Thanks to Miroslav Oprsteny

Refer to Enhancing Material Master for adding new fields.. Thanks to Shahanaz Hussain

Use your own screens if you want to have different field groupings , Tools-->Abap workbench-->development-->user interface-->screen painter.

An example for configuring material master :

I want to use the subscreen with Environmentally relevant and DG Indicator Profile fields in Purchasing view in the case of a special material type and only by certain users.

* In the technical information dialog box , screen number 2010 for the program SAPLMGD1 , Note : Users have to use their own programs to insert fields from their tables and their sunscreens for material masters.

* Create a new screen sequence , copy 21 to Z0  , configuration steps :

--> ZO screen sequence created

--> Check data screens

On columns , you can maintain screens :

Screen types :

1 : Main screen such as Basic data , Purchasing , Sales

2 : Secondary screen such as Additional data

Screen container :

Screens for program SAPLMGMM like a 4004 Main screens with 10 subscreens.

Maintenance status :

Special user departments can maintain a MM record of a particular material type.

GUI Status :

GUI status are defined in Menu-->Painter which consists of a menu bar with menus, a standard toolbar, an application toolbar and functions with function key settings.

Title type for selection group:

Type 2: three/four-part title type, for main screens

When transaction title maintain , it is made up  description, screen name, industry sector and material type.

Retail maintain status :

* Change data screen for purchasing related fields in the subscreen 2010.

--> General information : Double click subscreens

* Also ,you can view subscreen and data screen

--> Configurations for adding subscreen to purchasing view , sequence 14 purchasing

--> Replace subscreen 5 with the environment relevant fields

--> Specify for your requirements like a transaction , user , material type , industry sector

--> For example - Specify for material type screen reference : Sarf

--> Go to OMS2 and maintain screen reference of material type

--> You can see Environment related subscreen in Purchasing view of  Sarf material type

Thanks to Selin Unal for her passion

Regards.

M.Ozgur Unal.

Batch Master

Batch Definition

Batch management indicator:

Material Master

• Purchasing View
• Work Scheduling View
• Plant data/stor1. View

SAP Notes:
30656 - Change base unit of measure/batch management requirement
533276 - Setting the batch management requirement

Batchprocess:

Transaction Code: MSC1N/MSC2N/MSC3N  (Table MCH1/MCHA/MCHB)
Check change document: MSC4N
Mass processing: MSC5N

Program:
FUNCTION           VB_CREATE_BATCH
FUNCTION           VB_UPDATE_BATCH
FUNCTION           VB_CHANGE_BATCH

BAPIs:
BAPI_BATCH_CREATE (note 619913, item5)
BAPI_BATCH_SAVE_REPLICA (including classification >=470)

Batch Level

Function module: VB_BATCH_DEFINITION             

Table: TCUCH

FAQ during batch level conversion

Batch Number Assignment

Creating Batch:

• In batch master record maintenance(Batch Management)
• In goods movement(Inventory Management)
• In purchase orders(Purchasing)
• In production/process orders(Production)
• In results recording(Quality Management)

Automatic/Manually: Control in customizing OCHA

Batch number assignment: Internal/External

User-exit:

Automatic: EXIT_SAPLV01Z_001/EXIT_SAPLV01_Z_002

Manual: EXIT_SAPLV01Z_003/EXIT_SAPLV01Z_004, EXIT_SAPLV01Z_013 and EXIT_SAPMM07M_003 (inventory management, only for new batches) can be used to change the master data of a batch.

Common information:

• Since release 470 definition for batch number assignment is transported via table TCUBN
  (before it was part of table TCUCH!)
• Batch numbering without gaps is impossible (for explanation see note 619913, item 6)
• Assign the same batch number for more than one goods receipt:
  Use exit
  EXIT_SAPMM07M_010 (if goods movements are posted)
  Use modification according to note 523589for VB_CREATE_BATCH (relevant e.g. for REM - release >= 470).
  [The modification is replaced by BADI mentioned in note 1035372 - Exception BATCH_EXIST in VB_CREATE_BATCH II]
• Functionmodules:
  VB_NEXT_BATCH_NUMBER (internal batch numbering)
  VB_CHECK_BATCH_NUMBER (external batch numbering)
• Idoc type: BATMAS03
• 1970502 - Error message M3 682 when posting good movements to the same batch in parallel
• 1847487 - The Length of batch number is limited to 10 characters

Related documents:

Align vendor batch number with SAP batch number during Goods Receipt

Batch Classification

Characteristic Types in Batch Classification:

• User-defined characteristics: Characteristics that do not reference table fields
• Object Characteristics: Characteristics that refer to table fields.
• Standard characteristics: These are Batch Management characteristics that are delivered in the SAP standard system. They are reference characteristics from tables MCHA and MCH1. All standard characteristics can be found in F4 help by specifying LOBM_*. You are normally not allowed to make changes to standard characteristics in the characteristic master record.

One batch class per material (note 115581), but batch classification can be assigned to multiple objects (check transaction O1CL)

Accordingto batch level class type is determined (material/client: 023, plant: 022)

Batch classification can be maintained in batch master transactions, and in several applications (goods movements, orders, process messages)

Update standard Features: BMSM

Classifying batch during goods movement: OMJJ

Tables:
Do you know the links among tables in Classification and Variant Configuration?

Classification is called in: VB_CREATE_BATCH and VB_CHANGE_BATCH

Classification FM: CLFM_OBJECT_CLASSIFICATION

User Exits to fill free characteristics:

• EXIT_SAPLV01Z_014(not called in MB* transactions, but in MIGO!)
• EXIT_SAPMM07M_004(called in inventory management transactions and when posting goods movements via MB_CREATE_GOODS_MOVEMENT)

Reports:

• Integrity Check for Batch Classification – BMCC
• RCCLZUOB(checks whether object exists for classification entry in table INOB - e.g. entry for temporary document number)
• RCCLINOBDEL(deletes multiple INOB entries for one object)
• RVBCOR16(checks the customizing of batches concerning classification)

SAP Notes/KBAs:
1427890 - FAQ: Standard characteristics

1797792  - Slow performance when accessing classification data

Related documents:

Batch Class Conversion in SAP

Batch Archive

SARA:

Archiving Object MM_SPSTOCK

Pay attention on the indicator:

‘Only consider batch stock records; batch master record will not be deleted’

Batch Status Management

• Batch status management is activated via transaction OMCT.
• Batch status can be changed in batch master transaction and via usage decision (transaction QA11).
• There are two options to prevent restricted batches from being selected within batch determination:
  - insert characteristic LOBM_ZUSTD in batch class and selection class
  - work with dynamic ATP check (scope of check – OVZ9)
• Functionmodules:
  VB_CHANGE_BATCH_STATUS
  VB_CHANGE_BATCH_STATUS_STOCKS
  VB_BATCH_DEFAULT_STATUS
• Exit:EXIT_SAPLV01D_001 (determine initial status of batch)
• Fields:    TCUCH-KZDZV   T001W-CHAZV (batch level on plant)

Batch Determination

Batch Search Strategy Customizing

Five Scenarios

• Inventory Management
• Production order
• Process order
• Sales and distribution
• Warehouse Management

Five scenarios have similar steps to define the batch search strategy.

Five Steps in OCHA:

1. Define Condition tables : Condition tables are combinations of fields that form the key of the batch search strategy.
2. Define Access Sequences: The order in which the system accesses condition tables during batch determination.
3. Define Strategy Types: The default values used when a strategy record is created.
4. DefineSearch Procedure: The order in which you assign the strategy types is the order in which the system searches for strategy records.
5. Search Procedure allocation and check activation: Allocate the search procedures to the application-specific parameters. Batch determination becomes active as soon as you make the allocation.

Selection Class

Define in CL01/CL02/CL03

With the help of these selection classes, you define according to which criteria, that is, using which characteristics, batches are to be selected

• All characteristics (this applies to standard characteristics as well as to user-defined characteristics) you want to use for selection must also be contained in the batch class. Characteristics LOBM_RLZ and LOBM_LFDAT are an exception; they can be used for selection but not for classification
• To copy the characteristics from client 000 to your logon client, use report RMMCCH01.
• 33396 - Batch determ.: Selection w. remaining life LOBM_RLZ

Sort Rule

Define in CU70/CU71/CU72

With the help of sort rules, you define according to which criteria, that is using which characteristics batches are to be sorted.

• All characteristics (this applies to standard characteristics as well as to user-defined characteristics) you want to use for selection must also be contained in the batch class. Characteristics LOBM_MENGE and LOBM_LGORT are an exception; they can be used for selection but NOTfor classification.
• 1979691 - How to set up FIFO in batch determination

Batch Search Strategy Setup-SD

Transaction Code : VCH1/VCH2/VCH3

Set Up Batch Determination in Sales and Distribution

Batch Search Strategy Setup-PP

Transaction Code: COB1/COB2/COB3

Set Up Batch Determination in Production Planning

When the batch determination should be done in production process.

Batch Search Strategy Setup-MM

Transaction Code: MBC1/MBC2/MBC3

Set Up Batch Determination in Inventory Management

Batch Search Strategy Setup-WM

Transaction Code: LS51/LS52/LS53

Batch determination is used for goods issues and stock transfers in SAP warehouse management systems.

• Batches to be picked are transmitted to warehouse management (batch determination takes place in upstream applications).
• Batches are determined from warehouse management (Batch determination in warehouse management).

Batch Determination Analysis

Function Module VB_BATCH_DETERMINATION

• Trouble Shooting in Batch Determination
• Debugging Point of Batch Determination
• Batch Determination – Debug Tips

User Exit
SAPLV01F

• EXIT_SAPLV01F_001
• EXIT_SAPLV01F_002

BADI
VB_BD_SELECTION

585576 - BAdI preselection of batches in batch determination

Batch Information Cockpit

Basics        

Transaction BMBC functions as single point of entry for batch information and comprises several transactions:

MSC2N, MSC3N, MB56, MMBE, CO09, CL30N, MB5C

Selections

• Note 619912 - FAQ: Batch Information Cockpit

Selection Result

SelectionResults: Batches

Here, the main focus is on the selected batches. The batches are displayed in accordance with the batch definition level.

SelectionResults: Stock

• Here, the main focus is on the stock situation of the selected batches.
• Following stock tables are read:

–MCHB
(free stock, special stock indicator = blank)

–MKOL
(Special stocks from vendor, special stock indicator = k)

–MSKA
(sales order stock, special stock indicator = E)

–MSKU
(special stocks with customer, special stock indicator = V and W)

–MSLB
(special stocks with vendor, special stock indicator = O)

–MSPR
(project stock, special stock indicator Q)

Restrictions

Nmber of batches 50 but only 20 displayed.

• System read all batches of material A, for example 70. User Parameter said maximum 50 batches, so system take the first 50 and send message ‘more then 50 batches found’
• Next step take 50 batches and check if they fit the selection criteria, so for example only 30 batches are displayed customer

In the selection result of the Batch Information Cockpit you can display in all 50 characteristics, but it is limited to 20 for character types, 20 for numeric types and 10 for date and time types.

1701988 - Transaction BMBC - Not all characteristics are displayed in the selection result screen

Old batches are note displayed after upgrade to EHP5, reason is new added field BATCH_TYPE, note 1297566 provide a report to update the old
batches

Main Program: RVBBINCO

BAdI:
BIC_FOLLOW_UP_ACTION
BIC_SELECTION

Batch Derivation

Basic Information

• Batch Derivation is based on batchwhere-usedlist (table CHVW and CHVW_PRE areread).
• Batch Derivation is triggered by certaine vents (transaction DVC8)
• No batch derivation for stock transfers (use exit EXIT_SAPMM07M_004 instead)

Derivation Mode:

• Pull Derivation (1 Receiver, n Sender) 
  The derivation is triggered from a transaction that affects the product. Here, data from various senders can be collected, cumulated, and calculated. Within a derivation according to the pull principle, there can only be one receiver, but there can be several senders (example usage: pick and pack for pharmaceutical products).
  
• Push Derivation (n Receiver, 1 Sender)
  Within a derivation according to the push principle, there can only be one sender and several receivers. This derivation is started from a transaction that affects the component batch. Here, data from a sender batch can be derived onto several receiver batches (Example usage: Filling bulk batches in the Chemicals industry).

Customizing

Derivation events (DVC8)

• Determine at which time a derivation should happen and which rule should be used.
• Static or dynamic derivation
  • Static Derivation: For a static derivation, the attributes determined for the sender batch(es) are transferred to the receiver batch(es).
  • Static derivation is recommended if a batch is newly created or changed and the values in the receiver batch(es) should be filled with the attributes from the sender batch(es).
  • Dynamic derivation: For a dynamic derivation, no attributes are transferred to the receiver batch(es), in other words, the derivation is simulated and the values are merely displayed. The derivation is saved, but the receiver batch(es) are not automatically changed.
  • Dynamic derivation is used when the receiver batch must/should not be changed and the sender values should be used as the basis for a user decision.

Set Up Condition Technique for Derivation (Need to be set for sender and receiver both.)

• Define Condition tables
• Define Access Sequences
• Define Strategy Types
• Define Search Procedures

Derivation activate or not (DVSP)

Batch Derivation Rule

Sender Rule (DVS1)

• Which characteristic values should be used to send
• Pull or Push-Derivation

Receiver Rule (DVR1)

• how many levels of WUL should be read
• what happen if more then 1 value available which rule should be used to find the value

Details:

Set Up Batch Derivation in Production Process

Checking Derivations

Transaction DVMO

• Check and display derivations
• When you perform derivation, the following are logged:

        –Derivation type

        –Derivation event

   –Derivation status

        –Result of the derivation, as well as the sender batches and the data sent

        –Messages that arose during a derivation (for example, error messages when a derivation fails, due to a sender field being non-valuated)

Transaction DVMAN

• Manually derivation for example for testing or reproducing

Related documents:

Batch Derivation in Production

Batch Derivation with BADI Derivation

Batch Derivation Overview with example

Shelf Life Management

Prerequisite

Material Master

View “Plant data/stor. 1”, the “Min.Rem Shelf Life” should be maintained: ŸMARA-MHDRZ

Customizing

• OMJ5 for plant or movement type

T159L-XWMHD (Plant)
T156-KZMHD (Movement Type)

–check only when KZMHD = 1

–KZMHD = 3 for goods issues (system message M7 667 moving to trash)

Functionality for all materials not only batches!

Process

• Expiration date is checked (KZMHD = 1) when goods come into the system .(goods receipts, reversals of goods issues, transfer postings)
• System prompts to enter an expiration date.
• When total shelf life is maintained in material master, system prompts for production date.
• When production/expiration date already exists (only for batches possible), these values are entered as default.
• Customizable system messages (overwriting allowed etc. in transaction OCHS)
• Expiration date stored in batch master
• Production date stored in batch master since release 4.5.
• Expiration date also stored in warehouse management (quants).
• If finer steering is needed (plant or storage location dependent values)
  User-Exit EXIT_SAPLVBMD_001
• Function Module: VB_MAINTAIN_MHD
• BADI: VB_SLED_MANAGEMENT -> called in MM07MMHD
• Notes:
  354914 - Documentation for EXIT_SAPLVBMD_001

        616028 - FAQ: Minimum shelf life processing

Related documents:
Considering  component shelf life in batch determination

Batch Specific UoM

ProductionUnit ofMeasure

Notes

162925 - Documentation for product quantity

362932 - Conversion with proportion/product units

Function module: MURC_MENGENUMRECHNUNG

Postings are done in base unit.

Conversion:Function Module MATERIAL_UNIT_CONVERSION

Related documents:

Batch Specific UoM and Active Ingredient Management

Catch Weight Management

Original Batch

Original Batch

  Creation of Service PO w.r.t a Service PR using BAPI with minimal inputs.

  I have seen many people struggling with the BAPI_PO_CREATE1 in case of replicating service PO.This document is a reference for the same with minimal inputs.

BAPI Used: BAPI_PO_CREATE1

   The table structure that need to be passed are as follows:

The respective POHEADERX & POITEMX structure need to be marked as 'X' against the entries maintained in the POHEADER & POITEM structures.

POSERVICES

POSERVICES Structure can be filled identical to the ML_ESLL table after passing the referenced PR to the ML_ESLL-EBELN field .

The structure looks as follows:

  All the fields shown need to be manually maintained, including quantity,price & short text.

  If there are any other mandatory field in the specified PO document type or otherwise then you need to enter the same as well in the respective POHEADER/POITEM structures.

If the PACKAGE Number & SUB PACKAGE Number are used as per the referenced PR, then the account assignment data & other data is not required to be entered in BAPI.

Otherwise ,the additional structure that need to be filled in case PO is created without PR(or without PR package & using default 0000000001 as package number) are:

1.POACCOUNT

2.POACCOUNTX

3.POSRVACCESSVALUES

In case you are creating a dashboard which converts a PR to PO,then the PR details which need to be filled in the BAPI_PO_CREATE1 can be fetched by BAPI_PR_GETDETAIL. However the service level detail need to be fetched from from ML_ESLL table or use the FM BAPI_REQUISITION_GETDETAIL.

Additional Features of BAPI_PO_CREATE1

1.TEST MODE:This parameter is a test switch. If you activate the switch, the system does not save the document. Activate using “X”.

2.MEMORY_UNCOMPLETE: You can use this parameter to specify whether a faulty or incomplete purchase order is to be put on hold.Activate using “X”.

3.MEMORY_COMPLETE:You can use this parameter to control whether an error-free and complete purchase order is to be put on hold or saved.Activate using “X”.

Purpose of the document: How to print multiple copies of ERS Invoices

Introduction

In standard SAP, you cannot print multiple copies of ERS invoices like other logistics Invoices. So from this document you shall be able to know how multiple copies of ERS invoices are printed in SAP.

1.    Requirements

1.1 STANDARD SAP ERS Process

ERS [Evaluated Receipt Settlement] as the name suggests it is used for settling the amount for Goods Receipts made, without invoice for the same not being received from vendor. So SAP shall automatically generate Vendor Invoices for Goods Receipts made and Amount in Invoice is calculated from Purchase Order and Quantity from Goods Receipt.

Prerequisites:

• In Vendor Master, “AutoevalGRsetm Del” and “AutoevalGRsetm Ret” need to be checked. Thus vendor will become ERS enabled vendor.
• In Purchase Info Record, “No ERS” should not be checked.

Process Flow

When a Goods Receipt is made in SAP, it creates an entry in “ERS”(EKRS) table and as per the input conditions selected by the user, ERS program (RMMR01RS)  determines all the documents satisfying input conditions and allows us to generates the invoice documents as per the selection.

ERS Invoice is generated through TCode MRRL with any of the following input selection criteria.

• Company Code
• Plant
• Posting Date of GR
• Purchase order and PO Item
• Goods Receipt document for GR based IV

SAP Path

1. SPRO ->Materials Management ->Logistic Invoice Verification -> Evaluated Receipt Settlement ->Specify Automatic Settlement of Planned delivery Costs.

We need to maintain company code / Purchase Organization / Freight Vendor is maintained with check so that planned delivery cost maintained in Purchase Order gets settled while running ERS

2)SPRO -> Materials Management -> Logistic Invoice Verification -> Evaluated Receipt Settlement ->ERS Invoice Numbering -> Create Number Group

3) SPRO -> Materials Management -> Logistic Invoice Verification -> Evaluated Receipt Settlement ->ERS Invoice Numbering -> Create ERS Number Range

4)SPRO -> Materials Management -> Logistic Invoice Verification -> Message Determination -> Maintain Message Type

Output Type used for Printing ERS invoice is “ERS” and the same is maintained here

5)TCode: MRRL | | Logistics-> Materials Management -> Logistic Invoice Verification -> Automatic Settlement ->Evaluated Receipt Settlement

1.1FUNCTIONAL REQUIREMENT

In Standard SAP, ERS Invoice can be printed through “ERS” output type through TCode:MR90

Already Processed ERS Invoice

Input Selection

Output type: ERS
Processing mode: 2   (Repeat Processing)
Invoice document no : XXXXXXXX
Fiscal Year: XXXX

Now using transaction MR90 we tried to repeat process the output

  On execution of above it gives below message:
“ NO MESSAGE FOR REPEAT PROCESSING EXIST”

So here, ERS Invoice cannot or not able to print the ERS Invoice which is already processed or Printed.

  Whereas other logistics invoices are enabled to Print multiple copies and now this requirement is to print already processed or printed ERS invoices (multiple copies) through ERS output type.

FUNCTIONAL CONFIGURATION

Config As-Is in Standard SAP :                              

Path>NACE> Application MR>ERS Output type

  “CannotBeChanged” check box is activated as per standard SAP Package.

Config Changed to fix the Requirement:

“CannotBeChanged” check box is De-activated.

Now ERS Invoice is printed through Tcode MR90

Output type: ERS
Processing mode: 2   (Repeat Processing)
Invoice document no : XXXXXXXXX

Fiscal Year: XXXX

Thus , Multiple copies of Invoice can be printed.

Introduction:

Very often we get issues like stock shown in Material Master record with Stock available in MMBE . At the same time, valuated stock will not match with codes/reports like MCBE, MC.9, MB53. It is very important in Inventory Management to check that the stocks are properly maintained for their correctness in terms of quantity and value. These type of inconsistencies cause instability of system in terms of incorrect reporting, false stock statements and incorrect decisions.

This document deals with possible causes of stock inconsistencies and the analysis required for finding the same and taking corrective measures.

Possible Reasons for Stock Inconsistency:

Prolonged usage of inventory management transactions like MIGO, MB1B for stock posting.

Archiving of documents.

Wrong postings with negative stock\

History tables MBEWH, MARDH, MSEG, MKPF not updated properly

Errors during Inventory Transactions:

Whatever may be the reason, system would become inconsistent which may provide error message like any of the following :

M7 308 'Stock value and qty are unrealistic: & / &

M7 309 'Stock value is negative: &

M7 310 'Valuated stock is negative: &

M314 'Valuated stock becomes negative: &

The possible reason is, there exist no actual stock in the system, though MMBE shows some stock. Most of the time this could be the reason for error messages.

Transactions where we can check the stocks:

Various transactions which are used to find stocks in SAP are :

MMBE - Stock Overview Report

MM03 -  Accounting view of material master fetches data from MBEW (table for valuated stock)

MB53 - Plant Stock Availability

MB52 - Warehouse Stock Availability

Possible causes of inconsistency and their solution:

1. Difference between storage location stock and batch stock

Sometimes, the sum of all batch stocks from MCHB table for a particular material differ from storage location stock available from table MARD. This is not applicable to spacial stock like Sales Order stock or Project Stock.

The possible reason for this inconsistency could be when you use a modification for batch number assignment. One batch is assigned several times (e.g. use of a dummy batch number or the actual date)

Solution:

Check your modification in batch number assignment, in particular in Function Module VB_NEXT_BATCH_NUMBER.

A second option to find whether the inconsistency is a result of such a modification is to call transaction MSC3N for the relevant batch and display the change documents. If there there several change documents with the content "Batch created", this usually hints to a modification in batch number assignment.

To avoid further inconsistencies, delete your modifications. Implement Notes 1035372 and 1062164 and set the parameter ALLOW_EXISTING_BATCH in the existing user exit EXIT_SAPLV01Z_002 to make postings to the existing batch. If the system now issues the error message M3 204 'Batch & already exissts in plant &' or M# 556 'Batch & already exists for material &' , you must repopulate the batch number in the user exit EXIT_SAPMM07M_010.

2. Wrong Goods Receipt

In your system, there is a GR for PO, in which an item in the material document contains the material number of the previous purchase order item.

3. A material has inconsistent data

The stock in Accounting View (Table MBEW) does not correspond to the stock in the Stock Overview. You have own programs which cary out an update on MBEW.

Cause and Prerequisites:

Table MBEW contains valuation data of material , for example the total stock and total value.  These fields are updated with every goods movement. With these frequent changes in the table, each updatem which doesnot lock the table correctly, can cause data inconsistency.

Solution:

Do not use your own programs to change fields LBKUM, SALK3, SALKV, VKSAL, STPRS, VERPR, VPRSV of table MBEW.

If you use own programs which changes other fields of table MBEW, always use the addition SET. Thus, on the database only, fields specified with command SET are changed. Stock postings which may be carried out at the same time remains unaffected.

4. Non-generation of Accounting Document in MIGO

When Goods Movement is posted, a material document is generated. However, no update on the dependent stock tables, such as MARD and MBEW are carried out. In addition, no accounting document gets generated.

Causes and Prerequisites

Following procedure causes incorrect update.

i. You post goods movement with transaction MB11 or MB1A

ii. You enter movement type, plant and storage location in initial screen and choose Enter

iii. You enter material number in the following overview screen and confirm your entry by choosing Enter.

iv. Since you did not fill the field quantity, you reach the detail field automatically. Your system generates warning message M7 129 'Enter a quantity'.

v. You display the movable quantity using Key combination Shift + F5, and exit the dialog box (F12).

vi. Enter the entry quantity in the following detail screen and confirm it by choosing Enter.

vii. Then press cancel (F12)

viii. You reach the Overview screen again and post goods movement (F11)

5. Due to Period Closing Issues

In period closing for material master (MMPV), goods movement are done during the interval between Last Day of the Old Period and First Day of the New Period.

It is recommended not to post any documents whilst the period closing programs are running. Before the period closing program runs, check in transaction SM13 whether outstanding update terminations of goods movement are still displayed. These must be cleared and closed before the period closing program runs.

Useful Reports to Analyze Inconsistencies:

RM07SHUP - Shows updates recorded in table mminkon_up.

MBANEKBE - Display of a purchase order history

MBCKBSEG - This report checks Materials having balance in FI with no entry in MBEW, Materials with wrong valuation class in MBEW as a result of which account determination gets different account as in BSEG , Materials which have a different actual value in MBEW as in BSEG, Manual Postings or with posting key not equal to BSX for stock accounts

MBCKBSIM - This report checks whether for all BSEG entries, a BSIM entry exists

MBTRAMEW - This report will try to find inconsistencies caused by Stock Transfer Orders with active ingredient batches. This report also allows posting the correction using transaction MWBE

RM07HIST - routine to read history stock from history tables.

MBUPDATE - This report allows modification of MM-IM table fields. Updated values are stored in table MMINKON_UP

MBLABST - Shows general information and Stocks for a specified material in a specified plant.

MBMSSQCR - Using this report, user may change the content of field MSSQ-KZBWS (special stock valuation indicator) when the special stock is 0.

Conclusion:

Although there are many reasons for stock inconsistencies, some of possible reasons and there solutions have been discussed. Finding out inconsistencies and their corrections will improve the stock management thereby, reducing the inventory costs.

This document consists of authorization problem in MM01/02/03 (Material master) for material types.

I add material authorization group (BEGRU field) to T134 table  so you can implement authorization for different material types in material masters.

I hope that it can be helpful...

Related Oss Notes :

545380 - FAQ: Authorizations material master

303483 - Authorization check enhancement

Related Authorization Objects :

M_MATE_MAR , M_MATE_MAN , M_MATE_MAT , M_MATE_STA , M_MATE_WGR

For example , i implement authorization for HAWA material type creation.

  -->  Go to SE54 tcode and create authorization group

  -->  Assign authorization group ---> determine work area  ---> Table name T134 , Authorization group HAWA

--> New entries .

--> Go to HAWA material type configurations and define authorization group...

-->  You can see T134 details with SE16 , BEGRU-HAWA

**Solution -- SU01 - Roles/ Authorizations / Add - M_MATE_MAR - Authorization Group HAWA and generate.

**Result: You can manage your authorizations in MM01/02/03 with material types.

     I hope that it can be beneficial for someone.

     Regards.

     M.Ozgur Unal

These days, I read documents related with M8 system messages , tolerances , invoice reduction etc.

In this document , i work on implementation and configuration SAP MM Logistic Invoice Verification. My example contains a example which it prevents different postings based on quantity and amount. We will get a problem that i want to post bigger amount, sap will not give permission with error messages finally invoice reduction will solve our this problem.

You can get details : MM-IV-LIV-CRE Set Tolerances for Incoming Invoice - ERP SCM - SCN Wiki

Related Oss notes&KBA :

1372102 - IMG documentation: Set Tolerance Limits

786810 - MM IV: Tolerance check when you enter invoices

313190 - MR1M: Tolerance groups not taken into account

963185 - MM IV: Tolerance check for entering and releasing invoices

791036 - Tolerance check on account assignment item

1674901 - MIRO shows error message M8083 and does not propose amount value when working with Invoicing Plan

608041 - Tolerance checks with service-related invoice verification

1598731 - No payment block if the lower limit is exceeded during invoice posting - MM-IV

2054815 - MR8M: Not able to cancel a credit memo due to tolerance limit error.

134976 - Tolerances for blanket purchase order

396095 - MRBR: Message M8215 for tolerance key 'DW'

610340 - No tolerance check for the credit memo

2004992 - MIRO/MIR7: System will not automatically propose "Amount" and "Quantity" after you have done GR 107.

1880413 - Duplicate Invoice Check functionality does not work

158611 - MR1M: Block of invoices for services

753286 - Moving average price becomes very low

90013 - Tolerance limits not converted to local currency

1890543 - Cannot set message "M8 082" as an error at company code level

1853807 - MIR4: Message M8 084 as error message stops posting

1919689 - MIRO: User tolerances are not taken into account

I have a PO , my person posted a material document 100 qty.

     In Miro , can you post more quantities and amounts ? Is it related your tolerances ? Not at all.

     If posting exceed your tolerances , you can post but it is blocked. If not, you can not prevent. Sometimes , you can not be aware of tolerances when you can post fastly. It is dangerous.

Examples :

1 - Amount is bigger than PO.

2- Quantity and amount are bigger than migo and po values.

     What can i do ?

     Firstly , check your LIV system messages.

     You can update your M8 / 81-82-83 messages with ERROR also if you get them.

     MM/Logistic Invoice Verification/Invoice Block/Set tolerance limits

     * Please check DQ and PP tolerance keys.

     However , it is not enough to prevent posting . You have to maintain your LIV system messages.

     * I configure M8 messages with ERROR.

     * When i post our invoices , sap will not give permission...

     ** Unfortunately , i have to post some like a weigher result , vendor errors invoices with variances , how can i solve this problem ?

     **Sometimes , you can post your invoices with tolerance even though you implement system messages. Invoice reduction can help you.

     *Select layout : Invoice reduction , Correction ID : 2 Vendor error - reduce invoice ,Invoice amount Acc to Vendor , however you can use similiar way for quantities. Sap will create one more fi record for differences.

     Results :

    ** Configurations :

     You have to configure your T030 table with RKA transaction (OBYC tcode) and invoice document types.

     I add RK document type for invoice reduction. (OMR4)

     However, if you want to update some datas to implement in your country like a tax rates ..

     You have to update records with enhancement implementation program LMRMCF07 .

     I hope that it can be benefical for your business life thoughts.

     Thanks a lot for spending times ...

     Regards.

     M.Ozgur Unal

This document consists of configuring the material master. However , an understanding of how to make changes to material master.

You can benefit from related Oss notes :

192798 - Problems copying and deleting logical screens

1088189 - Composite SAP Note for material master

545211 - FAQ: Material master Customizing

580227 - Material master: Subscreen staggered by one column

327936 - Classification subscreen in the material master

32139 - User-specific material master - default setting

41174 - Material Master Customizing

107404 - Missing Text in Material Master Views/Screen Sequences

955032 - Material Master: Additional fields for Service Parts Mgmnt

1038117 - ED: Maintaining new field in matrl master data at CC level

1304710 - Material Master: Add. fields on client level for SPM

1141122 - Material Fields for EWM not change document relevant

I try to explain configuration the material master settings for different users or everyone. When you run MM01 tcode , you will see datas for several departments like a purchasing , accounting , mrp , wm , qm ... If you want to prevent some views , you can configure material master dialog.

Logical screen and subscreen :

Bellowed print - screen have a Subscreen-General Data with screen number 2001 . Also , all of the datas of subscreens built a Logical screen-Basic data 1.

When designing your own logical screens, you can use either your own subscreens or standard sap subscreens.

Refer to Additional Fields on the Material Master ... Thanks to Miroslav Oprsteny

Refer to Enhancing Material Master for adding new fields.. Thanks to Shahanaz Hussain

Use your own screens if you want to have different field groupings , Tools-->Abap workbench-->development-->user interface-->screen painter.

An example for configuring material master :

I want to use the subscreen with Environmentally relevant and DG Indicator Profile fields in Purchasing view in the case of a special material type and only by certain users.

* In the technical information dialog box , screen number 2010 for the program SAPLMGD1 , Note : Users have to use their own programs to insert fields from their tables and their sunscreens for material masters.

* Create a new screen sequence , copy 21 to Z0  , configuration steps :

--> ZO screen sequence created

--> Check data screens

On columns , you can maintain screens :

Screen types :

1 : Main screen such as Basic data , Purchasing , Sales

2 : Secondary screen such as Additional data

Screen container :

Screens for program SAPLMGMM like a 4004 Main screens with 10 subscreens.

Maintenance status :

Special user departments can maintain a MM record of a particular material type.

GUI Status :

GUI status are defined in Menu-->Painter which consists of a menu bar with menus, a standard toolbar, an application toolbar and functions with function key settings.

Title type for selection group:

Type 2: three/four-part title type, for main screens

When transaction title maintain , it is made up  description, screen name, industry sector and material type.

Retail maintain status :

* Change data screen for purchasing related fields in the subscreen 2010.

--> General information : Double click subscreens

* Also ,you can view subscreen and data screen

--> Configurations for adding subscreen to purchasing view , sequence 14 purchasing

--> Replace subscreen 5 with the environment relevant fields

--> Specify for your requirements like a transaction , user , material type , industry sector

--> For example - Specify for material type screen reference : Sarf

--> Go to OMS2 and maintain screen reference of material type

--> You can see Environment related subscreen in Purchasing view of  Sarf material type

Thanks to Selin Unal for her passion

Regards.

M.Ozgur Unal.

SAP MM / Partner Determination

This document explains the settings for partner determination in the vendor master. When you create a business partner, assign data to an account group. An account group decides the business partner. Partner roles refered as partner functions. Various partner roles can be stored in vendor master like Payee , Invoicing party , Goods Supplier and Ordering Address etc.

Related notes :

938652 : PI partner Pur.Org.Data not relevant for Partner Determination

673062 : Partner determination selects blockd/deleted partners

542645 : ME22N : No partner determination when checking/saving PO

431351 : ME22N : Change PO , no new partner determination

420058 : ME21N error ME366 after changing the document type

407600 : Message determination of partners in STO

401734 : ME21N  STO , partners disappear

394091 : Partners are not transferred from vendor master

376319 : ME21N partner from reference document not found

117537 : ME27 : No partner determination w.stock transp.orders

FAQ :

-- OSS Note 459350 - FAQ : Partner determination in purchasing

Info :

Some partner roles are predefined in SAP :

*Vendor (VN) , Ordering address (OA) , Invoicing party (IP) , Different payee (AZ), Contact person (CP), Employee responsible (ER) , Intrastat  declaration (GS )

Intrastat declaration : Intrastat is the system for collecting information and producing statistics on the trade in goods between countries of the European Union (EU)

Helped :INTRASTAT Processing in Purchasing - Materials Management (MM) - SAP Library

Partner determination can be used for price determination, message determination, address determination, statistics. If you define a lot of partner roles, you can select one of them like a default. When someone creates a purchasing document, default value is seen in the list.

To use partner determination , you will need to define a partner schema for purchasing document. When you define schemas, the previously created partner roles are assigned to the schema. If account group is assigned a partner schema, sap checks whether the role you enter in schema or not. You can receive a error message, if sap does not find related role.

1- Define Partner Schemas :

SPRO / Materials Management / Purchasing / Partner Determination / Partner Settings in Purchasing Documents / Define Partner Schemas

Select partner schema 0002 and choose Partner Functions under the Procedure node in the Dialog Structure tree.

      INDICATORS:

      No change indicator : If you want to prevent changes in partner defined in the vendor master record and prevent deleting partner roles, it is set.

      Mandatory indicator : Whether a partner role is mandatory in a vendor master or PO.

      Higher level indicator : If partner role does not been found in plant or sub-range level, sap looks for partner role at purchasing organization level. Hpwever, higher level is used process of automatic creation PO.

     End indicator : If it is set , partner role is defaulted from vendor master when document is saved or checked. It is useful when different data is added in the vendor at the plant/vendor subrange. Whether all items contain same plant or subrange. Invoicing parties are not determinated until end of document process PO so end incator might change it.

2- Define Settings for Vendor Master Records :

Firstly , configure your 'Vendor Account Group' for Partner determination procedure.

SPRO / Logistics - General / Business Partner / Vendors / Control / Define Account Groups and Field Selection (Vendor)

     How can i select L1 partner schema for Purchasing organization ?

     Spro/ Mm / Purchasing / Partner determination / Partner Settings in Vendor Master Record

     Firstly , define partner roles.

     Secondly , Assign Partner Schemas to Account Groups .

3- Message Determination :

- Determine partner schema for account group.

- Ordering address partner role (OA) must be maintained. The role is allowed for account group.

- Check whether partner schema is used to determine partner roles for purchasing document type.

Output a message to  this partner , you need to create a message condition record in purchasing master data. MN04 will help you.

Firstly, decide output type , after that specify dependent information for message determination.

Related subjects :

You can enter alternative freight vendor for planned delivery costs when you post a good receipt.

M8 / 776 (IP must have allowed in partner role) and 777 (IP has partner role in Purchase Order) system messagescheck partner roles as soon as invoice verification. They can be configurated as a warning or error.

Configuration steps:

Access Sequences

SPRO > Material Management> Purchasing > Message > Output Control>Access Sequences>Define Condition Table for Purchase Order

Message Type

SPRO-> Material Management> Purchasing > Message > Output Control>Message Types>Define Message Type for Purchase Order

Message Determination Schemas

1. Message Determination Schemas

SPRO> Material Management> Purchasing > Message > Output Control > Message Schema >Define Message Schema for Purchase Order > Maintain Message Determination Schema

2. Assign Schema to Purchase Order

SPRO-> Material Management> Purchasing > Message > Output Control >Message Schema >Define Message Schema for Purchase Order> Assign Schema to Purchase Order

Partner Roles per Message Type

SPRO > Material Management> Purchasing > Message > Output Control > Partner Roles per Message Type >Define Partner Role for Purchase Order

**Condition Record

SAP Easy Access Menu > Logistics > Material Management > Purchasing > Master data >Messages > Purchase Order> MN04-> Create

Now you create PO (ME21N) and save it.

4- Allowed partner roles

You can do with Account group : Field reference , Permitted partner roles

After that specify partner role VN is allowed for account group ZVMU.

SPRO / Materials Management / Purchasing / Partner Determination / Partner Roles / Define Permissible Partner Roles per Account Group

Spro / MM / Partner Determination / Partner Settings in Purchasing Documents / Assign Partner Schemas to Document Types

*** Also , you can assign to UB document type for STO.

5- Vendor settings and an example for price determination

For instance , i used a vendor master 'T-K55001' also i maintained Partner Function datas in master data.

DP : Default partner

I set a discount for Invoicing party. MEKJ tcode will help us.

If a partner role is found at the end, the system does not update the prices.

I created a PO to Vendor , but discount is implementable for Invoicing Party.

     Thanks to Mr.Jurgen for his valuable feedback.

     Regards.

     M.Ozgur Unal