Product Intransit (Plant)

[whitehead6682]

Hi All

I'm after a little help if possible?

I have a problem where residual production stock that is showing as In Transit (Plant), my normal course of correction would be to receive the delivery in MIGO and the Transfer Post back to the production site (301 transaction), however, some of these transits date back to 2005 and any posting will hit accounts that have not budgeted for them, does anybody know of a way to write off the intransit without receiving into destination and carrying out a write off?

Thanks for any help.

[svetja]

Any movement that corrects valuated stock will certainly hit a financial account.

[whitehead6682]

Thats what i thought the answer maybe, thanks for your help

[whitehead6682]

Hi All

Back to this problem, I have finally been given the green light to clear these off.

Problem being I have stocks showing in 'In Transfer (Plant)' dating back to 2004, the only way I can see to resolve these is individually MB51 each material and find a open delivery number to complete the 605mvt via Migo.

Does anybody know of a better solution?

I am all ears.

Thanks for any help.

[svetja]

I have never used a 605, cannot even imagine when this would be used.
However, a 605 is certainly related to STO, hence you should be able to find the purchase order in MB5T.
And from the PO history you can easily get the delivery, no need for MB51

[Seany]

if your intention is to goods receipt the stock then write it off and you have open POs/STOs do this against the best approach would be to execute firat the GRs then the write offs. If you no longer have the PO/STOs or you do not wish to follow the 2 step process you could use movement type 557/558 to directly update the MARC-TRAME stock in transit figures. This of course will not update any of the document flow so should be used as a last resort. Also, like Svetja I am not familiar with the 605 movement type so I suspect that you may be using a different module/solution than the standard so I would recommend that you test any solution first before executing it in production