Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Diane Boone]

Hi, we are new to D365 F & O – we have learned that we cannot post a cycle count journal until the retail side has posted their batches for the day. When we create a cycle count journal it’s based off of the physical inventory, rather than the available physical, so until our retail staff post the sales from the day before we can not create a cycle journal or post a cycle count because if we have the inventory locked the retail folks cannot post the days sales and until the days sales are posted we can’t cycle count. Everything is in the physical reserved until sales batches are posted. Is there another way to do a cycle count without inventory and retail crossing over each other? Any help or insight would be greatly appreciated. Thanks,

——————————
Diane Boone
Sight & Sound Theatres
Ronks PA
——————————

[Corey Warawa]

Hi Diane,

The way we try to handle this is by posting the retail statements in batch overnight and then creating the count journals before start of business the next day.  This way the values in the journal represent what should be available.  Of course, if the count is not performed before store opening then there can be a bit of manual reconciling to do when items are sold.

——————————
Corey Warawa
Functional Architect
Liquor Stores North America
Edmonton AB
——————————
——————————————-

[Diane Boone]

Hi Corey,

Thank you for the information. Our challenge is that our retail folks don’t post the batches at the end of the day, they wait and post first thing the next morning. We have to wait until the batches are posted before we can begin my cycle counts, otherwise our inventory is not accurate in the journals. If they run into posting issues, this also holds up the process. We might have to look at another way of doing our processes.

——————————
Diane Boone
Sight & Sound Theatres
Ronks PA
——————————
——————————————-

[Graeme Thom]

Hi Diane, 

We are not on 365, but found a simillar issue with Reporting in AX, we found that running:

Retail > Retail IT > POS Posting > Post Inventory.

Running the above every 15 minutes on batch would post stock through out the day and the end of day statement would deal with the finanical part. 

Is there any reason they close their statements the next day rather than end of day? 

Thanks,  

——————————
Graeme Thom
AX Administrator
Hunter Boot Ltd
Edinburgh
——————————
——————————————-

[Robert Menschel]

>  Is there any reason they close their statements the next day rather than end of day?
I cannot answer for Diane, but we are a retailer open until almost 10 pm at night. Nobody wants to stick around after 10 pm to balance and post the day’s transactions. That’s a process we do mid-morning the following day. Not only do we want to be able to do cycle counts first thing in the morning, but we need to report daily sales to management, and run our automatic replenishment system and get purchase orders to vendors, both before store opening around 5 am. 

Our solution (in version 2009) is to simply automate the posting of all retail sales every night, with the assumption that everything is correct and accurate. When the cash room personnel then balance the previous day’s sales (and generate the day’s bank deposits), they identify any variances, and notify our Finance team, who post any needed adjustments. 

——————————
Robert Menschel
Lead Systems Engineer
HD Supply Repair & Remodel
Roseville CA
——————————
——————————————-

[Diane Boone]

Hi Robert, 

Thanks for your feedback. Yes, we have a retail operation and the last retail transaction is usually completed at 10:30 pm. Like you no one wants to stick around until 11 pm at night reconciling batches. I do like your solution regarding the automation of posting, can you tell me more about how easy or complicated it is to get set up to automate postings? I would like to have more information so I can present this as a possible solution to my management team for discussion. 

I appreciate your help. 

Thanks,

——————————
Diane Boone
Sight & Sound Theatres
Ronks PA
——————————
——————————————-

[Corey Warawa]

Hi Diane,

We also have our inventory posting, retail distribution jobs and statement calculation/posting scheduled in batch.  The inventory posting and P-0001 job are set to run every 10 minutes.  The distribution jobs run nightly at 1 or 2 a.m. and the statement calculation/posting runs after our stores close – generally 3 a.m.

To run these in batch simply select the batch processing option and set a recurrence based on your needs.

——————————
Corey Warawa
Functional Architect
Liquor Stores North America
Edmonton AB
——————————
——————————————-

[Diane Boone]

Thank you so much for your feedback and suggestions. We are interested in exploring more about automating our batch postings. Could someone walk us through the steps on where to go and how to set this up? This is so new to us and we would like to test this option for our retail and inventory folks.

Your help with this is much appreciated.

Thanks,

——————————
Diane Boone
Sight & Sound Theatres
Ronks PA
——————————
——————————————-

[Robert Menschel]

Again, we’re 2009, so YMMV.  Within the Retail Headquarters module menu we have of RBOStatementCalculate_Multi and RBOStatementPost_Multi. We execute this calculation class every 3 hours during the day, generating one statement for each retail store. That seemed to be a good frequency to help manage performance during the nightly posting (too-large retail statements take too-long). We then schedule, for about an hour after closing, a final execution of the calculation class, followed by executing of the posting class.  

We have made some minor tweaks to these classes.

• We’ve identified some conditions within transactions which originally caused Calculation or Posting to fail, but which we consider non-critical. We modified the calculation class to flag those transactions for a diagnostic report, and then skip those transactions, excluding them from the retail statement. 
• Posting would normally fail if it encounters an empty retail statement, such as when a store closes early for physical inventory counting, or when we are closed on Christmas Day. We modified the posting class to identify and delete empty retail statements without failing.

——————————
Robert Menschel
Lead Developer
HD Supply Home Improvement Solutions
Roseville CA
——————————
——————————————-

[Diane Boone]

Robert and or Corey,

Thank you so much for your feedback and suggestions. We are interested in exploring more about automating our batch postings. Could someone walk us through the steps on where to go and how to set this up? This is so new to us and we would like to test this option for our retail and inventory folks. 

Your help with this is much appreciated.

Thanks,

——————————
Diane Boone
Sight & Sound Theatres
Ronks PA
——————————
——————————————-

[Graeme Thom]

Hi Diane, 

Please see the below link to setup the two jobs its really easy. The nightly posting is split, we run “Calculate Statement” batch at 10pm which will create a statement per store. At 10:30 we run Post the Statement” which will look for any open statements and post them. 

The only problems we have with this are: 

Posting difference – You can set a posting difference under Retail Stores > open the store > Statement / closing fast tab. we have a £50 limit anything above that will stop the statements from posting automatically they will have to be manually interveined. 

Timings – If the store opens late, we can calculate the statement without their end of day count throwing off the totals, this doesnt happen offten as our P job runs every 15 minutes. 

https://docs.microsoft.com/en-us/dynamics365/unified-operations/retail/tasks/run-job-calculate-statements
https://docs.microsoft.com/en-us/dynamics365/unified-operations/retail/tasks/run-job-post-statements

——————————
Graeme Thom
AX Administrator
Hunter Boot Ltd
Edinburgh
——————————
——————————————-

[Corey Warawa]

Hi Diane,

In addition to the P-0001 job and the statement calculation and posting, you will also need to set up the “Post inventory” job and the “Validate store transactions” (if running version 8.1.3 or greater) job.

We run the jobs in this fashion:
1. P-0001 – Runs every 10 minutes
2. Post inventory – Runs every 10 minutes; staggered with the P-0001 job
3. Validate store transactions – Runs every hour
4. Calculate and post statements – A single job that runs at 3:45 a.m. daily.  We have combined these into one batch so that all statements attempt to calculate and then post. If a statement does not calculate successfully then it will not post, however all others will.  Below is a screenshot.

——————————
Corey Warawa
Functional Architect
Liquor Stores North America
Edmonton AB
——————————
——————————————-