How To Fix W5079 - Purchase order & could not be saved

SAP Error Message - Details

• Message type: E = Error

• Message class: W5 - Messages for MM-WEB Applications and BAPIs

• Message number: 079

• Message text: Purchase order & could not be saved

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message W5079 - Purchase order & could not be saved ?

  SAP Error Message:
  
  W5079 - Purchase order & could not be saved
  
  Cause:
  The warning message W5079 typically occurs when there is an issue preventing the purchase order (PO) from being saved successfully. The ampersand (&) in the message is a placeholder for the PO number.
  Common causes include:
  
  Incomplete or incorrect data in the PO header or item details.
  Missing mandatory fields required for saving the PO.
  Authorization issues where the user does not have sufficient rights to save or change the PO.
  Locking conflicts if the PO is being edited simultaneously by another user or process.
  System or configuration errors such as missing or incorrect settings in the purchasing document types or related customizing.
  Inconsistencies in related master data, such as vendor master, material master, or info records.
  Validation or substitution rules triggered during save that prevent the PO from being saved.
  
  
  Solution:
  To resolve the W5079 error, follow these steps:
  
  
  Check the detailed error log:
  
  After the warning, SAP usually provides additional messages or error details.
  Use transaction ME23N or ME22N to review the PO and check for any error messages or missing data.
  
  
  
  Verify mandatory fields:
  
  Ensure all required fields in the PO header and item level are filled correctly.
  Common mandatory fields include vendor, purchasing organization, purchasing group, material number, quantity, delivery date, and price.
  
  
  
  Check authorizations:
  
  Confirm that the user has the necessary authorizations to create or change purchase orders.
  Use transaction SU53 immediately after the error to check for authorization failures.
  
  
  
  Check for locks:
  
  Use transaction SM12 to check if the PO is locked by another user or process.
  If locked, coordinate with the user or release the lock if appropriate.
  
  
  
  Review validation and substitution rules:
  
  Check if any validation or substitution rules are active that might block saving the PO.
  Use transaction GGB0 (Validation) and GGB1 (Substitution) to review these rules.
  
  
  
  Check master data consistency:
  
  Verify vendor master data (transaction XK03), material master data (transaction MM03), and info records (transaction ME13) for correctness.
  
  
  
  Review customizing settings:
  
  Check the configuration for purchasing document types (transaction OMWN) and related settings.
  Ensure that the document type allows the intended operation.
  
  
  
  Debug or check system logs:
  
  If the issue persists, check system logs (transaction SM21) or perform debugging with the help of an ABAP developer.
  
  
  
  
  Related Information:
  
  
  Transaction codes:
  
  ME21N – Create Purchase Order
  ME22N – Change Purchase Order
  ME23N – Display Purchase Order
  SU53 – Authorization Check
  SM12 – Lock Entries
  GGB0 / GGB1 – Validation and Substitution
  OMWS / OMWN – Purchasing Document Type Customizing
  
  
  
  SAP Notes:
  
  Check SAP Service Marketplace or SAP ONE Support Launchpad for notes related to message W5079 or PO saving issues.
  
  
  
  User roles and authorizations:
  
  Ensure users have roles with appropriate authorization objects like M_BEST_BSA (Purchasing Document Type), M_BEST_EKG (Purchasing Group), and M_BEST_WRK (Plant).
  
  
  
  
  Summary:
  W5079 Purchase order & could not be saved is a warning indicating the PO could not be saved due to data, authorization, locking, or configuration issues. Investigate detailed error messages, verify data completeness, check authorizations and locks, and review validation/substitution rules to resolve the issue.