Create a New Shop

Outcome

A shop is created. The information to be transferred between M3 and the POS system is defined.

You can link an assortment for the shop after which the shop is ready to be used. The shop constitutes a unit that is used to transfer information between M3 and the POS system. The shop can, for example, be used to create sales statistics for comparing sales in one shop with sales in another shop.

The following files are updated:

• The shop file - OSTORE
• The file for start values and parameters - CSYSTR

Before you start

• A warehouse must be created in 'Warehouse Open' (MMS005). The 'Shop information' field in (MMS005/E) must be selected to indicate that shop information can be entered for this warehouse. If you add 5 to the panel sequence in (MMS005/B), 'Shop. Open' (OPS500) is automatically started after warehouse information is specified.
• The users accessing this shop must be defined in 'User. Open' (MNS150).
• User groups must be defined in 'User Group. Open' (CRS004). A user group is a group of users that has the same access rights to files and records in M3.

Follow these steps

1. Start 'Shop. Open' (OPS500/B). Select the warehouse you have created for this shop and select Create. (OPS500/E) is displayed.

   You can also start (OPS500) directly when you have created the warehouse from 'Warehouse. Open' (MMS005/B), either through option 15='Shop information' or by adding 5 to the panel sequence.

Define basic data

1. On the E panel, specify shop category, business area and, when needed, shop surface.

2. Specify the shop class, shop volume class and, when needed, shop rank. Specify the weekdays on which the shop should be open.

3. On the E panel there are six user-defined fields that can be used freely. Press Enter to open the F panel.

4. On the F panel there are 16 user-defined fields that can be used freely. None of these fields are required. Press Enter to open the G panel.

Define what is to be transferred between M3 and the POS system

1. On the G panel, select the 'POS system interface' field to indicate that the shop should be interfaced with an external POS system.

2. Specify which of the following M3 files should be transferred to the external POS system:

   • Item master
   • Item/warehouse
   • Item language
   • Item alias
   • Customer
   • Sales price
   • Promotion
   • User

3. Specify whether M3 stock, sales statistics, accounts receivable, and general ledger should be updated with sales ticket information.

4. Specify whether the POS system's VAT calculation should be used in M3. Press Enter to display the H panel.

5. On the H panel, specify the alias category and alias qualifier, if required.

6. Specify the price lists, currency methods, and user groups to use when exporting information to the POS system. Enter the date for activating price lists when transferring information.

7. Specify the requisition order type to use in M3 for registering a negative or positive stock adjustment from the external POS system.

8. Enter distribution order type 51 (Distribution order issue) in the 'POS to M3 distribution order main warehouse' field to update distribution orders between two warehouses.

9. Enter distribution order type 51 (Distribution order issue) in the 'POS to M3 distribution order shop' field to update distribution orders between two warehouses. Press Enter to display the I panel.

10. On the I panel, specify the shop addresses. Press Enter to finish.

Parameters to set

Program ID/Panel	Field	The field indicates …
(OPS500/B)	Warehouse	…the warehouse/shop ID. Normally, the warehouse is used to distinguish the various geographical locations of a company. In the point of sales integration process, a warehouse must be defined before a shop can be created. See the Before Starting section above.
(OPS500/E)	Shop category	…the shop category. Shop categories are used to group shops by their assortment, for example, clothing and furniture shops. They are defined in 'Shop Category. Open' (CRS490). This field is mandatory.
(OPS500/E)	Business area	…the business area for this shop. The business area is used as a tool to group information for budgeting and statistical purposes and is created in 'Business Area. Open' (CRS036).
(OPS500/E)	Shop surface	…the shop's surface space in square meters.
(OPS500/E)	Shop class	…the shop class. Shop classes are defined in 'Shop Class. Open' (CRS492). This field is mandatory.
(OPS500/E)	Shop volume class	…the shop volume class. The shop volume class categorizes the shops by their receipts. The values are defined in 'Shop Volume Class. Open' (CRS491). This field is mandatory.
(OPS500/E)	Shop rank	…the shop priority. This field can be used if you want to rank the shops; for example, which shop has the highest sales.
(OPS500/E)	CRS796 free 1 to CRS796 free 6	…user-defined fields that can be used as desired. You must define four of these six fields in 'User-Defined Shop Field. Open' (CRS390) and you can use F4=Browse to retrieve the values. Field headings for these fields are defined in 'User-Defined Field Heading. Open' (CRS796), where the file identity code=OSTORE.
(OPS500/E)	Monday, Tuesday etc.	…whether the shop is open on the specified weekday.
(OPS500/F)	CRS796 free 7 to CRS796 free 22	…user-defined fields that can be used as desired.
(OPS500/G)	POS system interface	…whether this warehouse/shop should be interfaced with an external POS system. POS interface parameters are managed by 'Settings - POS' (OPS700). This field is mandatory.
(OPS500/G)	Item master interface	…whether M3 item data should be exported to the external POS system connected to this shop. The item master batch interface is managed in 'POS Item. Transfer' (OPS610).
(OPS500/G)	Item/warehouse interface	…whether M3 item/warehouse and item/facility data is to be exported to the external POS system. The item/warehouse and item/facility batch interface is managed in 'POS Item. Transfer' (OPS610).
(OPS500/G)	Item language interface	…whether M3 item language data is to be exported to the external POS system. Item-language batch interface parameters are set in 'POS Item. Transfer' (OPS610).
(OPS500/G)	Item alias interface	…whether the data for M3 item alias types 02 and/or 03 should be exported to the external POS system. The item-alias batch interface is managed in 'POS Item. Transfer' (OPS610).
(OPS500/G)	Customer interface	…whether M3 customer data should be exported to the external POS system. Customer batch interface is managed in POS customer batch 'POS Customer. Transfer' (OPS615).
(OPS500/G)	Sales price interface	…whether M3 price list data should be exported to the external POS system. The sales price batch interface is managed in 'POS Price. Transfer' (OPS616).
(OPS500/G)	Promotion interface	…whether M3 promotion data should be exported to the external POS system. The promotion batch interface is managed in 'POS Promotion. Transfer' (OPS617).
(OPS500/G)	User interface	…whether M3 user profiles should be exported to the external POS system. The user batch interface is managed in 'POS User. Transfer' (OPS618).
(OPS500/G)	Inventory interface	…whether the M3 stock system should be updated with sales tickets received from the external POS system. The inventory accounting batch interface is managed in 'POS Sales Ticket. Update' (OPS280). Note that the M3 stock system will not be updated unless the 'Inventory accounting interface' field is selected in both 'Shop. Open' (OPS500/G) and in 'POS Sales Ticket. Update' (OPS280/E).
(OPS500/G)	Sales statistics interface	…whether the M3 sales statistics system is updated with sales tickets received from the external POS system. The sales-statistics batch interface is managed in 'POS Sales Ticket. Update' (OPS280). Note that the sales statistics in M3 will not be updated unless the 'Sales statistics interface' field is selected in both 'Shop. Open' (OPS500/G) and 'POS Sales Ticket. Update' (OPS280/E).
(OPS500/G)	Financial interface	…whether the general ledger is updated with sales ticket information received from the external POS system. The financial batch interface is managed in 'POS Sales Ticket. Update' (OPS280). The M3 financial system will not be updated unless the 'Financial interface' field is selected in both 'Shop. Open' (OPS500/G) and 'POS Sales Ticket. Update' (OPS280/E).
(OPS500/G)	Tax calculation from POS	…whether the POS system's tax calculations should be used in M3. Usage of tax calculations from the POS system is mandatory if tax method 2 or 3 was entered in 'Company. Connect Division' (MNS100) for the division to which the warehouse is connected.
(OPS500/G)	Amounts exclude tax	…whether the amounts sent from the POS system excludes tax.
(OPS500/H)	Alias category	…the alias types that will be exported from M3 to the external POS system. The valid values are 02 (EAN number) and 03 (External database). If you select alias category 02, you must enter the alias qualifier. See the next field description. The item-alias batch interface is managed in 'POS Item. Transfer' (OPS610).
(OPS500/H)	Alias qualifier	…the alias qualifiers that will be exported from M3 to the external POS system. The valid values related to alias category 02 are: EA08 = EAN 8, an EAN number consisting of 8 digits EA13 = EAN 13, an EAN number consisting of 13 digits DU14 = DUN14, a packaging variant of an EAN number UPC = UPC number No control if alias category=03. If you select alias category 03, then you can define the qualifier ID as you want. The item-alias batch interface is managed in 'POS Item. Transfer' (OPS610).
(OPS500/H)	Price list	…the price list that should be exported from M3 to the external POS system. You can transfer up to three price lists. The sales price batch interface is managed in 'POS Price. Transfer' (OPS616).
(OPS500/H)	Currency method	…the currency method used. The method entered here is set in the price lists or promotions that are exported from M3 to the external POS system. If you select this field, all currencies connected to the price list code will be used. Otherwise the division's currency will be used.
(OPS500/H)	From date method	…how dates for price lists are processed. The price lists are exported from M3 to the external POS system. If you select this field, price lists that are valid on the interface date as well as those that will be valid in the future are exported from M3. If this field is not selected, only price lists that are valid on the interface date are exported.
(OPS500/H)	User group - function access	…the user groups that will be exported from M3 to an external POS system. The user batch interface is managed in 'POS User. Transfer' (OPS618).
(OPS500/H)	POS to M3 Requisition +	…the requisition order type that is used in M3 to register a positive stock adjustment from the external POS system. You must enter transaction type 40 (Requisition order receipt), managed in 'Requisition/Distribution Order Type. Open' (CRS200).
(OPS500/H)	POS to M3 Requisition -	…the requisition order type that is used in M3 to register a negative stock adjustment from the external POS system. You must enter transaction type 41 (Requisition order issue), managed in 'Requisition/Distribution Order Type. Open' (CRS200).
(OPS500/H)	POS to M3 distribution order main warehouse	…the distribution order type that is used in M3 to update distribution orders between two warehouses. The target warehouse is interfaced with the external POS system. You must enter transaction type 51 (Distribution order issue), managed in 'Requisition/Distribution Order Type. Open' (CRS200).
OPS500/H)	POS to M3 distribution order shop	…the distribution order type that is used in M3 to create and update distribution orders between two warehouses. Both the source and target warehouses are interfaced with the external POS system. You must enter transaction type 51 (Distribution order issue), managed in 'Requisition/Distribution Order Type. Open' (CRS200).
(OPS500/I)	Addresses 1-4	…the address of the shop. This field is only used for informational purposes.