Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix WG335 - PO split not possible. Split module ends with error &1


SAP Error Message - Details

  • Message type: E = Error

  • Message class: WG - Messages for store order and investment buy

  • Message number: 335

  • Message text: PO split not possible. Split module ends with error &1

  • Show details Hide details


  • 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 WG335 - PO split not possible. Split module ends with error &1 ?

    Certainly! Here's a detailed explanation for the SAP error message:


    SAP Error Message:

    WG335 - PO split not possible. Split module ends with error &1


    Cause:

    This error occurs during the processing of a Purchase Order (PO) when the system tries to split the PO (for example, during release strategy processing or workflow) but fails due to an error in the split module. The placeholder &1 contains the specific error message or code that caused the split to fail.

    Common causes include:

    • Custom split logic error: If a custom split module (user-exit or BAdI) is implemented, it might have a bug or incorrect logic causing the split to fail.
    • Inconsistent PO data: The PO might have inconsistent or incomplete data that prevents the system from splitting it correctly.
    • Configuration issues: Incorrect or missing configuration in the release strategy or split criteria.
    • Authorization or system errors: Missing authorizations or system errors during the split process.

    Solution:

    1. Check the detailed error message:
      Look at the actual error text in place of &1 to understand the specific reason for the failure.

    2. Review custom split logic:

      • If a custom split module is used (e.g., via user-exit EXIT_SAPLMEKO_001 or BAdI ME_PROCESS_PO_CUST), debug or review the code to identify why it ends with an error.
      • Correct any logical errors or handle exceptions properly.
    3. Verify PO data consistency:

      • Check the PO for missing or inconsistent data fields.
      • Ensure all mandatory fields for splitting are correctly filled.
    4. Check configuration:

      • Review the release strategy and splitting criteria in SPRO.
      • Ensure that the splitting rules are correctly defined and applicable to the PO.
    5. Debug the split process:

      • Use transaction SE37 to test function modules related to PO splitting.
      • Use debugging tools to trace the split module execution.
    6. Check authorizations:

      • Ensure the user has the necessary authorizations to perform PO splitting.
    7. SAP Notes and Support:

      • Search for SAP Notes related to WG335 and the specific error message in &1.
      • Apply any relevant patches or corrections.

    Related Information:

    • Transaction Codes:

      • ME21N / ME22N (PO creation/change)
      • ME28 (Release Purchase Order)
      • SE37 (Function Module testing)
      • SE80 / SE38 (Debugging user-exits or BAdIs)
    • User-Exits / BAdIs:

      • EXIT_SAPLMEKO_001 (User-exit for PO processing)
      • ME_PROCESS_PO_CUST (BAdI for PO processing)
    • SAP Notes:

      • Check SAP Support Portal for notes related to WG335 and PO splitting errors.

    If you provide the exact error message in &1, I can help you further narrow down the cause and solution.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author