article - IsRetail

Objectives

This development was created improve two aspects from WPMS. First when we put away multi article containers and second when we preform the let downs.

In this development we made possible put away expedition containers when executed. This mean after executed we can change the expedition container from the shipment place to a buffer place.

All the multi article containers it will be put away in buffer places, this means the picking place it will stay assigned to just one article.

Create multi article put away determinations.

Global Application -> Application -> Warehouse Management -> Operational Definitions -> Determinations On Allocation of Multi-item Containers [AL380].

To put away this containers we need a set of rules. To create this set of rules we gone need click in the button add .

Here we can create our rules:

Site → Here we should fill the Warehouse where this rule apply.

Sequence → This field should be fill in a sequential way. So to the same Site we can’t have 2 sequences with the same value

To the system could make the right space determinations, it will be needed to fill the fields in this box.

Is not mandatory fill any of this fields, and we advise to create a rule without any of this fields fill, in this way we gone have a default rule.

In the next box the system is gone find where this rule should be used, and how is used

All the fields in this box are mandatory.

Priority → This field is gone set the priority of the rule, where the smallest value means high priority

Class of use → Here we can set the rule to stock containers, expedition containers or for both

Allocation rule → The allocation rule to put away the containers.

Space Type, Space → This it will be the reference space.

After we create all the rules the system when is going to try put away the container this way:

→ The system is going the get all the articles from the container, and also the containers settings
→ The system is going to get all the rules for multi article containers
→ Now the system is going try to match the articles and container definitions, with the rules we create.
→ With all the matches the system is going to choose the one with the priority value smaller.

New and changed reports.

Global Application -> Application -> Warehouse Management -> Containers Management -> Transfer the Container to Another Place [AL043].

In this report it will be possible transfer expedition containers to another place. Is not possible transfer the container to picking places, the expedition containers just can be placed in buffer places.

Global Application -> Application -> Warehouse Management -> Containers Management -> Containers by picking Space Summary [AL053].

In this report we just add a new column where we show the amount of expedition containers in the space.

Global Application -> Application -> Warehouse Management -> Containers Management -> Containers by picking Space Summary [AL053].

In this report it was removed the column with the articles, and now show all the containers presents in the space.

To see the articles present in the container you should click in the button . To hide again the articles you should click in the same button.

Global Application -> Application -> Warehouse Management -> Other Movements -> Spaces Cycle Counting [AL073].

In this report we add an image like is showing above to advise the user that in this space we have expeditions containers and we can’t make cycle counting to this place

Global Application -> Application -> Warehouse Management -> Containers Management -> All Containers in Spaces [AL381].

Here we can check all the expedition and stock containers there are in the chosen space.

Put away expedition containers.

Global Application -> Application -> Warehouse Management -> Goods Issue -> Delivery Docks [AL063].

Is in this report where we can put away the expeditions containers. To do that we just need click in the button . Also we need to have the document 49 defined to create work units, this is mandatory to put away expeditions containers, to have a work unit.

To transfer again the containers to the dock we have two ways:

→ With transport planing, just go to the tours transaction and force a space to the tour.
→ Without transport planing in the detail of AL063 choose the dock and save.

Cycle Counting.

When we are making a cycle counting to a multi article container the system will ask to the quantities for all the articles in the container.

It will not be possible create cycle counting to the spaces where we have expedition containers.

Let Downs.

When the system creates a new let down to a container, this container is just defined multi article container just in the case there are two or more articles in the container with quantities.

The let downs to this kind of containers it will be always by book quantity or specific quantity, and the containers just come back to the buffer if at least there is one article still with quantities.

When we start the let down the system checks if we have a container with more than one article. And then the system goes work in the follow way:

1 → If there are more let downs to the same container we going to join all the work units to our work unit.

2 → To all the articles in the container we need to check if in the report AL077 logistic definitions, is define to violate the extracting rule.

3 → We gone find the created let downs to the other articles in the container with the selected field to violate the extracting rule.

4 → Transfer the book quantities from the other containers to our container, we transfer the most quantity we can, if we couldn’t transfer all the quantity that container will be a let down with the remain quantity. If all the quantity is transfer the other container it change the status to in place.

5 → Our work unit will do all the let downs to all the articles we transfer the quantities.

Purpose

Transfer merchandise between stock (receiving) containers. This new functionality must allow the transfer between two containers, the origin or source container, to target container, updating the transferred quantity in each container.

The two containers must have the same stock type and they must belong to the same operation flow.

If an article is managed with expeiration date, there’s the possibility to transfer quantity to a container that have the same expiration date or if they are different, the target container’s expiration date will have the minimum expiration date of them. If one of the containers have a date lower that allowed, that container will not be considered and an error message will pop up.

The origin label is always manadtory, and the container must be available and in place to execute the task, no matter where’s the container in the warehouse wise.

The target label is mandatory, if the operation assigned to the origin container, has defined that the label is anonymous, if not, the target container label is not mandatory, which the system will produce and print through the access of label numbering.

It is possible to transfer a complete container to another one, or just the selected articles in the container, eitherway the quantity considered to transfer is only the available one, i.e, “Available Quantity” must be higher than “Reserved Quantity”.

This functionality is “On Demand”, which means that only users that are allowed, through RF menu permissions, will be capable to perform it.

RF Main Menu

This functionality is “On Demand”, which menas that only allowed users will have permission to perform it. The action “TRANSF.BETWEEN CONTAINERS” is available on the menu action “MNVAPRFS7A” (MISCELLANEOUS).

Declare labels

To begin the process of transfer, the origin label is mandatory and the container assign to it must be available and in place, no matter where in the warehouse. The target label instead is mandatory only if in the operation definition the “Label anonymous” is set, which means the user must supply the label since it must be already printed. If the target label is not assigned to a container, a new one will be created and allocated.

Both containers must have the same stock type and the same operation flow. The expiration date control is made considering the definition made on AL118, which have two choices:

both contianer must have the same expiration date (4090)
the target label will keep the minimum expiration date of the two containers (4100)

Either way, in both cases both containers must have valid expiration dates to perform the transfer process.

If the totality of container is chosen, all articles in the origin container will be transferred to the target container, which will be updated considering all the validations written so far.

If the user does not supply the target label and the operation definition is not “Label anonymous”, the system will get a number for the label, and print it. If in AL118 is defined to confirm the new label, the user must supply the “just new printed” label to continue the process. This validation is needed to check that the user will transfer the goods to the right container.

Declare Article to Transfer

In the following screen, the user can supply the article code, or the article barcode, which will be decoded. The article must be in the origin container and must have available quantity to be considered. In the previous screen, on the declaration of labels, if the origin container only has one valid (with available quantity) article, this screen won’t appear and the user can declare the quantitis to transfer immediatly.

If the user cannot suplpy the article code or the barcode, he still can list all the valid (articles with available quantity) articles present on origin container, for that he must select the menu option “Article List”. This list will display all the valid articles present on container, so user can choose the next one to transfer.

The list is displayed under links so the user can click directly on the article to transfer.

There are a menu option to “End” the transfer process that will end the work unit.

Declare Quantities to Transfer

Finally on this screen the user must supply the quantites from the selected article that he want to transfer. If the operation predicts to supply the second quantity, the field will be displayed and it will be mandatory. The quantities the user suplpy are request on the unit of measure defined for the operation assigned to the article’s flow.

The user must supplly a quantity equal or less than the available quantity present in the container. When all quantity, from all articles are transferred, the origin container will no more be available and the work unit ends.

When the user declares a quantity, the next action can be one of the following:

if the container only have a valid article, it will be showned to transfer; the user can end the work unit whenever he wants.
if the container have more than one valid article, the screen to declare article will be showned; the user can end the work unit whenever he wants.
if the user declares all the quantity of an article and the container has no more articels, so the work unit will end.