Difference between IDOC segments starting with E1 and E2

Hi all,
What is the difference between IDOC segments starting with E1 and E2
Thanks

Hi Kajol,
A segment in SAP system is technically implemented as three physically separate pieces.
1. Segment type u2013 the version-independent name of the segment. Standard SAP names begin with E1.
2. Segment definition u2013 contains the fields which represent the data. Its maximum size is 1000 bytes. Standard SAP definitions start with E2 with the last 3 characters implying the version of the segment.
3. Segment documentation u2013 represents the data dictionary documentation for each field in the segment definition. It begins with E3 for SAP provided segments.
For example, E1EDP01 will be your segment type and E2EDP01003 will be your segment definition with 003 indicating its version.By default, the segment type points to the latest segment definition.
Kindly do reward points if you find this as useful.
Regards,
Aswin

Similar Messages

  • What is the difference between READ TABLE ITAB WITH KEY  and  TABLE KEY

    Hi Experts,
    what is the difference between
    READ TABLE <ITAB> WITH KEY <K1> = <C1>
                                                    <Kn> = <Cn> .
    and 
    READ TABLE <ITAB> WITH TABLE KEY <K1> = <C1>
                                                              <Kn> = <Cn> .
    Thanks
    Akash.

    Hi akashdeep,
    Nice question. I also tried to find out, but no much success. My opinion is that for practical purposes there is no difference.
    It may have difference in case of searching, especially sorted tables. (binary search or normal linear search).
    Case1: If our table is sorted table with defined key fields, and we give WITH TABLE KEY, then faster binary search is used.
    Case2 : If our table is sorted table with defined key fields, and we give WITH  KEY, (and no field contained in the keys), then normal linear search is used.
    regards,
    amit m.

  • Difference between IDOC Bundling and IDOC Packaging

    Hi,
    Can anybody please explain the difference between IDOC bundling and IDOC packaging?
    Thanks,
    Loveena.

    Hi,
    IDoc Bundling is the changing the occurance of IDoc.
    In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC u have to perform this steps
    1.Import the IDoc to XI.
    2.Export the IDoc(i.e XSD format) and save it to the local machine.
    3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
    4.Save it as an XSD file Itself.
    5.Import the XSD file in the IR under the External Defination.
    6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
    Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
    IDoc Packing is collecting of IDoc
    <a href="/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm of Multiple type IDOCs in BPM</a> BY Pooja
    Regards
    Santhosh
    Remember to set the thread to solved when you have received a solution
    [url=Use a Good Subject Line, One Question Per Posting - Award Points;  Use a Good Subject Line, One Question Per Posting - Award Points[/url]

  • Difference between Idoc Adapter and Proxies..

    HI XI Guru's,
    I am new to XI, I wanted to know what is the difference between Idoc adpater and proxies. When and what should be preffered ?
    Warm Regards,
    - Priya R

    idocs which mean - (intermediate documents)  are standard  document formats which sap systems use to store as well send data from one system to another. If this is the format in which data has to received by R/3 then you will use idoc adapter in XI.  idoc adapter can be used to communicate between systems is with  SAP release higher than  3.1.X. Communication using idoc adapter is always asynchronous.
    proxies are available for communication between  SAP systems with version WAS 6.20 and above. They support both synchronous as well as asynchronous modes of communication. Generally when you are looking at developing new application using WAS 6.20 and above then you can design the interfaces for this new applications in SAP XI and generate the required code for these interfaces automatically in SAP systems using transaction code - SPROXY in the case of ABAP Proxy and in the case of Java proxies the code is generated by SAP XI system itself. You only have to implement these interfaces in your new application. So, basically you have to only worry about building the application and the interface part is taken care by XI itself. you can also look at using proxies when data has to be inserted or fetched from custom/standard tables in R/3 using XI.
    ,idoc adapter can be used for commuincation between ABAP stacks only but Proxy can be used for both ABAP as well JAVA stack.

  • Difference between idoc and .txt

    What would be the main difference between managing an interface with txt files and creating idocs to make a connection on SAP and an external system.

    Refer this thread -
    what are the advantages of idoc compare to flat file. how data is secure
    Regards,
    Amit

  • Difference between idoc and rfc

    what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

    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
    RFC
    Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    note:reward points if solution found helpfull.....
    regards
    chandrakanth.k

  • Difference between IDOC Type WBBDLD06 and WP_PLU03

    Hello Friends,
    Can you please suggest me the difference between IDOC Types WBBDLD06 and WP_PLU03.
    Regards,
    Narendra Goyal

    No Answer

  • Difference Between Rollback Segments and UNDO Tablespace

    Hi guys,
    Can you tell difference between Rollabck segments and UNDO Tablespaces.
    I think that rollback Segemnts and UNDO tablespaces are similar both are used for storing before imags of data, which is going to be modified.
    but my question still both the rollback abck segments and UNDO tablespaces exists.
    why and what is the reason of both existing and at what time, we can use..them at which scenarios's
    Regards,
    Pavan Kumar N

    Undo segments in undo tablespaces, introduced in 9i, are the successor of rollback segments.
    They are automatically managed by Oracle.
    Rollback segments exist for reasons of backwards compatibility.
    That said, you should switch to undo segments and stop using rollback segments.
    Other than that: could you please avoid rehearsing the complete documentation in this forum?
    Sybrand Bakker
    Senior Oracle DBA

  • Difference between IDOC Type and Message Type

    Hi, please let me know the difference between IDOC type and Message Type?
    Thanks

    Hi,
    Message type is business name for IDOC you are sending hiding all technical details of the IDOC.
    IDOC type gives more technical information about structure of the IDOC.
    You will be linking IDOC type to message type while processing IDOC in runtime.  You will be specifying message type and IDOC type in WE20 trasaction which says which message will go to which partner whether it is outbound or inbound.
    Best Regards,
    Krishna

  • Difference between IDOC & RFC

    1. Can someone explain the difference between IDOC & RFC
    2. from processing point of view which one would be the best performance

    IDOC      BAPI
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system.
    BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    Idocs are processed asynchronously and no information whatsoever is returned to the client,      
    BAPIs are called synchronously and (usually) return information
    The target system need not be always online. The IDOC would be created and would send the IDOC once the target system is available (tRFC concept). Hence supports guaranteed delivery      
    whereas for BAPIs the client code needs to do the appropriate error handling.
    With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later      
    Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client cannot be finished (otherwise there would be data inconsistencies).
    The disadvantage of asynchronous links is that the sub-process on the server cannot return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.      
    Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link.
    IDOCs may
    be more changeable from release to release.
    BAPIs are not totally immune to upgrades
    IDOCs  are poorly documented      
    BAPIs are reasonably well documented.

  • Difference between the design of clusters PCLx and others like RFBLG etc .

    There are a few nagging questions which I was not able to find in the forum hence i have to post a new question.
    I am a little confused about the difference between the different clusters .
    If i start with RFBLG i.e. the cluster for BSEG BSEC etc ,I can see that the tables which are part of this cluster
    can be viewed through different methods like
    1) whr usd list for RFBLG
    2) dd02l table and give the required parameters there
    now when I compare this with another so-called cluster PCL1 if find that PCL1 is not recognized as  a cluster
    and also I am not able to see the same in dd02l table when i give PCL1 and the tabtype as cluster which I was able to see
    for the RFBLG ,there are other tables similar to RFBLG .
    1) SO what is the difference between the RFBLG type of clusters and the PCLx type of cluster
    2) are pclx and rfblg..type of clusters same ?
    3) why does PCL1 shows that it is a transparent table ? where as rfblg shows in a diff way in se11
    4) i know we access data from PCL1 using import and export stmts ,DO OR CAN WE DO THE SAME FOR RFBLG
    5) I found that each and evry cluster table had diff fields ,this was kinda surprising for me as I had been thinking
    that all cluster tables need to follow a certain rule ,SO WHO DECIDES THE FIELDS OF A TABLE CLUSTER ?
    6) PCL1 has the index button enabled ,which again I think is not according to the cluster table rules?how?
    7) I understand that we can save data in form of internal tables in the PCL1 cluster ,can we do the same in RFBLG ?
    8) Can I think on lines that PCL1 and RFBLG type of cluster are two totally different types of data dictionary objects
    and the usage and implementation of both of them is different and that the design and the BASE of both of such objects
    is different .
    I know this is a long list but I am sure that answers to these questions would really require some one who has really really work hard and invested a lot of time in understanding the dictionary system.I am awaiting a few answers ,few hints and a healthy discussion till we get them .
    Thanks ...
    a

    Hello,
    1/
    BSEG is a typical Cluster Table.
    This means that the physical table BSEG does NOT exist in the database, physical data for BSEG is stored in the database (table) cluster RFBLG.
    In ABAP however you can perform selects on BSEG (with all fields from the SAP repository structure, see SE11 on BSEG), during execution the SAP database layer will translate these statements to physical selects in the RFBLG database table, so in ABAP this is transparant.
    More info :
    [http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm]
    2/
    PCL1, PCL2, ... are normal SAP transparent tables, however in HR they are often called HR cluster table.
    Transparent tables are SAP objects where there is also a database table with the same name that contains the physical data.
    However the PCL tables are somewhat different from normal transparent tables (data is compressed, external programs can not interpret the data, ...).
    This means that in ABAP you can not use simple SQL statements to access data in PCL tables (because of compressed format).
    In stead statements like EXPORT TO DATABASE and IMPORT FROM DATABASE need to be used.
    More info :
    [http://fuller.mit.edu/hr/cluster_tables.html|http://fuller.mit.edu/hr/cluster_tables.html]
    Wim

  • Difference Between IDOC Message Type PORDCH & ORDCHG

    Hi
    Could anybody clarify me difference between Idoc types PORDCH & ORDCHG.
    For PO Change (Can be adding new line item, deleting existing line item, Change existing line item )
    which IDOC is suggested.
    Can i use ORDCHG Idoc for this purpose, But i find many fields are not exist in this segment.
    Pl clarify.
    Rams.

    Use ORDCHG message type with basic type ORDERS03

  • What is the difference between the Intel HD Graphics 5000 and the Intel Iris Pro Graphics in  the current iMacs

    What is the difference between the Intel HD Graphics 5000 and the Intel Iris Pro Graphics in  the current iMacs?

    I am assuming you are talking about PPC Macs? Those haven't been manufactured or sold in years (since early 2006 I believe) when Apple started using Intel processors. There are still some apps which run on PPC code only which makes them incompatible with the last three Mac operating systems.
    There are different Applecare products depending on which Mac product you buy, although the coverage is about the same (except for iOS devices).

  • Are the main differences between the 768 GB Flash storage and the 3 TB Fusion Drive?

    Are the main differences between the 768 GB Flash storage and the 3 TB Fusion Drive?

    About Fusion Drive
    Fusion Drive combines 128GB of super fast flash storage with a traditional hard drive. It automatically and dynamically moves frequently used files to flash for quicker access. With Fusion Drive in your iMac, booting is up to 1.7 times faster, and copying files and importing photos are up to 3.5 times faster.* Over time, as the system learns how you work, Fusion Drive makes your Mac experience even better. All while letting you store your digital life on a traditional, roomy hard drive.
    About Flash Storage
    For maximum performance, you can configure your iMac with 768GB of flash storage instead of a traditional hard drive. Flash storage delivers up to four times the performance of a traditional drive — speed you’ll notice when you start up your iMac, launch an app, or browse your photo library.
    In addition the prue flash option is $900 more the then 3TB fusion drive.

  • What is the difference between the new version of lion and the one manufactured last year.

    I just bought a new iMac. I found out it is the version of lion from mid last year and not the latest version. What is the difference?Should I return it and buy the latest version?

    Shootist007 wrote:
    petermac87 wrote:
    Shootist007 wrote:
    Barney-15E wrote:
    The difference between the one releases last year and the one that will be released this year is that the one that will be released this year is different from the one released last year.
    Not really. Lion is Lion, last year, this year, it is still Lion.
    Yes, but it's a different version. Very cleverly said Barney
    Pete
    No it is not. The newest update just adds some things to it, no new features and only fixes bugs. It is still Lion OS X 10.7.x. It is not 10.6 or 10.8.
    It is just a "Point" release and not a New Operating system. All Macbook Pros that could run Lion from last year can run the newest Lion Point release from this year.
    Oh and by the way Barney was talking about Mountain Lion, 10.8. Which is a NEW OS X operating system and has nothing to do with Lion 10.7.x. And it is not out yet.
    lol. Don't bust a blood vein. The comment was made in jest, but if you want to be serious, then OK 10.7 and 10.7.1 were different than 10.7.2 and 10.7.3. Why? Well one little thing called 'iCloud' for a start.
    Shootist007 wrote:
    Oh and by the way Barney was talking about Mountain Lion, 10.8. Which is a NEW OS X operating system and has nothing to do with Lion 10.7.x. And it is not out yet.
    Sorry, there was absolutely no mention of the upcoming 10.8 that I could see in Barney's comment.
    Cheer Up. Life can't be that bad.
    Pete

Maybe you are looking for