Which eConnect schemas to use?

(0) Share

Report

Posted on by Community Member

I am just getting started with my review of the Dynamics GP eConnect API and have the following questions please:

1a. I need to send vendor bills/invoices (ie. check requests) to Dynamics GP using the eConnect API. Do I use PMManualCheckType for this?

1b. How would I cancel that transaction later on?

2a. I need to send employee expense reimbursement check requests to Dynamics GP using the eConnect API. Which schema would I use for that? I checked UPRManualTrxType which includes taCreateManualCheckLineInsert but the MLTRXTYP element does not include a code for an expense reimbursement.

2b. How would I cancel that transaction later on?

Thank you!

*This post is locked for comments

All responses (5)

Answers (3)

Community Member on at

Like (0)

Report

RE: Which eConnect schemas to use?

Thank you Steve and Somakarpagamoorthy for your detailed replies. You have pointed me in the right direction and I think I am now ready to start building my interface to Dynamics GP!
Verified answer

steveendow 2,281 on at

Like (0)

Report

RE: Which eConnect schemas to use?

Hi Randy,

Web Services does have some capability to cancel or delete, but it is a completely different API. While it can perform a few of the 'cancellation' type operations that eConnect cannot, it does have some limitations of its own that can make it frustrating to work with. So your requirements may dictate whether eConnect or Web Services makes more sense.

You do also have the option of doing some things directly in SQL. But I wouldn't typically recommend doing voids or deletes via SQL.

Employee expenses processed through AP would be done with Payables Transactions, just like a vendor invoice. The employees are setup as vendors (with a vendor ID), and would have expenses entered like vendor invoices and would then be paid through an AP check run, if you are using Dynamics GP to process your AP checks. The employees could have a vendor ID that is the same as their employee ID, if that would help, but the employee record and vendor record are separate and would have to be maintained separately. When importing employee expenses, you would have to know the employee's corresponding vendor ID--you could potentially store it in an extra employee user defined field, or store the employee ID in an extra vendor field, which would effectively provide a mapping between the two.

If you aren't using GP for printing checks (such as an external payables service, or printing checks outside of GP), that changes things completely. If that is the case, please provide more background on your process and I can offer additional guidance.
Verified answer

soma 24,410 on at

Like (0)

Report

RE: Which eConnect schemas to use?

Yes. We can not cancel,delete or void the documents from GP with using eConnect.

But, few of the method references are available for delete the records from GP with using web services. But, this is not available for all type of transactions(especially AP).

For your reference, please have a look on the below link.

msdn.microsoft.com/.../cc508424.aspx

Additionally, while recording AP transactions from eConnect with using the schema (taPMDistribution & taPMManualCheck ), you can not use employee id instead of vendors. This is standard functionality. I hope AP used to record expenses with belongs to vendors, not employee.

Hope this helps!!!
Community Member on at

Like (0)

Report

RE: Which eConnect schemas to use?

Thanks Steve! You wrote...

"eConnect can't cancel, delete, or void..."

Is this common to ALL automated/non-human interface options or do some interface options allow for these transactions to be cancelled (eg. web services option)?

"In my experience, expense checks are usually handled through AP..."

Would that be the PMManualCheckType schema? If so, both the taPMDistribution and taPMManualCheck require a mandatory VENDORID field. How do you specify the employee instead of the vendor?

Thank you!
Verified answer

steveendow 2,281 on at

Like (0)

Report

RE: Which eConnect schemas to use?

Hi Randy,

1a. For vendor invoices, you would use PMTransactionType / taPMTransactionInsert. Those invoices would then be posted in GP and your AP department would do a check run to pay those bills.

1b. eConnect can't cancel, delete, or void Payables transactions after they are imported. That would have to be done in GP by the AP department.

2a. In my experience, expense checks are usually handled through AP, not through payroll (UPR), but I suppose your company might process certain employee expenses through payroll pay codes. I would check with your payroll and AP department to determine which GP module they use to issue employee expense checks.

2b. eConnect can't cancel, delete, or void Payroll transactions. That should be done through GP.