Why no MI for IDOC?

Hi,
Why message interface is not needed for an IDOC? I just know that IDOC acts as DT , MT and MI. Can anyone give a brief idea what happens internally to XI when it comes to IDOC?
Thanks,
Vishal.

Hi Vishal,
Why message interface is not needed for an IDOC?I just know that IDOC acts as DT , MT and MI. Can anyone give a brief idea what happens internally to XI when it comes to IDOC?
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/frameset.htm
The messages exchanged between systems are of various message types. The message type depends on the data contained and the process involved. It determines the technical structure of the message, the IDoc type. For example, the FIDCMT message type is used for journal messages.
The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
An IDoc type consists of the following components:
·       a control record
This is identical for each IDoc type.
·       several data records
One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.
·       several status records
These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.
Regards,

Similar Messages

Why thet gave option for idoc in bw

hi friends,
why they gave option idoc (data transfer method ) in bw. what is the use. we have psa, again why we need idoc.
Thanking u
suneel.

IDOC (Intermediate Document)
IDOC is SAPs standard format for electronic data interchange between systems. IDOCs can be used in the following business scenarios:
- Application link enabling (ALE). Communication between logical systems; logical systems can be SAP R/3, R/2, or non-SAP systems.
- Electronic data interchange (EDI). Communication between an SAP R/3 or R/2 system and a non-SAP system
In SAP BW, an IDOC is a data container for data exchange between SAP systems or between SAP systems and external systems based on the EDI interface.
SAP RESTRICTIONS
IDOCs support limited file size (1,000 bytes).
Data cannot be loaded to PSA using IDOCs (ALE).
OPTIMIZATION
Queries and Data Staging
You should leverage PSA (and ODS) to store detailed data rather than in the InfoCube as it may contribute considerably to the increase in the query (keep detailed data out of the InfoCube) and system performance (due to higher throughput during data load since PSA uses TRFC rather than IDOC).
Regards
Naga

Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

Hi,
I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
Thanks in advance.
Best Regards.
Alex

Hi Aamir,
The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
Thanks anyway.
Alex

Batch job for IDOC processing in 64 status

Hi experts ,
i want to know the name of Batch job for IDOC processing in 64 status.
I have configured the partner profiles as 'process immediatly'.
So with this configuration whenever an idoc comes in production it gets processed immediatly and automatically.
i want to know how they are getting processed automatically.
is there any job which looks for these idocs(in 64 status and process immediatly flag) and process it.
What is the trigger for thiese idocs processing???
Please guide me
thanks in advance
Anit gautam

Hi Thanks for ur reply.
=====Upon arrival, "process immediately" should fire that process =====
how it is getting fire?
means is there any batch job running which looks for idoc in 64 status or is there any event which get triggered when an idoc
comes in 64 status.
why we use OYEB transaction???
Regards

We 19 rest tool for idoc processing

hi to all abap gurus
i heard that we19 is test tool for idoc proceesing and it is also also used for idoc deletion .
may i know what is idoc testing why it is required . can u pls explain n in detail ?
and so many options are there in we19 tcode like inbound function module .
and tell me how to create idoc dynamically and send to the other system by using we 19 tool
thanksssss in adavance

Intermediate Document
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. IDoc is not a process.
-         IDocs are stored in the database.
-         In the SAP system, IDocs are stored in database tables.
-         IDocs are independent of the sending and receiving systems.
-         IDocs are independent of the direction of data exchange.
Creation of IDOCs
?         Transaction code: WE 30
Defining Segment:
Creating Segment : Tcode - WE31
Creating Message Type : Tcode - we81
Assigning Message type to Idoc type: Tcode - we82
Process
The two processes for IDoc are Outbound Process and Inbound Process.
Outbound Process
When the data is sent out from the system, the process is called Outbound Process and the IDoc is known as Outbound IDoc.
Inbound Process
When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.
Outbound Process (Sending System) Steps :
1) Goto Tcode SALE:
Click on Sending & Receiving Systems à Select Logical Systems
Here Define the Logical Systems à Click on Execute Button
Go for New Entries
1)       System Name : LOG1
Description: Sending System
2)       System Name : LOG2
Description: Receiving System
Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.
Assigning Client to the Logical System:
Select Assign Client to Logical Systems -à Execute
Ø      100 à Double click on this and give the following information
           Client                   : Sending System
           City                      : Chennai
           Logical System    : LOG1
            Currency                   :
            Client role                  :
Ø      250 à Double click on this and give the following information
Client                     : Receiving System
City                        :
Logical System    : LOG2
Save this Data.
Step 2) For RFC Creation:
-         Goto Tcode SM59 à Select R/3 Connects
Click on create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
Give the information for required fields:
RFC Destination    : LOG2
Connection type     : 3
Target Host              : sappdc.wipro.com
System No              : 00
Client                       : 210
User                            : Login user name
Password                   :
Save this & Test it and Remote Login
Step 3) Goto Tcode BD64: - Click on the change button
Click on the create model view
Short Text: model view
Technical Name: LMOD
Save this & press ok
Select just created model view
Name: "LMOD"
Goto add message type
Model Name : LMOD
Sender           : LOG1
Receiver          : LOG2
Message type: ZAZHARMESS
Save and press Enter.
4) Goto Tcode BD82:
Give Model View   : LMOD
Partner system      : LOG2
Execute this by pressing F8
It will gives you sending system port No: A00000000089 (Like)
5) Goto Tcode BD64:
Select the model view
Goto à Edit à model view à Distribute
Press ok & Press Enter.
Run your Zprogram
REPORT ZIDOC1                             .
DATA: Begin of imara occurs 0,
matnr like mara-matnr,
mtart like mara-mtart,
end of imara.
DATA: wamas_con LIKE edidc,
imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,
icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.
PARAMETERS: e_matnr LIKE mara-matnr,
e_msgtyp LIKE edidc-mestyp,
e_rcvprn LIKE edidc-rcvprn.
retrive app. data from DB
SELECT matnr mtart FROM mara INTO TABLE imara WHERE
matnr = e_matnr.
*Master idoc control record
wamas_con-rcvprt = 'LS'.
wamas_con-rcvprn = e_rcvprn.
wamas_con-idoctp = 'ZAZHARIDOC'.
wamas_con-mestyp = e_msgtyp.
master idoc data records
LOOP AT imara.
imas_data-segnam = 'ZAZHARSEG'.
move imara to imas_data-sdata .
APPEND imas_data.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = wamas_con
TABLES
communication_idoc_control = icom_con
master_idoc_data = imas_data
COMMIT WORK.
6) Verifying Transfer of IDOCs Tcode - we05
ALE/IDOC Status Codes (outbound):
01    à IDoc Added
30 à IDoc ready for dispatch
29 à Error in ALE service Layer
12 à Dispatch ok
      03 à Data passed to port ok.
Inbound Process (Receiving System) Steps:
Do the same step as you did in sending system
ü      Creating IDoc
ü      Defining the Segment
ü      Creating Message Type
ü      Assigning the Message Type
ü      Defining the Logical System
ü      Assigning the Logical System
ü      Creating the Distribution Model
Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
Creating Inbound process code - we42
Verifying Idoc List Tcode - we05
ALE/IDOC Status Codes (Inbound):
50 à IDoc Added
51 à Application Document not posted
64 à IDoc ready to be transferred to application
62 à IDoc passed to application
53 à Application Document posted
Useful transactions for IDocs
BD87 : Status Monitor for ALE Messages
SALE : Display ALE Customizing
WE02 : Display IDoc
WE05 : IDoc Lists
WE09 : Search for IDoc in Database
WE19 : Test tool
Check this link,
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/step%2bby%2bstep%2bprocedure%2bfor%2bcreation%2bof%2bidoc

WHY WE GO FOR SESSION RATHER THAN LSMW ?

WHY WE GO FOR SESSION RATHER THAN LSMW , AND I WANT TO KNWO THE DIFFERANCES BETWEEN THEM AND IN WICH CONDITIONS SESSION AND LSMW ARE MOST SUTED? THANKING U

hi,
In BDC ,we can run session as per our need, you can run in foreground ,background or even you can run on periodic wise ,where as in LSMW
you cant run as your wish .
BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/backgrou nd processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Reward points if this helps you.
Siva

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

Why no support for iTunes in tiger?

Why no support for iTunes running on Tiger?
WE NEED THIS Apple!

iTunes is completely supported on Mac OS X 10.4. I used, and supported, iTunes on 10.4 for years. If it won't start on your system, something is corrupted. Let us know what version of iTunes you are trying to run and exactly what happens, including error messages if any, and someone can probably provide suggestions. As it is, you're just asking people to guess.
Regards.

Why we go for SAP ?what are the benifits to implement SAP inanyorganizat?

Hi,
Why we go for SAP ?what are the benifits to implement SAP in any organization?
Early reply is highely appruciable.
Regards,
Chow.

Hi
check following link for ur doubts
http://www.sap.com/solutions/business-suite/erp/businessbenefits/index.epx
Some key points to switch to SAP is like
Focus on Business Processes
Elimination of Redundant Data (Common & Consistent Data)
Easier Corporate Consolidation
Better Managerial Control
Elimination of Interfaces
Faster reaction to changing structures
Organization/Customers/Competitors
Integration is the Key
Integration of all business modules
Major reduction in time required for accounts finalization
Easier Corporate Consolidation
Cost control Batch wise / Cost centre wise
Centralised Inventory planning and control
Reduction in Inventory carrying Costs
Best Business practices across the organisation
Elimination of redundant data
Better Managerial control
Data Integrity
Enhanced Organisational flexibility
Improvement in Personal productivity
High Data availability
Improved Order cycle time / accuracy / cost
hope this is what ur looking for
If not pls revert
Vishal...

What is SLD .. why we go for SLD.. what is the the uses of thisSLD

Hi friends,
can you give me the brief idea about SLD... first of all WHAT is SLD.. WHY we go for SLD.. and what are the Uses of this SLD..
plz calrrify my doubt..
Thanks
Babu

there is an excellent how to guide about handling the SLD for SAP XI - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
do read thru the same, and in case you need more inputs let us know.

MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER

Hi Experts,
How the MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER?
Scenario : when 2nd system create the invoice,it will create a po in the 1st system.
51 error msg we are getting material does not exists.but the material is available in the receiving plant.
Please suggest

If you say the material master is available in the 1st system (where you create the order), then the material number in the IDOC may not match with the material number in your database.
leading zeros. material number stored as alphanumeris instead of numeric.

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

EOIO for IDOCs to XI

Hi,
My scenario is IDOC ---> xi ---> File.
Need to implement EOIO(serialization) for IDOCs coming from ECC.
Checked "Queue Processing" and assigned rule "FIRST_16_OF_MESTYP".
When I send the IDOC using WE19, I get message "IDocs are stored in the queue".
But, IDOCs are not coming to XI. Please help.
Versions: ECC 6.0 & PI 7.0 SPS 13.
Also, do I need to maintain an entry in IDXQUEUE table?

Hi
use similar thread
How to implement IDOC Serialization(EOIO) using IDOC Adapter
Re: Posting idocs in sequence in SAP from file (without BPM)

SA PI 7.1 EHP1 - Support for IDOC Adapter using AAE

Hi,
Can anyone confirm if the SAP PI 7.1 EHP1 supports the IDOC adapter in the AAE ?
Cheers
Colin.

Hi Colin,
I am workinngt on EHP1 PI7.1,but no support for IDoc Adapter in the AAE.
The new features added for IDoc adapter is IDoc packging and new conversion module added .
we have to wait till next release,but not sure...
Regards,
raj

Why no MI for IDOC?

Similar Messages

Maybe you are looking for