Purchasing Errors in SAP
1) SAP Error: ME083 - Purchase Order already exists
T-Code: ME21N
Solution: Check for duplicate POs in ME23N and verify
the document numbers.
The SAP error ME083 "Purchase Order already exists"
means you're trying to create a purchase order (PO) with a number that the
system already has assigned to another PO. This typically happens in one of
these scenarios:
Ø
Number Range Conflict: The number you're
entering (or the system is trying to automatically assign) is already in use.
Ø
Accidental Duplicate Entry: You might be
accidentally trying to recreate a PO that already exists.
2) SAP Error: ME005 - Account assignment is missing.
T-Code: ME21N
Solution: Enter the correct account assignment (cost
center, internal order).
Why it Occurs:
Ø
Material Master Data: The material master
record for the item you're ordering might be configured to require account
assignment. Check the material master's accounting views.
Ø
Configuration Settings: Certain system
configurations might mandate account assignment for specific transaction types
or material groups.
Ø
Automatic Account Determination Failure: Even
with automatic account determination configured, sometimes the system can't
derive the necessary account assignment information.
How to Fix It:
Identify the Required Account Assignment Category: The most
important step is to figure out what kind of account assignment is needed.
Common categories include:
Cost Center (K): Assign the cost to a specific cost center.
Asset (A): Capitalize the purchase as an asset.
Order (F): Assign the cost to an internal order.
Project (P): Assign the cost to a project.
General Ledger Account (GL): Directly assign the cost to a G/L
account.
Enter the Account Assignment: Once you know the category, enter
the required information in the "Account Assignment" tab of the PO
item details. This usually involves:
Selecting the account assignment category (e.g., K, A, F, P, GL).
Entering the specific account assignment object (e.g., the cost
center number, asset number, order number, project number, or G/L account).
Ø
Check Material Master Data: Review the
material master record (transaction MM03) to see if account assignment is
mandatory for this material. If so, and you don't want it to be, talk to your
MM config team or the business leads who own the material.
Ø
Review Configuration (for administrators): If
the issue occurs frequently, your system configuration might be too
restrictive. Consult with your SAP consultant to review the settings related to
automatic account determination and account assignment categories.
Ø
Automatic Account Determination Issues: If you
believe the account assignment should be determined automatically, investigate
why it's failing. Check the configuration in OBYC (Automatic Account
Determination).
3) SAP Error: ME013 - Purchasing group not maintained.
T-Code: ME21N
Solution: Maintain the purchasing group in SPRO →
Materials Management → Purchasing → Maintain Purchasing Groups.
Here's what you can do:
1. Check the
Material Master Data: The purchasing group is often assigned at the material
level. Go to transaction MM03 (display material) and check if a purchasing
group is assigned to the material. If not, you might need to add it using
transaction MM02 (change material).
2. Check the Vendor
Master Data: Sometimes, the purchasing group can be assigned at the vendor
level. Use transaction XK03 (display vendor) to check if the vendor has a
default purchasing group assigned.
3. Check your User
Settings: Your user profile might not have a default purchasing group assigned.
Check with your SAP administrator to see if this is the case. They can use
transaction SU01 (user maintenance) to update your profile.
4. Review the
Transaction: Carefully review the transaction you're trying to perform (e.g.,
creating a purchase order, purchase requisition, etc.). Make sure you've
entered all the required information, including the purchasing group if it
needs to be specified directly.
5. Check for
Customization: Depending on how your SAP system is configured, there might be
specific settings related to purchasing groups. If you've tried the above steps
and are still encountering the error, you might need to contact your SAP
support team to check for any custom configurations causing the issue.
4) SAP Error: ME083 - Vendor blocked.
T-Code: XK05/BP
Solution: Unblock the vendor in the vendor master
record.
The SAP error "ME083 - Vendor blocked" indicates that
the vendor you're trying to use in a transaction (like creating a purchase
order) is currently blocked in the system. This block prevents any further
transactions with that specific vendor.
Here's a breakdown of how to address this and what it might mean:
1. Determine the Type of Block:
There are different types of blocks in SAP. The most common are:
• Purchasing
Block: This specifically prevents purchasing activities with the vendor.
• Payment Block:
This prevents payments from being made to the vendor.
• General Block:
This blocks all transactions with the vendor.
You'll need to determine the specific block type to understand the
reason and resolve it.
2. Check the Vendor Master Data:
Use transaction XK03 (Display Vendor) to view the vendor's master
data. Look for any indicators of a block. Often, there will be a clear visual
cue (like a lock icon or a status message) indicating the block and its reason.
Check the following tabs:
• General Data:
Look for any status indicators related to blocking.
• Purchasing Data:
Specifically check for a purchasing block.
• Company Code
Data: Check for any payment blocks or other relevant blocks.
3. Identify the Reason for the Block:
Ø
Once you've found the block, try to understand
why the vendor was blocked. Common reasons include:
Ø
Poor performance: Consistent late deliveries,
quality issues, etc.
Ø
Financial issues: Bankruptcy, outstanding
debts, etc.
Ø
Compliance issues: Violations of regulations
or internal policies.
Ø
Temporary hold: Perhaps for an audit or
review.
5) SAP Error: ME459 - Delivery date is in the past.
T-Code: ME21N
Solution: Change the delivery date to a future date in
the PO.
The SAP error "ME459 - Delivery date is in the past" is
straightforward: the delivery date you've entered for a purchase order (or
other related document) is earlier than the current date. SAP doesn't allow
this in most standard configurations because it doesn't logically make sense to
request a delivery in the past.
Here's how to fix it:
1. Correct the
Delivery Date: The most obvious solution is to update the delivery date to a
future date. In the relevant transaction (likely ME21N for creating a purchase
order, ME22N for changing a purchase order, or similar), locate the delivery
date field and enter a valid future date.
2. Check Scheduling
Agreements (if applicable): If you're working with a scheduling agreement
(transaction ME31L to create, ME32L to change), the delivery dates are defined
within the schedule lines. You'll need to adjust the dates within the
scheduling agreement itself.
3. Consider GR
Processing Date (if applicable): In some specific scenarios, you might be
trying to post a Goods Receipt (GR) for a delivery that occurred in the past.
In this case, you need to ensure the GR processing date (the date you're
recording the goods receipt) is also in the past and matches the actual
delivery date.
4. Check for
Relevant User Exits or Customizations: There might be specific configurations
or user exits in your system that influence how delivery dates are handled. If
you've corrected the date and are still encountering the error, contact your
SAP support team to check for any customizations that might be causing the
issue. They might be able to adjust the system's behavior or provide a
workaround.
5. Review Business
Process: Sometimes, this error highlights a bigger issue in the procurement
process. If you're frequently encountering this error, it might be worth
reviewing your internal processes to identify why past delivery dates are being
entered in the first place.
Example (Purchase Order):
If you're creating a purchase order in ME21N, you would:
• Go to the
"Delivery/Invoice" tab.
• Locate the
"Delivery Date" field.
• Enter a valid
future date.
6) SAP Error: ME545 - No plant assigned to company code
T-Code: OX18
Solution:
Assign the plant to the company code in configuration.
The SAP error "ME545 - No plant assigned to company
code" arises when you're trying to perform a purchasing-related action,
and the system cannot find a plant assigned to the company code you're using.
This is a common configuration issue.
Here's how to resolve it, along with a deeper explanation:
Understanding the Relationship:
In SAP, company codes represent legal entities, while plants
represent physical locations where materials are stored, manufactured, or
distributed. For purchasing processes to work correctly, a plant must be
assigned to a company code. This assignment links purchasing activities to a
specific physical location within the legal entity.
Resolution Steps:
1. Check Company
Code and Plant Assignment:
Use transaction OX18 (Assign Plant to Company Code) to verify if
the plant is assigned to the company code you're using. If the assignment is
missing, you can create it directly within this transaction. You'll need the
appropriate authorization to make changes in OX18.
2. Check Material
Master Data (if applicable):
If you're working with a specific material, the plant might need
to be assigned in the material master data. Use transaction MM03 (Display
Material) to view the material master. In the "MRP 1" view, check if
a plant is assigned. If not, you may need to add it using transaction MM02
(Change Material).
3. Check Vendor
Master Data (if applicable):
In some cases, the vendor master data might influence plant
determination. Use transaction XK03 (Display Vendor) to view the vendor's data.
While less common than material master data, certain vendor-specific settings
could be contributing to the issue.
4. Check Purchasing
Organization and Plant Assignment (if applicable):
Purchasing organizations are responsible for procuring materials.
The plant needs to be assigned to the purchasing organization. Transaction OX17
(Assign Purchasing Organization to Plant) allows you to view and maintain these
assignments.
5. Review User
Settings:
While less likely, your user profile might have incorrect default
settings related to plant and company code. Contact your SAP administrator to
check your user settings in transaction SU01 (User Maintenance).
6. Consult with SAP
Support or Functional Consultant:
If you've checked the above and the issue persists, contact your
internal SAP support team or a functional consultant. They can analyze your
system configuration in detail and identify any other underlying problems or
custom settings that might be contributing to the error.
Example in OX18:
In OX18, you would enter the company code and the plant you want
to assign. Then, select the appropriate valuation area (if applicable) and save
the changes.
7) SAP Error: MEPO012 - Material is flagged for deletion
T-Code: MM06
Solution:
Remove the deletion flag for the material in MM06.
The SAP error "MEPO012 - Material is flagged for
deletion" indicates that the material you're attempting to use in a
purchasing document (like a purchase order or purchase requisition) has been
marked for deletion in the system. This means someone has initiated the process
of removing this material from the active database.
Here's how to understand and address this error:
Understanding Material Deletion Flags:
In SAP, deleting a material is not always immediate. Often, it's a
multi-step process involving different deletion flags or indicators. This is to
prevent accidental deletions and to allow for archiving or other procedures
before the material is completely removed.
Resolution Steps:
1. Check Material
Status:
Use transaction MM03 (Display Material) to view the material's
status. Look for deletion flags or indicators. The specific fields and
terminology might vary slightly depending on your SAP system's configuration,
but common indicators include:
Ø
Deletion Flag: Check if the material has a
deletion flag set at the client level, company code level, or sales
organization level.
Ø
Deletion Indicator: Similar to a deletion
flag, this indicator signifies that the material is scheduled for deletion.
Ø
Material Status: Look for a status like
"Marked for Deletion" or similar.
2. Determine the
Reason for Deletion:
If the material is flagged for deletion, find out why. Common
reasons include:
Ø
Material obsolete: The material is no longer
used or produced.
Ø
Material replaced: A new material has replaced
the old one.
Ø
Data cleanup: Part of a larger data cleanup
effort.
Understanding the reason can help you determine the appropriate
course of action.
3. Contact the
Relevant Party:
Talk to the person or department responsible for marking the
material for deletion. This could be someone in material management,
purchasing, or another related area. They can provide more information about
the deletion process and whether it can be reversed.
4. Consider
Alternatives:
If the material is indeed obsolete or replaced, you'll need to use
the appropriate replacement material in your purchasing document.
5. Undelete the
Material (if appropriate):
If the material was marked for deletion in error, and if it's
still possible, you might be able to undelete it. This typically involves
removing the deletion flags or indicators. However, you should only do this if
you are authorized and understand the implications. Incorrectly undeleting a
material can cause data inconsistencies.
8) SAP Error: MEPO151 - Net price is zero
T-Code: ME21N
Solution:
Enter the correct price in the PO.
The SAP error "MEPO151 - Net price is zero" occurs when
you're creating or changing a purchasing document (like a purchase order) and
the system detects that the net price for an item is zero. This is usually not
allowed, as it indicates a missing or incorrect price.
Here's how to troubleshoot and resolve this:
1. Check the Info Record:
• Transaction ME11
(Create Info Record), ME12 (Change Info Record), ME13 (Display Info Record):
Info records store purchasing-related information for a specific material and
vendor combination. The net price is often maintained here. Verify if an info
record exists and if it contains a valid net price. If not, create or update
the info record with the correct price.
2. Check the Conditions in the Purchase Order:
• Transaction
ME21N (Create Purchase Order), ME22N (Change Purchase Order), ME23N (Display
Purchase Order): Go to the "Conditions" tab in the item details.
Check if the net price condition is present and has a value other than zero. If
the net price is missing or zero, you can manually enter it or let the system
determine it based on existing pricing conditions (like info records,
contracts, or agreements).
3. Check the Source List (if applicable):
• Transaction ME01
(Create Source List), ME02 (Change Source List), ME03 (Display Source List):
Source lists specify allowed vendors for a material within a given plant. They
can also contain pricing information. Check if a source list exists and if it
has a valid price. If not, create or update the source list.
4. Check for Automatic Pricing:
• Customization:
Your SAP system might be configured to automatically determine prices based on
various factors. If the automatic pricing procedure is not working correctly,
it could result in a zero net price. Consult with your SAP support team to
check the pricing procedure configuration.
5. Check for User Exits or Customizations:
• Customization:
Custom code (user exits, enhancements) could interfere with price
determination. Contact your SAP support or development team to investigate if
custom code is causing the issue.
6. Check if the Material is Free of Charge:
• Material Master:
While less common, some materials might be genuinely free of charge. If this is
the case, there might be specific settings in the material master data
(transaction MM03 - Display Material) to indicate this. Check with your
material management team to confirm if the material should indeed have a zero
price.
Example (Changing a Purchase Order - ME22N):
1. Go to the item
details.
2. Navigate to the
"Conditions" tab.
3. Locate the net
price condition (usually labeled with a condition type like PB00).
4. Enter the
correct net price.
9. SAP Error: MEPO017 - Tax code is missing
T-Code: ME21N
Solution:
Specify the tax code in the invoice tab during PO creation.
The SAP error "MEPO017 - Tax code is missing" indicates
that a required tax code is missing from an item in a purchasing document, such
as a purchase order. This prevents the system from correctly calculating taxes.
Here are several ways to resolve this issue:
1. Manually Enter the Tax Code:
• In the Purchase
Order (ME21N/ME22N/ME23N): The simplest solution is to manually enter the
correct tax code in the item details. Go to the "Conditions" tab and
find the tax code field. Enter the appropriate code.
2. Check the Info Record:
• (ME11/ME12/ME13):
Info records often contain default tax codes. If an info record exists for the
material/vendor combination, check if a tax code is maintained there. If not,
add the correct tax code to the info record. This will automatically populate the
tax code in future purchase orders.
3. Check the Material Master Data:
• (MM01/MM02/MM03):
In some cases, the tax code can be determined from the material master data.
Check the "Accounting 1" view to see if a tax classification or other
tax-relevant information is maintained.
4. Check the Vendor Master Data:
• (XK01/XK02/XK03):
Though less common, vendor master data can also influence tax code
determination. Review the vendor master record for any tax-related settings.
5. Check the Country Settings:
• (Customization):
Tax codes are often based on country-specific regulations. Verify that the
correct country is assigned to the vendor, plant, and company code.
6. Check Automatic Tax Code Determination:
• (Customization):
Your SAP system might have automatic tax determination configured. This
automatically calculates the tax code based on various factors. If the
automatic procedure isn't working correctly, it might result in a missing tax
code. Consult your SAP support team to check the configuration.
7. Check for User Exits or Customizations:
• (Customization):
Custom code could be interfering with tax code determination. Contact your SAP
development or support team to investigate.
Example (Adding Tax Code in a Purchase Order - ME22N):
1. Go to the item
details in the purchase order.
2. Navigate to the
"Conditions" tab.
3. Find the
condition type for the tax code (it often starts with "MW"). If it's
missing, add a new condition.
4. Enter the
correct tax code.
10.SAP Error: MEPO074 - Source of supply not found.
T-Code: ME57
Solution: Assign a valid
source of supply (vendor, contract) to the purchase requisition.
The SAP error "MEPO074 - Source of supply not found"
means the system can't find a valid source of supply for the material you're
trying to purchase in a purchase order or other purchasing document. This
usually relates to missing or incomplete configuration in areas like source
lists, quota arrangements, or contracts.
Here's how to resolve this:
1. Check the Source List:
• (ME01/ME02/ME03):
The most common solution is to create or update a source list. A source list
specifies approved vendors for a material within a given plant and validity
period. If no source list exists, create one (ME01) specifying the vendor,
validity period, and other relevant information. If a source list exists, make
sure it's valid for the current date and plant.
2. Check Quota Arrangements:
• (MEQ1/MEQ2/MEQ3):
Quota arrangements distribute purchasing quantities among different vendors. If
a quota arrangement exists, ensure that it has valid entries for the material,
plant, and vendor. Also, check if the quota has been exhausted.
3. Check Contracts and Scheduling Agreements:
• Contracts
(ME31K/ME32K/ME33K): Contracts establish longer-term agreements with vendors.
• Scheduling
Agreements (ME31L/ME32L/ME33L): These define delivery schedules for materials
from specific vendors.
If you're supposed to be using a contract or scheduling agreement,
make sure it's valid and has sufficient quantities or schedule lines available.
4. Check Material Master Data:
• (MM01/MM02/MM03):
While less likely, check the "Purchasing" view in the material master
data. Make sure the procurement type is set correctly (e.g., external
procurement, internal procurement).
5. Check Vendor Master Data:
• (XK01/XK02/XK03):
Ensure the vendor you're trying to use is approved for purchasing and that
their master data is complete.
6. Check Plant and Storage Location Settings:
• (Customization):
Verify that the plant and storage location are correctly configured and
assigned to each other.
7. Check for User Exits or Customizations:
• (Customization):
Custom code might interfere with source determination. Consult your SAP support
or development team.
Example (Creating a Source List - ME01):
1. Enter the
material number and plant.
2. Add a new entry
specifying the vendor, validity dates, and purchasing organization.
