Restricted content

Aqui ... só depois do login!

Analyze Picking Zeros

Purpose

Analyze the picking zeros given by the operators during normal picking, i.e., stock and JIT, including complete containers picking.

During picking, when an operator gives a zero, i.e., when not all merchandise is picked by the requested quantity, WPMS logs that information, so it can be analyzed on a new report located on

Application → Warehouse Managment → Goods Issue → Inquery → Analysis Picking Zeros (AL382).

This new report should display several info’s such as the article, quantity requested, quantity not picked, picked quantity, operator, final site, container, work unit (if available), etc.

Picking Complete Containers

On the following image there is a traditional report to pick a complete container. In this case the operator will give a zero, so the WPMS will log that zero, so it can be analyzed afterwards on the new report.

The action is registered and it can be seen and analyzed on the new report.

Application → Warehouse Managment → Goods Issue → Inquery → Analysis Picking Zeros (AL382)

Normal Picking

In the following example on normal picking, when the article is picked with partial quantities (if it is defined on work unit type to allow partial quantities), that will not be registered as a given zero and the remaining quantity will be requested on a new report action, as usual.

Only at this point, if the operator gives a zero, then the action is registered as a given zero, and it can be analyzed immediately on AL382.

Back Picking

This new log will also work on back picking work units, because the main reason to register this type of situation is to pick less than requested, so this feature also predicts back picking zeros.

In the example above, the operator decide to pick the article in teh end of the work unit, so he chooses back picking feature. After all articles picked, the article chosen to be in the back picking pops up.

Once again only at this point, if the operator gives a zero, then the action is registered as a given zero, and it can be analyzed immediately on AL382.

Container types sequence and transport accessories lists and sequences

Objectives

The goal of this guide is to provide a view of the new development about container types sequence & transport accessories lists and sequences.

Container Type

Container type definition

Every container type has now a sequence that has to be defined. This sequence will influence how container types are displayed (their order) on the operations in PDT select buttons of the containers.

To sort the operation, the system fetches the alternative containers defined for the processing container in question. After that, he calculates the best fit (which will always appear first) based on the quantities entered and sorts the rest based on the sequence field. In case of sorting operation the system does not calculate the best fit, it just sort the container types based on sequence.

Global → Global Application → Application → Master Data → Warehouse Management → Containers → Containers Definitions [AD012]

Transport Accessories Lists

To the Transport Accessories Lists was also added a sequence field in order to sort the transport accessories in PDT select buttons. But, in this case was also added a new Boolean field called Default value which must be unique per list/warehouse. In other words, on PDT selection of the Transport Accessories, that will be sorted by default value plus the sequence.

Global → Global Application → Application → Master Data → Warehouse Management → Containers → Containers Definitions [AD012]

Transfer Between Stock Containers

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:

Global Global → Global Application → Application → Warehouse Management → Tailoring→ Actions and Working Units → Work Unitid Manegement [AL118]

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

Maintenance with Quantities

Objectives

With this development, we want create a new action to insert the quantities need to do the maintenance task we choose. And with that, when we generate the statistics we have a better notion what was done by the user.

How to configure the system

Global → Application → Application Warehouse → Management Tailoring → Actions → and Work Units → Work Unit Manegement[AL118]

First we need to go to the transaction AL118, and choose our maintenance work unit type in this sample case it will be the work unit type “77 – VitaFilm”.

After we list we need to modify the work unit type:

In this screen we need give to the work unit type an Execution Queue a Priority, and for the statistics we need choose a Data Calendar and choose the Actions resume field.

After we confirm our changes we need to go tot he Actions screen . And here we need to field the our screen like the image below:

And with that we have our configuration done.