The main objective of this development is create a functionality that allows the users put away the containers in two steps.
We create a new functionality that allows the user transport the containers from the gates to a transition area, and after that the system will update the put away document so the start point in the document is the transition area where the container is now, making possible to use the normal put away working unit to make the second step, from the transition area to the container final place.
Create the new working unit type
Global -> Global Application -> Application -> Warehouse Management -> Tailoring -> Actions and Working Units -> Working Unit Types [AL117]
The new working unit type should belong to the class 52 – Transport Containers.
Global -> Global Application -> Application -> Warehouse Management -> Tailoring -> Actions and Working Units -> Working Management [AL118]
In this screen we should define the Execution Queue and Priority.
We should go and define the actions like is shown in the picture below.
As you can see on the picture is possible to define how many labels can be declared in the working unit action to declare labels, in this case it will be three.
After this definitions we are just missing the connection between the working unit type and the internal document type.
Global -> Global Application -> Application -> Warehouse Management -> Operational Definitions -> Determinations -> Working Unit Type Determination [AL092]
In this sample we use the determination by Warehouse and Document Type but you can choose other options.
As you can see we link the working unit type created before with the new internal document 91 – Transport Containers.
After this definitions created we can start to use this new working unit type. This working unit is created on demand, and is implemented in the menu MNVAPRFS02 – Menu RF LetDown.
In the PDT menu MNVAPRFS02 – Menu RF LetDown we have a new action Container Transport, with this new action we are going to create a new working unit from the type created before.
When the user chooses this new action the next screen will appear.
On the first screen the user can choose the labels to put away in a transition area. Here as you can see we have three inputs because, in the first action we defined three lines, the user don’t need to fill all the three inputs but is mandatory to fill the first one.
The chosen labels should have a valid put away document so they must be with the status Aloc. Conf, in the report AL046.
In the next screen we can see the final destination to the labels.
After the labels been chosen to put away the user should click on the button CONF.
Here in this screen the user is has to declare the space, this space should be link to the space class 08 – Transition.
The number of label inputs in this screen is equal to the number of missing labels to declare. So if in the first screen the user declared three labels so here as you see we have three labels input fields.
But in this specific place we just want leave one of the labels, so the system now will show the screen with the final destination for the remaining labels.
As you can see and because before we declare one label, now we just have two labels input fields. If we want to leave all the containers except the first one we already leave in the other place. We can declare the missing two labels or don’t declare any label. When the users don’t declare any label the system assumes that all the missing labels are to leave in the declared space.
When we leave all the labels in the transition areas the system will close the working unit.