This 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) (Warehouse FG), and a shuttle truck will be driving the job-receipted pallets to the DC (Warehouse FG).
To load the pallets on the shuttle truck, a GIT OUT transaction must be performed.
Please ensure that the ‘move relationship’ has been configured within SYSPRO - https://datascopewms.atlassian.net/wiki/spaces/UG/pages/194150402/GIT+OUT+and+GIT+IN+both+warehouses+running+SYSPRO+DATASCOPE+WMS#Configure-the-%E2%80%98move-relationship%E2%80%99-within-SYSPRO.
If you don’t like reading, you can watch the video.
<link to YouTube video>
001_premium_GIT_IN_and_GIT_OUT_product_userguide_UG - v0.1.pdf
Try it!
The GIT OUT transaction is done on the mobile device.
To open the HTML 5 scanner window from the PC, go to the Main Menu at the top of your window and select Launch HTML5. This will open the HTML 5 sub-menu.
Click on the Launch HTML 5 icon.
Your HTML 5 scanner window will load.
Note: this is the window the warehouse staff will see on their scanners.
Search for GIT from the lookup icon.
Open the GIT OUT screen.
The GIT OUT screen will open on the Start TAB.
The source (production warehouse) and target warehouse (central distribution center) will appear in the drop-down list.
Select the Create New button to create a new GIT OUT transaction.
Note: a GIT Temp Reference number will automatically appear on the screen in the GIT Temp Reference in progress field.
Select Next to continue to the GIT Out TAB.
Start to scan all the TrackIDs (received via the Job Receipt process.)
Note: As you scan more TrackIDs, the No Pallets field will increase.
The details of the scanned TrackIDs are visible on the Summary TAB.
If an error was made, a TrackID can be deleted from the list.
Select the TrackID on the Summary TAB
Select the Delete button.
The list of TrackIDs visible in the Summary Tab has been assigned a temporary GIT reference number. Therefore, the Operator can exist and re-enter the screen at any point before completing the GIT.
When re-entering the GIT Out mobile screen, they can just select the temporary GIT reference number from the GIT Temp Reference in progress drop-down on the Start TAB.
Once the truck is full, the GIT Out can be processed.
Select the Create GIT button on the Summary TAB.
A pop-up message will appear, asking whether all TrackIDs have been scanned.
The Printer pop-up will appear. Select Apply to print the GIT Out document.
Note: Ensure the System Settings are pointing to a physical label printer to print the GIT Out document. To view or update this, go to Settings / Printers. You can use the filter icon to locate the <which setting> System Action.
The GIT Out reference number is created automatically.
A uniquely numbered GIT Out document will print.
A GIT Out document reprint can be done via the PC screen. On the Main Menu, browse SCT & GIT / Reprint GIT Document.
When the GIT Out document is reprinted, a large REPRINT message will be displayed on the document. This is to indicate that it is a duplicate copy. This is required for security reasons.
Note: Ensure the System Settings are pointing to a physical label printer to print the GIT Out document. To view or update this, go to Settings / Printers. You can use the filter icon to locate the GITOUTDOCUMENTPRINTING System Action.
The TrackID on the GIT Out document will become INACTIVE in DATASCOPE WMS.
GIT details can be seen on the TrackID History. On the Main Menu, browse to KPI Dashboard & Reporting / Standard Reports / TrackID History
The GIT Out transaction is also automatically performed in SYSPRO.
To view this in SYSPRO, perform a GIT Reference Query. Browse to Inventory / Goods in Transit / GIT Reference Query
