Clarification on Deployment Run & TLB

[Former Member]

Hi Experts,

I am new in APO SNP & need some clarification on Deployment Run & TLB

1. When we carry out a an SNP run, what I understand that planned orders and stock transport orders are created with respect to the supply locations. However when the demand and the supply do not match we go for deployment run. Does this deployment run deletes the stock transport orders created by SNP run?
2. The TLB run ensures the utilization of capacity of the transportation means. It converts the confirmed stock transfers into shipments. Does that mean it does a dispatch (equivalent to VL02N in ECC)?

Appreciate your concern & thanx in advance.

Regards,

Balraj

[Former Member · Accepted solution]

Hi Balraj

SNP Run (e.g. Heuristic) creates Planned Demand and Supplies - Deployment run deletes them and creates STR/STO depending on configuration. There are multiple horizons and rules that come into play depending on configuration - I would suggest you go through SAP Help

http://help.sap.com/saphelp_SCM700_ehp02/helpdata/en/32/56623bf3d040d29988441cafcedc24/frameset.htm

For TLB, it groups these STR/STO based on transport capacity and creates STO. Again there are no of config to tweak the behaviour. http://help.sap.com/saphelp_SCM700_ehp02/helpdata/en/1c/4d7a375f0dbc7fe10000009b38f8cf/frameset.htm

It is not same as delivery creation or shipment creation in ECC. Though you can create a STO in ECC as well. You can transfer these STOs from APO into ECC and carry out further transactional processes.

Thanks,

Prasun

[former_member209769]

Hi Balraj,

Let me add some more specific replies to your questions:

a) SNP will result in "planned" orders. It could be Production (planned) or "Distribution receipt (planned)" depending on what kind of procurement is possible for the product. When you run deployment, you would get "confirmed" orders. Deployment might delete or convert the "Distribution receipt (planned)", and provide "distribution receipt (confirmed)". In SNP, we tried to get receipts for the demands. In deployment, we consider how to deploy the available receipt elements to the locations having demand (and in more finer detail). So, logically deployment would follow the SNP run. You could send the result of deployment over to R/3 as STR or STO by maintaining settings in SPRO. Or you could use the results of Deployment in TLB, and then send TLB results to R/3.

b) TLB takes care of building truckloads. In Deployment, you had identified how you would deploy the supply to the locations having demand. Now in TLB, you identify that depending on your means of transport, how you would like to build truckloads. e.g. to have best utilization of your truck, it might make sense to combine few deployment orders which are currently a few days apart.

Result of TLB would be a STO (could also be a PO in R/3). This is not like a delivery as others also told.

Thanks - Pawan

[rajkj]

Hi Balraj,

Please find below additional explanation related to SNP.

1. SNP Planning run generates the STR proposals out side of SNP stock transfer horizon based on the factors such as supply shortage, target and safety stock requirements, lot sizes, and planning calendars.
2. SNP Deployment run refines these proposals by considering other constraints such as Pull deployment horizon, ATD receipts and issues, quotas, Push distribution, and fair share rules. This run will delete the STR generated by planning run and recreate them as Distribution Receipt/Demand confirmed.
3. TLB run constraints these confirmed proposals by applying capacity restrictions. It converts the deployment orders into TLB shipments that can be published to ECC as STO (or sales order in case of VMI). In ECC, these orders will undergo usual logistics execution process to transfer the stock.

Please refer to SAP documentation for further details and master data setup to control these SNP processes.

Thanks,
Rajesh

[former_member187488]

Hello,

SNP planning run (heuristic, optimizer or CTM) creates planned order (inhouse-production) and stock transfer requisition (external-procurement). There're two points:
1) This is done for each receiving location, not supplying location. Whenever there's a supply shortage in the receiving location, it creates planned order to cover the shortage.
2) This is done outside SNP production horizon  (inhouse-production) or SNP stock transfer horizon (external-procurement). Normally it makes no sense that you run SNP planning for current day/week/month.

After production planning run  (may be in APO PPDS or R/3 MRP), which is always inside SNP production horizon, you have production orders for the supplying plant.
Now you can run deployment, which is done on the basis of the supplying plant, and generally for the recent days.
So I don't think it's a good understanding that deployment is a supplement of SNP planning run. It should be done in a later phase, for example, after PPDS planning run.
Deployment will delete/reduce SNP stock transfer requisitions, and converts them to confirmed stock transfer requisitions/orders.

I don't think TLB does the same as VL02N in ECC ...

Best Regards,
Ada