on 03-20-2008 11:14 AM
Hi,
I am getting an error code : 56 as "Partner profile not defined " ,but in SAP R/3, i have defined Partner profile (WE20).
Now i got a doubt ..
In SAP R/3 - i have to define the RFC Destination right... but should the Logical sender system be of XI or of the source system(third party) for the RFC Destination ?
I have defined the logical system of XI but when i test that Remote Logon it is not connecting but Test Connection is Successful.
I had followed the steps given in various threads, but i am not clear enough and not able to proceed further.
Thanks in Advance.
Ravi
""error code : 56 as "Partner profile not defined "
in testing that Remote Logon it is not connecting but Test Connection is Successful
hi according to me the problem is their
if Remote Logon is not connecting then just
chack ur password client no and other information and then try for remote login without remote login u cant make comunication in between these system
and do anoter thing make same logical system at both side
R/3 and in XI
and logical system and port no have same name.
thanks
reward points if help full
Edited by: diwakar chaube on Mar 21, 2008 12:23 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
go through this one
Idoc processing with Idoc Adapter
The following document describes the configuration required, in order to send Idocs from SAP R/3 system to SAP XI via an Idoc Adapter. The document further describes the key points to be considered while developing the interfaces using an Idoc Adapter in the Integration Builder
Contents:
The following are the configuration tasks to be performed in the sender and receiver systems:
Configuration in the Sender SAP R/3 System.
§ Step 1: Define Logical Systems for Sender and Receiver Systems
§ Step 2: Assign the Sender Logical Systems to the Client
§ Step 3: Create RFC destination to SAP XI
§ Step 4: Maintain Distribution Model and Distribution Views
§ Step 5: Maintain Distribution Model and Distribution Views
§ Step 6: Distribute the Model View
§ Step 7: Send the Idocs to the Receiver
Configuration in SAP XI
§ Step 1: Define Logical Systems for Sender and Receiver Systems
§ Step 2: Assign Receiver Logical System to client
§ Step 3: Create RFC destination to SAP XI
§ Step 4: Port maintenance in IDoc adapter
§ Step 5: Load IDoc Metadata
Configuration Hints for Idoc Processing in Integration builder.
Integration Builder: Design
§ Hint-1: Importing the Software Component Version
§ Hint-2: Importing the Idocs from SAP System
§ Hint-3: Use of Imported IDoc in Graphical Mapping.
§ Hint-4: Use of Imported IDoc in Interface Mapping.
Integration Builder: Configuration
§ Hint-1: Specifying the IDoc interface in the Configuration Wizard
§ Hint-2: Editing the Communication Channel
Configuration steps in SAP R/3
Step 1: Define Logical Systems for Sender and Receiver Systems
Execute Transaction Code SALE
Execute: Define Logical Systems
Select: Continue
Select: Display Change
Select: New Entries
Enter: 020RECV --- RECEVING SYSTEM SAPXI WITH 020 CLIENT (Receiver System)
800SEND --- SENDING SYSTEM MIRSAP WITH 800 CLIENT (Sender System)
Click: Save
Step 2: Assign the Sender Logical Systems to the Client
Execute: Assign Logical Systems
Double click on 800
Specify: Logical System 800SEND
Select Radio Button: Change without automatic recording
Step 3: Create RFC destination to SAP XI
Select Create
Press Save
Select: Test Connection
Select: Remote Login
Step 4: Maintain Distribution Model and Distribution Views
Select Switch between display and edit mode
Select Create Model view
Enter: Short Text and Technical Name
Select Add Message Type
Enter: Sender and Receiver details and Message type
Step 5: Maintain Distribution Model and Distribution Views
Select Environment->Generate Partner Profile
Enter: Partner System
Need to create port & partner profiles
A the Above message is displayed showing that the Partner Profile has been created
Note: It also creates the tRFC Port (A000000018) automatically.
Note the Port Number to specify later in SAP XI in Port maintenance in IDoc adapter (IDX1)
Step 6: Distribute the Model View
Select Continue
A message is displayed about Distribution Model View
Step 7: Send the Idocs to the Receiver
Execute transaction BD12
Enter: Customer ,Output Type and Logical System
WE05
Double Click on DEBMAS
Configuration steps in SAP XI
Login to SAP XI
Step 1: Define Logical Systems for Sender and Receiver Systems
020RECV--- RECV LS WITH 020 CLIENT
800SEND--- SEND LS WITH 800 CLIENT
Step 2: Assign Receiver Logical System to client
Specify logical System
Select Radio Button Changes without automatic recording
Step 3: Create RFC destination to SAP XI
SAVE
Step 4: Port maintenance in IDoc adapter
Execute Tcode IDX2
Select Port Maintenance in IDoc Adapter
Select: Create
Specify : Port No (Created in SAP R/3 automatically)
Click: Save and Back
Step 5: Load IDoc Metadata
Select: Continue
Configuration for Idoc in the Integration builder
Hints that can be used while developing the interfaces using an Idoc Adapter in the Integration Builder are described below. (Description of the sequential steps for the creation of the Interfaces is not given)
Integration Repository Hints:
Hint-1: Importing the Software Component Version
While importing the software component version the radio button Import of RFC and IDoc Interfaces from SAP Systems Permitted should be selected. And also the Connection Data must be specified.
Hint-2: Importing the Idocs from SAP System
To import the Idocs from the SAP R/3 system the Import of SAP Objects is selected by right clicking on the Idocs under Imported Objects in the given Namespace.
The connection data to the SAP R/3 system is to be specified.
Select: Continue
The list of IDocs and RFCs will be displayed.
Select the required IDoc or RFCs to be Imported.
Select: Continue
Select: Finish
The Imported object will appear under the Imported Objects in the Given Namespace.
This imported IDoc can be directly used in the graphical mapping and also in specifying the interface mapping
Hint-3: Use of Imported IDoc in Graphical Mapping.
The Imported IDoc structure can be directly used to specify the source or target messages in the graphical mapping by selecting the Search for repository object option. Thus data types need not be created for the same.
The IDoc from any Software component can be specified to be taken in as the source or target message structure.
Select: The IDoc
Click: Apply.
The IDoc structure will be imported as the message.
Hint-4: Use of Imported IDoc in Interface Mapping.
The Imported IDoc is used to specify the source or target interface.
Integration Directory Hints:
Hint-1: Specifying the IDoc interface in the Configuration Wizard
In Integration Builder: Configuration select: Toolsà Configuration Wizard.
Select: Internal Communication.
The IDoc interface should be selected in the Inbound interface to specify the sender.
Select: Find Button for Interface
Select: All radio button for interface selection
All the Interfaces will be displayed and here select the required IDoc interface.
Select Adapter Type as IDoc
Note:
§ Then Specify the Receiver details for the Outgoing Message.
§ Sender Agreement is not required as the inbound interface is IDoc.
§ Continue with other Config details for the Scenario.
Hint-2: Editing the Communication Channel
Select the communication Channel Created for the IDoc by the Configuration Wizard and here specify the details RFC Destination (800SEND) and Port (A000000018).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In SAP R/3 - i have to define the RFC Destination right
No. U have to create RFC destination in XI.
but when i test that Remote Logon it is not connecting but Test Connection is Successful.
Make sure that the user is a dialog user and it has proper authorization according to the SAP Note 837595
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
" In XI also i have created the RFC destination pointing to SAP R/3 which is working fine by testing through Remote Logon. "
and i have checked the authorizations also .. for the user .. all authorisations are applied (SAP ALL).
1) I had created a RFC destination in SAP R/3 which is pointing to XI.
2) I had created a port in SAP r/3 (WE21) with SAP<SID> ( SID of XI ) and the RFC destination which i mentioned above.
3) I had created a Partner Profile in SAP r/3 (WE20) with the name of Logical system name specified for Standalone Sender system LS mentioned in ID with Type as 'US' (USer).
Even then i am getting the error saying "Partner Profile not defined ".
In point 1, i.e RFC destination .. when i test the Remote Logon, it is not working.. i mean i shud get login to XI system right but it is not working.
Please Help.
Ravi
Troubleshooting IDOC scenario
1. Start with checking the status in sm58 of sender R/3
Follow the steps
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
1) I had created a RFC destination in SAP R/3 which is pointing to XI.
2) I had created a port in SAP r/3 (WE21) with SAP<SID> ( SID of XI ) and the RFC destination which i mentioned above.
3) I had created a Partner Profile in SAP r/3 (WE20) with the name of Logical system name specified for Standalone Sender system LS mentioned in ID with Type as 'US' (USer).
Even then i am getting the error saying "Partner Profile not defined ".
In point 1, i.e RFC destination .. when i test the Remote Logon, it is not working.. i mean i shud get login to XI system right but it is not working.
Please Help.
Ravi
Hi Ravi,
As per your replys i understood that the IDOC reached to SAP R/3 and then in WE02 the idoc status is like 56 and EDI: Receiver partner type in control record is default.
A) In mapping we have to map the field RCVPRT to constant field and provide the value like KU or LS that the type which you are using in SAP R/3s partner profile.
And also make sure that you have checked the checkboxes Take sender from payload and Take receiver from payload along with the Apply control record values from payload checkbox in the IDOC receiver adapter
( make sure that u have mapped all the required control record values in mapping itself)
This should solve your problem
Regards
Seshagiri
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.