TR processed Automatically without TO

[Former Member]

Dear Experts,

In my Clients Production environment, there are few TR's automatically updated with "Processed" status by ADMIN ID.

311 movement happens from a WM managed S.Loc to Non WM managed S.Loc... TR is created with Destination ST 921.

311 movement type is relevant for Automatic TO creation. (Automatic TO - A) and job RLAUTA10 runs in Bg to create TO.

But in some cases, TO is not getting created but TR is updated (By Admin ID) with "Processed" Status.

Because of this Negative stock is piled up in ST 921. Please help.

Regards,

Ramprakash

[Former Member]

When you refer to ADMIN ID are you referring the the batch job user ID or a human system administrators user ID?

[Former Member]

Hi Jacob,

Its a Batch Job ID. Prorgam is RLLL02SE. (Warehouse Monitor: Determine unprocessed TR items)

Since the movement type 311 is relevant for automatic TO creation, ideally the TR(created for mvmt 311) should not be picked by this program. Only in few cases TO is not getting created.

Even for some reasons if the TO is not getting created, why the system is "check"ing "TR status delivery completed"?  (Like in the report LL01)

Thanks in advance.

Regards

Ramprakash

[JL23]

Now you are confusing your readers. RLLL02SE does not process transfer requests, it is just preparing the database for quicker access through LL01 transaction, all based on your own customizing.

It is is purpose to identify unprocessed TRs, even (or especially) for undesired situations.

[Former Member]

Hi Jurgen,

There are basically 2 issues here.

First, in some cases TO is not getting created for movement type 311. This we found out the reason. The Auto TO creation indicator in Movement type and program RLAUTA10 does not match for few new plants. So this is being taken care now.

Now Second issue. The TR's for which TO was NOT created,(Because of above reason) how its marked as "TR status delivery completed" with ADMIN ID? .. We were unable to find it out. Probably which program could have done that? Please provide your support . thanks.,

Regards

ramprakash

[Former Member]

FM: L_TR_CANCEL can be used in custom transaction via batch job, commonly used to cancel partially open TR qtys, this will set the processed flag in TR

TR status delivery completed is a selection option in LL01 to mark TR complete...

Suggest you check for any such batch job and/or wait until the first issue is resolved then mark delivery complete for any old TR, then you can see if any such issue persists.

Note: the TR should be marked complete only when the replenishment work queue is empty (no open TO for replenishment) just to be safe

EDIT: also note the batch job user I.D. mentioned in the TR is most likely the user user I.D. that created the TR and the processed flag is getting set be a human (unless you find a cancellation job is in fact running L_TR_CANCEL)