ALEAUD issue

Hi,
I am trying to send an invoice idoc from an external system to R/3 using XI and want to get the status of the idoc using ALEAUD.
This is my scenario:
External system -> XI -> R/3(Invoice Idoc)
R/3 -> XI -> External system (ALEAUD Idoc)
I am able to send the IDOC to R/3 but when I send the ALEAUDIT idoc from R/3, it is received in XI and then I get an error in the technical routing of the response.
This is the error that i see in the trace:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_ALEAUDIT</SAP:Code>
<SAP:P1>51</SAP:P1>
<SAP:P2>SAPEA066</SAP:P2>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText>Messages from IDoc processing can be found in application log</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>ALEAUDIT: 51 SAPEA066 </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have defined the receiver determination for R/3 -> External system for ALEAUD idoc.
Can anyone throw some light on this issue?
TIA
ASHOK S

Hi,
We had the same problem and we opened a service call for it.
The Ack is for SAP environment end to end.
It works only if you do it R/3 -> XI -> R/3.
BPM cannot handle the ack since it's a part of an automatic mechanism you cannot interfere with.
If the Ext. sys. is SAP R/3 you need to add a user exit in the ALEAUD for it to work.
control_out = control_in.
CASE control_out-mestyp.
       WHEN 'ALEAUD'.
            CASE control_out-sndpor.
                WHEN 'Sender SAP Name'.
                    control_out-sndpor = 'XI name as configured in the Sender SAP'
            END CASE.
END CASE.
The other way to handle it is to create your own ALEAUD as Francisco described
Cheers and good luck

Similar Messages

Problem with ALEAUDIT Acknowledgements

Hi!
I am trying to implement the IDoc acknowledgment procedure based on the "How to Handle Acknowledgments for IDoc" document.
I have successfully received the acknowledgment from one of my receiver systems, but two of them are not working although I have checked the configuration several times. The ALEAUD IDoc simply doesn't go out.
I have tried the RBDSTATE transaction but I receive the message "No parties are interested in the selected data" (when I try the same on the system that does work I receive the last ALEAUD IDoc it has sent).
What should I check in order to get everything working.
Any help will be appreciated.
Eumir

Hi Eumir,
Have a look at these threads:
ALEAUD issue
Processing Acknowledgment Messages
Cheers,
Chandra

IDOC Acknowledgement with ALEAUD01 does not work

Hi,
since my last thread Changing IDOC status after succesful processing i learned much about IDoc's and ALE.
But my problem is still alive! I have the scenario IDOC (HRMD_A06) --> XI --> file. I noticed that the file adapter creates an acknowledge message and transfers it to the IDoc Adapter as an ALEAUD01 IDoc.
Unfortunately XI does not fill the ALEAUD01 IDoc in the right way. The field DOCNUM in segment E1STATE (which should reference the original IDoc) is always empty but the STATUS Field is set in the right way to 50.
The SAP 4.7 Application Server processes these ALEAUD01 IDoc without an failure and set the ALEAUD01 IDoc to Status 53, but the original HRMD_A06 keeps in STATUS 03. (Of cource, the application server can't determine the referenced IDoc without the DOCNUM!)
When i am editing these ALEAUD01 with transaction WE19 by filling DOCNUM in segment E1STATE manually and sending it to the Input Queue, everything works fine. The STATUS of the referenced HRMD_A06 changed to 39 (IDoc received target System) That's what i expected.
But why does not XI set the DOCNUM in segment E1STATE empty, when it generates the ALEAUD01? This makes no sense to me. Is this a bug of the XI IDoc adapter? Or is there any other trick?
Greetings

Hi Erik,
Pls go through the below links and my answers, that may help you to fix your problem.
Re: Acknowledgements ever switch to Status 39
Re: ALEAUD issue
Re: Steps For Updating the IDOC Status using ALEAUD
Re: Asyncronous acknowledge from file adapter
Regards
Vishnu

RBDSTATE not working

Hi to all,
I use RBDSTATE program to generate Ale Audit IDocs, but I receive this error:
"No parties are interested in the selected data"
What can I do?
Thanks to all!

HI,
Have a look at these threads:
ALEAUD issue
Processing Acknowledgment Messages
Regards,
Akshay.
Reward points if find useful.

ALEAUD in SAP - XI - SAP scenario

Hi!
My scenario is SAP 4.6C -> (IDoc adapter) XI (IDoc adapter) -> SAP 4.6C and the receiving system should send back an ALEAUD. The IDoc control record of the incoming IDoc contains the following info:
SNDPOR: port of sending system
SNDPRT: LS
SNDPRN: sender logical system
RCVPOR: XI port
RCVPRT: LS
RCVPRN: XI logical system name
Shouldn't XI send out
SNDPRN: XI logical system
and
RCVPRN: receiving logical system
to the receiving system so that ALEAUD can work? Do I need to configure a header mapping?
In the header mapping configuration in the receiver agreement I set
sender: XI business system
and
receiver: receiving business system
but the control record did not change. How do I configure header mapping correctly?
I also set the Restore Original Parties for Acknowledgements indicator which is available with SP19. "The original parties from the IDoc request message are used. This means you no longer have to maintain the alternative identifiers (for party conversion) in the Integration Directory."
http://help.sap.com/saphelp_nw04/helpdata/en/44/1e642ad9cb72b5e10000000a422035/frameset.htm
Thanks for your help.
Regards, Tanja

Before I ask my questions, please note I do have a copy of the "How To Handle Acknowledgements for IDoc" How To Guide. I just need some clarification from the group.
Here are my questions:
1. XI will not send a positve acknowledgement/status to let the sender system know it made it to XI ok, correct?
2. The only status that XI itself will initiate will be if there is a techncial issue with XI, correct? (Granted the Receiver system could send a positive or negative status back to Sender System) I just want to make sure that XI will not send a status back to Sender System that equates to "Triggering EDI subsystem OK" (or something like that)
3. How does the status of an idoc get set to 12 from 03? Does that mean that I always have the program RBDMOIND configured when I am interfacing to XI in order to force the status from 03 to 12?
4. As a norm, are those who are using XI seeing a 12 status on the Sender System IDoc Status?
5. If a techical issue error occurs in XI, what specific error status will be sent back to the Sender System?(if at all) I am looking for an example status number of what to expect.
6. If we are doing SAP R/3 to a partners XI system directly and that partner does not have RBDSTATE configured on their SAP R/3 environment and there is nothing else on their XI system for ALEAUD processing, I am out of luck in determining if the IDoc actually made it to their XI system, correct?
7. The Configure Scenario 2 in the document How To Handle Acknowledgements for IDoc" How To Guide should allow us to determine "did the Idoc get to that Server" correct?
Thanks for any feedback on this,
Ian

Problem with ALEAUD IDOC

Helo everybody
We have this scenario:
JDBC>PI-(IDOC)---->SAP
SAP(ALEAUD IDOC)>PI----->JDBC
But we cant recive the Aleaud Idoc in PI. We get this error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Anybodoy knows what´s happenning and how to solve it????
Thanks a lot

Christian Abad Chico wrote:
> Helo everybody
>
> We have this scenario:
> JDBC>PI-(IDOC)---->SAP
> SAP(ALEAUD IDOC)>PI----->JDBC
>
> But we cant recive the Aleaud Idoc in PI. We get this error:
>
> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
> - 
> - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
> <SAP:Category>XIAdapter</SAP:Category>
> <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
> <SAP:P1 />
> <SAP:P2 />
> <SAP:P3 />
> <SAP:P4 />
> <SAP:AdditionalText />
> <SAP:ApplicationFaultMessage namespace="" />
> <SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
This IDoc is received by PI as acknowledgement. Hence it tries to correlate this to the request IDoc and is not able to find the request IDoc. The correlation used is the idoc number DOCNUM under E1STATE
So, If you are manually generating the ALEAUD Idoc through we19 make sure that you fill in proper Idoc number in the above field to get rid of this error.
> <SAP:Retry>N</SAP:Retry>
> </SAP:Error>
>
> Anybodoy knows what´s happenning and how to solve it????
>
> Thanks a lot
From the description of your scenario, You need to get the ALEAUD message as a request message as against acknowledgement. For that you need to use the program IDX_ALEREQUEST program in PI as suggested by others in your other threads. If this issue is already solved, Please close the same.
Best Regards,
Nageshwar

ALEAUD back to ccBPM

Hello,
I have a scenario like this
WebService -> XI -> ccBPM (Sync-Async Bridge) -> async IDOC to R/3 -> ALEAUD -> XI -> close Bridge -> WebService Response
R/3 sends ALEAUD back to the ccBPM.
I'm sending an IDOC from a ccBPM to R/3 and in R/3 I'm sending the status of the posting via ALEAUD back to XI.
XI takes the the ALEAUD IDOC which is sent via the SM59 to XI and treats it like an acknowlegement for the send step even so my BPM send step has no acknowledgment requested.
My question is: Can I make XI not treat the ALEAUD for the BPM, e.g. configure an outbound async ALEAUD interface to XI? Or if XI treats the acknowledgement how can I get the ALEAUD IDOC data used in my ccBPM, e.g I want to map the stautus back to my web service call.
Cheers
Stefan

Before I ask my questions, please note I do have a copy of the "How To Handle Acknowledgements for IDoc" How To Guide. I just need some clarification from the group.
Here are my questions:
1. XI will not send a positve acknowledgement/status to let the sender system know it made it to XI ok, correct?
2. The only status that XI itself will initiate will be if there is a techncial issue with XI, correct? (Granted the Receiver system could send a positive or negative status back to Sender System) I just want to make sure that XI will not send a status back to Sender System that equates to "Triggering EDI subsystem OK" (or something like that)
3. How does the status of an idoc get set to 12 from 03? Does that mean that I always have the program RBDMOIND configured when I am interfacing to XI in order to force the status from 03 to 12?
4. As a norm, are those who are using XI seeing a 12 status on the Sender System IDoc Status?
5. If a techical issue error occurs in XI, what specific error status will be sent back to the Sender System?(if at all) I am looking for an example status number of what to expect.
6. If we are doing SAP R/3 to a partners XI system directly and that partner does not have RBDSTATE configured on their SAP R/3 environment and there is nothing else on their XI system for ALEAUD processing, I am out of luck in determining if the IDoc actually made it to their XI system, correct?
7. The Configure Scenario 2 in the document How To Handle Acknowledgements for IDoc" How To Guide should allow us to determine "did the Idoc get to that Server" correct?
Thanks for any feedback on this,
Ian

ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5

Hi All,
I am trying to configure ALEAUD in SAP->XI->JDBC scenario for Idoc acknowledgment.
I did following config in SAP
WE21 create port for XI
WE20 create Partner type XIDLOGSYS1 LS , Inbound parameter ALEAUD.
In XI I delete all entries from IDXNOALE table.
But still I am not receiving any ALEAUD in D02 when, any IDOC posted from SAP to XI.
In SXMB_MONI I am able to see Ack status Acknowledgment not possible
Please guide how to get ALE AUD in SAP from XI.
Regards

Before I ask my questions, please note I do have a copy of the "How To Handle Acknowledgements for IDoc" How To Guide. I just need some clarification from the group.
Here are my questions:
1. XI will not send a positve acknowledgement/status to let the sender system know it made it to XI ok, correct?
2. The only status that XI itself will initiate will be if there is a techncial issue with XI, correct? (Granted the Receiver system could send a positive or negative status back to Sender System) I just want to make sure that XI will not send a status back to Sender System that equates to "Triggering EDI subsystem OK" (or something like that)
3. How does the status of an idoc get set to 12 from 03? Does that mean that I always have the program RBDMOIND configured when I am interfacing to XI in order to force the status from 03 to 12?
4. As a norm, are those who are using XI seeing a 12 status on the Sender System IDoc Status?
5. If a techical issue error occurs in XI, what specific error status will be sent back to the Sender System?(if at all) I am looking for an example status number of what to expect.
6. If we are doing SAP R/3 to a partners XI system directly and that partner does not have RBDSTATE configured on their SAP R/3 environment and there is nothing else on their XI system for ALEAUD processing, I am out of luck in determining if the IDoc actually made it to their XI system, correct?
7. The Configure Scenario 2 in the document How To Handle Acknowledgements for IDoc" How To Guide should allow us to determine "did the Idoc get to that Server" correct?
Thanks for any feedback on this,
Ian

"ALEAUDIT IDoc cannot find request IDoc in Integration Server" error in PI

Hi Experts,
i am getting error "ALEAUDIT IDoc cannot find request IDoc in Integration Server" and
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code> in PI .
i am using ALEAUD.ALEAUD01 IDoc in my scenario.
i found two threads in SCN (scn.sap.com/thread/1370194,scn.sap.com/thread/1132815)but still i did not understand clearly for this issue .
Please clearly expline the solution for this issue in this thread ,i will give you points who post the correct solution.
Please send me solution for this issue clearly.
see the below payload also.
Thanks,
Aadi

the same problem
"ALEAUDIT IDoc cannot find request IDoc in Integration Server"
Could someone help with it?

Missing ALEAUD idocs

Dear Experts,
For one of our existing interfaces for Delivery Idocs from R3>PI>third party; we have an issue with the ALEAUD messages. This configuration is in place since a long time. Some of the Delivery Idocs are in status 12 in R3 system and they do not have the corresponding ALEAUD Idocs- hence the staus remains 12 and does not get changed to 39. The third party application has been receiving these delivery Idocs; hence I am not sure why we do not have ALEAUD messages getting created for these. I have checked the below:
In R3 WE09 I have searched ALEAUD messages for the Idocs in status 12 with filter: Segment:E1STATE and Field DOCNUM and heValue <Original Delivery Idoc Number>. For the 39 status idocs I do find ALEAUD Idocs corresponding to th original delivery Idoc. But for the Idocs in status 12; as suspected; I do not find ALEAUD messages.
In PI SXI_Monitor; I do not know how to corelate/find the ALEAUD message for a specific Delivery Idoc message. But I checked with approximate timestamp randomly and could not find the ALEAUD message for my delivery. Is there any other way to find if an ALEAUD message is created for an Original message?Checked in Trace and reliable messaging in SOAP header, response header; but no luck. For 1 hr I could find 2000 messages and going through each of them individually is not an option. I do not have time/aprovals to implement content based search on my production box within a short duration to apply any filter to find these messages.
Can you please help and tell me
1. How can I find/correlate ALEAUD messages for an original message in PI?
2. What could be the reason that ALEAUD messages are not getting generated; only for some messages; eventhough the same has been received at the Destination?

My issue was solved.
After further analysis it was found that the ALEAUD messages are created from the response messages sent by the receiving 3rd part system. Eventhough the 3rd party system was receiving all our outgoing messages; they failed to process the acknowledgement or confirmation for some of the messages. Inturn we received no confirmation responses from the third party and hence the ALEAUD messages were not created for the same. After finding this, the same was informed to the thrid party system and they are fixing the message confirmation/acknowldgement processing from their side. So the issue was closed.
I had also raised an OSS message for this where the analyst had asked me to check the below.. Please go through the same for your issue. Maybe it will help you...
"I looked at the example IDoc messages and i found no request message
created by the external system. Please give us the message id that
for the request message id that should create and ALEAUD-IDoc
for IDoc xxxxxx. If this is missing in the system please contact
the administrator of the external system why this request messages
was not created.
I found 126890 messages in the system with system error, possible
one of these messages contain the information for your idocs.
transaction SM58 i found many errors with function module
IDOC_INBOUND_ASYNCHRONOUS, this function module transports IDocs
and these IDocs are possible missing in the receiving system ?
Please check the errors and try to correct them."
Thank you

Multiple ALEAUD Idocs are being generated per original Idoc

We have the following scenario in PI:
ERP (IDOC)> PI (JDBC)> 3rd Party
PI sends ALEAUD idocs back to ERP when the process is successful. Program RBDAPP01 is then ran on a schedule to update the ALEAUD idoc status, which in turn, updates the idoc status of the orignal idoc sent from ERP (03 to 12).
We just upgraded our PI from 7.0 to 7.1. Now, it seems multiple ALEAUD idocs are being created for each ERP outbound idoc. It used to be 1-to-1. From what I can tell, it look like an ALEAUD it created for every receiver. For example, if we sent one idoc and the data goes to 3 receivers, 3 ALEAUD idocs are created. This causes an issue because the first ALEAUD idoc will update the original outbound idoc to status 12, but any other ones will take it from status 12 to status 09. We want it to stay in status 12.
Any ideas why 7.1 would be any different?

This seems to be the standard behavior. I will explain it.
If an idoc comes and message is sent to say three receivers, all the three message should generate the ack unless they are not disabled. And in this case you will find multiple ALEAUD message at sender. In case the receiver adapters are like File, JDBC which do not support application ack, then ALEAUD won't be sent and you will receiver "Applicaition Ack Not Supported". With this error, if multiple ack are seen in sender then I guess they won't actually perform any update.
Regards,
Prateek

Error in ALEAUD Idoc

Hi All,
When i send the MATMAS Idoc from ECC to XI, it is giving success and iam expecting the ALEAUD back to SAP.
If the ALEAUD idoc is posted successfully to ECC means ,the outbound idoc status will be turned into 39 status.Else it is in 03 only
when i check the status of ALEAUD, few of the Status is in 51 and saying the error as
Error when locking the audit statistics for DR2CLNT200 DWMS ZATEMATMAS
Please let me know the solution for this.
Regards

HI Vamshi,
This is a lock issue. When one idoc is trying to update a table and at the same time another idocs come to update it, then it will be locked.
In your case i believe the first ALEAUD got updated with success but when the second ALEAUD is upadting ECC, the third might have also reached thus locking it. If you can add some time delay in getting the response back then it might help with the lock issue.
Hope this helps.
Thanks,
Sudhir

While processing ALEAUD - "Error when locking the audit statistics"

Hello,
I am sending out IDOC for HR data and then prcessing ALEAUD inbound idoc immediatley (setting is done in WE21 partner profiles).
While processing these incomming idocs, I am getting this error "Error when locking the audit statistics for P01LOGSYS1 IMTIMEDEP HRMD_A" for few idocs. e.g. out of 1000 for 100 idocs this error will happen and IDOC goes to status 51.
If I try to process thes idocs ALEAUD using background processing and if I schedule 2 jobs at a time then I will get same error and IDOC goes to status 51.
Can someone help me out?

Hi
I tried processing the idocs in background processing as you have suggested using program RBDAPP01 (inbound).
There are 2 options in this program serial processing and parallel processing. When I select serial processing everyhting goes smooth but it takes long time. But when I select parallel processing I get same locking error mentioned above and only few idocs will get processed successfully with status 53 and all other will error out with status 51.
If I schedule 2 different jobs in background program RBDAPP01 (inbound) using serial processing then same thing will happen. only few idocs will get processed successfully with status 53 and all other will error out with status 51.
And I will get locking error ....
Note 1333417 says, " these IDocs will be processed via background runs of report RBDAPP01 \ RSEOUT00 (using background work processes) in batch mode leaving dialog work processes free for users and mission-critical processes. Hence you will not encounter the resources problems you are currently experiencing. The only other option would be to try increasing the number of available dialog work processes. The number of dialog processes must be greater than or equal to the total of the number of update and background processes per application server and must be configured across all operation mode
switches (see SAP note 74141). *However when there are a large number of IDocs being processed this is not a practical solution."*
Does that mean there is no possoble solution for this issue. If I increase dialog work processes will it be helpfull ?

Problem With ALEAUDIT

Dear All,
I have configiured ALEAUDIT to send acknowledgment back to XI. The issue which I noticed is in few ALE Acknowledgment you get the document number but in few we do not get the Document number from the acknowledgment even if the payload is posted correctly. Any idea what may be the problem.
Thanks
RGK

Hi,
Please try to analyse the ALEAUDIT IDOCs listed under WE02/WE05 in R/3 as well as check the IDX05 if the document no is comming properly.
If in some cases you are getting the Document nos. then better just try to Run the report IDXNOLE to off the IDOC acknowledgment and then again activate it.
Thanks
Swarup

New DVR Issues (First Run, Channel Switching, etc.)

I've spent the last 30 minutes trying to find answers through the search with no luck, so sorry if I missed something.
I recently switched to FIOS from RCN cable in New York. I've gone through trying to setup my DVR and am running into issues and was hoping for some answers.
1. I setup two programs to record at 8PM, I was watching another channel at the time and only half paying attention. Around 8:02 I noticed a message had popped up asking if I would like to switch channels to start recording. I was expecting it to force it to switch like my old DVR, but in this case it didn't switch and I missed the first two minutes of one of the shows. I typically leave my DVR on all day and just turn off the TV, this dual show handling will cause issues with that if I forget to turn off the DVR. Is there a setting I can change that will force the DVR to choose one of the recording channels?
2. I setup all my recordings for "First Run" because I only want to see the new episodes. One show I setup was The Daily Show on comedy central, which is shown weeknights at 11pm and repeated 3-4 times throughout the day. My scheduled recordings is showing all these as planned recordings even though only the 11pm show is really "new". Most of the shows I've setup are once a week so they aren't a problem, but this seems like it will quickly fill my DVR. Any fixes?
Thanks for the help.
Solved!
Go to Solution.

I came from RCN about a year ago. Fios is different in several ways, not all of them desirable. Here are several ways to get--and fix--unwanted recordings from a series recording setup.
Some general principles.
Saving changes. When you originally create a series with options, or if you go back to edit the options for an existing series, You MUST save the Series Options changes. Pretty much everywhere else in the user interface, when you change an option, the change takes effect immediately--but not in Series Options. Look at the Series Options window. Look at the far right side. There is a vertical "Save" bar, which you must navigate to and click OK on to actually save your changes. Exiting the Series Options window without having first saved your changes loses all your attempted changes--immediately.
Default Series Options. This is accessed from [Menu]--DVR--Settings--Default Series Options. This will bring up the series options that will automatically be applied to the creation of a NEW series. The options for every previously created series will not be affected by a subsequent modification of the Default Series Options. You should set these options to the way you would like them to be for the majority of series recordings that you are likely to create. Be sure to SAVE your changes. This is what you will get when you select "Create Series Recording" from the Guide. When creating a new series recording where you think that you may want options different from the default, select "Create Series with Options" instead. Series Options can always be changed for any individual series set up later--but not for all series at once.
Non-series recordings. With Fios you have no directly available options for these. With RCN and most other DVRs, you can change the start and end times for individual episodes, including individual episodes that are also in a series. With Fios, your workarounds are to create a series with options for a single program, then delete the series later; change the series options if the program is already in a series, then undo the changes you made to the series options later; or schedule recordings of the preceding and/or following shows as needed.
And now, to the unwanted repeats.
First, make sure your series options for the specific series in question--and not just the series default options--include "First Run Only". If not, fix that and SAVE. Then check you results by viewing the current options using the Series Manager app under the DVR menu.
Second, and most annoying, the Guide can have repeat programs on your channel tagged as "New". It happens. Set the series option "Air Time" to "Selected Time". To make this work correctly, you must have set up the original series recording after selecting the program in the Guide at the exact time of a first run showing (11pm, in your case), and not on a repeat entry in the Guide. Then, even it The Daily Show is tagged as New for repeat showings, these will be ignored.
Third, another channel may air reruns of the program in your series recording, and the first showing of a rerun episode on the other channel may be tagged as "New". These can be ignored in your series if you set the series option "Channel" to "Selected Channel". Related to this, if there is both an SD and HD channel broadcasting you series program, you will record them both if the series option "Duplicates" is set to "Yes". However, when the Channel option is set to "Selected Channel", the Duplicates Option is always effectively "No", regardless of what shows up on the options screen.
As for you missing two minutes, I have sereral instances in which two programs start recording at the same time. To the best of my recollection, whenever the warning message has appeared, ignoring it has not caused a loss of recording time. You might have an older software version. Newest is v.1.8. Look at Menu--Settings--System Info. Or, I might not have noticed the loss of minutes. I regularly see up to a minute of previous programming at the start of a recording, or a few missing seconds at the beginning or end of a recording. There are a lot of possibilities for that, but the DVR clock being incorrect is not one of them. With RCN, the DVR clocks occasionally drifted off by as much as a minute and a half.

ALEAUD issue

Similar Messages

Maybe you are looking for