Define Basic Settings for Enabling POS Integration with M3

This document explains how you define the basic settings necessary to integrate M3 and an external point of sale (POS) system.


Division-specific parameters regarding sales ticket information are set for the POS integration.

The system parameters file (CSYPAR) and start values and parameters file (CSYSTR) are updated.

Follow These Steps

  1. Start 'Settings - POS' (OPS700/B). Enter a division and select Create to display the E panel.

  2. On the E panel, select an accounting dimension in which the due date will be updated.

  3. Select a customer order type and a time basis sum-up.

  4. Select the FAM function to be used for sales ticket invoicing and refunds as well as the accounting option to be used to book negative and positive rounding differences.

  5. Specify whether the sales ticket records in the OXSALE file are to be deleted after they are transferred to the OPSALE file.

  6. Enter an exchange rate type and specify whether sales received from the POS system are to be calculated as gross or net values.

  7. Specify whether the created accounting transactions are to be compressed. Press Enter to confirm the settings. The B panel will be displayed.

Parameters to Set

Program ID/ Panel Field The field indicates…
(OPS700/E) Account dimension for check due date …in which accounting dimension the due date is updated in the M3 general ledger system when a sales ticket is received in M3 from an external POS system. The valid alternatives are 2, 3, 4, 5, 6 and 7.
(OPS700/E) Customer order type

…an order type, which is a combined ID for settings that determine how the order is processed during order entry and in the processing flow.

The customer order (CO) number series of this CO type will be used for customer orders created when sales tickets are uploaded to M3. The CO type entered on this panel will be reserved for sales tickets only. Thus, it will not be available for use when entering customer orders in 'Customer Order. Open' (OIS100).

(OPS700/E) Time basis sum-up

…the time basis sum-up. The valid alternatives are:

  • 1 = Entry date and time (detailed)
  • 2 = Entry date and time bucket
  • 3 = Invoice date
  • 4 = Week
  • 5 = Month
  • 6 = According to period type SLS in 'System Calendar. Open Period' (CRS910)

Note that the functionality for alternative 2=Entry date and time bucket is not available in the current version of M3.

(OPS700/E) FAM function sales …the FAM function used for sales ticket invoicing (FAM entry ID OP20).
(OPS700/E) FAM function refunds …the FAM function used for sales ticket refunds (FAM entry ID OP20).
(OPS700/E) Accounting option–negative differences …the accounting option used to book negative rounding differences between the POS system and FAM.
(OPS700/E) Accounting option–positive differences …the accounting option used to book positive rounding differences between the POS system and FAM.
(OPS700/E) Delete ticket

…whether the sales ticket input in OXSALE should be deleted when it has been transferred to the OPSALE sales ticket input file. 'POS Sales Ticket. Transfer' (OPS270) or 'POS Sales Ticket. Open' (OPS275) are used to transfer sales ticket input to OPSALE.

Select this field to delete the sales ticket input in OXSALE. If this field is not selected, the sales ticket status will remain in status 90.

(OPS700/E) Exchange rate type

…the exchange rate type, which is mandatory information when maintaining exchange rates. The rate type is also connected to customers, suppliers, price lists, year-end and budget procedures.

The valid alternatives are:

  • 01 = Variable rate
  • 02-99 = May be used optionally

Exchange rate types are defined in 'Exchange Rate Type. Open' (CRS056).

(OPS700/E) Separate accounting

…whether sales from the POS system are to be accounted as gross or net values when transferring sales ticket information to the general ledger.

Select this field to account sales as gross values. Discounts 1-6 are accounted separately.

Do not select this field to account sales as net values (gross—discounts).

(OPS700/E) Compress ticket number

…whether the created accounting transactions are to be compressed for the 'Sales ticket number' field (OPORNS) in OPSALE before being transferred to the M3 financial system. Select this field to compress all accounting transactions into one record.

Only accounting transactions that have matching values in the following fields will be compressed:

  • Accounting date
  • Accounting dimensions 1-7
  • Currency
  • Rate type
  • VAT code
  • Base country
  • From/To country
(OPS700/E) Voucher per date …whether to split vouchers per date at the transfer to the general ledger.
(OPS700/E) Permitted delay …how many days old transactions (in the external POS sys-tem) are allowed to be in order to be processed. Transac-tions that are older than the specified number of days are blocked from further processing.
(OPS700/E) Balance control for sales ticket …whether a balance check of the sales ticket should be per-formed when the sales ticket is checked.
(OPS700/E) Mailing list basis

Select the basis ot the mailing list for the item transfer to the shop when running 'Item Net Transfer' (OPS620):

  • 0 = The item/warehouse(MITBAL)
  • 1 = The price lists connected to the shop(OPS500/H)
(OPS700/E) Price and discount origin … how the price origin is set when a sales ticket is entered via a POS system (OPS270MI). Select the check box to set the default price origin to A='API'. Leaving it unchecked means that the price origin is set to 8='Manual/copied' by default.
Related topics