Putaway TO creation in RF

[Former Member]

Dear Experts,

We have a requirement to create Putaway Transfer Order in RF.

Please letus know is it possible to create Putaway TO by scanning either HU or Delivery in RF?

If so, kindly share the transaction code.

Rgds,

Shetty

[Former Member · Accepted solution]

Hello Shetty,

do you plan to use LM* transactions for that task ? (you may browse all transactions in SE93 with LM*)

If so, unfortunately there is no RF transaction for this.

The idea of LM* transactions is executing existing work (like confirming open TOs), not creating work (creating TOs). TO creation is done outside RF world. You may use RLAUTA10 for TRs or WMTA message in inbound delivery for automated TO creation.

Then you can confirm open TO either by HU. by delivery number or system guided (which is typically not useful at inbound side)

If you really need the TO creation (for HU/inbound delivery) you may write a ZLMxx transaction calling L_TO_CREATE_DN function to get TOs.

Regards,

Matthias

[Former Member · Accepted solution]

Hi Mathias,

LM71 worked for me. It has a option to create TO for Inbound Delivery ( F8- generate TO)

Thanks,

Shetty

[satishkumar_kirla · Accepted solution]

Hi Mathias,

Based on your active participation i guess you can provide solution for my problem.

It is obvious that we need to have a Inbound delivery document for PO if we want to receive materials using RF transactions.

When we receive material in to HU Managed SLoc system will try to create a inbound delivery document in back ground to enable the entry of packaging details in the system. Similary when we move material out of HU Managed SLoc system will created out bound delivery docuemnt in background.

I had the following sceanrio to implement-

I had SLoc1010 (non-HU managed) and HU10 (whcih is HU counter part for 1010). My vendor send us delivery with packaging but he could not send vendor confirmation so that i could not automate inbound delivery creation.

I tried to receive material against a PO in to Sloc HU10. In this case system is trying to create a inbound delivery document in background. As the PO did not have any confirmation control key, it could not create inbound delivery document. If I add a confriamtion control key in PO before posting mateiral docuemnt, it will not allow GR using MIGO as inbound delviery is a pre-requisite for GR.

Can you plz help me in getting a soluciotn for this?

thanks in advance

[Former Member · Accepted solution]

Hi Satish,

I checked this szenario in our system. As you said, MIGO for PO with confirmation control=0004 is not possible due to missing inb.del.

But you can use VL31N to create inb.del 4 PO with conf. control=0004. The conf.control can be set automatically depending on vendor+material relation somewhere (I think).

Best regards,

Matthias