TrackingIDConsolidation [WMOVE003]
DATASCOPE.SDK.BusinessObjects.WarehouseMovements.TrackingID.TrackingIDConsolidation()
Performancing a TrackingID Consolidate
Returns:
Response – Success
Response Result set to True
Response Message - "Quantity: XXX1 of StockCode: XXX2 moved from Tracking ID: XXX3 to Tracking ID: XXX4”
Response - Failure
Response Result set to False
Response Message - Error generated
For a detailed overview of working with DATASCOPE PREMIUM WMS Business Objects, refer to E.Net Business Objects
If you don’t like reading, you can watch the video.
Description
Performancing a TrackingID Consolidate
Code | WMOVE003 |
---|---|
Name | TrackingIdConsolidation |
Module | WarehouseMovements |
Functional Area | TrackingID |
Name Space/Class | DATASCOPE.SDK.BusinessObjects.WarehouseMovements.TrackingId.TrackingIDConsolidate() |
Release Date | 1/1/2025 |
Release Version | v24.3 |
Prerequisites | None |
---|---|
SYSPRO Objects | Transaction.INTMB, Transaction.INVTMO |
Parameters
Name | Description | Mandatory field | Data Type | Default Value |
---|---|---|---|---|
pTrackingId | WMS TrackIs to consolidate stock From | Yes | string | <blank> |
pDestinationTrackingId | WMS TrackId to consolidate stock Onto | Yes | string | <blank> |
pStockCode | Stockcode on the TrackId to consolidate | Yes | string | <blank> |
pLotNumber | LotNumber on the TrackId to consolidate - Only required if the stock is lot traceable | Conditional | string | <blank> |
pQuantity | Quantity on the TrackId to consolidate | Yes | decimal | 0 |
pConsolidateModule | BIN_TO_BIN","Module to reflect against the TrackId history record | No | string | <blank> |
pDestinationHash | Destination Hash to validate against, if any | No | string | <blank> |
Validation
The following validation will take place.
Technical Specification
<sample code>
Example to follow
In this example, we will create a TrackID Consolidate and call the Object from the application.
We are interested in seeing which Properties Mandatory fields are required for this Business Object. These will be the basic Properties that we must set up on the Object.
Another important thing to take note of is the required SYSPRO Objects. When calling a DATASCOPE WMS Object, it might or might not call a SYSPRO Object in the background. For the TrackIConsolidation Business Object, it can either be the Transaction.INTMB or Transaction.INVTMO SYSPRO Objects. Therefore, if we post a TrackID Consolidate, TrackIDs that are in different Bins can either be invoke a SYSPRO Bin transfer (Transaction.INTMB), or if they are in different Warehouses, we will invoke a Warehouse transfer (Transaction.INVTMO).
It is, therefore, always important to take note of the SYSPRO Objects required, as the Operator doing the post must have the necessary permissions in SYSPRO.
Testing the BO (only for Internal/DSP use)
The Business Object Harness application should be used to assist in troubleshooting and testing any of the DATASCOPE WMS Business Objects.
Ensure you follow the installation process to install and configure the Business Object Harness application.
To test the Business Object
o Open the Business Object Harness
o Enter the Company ID you would like to login to, followed by a valid Operator, along with its password and company password (if any). Clicking the Login button will then attempt to log in to the system using the WebAPI.
o The first step in posting an object is to select and add it to the main content window.
o Now you are ready to start testing the Business Object.