Blocked TLanes

[Former Member]

Hi all,

We CIFed some Pur Info Records from ECC to APO, which created TLanes in APO. But some TLanes have blocking indicators marked (for the codes I am checking). I want to know if the system itself because of any reasons puts blocking indicators in a TLane?

I used to think that blocking indicators are put only manually. If system puts blocking indicators by itself, how can I find out why has it done so?

[GSU · Accepted solution]

HI

Three possibilities:

1)If you delete the SOS in ECC i.e The deletion flag for source of supply in ECC does not delete the external source of supply in APO. Unlike in ECC ,the external source of supply is blocked for newly created orders. In APO it is active/inactive flag instead of deletion flag.

2)Do you use 'Source list'?

Transport lines for integrated source of supply should be available only in case of:

- source list is not blocked

- source list is relevant to MRP

- source list don't exist at all (transport line is created according source of supply values in this case)

Otherwice transport lines should be set to status Locked.

Please refer the SAP Notes:1224603,1127329,998393,1271779)

3) If you Change 'Special procurement type type-20 in ECC Customizing---(i.e in TA-OMD9- key "U,# is replaced with blank --Initial) ,and re-activate CIF IMO

Also,make sure that note 1397763 is implemented in SCM system,and note 1390459 in ECC

Thanks and Regards

Suresh

[Former Member · Accepted solution]

Thanks a lot Suresh; that was a very useful reply.

I checked for this; Source List and Pur Info Record both are maintained for this code in R/3. Both are correct, e.g. SL is not blocked and valid for MRP... So I am not able to know why this is happening. I haven't checked SAP Notes you have referred, yet; I shall do that next. Actually this error is coming since we have setup a new plant in the system. Such errors didn't come for old plants as far as I know.

Right now I am thinking if we had some Quota arrangement maintained for another vendor, which we deleted. May be this TLane was created when there was a 100% quota maintained for some other vendor and hence APO blocked this TLane? We had deleted all Quota arrangement on this plant some time back. Can this be a reason?

[former_member209769 · Accepted solution]

Hi,

Quota arrangement would not be relevant for TLane block.

Your error is actually quite strange.

I think you would need to do some more checks to identify when the issue has actually happened.

1) Remove the block indicator in Tlanes, and also from the external procurement relationship, if they are also blocked.

2) Run your normal CIF jobs relevant for CIF of PIRs (or wait for them to finish at their regular timing), and see if there are issues again in Tlanes (and in external procurement) after these jobs have finished.

Source List blockage in not relevant for blockage of TLane in standard CIF as far as I know. Unless you used relevant enhancements, this should not matter.

Do the above checks 1 & 2 for the next couple of CIF runs for PIRs in your system. See if you can establish some pattern for the issue (only some particular materials or plants are affected), also whether it occurs again or not.

Mostly in APO systems, change logs are not activated for performance reasons, but if its possible for you, try to TEMPORARILY activate the change documents by going to SPRO-> Advanced Planning and Optimization-> Master Data-> Transportation Lane-> Activate Change Documents.

You can display the the change documents for a transportation lane via the SAP APO menu under Master Data -> Transportation Lane -> Display Change Documents or using transaction /SAPAPO/TR_CD_TLANE.

With the change log active, you could find out when/how the Tlane got blocked. This should be helpful in understanding the root cause.

Hope this helps.

Thanks - Pawan

[Former Member · Accepted solution]

Thanks a lot Pawan. I am trying out your suggested approach now.

I have removed blocking indicator in the TLane. Blocking indicator didn't exist in Ext Proc relationship as such. I am trying to run the CIF batch job and see.

[aparna_ranganathan · Accepted solution]

Hi

Iam sure you know this - but still trigger a dummy change in your source list and then run the CIF - a CIFSRC change pointer has to be created and picked up by the CIF thats the reason iam asking you to trigger dummy change.

Also only if source list is blocked , transportation lane will get locked. Go to change log of your source list and check if the source list was blocked at some point of time and then unblocked in R/3 . That will give you an idea why the transportation lane got locked in the first place

Thanks

Aparna