Archive Analysis of CO tables using RARCCOA1, RARCCOA2, RARCCOAA and RARCCOAP

When you want to archive CO tables (COEP, COEJ, COSP, COSS, COST), there are several possible archive objects:
  • CO_ALLO_ST
  • CO_CCTR_PL
  • CO_COSTCTR
  • CO_ITEM
  • CO_KSTRG
  • CO_ORDER
  • CO_PROCESS
  • COPA2_*
  • PM_ORDER
  • PP_ORDER
  • PR_ORDER
  • PS_PROJECT
  • RE_RNTL_AG
  • SD_VBAK
In order to choose the best archive object suitable to archive the data in your system, SAP has delivered the following programs:
  • RARCCOA1: Creates data extract for analysis of CO tables for archiving objects: CO_ITEM, CO_PROCESS, CO_KSTRG, RE_RNTL_AG, CO_COSTCTR, PS_PROJECT, CO_ORDER, PP_ORDER, PM_ORDER, PR_ORDER, SD_VBAK, COPA2_*
  • RARCCOA2: Evaluates the data extract from the report RARCCOA1
  • RARCCOAA: For analysis of CO tables for archiving object CO_ALLO_ST.
  • RARCCOAP: For analysis of CO tables for archiving object CO_CCTR_PL.

RARCCOA1 and RARCCOA2

Program RARCCOA1 counts the entries of required CO tables, assigns them explicitly to an archiving object and creates a data extract with the required information.

RARCCOA1 counts the entries of required CO tables

Report RARCCOA2 reads the dataset provided by RARCCOA1 and processes it as appropriate. You receive a list as a result of the analysis in which the number of the entries in these tables is compared with the archiving objects.

RARCCOA2 reads the dataset provided by RARCCOA1

The list first displays a summation of the data generated by program RARCCOA1. You can obtain more information by clicking on the totals line. In addition, you can set filters (for example, only analyze the data for one archiving object in detail), choose other sorting (for example by fiscal year) and change the summation.

The list states how many entries for the respective table and how many entries in the system (column 'ALL') are available in total. It does not inform you which entries can or should actually be archived. The system cannot determine how long you need data or want to retain it in the system.

You should pay particular attention to the following entries in the list:

  • Empty field for "Object" (5th row in the screenshot): there is not an archiving object responsible for these table entries or none is known to the program.
  • Archiving object CO_ITEM (not detected in this screenshot): All line items (COEP, COEJ, ...) can be archived using CO_ITEM. However, you are recommended to take the other cost objects into account as well.
  • Archiving object CO_COSTCTR (1st row in the screenshot): CO_COSTCTR also stands for CO_CCTR_ID, CO_CCTR_PL and CO_CCTR_EP (and CO_ALLO_ST). You have to decide in another step which object should actually be used (see reports RARCCOAP and RARCCOAA). You are recommended not to use archiving object CO_CCTR_ID. Use archiving object CO_COSTCTR to archive actual data.

RARCCOAA

The analysis of CO tables (COEP and COEJ) using this report is recommended particularly when Allocations (assessment, distribution and periodic reposting) are in use and are frequently repeated or reversed. The program calculates how many entries for the chosen tables can be archived in which fiscal years and controlling areas by using archiving object CO_ALLO_ST. It then processes the data calculated and displays it in the form of a list.

RARCCOAP

You are recommended to use this report if actual data must be retained for cost centers but you no longer need planning data. The program reads all entries for the tables chosen (COEJ, COSP, COSS, CPST) and determines which of them can be archived by archiving object CO_CCTR_PL and which selection criteria you can use (fiscal year, controlling area). It then processes the data determined and displays it in the form of a list.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more