Tag: logistic

Generating letdown working units in PC

Objectives

With this development, we want to create new transaction that allow to create letdown working units PC transaction.

Articles – Logistic Data

New options were added to the Spaces Assigned Permanently report (Add or Modify). In this options, the dropbox Letdown Types which is placed in the group Data for Picking Space Replenishment has now two more choices:

  • Suggested Full Picking: suggests the calculated quantity defined in the master data of the article.
  • Missing Full Picking: require to declare the missing quantity.

The goal of these types of letdowns is to allow the calculation of the quantity of occupancy of the spaces in relation the quantity of unit instead of the quantity of containers available.

As a result of these changes a new field has been added – UM to Calc. Quant. – select the unity mesure to calculate when one of the options previously described is picked.

Global Application → Warehouse Management → Operational Definitions -> Articles – Logistic Data -> Articles – Logistic Data [AL077]

Working Unit Types

A new letdown class of work units to ensure that the new type of work unit will have its own priority and will be distinguishable from the priorities of the other letdowns work units.

Global Application → Warehouse Management → Goods Issue → Tailoring -> Actions and Working Units-> Working Unit Types [AL117]

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

Generating Letdown on Demand

Global Application → Application → Warehouse Management → Goods Issue → Orders to be Processed → Generating Letdown on Demand [AL383]

The report will present the following selection parameters:

  • Warehouse
  • Stock type
  • Article
  • Unit of measure
  • Flow
  • Space type
  • Space
  • Space sequence
  • Spaces to create letdowns
  • Occupation rate

This report will have the following information:

→ Header:

  1. warehouse
  2. stock type
  3. space sequence
  4. work.Unit T. ( input required ) for Working Unit Class 45 – Letdowns on Demand.

→ Details:

  1. Space type
  2. Space
  3. Article
  4. Unit of measure
  5. Sub-spaces number
  6. Number of containers in Picking
  7. Number of containers in buffer
  8. Number of containers to putaway
  9. Number of containers in letdown
  10. Number of containers to letdown
  11. Occupation Percentage (%)

Display Space

Options→ Display

Current container in space

Options→ Current Containers in Space

Doc. Creation Letdowns

Options→ Doc. Creation Letdowns

After the operator selected the spaces that should be refilled and execute the option “Generate” a job will be created. During the execution of that job.

The priority of each work unit created will depend on the number of containers to let down. and it will be calculated using the following formula:
priority of work unit = “default priority” + “round up to the next highest integer”(fulfilment ratio of space * 10) .

View Working Units Management

Global Application → Application → Warehouse Management → Working Units Management (RF)> Working Units Monitor [AL055]

In Al 055 screen you can see if squats created for the type of work unit chosen and the priority.

  1. – Number Udt
  2. – Priority Udt
  3. – previous Space Type
  4. – Previous Space
  5. – Current space Type
  6. – Current space
  7. – Operator
  8. – Date

WU Letdown with calculated quantity:

Letdown – Buffer to picking

Here it will be shown how the PDT works when a unit of letdown is received.

After accept the working unit it will appear a screen to insert the label of the article.

Afterwards the verification, depending on letdown type, it will show one screen to state the quantity of the article to make the letdown:

  • Suggested Full Picking/ only specific quant. : suggests the calculated quantity defined in the master data of
    the article:
  • Missing Full Picking: require to declare the missing quantity.
  • Others types letdowns: it only requires the barcode space.

If the original container is not exhausted, the operator MUST confirm the pallet in buffer in the next step. This is only applied to suggested and missing letdown types.

Transition

To execute this task, the previously steps are similar, we just changed the space value from picking to the maintenance zone(04 to 09). After this was created another working unit to pass from maintenance zone to picking.

  • Missing Full Picking: require to declare the missing quantity.

2 º Create new letdown working unit from the transition space to the picking place.