Retention period not maintained

Hi,
When i'm doing data archiving for purchase orders,i got the message " Retention period is not maintained ".
Please any one can tell where i have to maintain.

Hai,
In SPRO - IMG - MM - Purchasing - Define tolerance limit for archiving. In this maintain the residence time 1 & residence time 2 for the Purchasinh doc type & also with item category also.
Define Tolerance Limit for Archiving
In this step, you specify how long external purchasing documents are retained unchanged in the database before being archived.
You can define two time periods, via which you control the archiving of the documents:
Residence time 1 for items without a deletion indicator
Before the deletion indicator is set for a document item, the system checks when the relevant item was last changed. In the process, a change in the PO quantity is taken into account in just the same way as a goods receipt, for example.
The date of the last change is compared with the current date. If no change has been made within the residence time 1 entered , the deletion indicator is set for the item.
Residence time 2 for items with a deletion indicator
For document items for which the deletion indicator was set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The whole document is only archived if:
The deletion indicator has been set for all items of the document
None of the items have been changed during the residence time 2 entered - i.e. the last change is the setting of the deletion
The archived documents are then deleted from the database.

Similar Messages

  • Retention Period Not maintained Error when Archiving

    Dear Experts,
    i am trying to Archive the Archiving Object(MM_EKKO) but i have got the error below
    "Retention Period Not maintained" Error
    i tried to read different forums on this issue but am not sure i understand why this error happens.
    i appreciate your fast response!
    best regards

    Hai,
    In SPRO - IMG - MM - Purchasing - Define tolerance limit for archiving. In this maintain the residence time 1 & residence time 2 for the Purchasinh doc type & also with item category also.
    Define Tolerance Limit for Archiving
    In this step, you specify how long external purchasing documents are retained unchanged in the database before being archived.
    You can define two time periods, via which you control the archiving of the documents:
    Residence time 1 for items without a deletion indicator
    Before the deletion indicator is set for a document item, the system checks when the relevant item was last changed. In the process, a change in the PO quantity is taken into account in just the same way as a goods receipt, for example.
    The date of the last change is compared with the current date. If no change has been made within the residence time 1 entered , the deletion indicator is set for the item.
    Residence time 2 for items with a deletion indicator
    For document items for which the deletion indicator was set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
    The whole document is only archived if:
    The deletion indicator has been set for all items of the document
    None of the items have been changed during the residence time 2 entered - i.e. the last change is the setting of the deletion
    The archived documents are then deleted from the database.

  • Archive purchase document  log -  Retention period not maintained

    Hello Everybody,
       I have been trying to archive the Purchase document, I have also set the Retention period is 0 (Zero), but  when i archive the some Purchase document, it is give log like that
    Object                                                     Message
    4700000053 00010                                           Retention period not maintained
    4700000066 00010                                           Retention period not maintained
    4700000079 00010                                           Retention period not maintained
    So please suggest me how to solve the problem
    Thanks

    Solved, by archiving

  • Default Folders Policy/Items retention period not respected ?

    Hello, 
    We have Exchange Server 2007 SP3 and we've set up a default folders policy to erase all mailbox content older than 31 days. 
    However in three mailboxes we've sampled this policy isn't properly applied : the mailboxes had mails newer than 31 days deleted ( some 20 days, some 28 days, mine had only 14 days old mails !
    Can you please explain to me why this is happening? 

    Thank you sir Allen
    I ran the commands you mentioned
    [PS] C:\Documents and Settings\Administrateur>Get-Mailbox "alias" | FL Identit
    y, ManagedFolderMailboxPolicy
    Identity                   : domain.com/Users/alias 
    ManagedFolderMailboxPolicy : TestPolicy
    [PS] C:\Documents and Settings\Administrateur>Get-ManagedFolderMailboxPolicy "TestPolicy" | FL Identity,ManagedFolderLinks
    Identity           : TestPolicy
    ManagedFolderLinks : {Entire Mailbox, Tasks, Notes, Journal, Contacts, Calendar
    [PS] C:\Documents and Settings\Administrateur>Get-ManagedContentSettings -FolderName "Entire Mailbox"
    Name                      MessageClass              ManagedFolderName
    testrem                   *                         Entire Mailbox
    [PS] C:\Documents and Settings\Administrateur>Get-ManagedContentSettings -FolderName "Tasks"
    Name                      MessageClass              ManagedFolderName
    Preventing Del            IPM.Task*                 Tasks
    I set the entire Mailbox to be deleted after 31 days, then creating managed content settings on tasks, agenda and contacts and uncheked the item retention period so that these items do not get deleted.
    tried to go with only deleting items from the inbox but it didn't delete those in custom folders(each user creates his own)... the other method worked though

  • Microsoft Azure Backups not reducing available recovery points or destination usage after retention period has been reduced.

    Microsoft Azure Backups not reducing available recovery points or destination usage after retention period has been reduced.  
    I had the retention period set to 30 day with around 6.8TB of backups. Over a week ago I changed the retention period down to 7 days, and it took a couple of days for the total recovery points to go down to 7. The destination usage was still going up.   
    I have come in today (monday) and the total backups is now 10 and the destination usage is now 7.57TB.  
    I only have the one server backing up to Azure Backups Services.  
    My questions are;  
    1. how long does it take for azure to delete backups from outside the retention period*   
    2. why are there move recovery points that the retention period?  
    3. Is there a way to purge just the backups outside the retention period?  
    *It does say the backup agent, "space allocation data is updated on a daily basis".
    It would be a great help if anyone had some information on this as the storage costs are getting very high.
    Thanks for the help in advance
    Z  

    Hi,
    Any update for this issue?
    If issue still exists, please open a case from http://azure.microsoft.com/en-us/support/options/, pick Recovery Services & problem type as “Backup”.
    Also please let me know the case ID so I can forward it to related support team for monitoring. Thank you for your time.
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Due times not aligned with Protection Group retention periods

    We have a customer running DPM 2012 and using disk and tape backup.
    There are 2 protection groups which have retention periods of 1 year and one with 5 year.
    In the tape report the following tapes are mentioned:
    4 tapes with a due date 1/2/2020
    4 tapes with a due date 1/2/2016
    And strange : 1 tape with a due date of 2/1/2018. This tape contains the protection for 2 servers using colocation for the so called Low and High group (1 year and 5 year which I mentioned previously).
    We can't explain the fact that the due date is on 2018 since we don't have a protection group with that retention parameter.
    Can anybody clarify with an example or assist?

    Plase put in this tape, make a rightclick and Show the "Tape Content"
    you should see which Datasource has which Retention range, maybe this helps.
    Seidl Michael | http://www.techguy.at | twitter.com/techguyat |
    facebook.com/techguyat |
    youtube.com/techguyat

  • E-Recruiting 6.0: Expiry & Retention Periods

    Hi Experts,
    Expiration Period
    Definition: It indicates the maximum period of time an application & the person-related data of the associated candidate may be saved in the system once the recruitment process has been completed.  The process is completed when the application status is set to 'rejected' or 'withdrawn'.
    Question (1):
    If I set the period to be 12 months, after 12 months, what happens to my applications?  Will the system automatically deletes it? How does the system actually works based on the config for this parameter?
    Retention Period
    Definition: It indicates how long a requisition and all related information (applications, applicant data, activities, audit trails etc) must be retained before they can be deleted.
    Question (2):
    I have set it to 12 months. But when i tried deleting a requisition which I have created, the system still allows it.  Can anyone share with me how does the system reacts based on my settings?
    Thanks in advance.
    William

    Well the functionality is not consistent.
    If you maintain periods of time for retention on a requisition, the workflow calculates a retention limit date for an application when it is rejected. It will never be updated automatically.
    A check on retention dates when deleting an requisition is not implemented. I checked the code but did not find anything.
    The only check on this date, which will be than in the candidacy information (hrp5133), is in report:
    RCF_DELETE_EXT_CAND
    Regards

  • Re: Retention Period, Residence time and Archiving Cycle

    Hello Experts,
    1.Could someone help me where we maintain the retention period, residence time and archiving cycle for an archiving object.
    2.How to schedule a background job for  archiving???
    Regards
    RR

    Hello RR,
    Residence period: Most of the archiving object residence period is maintained in customizing > Application specific customizing in Archive development tool access through transaction SARA.
    Note: There are some archiving object for which you can't maintain residence period however these archiving object residence period should be manually controlled in write variant.
    Retention Period: This retention period is mentioned in archive server.
    Total retention time = Online Residence period + Offline Retention period.
    2. You can schedule archiving jobs by SARA transaction. This transaction will help in scheduling the job background. Or By using Background user id, one can schedule the archiving jobs by background.
    -Thanks,
    Ajay

  • In Spool Retention Period adding - "Delete After 365 Days"? Is it possible?

    Team,
    rel 4.7
    I have the following retention periods in the spool drop down:
    Delete After 1 Days
    Delete After 2 Days
    Delete After 3 Days
    Delete After 8 Days
    Do Not Delete
    Question: I want to add other periods like 365...
    where can I maintain it.
    Thanks
    Naved
    PS. These retention periods carry over to SAPinBOX and populate expiration date field
    Message was edited by: SAPna2000
    Message was edited by: SAPna2000

    Hi,
    I know Job retention period by using T/code : SO16--> document org.
    Check this may help.
    Lanka

  • XI archiving retention periods doubt

    Hi All,
    I have a scenario in which i have to maintain different archiving and retention peroids for different interfaces in PI 7.0.
    But i can see that there is only place to in SXMB_ADM to maintain retention periods and we can just add our interface names to the list marked for archiving and deletion.
    So what can do to maintain different retention periods for different interfaces?
    Is this possible to not in the first place?

    Hi sivasakthi danasekaran
    It's NOT possible to have interface specific retention period and you noticed there are only 3 types possible a. for Asynchronous, b. for Synchronous c. History entries
    And it make sense that if you maitain some standards across the evironment.
    You may go through my Wiki on the same concept
    http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=147266890
    Regards
    Sekhar
    Edited by: sekhar on Dec 16, 2009 4:52 AM

  • Oracle BI publisher10g/11g -document retention period

    Hi
    I want to know once you get the output after scheduling a report in BI publisher , how long ( in number of days ) BI publisher keep that report or what is retention period of BI publisher for particular report after successful scheduling of job?
    can we alter the retention period of BI publisher reports?
    Regards,
    Sumit

    Hi,
    That was my problem, that the account details of the vendor are know by a person which does not work there anymore.
    Anyway, I manage to do it by integrating Weblogic with IIS and install the Siteminder Agent for IIS instead of Siteminder Agent for Weblogic.

  • Fiscal Year Variant not Maintained

    Hello All,
    while creating asset master using AS01 T Code i am getting an error "Fiscal year "A3" Variant is not maintained for Financila year 2010 for Compnay Code 0600".
    but i have configured Fical year variant and assigned to co code, i am able to post the transactions for all the periods i.e financial year 2010.
    here my question is whether we need to maintain the Fiscal year variant separately for Asset accounting in ECC 6.0.
    Please Suggest
    Thanks
    Shankar

    hi,
    please check the below path,
    spro--Financial Accounting (New) -- Asset Accounting -- Valuation -- Fiscal Year -- Fiscal Year Variants -- Specify Other Versions on Company Code Level and Specify Other Versions on Depreciation Area Level.
    check the above path, is there any FY is assigned to your company code or Depreciation Area.
    regards,
    Gopi.P

  • AUTOMATIC CLEARING FOR RECEIPTS실행시 PERIOD NOT OPEN ERROR

    제품 : FIN_AR
    작성날짜 : 2004-05-19
    AUTOMATIC CLEARING FOR RECEIPTS실행시 PERIOD NOT OPEN ERROR
    ========================================================
    Problem Description
    AR에서 Receipt이 "Remitted" 상태임에도
    "Automatic Clearing for Receipts"프로그램 실행시 아래와 같은
    Error가 발생하면서 처리되지 않음
    ARZACS module: Automatic Clearing for Receipts
    MSG MSG-01000: DEBUG: Before_Report_Procs.Check_GL_Date.
    MSG MSG-05000: DEBUG: GL_Date not within open period.
    ERR REP-1401: 'beforereport': Fatal PL/SQL error occurred.
    ORA-00000: normal, successful completion
    Solution Description
    Period가 open되어 있지 않아 발생하는 것으로,아래의 실제 Test과정을
    참조.
    Automatic Clearing Test step.
    1. Trx 입력
    GL_DATE 09-JAN-2004
    2. Receipt입력
    GL_DATE 09-JAN-2004
    Maturity DATE 15-JAN-2004
    (Payment Method는 Clearance Method가 "by Automatic Clearing"을 가진
    Receipt Class를 입력)
    3. Remittance 실행
    Receipts -> Remittances 에서 Auto Create
    4. Clearing실행
    Receipts -> Clear/Risk Eliminate에서
    "Automatic Clearing for Receipts" 실행
    Parameter중 Clear Date 11-JAN-2004로 입력
    5. 해당 Receipt이 Clearing안됨.
    6. 다시 Clearing실행
    "Automatic Clearing for Receipts" 실행시
    Parameter중 Clear Date 16-JAN-2004로 입력
    7. 해당 Receipt이 Clearing됨.
    위의 Test결과에서 알 수 있듯이,
    Clear Date는 Maturity Date보다 이후여야 함을 알 수 있다.
    또한, Maturity Date가 같은 Period내가 아닌 그 다음 Period, 예를들어 2월15일이라고
    해도 Clear Date를 2월 15일 이후로 입력해야만 해당 Receipt이 Clearing되었다.

    hi,
    pl go to OB52 and open the FI posting period for account type S.
    you will find either 1000 or 0001 as the field status variant for which you can select the acccoutn type S. You need to know what is the field status variant for your comp code. You find out by going to OBY6 ( Comp code global settings ).
    at OB52 you can maintain this way.
    1000 S zzzzzzzzz 1 2008 12  2008 13 2008 16 2008.
    regards
    sadhu kishore

  • Fiscal year "A3" Variant is not maintained for Financila year 2010

    Hello All,
    while creating asset master using AS01 T Code i am getting an error "Fiscal year "A3" Variant is not maintained for Financila year 2010 for Compnay Code 0600".
    but i have configured Fical year variant and assigned to co code, i am able to post the transactions for all the periods i.e financial year 2010.
    here my question is whether we need to maintain the Fiscal year variant separately for Asset accounting in ECC 6.0.
    Please Suggest
    Thanks
    Shankar

    Hi Murali and Christian,
    Thanks for your reply..
    now i have configured year dependent fiscal year to my co code, if i configure calender year i am able to create the Asset master
    please help
    Thanks
    Shankar

  • Error Message : Condition type is not maintained in the schema RM0002

    HI Gurus,
    I have created a new purchasing procedure as follows.
    ZVATV : <b>Condition Schema</b>
    VATV  : <b>Condition Type</b>
    VA : <b>Sch.Grp Vndr</b>
    When I create the Purchase order, the above mentioned schema, ZVATV is automatically determined.
    But when I create Contract, system throws an error message saying condition type VATV is not maintained in the schema RM0002.
    I am very new to SAP, Kindly explain in very detail about this error message and ways to get rid of it.
    If u have got any <b>very detailed material</b> about pricing kindly forward it to my mail id: [email protected]
    Thanks in advance.
    ~Gokul.

    Hi,
    The new condition type you are specifing is the gross price condition (PB00). for PB00 condition type a supplementary pricing procedure is assigned as RM0002. u may have copied the PB00 and changed it to VATV, but with out changing the RM0002. copy the RM0002 and in that also change the PB00 to VATV. after this go to VATV condition type control data (M/06) and assign the new supplementary pricing procedure instead of RM0002.
    The supplementary pricing procedure is required to have the condition types for which no access seqeunce is mentioned. All the condition types in main pricing procedure with out access sequence needs to be mentioned in supplementary pricing procedure.therefore all these condition types will have the same validity periods as PB00.
    Regards,
    Ramakrishna

Maybe you are looking for

  • ISync not finding Calendars in iCal

    To begin, I have "upgraded" to 10.5.3. I just attempted to sync my cellphone with my Mac, and noticed that iSync was not recognizing any of my calendars in iCal. When I clicked on the Calendars box in iSync, I got the following message: No writable c

  • Upgrade from 4.6C to ECC6.0 - development quality and production

    Upgrade from 4.6C to ECC6.0 I have got three systems right now... Development(D1)     Quality(Q1)    Production(P1). These three systems need to be upgraded to ECC6.0 The recommended process is to copy D1 to a new temporary server(D2) and then upgrad

  • Why does TCP tunneling remove http 503 response from async WS call?

    Hi all, I am facing a bit of a weird problem. I have developed and tested an asynchronous BPEL process which among other things invokes a 3rd party web service. It works fine in development environment. When I migrate to the customers test environmen

  • Copying Access Queries to Query Builder instead of SQL Commands

    Is there a way to copy Microsoft Access Queries to Query Builder (saved sql) instead of SQL Commands (saved sql)...Thanks in advance.

  • Service Calls - Major Bug or am I doing something stupid?

    Following on from a previous post I made: There are service calls for this equipment card Since version 2007 you can't change the customer equipment card's customer if there's related service calls (even if they're closed). I have made this post abov