When working with the Process Transport Task Part through WaDaCo, I’m noticing some strange behavior in which the Automatic Value selections are not being considered.
Environments (2 different environments):
Cloud 22R2- UPD3
Cloud 22R2 - UPD4
Date Set-up:
- Transport Task Consolidation
- Part By: Multiple Parts
- Source By: Single Ref 1
- From Location By: Warehouse
- To Location By: Warehouse
- Currently not using Drop-off or Forward to Locations
- Inventory Parts are Lot Batch Tracked (Order Based)
- Warehouse Data Collection Configurations (copied from the originals and I’ve made changes but similar behavior regardless)
- Start Warehouse Task
- Start Transport Task
- Process Transport Task Part
Overall Scenario:
The scenario includes a user manually creating a transport task for multiple reserved line items thorough the warehouse that will eventually be used for a Shop Order. Once the Transport Task is created, the user should be able to move this material via Transport Task to a staging location where it will ultimately be Issued/Pick from the Shop Order.
Process Steps:
- Select multiple items in Inventory Part in Stock Reservations Window
- Select Move with Transport Task
- Once Transport Task is created, go to WaDaCo emulator and select Start Warehouse Task (already released based on BDR)
- Configuration rolls the users into Start Transport Task then ultimately into Process Transport Task Part
- Once in Process Transport Task Part, it seems the Automatic Values have no control over the configuration:
- For example, a vast majority of the data should be able to be Defaulted or selected as Fixed from the already created Transport Task, however these do not work. The user must manually select the LOV and select the items, even if the Automatic Value is set to Fixed or Default. The application does allow the LOV to Auto Pick, although that doesn’t seem like the correct setting in this scenario.
- The 2nd issue is that the user is prompted for many Data Items that are not Process Keys (i.e. W/D/R, Engineering Change Level, Activity Sequence, Handling Unit ID, Alternative Handling Unit ID, SSCC, etc. etc.) This occurs regardless of any settings defined in the configuration.
Is this behavior a limitation of the configuration somehow (i.e. doesn’t support the consolidation we have defined) or is there a bug here?
Best answer by Dario Zani
View original