• Introduction - Types of Transit inventories in Dynasys

In Dynasys we manage 2 types of Transit Inventory:

> The One from SAP, what we have currently in transit between 2 sites at the moment we make the interface. This one is in ETA, the quantities are visible in arrival date (the month it is expected to arrive, data from SAP) and (depending on the design with the GBU) considered as an input of stock within that month.

example:

Shipping the 15Th of April 

Current SAP shipment planned to be arrived the 20th May

Current day is the 25th of April

Lead time in Dynasys is 1 month

> The one calculated by Dynasys, which is the quantity between 2 sites at the end of the period. It is not included in that period's projected inventory. It is visible in the Receipt site location, and calculated based on the Dynasys lead time in month(s).

• Types of Flows in SAP and interface design

> Stock Transfer Order ("Linked flow" intra GBU)

Standard transfer of stock between 2 sites in SAP. We have one single element which is the PO.

For receiving date, we take in consideration:

1. The confirmed date in the PO

2. Or, if no confirmation, the one from the Schedule delivery

The quantities are considered as "In-Transit" until the Goods Receipt in SAP.

Dates in past (up to 3 months) are considered in DIP in the current month .

> Unlinked flow (Intra GBU)

Unlinked flows are separated Purchase orders (to a Vendor X) and sales orders (to a customer Y) between two sites.

Example: Nota Fiscale Brazil

Today, we are not able to make the link easily.

For Dynasys project, we have implemented a specific Table in SAP to try to make the link between for "1 material-1 receiving Site" (table named ZMATVENDOR). This table is managed by SBS manually for the moment (automatic feed in progress).

Process to feed Dynasys:

Once the GI has been processed, we take the delivery date from the Outbound delivery document as the reference for Arrival date.

Example: Novecare - Fentamine from Asia 8160 to Itatiba Brazil 8227

In MD04 we retrieve the original PO - with the requested delivery date.

The shipments has been done, the delivery date from the sales order is 17th May.

This one is the reference for Dynasys:

Potential Issues:

Delivery date from the sale order is the reference.

> BW will consider Actuals Receipt when this delivery date will be past, even though the order is still in transit. => In Dynasys we don't see the InTransit - the quantities are missing and requested to be replenished in the planning.

> BW will consider In-Transit when this delivery date will be in the future, even though the order is already arrived. => In Dynasys, we consider those InTransit on top of the inventories (and already arrived!)

> Unlinked flow (cross GBU)

As all GBUs are not in the same database, it appears complicated to include the cross GBU as "In-Transit" field in Dynasys. We are limited by the data available (SKUs and Sites).

Example: TS and Novecare flows - TS is in DIP2 and Novecare DIP 3

=> That's why we have decided to exploit those Cross-GBUs flows as "External Purchase Order" for the receiving site. The limit is we don't know if products are "In-Transit" or "still to be shipped".

> WP1 - PF1 

Today with SAP we are not able to make the link between Material@SIte PF1 and Material@Site WP1.

It means we cannot define the InTransit quantities.

=> Those flow are considered as "External Purchase orders", whatever it is shipped physically, or not yet shipped. We will take the visibility of Purchase Order in MD04 at receipt site.

• Actuals Transit (end of month)

We can get from SAP the Actuals end of month Transit only for Standard stock transfer orders.

The Transit for "unlinked" flows and WP&-PF1 flows are not available.

For SILICA we have developped a specific design (inside Dynasys) in order to get those missing data.

=> We archive the picture of the last day of the month 

If necessary, we can develop it for other GBUs

• BW Report for Finance purpose which is different from Dynasys perspective

There is en existing BW report for Transit stock in a Financial perspective. 

This report makes the difference between Outbound In Transit, and Inbound In Transit. But we do not have the information of the 2nd Site.

Sales order 2916556/ Outbound delivery 0085822932

For finance, as long as the revenue recognition is done, this is not outbound GIT in Korea (8279)

For S&OP purpose, we have developed a specific interface calculated thru BW.

Link to Interface documentation

Link to the Planning Elements interfaced and rules