Problems with Vertex and ECC 6.0

[Former Member]

We have recently upgraded to ECC 6.0. We applied the CodePage to the R# database and the connection to Vertex was fine. But, the connection no longer worked after we upgraded to release ECC 6.0. We are receiving a TP connect error when checking the connection in SM59. We still do not have a solution. Can someone out there pleasssse point me in the right direction?

[Former Member]

Brett,

Has Vertex provided you a solution to your issue with ECC 6.0?

Regards,

Russ Cook

[Former Member]

I'm puzzled and also concerned on this post. I have Vertex ru ning with ECC 6.0. And I did nothing special to make it work. Are you still having issues?

[Former Member]

Jerry....my man....you might be the answer to my prayers. If you have Vertex running on an i5, V5R3 machine with ECC 6.0....we need to talk. We have a "bandaid" type of solution in place for now. We are not making a "RFC" call to Vertex; we are using the "program resgistration" method to talk to Vertex. There are some issues.....it is a little unstable....but it works.

[Former Member]

We have a solution....but it was not provided by Vertex. We are not using a RFC call (in SM59..."Start on explicit host") to Vertex....we are using "Registered server program" It is a little unstable on our system....but it works....sometimes.

[Former Member]

Hi Brett,

what is unstable there ?

I always use the registered version - already because of performance reasons ...

But, I would register - let's say 3 servers - to that destination ...

If you ensure, that they are always up, I don't had the situation of unstability ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

The Vertex app runs on the Production server. I have the registered program running in a subsystem (called Vertex), and it handles all the request. It is running on IP port "sapgw00" with the rest of the servers that are interfaced into SAP (Fax, Business Connector, Credit Card). I think this is what contributes to the instabiliy. I would love to run it on a separate IP port, with maybe 2 occurances running to handle the request....I just haven't figured out how to make that happen.

[Former Member]

Hi Brett,

sorry, but I think you do not fully understand the difference of an IP and a port ...

The IP is the thing, that makes the servER unique and the Port is the ing that makes the ServICE unique. As you have to use the gateway of your instance it will ALWAYS be sapgw00 as I do exepect that you are using instance number 00. In your case, there is just no reason, to install a second gateway instance - this makes it just more complicated ...

If you want to register from another IP (from another server), this is no problem either. Just move your config & programs over to that other server (where I don't see a reason as well) and it will work, because RFC is used to be located on different servers )

=>

I would just call your current program 3 times and let it run 3 times in the current subsystem, that you opted for and then it will work "round robin" and I would be interested in the question, if it still is unstable ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Brett we use the server method. We are on V5R4, and use Vertex Version 3.1.5 . I run this is the R#_xx sbs. We have no issues running in this manner. Here's the cl we use.

ADDENVVAR ENVVAR(RFC_INI) +

VALUE('/usr/sap/PRD/SYS/profile/saprfc.ini')

CALL VERRFC ('-D' 'VERTEX')

saprfc.ini:

DEST=VERTEX

TYPE=R

PROGID=VERRFC

GWHOST=HARPO

GWSERV=sapgw10

RFC_TRACE=0

Our instance number is 10.

[Former Member]

We received an email today from the vendor which states the message below. I have sent them a not so nice response stating the issues this will cause with our current upgrade plans.

-

---

Dear Vertex Sales Tax Q Series Customer:

Our records indicate you are an iSeries AS/400 user. There are certain AS/400 configurations that are not compatible with our current Vertex Sales Tax Q Series (STQ) and SAP TransLink products.

The Vertex Sales Tax Q Series product team creates and maintains hundreds of build configurations to support a wide variety of ERP platforms. While new platform configurations and products integrations are developed and updated monthly, Vertex does not currently offer the following builds:

• STQ Core build that is compatible with the latest iSeries V5R4 for AS/400

• SAP TransLink that is compatible with the SAP 4.6-Extended kernel to 6.4 kernel, and higher.This includes all ECC versions of SAP on iSeries – AS/400.

[former_member204746]

call the company that manufactures Vertex to find out if it supports ECC 6/0

[Former Member]

I have done that....they are working on the problem.

[Former Member]

What version of Vertex are you using? I have ECC 6.0 running in test instance, with Vertex working. Had some issues with codepage, but not upgrade....as I recall.

[Former Member]

We are running Rel 3.1.5 in Dev/Qa and Prod, and 3.2 .21 in SandBox. All instances have the codepage performed on them. Vertex worked after codepage, but not after upgrade. What issues did you have? We should talk. My direct number is 205-271-6051 or 1-800-877-5839 will ring in the datacenter.