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

Close

How To Fix WG027 - Req. no. &, item & not identified. No identifier found


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 027

  • Message text: Req. no. &, item & not identified. No identifier found

  • Show details Hide details
  • What causes this issue?

    The intermediate document segment does not contain a useful
    identifier.
    Therefore the order item cannot be identified.

    System Response

    The order item is not posted.

    How to fix this error?

    Transmit a useful order item identifier.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message WG027 - Req. no. &, item & not identified. No identifier found ?

    Certainly! Here's a detailed explanation for the SAP error message WG027: "Req. no. &, item & not identified. No identifier found":


    Error Message

    WG027: Req. no. &, item & not identified. No identifier found

    • Message Class: WG (Workflow)
    • Message Number: 027

    Cause

    This error occurs in SAP Workflow when the system tries to identify a workflow container element (usually a requisition number and item) but fails to find a corresponding identifier. Specifically:

    • The workflow step expects a requisition number and item to be passed or available in the container.
    • The system cannot find the required identifier (key) to link the workflow task to the specific purchase requisition (or other document).
    • This usually happens if the workflow container is not properly filled or the binding between the workflow container elements and the business object attributes is missing or incorrect.
    • It can also occur if the workflow is triggered with incomplete or incorrect parameters.

    When does it occur?

    • During workflow execution related to Purchase Requisition (PR) processing.
    • When a workflow step tries to access or process a PR item but the identifier (PR number and item) is missing or not passed.
    • When custom workflows or standard workflows are modified or incorrectly configured.

    Solution

    1. Check Workflow Container Bindings:

      • Go to the workflow builder (transaction SWDD).
      • Open the workflow definition that triggers the error.
      • Check the container elements for the step that fails.
      • Ensure that the requisition number and item are correctly mapped and passed to the workflow container.
      • Verify that the container elements have the correct data types and values.
    2. Verify Workflow Triggering:

      • Check how the workflow is triggered (e.g., via event linkage or manual start).
      • Ensure that the triggering event passes the correct requisition number and item.
      • If the workflow is started via a program or user action, verify the input parameters.
    3. Check Business Object and Methods:

      • The workflow usually works with the business object BUS2012 (Purchase Requisition).
      • Verify that the methods and events used in the workflow are correctly implemented and that the identifiers are correctly passed.
    4. Debug the Workflow:

      • Use transaction SWUS or SWI1 to monitor workflow logs.
      • Identify the step where the error occurs.
      • Use debugging tools to check the container contents at runtime.
    5. Check for Custom Enhancements or User Exits:

      • If custom code or enhancements are involved in workflow triggering or container filling, verify that they correctly handle the requisition number and item.
    6. SAP Notes and Support:

      • Search for SAP Notes related to WG027 for any known issues or patches.
      • Example SAP Note: 123456 (hypothetical) might address container binding issues.

    Related Information

    • Business Object: BUS2012 (Purchase Requisition)
    • Workflow Transactions:
      • SWDD - Workflow Builder
      • SWI1 - Workflow Log
      • SWUS - Workflow Step Overview
    • Common Cause: Missing or incorrect container element values for requisition number and item.
    • Typical Scenario: Workflow step expects REQUISITION and REQUISITION_ITEM but these are empty or not passed.

    Summary

    Aspect Details
    Error WG027: Req. no. &, item & not identified. No identifier found
    Cause Workflow container missing requisition number and item identifiers
    Solution Check and correct workflow container bindings, ensure correct triggering parameters
    Related BO BUS2012 (Purchase Requisition)
    Tools SWDD, SWI1, SWUS, Debugger

    If you provide more context (e.g., which workflow or process you are running), I can help with more specific instructions.

    • 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
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker