Question Re: TLB - heuristic creates STOs without considering the issue SLoc in Supply Chain Management Q&A

TLB - heuristic creates STOs without considering the issue SLoc

Former Member — Sun, 12 Jul 2015 11:22:59 GMT

Hi,

when I create stock transfer orders using TLB in APO the STOs do not contain the issuing storage location from the product / material master data.

then we have to go to the STO in ECC and update it with the issu SLoc...which is of course not nice.

What should be done to make sure that the STO from TLB contains the issue SLOC?

thanks,

kr,

Pilvi

Re: TLB - heuristic creates STOs without considering the issue SLoc

RahulHanda — Sun, 12 Jul 2015 13:04:21 GMT

Hi Pilvi.

Check the below link

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a05f7e44-0aa0-2e10-a588-ff4ab7a17717?overridelayout=t…

and SAP note

1866183 - Update of STO Issue storage location in ODL

Basically needs to be taken care in ECC.

Regards

Rahul

Re: TLB - heuristic creates STOs without considering the issue SLoc

Former Member — Sun, 12 Jul 2015 14:33:09 GMT

Hi Rahul,

thank you.

the doc behind the link speaks of mrp storage locations, not of STO between two storage locations in the same plant without using mrp areas. It says taht the issuing storage location has to be entered manually when creating the STO. But we create the STO using TLB in APO.

We cannot go to every single STO in ECC and update it with issuing storage location. I think there has to be some solution for it, I just did not find it yet.

And the SAP note says: This works only for Sales orders but not STOs.

but thank you for trying to help!

kr,

Pilvi

Re: TLB - heuristic creates STOs without considering the issue SLoc

RahulHanda — Sun, 12 Jul 2015 14:58:45 GMT

Hi Pilvi,

Since note mentions that it is for SO that's why I mentioned that you need to carry out this in ECC.

One option could be to put the issue storage location in MRP2 tab. When STO is transferred from APO to ECC, with the help of EXIT_SAPLMEPI_006 Customer Exit for Changing Purchase Order Data (Item Data) you can update the same from material master.

On the other hand there could be situation that one material has 2 or more issuing storage location, then in this case you need to use exit which could meet the criteria on the basis of ATP. Do you have this situation (though I am sure yes), could you confirm? Plus check above exit.

Regards

Rahul

Re: TLB - heuristic creates STOs without considering the issue SLoc

Former Member — Mon, 13 Jul 2015 18:37:14 GMT

Hi Pilvi,

Before running TLB, did you check if the deployment stock transfers had a source location.

Thanks,

Pramod

Re: TLB - heuristic creates STOs without considering the issue SLoc

Former Member — Mon, 20 Jul 2015 07:52:51 GMT

HI Rahul & Pramod,

thank you for responding.

we have two issuing storage locations, but depending on material one of them is imaintained in the mrp 2 view.

the deploymnet stock transfer orders have source location, but just the plant, no storage location.

best regards,

Pilvi

Re: TLB - heuristic creates STOs without considering the issue SLoc

Former Member — Tue, 21 Jul 2015 21:57:38 GMT

Hi Pilvi,

I get your point now.

Make sure all the storage locations are in APO, this can be done by CIFing MRP Areas from ECC to APO.

Make sure the Tlanes are set up between the "Issuing Storage Locations" and the required Destinations.

In this model, you will have to run Deployment and TLB at a storage location level rather than at a Source Location level. Once Deployment is ran using Storage Locations, the confirmed STRs are generated at a SLoc level and they can be published to ECC using TLB(Sloc --> Destination Location) and the STO will have the storage location on it.

I know that the above solve would be a huge change considering locations, product master and Transportation Lanes.

Thanks,

Pramod

Re: TLB - heuristic creates STOs without considering the issue SLoc

Former Member — Wed, 22 Jul 2015 12:56:30 GMT

Hi Pramod,

the issue is that we don't use mrp areas, we do not plan on Storage location within one plant.

we have one SLoc directly in the factory from which a few distribution centers are served, but most of the times we ship the pallets from the factory to an external warehouse which is set up as plant storage location = same plant.

I thought that the STO from TLB will pick up the storage location from material master data, the SLoc for external procurement.

But this is not the case. The STOs created via TLB are missing the issuing SLoc and I don't know why?

kr,

Pilvi