Skip to content

Frequently asked questions

No popup appears even though a message is maintained on the article. What can cause this?

Check in this order:

  1. Setting UDF to use on the POS: is it set to exactly the field that holds the message (e.g. udfStringXL1)? The name must match exactly, including capitalization. An unsupported value leaves a warning in the POS log; with an empty setting, simply nothing happens.
  2. Has the master data reached the POS? The message is read from the locally synchronized article data; after maintaining it in the Manager, the POS first has to synchronize the master data.
  3. Is the article active? No message is shown for inactive articles.
  4. Is the license valid? Without a valid license the plugin disables itself and shows a notice banner on the POS; the log contains a DISABLED entry (see Operations).

The message appears, but without sound. Why?

Sound output is not enabled on the POS (POS configuration, Allgemeines → Ton aktivieren, "General → Enable sound"). The message works without sound, too.

Why can't the popup be confirmed with ENTER?

By design; this is the core of the plugin. A barcode scanner behaves like a keyboard and sends an ENTER after the barcode. If the popup could be confirmed from the keyboard, the next scan (or the ENTER of the triggering scan itself) would dismiss the message unnoticed. That is why the keyboard is completely blocked while the message is open; confirmation happens only by touch or mouse on OK.

Can something scanned while the popup is open get booked by accident?

No. While the message is open, all keyboard and scanner input is discarded (and answered with an error tone). Only after OK does the POS accept input again.

Can I store different messages for different articles?

Yes. Each article gets its own text in the configured UDF field. Only the field is the same for all articles (the UDF to use setting); the content is free per article.

Why doesn't my text fit into udfString1?

udfString1 and udfString2 are short fields. For longer message texts, use one of the XL fields (udfStringXL1–udfStringXL4) and change UDF to use accordingly.

Does the plugin also work with messages on customers instead of articles?

No. Only UDF fields of the article master data are evaluated; the message is triggered by booking an article.

Does the setting apply centrally to all POS systems?

No, UDF to use is set per POS in its plugin settings. The message texts themselves, on the other hand, you maintain centrally on the articles in the CCO Manager.

Do I need different downloads for FP21 and the Cloud Edition?

No. One and the same jar supports SAP Customer Checkout 2.0 FP21 (on-premise) and the Cloud Edition 3.0 up to FP2602.