Uploading Sales Ticket Information to M3

Use this procedure to transfer sales ticket information from an external point of sale (POS) system to M3.

Note: All steps in this process are performed automatically when the upload is initiated from the POS system. If an error occurs, you can correct the error and then continue the upload manually.

Outcome

Sales ticket information is uploaded to M3 where it is checked and validated. If errors occur during the upload, you can correct the errors in 'POS Sales Ticket. Open' (OPS275) before the general ledger, stock, and sales statistics are updated in M3.

Refer to each respective instruction for information on How the system is affected.

Before you start

  • Create a warehouse in 'Warehouse. Open' (MMS005). Select the 'Shop information' field in (MMS005/E) to specify shop information for this warehouse.
  • Define a shop in 'Shop. Open' (OPS500).
  • Specify a customer order type in 'Settings—POS' (OPS700/E). The customer order number series of this order type is used when customer orders are created from sales tickets uploaded from the POS system.
  • Sales tickets with 00-'Received' status in OXSALE from external POS system must exist in the OXSALE transaction file.

Follow these steps

  1. Create new batch identity.

    The POS system asks M3 for a batch number for the sales ticket batch to be uploaded. Different application programming interface (API) transactions are used such as AddRoundNumber, SndSlsTicketLin, SndSlsTicketPay, GetRoundNumber, DelRoundNumber, and BchProcRound.

  2. Upload sales tickets.

    The sales tickets are uploaded through the 'POS Sales Ticket interface' (OPS270MI). The sales tickets are temporarily stored in the OXSALE file. You can make a selection of facility, warehouse, and transaction date. Use an interface round number to identify all transactions in a batch.

  3. Check the uploaded batch.

    The OXSALE records are displayed in (OPS275), where you can add or change information before the information is sent to the OPSALE file. The different statuses of the temporary orders are:

    • 00-'Received in OXSALE from external POS system'
    • 05-'Error found in OXSALE'
    • 06-'Record already exists in OPSALE'
    • 10-'Valid data in OXSALE'
    • 90-'Transferred to OPSALE'

  4. Delete the uploaded batch.

    If you review the sales ticket batch in the OXSALE file and find that some transactions differ from the transactions sent from the POS system, you can delete the uploaded batch and upload it again. To delete the uploaded batch, use the DelRoundNumber (delete interface round number) API transaction.

  5. Transfer and validate the sales tickets.

    Sales tickets are transferred to the OPSALE file and validated. You can transfer sales tickets in batch or individually. You must transfer the sales tickets from the OXSALE file to the OPSALE file before the M3 database update can take place.

    The sales tickets are automatically transferred and validated through the (OPS270MI) by using the BchPrcRound (batch process round number) API transaction.

    You can manually transfer and validate sales tickets in batches through 'POS Sales Ticket. Transfer' (OPS270), through the SlsTicketTrf API transaction in (OPS270MI), or individually through (OPS275).

  6. Correct errors.

    If the required information is missing or incorrect, the update of the OPSALE file fails.

    Specify this required information for all records:

    • Company, division, customer order number, customer order line number, delivery number, record type, warehouse, currency, transaction date, and invoiced amount

      This information is required for record types 1000-'Sales' and 1200-'Return'.

    • Customer number, item number, alternate U/M, VAT code, and invoiced quantity

      This information is required for record type 7000=Petty cash expenses.

    • Item number and VAT code

      This information is required for record types ending with 90.

    • Bank operation code

      This information is required to correct errors in (OPS275).

  7. Update M3.

    When all sales tickets are validated in the OPSALE file, you can update M3 with the sales ticket information. You can select to update the general ledger, sales statistics, and stock separately or at the same time.

    The parameters that control the update are defined in 'Settings—POS' (OPS700), 'Shop. Open' (OPS500), and in 'POS Sales Ticket. Update' (OPS280).

    M3 is updated automatically through (OPS270MI) using the BchPrcRound API transaction, through (OPS280MI) using the SlsTicketUpdate API transaction, or manually in (OPS280).

Related topics