What is IDoc in SAP???

Hii epxerts
Can anybody explain me what is Idocu ..??
What its significance , its functionalities, its benefits..etc???
Explain me in very short fiorm .
If explantion with example in MM is very helpfull...
So some experts can ....

Most simple thing in SAP is IDOC
suppose your client was earlier using some non sap system and now they have started working on SAP system.
but client say is that they will still be creating the purchase order in there legacy system and it should come to sap system and get created there automatically.
now to map this requirement we would need this flow
legacy system > SAP XI system> SAP ECC R/3.
So intially PO is created in legacy system and then a file comes to XI system carrying the PO information and then XI system sends IDOC to R/3 system
see IDOC is a group of fields
IDOC carries number of segment which further contains the exact data in fields
for example
ORDERS is the IDOC for PO
ORDERS has the segment E1PO which will carry the fields
EBELN
ebelP

Similar Messages

How to find at what time Idoc has gone out of SAP

Hi Gurus,
Could anybody let me know , how to check at what time Idoc has gone out of SAP in case of outbound Idoc.
I am not talking about Idoc creation date which we can see in control records in WE05.
-B S B

you have to see the status of the idoc ,if idoc status is green color ( Succesfully completed ) then use
EDIDC-UPDTIM ( This should be last Time)
Date is EDIDC-UPDDAT.
See the other table EDIDS to check the idoc status.
Thanks
Seshu

How to Trigger an IDOC from SAP R/3 to two systems at a time

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELVRY03 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once. We need to write a logic to route the same to two different systems
Can any one tell me how can we do that ?
Regards
Ram.

Hello Ram,
Do you have connectivity between your production & XIQ?
What does "connectivity" mean?
1. RFC destination is maintained.
2. Port defined for the RFC destination.
If no, create these. (Search in SDN for details).
If yes, proceed:
1. Define the logical system for XIQ.(BD54)
2. Define the same as your partner profile. (WE20). Add the message type SYNCH with the port for XIQ.(This is imp)
3. Create a distribution model view with sender as "your production" & receiver as XIQ.
3.1. Add the messages which you want to distribute.
3.2 Generate Partner profiles.
No coding is reqd. for this.
BR,
Suhas

Error while pushing idocs from SAP to XI

Dear All,
For doing ALE configurations for pushing IDOC's from SAP to XI, I am following the following blog posted on SDN:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I am able to create the model view distribution successfully but when I am clicking on EDIT --> MODEL VIEW --> DISTRIBUTE (which is one of the steps mentioned in the blog), I am getting an error tht
<b>Target system XIDEV Communication error occurred
User is locked. Please notify the person responsible</b>
please tell me what is the error ie which user is locked and how should i proceed now.
Waiting for your reply.
Warm regards,
N.Jain

hi krishnamoorthy,
i hve created one RFC in my R/3 system which is pointing to Xi-DEV. So, in the RFC I have used my XI user id & password for loging and the RFC is wrking fine when I am testing tht. I have used my id "XISUPER" in that RFC and it is not locked in XI-DEV. I have not used user id "XI_APPLUSER" anywhere.
Please suggest.
Warm Regards,
N.Jain

How to Trigger an IDOC from SAP R/3 to two XI systems

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELCERY01 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once.
Regards
Ram.

Hi Ravi,
Thank you very much for your answer.
As I am not completely aware of R/3 side,I am getting little problem in understanding your answer.
Could you please explain the same in some what beter way.. Thank you ..

What setting need in SAP R/3 if i want to send only changed records to XI

Hi All
     I had problem while sending Idoc from SAP R/3 to XI
     Thing is i want to send only the changed records in Idoc not all so what
     settings i need to in SAP R/3 ?
     Can any one explain me how to do this...
Adv thanks and Points
Prasad K

Hello Prasad,
Many cases you will find that there are standard message types for change idocs.
For Instance let us take Purchase order:
--For Order create ORDERS is the message type.
--For Order Change ORDCHG is the message type.
You will just need to maintain both in the outbound parameter in the Partner Profile in we20.
From XI side this means there are separate interfaces -- ORDERS.ORDERS02 & ORDCHG.ORDERS02 for instance. You just need to treat this as different interfaces and Configure. One last thing . If the basic type is same eg. ORDERS02 then you can use the same message mapping program for both Change and create if you want -- although the interface mapping will be different.
Make sure to maintain metadata in IDX2 in XI.
Cheers,
Himadri

Problem when pushing IDOC from SAP to XI

Hi,
I am trying to push an IDOC from SAP R/3 system to XI. When I processed the IDOC using test tool(WE19), it's showing message that IDOC sent succesfully to R/3 or External system. But in SM58 Transaction it gave error message that in Trabsaction IDX1: some RFC connection error. Then I opened the Transaction IDX1 on XI server, in that IDOC Adapter configuration I gave RFC destination, Logical system name of R/3 and saved it. Now When I tried again to push IDOC from R/3 to it's not giving any error message(in SM58), but I am not able to see any thing in SXMB_MONI. Can anybody guess what's happening? And also I am using fresh newly installed XI server. DO I need to configure something else? All RFC connections are well defined and working fine.

Hi,
It is not required to create Sender Agreement for the Idoc to XI scenario. Because it is implicitly exists.
Can u check Receiver Determination created in the XI once again. And also check for RFC destinations created in the R/3.
Hope it helps ..
-Moorthy

Legacy flat file to IDOC into SAP

after been given the task of converting a flat file structure to SAP idocs my research as lead me into the daunting world of CAPS. Basically I would like to know if using CAPS is the best choice for me
and if so what is actually involved to make this happen?
Thanks
Michael

hi michael,
from my point of view "the right thing to do" would be:
consider if this is the only task for you that is somehow EAI ish...
if it is do not care about technology... just do it with a very simple program
if you have to evolve choose a tool that is capeable of your systems you own: e.g. SAP AS400 .......
in caps you would typically do this:
setup CAPS
write an ftp2queue component
write a converter (custom otd + convertion logic + IDOC OTD)
write a idoc 2 sap component via TRFC
run ;-)
a good starting point would be:
http://developers.sun.com/docs/javacaps/index.jsp
or
http://wikis.sun.com/display/JavaCAPS/Grok+Java+CAPS
or try to convince your boss that sun will implement it for you if you have the money to do so.
we did that when introducing CAPS (we got it for free besides the CAPS licences of course ;-)).
regards chris

What is IDOC and ALE?

Hi anybody,
         Please tell me what is IDOC and ALE? What pupose using IDOC and ALE?
          Give me Example sample code of using IDOC and ALE.
Thanks
S.Muthu.

Dear,
Here is some facts which will be helpful to clear yr concepts for ALE/IDOCs.
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.
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.
*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.
ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
Distributed Process:
A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
Need for Distributed Process:
Business in Different Geographical Locations.
Non availability of dedicated network.
Cultural and language differences in Geographical locations.
Running of Mission-critical Applications (Like Maintenance downtime etc.).
Separate up gradation of Modules.
Distributed SAP SYSTEM CHALLENGES
A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
Receiving systems that can handle their own problems and not tie up the sending system.
Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
A sound technology and methodology that can be used in all distribution scenarios.
SAP Distributed environment:
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the
application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
Basic integrity check: A basic integrity check is performed on the control record.
Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function modules output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application
How to create idoc?
*WE30 - you can create a IDOC type
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
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
This report creates IDocs from the change pointers for the specified message type. It then sends them to the receiving system and flags the change pointers as processed in respect of the specified message type.
The receiving systems for the specified message type are determined from the customer distribution model.
Output:-The report outputs information about the number of master IDocs and communication IDocs created.
RSEOUT00 Process all selected IDocs (EDI) Report for generation of files for EDI outbound processing.The report processes the IDocs available in the system with the status 'to be processed'. The IDocs are selected according to the selection options and parameters specified.
It is important that you make sure that only test messages or productive messages are selected.
The IDocs are processed in various files for various output modes and for various ports. The names of the files are created according to the naming definition for the outbound file. This definition is determined in the port definition.
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.
Hope This will be helpful,
Best Regards ,
P Singh

Sending IDOC from SAP ECC to SAP MII

Hello,
Issue while configuring.
I have configured the RFC Destination in the Netweaver message listener and when i check the connection in SM59 I got error as timeout during allocate of registered program and I have attached the screenshot of the error page.
I would request a reply asap.
Thanks,
Praveen

Hi Praveen,
First, I would suggest that you identify what version, and SP, of MII and ECC. Also the NW version and SP if applicable.
Second, use this custom Google search and terms MII, IDoc Listener, and perhaps SM59. There are many discussions on IDoc Listeners going back a number of years. Many of the issues with IDoc Listeners have not changed in most of that time, so look at the older ones as well. I presume that you found and are using my How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0) to set up your Listener? If not, you should review your configuration and setup procedure against it.
I have not looked at MII 14.0 or 15.0, but understand that the configuration of Listeners really has not changed since MII 12.1. So the document is still applicable.
Third, roughly 90% of the problems experienced with IDoc Listeners involve multiple uses of the self registering ProgID. Deleting it in one place, generally does not work. Use it in one place only. Create a new ProgID for each separate Listener (either type) on each separate MII instance for each ECC instance. Save yourself a lot of headaches. Never, ever reuse ProgIDs!!!
Fourth, most of the other issues involve a PI/XI system in the middle. Those are a bit more complicated since they rely on getting the connection configuration set up properly in PI. Since I am not that familiar with PI systems (most times it is not involved with the Listeners), I generally have to get other experts involved. Sometimes a CSS ticket is required.
Regards, Mike
SAP P&I Technology RIG

"An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

Hi all,
While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
Only a particular Idoc type is having this issue.
Below are the checks done before posting this query:
1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
2. Reloaded the meta data in PI for the particular Idoc type in issue.
3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
5. Restarted the inboundRA service in PI AEX.
Is there anything still missing. What could be root cause of this issue.
If anyone has encountered it before, pleases share the resolution.
Thank you
Younus

Hi Amit,
Thanks for the reply. Log viewer doesn't provide much help on the error.
The error desc says
"JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
regards,
Younus

** Not able to import IDoc from SAP ECC system

Hi Friends,
I am not able to import the IDoc from SAP ECC system in IR. I have checked that, hostname, client, server no. everthing is correct. I checked in SLD also. Host Name is correct.
While import (after giving the user name and password), I am getting the following error.
Problems to reach R3 System
What could be the probelm ?
Kindly help me friends.
Thanking you.
Kind regards,
Jegathees P.

Hi,
Just counter check following step
1. Go to SWCV definition tab select radio button for Import of RFC....
2. In Connection Data for Import from SAP System maintain correct System and correct Client.
3. Make sure you maitain ECC system in Central SLD.
4. In Import Screen check at the top of the screen have SAP System, is that system from where you want to import the IDOC.
With Regards
Sunil

Thousands of IDOC to SAP

Hi.
My BPM must send thousands of IDOCS to SAP.
I've made a test sending 400 vendor IDOC to SAP and spent more than 6 minutes on it.
It's a long time?
In the future, i will have to send more than 20.000 FI IDOCS. What's the fastest way to send them?
Thanks.

Hi Inigo,
Are you using IDoc packaging or sending idocs one by one ?
If you package and send a IDocs then the performance will be better.
Check if this helps..
Re: Mapping JDBC -> IDOC
Anand
Message was edited by: Anand Torgal

Webmehods unable to lookup IDOC in SAP

Hi
We have some IDOCS in SAP.
Webmethods is talking to SAP and looking up these IDOCS.
However it is unable to lookup all the IDOCS.
We are using ECC6 system.
On further observation we've observed that IDOCS with release 4.6 are lookedup by Webmethods but IDOCS with release 700 ae not looked up.
What is the reason for this?
This is the error message that Webmethods gets
[SAP.108.9351] WmSAP Adapter: Could not find IDoc "ORDERS05.ZGSLSITE_CO(700)
Rergards
Dexter

HI,
ORDERS05.ZGSLSITE_CO looks like a custom Messagetype.
Maybe you have the wrong Messagetype or reimport the Metadato for ORDERS05.ZGSLSITE_CO.
Regards,
Gordon

Massive import of IDOCS in SAP

Hello, good morning.
I've an application that is generating a lot of files that I need to import in SAP.
- What's the better way to import in SAP ?? IDOC, BAPI, etc...
- I was thinking in IDOCS....What's the way to import massively all the files of a folder ?
- Can I import and transform in IDOC these files when they're generated in the source system and traspassed to the SAP folder ??
What steps must I follow to do this ??
Thanks in advance
Albert

Hello Frederic and Gurprit,
yes, I need to make some validations in the input data.
Because of this I think I need to convert the flat files (txt) into IDOC.
Is that correct ??
My idea is to "join" all the files in the source folder into an only one (this by an UNIX script) and after this via the command "startrfc" (scheduled, of course) create the IDOCS into SAP.
I don't know yet if the schedule is better with a UNIX cron or with a SAP Job.
What's is your opinion ?
Regards,
Albert

What is IDoc in SAP???

Similar Messages

Maybe you are looking for