Integration Manager - Payable Trx Import - POP error

(0) Share

Report

Posted on by Mark-Admiral

When the Payables Setup option "Warn if Vendor has Existing Purchase Orders" is marked, the Payables Transaction import errors out because of the message that is associated with the notification.

In this case, the user does want to process these invoices even though Purchase Orders exist for the Vendor. There's a valid reason for this. If the Payables transaction was done manually, the user would just click on Continue, but that option is not available when importing. They could just turn of the option to advise during the integration then turn it back on after the integration, but that doesn't seem like a good option.

Any ideas how to push the integration through and have it ignore the message?

Thank ou

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

26P2ER 1,775 on at

Like (0)

Report

Mark - There is an elaborate post by Mariano Gomez on the various configuration settings that are available.

The one setting I would like to try with your integration is the below:-

AllowOpenWindows=False/True
Suppresses checking of Dynamics GP windows status, this is, whether they are close or open.

Change this to True and then restart IM.

http://dynamicsgpblogster.blogspot.com/2009/09/integration-manager-10-ini-settings.html

Was this reply helpful? Yes No
Mark-Admiral on at

Like (0)

Report

Hi Ven

That's a great idea. I'm going to try it and let you know how it goes.

Thanks!

Was this reply helpful? Yes No
Mark-Admiral on at

Like (1)

Report

Hi Ven

Good idea. But that doesn't work.

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (1)

Report

Mark, while Ven has a great suggestion I think the reason it did not work in your case is that this checks for the existence of the open window 'prior' to running the IM - it does not deal with the fact that the execution of the IM forces the window and requires a response from the user.

I will have some time later today to look into IM in more detail related to this - I will see if there is anything I can see that might help.

Was this reply helpful? Yes No
Suggested answer

L Vail 65,271 on at

Like (0)

Report

Mark,

Since it is the option that is causing the problem, you could make an ADO connection to the database and simply 'uncheck' the box using the VBScript that's built in to IM. After the integration has finished, you could go back and check the box. Do you think this might work for you? The table is PM40100 and the column is named WarnIfVenHasExistingPO.

Kind regards,

Leslie

Was this reply helpful? Yes No
Mark-Admiral on at

Like (0)

Report

Hi Leslie

Always can count on you to come up with a good idea. I'll give this a try and let you know how it goes. I'm pretty sure this is it.

Thanks

Mark

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

Mark,

Did this work?

Leslie

Was this reply helpful? Yes No
Mark-Admiral on at

Like (0)

Report

Hi Leslie

While it did work on my instance, the solution has stalled at the client as it goes through IT red tape. They're looking for other options as they don't like the idea of accessing the table. I suggested using a stored procedure instead.

Was this reply helpful? Yes No