web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Re opening of a closed...
Microsoft Dynamics SL (Archived)

Re opening of a closed Period/ partially released batches/ complete status

(1) ShareShare
ReportReport
Posted on by Community Member

QN.1. one of the administrators closed the inventory module from period 3 to period 5 instead of period 4 so am asking how i can reopen period 4. Thanks

QN.2 what is the effect of a partially released batch

QN3. There are some batches that show a complete (c) status under inventory module and purchasing (receipt/invoice entry screen) but this means they don't update the GL so how can i make them update the GL

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Erich Strelow F Profile Picture
    Erich Strelow F 16 on at

    QN.1 Can't help on that.

    About the partially released batch, the obvious answer is that a batch started its release process but it couldn't reach its end.

    The worst case is usually like this: an inventory issue consisting a one muffin and one coffee got partially released. The muffin line was released but the coffee has not. The customer may already have eaten the muffin, so you can't just delete the whole transaction. Maybe that was your last muffin and you need your muffin inventory to show zero so you won't sale muffins you can't deliver. So, the issue isn't really complete, but you can't go back. So the issue gets to be partially released or the so called "S" status.

    The funny thing is that a batch consisting of a sole line can get partially released also.

    When this happens, normally a log file gets generated in your Eventlog folder so a corrective action can take place. There's a good article on this: https://support.microsoft.com/en-us/kb/871342 

    The rule of thumb is: always move forward, never backwards. Don't try to erase, cancel or void the batch. Always try to get it to the Fully released status. In the coffee situation the corrective action is normally put yourself on initialize mode, erase the coffee line and re-release the batch.

    About the "C" status, there's normally two scenarios:

    1. The PO receipt was released in the PO module, but not yet in the IN module. There might be an error in the EventLog about this.
    2. The batch has no content: all its lines may have been removed.
  • Community Member Profile Picture
    Community Member on at

    Hi!!! The QN2 A partially released batch will not let you do either closing the day or month.

    The QN3 Should be checked in all modules where this movement affects if he is detained or partially released to affect the GL

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans