Hi,

Normally I have selected archiving objects from a database space perspective. But what if I want to select from a perspective, where the goal is to have a better system performance?

Is there any way I can find the objects which will give the best performance improvements?

And will it be possible to measure the - hopefully - better performance in a way?

Thanks,

Claus.

Hi Experts,

please can you explain me

1. what are the checks will be done by pre-processing program and cross archiving object check program?

2. for what are the CRM objects, cross archiving object check program is mandatory? and how we can guess the same?

3. what are the status of the transaction no's or Object ID are able to archive?

    ex: transaction no should be closed i.e. should set the status I1005

4. why the "check and delete" functionality is available in both cross archiving object customizing and archiving object specific customizing in the customizing of CRM Objects? enclosed the screen shot for reference

5. what is Archive routine?

help is appreciated.

Thanks & Regards,

Ningappa S M

Hi Experts,

I am working on SAP ILM and would like to configure ILM Store to use File systems as the storage. Went through the SP13 ILM Store configuration guide to set up the FS connection and test them using the report provided. But getting a dump message. Has anyone configured ILM Store for FS system connections?

Best Regards

Raj

Hi All,

I would like to know what is the procedure followed for migrating ADK files and attached unstructured data stored on a non compliant ILM Storage to Compliant ILM Storage ?

Can you point me to any useful references and use cases on the same ?

When we implemented our manufacturing modules many years ago, we turned on auditing for many fields.

As a result, we have change documents that are very large.

So large, that they are causing the delivery archiving to abort due to memory.

When I tried to go into VL03N for the delivery in question, it also aborted when trying to display changes.

Has anyone else had this issue?

One workaround that I came up with is that we first PURGE all delivery change documents

before we archive the deliveries.  I just wanted to know what other alternatives that I have

and if anyone else had the same problem.

Mike

Hello Experts

We are planning to use third party external storage for the data archiving we have done and the document archiving which we will do in future?

I have following questions:-

1, What points should I consider for choosing best out of three apart from Cost and better functionality?

2. What would be your preference and why?

3. How complex it will be to move, already archived files from exchange directory to third party content servers?

Thank You

Hi all,

I have identified some large tables within SAP, and I'm looking at archiving possibilities.

Checking transaction SARA > Database Tables > Archiving Objects > Objects for Table, some tables have a 1-1 relationship with an archiving object while others have many archiving objects available.

Take for example Table COEP, when entered this lists many archiving objects.

Is there a way to determine which is the most appropriate archiving object to use, to remove the most records within the table?

Any advice appreciated.

Many Thanks.

Hi,

Can you share a comparison (pros and cons) between Informatica ILM Nearline and SAP data archiving tools, to be able to decide which one to use?

Thanks

Our application log is getting so large that it is causing performance problems.

I noticed that we have never archived or reorganized our application log.

I know that there are 2 options for managing the application log.

1. Tcode SLG2 - Program SBAL_DELETE can be used to purge old or expired logs
2. Archive object BC_SBAL can also be used to archive logs

Which option do you use at your company?

I tried testing the archive functionality in our QA test system and it was very slow.

It took over 7 hours to delete the following number of entries.

Type                               No.    Description

BALDAT                           293,908  Application Log: Log data

BALHDR                            61,254  Application log: log header

BAL_INDX                              13  Application Log: INDX tables

Has anyone else encountered such poor performance?

Hi experts,

I have a problem with archiving customers/vendors in sandbox system.

For some customers/vendors I have records in tables KNC1/LFC1.

Because of this I can not archive and delete customers/vendors by SARA.

Is it any way to archive-delete data from KNC1/LFC1 tables?

Thanks in advance

Hello Gurus,

    While considering for Archiving of an object how can we make sure that functional (including cross) dependencies are full filled?

    For example let's say I am Archiving Purchase Order data how can I make sure that relevant PO data in warehouse Module is good to be archived with no leaks? I know that DB15 gives all the tables/transaction codes that are cross connected across the functional areas.

    Any ideas? or document that I can refer too? further more is there a facility in SAP to see all the cross connected archiving data for example  I want to see the PO-> their relevant GR -> their relevant Invoices..etc...etc

Thanks ahead.

Charan

Hello Everybody:

We are in an Archiving Project and we had experienced a very poor performance when archiving RL_TA and RL_tb objects.

Thus we have to archive a lot of data, we had calculated that with the actual time of processing we will need almost a year to do this archiving data.

Does anybody have a tip or recomendation in order to improve the performance whe n archiving those objets?

We had look for SAP Notes about it without find something usefull

Thanks in advance for you valuable support on this matter.

Best Regards.

Julio Cesar

Hi All,

We are archiving customer master data through FI_ACCRECV Object and getting the below error even though I am marking the deletion flags.

Please help me on this.

Hi All,

I have a question, my client does not want to refer back archiving data from live system while performing operations.

How can we restrict? if we are disconnecting the archiving server then our web services are getting error messages.

Do we have to check for function modules which will not refer to archiving data.

If you have come across such scenarios could you please share your inputs.

We are using open text server as our archiving repository and we do it from SAP IS-U.

Thanks and regards,

N.Nagaraju

Dear Experts,

My problem is related to the following Forum -

http://scn.sap.com/thread/1332292#

I had already marked "Deletion Flag" & "Deletion Ind." for Production Orders using program PPARCHP1, but still found problem on archieving these Production Orders under "SARA" with object - "PP_ORDER" as below -

In the "Write" function, I unchecked "Delete with Test Variant" and executed with Production Mode -

The relevant scheduled jobs had been finished and these Production Orders could also be written to File System, but don't know why the following "Delete" log was still shown as "Test Mode (i.e. session 48)" instead of "Production Mode". I had ever tried to check the "Delete with Test Variant" in the "Write" function and execute the "Delete" function separately without checking the checkbox - "Test Mode", but the "Delete" log was still shown as "Test Mode (i.e. session 46 & 47). Now, these Production Order can still be displayed in CO03.

When archieving other objects such as "SD_VBAK" & "RV_LIKP", I didn't find the above problem. One more strange thing is that the session no. was NOT found in the above "Write" log to match the session no. of "Delete" log while the session no. of the "Write log" could be found in the other objects. Could you advise how to solve this problem ?

Many Thanks,

KH Fong

Dear Experts,

Further to the following Forum –

http://scn.sap.com/thread/3505830

I recently tested to archieve a Finished Good Material and found the following errors -

Error 1 –

MARC: 8200 planned order exists

Message no. W4008

Diagnosis

A planned order exists for the material. Procedure Delete the planned order. You can then archive the material.

Error 2 –

MARC: 8200 assignments (product group/planning) exist

Message no. W4024

Procedure

Delete the assignment of the material to the product group. You can then archive the material.

Error 3 –

MBEW: 8200 plant is assigned to the valuation area

Message no. W4031

Diagnosis

The material cannot be archived for this valuation area since the material is still used in dependent tables.

Procedure

Delete these dependencies. You can then archive the material for the valuation area.

Error 4 –

MARC: 8200 internal use of the material

Message no. W4107

Diagnosis

The material is still being used internally by another material.

Possible ways in which the material is being used:

As a pricing reference material

As a configurable material

As a follow-up material

As a manufacturer part number

The material may be in use both at material level and at plant level.

Error 5 –

MARA:  Dependent material master data still exists

Message no. W4134

For the Error 1, the above Forum had advised to check table PLAF and then found some Planned Orders for the Material in there. Would like to ask –

Q1) Why the Planned Orders could not be found in some transactions such as MD04 / MD16 (collective display planned orders) but could only be found in the table PLAF ?

For your ref., the following error was found when inputting those Planned Orders in MD14 (convert planned order to PR) –

Simulation planned orders cannot be converted

Message no. MD132

Diagnosis

The planned order selected is a simulative planned order from long-term planning. In long-term planning, the system only creates planned orders. These planned orders are not converted into either production orders or purchase requisitions. System Response Planned orders that are created in long-term planning cannot be converted. They are used to check the effects of the simulative demand program on production and procurement. Thus, a preview is availble of the planned demand program. The planned orders are changed or replanned in the operative planning run.

Q2) After deleting the Planned Orders found in the table PLAF using MD12 and then tested to archieve again, the above Error 1 was not found, but the rest of 4 Errors were still found. According to the above Forum (msg on 2014-2-27 7:52), the Error 5 (Message no. W4134) is a warning and will be fixed AFTER the other Errors have been fixed. Is it correct ?

Q3) Anyway, could you advise how to solve the above Errors 2-5 ?

Ref. SAP Note 900537 –

For Error 3 (W4031) - Plant is assigned to the valuation area:

The material cannot be archived for this valuation area since the material is still used in dependent tables. Delete these dependencies. You can then archive the material for the valuation area. This message is created when the MARC entry for valuation area has a check error, but there is no check error for the assigned MBEW entry.

Actually no exact solution on the above info. ?

For Error 4 (W4107) - Internal use of the material:

First, error message W4107 indicates that the material is used as an internal material for another material. Go to table MARA for this material and check fields BMATN and MFRPN.

Please call the function 'MG_BEZUG_MARA_CHECK' with the material and it should give you back a flag, if article is used or not

Also it can be possible that the material is used in table fields

MARA-PMATA

MARA-PMATN

MARC-NFMAT

MARC-STDPD

MARA-BMATN

MVKE-PMATN

Does it mean that we have to write program to call function 'MG_BEZUG_MARA_CHECK' to fix this error ?

For Error 5 (W4134) - Dependent material master data still exists:

Please refer note 561972. Also delete the routings / BOMs / PO for these Materials.

For the note 561972, does it mean that we have to apply Correction “SAP_APPL” ? If so, which Correction no. is suitable for ERP 2005 ? If the above Q2 is correct, is it still required to apply this Correction ?

Looking forward to hearing from your reply.

Many Thanks,

KH Fong

Accessing the aged data

Business Data is accessed quite frequently in the beginning of its lifecycle, when the business processes are still active. After sometime the data may not be accessed at all during the normal business operations. However, there may be instances wherein these old data become relevant for access, during an audit or analytical reports. Data aging characterizes the mechanism through which the operationally relevant data (known as current data) is kept in the in-memory and data that is no longer accessed in normal operations (known as historical data) stored in the disk space. In data aging the data temperature is used to horizontally partition the application data for optimizing the resource consumption and performance.

When the data is aged the aged data resides in the cold/historical area of the HANA database and the remaining data resides in the hot/ current area of the database. In this article, we discuss the data access behavior of the aged and non-aged data.

When the data is accessed from ABAP, only HOT/ Current data is retrieved by default. This is done in order to optimize the memory footprint when the data is accessed. In most of the use cases, the default behavior will suffice. However there are certain exceptions where the historical data access is justified.

The decision whether to access cold data or not should be derived from business criteria rather than using an aging specific UI control in the screens.

Core Classes

The following classes provide the necessary methods to access the aged data.

• CL_ABAP_SESSION_TEMPERATURE
• CL_ABAP_STACK_TEMPERATURE

We will examine the class methods and usage with a business example below. Please remember that, the data aging strategy should be in accordance with the data access pattern.

CL_ABAP_SESSION_TEMPERATURE

This class enables the data temperature to be set for the entire internal ABAP session. The temperature is then inherited by further calls in the in the call stack.

If a call stack is created (e.g. by calling a class method in a report), the temperature is inherited by the called units.

The below given diagram explains this behavior.

In the above diagram, the main program sets the temperature to be COLD with CL_ABAP_SESSION_TEMPERATURE. This temperature is inherited by all the modules (represented here as function modules).

CL_ABAP_STACK_TEMPERATURE

This class enables the ABAP session temperature (including the default Hot that is set implicitly) to be overwritten within procedures (FORM, FUNCTION or METHOD).

In the above diagram, the main program sets the temperature as COLD using CL_ABAP_SESSION_TEMPERATURE. However, in one of the calling modules (Func.Module3) the temperature is changed to HOT/Current using CL_ABAP_STACK_TEMPERATURE. This temperature (HOT) is valid only in the module in which it is set. i.e; in Func.Module3. Once the control is out of this module, the globally assigned temperature gets validity.

Both the classes mentioned above provide different methods which helps in accessing the aged data. Two of the prominent methods are

• SET_COLD
• SET_TEMPERATURE

Difference between SET_COLD and SET_TEMPERATURE

The diffference between the SET_COLD and SET_TEMPERATURE is described in the diagram below. As is visible in the diagram, the SET_COLD will load the whole data in the COLD/Historical area in to the memory. When SET_TEMPERATURE is used, only the partitions relevant are loaded in to the memory.

Example

Let’s look at the sales order selection program as an example. The selection screen is as given below.

As mentioned before, the data selection need to be based on business logic rather than the hot/cold flag.

The “open” sales orders are mainly accessed/updated quite frequently and they should reside in the hot/current area and should not be aged. The following screen explains the data access behavior when the hot/current data is retrieved. The default data access is always HOT/Current.

Screenshot: For Open sales orders, there is no need to look in COLD/Historical Area

However when it comes to the closed orders, these could be in HOT/Current or could be in COLD/Historical area depending on the aging run frequency. When the data need to be accessed from COLD, the coldness could be set using the CL_ABAP_SESSION_TEMPERATURE as given below.

Alternatively, the CL_ABAP_STACK_TEMPERATURE could also be used as given below to do the data access from COLD/Historical area.

Follow us @SAPILMfor more news and information on data aging.

Dear Experts,

My problem is related to the following Forums -

http://scn.sap.com/thread/3505830

http://scn.sap.com/thread/3875362

Found problem on archieving Material Document (Object: MM_MATBEL) as below -

After inputting the following 4 Mat docs. in "Write" variant and executing in "Test Mode",

Found only two Mat docs. in the log. The Mvt Type of these two Mat docs. is 601.

Even if inputting the two missing Mat docs. only in the "Write" variant to test archieving, no detailed log was found as below. The Mvt Type of these two Mat docs. is 101.

Could you advise reason & how to solved this problem ?

Tks,

KH Fong

Hi,

Archiving of MM_EBAN considering the majority of records but for some purchase requisites i am getting the message like "reference order not yet completely archived" . I have checked the customization, residence time everything is correct but still records are not considered for archiving.

Could you please provide some information on how i can archive such purchase requisites.

find the screen shot for reference.

Thanks & Regards,

Ningappa

Hi

We are using report RSPO1043 for controlling the growth of  TST03 table with the following criteria

Delete old write locks --checked

only list inconsistencies--Unchecked

Delete after runs --06

Can we consider to implement RSPO1041  also ? There is no standard archiving object for this? Can we do custom archiving for TST03?

Thank You