TLB with 2 products on the same Lane having different UOM for Wt and Vol??

[Former Member]

We have 2 products with different UOM for Volume and Weight. First product is in CCM and KG. The second is in FT3 and LB. Both are on the same Lane with one Means of Tranport. The TLB profile is defined in FT3 and LB. In the TLB View, the following 3 issues occur:

1. First product is displayed in CCM and KG without conversion to FT3 and LB.

2. The values of the 1st product are added as is to the values of the 2nd product without conversion to FT3 and LB to get the Total.

3. The max limits defined in the TLB profile are not honored.

The question is:

Can we not combine products with different Weight and Volume UOM's?? What is the solution?

Thanks,

Siva.

[somnath_manna · Accepted solution]

Hi Siva,

The first product should have alternate UoM conversion for the UoM defined in the TLB profile. Even with that you may need to do enhancement of TLB logic.

The BADI for sorting deployment orders for TLB is /SCA/TLB_EXT, method SELECT_NEXT_PRODUCT. Put in custom logic first to do the conversion of Deployment order quantity to TLB Profile maintained UoM and carry out sorting. See SAP Note 710198 for details.

Hope this helps.

Thanks,

Somnath

[Former Member]

Dear Siva,

We can take any No of products with Different UOM for TLB. The only thing is that we have to maintain conversion to a common unit which can be anything FT3,CCM,HL3,M3,KG,ST etc This conversion can be maintained in AUOM. We have to define the TLB Profile in that common unit.

The same way i have handled the scenario successfully in our Project.

Hope this will solve your problem too.

regards,

manjit

[raman_sethi]

Hi Manjit,

can you guide me in the integration of means of transport(for example a truck) and plant maint.

The business scenario requires preventive maint of trucks in PM, which are used to transport goods for a logistics company. Whilst under maint the truck should not be available for scheduling a shipment of goods

thanks in advance

best regards

Raman Sethi