Master Data (zones and lanes) structure in TP/VS

[Former Member]

We have about 2000 customer destination locations and about 240 source plant locations. How should the master data for T-Lanes be designed? If we make point to point lanes, then the number of lanes would be 20 Lacs. If we categorize customer locations into zones, then the structure gets complicated by Incompatibilities, and also zone to zone laning tends to become circular, even though number of lanes gets substantially reduced. Zone to zone laning has certain issues as time passes by and you keeop maintaining further lanes from one zone to zone 2 and then from zone 2 to zone 3 and so on which becomes a never ending process and one fine morning you find that this laning has become almost a ring.

Any thoughts on this please.

Sunil Madhogarhia

[Former Member]

Hi Sunil,

I hope the attached link will help you to build your scenario.

http://help.sap.com/saphelp_scm2007/helpdata//EN/9d/4ac637ec356838e10000009b38f8cf/frameset.htm

Regards

R. Senthil Mareeswaran.

[Former Member]

Hi,

I think one way to do it is by transportation zones as the no of lanes in case of point to point would be too large. There will be a long list of incompatibilities but the rules are written in groups so it should be limited. Also there are low level codes which determine the sequence in case of formation of circles this low level codes will not be generated and thus formation of cycles can be avoided.

Regards,

sireesh