How To Fix WS778 - Draft ID &1 does not contain pattern '$$' (invalid API call)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 778

• Message text: Draft ID &1 does not contain pattern '$$' (invalid API call)

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 WS778 - Draft ID &1 does not contain pattern '$$' (invalid API call) ?

  SAP Error Message:
  
  WS778 Draft ID &1 does not contain pattern '$$' (invalid API call)
  
  Cause
  This error typically occurs when working with SAP Web Services or APIs that involve draft handling, such as OData services or Business Object APIs that support draft entities.
  
  The system expects the Draft ID to contain a specific pattern, usually including $$ as part of the draft identifier.
  The error indicates that the Draft ID passed to the API does not contain the required $$ pattern.
  This usually means that the draft identifier is either malformed, incomplete, or the wrong ID is being passed to the API.
  It can also happen if the draft handling logic is incorrectly implemented or if the draft was not properly created or saved before the API call.
  
  
  When does it occur?
  
  When calling APIs that require a draft ID with a specific format.
  When trying to update or manipulate a draft entity but passing a non-draft ID or an invalid draft ID.
  In custom developments or integrations where draft handling is implemented manually.
  In OData services with draft-enabled entities, especially when the draft key is not correctly handled.
  
  
  Solution
  
  
  Check the Draft ID Format:
  
  Ensure that the Draft ID passed to the API contains the $$ pattern.
  Draft IDs in SAP often have a format like: GUID$$<some_suffix> or similar.
  Verify that the draft ID is correctly retrieved from the system or service before passing it.
  
  
  
  Verify Draft Creation:
  
  Confirm that the draft was successfully created and saved before the API call.
  If the draft does not exist or was not saved, the draft ID will be invalid.
  
  
  
  Review API Usage:
  
  Make sure you are using the correct API method for draft handling.
  Some APIs require different calls for draft vs. active entities.
  Check SAP documentation for the specific API to understand draft ID requirements.
  
  
  
  Debug and Trace:
  
  Use SAP debugging tools or logs to trace the draft ID value being passed.
  Check if the draft ID is being truncated or modified incorrectly in the code.
  
  
  
  Correct Integration Logic:
  
  If this is part of a custom integration or middleware, ensure that the draft ID is correctly passed and not replaced or corrupted.
  
  
  
  
  Related Information
  
  SAP Draft Handling: Draft handling is a mechanism in SAP to allow users to save incomplete data entries and continue editing later.
  OData Draft Entities: In SAP Gateway OData services, draft-enabled entities have special keys and draft handling logic.
  SAP Notes and Documentation: Check SAP Notes related to draft handling and the specific API you are using.
  SAP Community: Similar issues are often discussed in SAP Community forums, which can provide examples and solutions.
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Error
  Draft ID does not contain pattern $$
  
  
  Cause
  Invalid or malformed draft ID passed to API; missing expected $$ pattern in draft ID
  
  
  Solution
  Ensure draft ID format is correct; verify draft creation; use correct API calls
  
  
  Checkpoints
  Draft ID format, draft existence, API usage, integration logic, debugging
  
  
  
  
  If you provide the context of the API or transaction where this error occurs, I can help with more specific guidance.