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

Similar Messages

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.

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

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

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

Archiving Job. Running and no file..

Hello all!
For a some cubes (not for all!!!) I have problem.
Archiving job write to log
DROP VIEW "/BI0/0302712378"
SQL-END: 15.01.2007 12:09:29 00:00:00
Selection conditions for the archiving request were checked successfully
Archiving session 000012 is being created
And it is all... Job running up to 48 hours and no files created...
Other cube have not problem:
28.12.2006 12:04:49 SQL-END: 28.12.2006 12:04:49 00:00:00
28.12.2006 12:04:49 Selection conditions for the archiving request were checked successfully
28.12.2006 12:04:50 Archiving session 000010 is being created
28.12.2006 12:04:52 Path: /Archive/
28.12.2006 12:04:52 Name for new archive file: archive_BW_1228_0.120452.GOLOD
28.12.2006 17:09:09 Name for new archive file: archive_BW_1228_0.170909.GOLOD
Help me.
Thanks.

Hello,
Please ask in the
Visual Basic .Net Language forum on MSDN if you want a program.
If you are creating a script or batch file, I'd ask in
The Official Scripting Guys Forum!
Neither place is a good place to go to if you want someone else to do the work for you.
If you want hints or suggestions to improve what you already have, then the above suggestions are valid.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

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

Schedule archiving jobs

Hi,
We are trying to schedule periodically the archiving jobs for several objects.
To be more specific, we begin with MM_EKKO archiving object and we would like to chain the 3 steps : preprocessor the write, then delete.
Chaining delete after write is easy : In "technical Setting", we just have to tickle "start automatically" in the "delete jobs" parameters.
But how to chain automatically write step after preprocessor ?
Obviously, I tried usual options in SM36 and used "after job" parameter. But what job can I enter as the job name for precprocessor is automatically generated by SAP and changed at every new job (the date and time are included in the name, e.g : ARV_MM_EKKO_SUB20110406163238) ?
Do I need to use an exernal third party scheduler to do this ?

Serge,
I have been researching on your query lately and have put accross this question to some Archiving Experts at my end. Hopefully, will come up with a full-proof solution.
But in the meantime, if you have a sandbox or if you can do a research, please do the following:
1. In SARA, under the TECHNICAL SETTINGS tab go to the VERIFY ARCHIVE FILES box.
2. There just click on the following, Before Deleting, Before Reading and Before Reloading.
3. I think this BEFORE READING box could be a solution.
4. And for deletion check the START AUTOMATICALLY option.
Please try this and let us know. If solved, okay and if not then I will reply back after conveying from the experts.

How archiving jobs (WRI) on specific server

I have one database and two application servers. Whenever I start archiving jobs (WRI) are created on database server. I would like to push archiving on one other application server(but do not know how to do that). If i shedule job(..SUB..) and force it to an application server (long lasting) WRI jobs are being executed againon database server. How to avoid that
In trx "Sara"->customizing->Cross archiving Objects Customizing: Technical settings there is an setting "Server group for Background Processing" but I do not know what to set as Server Group Name(is it an logon group out of smlg or?). Setting like server_<SID>_<Inst.nr.) is not correct.
Please help

Hi,
You have to maintain the server group in transaction SM61--> button "Job Servergruppen" (nice english transalation !)
Regards,
Olivier

Automate Archiving Jobs

Hi
We wanted to run the Archive jobs every year by Company Code and Object wise.
We have around 7 sales companies and 10 objects so we have to run 70 jobs Every year. So we wanted to automate this process so that we dodnt need to eneter the texts etc and schedule the jobs every year.
But these are the problems which we are facing:
1.If we wanted to Archive SD_VBAK object for the ABC Sales org , then we need to enter some text( some thing like "ABC Slaes org 1999 Year Sales docs") in the varaint(this can done using table TVARVC(By using Dynamic variants).
2. But after the jobs, we need to change the Spool paramaters,where in we will select the output device,Storage Mode as " Archive " only, and Text same as which I used earlier in step .1.
But how can we make this Text field to get the value from TVARVC or somewhere ? Sicne its Popo-up box.(This spool text will be the Archove File name ,which will be displayed when we are reading the Archives.)
Can somebody help to advice what are ways to Automate the Archive jobs( so that users doenst need to run these 70 jobs manually every year by entering Text and spool text etc..?
We are running on SAP 4.7 version.
Thankyou

SARA is the tcode for archive objects

Scheduling of Archive jobs

Hi,
i really need to apologize here, but i did not found an appropriate forum to ask this, neither a forum for ADK archiving development kit nor a forum about XBP (intercepted jobs). If there is a froum for asking questions like this you can slap me for that
The archiving object is configured to schedule the ARVSTO jobs automatically which we want to keep to spread the load over a certain time and not to have a bunch of archiving jobs always running at a specific time.
In this system we do not have a connection to a central job scheduling tool due to license costs.
The problem is that sometimes ARVSTO jobs are scheduled exactly at the time where our IXOS serving is going down for 15 minutes for maintanence.
I'm now looking for ANY possibility to avoid that ARVSTO jobs are scheduled between 4 and 5 o'clock. I hat a look at OSS notes 458670 and 604496, with those notes i can avoid that the jobs are starting automatically but i need an external job scheduler or i need to start them manually. I dont have a job scheduler and i dont want to do this manually.
I had a look at report RSARCHD to do a modifaction but as far as i can see this one is only scheduling the ARVDEL jobs.
So does anyone have an idea to solve this? Even if it is a modification, or en enhancement, a BADI or en exit, i dont care.
Thanks in advance.

Create one procedure and write all your logic which you want to schedure.
Please execute the below block to set the job.
Please change ### with Your PROCEDURE NAME WITH PARAMETER.
'SYSDATE+1/1440' = Indicate that your job execute every minute..
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job => X
,what => '###'
,next_date => to_date('17/02/2010 12:54:32','dd/mm/yyyy hh24:mi:ss')
,interval => 'SYSDATE+1/1440 '
,no_parse => TRUE
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
END;
commit;
Edited by: user10594896 on Feb 16, 2010 11:28 PM

Archive jobs / Delete job

I have some questions regarding Archiving / Deleting..
1) What are the implication of not setting 'DELETION' category parameters in 'Specific configuration'.
2) How do I delete the messages that are archived? Will 'Delete job' handle this also?
3) Also I had archived some messages using Archiving job.. When try to lookup this message using 'Archived XML Messages (Search using Archive), I get a list of Archived messages. When I click on any of this messages, I get "Could not find message in archive" message.

hi,
- did you activate SAP_BC_XMB info structure?
- did you do all the configuration?
http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/content.htm
BTW
you can also fill activated information structure retrospectively for already existing archives:
http://help.sap.com/saphelp_nw04/helpdata/en/5c/11afaad55711d2b1f80000e8a5b9a5/content.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Problem while Scheduling Archive Jobs from SXMB_ADM

Dear all,
I am using this blog to delete and archive messages.
/people/deepak.shah/blog/2010/04/22/archiving-deletion-of-messages-in-pi--part-2
I have configured Retention periods from SXMB_ADM and there by scheduled Archive Jobs through SXMB_ADM itself.
Now when i check in SM37, after Archive jobs scheduled , i am not able to see 2 jobs as described in this Blog.
i am able to see only one Job with name "SAP_BC_XMB_ARCHIVE200"
Please assist me what might be the problem
Regards

Hi Ganesh,
Thank you for replying. Once this SAP_BC_XMB_ARCHIVE200 is finished, one more job has been generated
ARV_BC_XMB_WRP20100602112115. But this is not for deletion . it is doing archiving
When i check the log, SAP_BC_XMB_ARCHIVE200 contains the program as RSXMB_ARCHIVE_PLAN
and ARV_BC_XMB_WRP20100602112115 job contains the program as RSXMB_ARCHIVE_MESSAGES
There is no job generated for deletion of Archived ones.
>>Deletion job starts automatically if in archiving setting u have selected START AUTOMATICALLY option for deletion .
Could you please let me know where this should be done while doing Archiving jobs??
Regards

Archive Job error

Hi friends,
I have done Archive configuration setup. In Define interfaces for archiving given 1 interface (which i want to do archive) and retention period as 1 day under asynchronous XML msgs. Scheduled a archiving job on the same day. After all these, I triggered one successful msg. The job ARV_BC_XMB_WRP* gets cancelled with error msg "Error when accessing the archive data". But I am not able to see the archive file in the physical path given in the configuration.
whr this msg gets archived?
Could any one help me wht is the problem and how to correct this?
thanx,
kumar

Hi Sumit,
Thanx for ur reply.
Got the msg ID from table and that cancelled msg in Moni and that gets archived whn job ran today.
Cancelled msgs are getting archived only If I maintain the below entry
category            Parameters                                         Current value
RUNTIME    PERSIST_ARCH_MANUAL_CHANGES          1
in Integration Engine Configuration ---> Specific Configuration.
But in this case, every cancelled msg getting archived irrespective of the Interfaces given in Define Interfaces for Archiving. But i need to archive the cancelled msgs only for the interfaces defined.
To do this, I selected the "Manually cancelled Msgs" check box for the interface given in Define Interfaces for Archiving, but not working.
Again help me out on this.
Thanx,
Kumar.
Message was edited by:
        ms kumar

XI Archiving: Restarting a terminated archived job.

Hi All,
Due to some constraints, our PI server (devt) has only 9.5 GB of disk space for the archive directory. We have 300,000 messages that is flagged for archiving and it seems that the archiving job will terminate with a dataset_write_error which we assume is caused because there is not enough disk space in the archive folders.
After moving the previous archive files out of the directory to reclaim the disk space, we restarted the archive job.Will restarting the archive job allow the archive job to pick up from where it was terminated or will it "restart" from beginning?
Anyone experienced something similar before?

Dear Lugman,
the behaviour of the new archiving job depends on the configuration of archiving object BC_XMB (transaction AOBJ). If the option "Do Not Before End of Write Phase" is set (default), then the next archiving job will start from the very beginning. In this case all archive file written by the previous job can be deleted. If the option is de-selected the new archiving job will start with the last archiving file. All files that were written sucessfully before the error ocurred are safe.
In general you might also want to increase the retention period temporarily. This way you reduce the number of messages to be archived in one single blow and you have better control on the data volume that is written to file.
Best regards,
Harald Keimer
XI Development Support
SAP AG, Walldorf

IDOC Archiving Job

Similar Messages

Maybe you are looking for