Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Retail Merchandising System (MOSC)

clarification on price marking functionality e.g. xxx per 100ml

May 23, 2017 4:17AM edited May 24, 2017 12:08PM in Retail Merchandising System (MOSC) 6 commentsAnswered

In many versions of RMS including v16, there is price marking functionality.

This allows entering a measure of each, measure of price and unit of measure in the location ranging screen (held in ITEM_LOC) and extracted when creating a ticket type with detail of UOM.

In v14.1 the input fields are labelled like this

In 16.0, these fields have been relabelled as follows although the calculation to work out the unit price is the same in tcktdnld.pc

So the "measure of price" has now been replaced by the label "Ticket Price".

This doesnt make sense as tcktdnld uses the selling unit retail to calculate the unit price. Is this a change of functionality.

Tagged:

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month