0000088: Optimize "whole LU" window in touchscreen apps

Support > Tracker

View Issue Details [ Jump to Notes ]

[ << ] [ >> ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000088

BPS V2

Change Requests

public

2010-07-23 07:38

Reporter

pkoch

Assigned To

pkoch

Priority

normal

Severity

minor

Reproducibility

N/A

Status

assigned

Resolution

open

Platform

Windows 7

OS Version

SP0

Product Version

2.4.0

Target Version

Fixed in Version

Summary

0000088: Optimize "whole LU" window in touchscreen apps

Description

Currently, the inputs are preset exactly with the planned quantity.
It would be better however to calculate and insert the max units.

Example:

Planned = 50 and LU/TU = 48.
Old it would preset the TU input with 50.
New is should preset the LU input to 1 and the TU input to 2.

This basically also applies to the "correction" window, however in practise there would hardly ever be any whole LU's.

Special case: When planned is TU's and LU/TU is 1 it does not make sense to calculate and display LU's because that could confuse, so it would be better to still display the original planned unit in such cases. Same applies when the planned unit is CU's and the factors CU/TU and TU/LU are 1. Here is a possible algorithm:

  - If both, LU/TU and CU/TU are each 1, just fill in the OU input as before.
  - In other cases calculate max units.
  - If LU/TU = 1 and order unit = TU, fill the calculated LU's into TU input
  - If CU/TU = 1 and order unit = CU, fill the calculated TU's into CU input

Relationships

Notes
There are no notes attached to this issue.