Making Changes in T_GL_POSTING_HISTORY

Thanks, Ryan. But if I unpost the batches and repost them, it will change the posting date to today, right? Which also messes up our reporting.

In your eyes, would it be better to unpost, repost, and then update the posting date on the T_GL_POSTING_HISTORY (to reflect the actual, past post date)? Or to just combine the rows as I originally planned?

Rey

--

A. Rey Pamatmat

Tessitura Manager

The Public Theater

425 Lafayette Street

New York, NY 10003

(212) 539-8739

rpamatmat@publictheater.org

Always best to unpost using UP_UNPOST, and not directly alter rows in T_GL_POSTING_HISTORY directly.  If you have changed existing batch types to point to new batch type groups, the reposting should take care of the consolidation.

-Ryan

Happy new year!

Has anyone directly updated table above? And if so does anyone know whether this will cause some difficult to foresee problems?

I am specifically hoping to combine post_amt among a few rows with the same post_no, gl_act_no, and fyear, but different batch_type_groups. We started using a new batch type that wasn’t assigned to a batch type group, and this messed up some of our custom reports. We’ve fixed the error for all future batches, but it would be nice to fix the already posted batches as well.

Thanks,

Rey

--

A. Rey Pamatmat

Tessitura Manager

The Public Theater

425 Lafayette Street

New York, NY 10003

(212) 539-8739

rpamatmat@publictheater.org

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Thanks, Ryan. But if I unpost the batches and repost them, it will change the posting date to today, right? Which also messes up our reporting.

In your eyes, would it be better to unpost, repost, and then update the posting date on the T_GL_POSTING_HISTORY (to reflect the actual, past post date)? Or to just combine the rows as I originally planned?

Rey

--

A. Rey Pamatmat

Tessitura Manager

The Public Theater

425 Lafayette Street

New York, NY 10003

(212) 539-8739

rpamatmat@publictheater.org

Always best to unpost using UP_UNPOST, and not directly alter rows in T_GL_POSTING_HISTORY directly.  If you have changed existing batch types to point to new batch type groups, the reposting should take care of the consolidation.

-Ryan

Happy new year!

Has anyone directly updated table above? And if so does anyone know whether this will cause some difficult to foresee problems?

I am specifically hoping to combine post_amt among a few rows with the same post_no, gl_act_no, and fyear, but different batch_type_groups. We started using a new batch type that wasn’t assigned to a batch type group, and this messed up some of our custom reports. We’ve fixed the error for all future batches, but it would be nice to fix the already posted batches as well.

Thanks,

Rey

--

A. Rey Pamatmat

Tessitura Manager

The Public Theater

425 Lafayette Street

New York, NY 10003

(212) 539-8739

rpamatmat@publictheater.org

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!