nfocube Compression

I was dealing with the tab "compression" while managing the infocube, was able to
compress the infocube and send in the E- table but was unable to find the concrete
answer on the following isssues:

1. What is the exact scenario when we use compression?

2. What actually happens in the practical scenario when we do compression?

3. What are the advantages of compressing a infocube?

4. What are the disadvantages of compressing a infocube?

1. Compression creates a new cube that has consolidated and summed duplicate
information.

2. When you compress, BW does a group by on dimensions and a sum on measures... this
eliminates redundent
information.

3. Compressed infocubes require less storage space and are faster for retrieval of
information.

4. Once a cube is compressed, you cannot alter the information in it. This can be a big
problem if there
is an error in some of the data that has been compressed.

I understand the advantage to compressed the infocube is the performance. But I

have a doubt. If I compressed one or more request ID of my infocube the data it will
continue to appear in my reports (Analyzer)?

The data will always be there in the Infocube. The only thing that would be missing is the
request id's.. you can take a look in to your packet dimension and see that it would be
empty after you compress.

Compression yeap its for performance. But before doing this compression you should
keep in mind one thing very carefully.

1) If your cube is loading data with custom defined deltas you should check whether delta
is happening properly or not, procedure is compress some req and schedule the delta.

2) If your system having outbounds from cube and this happening with request ids then
you need to follow some other procedure because request ids wont be available after
compression.
These two things are very important when you go for compression.

How to Compress InfoCube Data

How Info cube compression is done?

v\:* {behavior:url(#default#VML);}o\:*
{behavior:url(#default#VML);}w\:* {behavior:url(#default#VML);}.shape
{behavior:url(#default#VML);}
Create aggregates for that infocube

-----------------------------------------------------------------------------------

I guess what the question was how we can compress a data inside a cube, I assume that's
usually done through by deleting the Request ID column value.
This can be done through Manage - > Compress Tab.

-----------------------------------------------------------------------------------

Go to RSA1
Under Modeling --> Choose InfoProvider --> InfoArea and then --> Select your
InfoCube

Right Click on your infocube --> from context menu --> choose Manage

Once you are in manager data Targets screen:

Find out the request numbers – decide till what request id you want to compress

Go to Collapse tab – under compress --> choose request ID and click Release

The selected request ID and anything below will be compressed.

What is happening behind the scene is “After the compression, the F fact table contains
no more data.
Instead, the compressed data now appear in the E fact table.”

Cube to Cube Load

You need to move some data from one cube to another.

The steps involved are :-

You need to first create 'Export Data Source' from original cube (right-click on the
InfoCube and select Generate Export Data Source).
Then, assign the new datasource to new cube. (you may click on 'Source system' and
select your BW server and click 'Replicate').

Then, you can configure your infosource, and infopackage.

Lastly, you are ready to load already.

SAP SD Standard InfoCubes and

DataSources
Example of Standard InfoObjects::

0BILLTOPRTY - Bill-to party

0COMP_CODE - Company code

0DISTR_CHAN - Distribution channel

0DOC_CATEG - Sales document category

0PLANT - Plant

0SALESORG - Sales organization

0SALES_GRP - Sales group

0SALES_OFF - Sales office

0SHIP_TO - Ship-to party

0SOLD_TO - Sold-to party

0VERSION - Version

0VTYPE - Value type for reporting

0DIVISION - Division

0MATERIAL - Material number

0SHIP_POINT - Shipping point

0PAYER - Payer
0DOC_CLASS - Document class Order/Delivery/Invoice

0DEB_CRED - Credit/debit postings (C/D)

Example of Key figure Infoobjects:

Key Figures - InfoObject - Description

0SUBTOT_1S - Pricing subtotal 1 from pricing determination procedure in statistics

currency

0SUBTOT_2S - Pricing subtotal 2 from pricing determination procedure in statistics

currency

0SUBTOT_3S - Pricing subtotal 3 from pricing determination procedure in statistics

currency

0SUBTOT_4S - Pricing subtotal 4 from pricing determination procedure in statistics

currency

0SUBTOT_5S - Pricing subtotal 5 from pricing determination procedure in statistics

currency

0SUBTOT_6S - Pricing subtotal 6 from pricing determination procedure in statistics

currency

0OPORDQTYBM - Open order quantity in base unit of measure

0OPORDVALSC - Net open order value in statistics currency.

0DLV_QTY_BM - Actual delivered quantity in base unit of measure

0QUANT_B - Quantity in base unit of measure

0DOCUMENTS - Number of documents

0DOC_ITEMS - Number of document items

0NET_VAL_S - Net value in statistics currency

0COST_VAL_S - Cost in statistics currency

0GR_WT_KG - Gross weight in kilograms

0NT_WT_KG - Net weight in kilograms

0VOLUME_CDM - Volumes in cubic decimeters

0DOCUMENTS - Number of documents (document counter)

It is recommend that you only use the document counter along with characteristics from
the document header (header characteristics). For example, 0SALES_ORG,
0DISTR_CHAN, 0BILLTOPRTY, 0SHIP_TO, 0SOLD_TO, 0PAYER,
0DOC_CATEG. *-- Anuradha

What is meant by Selection field, Hide field, Inversion and Field only Known
exit? What is the Use of these?

by: Anoo

Selection

When scheduling a data request in the BW Scheduler, you can enter the selection criteria
for the data transfer. For example, you may want to determine that data requests are only
to apply to data from the previous month.

If you set the Selection indicator for a field within the extract structure, the data for this
field is transferred in correspondence with the selection criteria in the scheduler.

Hide field

You should set this indicator to exclude an extract structure field from the data transfer.
As a result of your action, the field is no longer made available in BW when setting the
transfer rules and generating the transfer structure.

If you don't want to see this this ..you set this field and you can't see in the BW which is
available in extract structure.

Inversion
The field is inverted in the case of reverse posting. This means that it is multiplied by
(-1). For this, the extractor has to support a delta record transfer process, in which the
reverse posting is identified as such.

If the option Field recognized only in Customer Exit is chosen for the field, this field is
not inverted. You cannot activate or deactivate inversion if this option is set.

Field only known:

The indicator Field known only in Exit is set for the fields in an append structure,
meaning that by default, these fields are not passed to the extractor in the field list and the
selection table.
For Example:

You had posted one record in to the cube. All the key figures are updated (some are
added and some are substracted). But you want to revert it back. So what you can do is
if your data is present in the PSA. You can reverse post that request so that all the signs of
the key figures are reversed( i.e addition becomes minus and minus key figures becomes
additive) so that the net key figure change is nullufied. i.e., total change is Zero. In such
cases, only those key figures which have "inversion" set will be reversed.

Explain the steps to load master data hierarchies from R/3 system.

by: Reddy

A summary of the steps are as follows:

1) Goto Hierachy tab in infobject on to which your loading Hierachy data.

2) Select With Hierarchies.

3) Select Hierarchy Properties ( Time Dependent or not time depen..etc..)

4) Click on External Chars in Hierarchies, in that select the characterstics on which this
Hierarchy is depending.

5) Then Create Infosource, assign Datasource.

6) Create Infopackage, to load Hierarchies.

7) Hierarchy section tab in Infoapackage select load Hierarchy and refersh the Available
Hierarchies from OLTP, If it is Time dependent select time interval in update tab.

8) Then start the load.

If you want to load from Flat file, some what different way to do it.

It is normally done by the following:

Transferring the master datasources in RSA5 to RSA6 and then replicating the DS into
BW and assignment of DS to Infosource and cretaion of Infopackage and load it into the
master tables.

Generally, the control parameters for data transfer from a source system are maintained in
extractor customizing. In extractor customizing, you can access the corresponding source
system in the source system tree of the SAP BW Administrator Workbench by using the
context menu.
To display or change the settings for data transfer at source system level, choose Business
Information Warehouse --> General Settings --> Maintaining Control Parameters for Data
Transfer.

Note: The values for the data transfer are not hard limitations. It depends on the
DataSource if these limits can be followed.
In the SAP BW Scheduler, you can determine the control parameters for data transfer for
individual DataSources. You can determine the size of the data packet, the number of
parallel processes for data transfer and the frequency with which the status IDocs are
sent, for every possible update method for a DataSource.

To do so, choose Scheduler --> DataSource --> Default Settings for Data transfer.

In this way you can, for example, update transaction data in larger data packets in the
PSA. If you want to update master data in dialog mode, smaller packets ensure faster
processing.