SAP EWM: Doc. Flow (PWP-Put Away Planned) is not updated in the Warehouse Request (Inbound Delivery)

[former_member815012]

Hello All,

We have a problem with the update of the document flow and we would like to know if somebody had the same situation and found the solution.

Problem: An Inbound delivery (Warehouse Request) is created using the standard, the end user execute the packing of the items in different HUs, because the Goods Receipt is executed by HUs and not all the HUs at the same time, we created an Enhancement to create in background a product warehouse task for each HU using the FM: /SCWM/TO_CREATE_WHR. The Warehouse Task is created successfully and at warehouse task level we can see its reference Warehouse Request.

But now when we check the warehouse request in tcode /SCWM/PRDI, we are not able to see the document flow for the document category PWP (Put Away Planned) between Warehouse Request and Warehouse Task in Document flow tab. It generates a wrong Status information of the Warehouse Request (Inbound Delivery).

Question: Do we need to use another FM(For example /SCDL/DL_DOCFLOW_UPDATE) to update the Document Flow linkage between Warehouse Request and Warehouse Task, after warehouse task creation? Is it not done already by the FM: /SCWM/TO_CREATE_WHR in standard?

Thanks in advance.

Elizabeth

[former_member815012]

Hello Daniil,

We did the corrections using your advises and we continue with the same problème:

Dans LT_CREATE_HU we enter only the GUIHU and WPT

Thank you,

Elizabeth

[Daniil]

Hi Elizabeth, Warehouse task creation directly in enhancement is not such a good idea. This could lead to inconsistency, such as missing docflow record.

What you can do in enhancement - set FM /SCWM/TO_CREATE_WHR to the qRFC. Usually it is not required to do anything else, rest would be handled by standard. This is almost standard way for WT Creation. If it is already done in bgRFC or qRFC but still no docflow written you can check WMD* queue ( actually should not go via queue for WT creation, but worth to check it).

Actually HU WT Creation would be possible with Standard if you do POSC with unloading step and unload your HU.

Below is qrfc call example from standard.

MOVE: wmegc_qrfc_hu_prcs   TO lv_qname,
	  ls_create_hu-huident TO lv_qname+4.
ls_rfc_queue-mandt = sy-mandt.
ls_rfc_queue-queue = lv_qname.

CALL FUNCTION 'TRFC_SET_QIN_PROPERTIES'
	EXPORTING
		qin_name = lv_qname.
CALL FUNCTION 'GUID_CREATE'
	  IMPORTING
		ev_guid_16 = lv_guid.

CALL FUNCTION 'ENQUEUE_/SCWM/ERFC_QUEUE'
	  EXPORTING
		mode_/scwm/s_rfc_queue = 'S'
		mandt                  = sy-mandt
		queue                  = lv_qname
		guid                   = lv_guid.

	ls_rfc_queue-guid  = lv_guid.
CALL FUNCTION '/SCWM/TO_CREATE_WHR'
  IN BACKGROUND TASK
  AS SEPARATE UNIT
  EXPORTING
	iv_lgnum       = <tap>-lgnum
	iv_bname       = sy-uname
	it_crea_hu     = lt_crea_hu
	iv_wtcode      = lv_wtcode
	is_rfc_queue   = ls_rfc_queue
	iv_commit_work = ' '.

[former_member815012]

Hello Daniil

Thanks a lot for your help, it is really appreciated

We use a qRFC to create the WT. However, we dont use the paramètre is_rfc_queue = ls_rfc_queue in the FM.

I will have a look with out développeur.

Best Regards,

Elizabeth

[Daniil]

Hello Elizabeth,

it is not mandatory parameter.

Check the roles of your source and destination storage types. It works (or should work) when you have proper roles. And you can test it from the /scwm/prdi for one HU, to see if it works from standard.

BR,

Daniil