reuse HU in SHPCON (WHSCON) IDoc

[laxmikatta]

When we try to reuse the same Handling Unit in SHPCON IDoc, the picking confirmation and goods issue for outbound delivery is failing with the error messages : HUSELECT 008 "Handling unit &1 posted for goods issue exists already" & HUSELECT 005 "There is already a handling unit posted for GR without stock". The unique number assignment for handling units is active in Customizing.

In the two SAP OSS notes# 1839738 (Error HUSELECT005 - reuse HU in SHPCON (WHSCON)) & #2637609 (IDoc cannot update the HU due to HUSELECT008), SAP has stated "The required function is not possible in SAP Standard. The error doesn't occur in VL02N when using an existing HU. A development request might be taken into consideration according to SAP Note 11."

We raised a development request / improvement request # 251903 under customer influential program for this 'missing' functionality as per SAP note 11 and requested SAP to provide a solution to this missing function in standard SAP and allow reusing of Handling Unit in SHPCON IDoc. Not sure how long SAP will take to review our request # 251903 and get back to us (on this Business critical issue) if at all they accept our request.

I would like to know if anyone has developed a solution and get a modification from your own development team to force the system to use the original HU in case of such issue like this one. Can you please share your feedback.

Thank you in advance!

Regards,

Lakshmi

[clementfortin]

In the standard, the system checks the uniqueness flag set in customizing with function module HU_TVSHP_SELECT.

The enhancement you need to implement aim to temporary consider that variable ef_exidv_unique = 0 (uniqueness flag deactivated) to avoid the triggering of the standard error message.

To avoid side effect of the complete Uniqueness deactivation, this deactivation is required only when it is really required :
- when GI is posted against a SHPCON IDoc
- or in case of a manual VL09 cancellation flow of a delivery which was previously sent to an external system because other wise you will have an inconsistency

For the first case :

In our solution SHPCON IDoc are processed with a specific function module ZFM_IDOC_INPUT_DELVRY.

If this function module is triggered, we save in the memory buffer a boolean value = True. We call this value in the enhancement of function module HU_TVSHP_SELECT to proceed, if it is equal to TRUE, with the deactivation of HU uniqueness flag.

For the second case:

The goods issue cancellation flows in SAP uses the standard function group SAPLV51W. Include LV51WFHU contains the functions which are used to cancel goods issue on handling units. At this point, we’re able to retrieve the outbound delivery number which is not directly available in function module HU_TVSHP_SELECT
In the standard, the system checks the uniqueness flag set in customizing with function module HU_TVSHP_SELECT.

In your enhancement :
- you need to check if the transaction used is VL09 (sy-tcode = ‘VL09’) 
- you also need to check if an output has already been sent to an external system: use the delivery number to look up for an entry in table NAST (log table for output) with partner type = LS. If there is at least an entry, you can save the delivery number in the memory buffer and proceed with the enhancement.