4 Data Setup

The Data Setup chapter covers functionality found within the Data Setup menu of EICS.

Feature include:

• Code Information

• Inventory Adjustment Reasons

• Shipment Reasons

• Sub-Buckets

• Custom Flexible Attribute

Code Information

Figure 4-1 Code Information

The Code Info is an administrative screen for maintaining the code information in the system. You can access this screen by selecting Code Info menu from the Admin / Data Setup menu after logging in EICS. You need proper permissions to access this screen.

You can create or edit the code information for the below code types in the system. The values setup here should correspond to the same values set up in the external merchandising system to ensure integration.

Table 4-1 Code Types

Code Type	Code Type Description	Usage in the System
RTV	Label RTV	Not used.
RTVR	Return to Vendor Reasons	Not used.
RM	Replenishment	This value is displayed on the Item Lookup under the Replenishment method. Retailers can integrate different display values for replenishment. These values should align with the values received from the merchandising system.
RTW	Label RTW	Not used.
RTWR	Return to Warehouse Reasons	Not used.
CNTX	Transfer Context Type	Context Types drop down selected while creating the new transfer request and creating a new transfer. Example values are PROMOTION, REPAIR. If promotion is selected, you can enter the context value. Context value is enabled if the Context Type is set to 'promotion' (Database value of PROM). If the field is enabled, you can optionally enter a valid or invalid promotion ID. The system will display the promotion ID and the promotion description. Valid promotions are of promotion type and exist in the EICS database. In case the promotion does not exist in the database, the promotion ID will still display, but the promotion description will be unknown.
RTF	Label RTF	Not used.
RTFR	Return to Finisher	Not used.
BOLT	Bill of Lading - Transfer	The motive for the shipment for the Transfer functional area. These values will be listed on the drop down on the Motive field on the BOL detail screen on the transfer shipment.
BOLR	Bill of Lading - Vendor	The motive for the shipment for the Return to vendor functional area. These values will be listed on the drop down on the Motive field on the BOL detail screen on the RTV shipment.
BOLF	Bill of Lading - Fulfillment Order	The motive for the shipment for the Customer Order Delivery functional area. These values will be listed on the drop down on the Motive field on the BOL detail screen on the customer order delivery shipment.
RCNX	Return Context Type	Context Types drop down selected while doing the return.

The following are the list of codes that are predefined and available after the deployment in the EICS for the user.

The user is not allowed to edit or delete the codes that are marked as 'System'.

Table 4-2 Predefined Code Types

Code Type	Code	Description	Sequence	System
Transfer Context Type	PROM	Promotion	1	Yes
Transfer Context Type	REPAIR	Repair	2	No
Replenishment	C	Constant	5	Yes
Replenishment	D	Dynamic	3	Yes
Replenishment	F	Floating Point	2	Yes
Replenishment	M	Min/Max	6	Yes
Replenishment	T	Time Supply	4	Yes
Replenishment	SO	Store Order	1	Yes
Bill of Lading - Vendor	RTV	Return to Vendor	2	Yes
Bill of Lading - Vendor	CHY	Charity	1	Yes
Bill of Lading - Transfer	TSF	Transfer	1	Yes
Bill of Lading - Transfer	ADM	Administrative	2	Yes
Bill of Lading - Transfer	RAL	Re-Allocation	3	Yes
Bill of Lading - Fulfillment Order	COF	Customer Order Delivery	1	Yes
Bill of Lading - Fulfillment Order	B2B	B2B	2	Yes

Inventory Adjustment Reasons

Figure 4-2 Inventory Adjust Reasons

The Inventory Adjustment Reason screen is an administrative screen for the creation and maintenance of inventory adjustment reason codes to be used within the system. The reason codes are used within inventory adjustments. Upon initial install, a list of default inventory adjustment reason codes is available. The reason codes defined in EICS need to match that of the merchandising system.

The following table provides the list of Inventory Adjustment reason codes:

Table 4-3 Inventory Adjustment Reason Codes

Code	Reason	Disposition	To Sub-bucket	From Sub-bucket	UI	System	Transaction	Published Ind
1	Wastage	-Stock on Hand			No	Yes	Wastage	Yes
2	Shrinkage	-Stock on Hand			Yes	No		Yes
3	Repair - In	-Unavailable		Trouble	Yes	No		Yes
75	Stock Count Unavailable to Missing	-Unavailable		Trouble	No	Yes	Stock Count for UIN	Yes, all types except Unit and Amount
76	Unit Late Sales Increase SOH	+Stock on Hand			No	Yes	Late Sales	Yes
77	Unit Late Sales Decrease Sales	-Stock on Hand			No	Yes	Late Sales	Yes
78	Unit and Amount Late Sales Increase SOH	+Stock on Hand			No	Yes	Late Sales	Yes
79	Unit and Amount Late Sales Decrease SOH	-Stock on Hand			No	Yes	Late Sales	Yes
81	Damaged - Out	-Stock on Hand			Yes	No		Yes
82	Damaged - Hold	+Unavailable	Trouble		Yes	Yes	Receiving of Damages	Yes
83	Theft	-Stock on Hand			Yes	No		Yes
84	Store Use	-Stock on Hand			Yes	No		Yes
85	Repair - Out	+Unavailable	Trouble		Yes	No		Yes
86	Charity	-Stock on Hand			Yes	No		Yes
87	Stock Count In	+Stock on Hand			No	Yes	Stock Count	Yes, all types except Unit and Amount
88	Stock Count In	-Stock on Hand			No	Yes	Stock Count	Yes, all types except Unit and Amount
89	Dispose from on Hold	-Stock on Hand and -Unavailable		Trouble	Yes	No		Yes
90	Dispose from SOH	-Stock on Hand			Yes	No		Yes
91	Stock - Hold	+Unavailable	trouble		Yes	No		Yes
92	Admin	-Stock on Hand			Yes	No		Yes
93	Store Customer Return	+Stock on Hand			Yes	No		Yes
94	Product Transformation In	+Stock on Hand			Yes	No		Yes
95	Consignment	-Stock on Hand			Yes	No		Yes
96	Ready to Sell	-Unavailable		Trouble	Yes	Yes	RUA Decrease Receiving.	Yes
98	Product Transformation Out	-Stock on Hand			Yes	No		Yes
180	Customer Order Reservations - In	+Customer Order			No	Yes	Reserve Customer Order In POS	Yes
181	Customer Order Reservations - Out	-Customer Order			No	Yes	Cancel Fulfill Customer Order in POS	Yes
182	Stock In	+Stock on Hand			Yes	Yes	Moving UIN from another store in Inventory Adjustments	Yes
183	Stock Out	-Stock on Hand			Yes	No		Yes
184	Unit Late Sales Inventory Adjustment Increase SOH	+Stock on Hand			No	Yes	Inventory Adjustment Late Sales Unit	Yes
185	Unit Late Sales Inventory Adjustment Decrease SOH	-Stock on Hand			No	Yes	Inventory Adjustment Late Sales Unit	Yes
186	Unit and Amount Late Sales Inventory Adjustment Increase SOH	+Stock on Hand			No	Yes	Inventory Adjustment Late Sales UA	Yes
187	Unit and Amount Late Sales Inventory Adjustment Decrease SOH	-Stock on Hand			No	Yes	Inventory Adjustment Late Sales UA	Yes
188	Receipt Hold	-Unavailable	Trouble		No	Yes	Receiving Unavailable	Yes

All reason codes have a disposition associated with them. The disposition is used to define the direction of stock movement for the adjustment. The following table lists the available dispositions:

Table 4-4 Available Dispositions

Display Value	Stock Movement
- Stock On Hand	Decrease Total SOH Decrease Available SOH
+ Unavailable	Decrease Available SOH Increase Unavailable SOH
+ Stock On Hand	Increase Total SOH Decrease Available SOH
- Unavailable	Increase Available SOH Decrease Unavailable SOH
+ Customer Order Reserve	Decrease Available SOH Increase Customer Order Reserve
- Customer Order Reserve	Increase Available SOH Decrease Customer Order Reserve
- Stock On Hand and - Unavailable	Decrease Total SOH Decrease Unavailable SOH
-Unavailable and + Unavailable	Decrease Unavailable SOH Increase Unavailable

Those reason codes that have the "Use in UI" indicator set to 'Yes' appear as reason codes in the Inventory Adjustment dialog.

System reason codes cannot be removed and can only have the description edited. System reason codes are those used within the system for making stock on hand updates, for example, "Stock Count-In" which is used within stock counts.

Note: These are not considered inventory adjustments as the stock count itself represents the transaction of the change.

If the system is configured to use sub-buckets, then the sub-buckets are enabled. Sub-buckets are linked with the inventory adjustment reason codes to make it easy for users to move inventory to, from, and between sub-buckets when adjusting unavailable stock. An example is stock reserved for display or demonstration purposes versus stock that is unavailable because it needs to be repaired. A sub-bucket is a pre-populated list which is defined in the database.

If using sub-buckets, all reason codes that have a disposition which is "to unavailable" stock require a "to sub-bucket" to be selected. Those reason codes that have a disposition which are from unavailable stock require a "from sub-bucket" to be selected.

Note that the -Unavailable and + Unavailable is a disposition used for those retailers that are configured to use sub-buckets. It allows movement of inventory from one sub-bucket to another only within EICS. The inventory stays within the unavailable bucket. These adjustments are not published.

The Publish indicator is used for integration purposes. If this check box is checked, the adjustments associated with that reason code are published upon completion of the adjustment. This indicator can only be modified for those reason codes which are normally editable (non-system reason codes). All reason codes installed on setup have this indicator checked, meaning they are published.

Note: A common use of the Publish indicator is the support of initial inventory position seeding from the merchandise system during implementation. Inventory adjustments may come to EICS (through a web service) and then updates the inventory per the adjustment; the adjustments do not get published out to the external system per the Publish indicator. Also, the Publish indicator can be used to update EICS inventory positions in a custom RMFCS or third-party implementation to sync both inventory positions with the corporate system.

Shipment Reasons

Figure 4-3 Shipment Reasons

The Shipment Reasons screen is an administrative screen for the creation and maintenance of shipment reason codes to be used within the system. The reason codes are used within Transfer Documents, RTV Documents, Transfer Shipments, and RTV Shipments. Upon initial install, a list of default shipment reason codes will be available. The reason codes defined in EICS need to match that of the merchandising system.

The following table provides the list of shipment reason codes:

Table 4-5 Shipment Reason Codes

Type	Type ID	Code	Description	Use Available	Nonsellable	System
Finisher	4	F	Externally Initiated	Yes		Yes
Store	1	O	Overstock	Yes		No
Warehouse	3	O	Overstock	Yes		No
Finisher	4	O	Overstock	Yes		No
Supplier	2	O	Overstock	Yes		No
Finisher	4	U	Unavailable Inventory	No	Trouble	Yes
Store	1	U	Unavailable Inventory	No	Trouble	Yes
Warehouse	3	U	Unavailable Inventory	No	Trouble	Yes
Supplier	2	U	Unavailable Inventory	No	Trouble	Yes
Store	1	W	Externally Initiated	Yes		Yes
Supplier	2	W	Externally Initiated	Yes		Yes
Warehouse	3	W	Externally Initiated	Yes		Yes

All reason codes have an inventory status associated to them. The inventory status is used to define the inventory bucket which will be relieved when the shipment is dispatched.

Those reason codes that are for the type of Store, Warehouse, or Finisher appear as reason codes in the Transfer dialog. The reason codes that are for the type of Supplier appear as reason codes in the RTV dialog.

System Reason codes cannot be edited or removed. System reason codes are required to be available for use in the system. These values are populated upon install and the system check box is only checked during that process. For those non-system reason codes, once the reason code is saved, only the description can be edited.

If the system is configured to use sub-buckets, then the sub-buckets field will be enabled. Sub-buckets are linked with the shipment reason codes to make it easy for users to move inventory to, from, and between sub-buckets when adjusting unavailable stock. Some examples of these are stock reserved for display or demo purposes versus stock that is unavailable because it needs to be repaired. Sub-buckets can be setup and maintained within the Sub-buckets dialog.

If using sub-buckets, all reason codes that have an inventory status of unavailable will require a sub-bucket to be selected.

Note: Before a reason can be accessed by a user, it is important to associate that reason code to a role that the user has the privileges to use in that store.

Sub-Buckets

Figure 4-4 Sub-buckets

The Sub-buckets screen is an administrative screen for the creation and maintenance of sub-buckets to be used within the system. They allow for breaking down the unavailable (non-sellable) inventory bucket further into smaller buckets or what we call sub-buckets.

The system is configurable to use sub-buckets. If the system is configured to use sub-buckets, they will be available within Inventory Adjustments, RTVs, and Transfers. Sub-buckets are attached to reason codes that update unavailable inventory. The reason codes would be either inventory adjustment reasons or shipment reasons. When a user uses the reason code on a transaction, the system will update the proper sub-bucket associated with the reason code.

Sub-buckets can be added, deleted and edited via this dialog. Sub-buckets will have a system generated ID along with a user defined sub-bucket description.

Sub bucket id for 'Trouble' is predefined in the system for the user during the system is deployed.

Custom Flexible Attribute

Figure 4-5 Custom Flexible Attribute

The Custom Flexible Attributes screen is an admin screen used to setup and maintain transaction level flexible attributes for transactions such as Inventory Adjustment and Customer Orders. The flexible attributes set up here will be available in mobile in Inventory Adjustment and Customer Order transactions and you can capture values for these attributes. Appropriate permissions are needed to access, edit and delete flexible attributes.

The flexible attributes can be set up to have values in any of the following data types: Text, Date, Decimal and Long. You can also set minimum and maximum range for values that you can enter for these flexible attributes in the transactions (Inventory Adjustments and Customer Orders). The retailer also has the flexibility to set up certain flexible attributes that belong to Inventory Adjustments as mandatory and that you specify values for them before confirming the transaction in mobile.