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
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 regardsHai,
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. -
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. -
Configurations & Process Steps to Archive Purchasing Documents
Hello All,
Can you please let me know what are the steps involved in Configuring steps for archiving Purchasing documents & also the Process Steps to Archive Purchasing Documents
Awaiting for your replay..
Thanks in Advance.
KiranHello Mushtaque,
You can use the link
http://help.sap.com/saphelp_nw70/helpdata/EN/8d/3e4e74462a11d189000000e8323d3a/frameset.htm
Regards, Jatin -
Dear Experts
1. Is ME82 meant for Archiving the Purchasing Documents or for viewing the Archived Purchasing Documents.
2. Here arcive Puchasing Documents : does it mean archive of only po or other documents also like PR,RFQ,Scheduling agreement,Contract.
Pls solve my doubts.
Kind Regards
Sajid1. Is ME82 meant for Archiving the Purchasing Documents or for viewing the Archived Purchasing Documents.
For viewing
2. Here arcive Puchasing Documents : does it mean archive of only po or other documents also like PR,RFQ,Scheduling agreement,Contract.
All purchasing document types -
SARA Archiving Idocs and the retention period , RSEXARCB
Hi Experts
I am having few questions on the Idoc Archivng -
1. I want to know the safe retention period for Idocs , I am planning to do archivng of Idocs which are 60 days older or more. How to determine the exact period for Idocs that we can keep in the database tables and also in the file system. What will the exact time in tables and also in Filesystem before we copy to a tape.
2. About program RSEXARCB , I want to schedule automatic background job for only Idocs which are in status 3 and 53 using this program every week. In this program I dont see any variable or any selection field where I can select this options. Is there any other program in SAP where we can select this options?
FYI - We are on ECC 5.0
Thanks
ChandraHi,
Thanks for your reply please.
But while making changes to the retention period i am getting following message:
Diagnosis
A retention period has been entered for a profile value category, that
is shorter than that of the billing document headers.
This is an invalid entry, because you cannot archive profile values
before billing document headers.
System Response
The system does not permit you to save the retention period combination.
Procedure
Correct the retention period for the profile value category or the
corresponding billing document header category accordingly.
Please guide.
Thanks and Regards -
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 -
How to adjust SM21 logs retention Period
Hi,
My requirement it to get the system logs for minimum for 5 months,
i have set the parameter "rslg/max_diskspace/central"
but still i am getting the logs for 13 days only.
So please let me know the exact clean up job name for SM21 log,
so that i can adjust the retention period.
and also do i need to adjust the parameter "rslg/max_diskspace/local" too to get the required SM21 logs?
Regards,hi,
For the list of standard jobs please refer this sap note
16083 Standard jobs, reorganization jobs
1411877 New standard jobs
For the system log details please refer this points
1. The local system log file
a) File names
The local system log file that is written to each application server is determined by the profile parameter rslg/local/file.
The name of the file is usually SLOG<inr>, where <inr> is the instance number. Therefore, the name is SLOG77, for example.
In most systems, the profile parameter rslg/local/old_file is also set and points to a file SLOGO<inr>. This 'old' local system log file is not created by default. Instead, the current local system log file is written 'in a circle'.
b) File size
'Writing in a circle' means the following: If the file has reached the maximum size (profile parameter rslg/max_diskspace/local), the system overwrites the oldest entry with the latest entry and so on. The local system log file always has the same file size as of this moment. The profile parameter rslg/max_diskspace/local describes the maximum file size in bytes. If you switch from non-Unicode to Unicode, you must double the value of this profile parameter.
The central system log file
a) File names
The profile parameter rslg/central/file describes the name of the current central system log file, and the profile parameter
rslg/central/old_file describes the name of the 'old' central system log file.
b) Size of files
The profile parameter rslg/max_diskspace/central specifies a size in bytes. If the current system log file has reached half of this size, it is copied to rslg/central/old_file, and a new current central system log file is started.
Additionally refer this note
862 Reduce size of system log file
Regards,
Naveen.
Edited by: Naveen Kumar on Mar 5, 2012 2:18 PM -
Transaction Logs - Retention Period
Hi,
Which parameter/bg job is responsible for maintaining the transaction log for <n> number of days?
Regards,
CsHi Cs,
The data is you get from STAD is stored at the OS level file (location given by the parameter stat/file). This parameter points by default to the instance-specific /Data-directory (for example: \usr\sap\<SID>\DVEBMGS00\data) however this can be changed depending on your choice.
For each hour a new stat file is written.
The parameter stat/maxfiles determines how many stat files will be written until the oldest is overwritten.
So depending on your requirement and available disk space size, you can increase these parameters.
Note - these parameters are instance specific. you have to maintain for each instance you may have.
Regards,
Debasis. -
Archiving Purchasing documents particularly scheduling agreements
Hi ,
I need to archive scheduling agreements.
Kindly let me know the process for archiving it.
I have tried using SARA and the object MM_EKKO but the agreement number which i try to archive returns the message , no data selection found.
Thanks in advance,Hi ,
The steps followed are :
goto SARA.
1. select object MM_EKKO.
2. Then goto "maintain variant". Input the scheduling agreement number. Save the variant.
3. Start the program by clicking START DATE and SPOOL PARAMETERS.
4.This is how i start the write process.
5. The message NO DATA CORRESPONDING TO SELECTION FOUND is received after the write process.
Kindly suggest a way to resolve this.
The scheduling agreement has been deleted i.e. the line item has been marked for deletion.
Edited by: Vinayak Venkatesh on May 1, 2010 6:46 PM -
Archiving purchase orders of a specific order-type
hello,
does anyone have a simple-doc or plan for archiving purchase orders. archiving for dummy's as I have never done this?
points to be taken into consideration:
- order of a specific type (ZRL0)
- order must be older then 10 days
thanks,Hi,
In order to archive PO's , there are a number of considerations that must be taken into account.
The archiving program SARA -> MM_EKKO , Write , does a large number of checks before archiving can be done.
The first step is to go to SARA -> MM_EKKO , customizing. In here , you can specifiy what kind of documents you want to archive and specify the retention period (document life) for each type of document.
For example :
Go to C MM-PUR : Reorganization PO
You will find several type of PO Doc types
DB Dummy purchase order Standard
NB Standard PO Standard
NB Standard PO K Consignment
NB Standard PO L Subcontracting
NB Standard PO S Third-party
NB Standard PO D Service
UB Stock transport ord. U Stock transfer
Suppose you want to archive Standard PO's , go into the customizing option and then set the residence time 1 and residence time 2.
Res time 1 is the number of days which must elapse after which a deletion indicator can be set for the document. The elapsed days are calculated from the last change date of the document record in EKKO table.
Res time 2 is the number of days which must elapse after which a document with a deletion indicator can be actually deleted out of the EKKO table.
Once the customizing is finished , then you should run the SARA Preprocessing job (which sets the deletion indicators for the selected set of documents) , then the write job (which will write the DLT status documents to an archive file) and then the delete step (which will remove documents from the EKKO and other related Purchasing tables. TO get a trailer of what gets archived and deleted , run the archive write job in "Test" Mode , rather than "Production" mode.
Hope this helps.
-Chandra -
Change document log for Infotype 0033 Statistics
Dear experts,
I must log IT0033 Statistics as we do for other infotypes using report RPUAUD00. As only subtype is filled log doesn't show changes for it.
Could you help me with that? I've tried with SCU3 but as PA0033 in marked as not logged it doesn't work also.
Thanks in advance and have a nice day,Please check if configuration is maintained in the below SPRO path:
IMG->Personnel Management->Personnel Administration->Tools->Revision->Set up change document
If infotype is not maintained, try maintaining it for :
HR documents: Infotypes to be logged - Tr Class - 'A', Infotype - '0033'
HR documents: Field group definition - Field group - '01', Field name - '*'
Now re-run the report RPUAUD00 after making changes to IT033 record. -
Differentiating of pricing schema for each purchasing document type
Dear colleagues,
This topic could be discussed before but I need to clarify some points.
We would like to differentiate pricing schema per purchasing document types (e.g. AA and ZZ). These purchasing documents are not like domestic and import types.
There some condition(s) where purchasing document type AA should not be able to maintain whereas ZZ should be able to.
In this case shall use one unique pricing schema for both purchasing document types if so how can I hide some conditions for document type AA or if I use separate pricing schema how can I set different pricing schemas for different purchasing document types because both document types have same purchasing organization, vendor etc.
Regards
MetinHi,
Why to have two different schema groups! Is procurement process is completely different, so use to have!
(have thought of separate condition types for each Calculation Schema)
Based on Schema Group Of Vendor in the vendor master, the PO for vendor with respective Schema Group Of Vendor will populate the assigned condition typesu2019. Follow path:
SPRO->MM->Purchasing->Conditions->Define Price determination process ->Define Schema Determination
Under segment:
Determine Calculation Schema for Standard Purchase Orders
Here you can assign Schema Group Purchasing Organization, Schema Group of Vendor and Calculation Schema
Under segment:
Determine Schema for Stock Transport Orders
Here you can assign Schema Group Purchasing Organization, PO document type and Calculation Schema
Regards,
Biju K -
Report for finding G/L account per purchasing document / reservation
Is there a report to get a list of G/L account for Purchasing documents / Reservations? If not, can a new scope of list for any standard report such as ME2N / ME2B be created to include the G/L account list?
Hi,
As division is not header field of invoice it is not available in accounting document header as well. Thus it will not be available in any standard reports showning items per account. I'm affraid you need to develop your own report or try to extend existing using user-/customer-exits.
You can find more information in OSS note 13131.
Regards,
Marcin -
Hi experts,
I'm working on the SRM archive process. I'm in extended classic scenario so my purchase order is created on SRM and duplicated on ECC. I only want to archive purchase order on SRM and not on ECC.
When the user is looking for the purchase order on ECC how does he know that the order is archived on SRM ?
Thank you for your help.
Regards,
Mikaël.Hi Peter,
Thank you for your answer.
I will used a cutomer field on the ECC purchase order and create a specific program to update this customer field from SRM data and tables ZARIX...
Thanks,
Mikaël.
Maybe you are looking for
-
When playing games on an iphone 3gs is it common for it to go warm on the back?
when playing games on an iphone 3gs is it common for it to go warm?
-
Currently I family-share my iTunes with my minor daughter. She purchases songs which are charged to my bank card. l would like to set her up with her own apple id so she can purchase her own songs and use her own bank card, but still share so I kno
-
*Im getting frustrated !* Specs: I just bought an airport extreme (802.11n) Mac os X 10.5.4 & Windows Vista I want to connect the airport wirelessly to my mac and some other wireless devices but also connect it through my D-link DSL-302G internet mod
-
I was wondering if there is any way to tell, using SAX, if an attribute is actually defined in an XML document or if it is only being defined by the default value in the DTD. The issue is I am creating objects modelled by XML, and there is a "base" a
-
User should not be able to import a request.
Dear Forum, We have a role created with all the transaction (*) given to a user. We want to revoke/restrict the authorization to import a request. User be able to create/edit/release the request but should not be able to import. This should happen