Low Level Code - Product Specific & All Products T Lane cyclic behavior

[Former Member]

Hello Team,

This query is related to Low Level Code Determination & it's output spool.

Spool is showing some codes which it suggests have cyclic behavior. Scenario is as below:

Product - P1234, Location - L1 & L2. T Lane setup :

From L1 > To L2 : P1234 - Product Specific T Lane.

From L2 > To L1 : P1234 - Product Specific T Lane is - Locked (X) & All Products T Lane is Open. (all other parameters - Proc Priority etc is same)

As per my understanding, Product Specific Lock should be respected in Low Level Code determination as well, as it is respected in Heuristics Run.

Now, in this case, why should Low Level Code Determination Program should show - P1234 as a code having Cyclic Behavior?

Any inputs or pointers will be helpful?

Regards,

Pushkar

[m_manimaran]

Hi Pushkar,

What is the procurement type of the material P1234 at locations L1 and L2?

If the procurement type in L2 is E -inhouse production, then the T-lane L2-->L1 will be ignored.

If the procurement type in L2 is F or X- then the system will look for the SoS.

I tested this scenario in my system, it is not giving any cyclic error, when the L2-->L1 t-lane is locked for product specific. Please check the validity period and lot size validity for your product specific t-lane. If it is invalid, then system will take 'All products' t-lane and it will display cyclic behavior.

Regards,

Manimaran M.

[Former Member]

Hi Manimaran,

Thanks for checking.Here are more details about P1234 & L1 & L2.

It is "F" at both the locations.

P1234 on T Lane From L1 > L2 : Product Specific - Open (No All Products)

Start Date - 23.04.2007,  End Date - 31.12.9999;

Min LS - 1, Max LS - 999,999,999; Proc Prio - 1

P1234 on T Lane From L2 > L1 : Product Specific - Locked & ALL Products - Open

Product Specific - Parameters :

Start Date - 24.04.2007, End Date - 31.12.9999; Min LS - 0, Max LS - 0; Proc Prio - 1.

All Products - Parameters :

Start Date - 1.09.2011, End Date - 31.12.9999; Min LS - 0, Max LS - 0; Proc Prio - 0.

I understand your inputs & that's the behavior we are also expecting in our system, however, LLC Job flags it as Cyclic behavior.

Hope above parameters will elaborate real time scenario in details, and may be someone can point me - what's wrong with this setup to get it flagged as Cyclic.

Are the Start Date & End Date or LS are influencing here for LLC?

Plz share your inputs.

Regards,

Pushkar

[former_member187488]

Hello Pushkar,

"All Products" and product specific T-lane are considered as two different lanes. If you have set both, you'll get two lanes during source determination. So you can understand that blocking product specific lane would not have any affect "All products" lane. That's why you get the cyclic error.

Besides, it is not suggested to us "All Products" lane unless you really ship all products with that lane. It will cause performance issue or memory problem during some processes like LLC determination.

Best Regards,

Ada

[Former Member]

Hi Ada,

Thanks for your reply.

I checked this scnario in system & found that Product Specific gets precednece over All Products in Heuristics when getting SoS. ANd this is on expected lines.

However, LLC is shopwing some flase results, not sure why?

As I mentioned in my scenario - I have Product Specific - Locked where there is Open All Products T Lane.

Regards,

Pushkar