Ansicht
Dokumentation
03722 - Problems with RFC destination for Vertex
CPI1466 during Backup ABAP Short ReferenceThis documentation is copyright by SAP AG.
Problems with RFC destination for Vertex
In the past I had 2 production instances (02 and 05) created on 2separate AS400s (Q2 - central instance and Q3 - app server). These
were opticonnected together. I had a RFC destination set up in SM59
that pointed to a program for Vertex and the gateway service that
existed on the central instance 02. This was working fine. When a
batch job or dialog was run on the 05 app server instance that
required Vertex it ran on the central instance and ran under user id
PRD02.
I recently created a new PRD app server instance 09 on the same AS400
as the central instance 02. Now when I attempt to use the same Vertex
RFC destination, it is using the user id PRD09 instead of PRD02. I
do not understand why this works differently between the 3-tier
setup, and running a new instance on the same box as the central
instance. In both cases, they are pointing to the same gateway and
host. I need the RFC destination to always use the same SAP instance
user id (PRD02) because Vertex has a paramter file where you must
code the user id to access the Vertex SQL collection. Has anyone run
into a problem like this?
Durban Tours - Südafrika Safari
RFUMSV00 - Advance Return for Tax on Sales/Purchases Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 1568 Date: 20240420 Time: 140449 sap01-206 ( 3 ms )
