Ansicht
Dokumentation
05203 - Problem with Vertex tax interface
General Data in Customer Master General Material DataThis documentation is copyright by SAP AG.
Problem with Vertex tax interface
You need to change the first line, and put the library name behindthe Translink line. A 46C instance that did work had the follwing.
VERTEX is the name of our Relational Database for Vertex. VTSQA6COL
is the collection with the regprxxxx files, VTSQA6 is equilvant to
Vertex's to VERLNK. We used no id or passwords in 46C in this config.
000300010726[HKEY_LOCAL_MACHINE/SOFTWARE/Vertex/TransLink/VTSQA6]
000400000000
000500000000"DefaultLocDataSource"="VTSQA6COL"
000600010730"DefaultLocServer"="VERTEX"
000700000000"DefaultLocUserID"=""
000800000000"DefaultLocPassword"=""
000900000000"DefaultRateDataSource"="VTSQA6COL"
001000010726"DefaultRateServer"="VERTEX"
001100000000"DefaultRateUserID"=""
001200000000"DefaultRatePassword"=""
001300000000"DefaultRegDataSource"="VTSQA6COL"
001400010726"DefaultRegServer"="VERTEX"
001500000000"DefaultRegUserID"=""
001600000000"DefaultRegPassword"=""
001700000000"DefaultTdmDataSource"="VTSQA6COL"
001800010726"DefaultTdmServer"="VERTEX"
--- In SAP on System iZy..., "rwc0225" <russ.cookZg...> wrote:
> Hi Jim,
>
> I have another question for you. When you migrated to release 2.0
of
> Vertex, did you reconfigure a REG member in the translink file? On
> our old version of Vertex, this member use to be called CFG. If
you
> have a new REG member, could you share with me the syntax for the
> first 10 lines or so. Our's currently appears as follows:
>
> REGEDIT4
>
> [HKEY_LOCAL_MACHINE/SOFTWARE/Vertex/TransLink]
>
> "DefaultLocDataSource"="VERTEX"
> "DefaultLocServer"="AS400Q3"
> "DefaultLocUserID"=""
> "DefaultLocPassword"=""
> "DefaultRateDataSource"="VERTEX"
> "DefaultRateServer"="AS400Q3"
> "DefaultRateUserID"=""
> "DefaultRatePassword"=""
> "DefaultRegDataSource"="VERTEX"
> "DefaultRegServer"="AS400Q3"
>
> Thanks,
> Russ
>
>
>
> --- In SAP on System iZy..., "jcummins1942" <jcumminsZy...> wrote:
> > We are testing 46C, and in going from 31H Vertex 2.0 to the 46C
> > enviroment, we found Vertex's LIBRFC would not connect, but in
> their
> > library they had also deliveried a LIBRFCBCK. The LIBRFCBCK
> version
> > had to be renamed to LIBRFC for Vertex to run in the 46C
> enviroment.
> > I don't know if this is applicable in your case, but you might
> check.
> >
> >
> > --- In SAP on System iZy..., "rwc0225" <russ.cookZg...> wrote:
> > > We are attempting to upgrade our Vertex tax package to the new
> 2.1
> > > release of the software. We are currently running on release
> 4.5B
> > of
> > > SAP and V5R1 of OS400. After installing the new Vertex
software,
> we
> > > have been unable to get the RFC connection to work in SM59.
The
> > > error we receive in SM59 is a timeout error. We are suspecting
> > that
> > > there is a problem with the VERRFC program that get called or
the
> > > LIBRFC service program. We have been unable to find any good
> error
> > > messages in the joblogs or the RFC trace. Is anyone on this
> group
> > > using release 2.1 of Vertex on a 45B system? I am thinking that
> > > perhaps the VERRFC program was created with a 46 version of
> LIBRFC
> > > but VERTEX support has been very poor in helping us determine
the
> > > problem. Any ideas in determining the problem would be
> appreciated.
> > >
> > > Kind regards,
> > > Russ Cook
Durban Tours - Südafrika Safari
CPI1466 during Backup BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 4254 Date: 20240328 Time: 161934 sap01-206 ( 3 ms )