How To Fix VG217 - Order could not be determined using BSTNK & VKORG & customer &

SAP Error Message - Details

• Message type: E = Error

• Message class: VG - EDI Messages in SD

• Message number: 217

• Message text: Order could not be determined using BSTNK & VKORG & customer &

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 VG217 - Order could not be determined using BSTNK & VKORG & customer & ?

  SAP Error Message:
  
  VG217 - Order could not be determined using BSTNK & VKORG & customer &
  
  Meaning of the Error
  This error occurs in SAP Sales and Distribution (SD) module, typically during order processing or delivery creation, when the system tries to find a preceding sales document (like a sales order or contract) based on certain key fields but fails.
  The message indicates that the system attempted to determine the sales order using the following combination of fields:
  
  BSTNK: Customer Purchase Order Number (PO Number)
  VKORG: Sales Organization
  Customer: Sold-to party or customer number
  
  But no matching order was found.
  
  Cause of the Error
  
  
  No Sales Order Exists with the Given PO Number (BSTNK):
  
  The customer PO number entered does not exist in any sales order for the specified sales organization and customer.
  
  
  Mismatch in Sales Organization (VKORG):
  
  The sales organization entered does not match the sales organization in the sales order with the given PO number.
  
  
  Customer Number Mismatch:
  
  The customer number used does not correspond to the customer in the sales order with the given PO number.
  
  
  Incorrect or Missing Data Entry:
  
  The PO number, sales organization, or customer number might be incorrectly entered or missing.
  
  
  Document Flow or Reference Document Missing:
  
  The system expects a preceding document (e.g., sales order) to create a delivery or billing document, but it cannot find it.
  
  
  Customizing or User Exit Issues:
  
  Sometimes, custom logic or user exits that influence order determination might cause this error if they filter or restrict the search incorrectly.
  
  
  
  When Does This Error Typically Occur?
  
  During delivery creation (VL01N) when referencing a sales order by PO number.
  During billing or order processing when the system tries to find the original sales order.
  When using transaction or process that requires referencing a sales order by PO number, sales org, and customer.
  
  
  How to Solve the Error
  
  
  Verify the PO Number (BSTNK):
  
  Check if the PO number entered exists in the sales order header (field VBAK-BSTNK) for the given sales organization and customer.
  
  Use transaction VA03 (Display Sales Order) and search by PO number.
  Or run a query on VBAK table:  
  SELECT * FROM VBAK WHERE BSTNK = '<PO Number>' AND VKORG = '<Sales Org>' AND KUNNR = '<Customer>'
  
  
  
  
  Check Sales Organization and Customer:
  
  Confirm that the sales organization and customer number are correct and consistent with the sales order.
  
  
  Correct Data Entry:
  
  Ensure that the PO number, sales org, and customer are entered correctly in the transaction.
  
  
  Check Document Flow:
  
  If creating a delivery or billing document, ensure the preceding sales order exists and is not blocked or deleted.
  
  
  Check Customizing Settings:  
  
  Verify if any custom logic (user exits, BADIs) is influencing order determination.
  Check if the system is configured to determine orders by PO number in the given sales org and customer.
  
  
  
  Use Alternative Search Criteria:
  
  If PO number is not mandatory or not unique, try searching by sales order number directly.
  
  
  Check Authorization:
  
  Sometimes, missing authorizations can prevent the system from reading sales orders.
  
  
  
  Additional Information
  
  
  Field Descriptions:
  
  BSTNK: Customer Purchase Order Number (VBAK-BSTNK)
  VKORG: Sales Organization (VBAK-VKORG)
  KUNNR: Customer Number (VBAK-KUNNR)
  
  
  
  Related Transactions:
  
  VA01 / VA02 / VA03 – Create/Change/Display Sales Order
  VL01N – Create Outbound Delivery
  VF01 – Create Billing Document
  
  
  
  SAP Notes:
  
  Check SAP Notes related to VG217 for any known issues or patches.
  
  
  Debugging:
  
  If the problem persists, debugging the order determination logic in the relevant program or user exit can help identify why the system cannot find the order.
  
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  No sales order found matching PO number, sales org, and customer combination.
  
  
  Solution
  Verify and correct PO number, sales org, and customer; ensure sales order exists.
  
  
  Check
  Data entry, document flow, customizing, authorizations, and custom code/user exits.
  
  
  Related Info
  VBAK table, VA03 transaction, delivery/billing creation processes, SAP Notes on VG217.
  
  
  
  
  If you provide the exact transaction or process where this error occurs, I can help with more specific troubleshooting steps.