Unhandled script exception index 0 error when clicking on source document from GL Transaction for Intercompany payments.

(0) Share

Report

Posted on by Katy Deming

595

"Unhandled script exception index 0 of array 'PM Transaction Abbreviation' is out of range in script 'PM_Transaction_Inquiry_Scroll_FILL'. Script Terminated". This error occurs when in the GL Detail Inquiry, selecting a record and then clicking on the Source Document. This is only happening on the Intercompany transactions, so records with an audit trail # beginning with ICTRX. It's not limited to one batch, it seems to be every Intercompany transaction. Is this a GP limitation? You can't access Vendor detail for intercompany transactions through the GL Detail Inquiry or is there something else we should try?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Redbeard 12,931 on at

Like (0)

Report

RE: Unhandled script exception index 0 error when clicking on source document from GL Transaction for Intercompany payments.

It has been awhile since I have recommended or deployed Dynamics GP intercompany. So someone please correct me should I be wrong. I believe this is a limitation of the solution. I also noted some of the GP 2015 new features are related to intercompany. Here is a link to an article, which seems to indicate this is the case. It also mentions several alternatives to GP 's native intercompany functionality.

dynamicserppros.com/intercompany-processing-in-microsoft-dynamics-gp

Was this reply helpful? Yes No
Suggested answer

Victoria Yudin 22,768 on at

Like (0)

Report

RE: Unhandled script exception index 0 error when clicking on source document from GL Transaction for Intercompany payments.

Katy,

What version and build of GP are you using? In my GP 2013 SP 2 when I drill down on an intercompany GL transaction and then click on Source Document, I get the following pop-up:

"Unable to zoom. The transaction originated in General Ledger."

Are you possibly using a 3rd party product for Intercompany or do you have a customization that would do something different?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Unhandled script exception index 0 error when clicking on source document from GL Transaction for Intercompany payments.

I work with Katy - This customer uses the interco functionality in GP 2010.

Was this reply helpful? Yes No
Sheilajr 745 on at

Like (0)

Report

RE: Unhandled script exception index 0 error when clicking on source document from GL Transaction for Intercompany payments.

Hello Katy,

I had the same message but would also like to add some information to this conversation to help clarify some of the confusion and to make sure that you can find the information that you are looking for.

I am using GP 2013 SP2 and when you post an I/C transaction from the originating company AP it will create a PMTRX posting to the source company GL and the destination company will receive a GL transaction with the ICTRX source code.

You cannot drill back to the AP transaction while logged into the destination company because it originated in the AP of the source company. The vendor does not live in your destination company.

Although you can't see this in the Journal Inquiry, you can see originating vendor information in the destination company's GL Account Transactions SmartList. For example: Originating Company ID, Document Number, Master ID, Master Name, Control Number, Posted Date, Journal Entry, etc. (each field name starts with the word 'Originating'. Add these columns to a SmartList favorite and you'll always see the payable information you need.

I am getting the same message that you have described when drilling back onto the source document from the GL Detail Inquiry in the Originating Company. The error displays more than one time and then finally pulls up the Purchasing Zoom window & then I can highlight the document & drill into the Payables Transaction Entry Zoom. I think the problem is with the Purchasing Zoom window since I don't believe this window needs to open. If I drill back again from the Journal Inquiry screen I sometimes don't get the error & the correct document screen opens. I believe that the data is OK in the database it just a matter of what screen is being called up. I'll be checking this out with the Microsoft team to see if they have maybe resolved this in a future version.

Sheila Jefferson-Ross

Was this reply helpful? Yes No