Open Forum

I am utilizing the landed cost feature in GP by adding it through enter/match invoices.  When this invoice is posted during batch posting, GP would randomly crash about 1% of the time and has to be restarted.  When this happens, the total amount on the matched invoice is posted to the GL accounts, but total isn't distributed to the line items nor is it posted to the line items.

Looking at the POP10600 table confirms that the status for each line item is 0 so they do not have their cost updated, while the POP30390 shows the distribution to the GL accounts, which causes a reconciliation issue.

  After restarting GP, we can no longer repost the landed cost invoice as it got marked, and unmarking it to repost again puts it into a posted state after with no updates to the items costs.

Have anyone else ran into this issue?

------------------------------
Lien Truong
BREA
------------------------------

Lien, I'eve encountered something similar but it was caused by having a 1099 amount that was greater than the invoice amount (we had AP invoices being imported from our Document Mgmt. System).  It was an utter bear to correct whenever it happened and wasn't caught by an AP clerk before they attempted to post.

------------------------------
Matthew Arp
Business Systems Developer
Hunton Group
Houston TX
------------------------------

Original Message:
Sent: Oct 04, 2019 01:34 PM
From: Lien Truong
Subject: Match invoices posting / landed cost causing GP to crash

I am utilizing the landed cost feature in GP by adding it through enter/match invoices.  When this invoice is posted during batch posting, GP would randomly crash about 1% of the time and has to be restarted.  When this happens, the total amount on the matched invoice is posted to the GL accounts, but total isn't distributed to the line items nor is it posted to the line items.

Looking at the POP10600 table confirms that the status for each line item is 0 so they do not have their cost updated, while the POP30390 shows the distribution to the GL accounts, which causes a reconciliation issue.

  After restarting GP, we can no longer repost the landed cost invoice as it got marked, and unmarking it to repost again puts it into a posted state after with no updates to the items costs.

Have anyone else ran into this issue?

------------------------------
Lien Truong
BREA
------------------------------

My experience with the POP module is if you experience problems posting, usually caused by network problems, etc., is you need to fix the data with SQL queries to finish posting the problem transactions.  Put the problem transaction in its own batch and post the rest.  If your consultant cannot help, maybe I can help next week.

------------------------------
Bruce Strom
Programmer Analyst
Superior Lighting, Inc.
Sunrise FL
------------------------------

Original Message:
Sent: Oct 15, 2019 01:24 PM
From: Matthew Arp
Subject: Match invoices posting / landed cost causing GP to crash

Lien, I'eve encountered something similar but it was caused by having a 1099 amount that was greater than the invoice amount (we had AP invoices being imported from our Document Mgmt. System).  It was an utter bear to correct whenever it happened and wasn't caught by an AP clerk before they attempted to post.

------------------------------
Matthew Arp
Business Systems Developer
Hunton Group
Houston TX

Original Message:
Sent: Oct 04, 2019 01:34 PM
From: Lien Truong
Subject: Match invoices posting / landed cost causing GP to crash

I am utilizing the landed cost feature in GP by adding it through enter/match invoices.  When this invoice is posted during batch posting, GP would randomly crash about 1% of the time and has to be restarted.  When this happens, the total amount on the matched invoice is posted to the GL accounts, but total isn't distributed to the line items nor is it posted to the line items.

Looking at the POP10600 table confirms that the status for each line item is 0 so they do not have their cost updated, while the POP30390 shows the distribution to the GL accounts, which causes a reconciliation issue.

  After restarting GP, we can no longer repost the landed cost invoice as it got marked, and unmarking it to repost again puts it into a posted state after with no updates to the items costs.

Have anyone else ran into this issue?

------------------------------
Lien Truong
BREA
------------------------------

Or you can simply delete the problem transaction and re-enter it, which is probably the best solution in many cases.

------------------------------
Bruce Strom
Programmer Analyst
Superior Lighting, Inc.
Sunrise FL
------------------------------

Original Message:
Sent: Oct 16, 2019 12:43 AM
From: Bruce Strom
Subject: Match invoices posting / landed cost causing GP to crash

My experience with the POP module is if you experience problems posting, usually caused by network problems, etc., is you need to fix the data with SQL queries to finish posting the problem transactions.  Put the problem transaction in its own batch and post the rest.  If your consultant cannot help, maybe I can help next week.

------------------------------
Bruce Strom
Programmer Analyst
Superior Lighting, Inc.
Sunrise FL

Original Message:
Sent: Oct 15, 2019 01:24 PM
From: Matthew Arp
Subject: Match invoices posting / landed cost causing GP to crash

Lien, I'eve encountered something similar but it was caused by having a 1099 amount that was greater than the invoice amount (we had AP invoices being imported from our Document Mgmt. System).  It was an utter bear to correct whenever it happened and wasn't caught by an AP clerk before they attempted to post.

------------------------------
Matthew Arp
Business Systems Developer
Hunton Group
Houston TX

Original Message:
Sent: Oct 04, 2019 01:34 PM
From: Lien Truong
Subject: Match invoices posting / landed cost causing GP to crash

I am utilizing the landed cost feature in GP by adding it through enter/match invoices.  When this invoice is posted during batch posting, GP would randomly crash about 1% of the time and has to be restarted.  When this happens, the total amount on the matched invoice is posted to the GL accounts, but total isn't distributed to the line items nor is it posted to the line items.

Looking at the POP10600 table confirms that the status for each line item is 0 so they do not have their cost updated, while the POP30390 shows the distribution to the GL accounts, which causes a reconciliation issue.

  After restarting GP, we can no longer repost the landed cost invoice as it got marked, and unmarking it to repost again puts it into a posted state after with no updates to the items costs.

Have anyone else ran into this issue?

------------------------------
Lien Truong
BREA
------------------------------

Bruce,

Thanks for the tips - that is exactly what we ended up having to do.  We had to see what got posted to the GL and do an entry to reverse that, clean up the work tables, then re-posted the landed costs.

------------------------------
Lien Truong
BREA
------------------------------

Original Message:
Sent: Oct 16, 2019 12:43 AM
From: Bruce Strom
Subject: Match invoices posting / landed cost causing GP to crash

Or you can simply delete the problem transaction and re-enter it, which is probably the best solution in many cases.

------------------------------
Bruce Strom
Programmer Analyst
Superior Lighting, Inc.
Sunrise FL

Original Message:
Sent: Oct 16, 2019 12:43 AM
From: Bruce Strom
Subject: Match invoices posting / landed cost causing GP to crash

My experience with the POP module is if you experience problems posting, usually caused by network problems, etc., is you need to fix the data with SQL queries to finish posting the problem transactions.  Put the problem transaction in its own batch and post the rest.  If your consultant cannot help, maybe I can help next week.

------------------------------
Bruce Strom
Programmer Analyst
Superior Lighting, Inc.
Sunrise FL

Original Message:
Sent: Oct 15, 2019 01:24 PM
From: Matthew Arp
Subject: Match invoices posting / landed cost causing GP to crash

Lien, I'eve encountered something similar but it was caused by having a 1099 amount that was greater than the invoice amount (we had AP invoices being imported from our Document Mgmt. System).  It was an utter bear to correct whenever it happened and wasn't caught by an AP clerk before they attempted to post.

------------------------------
Matthew Arp
Business Systems Developer
Hunton Group
Houston TX

Original Message:
Sent: Oct 04, 2019 01:34 PM
From: Lien Truong
Subject: Match invoices posting / landed cost causing GP to crash

I am utilizing the landed cost feature in GP by adding it through enter/match invoices.  When this invoice is posted during batch posting, GP would randomly crash about 1% of the time and has to be restarted.  When this happens, the total amount on the matched invoice is posted to the GL accounts, but total isn't distributed to the line items nor is it posted to the line items.

Looking at the POP10600 table confirms that the status for each line item is 0 so they do not have their cost updated, while the POP30390 shows the distribution to the GL accounts, which causes a reconciliation issue.

  After restarting GP, we can no longer repost the landed cost invoice as it got marked, and unmarking it to repost again puts it into a posted state after with no updates to the items costs.

Have anyone else ran into this issue?

------------------------------
Lien Truong
BREA
------------------------------