R/3(DB tables) and BW cube reconciliation

1) SOURCE
3 tables are there GLPCA , BSEG , BKPF .We are getting company code , GL , Local Currency and Group Currency from these tables .
TARGET
BW cube (Profit center cube)
Can please somebody suggest how to reconcile the datas between the SOURCE and TARGET.
Thanks
Suraj

Hi haritha
I need to compare the following characteristics :
company code
gl Account
Local currency
group currency
with the key figure values(Between the remote cube and the basic cube ).
I have created the 2 restricted key figure (which stores the respective values
from different infoproviders) ..and finally i have made a calculated key figure which
does the difference of the 2 restricted key figures i have created ...
Now if the value of the calculted key figure is 0 then fine if not then show the exeption (how do i implement this OR what should i put in the "from" and "to" fields in the exception for the calculted key figure)..
Thanks
Suraj

Similar Messages

How to create solved fact table and corresponding cube

Hello,
I want to create cube with solved fact table. It means, i need to feed data for higher levels of dimension also from fact table instead of aggreting from base level.
I am using star schema and AWM 10g R2 for creating cube.
If anyone knows how to do this, i would be very benificial.
Thanks
Subash

I have generated parent child script using cwm2_olap_pc_transform.create_script. After running this generated script, it has created 3 table/view.
My Base Parent Child table is like this:-
drop table PARENT_CHILD;
create table PARENT_CHILD (PARENT varchar2(30), CHILD varchar2(30));
insert into PARENT_CHILD values ('Eligible', 'Compliant');
insert into PARENT_CHILD values ('Eligible', 'Non-Compliant');
insert into PARENT_CHILD values ('All', 'Eligible');
insert into PARENT_CHILD values ('All', 'Ineligible');
insert into PARENT_CHILD values (null, 'All');
After running generated script thru cwm2_olap_pc_transform.create_script, it has created :-
Table - PARENT_CHILD_SOLVED
View - PARENT_CHILD_SOLVED_view , PARENT_CHILD_view
This script also inserted data in above table/view. (5 rec in each). Table/View structure is like this:-
SQL> desc PARENT_CHILD_view
Name Null? Type
GID NUMBER
CHILD1 VARCHAR2(30)
CHILD2 VARCHAR2(30)
CHILD3 VARCHAR2(30)
Data:-
0 All Eligible Compliant
0 All Eligible Non-Compliant
1 All Eligible
1 All Ineligible
3 All
SQL> desc PARENT_CHILD_SOLVED
Name Null? Type
GID NUMBER
CHILD1 VARCHAR2(30)
CHILD2 VARCHAR2(30)
CHILD3 VARCHAR2(30)
Data:-
0 All Eligible Compliant
0 All Eligible Non-Compliant
1 All Eligible
1 All Ineligible
3 All
SQL> desc PARENT_CHILD_SOLVED_view
Name Null? Type
GID NUMBER
SHORT_DESCRIPTION VARCHAR2(30)
LONG_DESCRIPTION VARCHAR2(30)
CHILD1 VARCHAR2(30)
CHILD2 VARCHAR2(30)
CHILD3 VARCHAR2(30)
Data:-
0 Compliant Compliant All Eligible Compliant
0 Non-Compliant Non-Compliant All Eligible Non-Compliant
1 Eligible Eligible All Eligible
1 Ineligible Ineligible All Ineligible
3 All All All
I tried to create dim and cube based on this. I am not sure whether its correct or not! Though validate_dimension API call shows that it is valid.
Script for Dim:-
DECLARE
-- variable to hold error message
errtxt varchar(60);
BEGIN
-- To be on safer side just drop dimension before creating new one and catch exceptions
BEGIN
cwm2_olap_dimension.drop_dimension('APPS', 'HCP_DIM_PC');
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('Dimension HCP_DIM_PC not dropped');
END;
cwm2_olap_dimension.create_dimension(
'APPS',
'HCP_DIM_PC',
'Parent Child',
NULL,
'Parent Child',
'Parent Child',
NULL);
cwm2_olap_dimension_attribute.create_dimension_attribute(
'APPS',
'HCP_DIM_PC',
'Short Description',
'Short Description',
'Short Description',
'Short Description',
TRUE);
cwm2_olap_dimension_attribute.create_dimension_attribute(
'APPS',
'HCP_DIM_PC',
'Long Description',
'Long Description',
'Long Description',
'Long Description',
TRUE);
cwm2_olap_dimension_attribute.create_dimension_attribute(
'APPS',
'HCP_DIM_PC',
'Grouping ID',
'Grouping ID',
'Grouping ID',
'Grouping ID',
TRUE);
cwm2_olap_hierarchy.create_hierarchy(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'Standard',
'Standard',
'Standard Parent Child Hierarchy',
'SOLVED LEVEL-BASED');
cwm2_olap_dimension.SET_DEFAULT_DISPLAY_HIERARCHY ('APPS', 'HCP_DIM_PC', 'HCP_DIM_PC_HIER');
cwm2_olap_level.create_level(
'APPS',
'HCP_DIM_PC',
'ALL_PARENT_LVL',
'All Parent Child',
'All Parent Child',
'All Parent Child',
'All Parent Child Level');
cwm2_olap_level_attribute.create_level_attribute(
'APPS',
'HCP_DIM_PC',
'Short Description',
'ALL_PARENT_LVL',
'Short Description',
'Short Description',
'Short Description',
'Short Description',
TRUE);
cwm2_olap_level_attribute.create_level_attribute(
'APPS',
'HCP_DIM_PC',
'Long Description',
'ALL_PARENT_LVL',
'Long Description',
'Long Description',
'Long Description',
'Long Description',
TRUE);
cwm2_olap_level_attribute.create_level_attribute(
'APPS',
'HCP_DIM_PC',
'Grouping ID',
'ALL_PARENT_LVL',
'Grouping ID',
'Grouping ID',
'Grouping ID',
'HTB Grouping ID',
TRUE);
-- Add all levels one by one to dimension hierarchy. For top most level last parameter is null.
cwm2_olap_level.add_level_to_hierarchy(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
NULL);
BEGIN
cwm2_olap_table_map.removemap_dimtbl_hierlevel(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL');
cwm2_olap_table_map.removemap_DimTbl_HierLevelAttr(
'APPS', 'HCP_DIM_PC', 'Short Description', 'HCP_DIM_PC_HIER', 'ALL_PARENT_LVL', 'Short Description');
cwm2_olap_table_map.removemap_DimTbl_HierLevelAttr(
'APPS', 'HCP_DIM_PC', 'Long Description', 'HCP_DIM_PC_HIER', 'ALL_PARENT_LVL', 'Long Description');
cwm2_olap_table_map.removemap_DimTbl_HierLevelAttr(
'APPS', 'HCP_DIM_PC', 'Grouping ID', 'HCP_DIM_PC_HIER', 'ALL_PARENT_LVL', 'Grouping ID');
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('Level map for ALL_PARENT_LVL not removed');
END;
-- Map ALL_PARENT_LVL level to dimension table. Last parameter is null since it is top most level
cwm2_olap_table_map.map_dimtbl_hierlevel(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'GID',
NULL);
-- one by one map all the level attributes to respective columns in the dimension table.
cwm2_olap_table_map.Map_DimTbl_HierLevelAttr(
'APPS',
'HCP_DIM_PC',
'Short Description',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'Short Description',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'SHORT_DESCRIPTION');
cwm2_olap_table_map.Map_DimTbl_HierLevelAttr(
'APPS',
'HCP_DIM_PC',
'Long Description',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'Long Description',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'LONG_DESCRIPTION');
cwm2_olap_table_map.Map_DimTbl_HierLevelAttr(
'APPS',
'HCP_DIM_PC',
'Grouping ID',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'Grouping ID',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'GID');
-- Use cwm2_olap_validate.validate_dimension to validate the dimension
cwm2_olap_validate.validate_dimension('APPS', 'HCP_DIM_PC');
cwm2_olap_metadata_refresh.mr_refresh;
-- Rollback if any exception occurs during processing this script
EXCEPTION
WHEN OTHERS THEN
cwm_utility.dump_error;
errtxt := cwm_utility.get_last_error_description;
dbms_output.put_line('ERROR: ' || errtxt);
ROLLBACK;
RAISE;
END;
Script for Cube:-
declare
HCP_time_dim number;
errtxt varchar(60);
begin
cwm_utility.collect_garbage;
begin
cwm2_olap_cube.drop_cube('APPS', 'HCP_PC_CUBE');
exception
when others then
dbms_output.put_line('No HCP_PC_CUBE to drop');
end;
begin
cwm2_olap_catalog.drop_catalog('HCP_PC_CAT');
exception
when others then
dbms_output.put_line('No HCP_PC_CAT to drop');
end;
CWM2_OLAP_CUBE.Create_Cube('APPS', 'HCP_PC_CUBE', 'Parent Child Cube', 'Parent Child Cube','Parent Child Cube');
cwm2_olap_cube.add_dimension_to_cube('APPS', 'HCP_PC_CUBE','APPS', 'HCP_DIM_PC');
cwm2_olap_measure.create_measure('APPS', 'HCP_PC_CUBE', 'HCP_PC_MEASURE', 'PC Measure','PC Measure', 'PC Measure Fact');
cwm2_olap_table_map.map_facttbl_levelkey('APPS','HCP_PC_CUBE','APPS','HCP_PC_FACT','ET', 'DIM:APPS.HCP_DIM_PC/HIER:HCP_DIM_PC_HIER/GID:GID/LVL:ALL_PARENT_LVL/COL:CHILD3;');
cwm2_olap_table_map.Map_FactTbl_Measure('APPS', 'HCP_PC_CUBE','HCP_PC_MEASURE', 'APPS', 'HCP_PC_FACT', 'MEASURE_COL', 'DIM:APPS.HCP_DIM_PC/HIER:HCP_DIM_PC_HIER/GID:GID/LVL:CHILD3/COL:SHORT_DESCRIPTION;');
cwm2_olap_catalog.create_catalog('HCP_PC_CAT', 'Parent Child Catalog');
cwm2_olap_catalog.add_catalog_entity('HCP_PC_CAT', 'APPS', 'HCP_PC_CUBE', 'HCP_PC_MEASURE');
cwm2_olap_validate.validate_cube('APPS', 'HCP_PC_CUBE','DEFAULT','YES');
cwm2_olap_metadata_refresh.mr_refresh;
exception
when others then
cwm_utility.dump_error;
errtxt := cwm_utility.get_last_error_description;
dbms_output.put_line('ERROR: ' || errtxt);
rollback;
raise;
END;
My Fact Table is :-
DROP TABLE HCP_PC_FACT CASCADE CONSTRAINT;
CREATE TABLE HCP_PC_FACT (
SHORT_DESCRIPTION VARCHAR2(30) NOT NULL,
GID NUMBER NOT NULL,
CHILD1 VARCHAR2(30) NOT NULL,
CHILD2 VARCHAR2(30) ,
CHILD3 VARCHAR2(30) ,
MEASURE_COL NUMBER NOT NULL);
Data in Fact Table:-
insert into HCP_PC_FACT values('Compliant',0,'All','Eligible','Compliant', 100);
insert into HCP_PC_FACT values('Non-Compliant',0,'All','Eligible','Non-Compliant', 200);
insert into HCP_PC_FACT values('Eligible',1,'All','Eligible',null, 300);
insert into HCP_PC_FACT values('Ineligible',1,'All','Ineligible',null, 400);
insert into HCP_PC_FACT values('All',3,'All',null,null, 500);
I am not sure how to create level, level attr, dim attr for such dim.
All CWM2 validation API shows that my all dims, cubes are valid but when I try to create presentation thru JDev it hangs after selecting Parent-Child Measure.
Any complete working exapmle will be helpful.
P.S. One more query I have can we have one solved and one un-solved dim in the same cube/measure?
regds
Prakash

Updating Physical Cube Tables and Hierarchies OBIEE 11.1.1.7

OBIEE 11.1.1.7
I have imported a MSAS Cube, modeled it and created a presentation layer. I now have some new hierarchies I need to add to the phyicial layer.
How do you import new Cube Tables and/or Hierarchies?
When I select the Import option it creates a new OLAP database and connection pool, I am unable to successfully move those changes into the existing OLAP Connection.
I have been through the documentation and it reccomends importing over a manual process. However I am unable to figure out how to do this with the import process.
Oracle® Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition
11g Release 1 (11.1.1) Part Number E10540-05
Chapter 8 Working with Physical Tables, Cubes, and Joins
There is a section called Working with Multidimensional Sources in the Physical Layer, in this section is says
"Each multidimensional catalog in the data source can contain multiple physical cubes. You can import the metadata for one or more of these cubes into your Oracle BI repository. Although it is possible to create a cube table manually, it is recommended that you import metadata for cube tables and their components"
The New Utilities feature(s) is really cool, but it doesn't work for OLAP connections.
Any help is greatly appreciated.

Hi Michael,
it works, but its a bit tricky. I did it with Oracle OLAP and I think it must be similar with other OLAP Databases.
Rename your existing Database in Physical Layer to the name Metadata Import dialog would create. With Oracle OLAP the "Data Source Name" ist used. Just try it once.
Unfortunately you can not merge dimensions and cubes as it is with relational Objects . So you have to delete the cube and dimensions you will import from you renamed Database in Physical Layer. Of course the mapping between physical and business model will be lost
Now you can import your modified OLAP-Cubes and Dimensions and it should be placed in your renamed Database in Physical Layer
Open the sources of your logical tables in business model and add the Dimensions or Cubes in the "General" Tab. Move to the Tab "Column Mapping" and check if mapping is OK. If not (this will be the case, if you customized the column names), you have to do the mapping from the scratch .
I recommend to use the original names from the data source. If you need another name for a column, just create a new logical column and use "Derive from existing columns". Now you can reimport OLAP Metadate quicker because the Mapping is done automatically.
Hope this helps
Regards Claus

Are fact tables and cubes same in OWB?

Dear all
A simple question. How can I create a star schema (that is, with a fact table and dimensions) using OWB?
OWB has options to create cubes, but as per my understanding a cube is not a fact table.
Cube contains pre-computed data where as fact table contains normal data with references to dimensions.
Please correct me if I am wrong.
thanks in advance

These are just different levels of abstraction.
"Cube" is the highest level of abstraction referring to the overall package of data.
"Star schema" is how cubes are modelled showing the relationships from a fact entity to the dimension entities.
Relational and OLAP are different methods of physical implementation.
In OWB, to promote sharing of dimensions across cubes to avoid inconsistency the idea is you define and build the dimensions independently. Then you define the "cubes" as measures and references to the dimensions. When you build the "cube" you pass in business identifiers from the source data which OWB will use to link the measures to the applicable dimension data. Due to the wonders of inner joins anyone reading the "cube" will only see dimension data related to the data in that cube!
Using OWB you do not need to be concerned with the physical implementation when you use the dimension and cube operators as those operators know what to do.

How to find datasource and standard cube for given R/3 table

Hi All,
Can anyone help me that how to find a datsource, standard cube and Standard BI reports for given R/3 table.
For example if am having the table names "EKKO (Header)
EKPO (Line item)
EKET (Schedule Lines)
EKBE (PO History)
EKKN (Account Assignment/WBS)
EKAN/EKPA (Partner Info)" for all these tables how can i find the standard datasource and standard Cube.
Please help in this. I will assign the points.
Regards,
Shanthi

https://wiki.sdn.sap.com/wiki/display/BI/BWSDMMFIDATASOURCES
MM
Data Sources Tables
Purchasing
2LIS_02_SCL EKKO, EKBE, T001, T001W, EKET, EKPA.
2LIS_02_HDR EKKO, EKBE, T001, EKPA.
2LIS_02_ITM EKKO, EKBE, T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K, T147
2LIS_02_SCN EKET, EKES, EKPO.
2LIS_02_CGR EKBE, EKES, EKPO.
2LIS_02_SGR EKET, EKBE, KKPO
Inventory
2LIS_03_BX stock tables, MCHA, MARA, T001, T001W, CALCULATED FROM MBEW, EBEW, QBEW.
2LIS_03_BF MSEG, MBEW, MKPF.
2LIS_03_UM BKPF, MBEW, QBEW, EBEW, BSEG.
MM
Purchasing   Datasources
ODS
0PUR_O01 2LIS_02_ITM, 2LIS_02_SGR, 2LIS_02_CGR, 2LIS_02_SCN.
0PUR_O02 2LIS_02_HDR, 0PUR_O01
0PUR_DS03 2LIS_02_SCL and 2LIS_02_SGR.
CUBE
0PUR_C10 2LIS_02_SCL and 2LIS_02_SGR.
0PUR_C07
0PUR_C08
0PUR_C09 0PUR_O02, 80PUR_O01, 2LIS_02_HDR
0SRV_C01 2LIS_02_S174
0PUR_C04 2LIS_02_S011, 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR
0PUR_C01 2LIS_02_S012, 2LIS_02_ITM, 2LIS_02_SCL
0PUR_C02 2LIS_02_S013
0PUR_C05 0MM_PUR_VE_01
0PUR_C06 0MM_PUR_VE_02
0PUR_C03 2LIS_02_S015
Inventory Management
CUBE
0IC_C03 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM
0IC_C02 2LIS_03_S195, 2LIS_03_S197
0IC_C01 2LIS_03_S196, 2LIS_03_S198
SD
Data sources Tables
2LIS_11_VAKON VBUK, VBUP, VBAK, VBAP, VBKD, KOMV, T001.
2LIS_11_VAHDR VBAK, VBUK, T001
2LIS_11_VAITM VBAP, VBUP, VBAK, VBKD, VBAJP, T001, VBUK, PRPS.
2LIS_11_VASCL VBAP, VBUP, VBAK, VBEP, VBKD, T001, PRPS
2LIS_11_VASTH VBUK
2LIS_11_VASTI VBUP, VBUK
2LIS_11_V_ITM VBAP, VBAK, VBKD, VBUP, T001, PRPS, VBUK.
2LIS_11_V_SCL VBUP, VBEP, VBKD, VBAP, VBAK, T001, PRPS.
2LIS_11_V_SSL VBAP, VBEP, LIPS, WVBEP, VBUP
2LIS_13_VDKON VBUK, VBRP, KOMV, T001, VBRK.
FI
DATASOURCES Tables
Cost Center Accounting
0CO_OM_CCA_1 COSP, COSS
0CO_OM_CCA_2 COSP, COSS
0CO_OM_CCA_3 COSL, COKL.
0CO_OM_CCA_4 COSR
0CO_OM_CCA_5 COSB
0CO_OM_CCA_6 COOMCO
0CO_OM_CCA_7 BPJA, BPPE.
0CO_OM_CCA_8 COST, TKA07,COOMCO, CSLA, COST, COKL.
0CO_OM_CCA_9 COVP (COEP& COBK), COSP, COST, COEJ, COEP, T001.
0CO_OM_CCA_10 COOI, COSP_VTYPE.
Product Cost Controlling
0CO_PC_PCP_01 KEKO, TCKH3, TCKH8.
0CO_PC_PCP_02 KEKO, TCKH3.
0CO_PC_PCP_03 CKIS, T001K, TKA02, KEKO, MARA, MBEW.
0CO_PC_PCP_04 CKIS, T001K, TKA02, KEKO, MBEW, MARA
0CO_PC_01 AUFK, AFPO, COSS, COSP, COSB, COSL, COKEY, TKA09, TKV09
0CO_PC_02 AUFK, AFPO, COSS, COSP, COSB, COSL, COKEY, TKA09, TKV09
Hope this Helps.

What are the tables and fields in fico & sd module

what are the tables and fields in fico & sd module

Hi,
<b> Sales and Distribution:</b>
Customers KNA1 General Data
KNB1 Customer Master Co. Code Data (payment method, reconciliation acct)
KNB4 Customer Payment History
KNB5 Customer Master Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data (credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Partner Function key
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link
Sales Documents VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document Header Data
VBKD Sales Document Business Data
VBUP Item Status VBAP Sales Document Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records
SD Delivery DocumeLIPS Delivery Document item data, includes referencing PO
LIKP Delivery Document Header data
Billing Document VBRK Billing Document Header
VBRP Billing Document Item
SD Shipping Unit VEKP Shipping Unit Item (Content)
VEPO Shipping Unit Header
<b>Financial Accounting</b>
FBAS             Financial Accounting Basis
BKPF             Accounting Document Header              BUKRS / BELNR / GJAHR
BSEG             Accounting Document Segment             BUKRS / BELNR / GJAHR / BUZEI
BSIP             Index for Vendor Validation of Double   BUKRS / LIFNR / WAERS / BLDAT /
                 Documents                               XBLNR / WRBTR / BELNR / GJAHR / BUZEI
BVOR             Inter Company Posting Procedure         BVORG / BUKRS / GJAHR / BELNR
EBKPF            Accounting Document Header (docs from   GLSBK / BELNR / GJHAR / GLEBK
                 External Systems)
FRUN             Run Date of a Program                   PRGID
KLPA             Customer / Vendor Linking               NKULI / NBUKR / NKOAR / PNTYP
                                                         / VKULI / VBUKR / VKOAR
KNB4             Customer Payment History                KUNNR / BUKRS
KNB5             Customer Master Dunning Data            KUNNR / BUKRS / MABER
KNBK             Customer Master Bank Details            KUNNR / BANKS / BANKL / BANKN
KNC1             Customer Master Transaction Figures     KUNNR / BUKRS / GJHAR
KNC3             Customer Master Special GL Transactions KUNNR / BUKRS / GJAHR / SHBKZ
                 Figures
LFB5             Vendor Master Dunning Data              LIFNR / BUKRS / MABER
LFBK             Vendor Master Bank Details              LIFNR / BANKS / BANKL / BANKN
LFC1             Vendor Master Transaction Figures       LIFNR / BUKRS / GJHAR
LFC3             Vendor Master Special GL Transactions   LIFNR / BUKRS / GJHAR / SHBKZ
                 Figures
VBKPF            Document Header for Document Parking    AUSBK / BUKRS / BELNR / GJHAR
FBASCORE         Financial Accounting General Services Basis
KNB1             Customer Master (Company Code)          KUNNR / BUKRS
LFA1             Vendor Master (General Section)         LIFNR
LFB1             Vendor Master (company Code Section)    LIFNR / BUKRS
SKA1             G/L Account Master (Chart of Accounts) KTOPL / SAKNR
SKAT             G/L Account Master (Chart of Accounts SPRAS / KTOPL / SAKNR
                 Description)
MAHNS            Accounts Blocked by Dunning Selection   KOART / BUKRS / KONKO / MABER
MHNK             Dunning Data (Account Entries)          LAUFD / LAUFI / KOART / BUKRS /
                                                         KUNNR / LIFNR / CPDKY / SKNRZE /
                                                         SMABER / SMAHSK / BUSAB
FI-GL-GL (FBS)   General Ledger Accounting: Basic Functions- G/L Accounts
SKAS             G/L Account Master (Chart of Accounts SPRAS / KTOPL / SAKNR / SCHLW
                 Key Word list)
SKB1             G/L Account Master (Company Code)       BUKRS / SAKNR
FI-GL-GL (FBSC) General Ledger Accounting: Basic
                 Functions - R/3 Customizing for G/L Accounts
FIGLREP          Settings for G/L Posting Reports        MANDT
TSAKR            Create G/L account with reference       BUKRS / SAKNR
FI-GL-GL (FFE)   General Ledger Accounting: Basic
                 Functions - Fast Data Entry
KOMU             Account Assignment Templates for G/L    KMNAM / KMZEI
                 Account items
FI-AR-AR (FBD)   Accounts Receivable: Basic Functions - Customers
KNKA             Customer Master Credit Management :     KUNNR
                 Central Data
KNKK             Customer Master Credit Management :     KUNNR / KKBER
                 Control Area Data
KNKKF1           Credit Management : FI Status data      LOGSYS / KUNNR / KKBER / REGUL
RFRR             Accounting Data A/R and A/P           RELID / SRTFD / SRTF2
                 Information System
FI-BL-PT         Bank Accounting: Payment (BFIBL_CHECK_D) Transactions General Sections
PAYR             Payment Medium File                     ZBUKR / HBKID / HKTID / RZAWE /
                                                         CHECT
PCEC             Pre-numbered Check                      ZBUKR / HBKID / HKTID / STAPL
FI-BL-PT-AP(FMZA)Bank Accounting: Payment Transactions Automatic Payments
F111G            Global Settings for Payment Program for MANDT
                 Payment Requests
FDZA             Cash Management Line Items in Payment   KEYNO
                 Requests
PAYRQ            Payment Requests                        KEYNO
Hope this solves your concern...
Regards,
Habeeb
Assign points if helpful

How to find rows in F table of a cube for a given request ID

Can someone tell me how to find the rows in the F table of a cube for a given request id?

Hi,
Copy the Request ID number of that cube and go to manage of the cube and select contents tab, select Infocube content,
select list of objects to be displayed with results and in that screen give Request ID at Request ID row and at bottom Max no. of Hits keep blank and execute at the top.
this will display all the data rows loaded with that request. this is records from cube.
from Fact table, go to SE11, give /BIC/FXXXX "XXXX" is cube name for custom cube.
get the SID of that cube from the Cube contents as mentioned above, for field select for output along with Request ID select Request SID also.
from SE11 give table /BIC/DXXXXXP "XXXX" is cube name for custom cube. P for Packet Dimension. here pass reqest SID in 'SID_0REQUID' and get value for DIMID.
pass this DIMID into KEY_XXXXP, this give the fact table rows for that request DIM ID.
hope this helps
Regards
Daya Sagar

How to combine multiple fact tables and dimensions in one worksheet?

Hello Forum,
I am encountering a reporting problem when trying to create a worksheet that uses more than one cube/fact table and common dimensions. I have used Oracle Warehouse Builder 10Gr2 to design and deploy a pretty simple ROLAP data mart. We are using Discoverer Plus for OLAP as our reporting tool. We have 5 dimension tables using a star schema and 3 fact tables, when I create the worksheet I bring in our sales measure from our sales item table and then Store_Name from my Stores Dimension and then day from my time dimension, everything looks good at the stage, we're just trying to get a sum of all sales for that store on that day. Then I bring in a measure from our advertising cost table and a join window pops up asking which join to use, if I choose either the Store or the Time dimension I get correct data for the first fact table (sales) and grossly incorrect data for the ad cost measure from the second fact table (advertsing costs)...... any help would be appreciated

You have encountered one of the key limitations of Discoverer... which I complained about to the Discoverer product manager at OpenWorld in 2001....
Anyhow, to get around this, you are going to have to deal with it either in the database, (views, materialized views, tables), or within the admin tool by creating a custom folder.
Discoverer also calls this the "fan trap", but never really had a solution to the problem. [The solution only worked is you joined to one and only one dimension!]
What you want (using Sales_Fact and Inventory_Fact as an example) is to join Sales to Time, Store, and Product, and save that result. Then join Inventory to Time, Store, and Product, save that result, then do a double outer join between the two intermediate temporary tables in order to calculate something useful like inventory turns by store and product line.
This is also known a "multipass SQL", and is supported by some (but not many) other tools.
So, to accomplish this with Discoverer, you'll either need to create a view, or table, or materialized view that has already put Sales and Inventory into a single (virtual?) fact table. Alternatively you can write the SQL for how to do this linkage (don't forget to handle missing data), and use the Discoverer admin tool to create a custom folder that uses your SQL.
Hope this helps!

Validity table for stock cube

hi,
I am designing a stock cube with non-cumulative values.
Data for amounts of stock movements I plan to get from Transfer Order documents.
Data will be extracted on daily basis and in cube I want to have among others following chars: quant, storage bin, storage type and warehouse nr.
I would like to include in validity table such all of chars mentioned above (i.e. quant, storage bin, storage type, warehouse nr and date).
I am wondering is it ok to include so many chars in this table. Are there any guidelines for designing this table?
Can you suggest any documentation?
Regards,
Andrzej

You can use RSDG_CUBE_VALT_MODIFY report for this.
See:
http://help.sap.com/saphelp_bw31/helpdata/en/02/9a6a1c244411d5b2e30050da4c74dc/content.htm
Also take a look on notes:
360249
534865
419490
Regards

Dimension Table and Fact Tables

Hi,
Is there any way to see the Dimension Table contents and Fact Table Contents.
For eg:- I should be able to see the DIM ID and the SID's of a Dimension.

Well you can see them in SE11, by giving the table name.
Go to list schema and give the cube name. It will display all the table for that cube. Give the table name in SE11 or SE16 and see the content there.

Tables and Cells - can all corners and cells be rounded?

I need to recreate a form and it requires a lot of round "cubes" thoughout. If these were squares, I would be doing this creating tables and cells but because most everything in it seems to have rounded corners, thats making me question the best way of going about this. Is this possible somehow?

Another way to do it would be to add anchored objects inside your table to mimic the rounded corners as shown in the following screen capture.
The first exemple is relatively easy, needing only one object per cell, except for the top row and the left column which need nothing.
The second one is more difficult, especially for the surroundings which needs more than one anchored object (especially the last cell which inherited five of them).
But both of these are still tables and can be adjusted as needed in width and height.
This could prove usable if you can trust the people doing the editing inside the table and this doesn't mess with the printing.
(the inspiration for abusing tables and anchored objects in this way comes from Michael Murphy).
emmanuel

Merging Multiple fact tables and creating a BIA target

Hi Folks
We are using Dataservices with BIA.
We want to merge mutliple fact table and create a sinvglc cube on BIA.
when we tried to do that we get a error message that we cannot merge multiple fact tables.
any pointers ?
Poonam

You could have the cubes individually on the BIA and then have a multiprovider which you can use..?
or create separate universes on the cubes and then merge the universes in BO and then you could hit the BIA for the same..?

Number of Entries in Dimension Tables and Fact Tables

Hi all,
is there an easy way to check
- the number of entries in the dimension tables
- the number of entries in the fact table?
Thanks a lot
Alex

Hi Alex,
If u want to see the content of Dimension table and Fact table for a infocube then just right click on a particular info cube then select manage . Select coneten tab there , form there u can either select Fact table to see the fact table conten or Infocube content to see the Dimensiontable content.
Regards..

Find list of FACT tables in the cubes

Hi experts,
Pls help me to find list of FACT tables in the cube and Dimension table associated with the Fact table. your answer will be very helpful for me.
Thanks

hi,
Go to Analysis Server (SSMS)-> use
--All Measures
SELECT [CATALOG_NAME] as [DATABASE],
CUBE_NAME AS [CUBE],[MEASUREGROUP_NAME] AS [FOLDER],[MEASURE_CAPTION] AS [MEASURE],
[MEASURE_IS_VISIBLE]
FROM $SYSTEM.MDSCHEMA_MEASURES
WHERE CUBE_NAME ='Adventure Works DW2012'
ORDER BY [MEASUREGROUP_NAME]
You can use below link ;
http://bennyaustin.wordpress.com/2011/03/01/ssas-dmv-queries-cube-metadata/
Thanks

Detailed analysis about the dimension tables of a cube

Hi Experts,
how can I get a detailed analysis about the dimension tables of a cube? (E.g. how many records include the fact tables, dimension tables and how much percent are these records compared with the whole records of the cube?!)
Thx in advance for your answers!

Hi,
You will get most of the information in LISTSCHEMA transaction code. If you want to see further you can see the records in SE11.
Regards
Githen

R/3(DB tables) and BW cube reconciliation

Similar Messages

Maybe you are looking for