Explore topic-wise InterviewSolutions in .

Auto generation or auto printing of TICKETS is the process by which a specified ticket type is automatically PRINTED when the item associated with it through a PURCHASE order gets

• Approved
• Received
• Undergoes a permanent price change

Auto generation or auto printing of tickets is the process by which a specified ticket type is automatically printed when the item associated with it through a purchase order gets

The setting of the format of the TICKET or making the ticket type as well as MANUAL initiation of requisitioning a ticket happens in RMS. While the actual printing of the tickets are done by an EXTERNAL application viz; AVERY

The setting of the format of the ticket or making the ticket type as well as manual initiation of requisitioning a ticket happens in RMS. While the actual printing of the tickets are done by an external application viz; Avery

In RMS the ticketing FUNCTIONALITY allows the retailer to specify the type of INFORMATION the TICKET should contain as REGARDS the product.

In RMS the ticketing functionality allows the retailer to specify the type of information the ticket should contain as regards the product.

A ticket contains important information about the PRODUCT. Information like the ITEM code, price of the product, PARTICULAR instructions for HANDLING the product, ETC:

A ticket contains important information about the product. Information like the item code, price of the product, particular instructions for handling the product, etc:

A ticket is a tag that is AFFIXED to an item in the store. The PURPOSE of the ticket is to CARRY information on the item that cannot be usually DEPICTED on the PRODUCT.

A ticket is a tag that is affixed to an item in the store. The purpose of the ticket is to carry information on the item that cannot be usually depicted on the product.

The USE of Pending Merchandise Hierarchy is to change the structure of the merchandise hierarchy itself.

For example:

SUPPOSE you have the following hierarchy:

Dept 1: Class 1001: SUBCLASS 101

Dept 1: Class 1002: Subclass 201

Dept 2: Class 2001: Subclass 211

Now suppose you want to move Class 1002 into Dept 2.

Using Pending Merchandise Hierarchy you can make this move so the structure will look LIKE this:

Dept 1: Class 1001: Subclass 101

Dept 2: Class 1002: Subclass 201

Dept 2: Class 2001: Subclass 211

A item reclassification is different. It could be used to move the items between departments, but it would not affect the structure of the merchandise hierarchy itself.

The use of Pending Merchandise Hierarchy is to change the structure of the merchandise hierarchy itself.

For example:

suppose you have the following hierarchy:

Dept 1: Class 1001: Subclass 101

Dept 1: Class 1002: Subclass 201

Dept 2: Class 2001: Subclass 211

Now suppose you want to move Class 1002 into Dept 2.

Using Pending Merchandise Hierarchy you can make this move so the structure will look like this:

Dept 1: Class 1001: Subclass 101

Dept 2: Class 1002: Subclass 201

Dept 2: Class 2001: Subclass 211

A item reclassification is different. It could be used to move the items between departments, but it would not affect the structure of the merchandise hierarchy itself.

You can setup a dynamic item LIST and select all items in the CLASS to be included in it and then USE the item list to reclassify the class. You cannot reclassify all the items in a class without using an item list. After you setup the dynamic item list, there is an option to 'Use' the item list, and it will allow the USER to select a RECLASSIFICATION.

You can setup a dynamic item list and select all items in the class to be included in it and then use the item list to reclassify the class. You cannot reclassify all the items in a class without using an item list. After you setup the dynamic item list, there is an option to 'Use' the item list, and it will allow the user to select a reclassification.

• Inserts RECORDS into the Point Of Sale (POS) download and writes a transaction code.
• Inserts records into TRAN_DATA with an in and out record.
• The Open To Buy(OTB) is updated to reflect CHANGES.
• History, such as sales history, is NOT MOVED.
• Stock Ledger transactions are created to MOVE the current on-hand inventory from the old merchandise hierarchy to the NEW merchandise hierarchy.

• RMS will check to see if the item has the UDA (User DEFINED Attributes) that is required for the new Merchandise hierarchy, if it does not the item will be rejected.
• RMS will check to see if the item has default UDA's, if it does not, it will still reclassify the item but, a warning message will be written to a report.
• If the item is on any not-yet-processed "unit and value" stock count. If it is, it can not be reclassified. 
• If the item is part of a consignment department and it is being reclassified to a non-consignment department and vice versa reclassification fails.
• If the item is forecastable, RMS will check to ensure the new merchandise hierarchy has a domain in Retail Demand Forecasting (RDF). If a domain is not associated with the new merchandise hierarchy, the reclassification will be rejected. If there is a domain change in RDF, RMS will write all store sales history for the item to the forecasting download.
• The item exists in another reclassification EVENT.
• If the item level of the item is not equal to 1, then it cannot be reclassified. .
• One or more ITEMS on the reclassification event exist on approved PARTIALLY received orders.
• If item is in a simple pack, it will fail reclassification. The item can only be reclassified along with its component item. 
• If item is a pack item, it cannot be reclassified from merchandise to consignment department. 

• Reclassification is the process through which an item or item list is moved from one department/class/subclass to another.
• Reclassification is initiated on-line INDIVIDUALLY or using an Item List An effective date is specified.
• Reclassification occurs in the OVERNIGHT BATCH Items are reclassified the NIGHT before the effective date.

Loc=0 record in PRICE_HIST gives the INITIAL base RETAIL for the item. This is for REPORTING or audit PURPOSES only.

Loc=0 record in PRICE_HIST gives the initial base retail for the item. This is for reporting or audit purposes only.

TAXABLE indicator (taxable_ind) is sent to the Point Of Service (ORPOS) system, this is not applicable for warehouses. Because ITEM LOCK table is maintained for both STORE and warehouse locations, at warehouses RMS assigns a DEFAULT VALUE which will not be used for anything.

Taxable indicator (taxable_ind) is sent to the Point Of Service (ORPOS) system, this is not applicable for warehouses. Because ITEM LOCK table is maintained for both store and warehouse locations, at warehouses RMS assigns a default value which will not be used for anything.

In GENERAL, UNIT_COST COLUMN in the ITEM_LOC_SOH table is updated and USED when the STD_AV_IND = 'S' in SYSTEM_OPTIONS table, otherwise AV_COST is used (i.e., STD_AV_IND = 'A' SYSTEM_OPTIONS table).

The following list of modules use column UNIT_COST in the ITEM_LOC_SOH table for different PURPOSES:

• costextb.pls
• delitemb.pls
• invadjb.pls
• ioattrb.pls
• itappb.pls
• lkitemsqlb.pls
• lkstexeb.pls
• mrt.pc
• stkupld.pc

In general, UNIT_COST column in the ITEM_LOC_SOH table is updated and used when the STD_AV_IND = 'S' in SYSTEM_OPTIONS table, otherwise AV_COST is used (i.e., STD_AV_IND = 'A' SYSTEM_OPTIONS table).

The following list of modules use column UNIT_COST in the ITEM_LOC_SOH table for different purposes:

Pack ITEMS will not have a unit cost STORED in the ITEM_LOC_SOH table. Stock for a pack item is determined at the component LEVEL and therefore a unit cost is not APPLICABLE for a pack item. Hence the unit cost is not updated in the ITEM_LOC_SOH table for a VENDOR pack item after a cost change.

Pack items will not have a unit cost stored in the ITEM_LOC_SOH table. Stock for a pack item is determined at the component level and therefore a unit cost is not applicable for a pack item. Hence the unit cost is not updated in the ITEM_LOC_SOH table for a vendor pack item after a cost change.

The Buyer Pack Cost EQUALS the sum of the cost of the components. Buyer packs are a pack of ITEMS that a buyer GROUPS together to simplify the ordering PROCESS.

The Buyer Pack Cost equals the sum of the cost of the components. Buyer packs are a pack of items that a buyer groups together to simplify the ordering process.

The Vendor PACK cost is not based on the component COSTS. Vendor packs are GROUPS of ITEMS that come in packs predefined by the vendor. The vendor determines the cost of the pack.

The Vendor Pack cost is not based on the component costs. Vendor packs are groups of items that come in packs predefined by the vendor. The vendor determines the cost of the pack.

If the retail of the PACK provides a discount, the discount is prorated across the component items at the time of SALE and will show as a markdown on the stock ledger. 

If the retail of the pack is greater than the SUM of the retail of the components, the OVERAGE will be prorated across the component items at the time of sale.

If the retail of the pack provides a discount, the discount is prorated across the component items at the time of sale and will show as a markdown on the stock ledger. 

If the retail of the pack is greater than the sum of the retail of the components, the overage will be prorated across the component items at the time of sale.

Inventory is kept and VIEWED at the component ITEM level. Pack "inventory" can be viewed when manually requested, but is not held in Retail Merchandising SYSTEM (RMS). RMS allows users to view the inventory of SELLABLE Complex Pack Items through the Sellable Pack Build (packable) screen in the Inventory MENU. 

Inventory is kept and viewed at the component item level. Pack "inventory" can be viewed when manually requested, but is not held in Retail Merchandising System (RMS). RMS allows users to view the inventory of Sellable Complex Pack Items through the Sellable Pack Build (packable) screen in the Inventory Menu. 

The Sellable Pack cannot be ordered or TRANSFERRED UNLESS the pack is SET up as both VALUABLE and orderable. 

The Sellable Pack cannot be ordered or transferred unless the pack is set up as both valuable and orderable. 

The RETAIL price will default to the sum of the cost of the COMPONENTS PLUS the pack's department's MARKUP, but can be changed. 

The retail price will default to the sum of the cost of the components plus the pack's department's markup, but can be changed. 

The pack can CONTAIN different items and/or multiples of the same ITEM. Component items can come from different departments. ALSO, component items can come from multiple suppliers/origin COUNTRIES.

The pack can contain different items and/or multiples of the same item. Component items can come from different departments. Also, component items can come from multiple suppliers/origin countries.

A sellable PACK is a pack item that CONSISTS of MULTIPLE ITEMS that are sold as one item. These items are generally sold as one unit as a benefit to the consumer, either in convenience or price savings. The strategy is, THEREFORE, to encourage the customer to purchase more.

A sellable pack is a pack item that consists of multiple items that are sold as one item. These items are generally sold as one unit as a benefit to the consumer, either in convenience or price savings. The strategy is, therefore, to encourage the customer to purchase more.

USING scripts to manually generate these transactions will create such records. Since item type validation is CONDUCTED at the APPLICATION level, RMS does not validate for the item type at the package level again while consuming data from an external system (RWMS/SIM). If external SYSTEMS other than SIM/RWMS are used, make sure that these systems validate that no transactions are done on these items.

Using scripts to manually generate these transactions will create such records. Since item type validation is conducted at the application level, RMS does not validate for the item type at the package level again while consuming data from an external system (RWMS/SIM). If external systems other than SIM/RWMS are used, make sure that these systems validate that no transactions are done on these items.

All the Merchandise Operations MANAGEMENT (MOM) products ensure that no inventory updates can happen for a concession item. These validations are HANDLED at the application level.

For example, in Retail Warehouse Management System (RWMS)/STORE Inventory Management (SIM), the application does not allow a concession item to be added as a part of any transaction. The same applies for RMS as WELL.

All the Merchandise Operations Management (MOM) products ensure that no inventory updates can happen for a concession item. These validations are handled at the application level.

For example, in Retail Warehouse Management System (RWMS)/Store Inventory Management (SIM), the application does not allow a concession item to be added as a part of any transaction. The same applies for RMS as well.

CONSIGNMENT Items are items that are purchased from the SUPPLIER only when the items are SOLD to a CUSTOMER.

Consignment Items are items that are purchased from the supplier only when the items are sold to a customer.

CONCESSION Items are items that are not owned by the RETAILER but are CAPTURED for FUTURE use. The supplier rents a space from the retailer, and the retailer never owns the items.

Concession Items are items that are not owned by the retailer but are captured for future use. The supplier rents a space from the retailer, and the retailer never owns the items.

The phase dates need not necessarily be always within season dates. This is because sometimes you may have items crossing seasons. For instance, sometimes you can have a transitional phase that bridges the two seasons. There are some items which transcend from ONE season to another and hence are associated to a phase which LIES in both seasons.

RMS only uses Season and PHASES as attributes or to do things such as create item lists and allows OVERLAPS because they have no CRITICAL functionality based on those seasons or phases.

The phase dates need not necessarily be always within season dates. This is because sometimes you may have items crossing seasons. For instance, sometimes you can have a transitional phase that bridges the two seasons. There are some items which transcend from one season to another and hence are associated to a phase which lies in both seasons.

RMS only uses Season and Phases as attributes or to do things such as create item lists and allows overlaps because they have no critical functionality based on those seasons or phases.

A season is a specific selling period during the year, and a Phase is a smaller time period within a season. A season may have multiple phases. However while creating a season if a phase is not CREATED under it then a phase with same name and dates as the season is automatically created for the season. For example, a season has to have at least one phase under it.

Seasons and phases are USED in Replenishment. The ITEMS are on replenishment during the dates of the selected season and phase.

A season is a specific selling period during the year, and a Phase is a smaller time period within a season. A season may have multiple phases. However while creating a season if a phase is not created under it then a phase with same name and dates as the season is automatically created for the season. For example, a season has to have at least one phase under it.

Seasons and phases are used in Replenishment. The items are on replenishment during the dates of the selected season and phase.