View Source

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.

Syensqo IS - Customer Support > 4. Transit Inventory in Dynasys > image2021-5-4_10-24-47.png

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

What the Shipping site is seeing in Dynasys	April	May
Actuals Shipped	100 To

What the receiving site is seeing in Dynasys	April	May
In Transit from SAP		100 to
Projected Inventory	0	100 to

> 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).

Syensqo IS - Customer Support > 4. Transit Inventory in Dynasys > image2021-5-4_10-26-33.png

What the Shipping site is seeing in Dynasys	April	May
Actuals Shipped	100 To
Planned shipment		50 To

What the receiving site is seeing in Dynasys	April	May	June
In Transit from SAP		100 to
Transit Stock	100 to	50 To
Receipt Plan			50 To
Projected Inventory	0	100 to	150 To

Types of Flows in SAP and interface design

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

(comment différencier STO des Unlinked?)

Standard transfer of stock between 2 sites

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

> Unlinked flow (Intra GBU)

> Unlinked flow (cross GBU)

> WP1 - PF1

Design of the In Transit from SAP in Dynasys

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.

Syensqo IS - Customer Support > 4. Transit Inventory in Dynasys > image2021-5-4_14-44-22.png

Sales order 2916556/ Outbound delivery 0085822932

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

Syensqo IS - Customer Support > 4. Transit Inventory in Dynasys > image2021-5-4_14-59-26.png

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