Idoc Archiving

hi,
   In the production for writing idocs to archive file , a variant is scheduled every monday, which has mesgtyp and last changed date.
mesgtyp is BOMMAT
   the issue is they say that the job is skipping records...can anybody suggest how to check which are the records that are skipped?
points are assured....
regards,
priya.
Message was edited by:
        Priya Parvathi Jammalamadaka

Hello,
Not exactly sure what to say execpt to check out oss note 791185 to see if that helps. Also, the help text on the last change field states:
Date on which control record was last changed
Use
The time of the last change does not match the time of the last generation! The controlrecord therefore always changes if the IDoc is credited a new status record.
You could manually query table EDIDC using the "last change date" field (UPDDAT) to get a list of idoc's that you wish to archive. Then, run the archive job. Use the IDOC Read program to analyze the archive file to see which idoc's were selected and compare that list to the query to find out which idoc's were not selected.
Regards,
Karin Tillotson

Similar Messages

Runtime error DBIF_RSQL_INVALID_RSQL on BW Idoc archiving.

Hi Experts,
I am facing one issue while performing IDOC archiving in BW system.
While running write program with RSEXARCA, I am getting ABAP dump DBIF_RSQL_INVALID_RSQL
with a exception CX_SY_OPEN_SQL_DB. 'Error in RSQL module of database interface' as a short text.
Please let me know what could be the problem.
Regards,
Mohan.

Hi,
You can try to implement the latest DBSL patch in order to solve this. You can implement the latest Kernel and DBSL patches from the links below.
-> http://service.sap.com/patches
-> Support Packages and Patches - Entry by Application Group
-> Additional Components
-> SAP Kernel
Regards,
Rafael

Long runnning IDOC Archiving jobs

Hi Techies,
Long runnning IDOC Archiving jobs: ARV_IDOC_WRI* are being observed in PRD system with Avg runtime > 150,000 sec.
Job Details:
Main Program: RSEXARCA
Parameter: IDOC ALL MONTH
These jobs are also resource consuming & extensively using CPU & Memory.
For info: These jobs are getting finished but only after long runtime.
Some SQL stmts observed while this job-execution:
SELECT
"OBJKEY" , "OBJTYPE" , "LOGSYS" , "ROLETYPE" , "ROLEID" , "UTCTIME"
FROM
"SRRELROLES"
WHERE
"CLIENT" = :A0 AND "OBJKEY" = :A1 AND "OBJTYPE" = :A2#
SELECT
"MANDT" , "DOCNUM" , "COUNTER" , "PAGENO" , "TIMESTMP" , "PAGELG" , "VARDATA"
FROM
"EDI40"
WHERE
"MANDT" = :A0 AND "DOCNUM" = :A1
ORDER BY
"MANDT" , "DOCNUM" , "COUNTER" , "PAGENO"#
SELECT
"DOCNUM" , "DOCREL" , "STATUS"
FROM
"EDIDC"
WHERE
"MANDT" = :A0 AND "UPDDAT" >= :A1 AND "UPDDAT" BETWEEN :A2 AND :A3 AND "DIRECT" BETWEEN :A4 AND :A5 AND
"STATUS" = :A6 AND NOT "MESTYP" IN ( :A7 , :A8 , :A9 , :A10 , :A11 , :A12 , :A13 , :A14 , :A15 , :A16 ,
:A17 , :A18 , :A19 , :A20 , :A21 , :A22 , :A23 , :A24 , :A25 , :A26 , :A27 , :A28 , :A29 , :A30 , :A31 )
Please suggest as to how the job runtime can be reduced.
Awaiting for your reply.

Hi,
Since the variant used is fetching data for the entire month, you could try splitting the jobs and have multiple runs instead.
You can also try to schedule the jobs when there is minimum system load, incase its not already done.
As far as the program is concerned, if this is standard program, there is little scope for tuning.
You can always check for related index quality and statements with high CPU costs to better understand why the job is running for such a long duration.

RSEXARCD: Idoc archiving deletion program issues

Hi,
I have two queries:
1. The Idoc archive deletion program, RSEXARCD, when executed in background, terminates when there are no archive files to process (as seen in SARA). How can we prevent this? Our deletion jobs are scheduled weekly, but sometimes there are no archive files created from the archive write program RSEXARCA.
2. Secondly, how can we process multiple archive files using this program RSEXARCD in background? Currently, it processes only one archive file at a time and takes up the oldest unprocessed archive file. Also, would like to know how it gets this information of the oldest unprocessed archive file?
Thanks.

if a program terminates, then you should look into the dump to see the root cause and follow the instructions. e.g. search for OSS notes with the metioned terms
I just searched with the terms "archiving idocs termination" and found 12 notes with program fixes.
Further, the program names you mentioned are not the most recent programs.
Have a look into OSS note Note 582828 - IDoc archiving: Standardization
maybe you will not have your problems anymore if you use the new programs

Delete job failed in IDOC archiving

Hi Gurus
Delete job for IDOC archiving failed with the following error.
"Job started
Step 001 started (program RSEXARCD, variant PROD_DELETE, user ID CTMBATCH)
Archive file 002558-001IDOC is being verified
Operating system message: Permission denied
Archive file 002558-001IDOC does not exist
Error during verification when accessing archive file 002558-001IDOC
1 archive file(s) were not successfully verified
Job cancelled after system exception ERROR_MESSAGE "
I checked the status of the job in management , and it says Write and Storage is successful. I checked for the archive file and it is present in Exchange directory.
As the error message states that "Operating system message:Permission denied", so I am expecting that It should be related to some authorization for the directory. Or might be if authorizations has been modified for uid which. But I am not sure on this. How can I confirm this on SAP level ??
This job is a weekly job but it failed this time. What else should I check?
Please let me know if anyone has encountered similar issue before. I wish to know the reason for this error and the resolution to it.

Hi,
based on your description I am not quite sure if this is really a question on DMS. Could you please provide more details about which IDOC type do you use and maybe some error message number. This would help to clarify the reason faster.
Best regards,
Christoph

ABAP or variant for IDOC archiving?

If I want to create a batch job that archives certain IDoc status records based on a formula ie. (current date - 90 days or earlier) will I have to write ABAP to make the call to the archive program or is there a trick to create a variant and schedule this easily?

I am sorry, I left after my last response. What I told you will work for you. For the date-from you will select the variable "current date +/- days" and give -90 there. Also for the date from you will say <=(less than or equal to). So your range should have looked like
Date Created <=06/03/2005 to blank.
I forgot to put the <= sign in my previous post. I tried this and it worked for me. You don't have to manually enter any values here. All you have to do is save the variant with the selection variable and the sign <=.
Anyway, I see that you closed the post, so I assume you got the solution.
Srinivas

EDIFACT File TO IDOC Archive directory file name.

HI Experts,
I have EDIFACT file to IODC scenario. I have multiple source file locaiton but only one Archive location directory.But I have three different kind of file coming form three different location.
we can only have one archive directory per service, is it possible to manipulate the file name so we can tell if files were successful or failed?
For example, FileName1.txt, if it was successful, it would move to the archive directory and rename to u201CFileName1.txt.PASSu201D,
if it failed it would move to archive directory like u201CFileName1.txt.FAILu201D. Is this functionality possible?
Or will we just have to rely on Alert Categories to tell us when files have failed?
Kindly give your valuable suggestion.
Regards,
Sumit Gupta

>
sumit gupta wrote:
> HI Experts,
>
> I have EDIFACT file to IODC scenario. I have multiple source file locaiton but only one Archive location directory.But I have three different kind of file coming form three different location.
>
> we can only have one archive directory per service, is it possible to manipulate the file name so we can tell if files were successful or failed?
> For example, FileName1.txt, if it was successful, it would move to the archive directory and rename to u201CFileName1.txt.PASSu201D,
> if it failed it would move to archive directory like u201CFileName1.txt.FAILu201D. Is this functionality possible?
> Or will we just have to rely on Alert Categories to tell us when files have failed?
>
> Kindly give your valuable suggestion.
>
> Regards,
> Sumit Gupta
When you say success or failure does it mean a successful IDoc created in SAP? if so you will have to use a BPM and on successful creation fo the IDoc write the file out with the PASS name else FAIL name.
you can also look at employing scripts but there is no standard feature for this requirement. I gather alert is a better option.

IDocs archiving - legal requirement?

Hi everyone,
I am quite well aware of everything concerning archiving but lately a legal point has been raised within my company which is to know if we must keep or not the iDocs we archived. If yes how long?
We do archive and retain documents such as invoices, sales orders, financial docs etc.. as long as it is specified by the most restrictive law of the country where our business is present. Right now we are also archiving all our iDocs after a couple of months and we keep them in retention for 10 years, however this has a cost because it needs a huge amount of disk space. We are wondering if this is necessary from a legal point of view (especially for the iDocs concerning invoices) since the iDocs are not the document themselves but could be needed to retrace the workflow of a specific document.
Hope my explanations were clear enough
Thank you for any clarification on the topic

Hi Sreeny,
Thank you for your reply. This specific Requirement to ARgentina will maybe developed for us, since we have no way to assure the solution by keeping the standards tools. Thank you for your cooperation.
note: in the past, about 5 years ago, it was possible to download prin documents as you´ve sent me. Do you know is this document is still available in the web? (print files, print document).
Best regards,
Lucia

Idoc archival Path

Hi Guys,
I want to know the path where idoc been archived? Is it somewhere in the sap database or at operating system level?. If it is at operating system level, can you let me know how to find the path where idocs are achived.
Thanks in advance,
Harikrishna.

Hi Hari,
archive files will not be stored in the database; it will be stored in the file system at operating system level (or on any of the mounted file systems). another possibility is that it can be stored in an external storage system if you are using one.
You can know the path as follows (if it is stored in the file system):
- go to transaction SARA
- enter object name as IDOC and enter
- click on management
- expand the tree of 'complete archive session'
- select any of the recent archive sessions and expand the tree to the maximum level
- then double click on any of the archive files, you will see the path where the file is archived and file name of the archive file
hope this helps,
Naveen

IDOC Archiving Job

Folks,
I submitted a single IDOC job in R/3 (Immediate run) in Production system. Interestingly my job did not got triggered, I verified going to SM37 with my ID no jobs listed and also when I clicked Management button in SARA I'm getting a message No Management data available. Can some one suggest me what would be the problem for this?
Thanks in Advance,
Kumar

Hi,
based on your description I am not quite sure if this is really a question on DMS. Could you please provide more details about which IDOC type do you use and maybe some error message number. This would help to clarify the reason faster.
Best regards,
Christoph

Reg : Blocking and archiving of IDocs

Hi All,
          Could anyone please let me know when does the need arise to block an IDOC?
          I heard it some where that for some type of errors we can not reprocess the idoc and so they will block that and resend it once more.
         If anyone has worked on this type of issue, could you please give me some information?
And one more thing is regarding the Archiving of IDOCS : Could nay one please let me know the importance of IDOC ARCHIVING and it's use?
Regards
Abhilash.

Hi,
Blocking Idocs most extensively is used in master data, where we block the errored IDocs, rectify the error and replicate once again. Transactional data IDocs can also be blocked as per the situation.
With archiving, IDocs are archived in various tables in the database in order that the size of the tables could be reduced without losing any IDocs. The transaction used for archiving is, SARA where the archiving object selected in this case is "IDOC".
~ Bineah.

Error in creation of PurOrd IDoc

Hi All,
I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG but when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
What could be the possible problem?
Highly appreciate any kind of help.
Thanks in advance,
Shweta
PS: <REMOVED BY MODERATOR>
Message was edited by:
Alvaro Tejada Galindo

Hi
Check the Partner Profile in WE20 correctly
also see the steps for it as per the doc
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.
Regards
Anji

Unable to get Field Names from Archived File

Hi All,
We have a ECC 6 Ehp4 system. When i retrieve Idocs archived using SARA, the data only contains application data. There is no field names available - eg: posting date, tax code etc. Please find below the background on this issue.
I configured archiving of process idocs (status 52,12,03) from EDIDC tables. I set up the settings for Archive Object IDOC and archived the data for 15 days.
Both archiving and deletion of data from the table was successful.
I tried reading the Idoc data from Archive File using the Information System option -> Info structure (available as default for Idoc).
But the data retrieved only shows the Application data for all the segments of the IDoc. The fields for the segments like Tax Code, Posting Date etc are not available in the data. Functional teams will not be able to make sense with just the application data.
Am I missing some setting? Is there any way to retrieve the related field values also ?
Please help.
Thanks and Regards,
Raghavan

Hi All,
There is tcode WE10. You could choose if the data source is archive and also the archive session. You will get the list of segments provided. click on the segment number and you will get the data.
Thanks and Regards,
Raghavan

How to cancel an idoc in status 64

How to cancel an idoc in status 64

Hi Manju,
If you have table updation access then
Go to SE16 --> Table EDIDC --> Give your "IDoc number" --> change the status from 64 to "73 IDoc archived".
Or you can ask to your ABAPer to do that.
Hope it helps,
Regards,
MT

Archieve idoc

hi all
i m solving error(status 51) idoc but its posting period is closed so need to post it by archeiveing it.
so plz do needful

Hi Paresh,
Please try with tcode SARA and object IDOC for idoc archiving.
Reward points pls.
Regards,
Govind.

Idoc Archiving

Similar Messages

Maybe you are looking for