> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-for-im-wm-strm/app-master-data/screen-framework/features/displaying-alternative-units-of-measure.md). # Displaying alternative units of measure By default, PreBilt apps display quantity and unit of measure (UoM) fields in either the **base unit** for a material or the UoM from the relevant document (e.g., transfer order, reservation, order, or delivery). This feature allows you to configure alternative UoM conversions by app transaction and screen, following an **AMD-controlled sequence** of UoM types (e.g., WM unit, Issue unit, Planning unit, Base unit). When PreBilt generates a screen, it checks the configured UoM sequence to determine if the material is maintained for a specific UoM type. If a match is found, the system converts the **base** or document quantity into the specified UoM from the material master. **Example:**\ If a material has a Base UoM of **Eaches** and an Issue UoM of **Cases**, and the sequence is set to **Issue → Base**, the app will display the quantity in **Cases** instead of Eaches. This feature applies to both input and list screens. The UoM Conversion AMD element specifies which quantity and UoM fields should be converted for each app screen. A global default sequence (*\_GLOBAL\_DEFAULTS*) exists in AMD, but app-specific sequences can also be configured. There is a global default sequence in AMD for “\_GLOBAL\_DEFAULTS” but an app specific sequence can also be setup. {% hint style="info" %} **Note** For jumps to other app transactions, the “UoM” does not jump automatically. Suitable AMD settings need to be setup consistently between the “from” app transaction and the “to” app transaction. {% endhint %} ## UoM determination sequence A global UoM sequence can be maintained in AMD for the app transaction *\_GLOBAL\_DEFAULTS*. The configuration element "UOM\_SEQ" allows you to define a sequence of UoM types (e.g., WM unit, Issue unit, Planning unit, Base unit). By default, the global sequence is used unless a specific app transaction sequence is configured. Each app transaction is typically provided with the UOM\_SEQ configuration element but left blank. If needed, you can define a custom sequence to override the global default.
An initial sequence will be provided in the core package but can be changed to suit requirements. {% hint style="info" %} **Note** It is advisable to always ensure that the last item in the sequence is “BS” for Base Unit of Measure (although most apps will make that assumption if it is not there). {% endhint %} ## UoM conversion If a specific app transaction requires the quantity to be converted to an alternative UoM then the UoM Conversion AMD element needs to be maintained. This is done for each specific screen required and includes the specific fields for both 'Quantity' and 'UoM' that need to be displayed with the converted data.
Each column on the ‘UoM Conversion’ table is represented by the options below:
OptionUsageComments
AMD Screen IDIdentifies the AMD configuration elementThis field identifies the specific screen (configuration element) that the conversion is valid for.
Screen: Qty FieldThis is the field that will display the converted quantity.This needs to match field in the AMD screen.
Screen: UoM fieldThis is the field that will display the converted UoM.This needs to match field in the AMD screen.
Data source: Material fieldField that identifies the material number to be used for the conversion.This needs to be a valid field from the screen that contains the material number.
Data source: Plant fieldField that identifies the plant to be used for the conversion.This needs to be a valid field from the screen that contains the plant.
Data source: Qty fieldField that identifies an alternative quantity to be converted from.This is only needed if the Qty field being used is not a “real” field in a data structure or another quantity field is to be used as the source.
Data source: UoM fieldField that identifies the UoM to be converted from.This is only needed if the UoM field being used is not a “real” field in a data structure or another UoM field is to be used as the source.
UoM Type Over-rideUoM Type to by-pass / override the sequence.This allows you to specify specific UoM type and therefore completely ignore the sequence.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.theconfigteam.com/prebilt-for-im-wm-strm/app-master-data/screen-framework/features/displaying-alternative-units-of-measure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.