Regd. Creation of Port and RFC dest in PI

Hi Experts,
I have two scenarios 1. file to IDOC and 2. IDOC to file.
for first , i need to connect to ECC for posting IDOC. in sap side they have created port ,partner profile etc.
in PI sides i created an RFC destination(sm59) ,given generic name, i have created port(idx1) and mentioned the partener num say(SAP123) ant type (LS). Loaded the meta data in idx2. i am able to post IDOC in sap.
for the second case,i am supposed to receive idoc from sap.
do i need to create another port and rfc destination ? or simply adding the metadata in the prev created port will help.
Actually i tried creating another RFC dest and port and was trying to assign same partner num (SAP123) and type (LS)
while loading the metadata i get an error saying 'basic type of the IDOC is unknown'.
from SAP side the IDOC status is green , saying idoc is dispatched to the target port.But in Trn. SE58, there is error show.
Is this something wrong in PI or SAP ?
Please help me with the steps to be followed with suggested naming conventions if any.
Best regards,
Srinivas

Hi,
Port type shouldbe SAP SYSID ...it is important that you create the port with this naming convention as the name is very important to be followed...
Try to create the port name with the above mentioned..and give a try...
Also post the error generated in the SM58 ...
HTH
Rajesh

Similar Messages

IDOC Adapter and RFC Adapter

Hi experts,
Q1. What are the configurations steps (Transaction codes) required at R/3 and XI while sending the IDOC to XI? Please provide the list of TCodes required at both sides. if any weblog is exists which provides detail explanation on IDOC scenarios plz provide the path.
Q2. While sending the IDOC we need to generate partner profile and port. How many types of port exist and wht each port represents?
Q3. In RFC Sender Adapter we need to create RFC port in R/3 and there we specify Connection type as T which TCP/IPwhy we use connection type T instead of 3 (which represents connection type as R/3). While communicating with SAP systems we need to specify the connection type as 3.
Q4. How many types of partner profiles exist and wht each type represents?
Q5. How to transport design, configuration objects and SLD objects from Development system to Quality system. Please provide me the steps to transport the objects?
Q6. Once the objects are transported a .tpz file is created wht is the purpose of the file and where it will generated? Suppose if Ive transported the namespace from Dev to Quality system then at quality side to which SWC this transported namespace is assigned. Do we need to create any SWC at quality system side?
Cheers
Faisal

Hi Abdul,
for the first one u need to create a logical system and assign that logical system and need to create a port and partner profile and distribute the system,, for that follow this blog
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
2.& 3 ) for the 2nd question the answer was in above u need to create the partner profile and port.
port can be created as HTTP Port and RFC port which are used to communicate with the R/3 server and depends on the requirement we need to choose the port..
4. partner profile creation depends on ur scenario, it is a custmized one it purely depends on the customer requirement, there is no specific partner profiles exists in R/3.
5. For transportation u may choose File level transport or CMS, if u trnasfer through File level it is very easy to maintain and reimport in the production server,, just while exporting from the development server a .TPZ file was created and import this .TPZ file in the production server this gives the entire objects of IR and ID, but when u deal with SLD instead of .tpz there u will be creating .zip file, so u neeed to reimport the file in the production server..
6. The .TPZ file will be created when u export the objects either in IR and ID..., so as i explained in the above point it will go top the export directory of development server and import in production server with IMPORT directory..
regards,
Kishore

Rfc dest

hi ,
1. if i am doing only a file to idoc scenario do i need a rfc dest from SAP to XI
if yes why??
2. if i am doing a idoc to file scenario do i neeed rfc dest and port from XI to SAP
if yes why??

for file to idoc check:
http://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
for sender IDOC check:
https://wiki.sdn.sap.com/wiki/display/XI/SAPR3IdocsToXI--Steps+Summarized
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660?quicklink=index&overridelayout=true

TCP/IP RFC dest entry not displaying in we21

Hi Experts,
i have created an RFC Destination in sm59 with connection as TCP/IP. In we21 when i try to assign the RFC dest to the tRFC port, the dest entry was not displayed. No RFC dest belongs to TCP/IP connection was displayed there.
Please give your input for the cause of the issue.
Thanks,
Siva

Go back to SM59 and see whether you save the new connection and its displayed there ?
Thanks
Prince Jose

Change of RFC dest during Create BP via DSWP

Dear all,
I'm creating Business Partner via Tcode DSWP. Where in the screen "Create Business partner" got to know there are Satellite system being attached on the tree in left hand.
My questions:
1) may i know how can i perform the config if i want to edit/delete/add the system?
2) How can i assign the RFC dest accordingly each of the system?
Please comment.
Thanks in advance.

My Answers:
1.) The creation of Business Partners along with their associated system, system identification number, and user ID is maintained in Transaction BP.
In Transaction BP select the button "Person" to create. Go to the Identification Tab. In the Identification Numbers area you will need to add entries for every system/client combination you want to create messages for.
In the IDType column Choose CRM001
In the Identification Number column maintain the entries as follows:
<System> <Installation Number> <client> <UserID>
For example: PSM 0005063405 300 RGODFREY
So, if you want to edit/delete/add systems that are mapped to business partners you may do that here.
2.) RFCs are required to be generated before creating business partners in BP. This is performed in transaction SM59. Once the RFS are created and generated in SM59, you are free to add/edit/delete the systems according business partner.
Award Points.

Naming of RFC Dest SAP R3- XI- Partner

Hello,
I want to send an Idoc via XI to different external partners. I know how to setup the RFC dest from R3 to XI and so on...
The question is the following:
How do you name your RFC Destinations in R3 system?
One for each external (the final receiver of the Idoc) or is it recommended to use the XI system as destination for all
How to handle ALEAUDIT messages...seems the better way to name the final partner...
what are the suggestions...
Thanks for your ideas,
bye
jo

Hi,
If you are going to be doing an IDOC to IDOC then by naming the partner as your R3 systems then you do not need to manipulate your Idoc's control record in XI.
If you did this wrt to XI, then the IDOC control record will have R3 as sender partner name and XI as receiver partner name... When XI send s the IDOC, the control record will need to be maniuplated with XI as the Sender Partner and R3 as the receiver partner.
I hope this clears the concept. I would recommend naming it( paretner profile ) with respect to the actual partners
The port / RFC destiation can be named with respect to XI and used in the partnerinside the partner profile.
Regards,
Bhavesh

Regarding ports and partner profiles in ALE.

Hi All,
Please tell me how to transport the partner profiles and ports from Development to Quality systems.
Please reply asap.

SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

Creation of Copy and insert in Table

Hi guys,
 I am new to Web Dynpro.I have created one table from SAP by calling of RFC Adaptive method. Now i want to create copy the table single or multiple rows and paste in same table.
 Could anyone please send me that exact documentation for creation of copy and paste button.
Regards
Velu.

Hi Kulanthaivelu,
There is no such exact documentation. But you can implement that using the code. You have to keep few things in mind for this particular code:
1) There should be one empty row where you want to paste the selected row.
2) You cannot copy a selected row on a row already having some data. If you want to do that you have to modify the code.
3) This code is not for multiple copy & paste. For doing that you can modify the code.
Steps for Copy:
1) Create a button and create a action for that say Copy
2) Write this code for implementation of this function:
public void onActionCopy(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionCopy(ServerEvent)
 int currentIndex = wdContext.node<having_the_attributes_for_column>().getLeadSelection();
 IWDNodeElement ne1 = wdContext.node<having_the_attributes_for_column>().createElement();
 WDCopyService.copyCorresponding(wdContext.node<having_the_attributes_for_column>().getElementAt(currentIndex),ne1);
 ne = ne1;
 //@@end
Steps for Paste:
1) Create a button and create a action for that say Paste.
2) Write this code for implementation of this function:
public void onActionPaste(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionPaste(ServerEvent)
 int currentIndex = wdContext.node<having_the_attributes_for_column>().getLeadSelection();
 IWDNodeElement tempElement = wdContext.node<having_the_attributes_for_column>().getElementAt(currentIndex);
 if(!isRowBlank(tempElement)){
 wdThis.wdGetAPI().getComponent().getMessageManager().reportException("You can paste elements only in a blank row");
 else{
 WDCopyService.copyCorresponding(ne,wdContext.node<having_the_attributes_for_column>().getElementAt(currentIndex));
 //@@end
isRowBlank Funtion:
public boolean isRowBlank( com.sap.tc.webdynpro.progmodel.api.IWDNodeElement nodeElement ) {
 //@@begin isRowBlank()
 IWDNode node = nodeElement.node();
 Iterator itr = node.getNodeInfo().iterateAttributes();
 while(itr.hasNext()){
 IWDAttributeInfo info = (IWDAttributeInfo)itr.next();
 if(nodeElement.getAttributeValue(info.getName())!= null){
 return false;
 return true;
 //@@end
I hope this helps you!!
Regards
Pravesh
PS: Please consider rewarding points for helpful answers.

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Preserving SOA Logical Ports and Trust Relationships during DB Refresh

Hi,
I have been searching for this for a while and have not had any luck so far. I thought maybe the vast experience in this community might be able to help me.
I am trying to preserve the SOA Logical Ports and the SMT1 Trust relationships of the target server during DB Refresh. Is there a list of tables that we could export (Much like exporting/transporting RFC Destination)?
Regards
Shantanu

Hi
Check the here under tables if they fits to your needs
Regards
SRT_LP                       Logical Ports
SRT_LP_FEAT            Logical Port Feature
SRT_LP_OP_FEAT     Logical Port Feature (Operation-Dependent)
SRT_LP_SXI_ADDR   Logical Ports: XI Addressing
RSECACTB                 Table for ABAP Access Authorization for Secure Memory
RSECTAB                    Secure Memory: Memory for Encrypted Data
RFCTRUST                 List of existing trusting systems
RFCSYSACL               List of permitted trusted systems for the current system

Remote comparison RFC Dest

Hi,
my system is solution manager 7.1 the last stack
ST-PI 05
when i use in CDMC i get the results i want to try - remote comparison,
when i click on the remote comparison i need to choose RFC dest,
i get a list of rfc that i dont understand from where the solution manager gets it,
also when i try to choose RFC i get the Error
"RFC destination different from destination system"
I find the note 1636163 but it's not compatible my system my ST-PI
Best regards
Naor Shalom
Edited by: Naor Shalom on Feb 2, 2012 9:27 AM

Gyula,
I believe it is all controlled in SM59 where you can set the login id and password as trusted. Whe you call this function module remotely from your program, the logical destination system set in SM59 probably not set as trusted.

RFC_SENDER_XI : RFC Dest Error

Hi All
I am configuring the RFC Destination on the ECC6 of typer TCP/IP to communicate RFC to XI, when i create the RFC destination RFC_SENDER_XI of type TCP/IP i am getting error
Error Details     SAP gateway connection failed. Is SAP gateway started?                    / CPIC
Error Details     ERROR: SAP gateway connection failed. Is SAP gateway started?
Error Details     LOCATION: SAP-Server eccserv_EC6_01 on host eccserv (wp 0)
I have configured the RFC Sender Adapter and i am using the same PID of RFC Sender in my RFC Dest, the RFC destnation is throwing error when i mention the host name of ECC in Gateway host.
Any clue where is the problem, how should i activate the gateway host on ECC, is there any such thing to activate gateway host also when i run TCode SMGW on ECC i am not able to see any active connectiions there.

Now i am getting the error on the RFC_SNDR Adapter
Error Details:
Error: 2007-08-07 11:02:26 GMT+05:30: com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'ECC_SERVER', toParty '', toService '', interface 'ZMK_TEST_RFC', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_RFC_SNDR' (channelId 389e1dc5421a32b5a336160fb15d71eb)
I have done the cache refersh still getting same error

RFC Dest. Parameters for ALIEN Device Integration?

hi,
    I am trying to Integrate Alien Device to SAP AII.
In RFC dest. ALE_OUT
   HOST: ip address
   service/port : 23
   path : /
but I am getting an " ICM_HTTP_CONNECTION_FAILED" error.
thanks,
arul.

hi,
    I am trying to Integrate Alien Device to SAP AII.
In RFC dest. ALE_OUT
   HOST: ip address
   service/port : 23
   path : /
but I am getting an " ICM_HTTP_CONNECTION_FAILED" error.
thanks,
arul.

RFC dest . parameter Problem

Hi Friends,
I am getting a problem when i restore the Source system.
No RFC dest.parameters maintained for the
Warehouse in source system BQACLNT100
When i am asking my basis team to checck for the connection in the source system they are telling that connection is working fine
Please help me to solve this problem
Regards
Raju

hi Raju,
it seems authorization problem,
oss note 126066, old one but may relevant, it's said ALE user (ALEREMOTE) is missing an authorization in the source system - BQACLNT100. what's your r/3 version.
you may have higher version, but still try to check authorization area.
Cause and prerequisites
The error message can have two causes:
1. The user ALEREMOTE is missing an authorization in the source system
    (only for systems as of Release 4.0B)
2. The field "Application server" carries out a conversion to upper
    case in the dialog "automatic connect" (only for source systems on a
    UNIX operating system)
Solution
Solution for 1:
Join the profile S_BI-WX_RFC in the source system to the authorization:
Object:        S_ADMI_FCD
Authorization: S_WF_RFCDEST
Value:         NADM

Regd. Creation of Port and RFC dest in PI

Similar Messages

Maybe you are looking for