PPV Not Displaying with PO Receipt

eConnect, when used with: Microsoft Dynamics GP 9.0 Microsoft Business Solutions–Great Plains 8.0 Microsoft Business Solutions–Great Plains 7.5

1.When loading a PO Receipt containing items with a FIFO/LIFO Periodic valuation method (standard cost), eConnect is not creating the distributions properly. eConnect is not handling this.

2.When loading a PO Receipt containing Non-Inventory items, eConnect is not creating the distributions properly for PPV.

You should handle this problem in taPOPEnterMatchInvHdrPost event.

Refer:https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?WTNTZSMNWUKNTMMYVTQUUXNNZOUKYPPPSMMXUWTPWLUULNTMZXTMXTOPZMLWWKUSTVTKSXKQQUOWLQPOSYNYUXWUUSKSVQLN

Why eConnect use windows authentication

While I am going to talk about eConnect, I would like to disclaim that the explanations are JUST out of my understanding of the concepts of eConnect and the structure. Please do refer to some more articles from Microsoft, Consultants worldwide and others to know more about this and also correct my own understanding in case you find it irrelevant.eConnect use Windows Authentication to converse with GP Databases instead of the traditional SQL Authentication (which GP uses). There could be various reasons why it is designed in such a way.

I am listing some of the important reasons:

1. eConnect does not require GP Application, or precisely, it does not depend on an Instance of GP Application to be running (which is the case with Integration Manager for most of its Integrations). This would mean that, the login credentials for an eConnect integration cannot be inherited from anywhere. We still have to establish a Connection String (ODBC) to the GP Databases to access the data and manipulate it.

2. eConnect is designed to run in the background and access/manipulate the GP databases without anyone's idea of what's going on with the records and database. Apparently, there should be a kind of authentication which is much more stronger than the basic SQL Authentication, which the Windows Authentication provides us.

3. eConnect is the base for almost all the web based features we have for Dynamics GP, such as Webservices, Business Portal, etc. We cannot have a compartively weaker Authentication level when we allow anyone to access GP Databases from anywhere.4. eConnect can utilize MSMQ (Microsoft Message Queuing), to queue the integrations from anywhere to the Dynamics GP server. In such cases, it has to have a Windows Authentication to pass the MSMQueuing validations.I am still learning more concepts on these two Authentications and its scope with respect to GP and related products. I will update more points with references, so it does not just go in as a theory.

-Vaidy

eConnect errors

Error: Login failed for user 'User name'.
Cause: The user does not have a Windows Authentication Login ID in the SQL Server.
Solution: Create a Windows Authentication Login ID in the SQL Server

Error: Server process could not be started because the configured identity is incorrect. Check the username and password.
Cause: The user has changed the System Password after the eConnect installation.
Solution: Change the eConnect Identity .
1.Go to Start --> Run, type dcomcnfg and click the OK button.
2.In the Component Services window, Expand Component Services > Computers > My Computer > COM+ Applications.
3.Under COM+ Applications, locate eConnect 8 for Great Plains and Right Click it and select Properties.
4.In the Properties window, select the Identity Tab. In that click the This User option button and enter the new Login Credentials for the user and click the Apply button.

Error :The partner transaction manager has disabled its support for remote/network transactions. An error occurred while enlisting in a distributed transaction.
Cause : This error comes up when you are doing inter sever transactions via Distributed Transaction Cordinator MSDTC.
Solution:
In Control Panel > Adminstrative Tools > Component Services > Expand Component Service > Right Click My Computers > Properties > MSTDC Tab > Click on Security Configuration button > Check Network DTC if not checked and Check Allow Inbound, Allow Outbound and select NO AUTHENTICATION REQUIRED

Error:The transaction has already been implicitly or explicitly committed or aborted
Cause:Network security for the particular user.
Solution: Add enlist=false in the connection string. Connection string would be like this;
ConnectionString = @”data source=SERVERNAME;initial catalog=DBNAME;integrated security=SSPI;persist security info=False;packet size=4096;enlist=false”;