CCO - Daily closings

[Former Member]

Hello,
Problem:
In times of sale or high commercial activity, the number of receipts can be very important.
The queue can be very long (more than 200 receipts) and the processing time for receipts by the b1i also very long, depending on the capacity of the server.
The daily closing is done just after the store closes.
If we do the daily closing before the end of the processing of receipts (it is the end of the day and the users are in a hurry to leave), the fences appear with gaps in the monitor.
It would be desirable to implement a solution that does not deal with the closure in the B1i until the processing of receipts is completed.
This would avoid manual interventions in the monitor.
Thank you
Best regards
Pierre BARRET

[JoaoC]

Hello Pierre,

I am not sure exactly what you mean with fences on the monitor, but generally speaking the day-end closing processing on the CCO endpoints is independent from the processing on B1/B1if downstream.

If you mean you need to run reports as soon as the day-end closings are done, then I would suggest the deployment of CCOM instances (if not yet in place), locally if the latency to the backend is high, and together with SQL Server if the amount of data is considerable. This way would be able to query all your sales data almost immediately after the day-end closing.

Later or on the following days you could than perform further analysis of your sales numbers on B1.

BR