TLB confirmed quantity less or equal to pallet size

[Former Member]

Hello APO community,

We are trying to create SNP TLB shipments for exact quantities (rounding value = 1) but the confirmed quantities per product per truckload should be equal or less to the pallet size.

We are using Minimum and Maximum lot size in the TLB profile to get the pallet size (e.g Min LS = 1 and Max LS = 48) and using rounding value = 1 so we get the orders to match the requirement.

So far we are able to get the orders as we need them but when running TLB to build the trucks, the pallets are greater than the Max LS (i.e. 1.2 full pallets displayed in the FULLPAL parameter). The requirement is to have the confirmed quantities from TLB to be equal or less than the Max LS.

Any help would be greatly appreciated as we are close to the project move to production and APO is the starting point for this process.

Thank you,

David Gonzalez

[rajkj · Accepted solution]

Hi David,

Please ensure your TLB profile is defined with FLOORSPOTS parameters as shown below.

Rule Counter	Parameter	Comp Op. Lower Limit	Parameter Value	Comp. Operator f. Upper Limit	Parameter Value	UoM
1	Floor Spot	>=	7000	<=	12000	PAL

If your stacking factor is blank or 1, FLOORSPOT will be same as PALLET. You also need to ensure that UoM conversion PAL to Base UoM is defined and the PAL quantity is exact multiples of max LS.

If mixture of products are allowed to share the same pallet, then the required configuration is bit complicated. Please check the following link for details.

http://help.sap.com/scenarios_bus2008/helpdata/en/e7/aa3340fa40ea01e10000000a155106/frameset.htm

Thanks,

Rajesh

[Former Member · Accepted solution]

Hi Rajesh,

Thanks for your reply. I think that would work for an scenario different from what I have. I think I had to add more details to my question.

We are already using the FLOORSPOTS parameter to limit the number of pallets we want in a truck and that is working fine. The orders are calculated with the right number of floorspots. The problem is that for those pallets/floorspots we have the system calculating the quantities above the pallet size.

Something else I have to mention is that the truck can have multiple products and each of the products have different pallet size. We are using Load balancing.

This is what I'm getting right now. TLB shipments

Order Number	Deliv.Date	FLOORSPOTS
742487	11/15/2012	20
742488	11/15/2012	20
742489	11/15/2012	20
742490	11/15/2012	20
742491	11/15/2012	20
742492	11/15/2012	20
742493	11/15/2012	20
742494	11/15/2012	20
742495	11/15/2012	20
742496	11/15/2012	10

TLB shipments (First order)

Order Number	Product	Confirmed	FULLPAL Qt	FLOORSPOTS	BUn
742487	26000	48	1	1	CV
742487	26001	69	1.44	2	CV
742487	26010	36	0.75	1	CV
742487	26015	104	2.17	3	CV
742487	26075	135	3.75	4	CV
742487	26126	70	0.78	1	CV
742487	26175	90	1.88	2	CV
742487	26177	86	1.37	2	CV
742487	26228	81	2.7	3	CV
742487	26234	39	0.97	1	CV

As you can see the FULLPAL Qty column is showing 1.44 for product 26001 (pallet size 48). We need the system to create orders with FULLPAL Qty = 1 and maybe the last container(s) with the remaining quantities.

TLB shipments (second order)

Order Number	Product	Confirmed	FULLPAL Qt	FLOORSPOTS	BUn
742488	26000	48	1	1	CV
742488	26001	68	1.42	2	CV
742488	26010	35	0.73	1	CV
742488	26015	104	2.17	3	CV
742488	26075	134	3.72	4	CV
742488	26126	69	0.77	1	CV
742488	26175	89	1.85	2	CV
742488	26177	86	1.37	2	CV
742488	26228	81	2.7	3	CV
742488	26234	39	0.97	1	CV

For the second order, again the quantities for FULLPAL are fractions. The first item is showing what we need, but I think it was only by coincidence that we got the values.

Thank you,

David

[rajkj · Accepted solution]

Hi David,

Thanks for the details.

Based on my system release level (SAPKY70108), the standard system does not provide any implementation to support FULLPAL. Hence, I assume that you would have implemented BAdI /SCA/TLB_EXT to support this parameter. If my assumption is correct, please check the BAdI implementation with reference to the example provided per method implementation

/SCA/CL_TLB_PARAM_CALC-parameter_into_product as described in the following note.

https://service.sap.com/sap/support/notes/710198

Thanks,
Rajesh

[Former Member · Accepted solution]

Hi Rajesh,

We are on the same release level. We have not implemented any BADI so far. I'm using FULLPAL just to display the actual Pallet number (as you saw in my previous message). The way I made it to work was simple. Included it in the TLB profile with no parameters and then you can see it in your layout.

So, is it fair to say that the confirmed quantity in the TLB shipment cannot be topped/rounded to the pallet size by using the parameters floorspots, volume or weight? in other words, the badi has to be implemented to use a new parameter achieve this?

Thanks for your help,

David

[rajkj · Accepted solution]

Hi David,

Per SAP note 710198, you need to implement BAdI /SCA/TLB_EXT to use any custom parameter other than VOLUME, WEIGHT, and FLOORSPOTS.

The default implementation calculates the pallet requirements (based on UoM conversion) and applies staking factor to derive number of floor spots, which would be rounded to nearest integer value.

Before attempting BAdI implementation, it might be a good idea to check the parameters such as backtracking, shipment upsizing and downsizing, along with rounding value equal to pallet size assigned to product specific t.lane. It might fix the issue otherwise you need to have a custom logic to round up both floor spot and pallet quantity.

Lot Size/Quantity and Date Determination
Rounding Value
The TLB uses the rounding value for building transport loads. However, the TLB first uses the value that you have defined in the transportation lane, that is, in the lot size profile (SNP) or transportation guideline set (SAP SNC). If no value is assigned, the TLB uses the value specified here or 1.
So that the SNP TLB can use this rounding value, you must set the relevant indicator in the SNP Customizing under Basic Settings ® Maintain Global SNP Settings. Otherwise, the SNP TLB uses the rounding value from the transportation lane.
Backtracking and upsizing
https://service.sap.com/sap/support/notes/1046965

Thanks,
Rajesh

[Former Member · Accepted solution]

Hi Rajesh,

The backtracking field made the magic!

Thanks so much for your help,

David

[rajkj · Accepted solution]

Hi David,

It's nice to know that your issue got resolved with backtracking and thanks for informing what worked for you. It is definitely a learning exercise.

Thanks,
Rajesh