Port no. for IDOC..??

hello all..
im makin a scenario of FTP to IDOC and when mentioning the port no. of IDOC..where do i get that from...???
regards..
vishal

hi vishal,
like Sudhir said:
you have to create in transaction IDX1 on your XI
take a look at this:
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm
Regards,
michal
Message was edited by: Michal Krawczyk

Similar Messages

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
Jerome

Hi 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

Sender Port Error in SAP ECC for IDoc

Hi,
I am creating scenario IDOC -> XI -> JDBC with Customer Master IDoc.
After sending it with we19 he said "IDoc sent to SAP system or external program".
In we02 and we05 the IDOC it says "Data passed to port OK".
But in SM58, the IDoc ends in error saying
Transaction IDX1: Port SAPIDST100, client 600, RFC destination contains error.
What I identified that the port SAPIDST100 is the sender port in the IDoc being send. However, for PI we do not need to maintain sender port.
Business Systems:
Sender : SAP ECC
Receiver: SAPPID
Kindly provide your inputs.
Thanks
Rahul

Hi Rahul,
thanks for the information that your scenario is working fine.
But i want to clarify some points:
 - If you send out an IDoc from an ECC system, the senderport is filled with SAP+<system-id> by the SAP IDOC API,
 i.e. if your system id is "ABC", the senderport is "SAPABC"
 => your senderport SAPIDST does not match this template, so i assume you entered the value for the senderport
 manually in the idoc test utility WE19
 - if you send out an idoc, only the receiver port must be created in transaction WE21, it is not necessary to create
 the senderport in WE21, this is not necessary and did not solve your problem
- the idoc was send from ECC (application system with application IDoc metadata) to an XI/PI system (basis system
 without application idoc metadata
 The IDoc adapter on the pi system must analyze the IDoc segments and must know the idoc application metadata,
 but this is not known. So the idoc adapter on PI side looks at the senderport to identify the sender.
 In transaction IDX1 an rfc-destination can be configured to point to the sendersystem with that senderport
 With this rfc-destination the IDoc adapter tries to read the idoc aplication metadata from the ECC system and stores it on PI side.
 If there is no rfc-destination configured in transaction IDX1 on PI side you get the error mentioned in your request.
 I assume that in transaction IDX1 somebody configured the correct RFC-Destination.
I hope this clarification helps you to understand the error and the solution.
Kind regards,
Andreas Dahl

Port details for particular IDOC

Hi All,
I want to find PORT details for a particular IDOC.
Will you please let me know how to find PORT details for a specific IDOC?
Thanks in Advance,
Ramana

Also Kcr, pls check this.
Assumin your instance number is 00
ABAP Port : 8000
JAVA Port: 50000
What is to be undwerstand here is the role of your port here, if you want to acess any Xi component residing on the Java stacj you will use 50000, since SLD and rwd are on the java stack you cannot have different port to acess them.
similary for ABAP Stack 8000 is used.....
inaddition to this you will also have the trfc Port for IDOC communication port,
you can check the abap port by SMICMgotoservices......
kindly reward if found helpful.
cheers,
Hema.

TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and

Hi All
Can anyone pls give me all the TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and BAPI
Thanks
ss

Hi SS..
 SM59-For creating the RFC destination
 we21- For ports
 we20-Partner profiles.
For more inforamtion Please look at the below information:
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 XI 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.
 Thanks and Regards,
 Chandu.
Message was edited by:
 Chandu
null

Business system for idoc reciver communication channel.

hi gurus,
iam doing one file to idoc scenerio.
for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
pls guide me .
warm regards.

Hi
You can use th Buiness system as a receiver for IDOC.
Making sure
1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
2. Use the same LS name for the BS pointng to FIle in the SLD.
Complete the IDOC configuration from XI
1. Create the RFC dest from XI to ECC
2. Create the Trfc port and call this RFC dest created..
3. Use this Trfc port in the IDOC receiver
On ECC:
Make sure the Partner Profiles is created properly.
it is suggested to use always the business systems when you deal with IDOC and Proxies.
Edited by: Nisar Khan on Feb 27, 2008 1:31 PM

What is the internal processing for idocs

Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)

1.Here out bound means sender.Inbound mens --receiver.
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.
SAP ALE & IDOC<<<<
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.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points..

Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
IDoc
- 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.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

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,
Kishore

Hi 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.

Process code for Idoc BANK_CREATE01 and BANK_CHANGE01

hi,
I want to create partner profile for Idoc BANK_CREATE01 and BANK_CHANGE01 standard Idocs.
But in transaction we64 , i am not finding the inbound process code for it.
So di i have to create a process code for it??
If yes , how do i create it and also the function module to be created.
kindly help.
Regards,
Loveena

hi ,
To create a partner profile Tcode WE20.
for your inbound or outbound idocs , just add these idocs in outbound or inbound parameters . For Idoc to File or File to Idoc , it is sufficient.
before creating partner profile you have to create port Tcode WE21
hope this will help
regards
HONEY

Urgent: Error during Import Metadata for IDoc

Hi
We successfully imported the metadata for IDoc from R/3 in Development and Test box and everything worked fine.
Now, when we try to import the metadata for IDoc in Production box it gives me an error" Basic type 'IDoc name' does not exist". I went back to the development box and I try to import some other Idoc metadata and it gives me the above error message.
I checked RFC destination, IDX1 and everything seems to works fine. Any suggestions will be helpful.
Thanks
Mohan

Hi Mohan,
Did you execute IDX2? And if so, please delete existing meta data for port and reimport, if you still receive an error check your R/3 connections (SM59) and port definitions in the receiver IDOC channel (directory)!
Cheers,
Paul

Examples needed for Idoc to file and IDOC to web services

Hi ,
Could any one of you give some examples which take me through step-by-step in building IDOC-TO-FILE and IDOC-TO-WEB SERVICES?
Regards,
XI Developer.

Hi,
For IDOC scenario you need to first do the required configuration:
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Testing purpose u can use the below method:
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters --> For Idoc sender: IDOC -file
IDOC configuration:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
SOAP scenario:
YOu have to first create the WSDL through ID and import that WSDL in to IR external definition.
Refer the below thread and pdf:
How to use SOAP adapter:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
SAP AII - How to consume and expose webservices ?
Thnx
Chirag
reward points if it helps.

Error when Loading Metadata for IDOC Adapter

Everybody,
I know this should be pretty straight forward and that there are a few posts about it. But following the Demo 3.0 guide and the posts I can't seem to load the data into the IDOC Adapter. I did every step in the guide and when I try to execute IDX2 for the source port I previously created I get the error "No RFC Destination is maintained for the port".
Following the guide I have my XI host
ID:ABC
Instance:01
Client:700
Executed IDX1 and got port SAPABC_107 with RFC Dest-ABC_107, which I defined previously with transaction sm59 and the test came back ok.
When I try to execute IDX2 I get the error message...
What am I missing ?????
Thanks!
Diego

Everything was setup before (by following the XI 3.0 Demo guide) here are the steps I did:
1. Setup an RFC R/3 Destination on my client 107 (American Airlines) to client 700 (my XI): ABC_700
2. Setup an RFC R/3 Destination on my client 700 to client 107: ABC_107
3. Setup the IDOC processing port "SAPABC" on client 107 with RFC Destination ABC_700.
4. Define partner type LS for logical system ABCCLNT105 (Airline Lufthansa)
5. Define partner type LS for logical system ABCCLNT700 (XI)
6. Specified the ALE distribution model in client 107.
7. Execute IDX1, I input the SAPABC port created in step 3, input the client number 107 and the RFC destination ABC_107 created in step 2 and save. The result is port SAPABC_107.
AND..!! where the error occurs:
8. Execute IDX2 input port SAPABC_107 and idoc type and get the error message "No RFC Destination is maintain for SAPABC_107"
Any ideas !?
Thanks
D
The client 107 represents the Airline American Airlines and has a R/3 RFC Destination to client 700, my XI. The same way my XI has an R/3 RFC Destination to client 107.

Materials for idoc

Hi am interested to learn about idocs can you provide me some useful links

Hi saranya srithar ,
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r all the t/codes which we will come across in IDocs:
TCODE     TTEXT
BD10     Send Material
BD100     IDoc display object channel view
BD101     Consistency check
BD102     Outbound registry
BD103     Inbound registry
BD104     maintain tbd53
BD105     Maintain Supported Business Objects
BD11     Get Material
BD12     Send customer
BD13     Get customer
BD14     Send vendor
BD15     Open vendor
BD16     Send Cost Center
BD17     Get Cost Center
BD18     Send General Ledger Account
BD19     Get General Ledger Account
BD20     IDoc passed to application
BD21     Select change pointer
BD22     Delete change pointers
BD23     Delete serialization data
BD24     Send Cost Elements
BD25     Send Activity Type
BD26     Get Activity Type
BD27     Send cost center activity prices
BD28     Send obj/cost element control data
BD30     Distribute material object list
BD31     Distribute document object list
BD32     Distribute plant allocations(matBOM)
BD33     Distribute material variants (ALE)
BD34     Distribute order BOM
BD35     Send Business Process Groups
BD36     Send Business Processes
BD37     Send Business Process Price
BD40     Read change pointer for group
BD41     Dispatch IDocs for group
BD42     Check IDocs for group
BD43     Post IDocs for group
BD44     Assign Message Types to Serlz. Group
BD47     Dependencies between methods
BD48     Dependency method - message
BD50     Activate Change Ptrs for Mess. Type
BD51     Maintain function modules (inbound)
BD52     Activ.change pointer per chng.doc.it
BD53     Reduction of Message Types
BD54     Maintaining Logical Systems
BD55     Maintain IDoc Conversion
BD55OLD     Maintain IDoc Conversion
BD56     Maintain IDoc Segment Filters
BD57     Maintain link and serialization ty.
BD58     Convert organizational units
BD59     Allocation object type -> IDoc type
BD60     Additional data for message type
BD61     Activate Change Pointers - Generally
BD62     Define Segment Conversion Rule
BD62OLD     Define Segment Conversion Rule
BD63     Transport ALE Tables of Message Type
BD64     Maintenance of Distribution Model
BD65     Maintain IDoc type required fields
BD66     IDoc type field -> change doc.field
BD67     Maintain methods (inbound)
BD68     Maintain Lists
BD68OLD     Maintain Lists
BD69     Assignment of Message Type to IDoc
BD70     Synchronize Number Ranges
BD71     Define FM for dependent bus. object
BD72     Activate Events
BD73     Reposting of IDocs (ALE)
BD75     Convert IDoc Status
BD77     Distribution of control data
BD78     Monitoring control data distribution
BD79     Maintain IDoc Conversion Rules
BD79OLD     Maintain IDoc Conversion Rules
BD81     Filter objects parameter filtering
BD82     Generate Partner Profiles
BD83     Send IDocs after an ALE error
BD84     Post IDocs after ALE error
BD85     Consistency check for transfer
BD86     Consistency check for sales
BD87     Status Monitor for ALE Messages
BD89     Control data model. - initial screen
BD91     Send Characteristic
BD92     Send Class
BD93     Send Classification
BD95     Specify ALE object types
BD96     filter objects of receiver determin.
BD97     Assign RFC dest. to Logical Systems
BD98     Consistency Check Workflow Connectn.
BD99     Message type dependencies
WE02     Display IDoc
WE05     IDoc Lists
WE06     Active IDoc monitoring
WE07     IDoc statistics
WE08     Status File Interface
WE09     Search for IDocs by Content
WE10     Search for IDoc in Archive
WE11     Delete IDocs
WE12     Test Modified Inbound File
WE14     Test Outbound Processing
WE15     Test Outbound Processing from MC
WE16     Test Inbound File
WE17     Test Status File
WE18     Generate Status File
WE19     Test tool
WE20     Partner Profiles
WE21     Port definition
WE23     Verification of IDoc processing
WE24     DefaultValuesForOutboundParameters
WE27     DefaultValues for Inbound Parameters
WE30     IDoc Type Development
WE31     Development IDoc Segment
WE32     Development IDoc View
WE34     Object for Display of XML IDocs
WE40     IDoc Administration
WE41     Process codes, outbound
WE42     Process codes, inbound
WE43     Funct.module: Status record display
WE44     Partner Types and Checks
WE45     Forward (inbound) (V3, EDILOGADR)
WE46     Error and Status Processing
WE47     Status Maintenance
WE50     System process codes: Texts
WE51     System process codes: Change texts
WE54     FMs for changing file names
WE55     Function Module for Path Names
WE56     IDoc Administration
WE57     Assignment Messages for Appl. Objs
WE58     Status process codes: Texts
WE59     Change status process codes
WE60     Documentation for IDoc types
WE61     Documentation for IDoc record types
WE62     Documentation for segments
WE63     Documentation
WE64     Documentation message types
WE70     Conversion: Basic types
WE71     Conversion: Extensions
WE72     Conversion: IDoc types
WE73     Conversion: Logical messages
WE81     Logical message types
WE82     Assign Messages for IDoc Type
WE84     Assignment of IDoc and appl. fields
WE85     Create Rule Names
WEBU     Printing Labels via Assortment List
WEDI     EDI Basis
WEINBQUEUE     IDoc Inbound Queue
WEKF     Purchase order SAP Retail
WEL0     Forward (inbound) (EDILOGADR)
WEL1     EDI: Interface Invoice for EDILOGADR
WELI     Maintain Status Groups
cheers!
gyanaraj

Configuartion for IDOC

Hi Experts,
If XI is sending an IDOC to R/3. wht are the configurations steps are required at XI and R/3 side. plz list down all the TCODES that are used at both sides?
Thanks
Faisal

Hi Abdhul...
Config for IDOC ...
Do these configurations in R/3 and in XI...
Step for Configuration fo IDOC in R/3
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
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.
Reward points if it is useful..
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Mar 19, 2008 4:13 PM

Port no. for IDOC..??

Similar Messages

Maybe you are looking for