How To Fix WTADDI252 - Additionals IDoc already requested via BAPI

SAP Error Message - Details

• Message type: E = Error

• Message class: WTADDI - Additionals: Messages

• Message number: 252

• Message text: Additionals IDoc already requested via BAPI

What causes this issue?

This additionals IDoc has already been requested via BAPI using the
same parameters. The <DS:DE.ADDIS_BAPI>status</> has been set to "fully
processed" accordingly.
The IDoc can only be generated once; the system refuses a second
request.

System Response

No additionals IDoc is generated.

How to fix this error?

If you do want to generate another additionals IDoc, however, use the
'Find' function in the additionals monitor to find the additionals IDoc
and reset the status. You can then generate a new additionals IDoc.
If you are not authorized to make this change, ask someone who has the
necessary change authorization to reset the status in the additionals
monitor.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WTADDI252 - Additionals IDoc already requested via BAPI ?

  Certainly! Here's a detailed explanation for the SAP error message WTADDI252: Additionals IDoc already requested via BAPI:
  
  Error Message
  WTADDI252: Additionals IDoc already requested via BAPI
  
  Cause
  This error occurs when an attempt is made to request or generate an additional IDoc (Intermediate Document) for a delivery or shipment via a BAPI (Business Application Programming Interface), but the system detects that the additional IDoc has already been requested or generated previously for the same document.
  In other words, the system prevents duplicate requests for the same additional IDoc to avoid redundant processing or sending duplicate messages.
  
  Context
  
  This message typically appears in the context of Logistics Execution (LE), especially when dealing with deliveries and shipment processing.
  Additional IDocs are often used to send extra information or updates related to deliveries, such as shipment status, delivery confirmation, or other logistics-related data.
  The BAPI involved might be something like BAPI_OUTB_DELIVERY_CHANGE or a similar function module used to trigger IDoc generation.
  
  
  Solution
  
  
  Check if the additional IDoc has already been requested or generated:
  
  Use transaction WE02 or WE05 to display IDocs and verify if the additional IDoc for the delivery/shipment already exists.
  Check the status of the IDoc to confirm if it has been processed or is still pending.
  
  
  
  Avoid duplicate requests:
  
  Review the program or process that calls the BAPI to ensure it does not request the additional IDoc multiple times for the same delivery.
  Implement logic to check if an additional IDoc has already been requested before making a new request.
  
  
  
  Reset or clear the request flag if necessary:
  
  Sometimes, the system sets a flag indicating that the additional IDoc has been requested.
  If this flag is set incorrectly or needs to be reset (for example, if the previous IDoc failed and you want to resend), you may need to reset the flag in the delivery/shipment data.
  This should be done carefully, preferably with SAP support or by following SAP notes, to avoid inconsistencies.
  
  
  
  Check for OSS Notes:
  
  Search the SAP Support Portal for OSS notes related to WTADDI252 or additional IDoc generation issues.
  There might be patches or corrections available if this is a known issue in your SAP version.
  
  
  
  
  Related Information
  
  Transactions:
  
  WE02 / WE05 — IDoc display and monitoring
  VL02N — Change Outbound Delivery (to check delivery data)
  VL03N — Display Outbound Delivery
  
  
  BAPIs:
  
  BAPI_OUTB_DELIVERY_CHANGE
  BAPI_OUTB_DELIVERY_CONFIRMATION
  
  
  Tables:
  
  LIKP — Delivery Header Data
  LIPS — Delivery Item Data
  EDIDC — Control record for IDocs
  
  
  SAP Notes:
  
  Check SAP Notes for any known issues or corrections related to additional IDoc generation and BAPI calls.
  
  
  
  
  Summary
  The error WTADDI252 indicates that an additional IDoc for a delivery or shipment has already been requested via a BAPI call, and the system is preventing a duplicate request. To resolve this, verify existing IDocs, avoid duplicate BAPI calls, and if necessary, reset the request flag carefully.
  
  If you need help with specific steps or code snippets to check or reset the flag, please provide more details about your scenario or the BAPI you are using.