SAP MM Configuration Guides

 The information below are SAP Baseline Packages. They are the standard SPRO configuration that can be done in the system without any form of Enhancements.

http://help.sap.com/bp_bblibrary/500/html/W30_EN_DE.htm

http://help.sap.com/bp_bl603/BBLibrary/Content_Library_BL_EN_CL.HTM

Upgrade Guides

Getting Started withan upgrade to SAP ERP 6.0
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e05ed6c7-c608-2b10-e0b9-95d2111c0b0a?QuickLink=index&overridelayout=true

http://www.thespot4sap.com/upgrade_guide_v2.pdf

https://websmp106.sap-ag.de/upgrade-erp.
This link requires SAP Marketplace ID.

Upgrading to SAP ERP 6.0

Please view from the link below to find the success stories of Upgrading to SAP ERP 6.0
http://www50.sap.com/m1/erpupgrade/SAP_Upgrade.pdf

SAP ERP 6.0 Upgrade FAQ

SAP ERP 6.0 Upgrade FAQ

Frequently Asked Questions

• General
• Why upgrade to SAP ERP? What are the business drivers to upgrade to SAP ERP?
• What is new about SAP ERP 6.0?
• Is there a way to do a cost/benefit analysis for an upgrade?
• Is there a minimal support package customers must be on on before upgrading to SAP ERP 6.0?
• What are the SAP upgrade options available and what are the recommendations to the present customers?
• Does SAP offer direct upgrades to and from SAP releases in extended maintenance? What is the oldest SAP R/3 release allowing a direct upgrade to SAP ERP?
• How do SAP and its partners support existing customers in upgrading?
• How can SAP Solution Manager support me in an upgrade project?
• What do I need to consider when upgrading an SAP component, for example, SAP ECC, within an SAP solution or multiple SAP components of an SAP solution?
• Where can I find detailed information on SAP's release and maintenance strategy?
• Does an upgrade to the current release of SAP ERP require additional training for end users?
• Do customers need to convert to a Unicode-compliant environment?
• Is there a way to reduce downtime when I perform an upgrade and a Unicode conversion?
• What production downtime should we expect during the technical upgrade?
• What should we consider when upgrading the new general ledger in SAP ERP?
• How should we organize an upgrade project?
• What constitutes an SAP upgrade project team?
• Technical Upgrade Procedure
• Where can I get more information on what the upgrade does in the various upgrade phases (ABAP)?
• How can I upgrade ABAP + Java double-stack systems?
• Can I upgrade from a pure ABAP system to an ABAP + Java system?
• Can I install additional usage types during a Java system upgrade?
• How can I save time for post-upgrade imports, such as release customizing, adjustments to customer-specific applications, interfaces and forms, and ABAP code modifications?
• IT Infrastructure
• What impact does an upgrade to SAP ERP have on the hardware?
• What does SAP offer to support the sizing of the future IT infrastructure?
• How does Unicode affect the hardware sizing?
• How does the database size influence or relate to the downtime and runtime of a technical upgrade in general?
• What are the resource requirements when upgrading to SAP ERP 6.0?
• Application and Modification Adjustment
• How should we manage modifications of the previous software during the upgrade?
• What do I need to consider when working with the SAP Modification Assistant?
• Does SAP recommend considering functional enhancements during an upgrade project?
• How do I handle problems if - after the technical upgrade - in certain areas, the application does not work properly anymore?
• Where do I get details on the relevant customizing changes for the target release?

SAP MM Reports

Master Data

Vendor Master
MKVZ - Vendor list
S_ALR_87012086 - Vendor List
S_ALR_87012087 - Address List
S_ALR_87012089 - Display Changes to Vendors
 
Material Master
MM60 - Material list
MM72 - Display Archive of Materials

Purchase Order
ME2N - Purchasing Documents per Purchasing Number
ME80FN - General Evaluations
Run SE38 --> Program: RM06EM00
ME2S - PO Reporting with Services

Inventory Management
MMBE - Stock Overview (Per Material)
MB52 - Display Warehouse stocks of materials
MB5B - Stock on Posting Date
MB5L - List of Stock Values : Balances
S_P00_07000139 - Stock card and Inventory Material Report

GR/IR
MB5S - List of GR/IR Balances

Service Entry
MSRV6 - Reporting on Services

Vendor Evaluation

ME65 - Ranking Lists

ME6B - Evaluations per Material/Material Group

ME6C - Vendors Without Evaluation

ME6D - Vendors Not Evaluated Since

ME6H - Standard Analysis

A good reference site for SAP Reports
http://wiki.sdn.sap.com/wiki/display/ERPLO/SAP%20Standard%20Reports?bc=true

Organizational levels in the SAP procurement process

The organizational level that you see above is the one related to Materials Management. No matter where you go under the MM Processes, you would have to go through at least 1 of the above.

Client
The Client is the highest hierarchical level unit within a SAP system. We can say that it represents an Enterprise. We can also say that within this Enterprise, there might be more than 1 companies, which leads us to the next level, Company Code. It is represented in the system by a 3-digit numeric key.

Company Code

A Company Code is the organizational unit that allows you to structure your enterprise from a financial accounting perspective. It represents an independent unit producing its very own balance sheet, e.g a company within an Enterprise (Client). It is represented in the system by a 4-character alphanumeric key. This includes the entry of all events that require posting to the accounts and the creation of a complete audit trail for balance sheets and profit and loss statements. A company code represents an independent unit producing its own balance sheet, for example, a company within a corporate group (client).

Plant
The plant is an organizational unit where Operations are concerned. When I say operations, I mean Production, Procurement, Materials Planning and Maintenance locations. It is represented in the system by a 4-character alphanumeric key.

Storage location

The storage location is an organizational unit where we differentiate stocks of materials within a warehouse/plant. If further breakdown is required, we can use Storage Bins. It is represented in the system by a 4-character alphanumeric key.

Purchasing Group
Purchasing Group is a key to identify a buyer or a group of buyers responsible for a particular type of purchase. It is however not related to other units in the company structure.

Purchasing Organization

A Purchasing Organization is a unit which is responsible for the procurement of services/materials, and condition negotiations with vendors.

Special Procurement Processes

Vendor Consignment

Consignment basically something that vendor provides you and you store in your warehouse but you do not have to pay for it, until you use it. In this case, the vendor still remains as the owner of the stocks. Only when we consume these materials, then we will be charged/liable for it. Therefore, to settle this liabilities, it is according to agreed periods with the vendor, for example monthly.

In order to start this consignment process, you will have to first have an agreement on the price per quantity for the consigned materials. In SAP, we call this Consignment Info Record.

Remember earlier, I have mentioned that we will only be charged when we "Use/consume" the consigned materials? So, when referring to this, the procurement cycle for Consignment is a little bit different. The procurement cycle starts with a Purchase Order for Consignment Items, and it ends after Receiving the goods. This is because payment is required not after supply but after withdrawal.

Subcontracting
This procurement process is actually similar to the standard Procurement cycle. However, we would provide some or all of the components required to produce the material.

The Process starts of with a Subcontract Order where you indicate the material which is to be delivered, plus the components that you would provide to the Subcontractor.

So, when the vendor has received the Subcontract Order, he cannot start production until you have provided him with the necessary components. You perform this transfer of components by means of transfer posting where the materials are no longer physically in your location. It is now with the vendor for him to consume in order to produce the end-product.

As soon as the subcontractor completes the production for the end/refined material, he would then deliver it to you. This is now the Goods Receipt process. Unlike the standard Goods Receipt, here for Subcontracting process we Receipt the end-material as well as Issue out the components that was used by Subcontractor. These components are considered as subcontract consumption. In the end, the subcontractor will send us an invoice for the service given.

Stock transfer with Stock transfer Orders
This is a unique type of procurement because it does not involve an external vendor. It is a procurement method that is done within a company. The plant that needs the material will come up with an internal order called Stock Transport Order directed to the other plant which will be providing the material.

The issuing plant who receives the Stock Transport Order, will then provide the materials by performing Goods Issue with reference to the Stock Transport Order in SAP. After this is done, the receiving plant performs Goods Receipt against this Stock Transport Order to receive the materials.

This process can also be simplified by means of Transfer Postings only. In this case, we do not have to create a Stock Transport Order, but instead, perform Transfer Posting between receiving and issuing plant straight away.

Basics of External Procurement Process

The MM Module will be revolving around this business process. It is just whether we will be using each of it to its full extent or not. Let's begin :)

Requirement Determination

Before we can start with an external procurement process, we would need to have a requirement for it. A requirement can come from a few sources. Example, when there is a need for a new Printer in the Finance Department, therefore a user over there would raise a Purchase Requisition manually. Another example, when we have a MRP Procedure for a particular material (MRP Planning/Reorder Point/etc), SAP is able to generate Purchase Requisitions automatically or create a Planned Order first, which would be converted to Purchase Requisitions later on individually.

Source of Supply Determination
In SAP, we can also classify Vendors where we are allowed to procure from. There are also various methods in SAP to help you identify the possible sources to procure the goods. By doing so, you will be able to send Request for Quotations to the respective sources. This step is however optional, you can actually proceed to create a Purchase Order immediately.

Vendor Selection

If you chose to send Request for Quotations to a few sources, SAP automatically performs price comparisons based on the Quotations that they have provided. SAP is also able to send rejection letters to the vendors that did not qualify for the purchase.

Order Processing

This is where you create the official Purchasing Document called Purchase Order. You can create them manually in SAP or Automatically by the system. In SAP, you do not have to re-enter the Data in Purchase Order, but instead, you can copy the data from Purchase Requisition, RFQ, or Outline Agreements.

Purchase Order Monitoring

After creating a Purchase Order, it is necessary to check from time to time, the statuses of the Purchase Orders. In the Purchase Order report, it is possible to check for each PO, how much has been delivered, invoiced, etc.  It is also possible at this stage to remind vendors of outstanding deliveries.

Goods Receipt

When you enter incoming deliveries (by looking at the delivery order provided by vendor), you will be referring to the Purchase Order, therefore, entry work is minimized. SAP is also able to check how much quantity is still open for receiving, and it is also possible to set tolerance levels. For example, If your Purchase Order quantity is 100, you can set a over delivery and/or under delivery tolerance. Therefore, system will check against the tolerance % that you have set, and if you enter a quantity that exceeds this, SAP will throw you an error message.

Invoice Verification
When performing Invoice Verification in SAP, you will be referring to either the Purchase Order or Goods Receipt document. SAP will perform the necessary checks to ensure that you do not over or under pay the Vendor. Once this is completed, the MM Cycle is over. The next step "Payment Processing" is under the FI Module.

Payment Processing
This is the final step where the payment program authorizes payment to the creditor liabilities.

This covers the Standard External Procurement Cycle. Apart from the above, there are other special procurement processes such as Vendor Consignment, Subcontracting, Stock Transfer, etc. They will be explained later. For now, we should all be clear of the Standard cycle because the whole of MM evolves around it.

TechCentral - SAP aims for a billion users worldwide

TechCentral - SAP aims for a billion users worldwide

KUALA LUMPUR: Enterprise software giant SAP AG wants to enlarge its worldwide user base about 30-fold by 2014.
V.R. Srivatson, managing director of SAP Malaysia, said the company has 34 million users (in 27,000 companies) globally and aims to have a billion users by that time.
The German company could not provide Malaysia-specific figures.
SAP believes that offering on-demand services via cloud computing will help with its goal.
"Traditionally, we have always been on premises and hosted our applications on servers at client sites but now we are offering software on-demand as well," Srivatson said.
He also noted that many enterprise applications will be created to include access via the mobile phone.
"More and more workflow processes will be brought onto the phone and other mobile devices," he said. "Leave applications, expense claims and other approvals will soon be done via cellphones."
SAP believes this will contribute to its growth because it makes it easier for company employees to work more efficiently.
Srivatson was speaking during the Kuala Lumpur leg of the SAP World Tour 2010. The event is aimed at offering networking opportunities and thought leadership keynotes, as well as focused product presentations and demonstrations.
 

What happens to PRs generated from Maintenance Orders once status is changed from REL to TECO

The Issue
When we change the Maintenance Order status to REL, a PR will be generated.
When we change the Maintenance Order status to TECO, the PRs will automatically have a deletion flag set to it.
So who controls PR in this case? PM or MM?

The Solution
Now the scenario is between Plant Maintenance and Materials Management. What you are saying is, when a PM Order with PM02/PM03 is control key is created, it will create a Purchase Requisition.
This is correct and in this case, the direct owner or controller is the Plant Maintenance Order itself. If you notice, when you release the Order, then only the PR is generated? And when you Teco the Order, the PR line items are automatically deleted? This is to prevent future creation of Purchase Orders based on PR when the Order is already closed.

For cases like these, involving both PM and MM, the owner is the Order, you cannot do the changes in PR. You have to do the changes in the Order. By doing so, the PR will be updated automatically.

If you Un-Teco the PM Order, the PR line items will be UN-deleted. They will be open again if PO has not been created against the PR line item yet.

SAP MM Important Tables

Related to Materials:

MARA - Material Master: General data
MAKT - Material Master: Description
MARM - Material Master: Unit of Measure
MAPE - Material master: Export control file 
MARC - Material master: Plant data
MARD - Material master: Storage location 
MAST - Material link to BOM
MBEW - Material valuation
MLGN – Material Master: WM Inventory
MLGT – Material Master: WM Inventory type
MDIP - Material: MRP profiles (field contents) 
MKOP - Consignment price segment (old versions of SAP)
EBEW - Valuation of sales order stock
QBEW - Valuation of project stock
MVER – Material Master: Consumption
DVER – Material Master: Consumption
MVKE – Material Master: Sales
MLAN - Material Master: Tax indicator
MARC - Material Master: Plant data
MAPR – Material Master: Forecast
MARD – Material Master: Storage Location
MCH1 – Material Master: X Plant Batches
MCHA – Material Master: Batches
MCHB – Material Master: Batch Stock
MDMA - MRP Area data
DBVM - MRP Planning File Entry: MRP Area
MOFF - Outstanding Material Master Records (Maintenance status)
MARCH - Material Master C Segment: History
MARDH - Material Master Storage Location Segment: History
MBEWH - Material Valuation: History
MCHBH - Batch Stocks: History
MKOLH - Special Stocks from Vendor: History
MSCAH - Sales Order Stock at Vendor: History
MSKAH - Sales Order Stock: History
MSKUH - Special Stocks at Customer: History
MSLBH - Special Stocks at Vendor: History
MSPRH - Project Stock: History
MSSAH - Total Sales Order Stocks: History
MSSQH - Total Project Stocks: History
MOFF - Outstanding Material Master Records (Views not yet extended)
MSTA - Material Master Status (Views maintained)

Related to Vendors:

LFA1 - Vendor Master: General data
LFB1 - Vendor Master: Company data
LFM1 - Vendor Master: Purchasing Data (Purchasing organization)
LFM2 - Vendor Master: Purchasing Data (Plant, Vendor sub-range)
ADR 2 - ADR 6 (Address and Phone details)

WYT1 - Vendor Subrange

Related to Purchasing:

EBAN - Purchase requisition: items
EBKN - Purchase Requisition: account assignment 
STXH - SAPScript Text Header
STXL - SAPScript Text Lines
EKKO - Purchasing document header 
EKPO - Purchasing Document: Item
EKES - Purchasing Document: Confirmations
EKET - Purchasing Document: Delivery Schedules
MDBS - Material View of Order Item/Schedule Line (good to find open PO's)
EKKN - Account assignment in purchasing document 
EORD - Purchasing Source List
EIPA - Order price history record 
EKAB - Release documentation 
EKBE - Purchasing document history 
EKBZ - Purchasing document history: delivery costs 
EKET - Scheduling Agreement Schedule Lines
EKPB - "Material to be provided" item in purchasing document 
ESKL - Account assignment specification for service line 
ESKN - Account assignment in service package 
ESLH - Service package header data 
ESLL - Lines in service package 
ESSR - Service entry sheet header data 
ESUC - External services management: Unplanned limits for contract item 
ESUH - External services management: unplanned service limits header data 
ESUP - External services management: unplanned limits for service packages 
ESUS - External services management: Unplanned limits for service types
EINA - Purchase Info Record: General
EINE - Purchasing info record: purchasing organization data 
KONP - Condition Item
KONH - Condition Header

Related to Inventory Management:

IKPF - PI Header
ISEG - Physical inventory document items
MKPF - Material document: Header
MSEG - Material document: item
RKPF - Reservation: Header
RESB - Reservation: Item

Related to Invoice Verification

BSIM - Secondary index: documents for material
MYMFT - FIFO results table
MYML - LIFO material layer 
MYMLM - LIFO material layer (monthly)
MYMP - LIFO period stocks, single material 
MYMP1 - Receipt data LIFO/FIFO valuation
MYPL - LIFO pool layer
MYPLM - LIFO pool layer (monthly)
RBCO - Document item, incoming invoice account assignment 
RBDIFFKO - Invoice Verification: conditions 
RBDIFFME - Invoice Verification: quantity differences
RBDRSEG - Invoice Verification batch: invoice document items
RBKP - Document header: incoming invoice
RBKPB - Invoice document header (batch invoice verification)
RBTX - Taxes:incoming invoice
RBVD - Invoice document: summarization data
RBVDMAT - Invoice Verification: summarization data, material
RBWT - Withholding tax:incoming invoice
RKWA - Consignment withdrawals
RSEG - Document item, incoming invoice
EKRS - ERS Procedure: Goods to be invoiced

Related to Customising and Other Master Data:

MDLV - MRP Areas
MDLG - MRP Areas - Storage Locations
MDLW - MRP Areas - Plants
MDLL - MRP Areas - Subcontractor
T023 - Material Groups
T024 - Purchasing groups
T030 - Standard Accounts Table (Automatic Account Determination)
T156 - Movement Type
T156T - Movement Type: Text
AUSP - Release Procedure: Strategy values (cl20n, cl24n)
AGR_USERS - Assignment of roles to users
CDHDR & CDPOS - Change history of master data and documents
EDID4 - EDI information
TSTC - SAP Transaction Codes, lock/unlock: sm01, created: se93
TSTCT - Transaction codes TEXT
NAST - Message status

Related to Address
ADRC - Addresses (Business Address Services)
TWLAD - Determination of Address from Plant and Storage Location

Related to Batch Management
MCHA - Batches
MCH1 - Batches (if Batch Management Cross-Plant)
MCHB - Batch Stocks

Related to Serial Numbers
SER00 - General Header Table for Serial Number Management
SER01 - Document Header for Serial Numbers for Delivery
SER02 - Document Header for Serial Nos for Maint.Contract (SD Order)
SER03 - Document Header for Serial Numbers for Goods Movements
SER04 - Document Header for Serial Numbers for Inspection Lot
SER05 - Document Header for Serial Numbers for PP Order
SER06 - Document Header for Serial Numbers for Handling Unit-Content
SER07 - Document Header for Serial Numbers in Physical Inventory
SER08 - Document Header for Purchase Order Item Serial Numbers

Related to Release Strategy
T16FS - Release Strategies
T16FT - Descriptions of Release Strategies
T16FG - Release Groups
CAWN - Characteristic values
CEBAN - Communication Release Strategy Determination: Requisition
CEKKO - Communication Release Strategy Determination Purch. Document

Related to Classification
KSSK - Allocation Table: Object to Class
KLAS - Sort table - internal class number
KSML - Characteristics of a Class
CABN -Characteristic
CAWN - Characteristic values
AUSP - Characteristic Values
INOB - Link between Internal Number and Object

Related to Oil and Gas
VTTK - Shipment Header
OIO_C1_CNTNR - RLM Oil and gas container master data

Related to BOM
STPO - BOM Item Details
STPU - BOM Sub Items (designators)
STKO - BOM Header Details
MAST - BOM Group to Material
STZU - BOM History Records
STAS - BOM Item Selection
STPF - BOM Explosion Structure

Related to Vendor Evaluation
ELBK - Vendor Evaluation: Header Data
ELBM - Vendor Evaluation: Material-Related Item
ELBP - Main Criterion for Vendor Evaluation

T147 Control Table for Vendor Evaluation

T147A Definition for Main Criteria for Vendor Evaluation

T147B Texts for Main Criteria in Vendor Evaluation

T147C Definition for Subcriteria for Vendor Evaluation

T147D Texts for Subcriteria in Vendor Evaluation

T147E Definition of Weighting Keys by Main Criterion

Main table for Calculating the Scores

T147F Description of Weighting Keys in Vendor Evaluation

T147I Definition for Subcriteria for Main Criterion

T147K Vendor Evaluation: Assignment Percentages - Points Scores

Please check the Program in this there are the function modules lsted whcih are used for Score calculations

SAPMM06L - Module Pool: Vendor Evaluation

ML_VENDOR_MATERIAL_RATING

EVAL_SEMIAUTOMATIC_CRITERIA

EVAL_AUTOMATIC_CRITERIA_S013

EVAL_AUTO_INVOICE_VERIFICATION

EVAL_PRICELEVEL_CRITERIA

EVAL_PRICEHISTORY_CRITERIA

EVAL_SEMIAUTOMATIC_CRITERIA

EVAL_AUTOMATIC_CRITERIA_S013

EVAL_AUTO_INVOICE_VERIFICATION

EVAL_PRICELEVEL_CRITERIA

EVAL_PRICEHISTORY_CRITERIA

EVAL_PROTOCOLS

Additionals
S011 - PURCHIS: Purchasing Group Statistics
S012 - Purchasing
S013 - PURCHIS: Statistics for Vendor Evaluation
S031 - Statistics: Movements for current stocks
S032 - Statistics: Current Stock and Grouping Terms
SO33 - Statistics: Movements for Current Stock (Individual Records)
S034 - INVCO: Movements (Batches)
S035 - Statistics: Batch Stocks

Incredible joy

Incredible joy-Thestar.com.my

WHEN SAP consultant Mohd Nazrin Rizal was contacted for this interview three weeks ago, he sounded frazzled.
The truth is, the timing couldn’t be worse. After patiently taking our phone call, he calmly said,........

How to set a default GL Account for a particular Account Assignment in SAP?

The Issue
How to set a default GL Account for a particular Account Assignment in SAP? For example, If I were to perform Goods Issue to Cost Centre. Or when I am creating a Purchase Order with Account Assignment K.

The Solution
For cases like Goods Issue, the key here is the Movement Type and also transaction OBYC (Automatic Postings).
1) First go to OMJJ to view your movement type.
2) Select the movement type that you require to check e.g. 201 Goods Issue to Cost Centre.
3) Now double click on Account Grouping on the left panel.
4) Check the Acct modif against next to GBB. For this case, it should be VBR.
5) Now that you have the Acct modif, you can find/set the default GL Account in OBYC.
6) In OBYC, double click on GBB.
7) Under VBR general modification, set the default GL accounts that you require against the relevant Valuation Class. If you cannot find any VBR here, just click on Create new to create it.
8) To default a GL for items without valuation class, create a new VBR line while leaving the Valuation Class field empty.

For cases where you would like to default a GL account during PR/PO creation, you would need to look at a different area. We shall use Create PO for Account Assignment K items.
1) Go to SPRO --> MM --> Purchasing --> Account Assignment --> Maintain Account Assignment Category --> Double click on K - Cost Centre
2) From here, you can see the Acct Modification key (Should be VBR).
3) To set a default GL, you can follow the above steps in OBYC --> GBB.

SAP Invoice Verification error "Account Determination for entry 8000 KDM not possible"

The Issue

User is unable to complete an Invoice Verification process because SAP is showing error "Account Determination for entry 8000 KDM not possible". The error is also related to Foreign Currency.

The Solution

The issue above happened because the exchange rate during Goods Receipt, and the exchange rate during Invoice Verification is different. To solve this issue, there are 3 options that you may choose.
1) Select Fix exchange rate in Purchase Order. This has to be done prior to goods receipt.
2) Manually search for the exchange rate used during MIGO-Goods Receipt (refer to MIGO-Goods Receipt Posting Date), and then use it during MIRO-Invoice Receipt. You can find it in t-code S_BCE_68000174.
3) Set in t-code: OBYC -- > KDM a particular GL Account for Exchange rate variances.

When performing MRP Run in SAP, how to exclude certain Storage locations

The Issue

There are times where a certain storage location in a warehouse is to be excluded from MRP Planning. How do we achieve this?

The Solution

It is certainly possible in SAP. There are 2 steps to follow.
1) For materials that are already extended to the storage that you would like to exclude from MRP, go to Change Material in t-code MM02. Then select MRP 4 View. Here, put value 1 at field Sloc MRP Indicator.

2) For materials which are not created, the above setting can be done automatically in SAP. Go to T-code OMIR, set value 1 at the MRP Ind. column for the related storage locations. By doing this, future materials which are extended to the particular storages will automatically have a value 1 at field Sloc MRP Indicator in MRP 4 view.

If we perform deletion for valuation type under storage location level, will it affect valuation type in other storages in SAP?

The Issue

If we perform flagged for deletion for material at valuation type level under storage location level, will it affect valuation type in other storage locations?

The Solution

Although Valuation Type appears to be below Storage location level when performing Flag for deletion in T-code MM06, Valuation Type is actually at Plant level. Therefore, by deleting valuation type in 1 storage location in MM06, it will delete it at Plant level.

Difficulty in searching for materials in SAP

The Issue

In SAP, there are numerous ways of searching for a material. This is done by clicking on F4. It is possible to search by Material Type, Old Material Number, by description, Manufacturer Part number, etc. However, Users would like to search based on other Criteria.

The Solution

If SAP extensive searching method is not suitable, I would suggest using Material Classification. With Material Classification, you are able to classify each material by your own searching criterias. For example, you can add Colour, Size, Location, etc.
To do this, follow the steps below.
1) Create the characteristics that you require, e.g. Colour, Size, etc in T-code CT04.
2) Create Class with Class type 001.
3) Assign the characteristics that you created in Step 1 to Class in Step 2.
4) Extend Material Master in MM01 to add Classification View. If you cannot find classification view while extending, you will need to add it in configuration. Go to SPRO --> Logistics General --> Material Master --> Basic Settings --> Material Types --> Define Attributes of Material Type --> Select your material type and double click on it. Then highlight Classification view and save.
5) Go to Change Material, t-code MM02. Select Classification view, then, add the values that is related to that particular material. For example, For a red material, you can add the value "Red" in Colour Characteristics.

Thats it. You're done with Material Characteristics. Now to search by using these "Values", Use the same method as before by clicking on F4 at the Material field. Then choose Search by classification.

What does a SAP Consultant do?

This is a video that i found on Youtube. It features a person from IBM describing her SAP Experience.
Link: http://www.youtube.com/watch#!v=Ejh65pFGGVE&feature=related

SAP Blanket PO with agreement, when the valid to date has passed, why is the system still allowing to procees with Receiving/Service Entry Sheet?

The Issue

For certain materials/services, agreement blanket POs has been set with the vendor where the prices are fixed for a certain period.
However, once the period is over, the system is still allowing receiving/ service entry sheet process.

The Solution

Currently, the system is only treating this as a Warning, which means that even if the valid to has passed, users are still able to proceed with Service Entry Sheet or Goods Receipt.
It is possible to change it to Error Message where it wont be possible to proceed with Service Entry Sheet / Goods Receipt. This can be done in SPRO --> MM --> Purchasing --> Environment --> System Messages

Will materials with Xplant Mat Status Blocked/Obsolete still be considered during Stock Take in SAP?

The Issue

There are some materials which are blocked from Procurement or Set as Obsolete in Material Master. Will these materials be planned during Stock taking/Physical Inventory?

The Solution

Materials with statuses Blocked for Procurement or Obsolete will still be considered during Stock Take.
The only way to exclude a particular material from Stock Taking process is to Set Deletion Flag to it.

How to know if a PO has been sent to Supplier in SAP?

The Issue

How to know if a PO has been sent to the supplier (list of PO and their status/ which ones need to be processed)

The Solution

For this case, it is not possible to find from any SAP Standard Reports.
However, you can find it if you look through a particular table
Here's what you should do.
1) Go to t-code SE16N or SE11. Either one would do
2) Enter Table name NAST
3) Now at Processing Status (VSTAT) field, enter 1 if you would like to find POs that you have already outputted a message. OR enter 0 if you would like to find POs which you have not outputted a message yet.
4) Optional - You can enter Vendor code under Partner field (PARNR) to narrow down your POs
5) Optional - You can enter PO number under Object Key field (OBJKY). However you would need to include leading zeros if your Purchase Order numbering does not add up to 10 characters.

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1723257&messageID=9262023#9262023

How to know if a PR has been converted to PO in SAP?

The Issue

How to know if a PR has been converted into a PO (list of PR and their status/ which ones need to be processed)

The Solution

If you want to check the PR status, use transaction code ME5A and select processing status B and run the report. Processing Status B indicates that Purchase Order is created for the Purchase Requisition

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1723257&messageID=9262023#9262023

How to set Expiry date for a particular Batch in SAP?

The Issue

For one particular batch, in SAP the expiry date is different from the expiry date maintained in BOX. Now how to change the expiry date, could some one please tell me the Tcode in which I can set the expiry date.

The Solution

As you can see from the previous post, to edit the Expiry Date, do it in MSC2N.
Now to explain a little further, Standard SAP gets the Expiry date by using the following Formula:
Production Date + Total Shelf life days in Material Master (Plant Data Stor. 1 view).
So maybe you can look into this to prevent future errors in Expiry Date.

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1723795&messageID=9262025#9262025

Split Valuation values issue in SAP

The Issue

If i am having split valuated material for value 10, 20 & 30.Should all have MAP or 2 materials can have S & other V.Can i upload the material with MAP or S with value zero in MMR

The Solution

For your information, if you are using Split Valuation, then you can only Use Moving Average Price. This is the requirement for split valuation.
So for each of the split valuation, you set them as MAP, then input the individual values separately.
You can upload the split valuated material with value of 0, or with the real value, e.g. 10, 20, 30.
I would suggest you upload with the real value so that when you raise a Purchase Requisition, system will pick this amount as valuation price.

Just to be clear step by step. We assume that you are creating a fresh new material Ok.
1) Create Material Master
2) At the Accounting 1 view, enter Valuation Category.
3) Leave the Moving Average Price field EMPTY
4) Save
5) Create Material again, this time update view Accounting 1.
6) When the organizational view appears, put in the first Valuation Type
7) Update field MAP with necessary value
8) Save
9) Repeat step 5 - 8

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1720247&messageID=9248733#9248733

Unit of Measure conversion issue in SAP

The Issue
Currently,
Material master is setup as a BUOM in Lbs.
Purchase order is created using BUOM
Vendor invoice is billed in Kg's.
Is it possible to enter a purchase order in a different unit of measure from the BUOM.
This change is required because, we buy stuff in lbs and pay to the customer in Kgs, so wanted to have the UOM in Kgs from the purchase order to the end of the transaction.

The Solution

Let me try to summarize and add a little information about UOms for you.

1) UOm for a particular material should be maintained by your own Stock keeping Unit, and not based on what vendor's or customer's own UOm.
2) In Material Master, you can set Order Unit. This means that for every vendor, the Order unit is XX. Alternatively, you can leave this field empty and set the Order unit in Info Record. I'm saying this because, maybe, the Order unit is only relevant for a particular vendor and not others.
3) In Material Master, you can also find Unit of Issue. Meaning conversion for Production Purposes.
4) And lastly, UOm for Sales. This can be done from Alternative unit of measure in Material Master.

So to sum up, you can maintain your Material A in EA (Each), Order it from Vendor XYZ in CAR (Cartons), Issue it in BOX (Boxes), and sell it in DZ (Dozen). Just an Example....

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1661793&messageID=8994862#8994862

Release Procedure for Contract and PO in SAP, does it clash?

The Issue

I am having release procedures(with clasification) in contract and Purchase orders.(Both are against Document types only). First i maintained PO's release procedure . For PO i maintained table - field. CEKKO- BSART.
For contract also same table and fields. How can i maintain release procedure for contracts with out any effecting PO's release procedure.

The Solution
You can use the same Release Group because they share the same release Table, CEKKO-BSART for all Purchasing Documents. These includes Purchase Orders, Contracts, and other Agreements.
However, it will not clash because PO and Contract have different document types.
For example, in PO document type will be NB, FO. Whereas for Contract it will be WK,MK.
So in SPRO under release strategy, you will have strategies for the NB and FO document types for Purchase Order. As for Contracts, you will have your own set of strategies for MK, WK, with the same Release Group.

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1669433&messageID=9022137#9022137

How to ensure No goods movement at Plant level in SAP?

The Issue

Is there configuration at the Plant Level to specify "No Goods Movement Allowed"? I want to stop the user's from any type of goods movement but at the Plant level. I thought I had seen this config but now can't seem to find it or maybe it doesn't exist??

The Solution

You can do either of the following:
1) Control users access by limiting his/her authorization (In transaction PFCG).
2) For each materials under plant (Set a blocking status 01/02/03 under the Xplant Mat status field in Material Master).
3) Physical Inventory document for each storage location under the particular plant (highly unlikely).

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1656676&messageID=8967654#8967654

What is Reconciliation Account

The Issue

What is significance of reconciliation account? Why it is important? and how does it helps MM/ FI person?

The Solution

I am not a finance user, but let me try to explain it in a language where both of us can understand.

You know there are many Vendor codes in the Vendor Master right?
So now, if you would like to include the balances of each vendor to the Balance sheet, what do you do?
Do you include all these vendor "codes" into the balance sheet?

No you cant do that, it will make your Balance Sheet have 100 pages.
This is why we have a Recon Account.. where it shows the balances for each vendor according to the Vendor Account Group. These balances according to account group will then be brought into the Balance Sheet.

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1650592&messageID=8938481#8938481

MD01 re-planning does not seem to work in SAP

The Issue

I have run MD01 for a specific scope of planning and it has planned the materials sucessfully. The problem is that if I try to re-run MD01 again (planning mode = 3), it doesn't plan any material. How should I solve this problem?

The Solution

Planning mode is not the solution.
You need to change the Processing Key from NETCH to NEUPL.
If you leave it at NETCH, this means that, whatever that have been planned before & changes were made, it will still not regenerate the MRP planning.
So to Re-plan, you need to use NEUPL.

So your settings should be
NEUPL
3 Planned Orders (If you want PRs then change it to 1)
3 Schedule Lines
1 MRP List
3 Delete and recreate planning Data

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1667016&messageID=9011964#9011964

How to Adopt PR price into PO in SAP?

The Issue

We are facing a problem with PO price not getting copied from PR, our Client dont want to maintain the Info record as material they are using is generic (general, not specific or special), so is there any way or configuration setting so the PR price get copied into PO

The Solution

Please follow the steps below.
1) SPRO --> MM --> Purchasing --> Authorization Management --> Define Function Authorizations for Buyers
2) Maintain 01 function authorization or copy it to create a new one
3) Under General Parameters, Check Adopt PO Price.
4) If you would like PO to have reference objects as mandatory, uncheck W/o Reference Optional
5) Go to each buyers ID by SU01 --> Parameter. Enter EFB and enter the 2 codes that you defined in Step 2.
6) Log out then log back in

Now with that ID, when you create PR, under valuation, you have a new drop down button asking whether you would like to adopt the price in PO.

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1656114&messageID=8963072#8963072

How to re-trigger Release Strategy which has already been released in SAP?

The Issue

I want to enable a functionality to release the PR after changing the existing one(Which is already released). Please let me know the configs to be done for enabling this.

The Solution

Regarding the issue of re-releasing a PR/PO after it has been released and then subsequently changed, please follow the steps below.
1) SPRO --> MM --> Purchasing --> PR --> Release Procedure --> Procedure with classification --> Set up procedure with classification --> Release Indicator
2) Double click on the indicator that you use for the Release (Most of the time, it would be 2 - RFQ/purchase order)
3) Set the changeabil to 4 (Changeable, new release in case of new release strat or val change)

With the setting above, it will re-trigger the release strategy. It can be retriggering the same Release Strategy or a different one, depending on the changes that you have made to PR.

However, if the change is a decrease in Value, it will not re-trigger the release. Only an increase in val change will it trigger a new release strategy.
Currently, there is no way to re-trigger release strategy when there is a change in value (decrease).

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1657203&messageID=8967611#8967611

Problem with Material Serial Number in Goods Receipt in SAP

The Issue

While creating the Material Master we could not activate Serial Number. We created the Purchase Order & done the Goods Receipt for the Material without Serial Number.
Later we activated the Serial Number profile for the Material and did the Good Receipt with Serial Numbers.

Now we want to reverse the first document where Material was received without serial number, but the system does not allow us to do so.

The displays the following message:
Maintain serial numbers for total quantity

We just tried to de-activate the Serial Number profile, but the system does not allow us to do that also.

The displays the following message:
Serial numbers already assigned to this material

We need to reduce the stock.

Please advice what to do?

The Solution

Method 1
1) Since you cannot remove the serial profile, you will have to create a Dummy profile e.g. ZMZZ (up to you to come up with the 4 alphanumerics).
2) In this profile, set the StkCk as Blank, procedure MMSL set it to 01 (SerUsage), 01(EqReq)
3) Once you have done the above, you can now do the necessary Inventory Movements e.g. transfer posting, GR,GI..
4) When you have you have removed the previous quantities without serial numbers, insert the proper serial profile back to the material master.
5) Perform receiving to get those quantity back in SAP while inputting new serial numbers.

Method 2
1) Instead of removing the previous quantities without serial numbers, you can try this.
2) Edit the current serial profile, set the StkCk as Blank
3) Create serial numbers according to the quantities that you do not have serial number. E.g. if you have 3 quantity without serial number, so you should create 3 serial numbers for this material.
4) Perform Transfer posting from MIGO_TR for the material from one storage location to another (you can choose to repeat the same storage location also). Input the serial numbers here. Once all is completed in this screen, check and Post.
5) All your quantities now will be serialized with status ESTO (within storage locations).

Source: http://forums.sdn.sap.com/thread.jspa?threadID=1655349&messageID=8961696#8961696