PI System Copy (JCO RFC destinations missing)

Hi,
We are doing a Homogeneous System Copy of a PI 7.0 system:
- Source system --> PI 7.0 Production system ("PIP")
- Destination system --> PI 7.0 Development system ("PID")
We are executing the specific POST activities for a PI system (point 5.2.3.2.4 in the "System Copy for NW2004s SR2 Abap+Java" guide). In point 5.2.3.2.4.2, PI RFC destinations must be adapted in both Abap (SM59) and Java (Visual Administrator, JCO RFC Provider). The problem is that in all PI abap RFC destinations (AI_RUNTIME_JCOSERVER etc) the program_id is pointing to our PI
Production system ("AI_RUNTIME_PIP"), is it OK?
Besides, in Visual Administrator (JCO RFC Provider service), all the required RFC listeners for PI ("AI_DIRECTORY_PIP", "AI_RUNTIME_PIP", etc.) are missing after the system copy (???). Must these RFC listeners be manually created? How can we do it? Must we create them with the development SID ("AI_RUNTIME_PID") or with the production SID ("AI_RUNTIME_PIP")? Perhaps PI configuration wizard must be executed after the system copy of a PI system so that these JCO RFC destinations are created, but we are afraid executing the wizard could harm the PI configuration...
Thanks in advance.
Jon Larrucea

Hi Jon
Probably the best thing to do is just create these destinations manually. You will need to do this in SM59 and the Visual Administrator. See the link below:
Creating RFC Destinations in the ABAP and Java Environments
http://help.sap.com/saphelp_nw70/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
Regards
Mark

Similar Messages

Purpose of RFC and JCO-RFC destinations

Hi,
Can you please tell me what is the purpose of RFC and JCO-RFC destinations and where do we create them.
Regards
Rahul

Hi,
RFCs are SAP interfaces for communicating between SAP systems. They accept inputs, do the processing and return the output values. You can call rfcs through different applications like web dynpro.
http://help.sap.com/SAPhelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
JCO helps Java applications to connect and communicate with SAP backend systems. Using JCO we can make rfc calls. JCO will help in getting the rfcs in a java compatible format.
http://help.sap.com/saphelp_nw04/Helpdata/EN/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm
Example for setting up jco destinations:
http://help.sap.com/saphelp_erp60/helpdata/EN/ca/115e4088dc0272e10000000a155106/content.htm
Regards,
Shyam.

RFC destination for RFC to File scenario

Hi,
I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
Step 1:
For this a Registered server program is created in Jco RFc Destinations with,
Program Id : pgm1
Gateway host : PI's host
Gateway service : PI's service
application server host: ECC's host
system numer     : ECC's number
client : ECC's client
logon user : ECC user
password : pwd
Step 2:
In SM59, TCP/IP connection the following parameters are given:
Program ID : pgm1
Gateway host : PI's host       -
> is this correct
Gateway service : PI's service      -
> is this correct
Step 3:
So i am calling the RFC in ABAP program (R/3 system) like:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
Step 4:
In PI side,
for RFC sender I am passing :
Application server : PI server
Application server service: PI host
program ID: pgm1 which was created in the previos step
For RFC Metadata Repository Parameter, i am passing all the values related to R/3
Please let me know whether the steps and values i given is correct.
B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
so i am confused as which is the correct method. pls clarify

Ok I will try to explain....
Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
IN BACKGROUND TASK
DESTINATION 'R3_TO_XI'
TABLES
    comp_detail = company_detail.
COMMIT WORK.
Regards,
Sarvesh

RFC Destination Settings

Hello Gurus,
Earlier we had 2 ECC systems in the landscape.
Purchase requisition A from APO system supposed use RFC destination 1 and reflect in Plant XXXX
Purchase requisition B from APO system supposed use RFC destination 2 and reflect in Plant YYYY
Now we have only 1 ECC system in the landscape. we have changed the publication settings accordingly. but preq still not getting transferred correctly to ECC system.
Debugging the code shows system trying use wrong RFC destination.
Is there any other configuration setting we are missing.
Please advise.
Thanks In Advance
Shyam

Hi Shyam,
Please find my suggestions in regards to respective configuration settings.
1) Did you delete the obsolete RFC destination(Logical System) from your landscape?
2) Did you correct the RFC destination of plant YYYY to RFC Destination1 (incase you scrap RFC destination2 from landscape)?
3) Check what is the Logical System that is maintained for the location YYYY from the table /SAPAPO/LOCMAP in APO system.
4) Similar check for the products in the table /SAPAPO/MATMAP.
5) Remove the obsolete ECC System from the BSG using T-code /SAPAPO/C2.
Post checking and correcting, do an intial transfer of locations via CIF from the current ECC system.
Thanks,
Santosh KB.

System copy questions

Let's assume we have two CRM systems CRD(dev&qas system) & CRP(prd system), and corresponding R/3 systems R3D & R3P, As I read some documents concenring system copy within CRM, I still have doubt on the transport strategy.
on CRD, After making the manual customizing and finish test replication of customizing/master data/transaction data from R3D, we would like to transport the customzing to CRP, and corresponding customizing from R3D to R3P. But I am not sure:
1. Only manual customizing in CRD will be transported to CRP? how about the customizing object download from R3D(e.g. condition customizing), are they also transported to CRP or need replication again from R3P?
2. the organizational model transported or need replication again?
3. internet user transported or need replciation again?
4. RFC destination transported or need cusotomizing again in CRP?
5. If I use the same logical system name in CRD & CRP, is there anything I should pay attention to?
6. number range transported or need cusotomizing again in CRP?
7. how about the java applications, like ISA web shop xcm settings?
Patrick

Hi Patrick,
1 - You must do an initial download of the R/3 adapter objects such as customising and business data in each system.
2 - Manually set it up in each system. If it is large then there is a transport program RHMOVE30.
3 - Users must be created in each system.
4 - RFC destination created in each system and all initial set up done (table CRMRFCPAR for example in R/3 prd)
5 - Create a new logical system name, don't use the same as dev.
6 - Transport the number range (this should have been done when creating it). If this hasn't been done already then best to do it start in production due to the current number will not be at the start in dev
7 - should be on different server so would require new xcm settings to point to the different production server
Cheers
Andrew

RFC destination ((((URGENT PLZZZZZZZZ)

Hi Sap Gurus
I am executing bd82 by giving my other client logical system that means mm_re
There It is giving one message
port could to be created
RFC destination MM_se( this is RFC destination name) is not specified for mm_se( logical system name)
Enter RFC destination restart generation is coming what I have to plz guide me
Points will be rewarded

Hi,
You need to create a port from we21 transaction.
You need to provide these 3 parameters. 1. Rcvpor 2. rvcprt 3. rcvprn.
in your case rcvpor is RFC destination name (mm_se)
port no. means your dev server name (like dev200 etc..)
port type may be LS(Logical system) in your case.
if its related to vendor then you can create port under LI. or customer then it is KU. etc..
Look at this link.
https://secure.topxml.com/biztalkutilities/walkthroughs/SAP%20Configuration.pdf.
Thanks,
Yoga.
Edited by: Yoga JJ on Feb 4, 2008 1:23 AM

RFC destination definition with non-unicode external program

Hello All,
we have one issue with our RFID system connecting to WM system (SWD).
For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.
But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.
We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.
To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
Anyone know how to help ?

Hi Jeongbae,
as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
In earlier releases, this is not possible.
In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.
Please check SAP note 788239.
Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
In addition I would recommend to have a look at SAP note 1021459.
However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
Best regards,
Nils Buerckel
SAP AG

RFC destination with CIF application case !

Hi,
Can someone explain the difference between
Assigning a logical system to a RFC destination and
u201CAssigning a logical system to a RFC destination with CIF Application case" (there are 4 of them in all as i see - AC, RL, RQ, DG, AC- refers to availability check)
e.g I have 2 entries in the system landscape settings.
1) Logical system u2013 RFC destination
2) Logical system- application case AC u2013 RFC destination.
Even if I remove the 2nd entry, the relevant APO ATP FMu2019s are called (just a negative testing to see what goes wrong without application case) but am clueless about this concept of CIF application case. Why such a provision to begin with. The context help says. some transaction need to have synchrious RFC and hence the need but i see the same even without his entry.
Regards,
Loknath

Hello Loknath,
If I understand your query correctly,
1.Assign logical system to RFC destination is OK for you.
2.Assigning the RFC destination to a specific CIF application is used in the following case,
You have a system/service user set up for communicating with the R/3 system thru CIF & this is assigned to the RFC destination assigned to the point no:1
& for debugging purposed you need a dialogue user, so you may assign this dialogue user to a different RFC destination & assign it here in the customizing (Assign RFC to application cases) to the application Debugging..so that while the particulat application is called (Debugging...CIF cockpit...etc)the corresponding settings from the different RFC destinations will be used.
I could not understand your query, where u relate some ATP stuffs with this CIF topic...
Thanks,
Mahesh

Clarification regarding RFC destination

Hi Ramesh,
Thanks for your information, can you please tell me do we need to create port and logical system name for creating RFC destination.
Thank
siva

Siva,
You do not need to create port / logical system while creating RFC destination.
Port and Logical system comes into picture while setting up Partner profile for idoc communication.
Nilesh

Question: Can Jco RFC Provider registers Program Id for BW7.3

Hello, Friends
I encounter the following issue and I wonder whether it is supported by Netweaver product. Please help answer.
My scenario is to create RFC (TCP/IP Connection) in ABAP server with program id registered by Jco RFC Provider (Visual Admin of NW7.02 Java)
If my ABAP BW NW server is 7.02 version, RFC can be tested successfully. However, for this time, I worked on another ABAP BW NW 7.3 Server and I create the RFC(TCP/IP Connection) with program id registered by Jco RFC Provider. As a
result, the RFC cannot find the program id registered by Jco NW 7.02 Java. Does Netweaver support ABAP 7.3 RFC with Program id registered by Nw 7.02 java Jco RFC provider?
Thanks a lot!
Welkin

Hi, Ejersbo
If you are using 7.3 portal, you can refer to the following on how to register Jco RFC provider on 7.3 Java:
(1) Open http://<server>:<port>/nwa
(2) Search for "Jco RFC destinations", open "Jco RFC destinations"
(3) Create a Jco RFC destination, with program id in the same name as the one which is used in your ABAP RFC in SM59
Welkin

RFC destination error in transport

Hello,
We are trying to import a transport into our BW QA system and we keep getting return code 8 with the following text:
BW RFC destination <systemname> is not maintained in the source system
Message no. R3078
The transport contains cubes and three ODSs. After the transport fails and I check the QA system, the cubes are active, but the ODSs are not.
I searched SDN and found another thread explaining the same problem and I tried everything suggested there. I looked in RSA1 --> Mapping of the source system names, and the BW DEV and QA systems are listed. I also looked in SM59 and checked the RFC connection, and that is ok as well.
Does anyone have any suggestions?
Thanks
Charla

I have searched OSS further and found that the contents of my RSLOGSYSDEST table are off.
The contents are as follows:
Src System    RFC Destination
AWQ100          AWP100
QAT100          QAT
I believe that in the above table, the AWP100 should be AWQ100. I looked at this table in our production environments, and in those cases the Src system entry and RFC Destination entry are the exact same, so I think this should be the case in our AWQ100 system as well.
Just curious if anyone knows if there is a program I can use to modify this table.
Thanks
Charla

Checking RFC destination availability

Hello,
In a transaction I'm working on, I loop at a table containing RFC destinations, and I call the same function module on each of these destinations. What I would like to do is, prior to the call, test if the system behind the RFC destination is available (neither completely crashed, nor just blocked by an administrator).
I tried to do this by simply calling any BAPI on the remote system, and check if there was a connection error. But the problem is, if the system is not down but just blocked by an administrator, the transaction suddenly displays the logon page of the remote system.
Do you know of a simple way to do this ?
Thanks in advance.

Hello Thomas
You could try with asynchronous RFC calls (for details refer to the ABAP documentation of CALL FUNCTION).
Asynchroner RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Regards
Uwe

LCRSAPRFC is missing in Visual Admin (JCo RFC Provider)

H y,
I'm facing a problem while connecting our SolMan via RFC to SLD.
Found documents explainig how to set up connection to SLD.
SAPSLDAPI (was present in Abap and Java - wrong credentials - repaired)
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
How can be the LCRSAPRFC added to JCo RFC Providers?
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Thanks in advance
Tom

Hi,
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Not Required.
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
Usual Process
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination:LCRSAPRFC
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: LCRSAPRFC_<SID>
where <SID> is the SAP system ID of your Integration Server host.
Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host.
To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and
gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in
Target System.
8. Save your settings.
Java Stack
SAP J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the SAP J2EE
Engine administration tool.
If you do not know how to start, see section How to start the SAP J2EE Administration Tool .
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for LCRSAPRFC that you used in the step Maintaining the RFC connection above.
Additionally, set the number of processes to 3.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client
and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
Testing
After you have maintained an RFC destination in both the ABAP and Java environment,
you can check it as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection.
No error should be displayed.
Regards,
Rao.Mallikarjuna
Edited by: Rao Mallikarjuna on May 31, 2008 11:40 AM

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

RFC destination for Sender System in R/3 4.6c

Hi All,
I am trying create a RFC destination in R/3 4.6 system which will be used as sender RFC communication channel in Xi scenario. However i dont seem to have all the options such as activation type,gateway host and service which used to be there in SAP Enterprise or mySAP ERP systems. Can some one guide me to create an RFC destination in 4.6 system that will be used as a sender RFC system?

Hi Arul,
One more important point u have missed.
Program ID,
When ur configuring sender service from RFC,The most important point is Program ID.
Use some name and create it.Use the same name in SM59.
s such its very crucial .Activate them .make sure the destination for that programID is what u expect.
Reghards
chandra shekar

PI System Copy (JCO RFC destinations missing)

Similar Messages

Maybe you are looking for