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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Batch ID Status Message Reads: "Message #27 missing."

(0) ShareShare
ReportReport
Posted on by 480

Hi,

I have uploaded a Journal Entry which I created in the ".txt" format. I have done this several times and there was no problem uploading it and when I went into the "Batch Entry" screen and pulled up the batch and looked, all the entries in the transaction looked fine. However, previous to this, when I was in the "Batch ID" screen, in the field below the "Status" column, the words: "Message #27 missing." was here (exact quote which included the period at the end).

I am not sure if I have had this message before as I have never noticed it and as mentioned, everything else about the batch i.e. the transactions which Uploaded, appear normal.

We are hoping someone can help us with translating the meaning of this Batch ID Status message.

 

Thank-you for reading our post.

 

Reed

 

 

 

 

 

*This post is locked for comments

I have the same question (0)
  • DinB Profile Picture
    3,951 on at

    First I suggest to exit your GP and log off any remote sessions and try again after re-login. It may be some random memory issue. Also check to see if other users have same message.

  • Suggested answer
    Redbeard Profile Picture
    12,931 on at

    Reed,

    I am unsure of how your batch was created on importing your transaction into GP and what tool you used.  These details would be helpful.   Batches are held in the SY00500 table in SQL at the Company Database level (not in the system DB - DYNAMICS).

    There is a BCHSTTUS field in this table, which tells GP the batch Status...

    Here is a really good list of possible values - sourced from Victoria Yudin's site.

    If the status of your batch were not in this data set, I imagine GP might not know exactly what to make of the situation.  

    Try running the following SQL query against your company database:

    Select BCHSTTUS,* from SY00500 Where BACHNUMB = 'Your Batch ID'

    If your batch status is not a value in this table, or the status should be  Available, run the following script to fix the error (MAKE SURE YOU HAVE A BACKUP)

    Update SY00500 set BCHSTTUS = 0 Where BACHNUMB = 'Your Batch ID'

    Replace Your Batch ID with the batch number from GP of the batch with the problem.

    Francisco’s list of BCHSTTUS (Batch Status) in SY00500:

    [This is a much more comprehensive list posted by Francisco Hillyer in a GP Newsgroup - provided courtesy of e-mail by Robert Cavill - thanks Robert and Francisco!]

    0 – Available

    1 – Batch Posting

    2 – Batch Being Deleted

    3 – Batch Receiving Transactions

    4 – Batch Done Posting

    5 – Being Printed

    6 – Being Updated

    7 – Interrupted While Posting

    8 – Interrupted While Printing

    9 – Interrupted While Updating

    10 – Recurring Batch Errors / Transactions Did Not Post

    11 – Single Batch Error / Transactions Did Not Post

    15 – Error While Posting Computer Checks

    20 – Interrupted While Processing Computer Checks

    25 – Interrupted While Printing Computer Checks Align

    30 – Interrupted While Printing Computer Checks

    35 – Interrupted While Printing Computer Checks Align Before Reprint Computer Checks

    40 – Interrupted While Voiding Checks

    45 – Interrupted While Reprinting Checks

    50 – Interrupted While Processing Remittance Report

    55 – Interrupted While Processing Remittance Report Align

    60 – Interrupted While Printing Remittance Report

    100 – Processing Computer Checks

    105 – Check Align Being Printed Before Print Checks

    110 – Printing Computer Checks

    115 – Check Align Being Printed Before Reprint Checks

    120 – Voiding Computer Checks

    125 – Reprint Computer Checks

    130 – Remittance Report

    135 – Printing Remittance Align Form

    140 – Printing Remittance Form

  • Richard Wheeler Profile Picture
    75,848 Moderator on at

    I would try reparsing your SQL get messages but adding/changing this line in your DEX.INI file:

    BuildSQLMessages=FALSE to BuildSQLMessages=TRUE

  • Thomas Newcomb Profile Picture
    1,810 on at

    Hi Reedq!

    I am just following up to see if any of the information that has been posted has been helpful to your issue or are you still having this issue? I would recommend trying what Richard has recommend as it could be a missing SQL message missing.

    Please let us know if your still having issues.

    ~Thomas Newcomb

    --------------------------

    Dynamics GP Support

    --------------------------

    This posting is provided "AS IS" with no warranties, and confers no rights

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…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans