How to view archived IDoc's

Hi experts,
i need to view the archived content of the archived idocs. i tried with SARI(Infostructure SAP_IDOC_001),
but i cant view the content of the archived IDOC's. the scenario is like,
> IDoc's are archived using SARA
> Delete that IDOC using SARA
> SAP_IDOC_001 infostructure got activated using SARI
after that i tried to view the content in WE10, but i cant. Is thr any other steps i missed here?
Plz help on this.
Thanks,
murugan.

Hi,
After activating Infostructure, Did you build the Info structure? If not then build it.
Path > SARI > Customizing > Status > Build structure > Select the Archive file and run it.
Note: After successfull execution the archive file will have green signle.
Then you can display the archived IDOC's
Hope this will help you.
-Thanks,
Ajay

Similar Messages

How to View Archived Data

Dear all,
        Can anyone pls tell me how to view the Archived data like same what we see in data target.
     I have used ODS as data target ,after archiving i want to see the same data format what we see on ODS Active data.
      Pls tell me how the data will be saved during archive and what format will it be saved and how to view it from the archived files.
Thanks in Advance.
Thanks
Gomango

Hi
Use the following tables to suite your objectives
RSARCHIPROLOCSEL BW Archiving: Archived Data Area
RSARCHIPRO BW Archiving: General Archiving Properties
RSARCHIPROIOBJ BW Archiving: General Archiving Properties
RSARCHIPROLOC BW ARchiving: General Local Properties
RSARCHIPROPID BW Archiving: Program References of InfoProvider
RSARCHREQ BW Archiving: Archiving Request
RSARCHREQFILES BW Archiving: Verfified Archive Files
RSARCHREQSEL BW Archiving: Request-Selections
Santosh

How to View Archived attachment in FI document

Hello Gurus,
We have a issue regarding to view attachment that was attached to Fi document.
Document was posted on last year and some mail attachment attached to that document.
We are able to view the attachment because it is archived.
Could you please let us know any one how to view attachment that is archived status.
Thanks & Regards,
Shanthi

Hi,
There is no standard procedure for change of BSEG table. You could develop your own using CHANGE_DOCUMENT function module.
Regards,
Eli

View Archived Idocs

HI Gurus,
Can you help me with reading archived IDocs by IDoc number. I tried SARA but that didnt help me.
Please help.

Hi Vinod,
You can use transaction WE09 to read an archived IDOC. After entering the IDOC number, click on the Data Source button and select the checkbox by Archive.
Hope this helps.
Best Regards,
Karin Tillotson

How to view archived projects

Hi
As an administrator I want to view or access archive project,How Can I do that
PS- I have archived project using below method
https://technet.microsoft.com/en-us/library/gg597607(v=office.14).aspx

The process indicates only non-admin users be given the Deny permission to view, so as an administrator you should be able to access the project. You should be able to simply access that project fro project Pro, or a view like "All projects"..
If you inlcuded yourself in that security group by accident, just take yourself out, and you will be able to see the project.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

How to view Archive documents in AW01N?

Hi,
I have 2 questions related to Asset Accounting
1. All my FI documents have been archived prior to 2007. Now in AW01N (Asset explorer), I am able to see the values of any asset prior to 2007. But, when i double click the Line item like Acquisition, sale, it isnt going to the FI doc and i receive an error message " It is not possible to view the accounting document" since its archived. In asset explorer, there isnt any document no., so I am unable to find which document it is.
2. We can post depreciation to Cost centre and Internal order, Whether can post to a Network or an activity?
Kindly let me know if anyone knows the solution
Regards,
Ameet
9840244480

Hi Markus,
Thank you for your reply!!!!
It helped me getting the accounting document nos. when Acq, retirement transactions are made. I have another issue, when a settlement from the WBS element is done to an asset, I am able to get the settlement document no. and when i branch in from the settlement doc to the accounting doc, i get the same error "Accounting document cannot be dispayled from financial accounting"
Is there anyway i can see the archived accounting document from a settlement document.
Thanks in Advance for your help!!!
Regards,
Ameet
9840244480

How to view archived printlist

Hi experts,
i want to view the archived printlist content. i did the following steps..
> Scheduling jobs in SM36 (before this i did the basic settings)
> Archiving the prinlist using SP01
> Pushing the queue to asyn req. using OAM1
then executed it. its archived, then what i have to do view the archived printlist content..
thanks,
murugan.

Hello,
In OADR transaction you can see archived Printlist document.
Hope this will help you.
-Thanks,
Ajay

How to view archived material master

Hi,
I need to view the archived master master.
When I checked in forum I found out it can be done through tcode SARA
and object MM_MATNR. But I cant find archived material master in it.
Please guide me.
regards
sathya

Hi Sathya,
The set of files which you are getting are the archive files. All your archived materials will be contained in those files. If you know the date when the material you are looking for was archived, you can select the archive file which was created on that date. Or as Juergen mentioned, if there is a proper note for the archiving session, it will be easier to find. In case you dont know the archiving date / there is no archiving note, then you may have to run MM72 on the archive files one by one till you get your material.
Thanks,
Naveen

How to view archived messages in XI

Hi All
we have recently done some settings in integration engine level to archive messages older than 3 months. it works fine.. However, as per current requirement, we need to analyze message ran approx 4 months ago. Is there a way to see archived messages? If so, can any one guide me ?
Thanks in advance.

Open sxmb_moni and there you will find archive option too.
Regards,
Prateek

View archived renumeration data

Hi friends,
Does any one have an idea how to view archived renumeration statements data?
We can view the payroll data from PC_PAYRESULT transaction code but customer needs to view archived renumeration statements data?
Many Thanks for your time.

Hi,
Please check SARA transaction - Arc object PA_CALC.
Regards,
Dilek

Archive & View Archived TDS documents

Hi All,
Can anybody explain me the procedure how to do Archive TDS Ddocument(2ID) and how to View Archived TDS documents(J2IE).
It is urgent, please help me out in this regard.
Regards
Srinivas

Hi Anandh,
Based on the settings provided by the Basis Team, messages in Adapter Engine will be archived. In your case messages from Adapter engine archived for every 5 days. You can also view these archived messages at RWB.
RWB --> Message Monitoring --> Messages from Component = Adapter Engine --> From = Archive  Click Display button.
At Filter select From Date and To Date --> click Start button. Then you can able to see the archived messages from Adapter Engine.
Reward points if this answer is helpful.
Regards,
Sridhar.

Cannot display archived idoc data records in SARA

Hello,
In our ERP system, we regularly archive idocs older than 6 months. To view these archived idocs I use transaction SARA (with archive object IDOC and infostructure SAP_IDOC_001) to search for the relevant idoc that has been archived. Once the idoc is displayed, I drill down further by clicking the magnify glass button which then displays the idoc levels:
EDIDC               Control record (IDoc)
EDIDD               Data record (IDoc)
EDIDS               Status Record (IDoc)
SRL_ARLNK      SREL: Archive Structure for Links
When I try to view the Data Records, I get a message saying "You are not authorized to display table EDIDD". According to our Authorizations department, this is not an Auth issue but rather config setup or program issue.
Why can't I view the archived idoc data records? Is there another way to view archived idoc data?
Regards,
Fawaaz

Hi Jurgen,
Thanks for moving my post to the correct space.
Our Auth team is very confident that this is not a user auth issue. This could possibly be true because the idoc data resides on the following tables when in the database (before archive) - EDIDC, EDID4 & EDIDS. The idoc could then be viewed via transaction WE02 or the Data Browser (SE16). There is no EDIDD table in our ERP system so obviously no authorization object to assign to.
Once the idoc is archived, the data is removed from the ERP tables and moved to our archive database/server for storage. So when trying to view the archived record, the system does not access the ERP tables but rather the archive directory (that it's mapped to in settings). I assume the SARA transaction merely displays the data in the same segments/grouping with these table names (mentioned above in my first post) but instead of EDID4 it displays EDIDD.
According to the error longtext, "The check performed when data is read from the archive is the same as that of the Data Browser (transaction SE16)". So I was not involved with setting up our archiving procedure but could it be that table EDID4 was incorrectly mapped to table EDIDD in archives?
Regards,
Fawaaz

PLEASE HELP ME. Some important emails have gone to an archive mail box and i really need them. Can someone please help me with how to view the archive email box and the emails that are in there?

PLEASE HELP ME. Some important emails have gone to an archive mail box and i really need them. Can someone please help me with how to view the archive email box and the emails that are in there?

http://kb.mozillazine.org/Recovering_deleted_mail_accounts

How to find linked IDOCs from Archive Sales Orders

Hi Experts,
    Just would like to know if there's a way to find IDOCs that is linked to an archive Sales Order. I'm archiving IDOCs base on its Sales Order Document, If the SO doc is already archive then its IDOCs should also be archive.
Best regards,
    JP

Hi Mylen,
Yup... they're linked. Our sales order document are created from an IDOCs. During the archiving of those sales orders, it's related IDOCs are still left in the system and later archived according to their age and not the status. What I want to do is to hold IDocs for as long as the reference sales document (object) is still on the system and archive them if the reference doc has been archived. Thanks for replying.
Best regards,
   JP

How to Read an IDOC

Hi Experts,
Can any one explain me about IDOC, and how to read it once it is created.
Regards
Venu

Hi,
IDOCS:
IDocs are SAPs file format to exchange data with a foreign system.
IDocs are an ASCII file format to exchange data between computers; the format is chosen arbitrarily .
IDocs are similar to segmented files; they are not a description language like ANSI X.12, EDIFACT or XML.
The IDoc contents are processed by function modules, which can be assigned in customizing.
IDocs are structured ASCII files (or a virtual equivalent). They are the file format used by SAP R/3 to exchange data with foreign systems.
IDocs are simple ASCII data streams. When they are stored to a disk file, the IDocs
are simple flat files with lines of text, where the lines are structured into data fields.
The typical structured file has records, each record starting with a leading string that identifies the record type. Their specification is stored in the data dictionary.
IDocs is the acronym for Interchange Document. This indicates a set of (electronic)
information which builds a logical entity. An IDoc is e.g. all the data of a single
customer in your customer master data file, or the IDoc is all the data of a single
invoice.
IDoc data is usually exchanged between systems and partners that are completely
independent. Therefore, the data should be transmitted in a format that can easily be
corrected by the computer operators. It is therefore mandatory to post the data in a
human readable form.
Nowadays, this means that data is coded in ASCII format, including numbers which
are sent as a string of figures 0 to 9. Such data can easily be read with any text editor on any computer, be it a PC, Macintosh, UNIX System, S/390 or any internet
browser.
The information which is exchanged by IDocs is called a message and the IDoc is
the physical representation of such a message. The name messages for the
information sent via IDocs is used in the same ways as other EDI standards. .
Everybody who has ever dealt with interface programming, will find IDocs very
much like the hierarchical data files used in traditional data exchange.
International standards like the ODETTE or VDA formats are designed in the same
way as IDocs are.
Other EDI standards like XML, ANSI X.12 or EDIFACT/UN are based on a data
description language. They differ principally from the IDocs concept, because they
use a programming language syntax (e.g. like Postscript or HTML) to embed the DATA.
The IDoc process is a straight forward communication scenario. A communication is
requested, then data is retrieved, wrapped and sent to the destination in a predefined format and envelope.
An R/3 application creates data and updates the database appropriately. An
application can be a transaction, a stand-alone ABAP Report or any tool that can
update a database within R/3.
If the application thinks that data needs to be distributed to a foreign system, it
triggers the IDoc mechanism, usually by leaving a descriptive message record in the
message table NAST.
The application then either directly calls the IDoc engine or a collector job
eventually picks up all due IDoc messages and determines what to do with them.
If the engine believes that data is ready to be sent to a partner system, then it
determines the function module which can collect and wrap the required IDoc data
into an IDoc.
In IDoc customising, you specify the name of the function module to use. This can
either be one which is predefined by R/3 standard or a user-written one.
When the IDoc is created it is stored in an R/3 table and from there it is sent to the foreign system.
If the foreign system requires a special conversion, e.g. to XML, EDIFACT or X.12
then this job needs to be done by an external converter, like the Seeburger ELKE
system. These converters are not part of R/3.
If you have to decide on a converter solution, we strongly recommend using a plain
PC based solution. Conversion usually requires a lot of fine tuning which stands
and falls with the quality of the provided tools.
DIFFERENCE B/W IDOC AND BDC:
IDOC's are intermediary documents into which the data will be transferred and then this idoc's gets transferred to sap or non-sap system.
ALE is used to create link between 2 systems. So without the linking the data cannot be uploaded or downloaded.
BAPI, LSMW and BDC are used to transfer data b/w systems.
BDC is used to transfer data b/w only sap systems.
LSMW is used to transfer data b/w sap and non-sap systems.
ale Idoc: Idoc is a part of ALE. it is applicable only if the external system and the sending system have the same format. ALE uses Internationally Standardized formats. Also it is facilitating Asynchronous data communication and safest data communication. If you got errors also you can correct it and send it again.
lsmw: It the legacy data transfer. which is used for bulk data transfers. It uses BAPI, IDoc, BDc internally....
bapi: SAP Provided way of data transfer. if the BAPi suits for our business bettere to go for bapi. it too uses internationally standardized data format Business Objects concept.
idocs
1.We will see the status of the IDOC in We02 or We05.
2.In that There are three records.
a.Data record
b.status record.
c.Control record.
3.If u click on data record you can see the data ,which is transfering it.
Details about IDOC:
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.
http://sap-img.com/abap/reads-an-existing-idoc-and-dispays-the-contents-in-a-spreadsheet-format.htm
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
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
IDOC Creation....
http://www.erpgenie.com/sap/sapedi/idoc_abap.htm
You can view the definition of any IDoc data structure directly with transaction WE30.
u cn use function module 'FIELD_POSITION_IN_SEGMENT_GET' to extract data from idocs.
You can view the idoc through we02 or we05. In that there are three types
status records gives the status of that idoc in differenttimes
data records gives the data in that idoc
control records gives the date, time and creater of that idoc.
I think its helps you.
Thanks and Regards,
D.Revathi.

How to view archived IDoc's

Similar Messages

Maybe you are looking for