Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

We apologize for the inconvenience. There is no F1 help available for this screen at the moment.

Please refer to the user manual or contact your local DSP (Datascope Solution Provider) for further assistance with the functionality and usage of this screen.

If you believe the absence of F1 help for this screen is an error or have any additional questions, please don't hesitate to contact our support team. They will be glad to assist you in any way they can.

Thank you for your understanding and patienceThis process moves the inventory of the TrackID onto a GIT Reference number to be moved to the Distribution Warehouse.

At this stage, the product will be ready to be moved to the central distribution center (DC), and a shuttle truck will be driving the job-receipted pallets to the DC.

To load the pallets on the shuttle truck, a GIT OUT transaction must be performed.

Info

This would typically be done on the mobile screen, as it will speed up the process when scanning the stock into the shuttle truck. Refer to GIT Out [GIT042]

  • Select the Source warehouse from the Source drop-down.

  • Select the Target warehouse from the Target drop-down.

  • Create a GIT Temp Reference number by selecting the Create new button next to GIT Temp Reference.

  • The Operator can Exist the screen at any time. When entering the screen again to continue elect the GIT Temp Reference number from the GIT Temp Reference in progress drop-down.

  • Select the Refresh icon to load the data grid.

  • Start entering the TrackID that are physically being moved to the target warehouse. On the pc-screen, refer to the PalletNumber column.

  • Enter the mass in the Total Mass field.

  • Select the Create / Add to button in the bottom right-hand corner.

Page Tree Search
rootPageF1 help

SPECIAL FEATURES

  • NoneA GIT Out document reprint can be done via the PC screen. On the Main Menu, browse SCT & GIT / Reprint GIT Document.

TECHNICAL

  • None

SYSPRO REQUIREMENTS & Business objects used

  • NoneThe GIT Out transaction is also automatically performed in SYSPRO.

REFERENCE

GIT030