SYSPRO
All transactions between SYSPRO and DATASCOPE WMS are posted via the SYSPRO E.Net Business Objects layer.
The Operator must already To add a user to DATASCOPE WMS, they must first be created in SYSPRO but must still be and linked to the E.Net Business Object layer, which the operator will be required to use for . This integration ensures that all SYSPRO and DATASCOPE WMS transactions are accurately processed. The user will then be able to perform their daily activities within DATASCOPE WMS using the E.Net Business Object layer.
| Info |
|---|
If you don’t like reading, you can watch the video. |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Try it!
Open SYSPRO 8
Browse to Admin e.net License Apportionment under the Main Menu Program description / Administration / e.net Solutions / Admin e.net License Apportionment
The Apportion e.net Licenses – Business Objects screen will open
Update the number of seats for each applicable business object for each user
| Info |
|---|
Note: use the matrix below that indicates which DATASCOPE WMS transaction requires which business object within SYSPRO |
FASTTRACK Transactions | SYSPRO Business Objects |
Bin Transfers | InvTransaction |
Check Out Put Away | InvTransaction |
Cycle Count Adjustments | InvTransaction |
Goods in Transit In | InvGoodsInTransit |
Goods in Transit Out | InvGoodsInTransit |
Job Issues (manual) | WipShopFloor |
Job Picking | WipShopFloor |
Job Receipts (no kit issues) | WipTransaction |
Job Receipts (with inspection) | WipTwoStageReceipt |
Job Receipts (with kit issues) | WipTransaction WipShopFloor |
Job Returns | WipTransaction |
Pallet Consolidations | InvTransaction |
Pickface Replenishment | InvTransaction |
Purchase Order Receipts | PorTransaction |
Purchase Order Receipt (with inspection) | PorTransaction InvInspection |
Put Away | InvTransaction |
Quality Release | InvInspection |
Receipt Palletization | InvTransaction |
Sales Order Picking | SorTransaction |
Stock Take Adjustments | InvStockTake |
Select Save and exit
| Info |
|---|
When new operators are created, ensure that the Operator name is the same as the Network username. The E.Net Business Object layer uses the Network username and you might experience login issues if these two aren’t the same. |