Skip to main content

1882260 - Error 06249 occurs when creating several Purchase Orders from one 3d party sales order

 At times, business users do purchase orders for the purchase requisitions created through sales orders. Again, after few days business users will try to use the same purchase requisitions to create new purchase orders.

 In this situation, SAP throws the error message Error '06249' even though it is maintained as a warning message in system messages.

This is standard SAP functionality and below is the workaround need be implemented as proposed by SAP in the note mentioned in the subject line.

 

The following workarounds are possible - from both MM and SD perspectives:

  1. Solution for MM side:
  • Use the already existing PO + item.
  • In this existing PO item, please create a new delivery schedule (tab "delivery schedule") for the new delivery date and the open units, then the system will allow you to continue.

- or -

  1. Solution for SD side:
  • Create a new schedule line in the old sales order item, or create a new item in the sales order for the remaining quantity.
  • You are then able to create a new purchase requisition, and this new purchase requisition can then be converted to a new PO.

 

 

Comments

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...