Sld settings for idoc to idoc
hi experts,
for the idoc to idoc scenrio (not making use of BPM)
I have 2 business systems in sld which will be referring to the two r/3 systems.
suppose bus_system1 has logical system name as logsys1 for server1
suppose bus_system2 has logical system name as logsys2 for server2
in we20 for server1 and server2 what logical system name is to be included for the partner profile .(is it the XI server name with receiver port leading to the xi server)?
here there are 3 systems participating in the transfer of data and i am a bit confused . Please help.
Regards,
Shrita.
Hi Shitra,
On the service marketplace there is a nice how-to-guide
(http://servie.sap.com/nw-howtoguides => Exchange Infrastructure => How To Sample IDOC Scenarios within XI 3.0) that explains every step you must go thru.
So you could use this how-to-guide as reference.
PS.: The guide "How to configure the IDOC Adapter" (same place) is also worth reading)
Regards
Rolf
Message was edited by: Rolf C. Weber
Similar Messages
-
ALE settings for MIRO outbound IDOC
PLz tell Output Type, Process Code etc...for MIRO outbound.
for inbound i am using INVOIC01..
Thanks and regardsHi madan,
u can use the transaction NACE to find out the output type of MIRO.
If u know the function module u can able to find the process code easily.
Since function module names are based on message types.
Regards...
Arun. -
Hi!
Can some one recommend a configuration Guide for setting up SLD for SAP EP 7.0?
Thank you very much!
regards
HolgerHi Holger,
Please check the blog on SLD configuration.
Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak
cheers
dev -
ALE Settings For File-IDOC Scenario
Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
BopannaHI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM -
Error : Pre Settings for IDoc inbound processing are missing error
Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299] -
R3 settings for IDOC-IDOC scenario
Hi,
For IDOC to IDOC scenario what are the settings we have to in R3 System other than XI configuration settings.
What are setting for both sender and receiver side.
Thanks,
KishoreHi Kishore,
http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
Refer this material..
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
You can directly create an iDoc using some transaction like...
Use TCODE bd10 - to Send Data
and TCODE bd11 - to Get Data
and you can check the IDoc List using TCODE we02.
As you want step by step procedure.
1. Define Logical System and Assign Logical System
TCODE sale
2. Define RFC
TCODE sm59
3. Define Port
TCODE we21
4. Define Partner Profile
TCODE we20
5. Define Distribution Model
TCODE bd64
6. Send Data
TCODE bd10
7. Get Data
TCODE bd11
8. IDoc List
TCODE we02
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
u can also check all these links related to idocs
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Reward points if this helps
Regards
Pragathi. -
Port Settings for IDoc Adapter
Hi All,
Our scenario is like this ERP -> XI -> File. ERP sends IDoc to XI. I have a couple of questions.
1. In the control part of an IDoc, there's a sender partner number and sender port. What are they used for? As I understand, the partner and port represent the destination of the IDoc instead of the source. Why is there sender port and partner?
2. We need to maintain port using IDX1. Should I set the name of the port to be the same as the sender port of the IDoc?
3. I didn't configure the scenario and the IDoc sender adapter. If the ERP system sends IDoc to XI, can I find it in t-code IDX5?
Best Regards
JeromeHi Jerome,
1. Sender Partner and Port : The control record should have sender port and partner number. This will be used by the receiver system (i.e., XI system). Because, receiver system should know from which system this IDoc is coming using Sender Partner number. This partner number should be same as Logical system name in Sender Business system which is configured in SLD.
The sender port should be SAP<Sys-id of sender system>
and sender partner number should be <sys-id of sender>CLNT<client number of sender>
2. The port created in IDX1 will be used for importing IDoc's metadata in XI system from R/3. IDoc metadata is needed by IDoc adapter to convert incoming IDoc to IDoc-XML format.
It is mandatory to have same name for Port in IDX1 and sender port of the IDoc's control record.
3. I think the IDoc wont be listed in IDX5 if scenario and IDoc adapter are not configured. IDX5 displays inbound and outbound IDocs in the IDoc adapter.
Regards,
Uma -
Hi,
For configuration of IDOC adapter
1) we need to create RFC Desination both XI System and R3 System.For port creation if v given same port name in both XI system and R3 system it will work or not ?
2) On Receiver SAP system, we need to configure the logical system normally for XI system, were v can find logical system of XI System.
3) Can RFC Destination b same on both systems( R3 system, XI System)
Regards,
PraveenHi
The following configurations are needed for Idoc scenarios
1) ECC Configuration : a) Create RFC connections from ECC to XI in SM59. rfc connection name should be target XI logical system name . BD54 or SALE are the tcodes for checking the logical system for respective client.
b) Create port in we21 & provide the above RFC destination.
c) Now Create Partner Profile in we20 ...partner profile name should be target logical system name.
assign the outbound parameters with receiver port created in we21.
2) XI Configuration : a) Create a RFC connection for XI to ECC ...rfc name should be target logical system name(ecc).
b) Create port in IDX1...it should be SAPXXX..where XXX is the ecc system id.
c) Import the idoc metadata in IDX2.
For Outbound idocs generate the model view in BD64.
Regards
Abhijit -
Hi all
I am doing a scenario IDOC - Xi - IDOC where CRM sends an IDOC to R/3 via PI.
I have configured everything in OCC (CRM system), PI and BSC (R/3 system) but when I test it with the transaction WE19 in OCC nothing happens in PI or BSC.
All i can see if a message in SM58 transaction in OCC.
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - XI.
Status Text - No service for system SAPOCC, client *** in Integration Directory.
Could anyone tell me what is the problem.
Your help will be very much appreciated
Regards
NainaError message: No service for system SAPCRD client 201 in the integration directory
Cause: There is no service without party in PI server that represents OCC server with client details.
Solution:
We send IDocs from system OCC to PI. In the control record (Segment EDIDC40) of the IDoc, the SNDPOR (SenderPort) field contains the value "SAPCRD". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service)
In System Landscape Directory (SLD) create a technical system for OCC system and assign a client for the same. Don't forget to assign an "ALE logical system" to the technical system created. Create a business system for this technical system. Then Business System can be imported under service without party/update the details existing in PI.
Edited by: Rodrigo Alejandro Pertierra on Jun 23, 2010 10:28 AM -
How to set up the communication channel for third party idoc
Hello,
I am trying to send an idoc from an sap 4.6c system to an third party system. The third party system is supporting idcos with trfc.
My problem is to set up the communication channel in the integration builder (configuration) for the third party system. The idoc is waitung in XI to transport.
My settings are:
adapter type: idoc
transport protocol: idoc
message protocol: idoc
adapter engine: integration engine
rfc destination: xyz (is working fine)
interface version: sap release 4.0 or higher
port: ??
sap release 46c
My problem is the port. should i set up a port in idx1? But the third party is not an sap system and so i dont have a client.
On the xi i have defined a port in transaction we21 (transactional rfc) for the third party with my rfc destination xyz. But if i enter that port in communication channel i got error messages.
Thanks for any help.Hi Christian,
yes, you have to mainztain that port in idx1.
First ypi load the rfc-metadata from an SAP referenzsystem and afterwards copy this metadata to the third party port.
For further details check the onlinedocumentation "IDoc Processing with the IDoc Adapter" XI -> runtime -> adapter
Good luck,
Holger -
How to block the status mail for an inbound Idoc to a specific user
Hi,
I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
Thanks,
SantoshHi,
I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
Thanks,
Santosh -
Issue with the configuration of http xml port for sending the idoc
Hello,
I am planning to send multiple idocs in a single file using http xml port.
Presently I am trying to send a single idoc, but am having the issue.
I am trying to create a RFC for HTTP XML port of type H i.e. HTTP Connection to ABAP System
In the how to guide for - How Tou2026 Send Multiple IDocs Within One XI Message
( https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b )
the following parameters are defined for the path prefix -
RFC destination of type H (HTTP Connection to R/3 System).
Specify the path prefix as follows:
/sap/xi/adapter_plain/
?namespace=< your namespace>
&interface=<IDoc_Type>
&service=<Sender System>
&qos=EO (or EOIO).
I am trying to use the following prefix -
/sap/xi/adapter_plain/
?namespace=urn:sap-com:document:sap:idoc:messages ( this is the standard namespace of SAP for all the idocs)
&interface=DEBMAS05 (Idoc type )
&service=SNDLS100 ( ECC system name )
&qos=EOIO
On testing the RFC connection, I am getting the error of page not found.
Can anyone please give me pointers for the issue.
Regards,
MayankThanks Barry!!!
Now I am getting a different message.
In RFC...it is giving me the following message ->
Status HTTP Response 204
Status Text Body is empty
In case of Idoc, the status is till 02...
the error description for the idoc is --
"When transferring the IDoc by HTTP, the return code with the message '500<SAP:Error><SAP:Category>XIServer</SAP:Category><S' has occurred.
The target address was: http://emgeccsnd1:8001/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interf
Check whether the IDoc can be sent again.
It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards"
I am still not able to resolve the issue.
Regards,
Mayank -
Partner Profile for file to IDOC scenario
Hi experts,
I am doing file to Idoc scenario. I did the ALE configuration steps between XI and r/3. For sender (ThirdParty) system, I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........
Thanks
ManojHi,
>>I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........
in most cases you will only use one logical system in WE20
this will be XI's logical system - and you can route all the traffic
via this logicail system - this is the most popular case
for more about IDOCs and XI have a look at my book:
Mastering IDoc Business Scenarios with the SAP XI
http://www.sap-press.com/product.cfm?account=&product=H1935
Regards,
Michal Krawczyk
http://mypigenie.com - XI/PI FAQ -
Desing requriment for processing the IDOC in real time
hi Gurus,
we have a requirement to design for processing the IDOC in real time i.e.all the IDOC must be store and process for give time line with out using BPPM tool.we have suggested to use cache storage or storing the files in file adapter.
please suggested good process with out compromising the Performance of PI.
regards
shankarhi Raj,
Please find the example below for your reference
let say
System A-->PI--
>system B
system A sends multiple files based on time(daily or weekly) and real time( as an when the record created) to systerm B (CRM) in the form of IDOC Via. PI
we needs to club the real time files and send it to system B.How best we can do without using BPM.
regards
shankar -
Sender port is not picking in PI for idoc to idoc scenario
Hi Guru's,
i am doing idoc to idoc scenario passing through sap pi ,while executing this idoc from client1 is successfully coming to PI, but while going from PI to client2 , i am getting error 51 (company code is defined for LS(logical system) for 1000 (vendor),i checked the configurations for sender idoc from pi ,it is taking a port value which is not present neither in xi nor in r/3 it is MDM interface port value i tried makking the port value constant in PI mapping ,but still same error is comming.
idoc created with partner type LI in source system.i am posting it as LS in receiver system.
Please help me in resolving this error.
Regards,
reddyHi,
The error mentioned by you is not related to the port..but its related to the Application ...
IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
Check with the functional consultant for the error you have received..
HTH
Rajesh
Maybe you are looking for
-
Using union query to return a value to Oracle Type object in a view
Hi All, I am using type objects inside a view to fetch data. For a particular type, in select statement when i use a "union all", it is throwing oracle error ora-03001 unimplemented feature. But it is working fine when it contains only select stateme
-
I have an error message, decompressing audio or video file, how do I fix it?
I have an error message, decompressing audio or video file, how do I fix it?
-
IPod Touch TV show list backwards...
I have episodes of 2 different TV shows on my iPod Touch, and while the show names are in alphabetical order, there is an issue when I go into the episode list of the shows. All of the episodes are listed in reverse order... Example: I have every epi
-
Regaring code ,its urgent
hi, i had amde dis code for displaying the changes made on material in purticular month,70% report is working fine but problem is dat when i want to see the deatils of changes made to it ,it is not displaying all records,i.e. if dere are 5 changes ma
-
Slide Presentation in ScrollPane
I load a Flash Professional Slide Presentation into a scrollPane. Is it possible to figure out which slide is currently being presented from the scrollPane and/or Parent of the scrollPane? If so, how? Thanks.