Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 735
  • Last Modified:

Great Plains 10.0 Integration Manager and Due Date

We are using Integration manager to attempt to update the Due Date.  However - after the transaction is successfully imported and we then look at the record in Great Plains, the Due Date is set to the calculated date from the default payment terms.  We would like to be able to override the due date from the calculated value based on the due date.  For instance - an account is set for default to 30 day net which would auto-calc to 10/15/2010 - we pass in a due date of 10/1/2010 with integration manager  but it still show 10/15/2010.

Any ideas?
0
Obeg_
Asked:
Obeg_
  • 2
  • 2
1 Solution
 
Victoria YudinCommented:
Are you're trying to update posted transactions or are these brand new transactions you're importing in?  What transaction type?

If these are already posted, I do not believe IM can update the due date.  You can either change the due dates directly in GP (recommended) or, if there are a lot, you could do this in SQL.  Without knowing what transaction type you are using it's hard to give a more specific answer than that.
0
 
Obeg_Author Commented:
They are all new transactions.

I expect that I need to pass in something for Payment Terms to let it know not to override my date with the default - but I have tried passing in blank and DUE ON RECEIPT  and neither helped.  

Currently my client imports the transactions and then goes and manually changes the due date.  Obviously this is not optimum.
0
 
Victoria YudinCommented:
You have not said what transaction type, so I just picked the PM Transaction to test with.  Here is what I did in the Destination Mapping:

On the Payment Terms section I choose Use Constant under Rule and entered a date, then I switched to the Options tab (still on the Payment Terms section) and chose Use Field Rules under the Rule for Record Source.  (Without this change it did not work properly!)

I left the Payment Terms field on the main section defaulted to Use Default, not mapped to anything.

When I import with these settings I have the Payment Terms populating from the Vendor setup, however, the due date populating correctly to what I set in IM - I set it to be in the following year, just to make sure.  I would expect this to work in a similar way if you have the Due Date in your source data, however, you may need to play with the Rules on the Options tab for the Payment Terms.

If this is still not working for you, can you provide some more detail, including the type of transaction, and the version and build of IM?

Also, if this is a situation where a payment term CAN be set up to calculate correctly, I would recommend that over passing in a due date for each transaction.  That way the payment term displayed on the transaction in GP will match the calculated due date.  
0
 
Obeg_Author Commented:
Excellent!  Thank you!  It was the setting under options that I was missing!

This import was set up and running for years by the previous contractor and Friday afternoon was my first time looking at it or Integration Manager in order to add the due date column.  

I am going to look into mapping over their payment terms from the inventory system but wanted to take this baby step first as there is a bit more work to do on that side first.


Thanks!
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now