Different types of tables........Explain

Hai Gurus,
Explain the following tables and give difference between them...
1. Transparent table
2. Pooled table
3. Cluster table.
Send it immediately very urgent....

Hi,
Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.
Pooled Table : Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables are used to store control data. Several pooled tables can be cominied in a table pool. The data of these pooled tables are then sorted in a common table in the database.
Cluster Table : Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to strore control data. They can also be used to store temporary data or texts, such as documentation.
difference between Standard tables, Pooled tables and Clusterd Tables
A transparent table is a table that stores data directly. You can read these tables directly on the database from outside SAP with for instance an SQL statement.
Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will create in data base and if is basically used to store transaction data.
A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.
One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in Abap are limited as well.
But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool.
All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data.
Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but few (1 to 10) cluster table.
For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table.
A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.
A view is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way the data needs to be represented. You actually call directly upon the underlying tables.
Go through this link
http://web.mit.edu/sapr3/dev/sap_table_types.htm
Regards,
Priyanka.

Similar Messages

Different types of tables and purpose

Hi,
Could someone explain me the different types of tables an what data they store.
Sonali

hi Sonali,
These are the different types of tables in MDM
Flat Tables : It is a simple table consisting of record and fields ( rows and column) .
Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.
Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.
Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
Tables are also Categorized as Object Tables like :
Images : This table is for storing Images
Sounds : This table is for storing Sound File.
Videos : This table is for storing Video Files .
Binary Objects : This table is for storing Binary Objects.
Text Blocks : This table is for storing block of text.
Copy Blocks : This table is for storing block of text interpreted as a Copy.
Text HTML`s : This table is for storing block of text interpreted as a HTML.
PDFs : This table is for storing PDF files.
There are various types of Special Tables , i have mentioned below:
Image Variants : Used to define the structure
and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.
Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.
Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.
Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).
Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.
Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.
Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.
There are various types of System Tables :
Roles : A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.
Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.
Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.
Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.
Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.
Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.
Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.
XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.
Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
In MDM SP06 5.5 we can have only one main table, but in MDM 7.1 version we can maintain many main tables.
Rewards points if helpful
Regards,
Vijay

What are the different types of tables in oracle --plz help

I want to know the different types of tables in orcle...Please help me

There are seven types of tables in Oracle.
1.Heap organized tables
2.Index organized tables
3.Index clustered tables
4.Hash clustered tables
5.Nested tables
6.Global temporary tables
7.Object tables
Source:http://www.adp-gmbh.ch/ora/concepts/tables.html
But if you are asking table types in the uses senses then they are n types :
1.Stage tables
2.Operational tables
3.Functional tables
4.Disposition tables
5.Archive tables
6.Other tables
Source:http://www.databasejournal.com/features/oracle/article.php/3616476/Types-of-Tables-in-Oracle.htm
And yes of course, the complete detail can be found in documentation.
HTH
Girish Sharma

Different types of table nodes?

Ok this is probably a silly question but I have two different kind of of tables. The first looks like 3 columns the first one yellow and the second two are white. This one I build table lines on the table painter and when I add nodes under it I have to create a table line first and it adds the cells under it. This lets me assign text to each cell.
The second type the icon looks like the "creates new session" icon (window with a sun inside of it) This one does not let me make table_lines but does let me create text's nodes directly and then assign what kind of table line under the text nodes output options.
I've gone through all the tabs on both types to see if there is a setting that changes it from one to the other but haven't found anything. The reason I'm asking is because I'm trying to line up some fields on the second type of table but I cant seem to tell the text node which cell to put each field in becuase the second type of table doesn't let me create the table line node under it.
does anyone know how to change a table from one type to the other?
Thanks!

Hi..
If I understood right, the second node is a 'old' table node which is no more used in smartform development, (you can't create one, however changes could be done). You may not convert it to the present Table node but can redefine those logic in new table node.
For some more information regarding OLD table node you can refer the following link:
http://help.sap.com/saphelp_crm50/helpdata/en/d2/69a148cd8b11d3b563006094192fe3/content.htm
Regards,
Karthik
Edited by: Karthik S on Aug 6, 2010 12:00 AM

Different types of tables and modes

Hi Experts
What is the specification of different tables in console and different modes in data manager.
What is the major difference between them.
Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
have fun..
Hari

Hi Hari,
Differnt types of tables in Console are :
Actually the Tables in Console are further categorized as :
Main Table and Sub table which include:
Flat Tables : It is a simple table consisting of record and fields ( rows and column) . In MDM Main table is always a flat table.
Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.
Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.
Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
Tables are also Categorized as Object Tables like :
Images : For storing Images
Sounds : For Sound File.
Videos : For storing Video Files .
Binary Objects : To store Binary Objects.
Text Blocks : To store block of text.
Copy Blocks : Stores block of text interpreted as a Copy.
Text HTML`s : Stores block of text interpreted as a HTML.
PDFs : To store PDF files.
There are various types of Special Tables also:
Image Variants : Used to define the structure
and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.
Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.
Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.
Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).
Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.
Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.
Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.
There are various types of System Tables :
Roles : A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.
Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.
Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.
Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.
Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.
Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.
Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.
XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.
Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Data Manager:
Data Manager in simple terms can be stated as a place where we manage the data that is taken from various systems.
All the data that you take from all the various systems that a business is using is then taken into data manager, so that it could be cleansed and can be maintained easily in future.
There are basically four different modes in Data Manager:
1. Record Mode: This mode allows us to search, view and edit the records of any table in MDM repository. This is the mode that one uses most often, primarily to view and edit records in the main table and also to view and edit records in any of the sub tables.
2. Hierarchy mode. This mode allow us to view and edit the hierarchy tables in the MDM repository, including regular hierarchy tables, taxonomy tables, and the Masks table. Though we can also view and edit the records of a hierarchy table in Record mode, Hierarchy mode specifically allows us to edit the parent/child relationships and the sibling ordering of the hierarchy.
3. Taxonomy mode. This mode allows us to view and edit the taxonomy tables in the MDM repository. We usually use this mode to create and maintain the category hierarchy used in the repository, and to manage the attributes associated with each category and subcategory. Though we can also view and edit taxonomy tables in both Record mode (for searching) and Hierarchy mode (for editing the other fields of information associated with each category), Taxonomy mode is unique in that instead of focusing on the records of the taxonomy table, it allows you to create and manage the pool of attributes associated with the taxonomy table, and to assign attributes to categories on a category-by-category basis.
4. Matching mode. This mode allows us to identify and eliminate duplicate records within an MDM repository. When you view the main table in Matching mode, MDM allows you to perform u201Cmatching-and-mergingu201D on and against any or all of its records, using various user-defined criteria (like creation of Rules and Strategies) to decide whether or not records are potential duplicates.
5. Family mode. This mode allows us to view and edit the Families table, which layers a hierarchy of families upon the taxonomy hierarchy to further break down each category into smaller groups of main table records. We usually use this mode to partition the categories of the taxonomy hierarchy by the values of other fields and/or attributes, and then to associate family data (such as an image, a paragraph, and bullets) once with each family of main table records rather than each individual record.
Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
The structure of the tables are defined in Console and those tables are then used in Data Manager, but if you have defined a table as a Hierarchy table you cannot use that table in Taxonomy Mode but you will be able to see all the tables in Record Mode.
Hope this would be useful...
If useful do reward points!!!!
Regards,
Parul

Different types of tables

Hi Experts,
I found tables- starting with A* (like A004) and S* (like S597) in a program.
I know A* tables are for Pricing conditions and are maintained by SD team.
can you please explain what are S* tables? and who will maintain them.
and also please suggest the other kind of tables, if any.
Thanks,
MK

Hi Sundeep,
actually we are doing system upgration and the table S597 exists in R/3 4.7c
and it is to store the customer stock inventory information.
the tables does not exist in ECC 6.0. so can you please suggest who will be responsible to maintain it in ECC 6.0.
Thanks,
MK

What are the differnet type of tables in mdm ?

hi experts i am new to mdm. just i have refered some documents in that the have created some table and fileds ,taxnomy,lokups,.......
so can any one give me the bref ida on
what is mdm ?
what are the different type of tables in mdm ? What is the requirement for the selection of table?
what is a feld ? what are the diff type of fealds in mdm ? And requriement ?
what is taxnomay ? And Requriement or where or when we can use ?
what is lookups in mdm ? what is lookup tables in mdm ?
what is mdm console ?
what is mdm data manager. ?
what is mdm import manager ?
what is mdm syndicator ?
please any body answer this questions .

Hello Praveen,
Below are the the all possible links of books,articles... etc for MDM.
http://hosteddocs.ittoolbox.com/RD021507b.pdf
demo
http://www.sap.com/community/int/innovation/esoa/demo/MDM_demo/index.html
http://www.asug.com/DesktopModules/Bring2mind/DMX/Download.aspx?TabId=66&DMXModule=370&Command=Core_Download&EntryId=3431&PortalId=0
MDM
http://www.asug.com/DesktopModules/Bring2mind/DMX/Download.aspx?TabId=66&DMXModule=370&Command=Core_Download&EntryId=1666&PortalId=0
SAP Netweaver MDM Overview
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b09b548d-7316-2a10-1fbb-894c838d8079
SAP NETWEAVER MDM Leverage MDM in ERP Environments - An Evolutionary Approach -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4059f477-7316-2a10-5fa1-88417f98ca93
Master Data Management architecture patterns
http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0703sauter/
MDM and Enterprise SOA
http://www.saplounge.be/Files/media/pdf/Lagae---MDM-and-Enterprise-SOA2007.10.10.pdf
Effective Hierarchy Management Using SAP NetWeaver MDM for Retail
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ee0c9e-29a8-2910-8d93-ad34ec8af09b
MDM World
http://mdm.sitacorp.com/
MDM: Master Data for Global business
http://www.sitacorp.com/mdm.html
MDM Master Data Management Hub Architecture
http://blogs.msdn.com/rogerwolterblog/archive/2007/01/02/mdm-master-data-management-hub-architecture.aspx
Improve Efficiency and Data Governance with SAP NetWeaver MDM
http://www.sapnetweavermagazine.com/archive/Volume_03_(2007)/Issue_02_(Spring)/v3i2a12.cfm?session=
Data Modeling i MDM
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d4211fa-0301-0010-9fb1-ef1fd91719b6
http://www.sap.info/public/INT/int/index/Category-28943c61b1e60d84b-int/0/articlesVersions-31279471c9758576df
SRM-MDM Catalog
http://help.sap.com/saphelp_srmmdm10/helpdata/en/44/ec6f42f6e341aae10000000a114a6b/frameset.htm
http://events.techtarget.com/mdm-ent/?Offer=DMwn716mdm
http://viewer.bitpipe.com/viewer/viewDocument.do?accessId=6721869
http://searchdatamanagement.bitpipe.com/data/search?site=sdmgt&cr=bpres&cg=VENDOR&sp=site_abbrev%Asdmgt&cp=bpres&st=1&qt=MasterDataManagement
http://viewer.bitpipe.com/viewer/viewDocument.do?accessId=6721819
http://www.dmreview.com/channels/master_data_management.html
http://searchdatamanagement.techtarget.com/originalContent/0,289142,sid91_gci1287620,00.html?bucket=NEWS&topic=307330
MDM Console -- http://help.sap.com/saphelp_mdmgds55/helpdata/en/88/9f9c427055c66ae10000000a155106/frameset.htm
MDM Import manager --http://help.sap.com/saphelp_mdmgds55/helpdata/en/43/120367f94c3e92e10000000a1553f6/frameset.htm
MDM DataManager --http://help.sap.com/saphelp_mdmgds55/helpdata/en/43/e0615a82b40a2ee10000000a11466f/frameset.htm
MDM Syndicator --http://help.sap.com/saphelp_mdmgds55/helpdata/EN/43/5fe0e8a55f5f6be10000000a1553f6/frameset.htm
Rgds
Ankit

Types of Tables in SAP BI

Gurus,
Could anyone help me to know what are the types of Tables available in SAP BI and what are the different categories we have . I've heard of A, T, P , Q etc.
Could anyone provide me the elobrative information about all the types of tables.
Regards,
Yaseeen

Hi ,
These are the different types of tables in MDM
Flat Tables : It is a simple table consisting of record and fields ( rows and column) .
Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.
Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.
Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
Tables are also Categorized as Object Tables like :
Images : This table is for storing Images
Sounds : This table is for storing Sound File.
Videos : This table is for storing Video Files .
Binary Objects : This table is for storing Binary Objects.
Text Blocks : This table is for storing block of text.
Copy Blocks : This table is for storing block of text interpreted as a Copy.
Text HTML`s : This table is for storing block of text interpreted as a HTML.
PDFs : This table is for storing PDF files.
There are various types of Special Tables , i have mentioned below:
Image Variants : Used to define the structure
and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.
Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.
Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.
Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).
Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.
Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.
Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.
There are various types of System Tables :
Roles : A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.
Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.
Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.
Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.
Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.
Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.
Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.
XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.
Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
for sap tables ..
SAP Tables
hope this helps ..
Regards,
Shikha

Different types of SmartForm Tables?

Hi,
I was explaining the concept of SmartForms to a collegue today and using the standard Invoice SmartForm as an example (LB_BIL_INVOICE) when I was asked a question that has stumped me.
Within the MAIN window, there are 3 TABLES (TABLEITEM, TABLEKOND and DOWNPAY_TABLE). The icons for TABLEITEM and TABLEKOND are different to the icon for DOWNPAY_TABLE. It seems that DOWNPAY_TABLE has an additional tab called "Calculations" while TABLEITEM and TABLEKOND have an "Events" tab.
Whenever I create a new table node, I get a "Calculations" table, and I can't seem to be able to create a "Events" table. Does anyone know how to do this and why we seemingly have these two types of tables?
Cheers,
Confused.

Patrick,
May be you are on 4.7 Version and new addition to table version is Calculation , other tables which you mentioned with Events would have been created in old version. Hence, you are still seeing Events tab not Calculation.
If you have old version 4.6c check and confirm :).
Rgds,
Mano Sri

Problems working with different types of aggregation in two facts table

Hello every Body!! Greetings from Brazil..
At fisrt I'd like to say that I've tried to find some thead with the same problem, but I've foud no answere. That is why I'm typing this new post.
Here we go ...
I've a Fact table with one metric and two degenerate dimensions..
For exemple:
Invoice_number
Puschase_Date
Purchase_Value$
When I model it at Business Model Mapping, I used the Aggregation's type below:
Invoice_number - None
Puschase_Date - None
Purchase_Value - Sum
So far it works fine at Answeres area.. Since I use only values from this Fact..
But... if I try to join values from two different Facts Table (both of them sharing the same Dimensions) and the Second Fact has an aggregated value, it does'nt work... I get 'null' as values (metrics) of the second Fact Table...
I think that it is caused because I'm working whith different types of aggregation, but I don't know the solution.
By the wat, the second Fact I've told has only one metric, aggregated whith 'SUM'.
Is there a solution? Any hint?
Tks.
Vettore

int x = (int)(7 + 3.0 / 4.0 * 2); //the variable will do the math bracket first. then the va type will still be an int because int was never changed.
Following the standard order of operations, 3.0/4.0 will result in a double, then 2 will be converted to a double before being multiplied to the result, then 7 is converted to a double before being added to the result, and then the (int) cast will force a conversion
back to an int.
Console.WriteLine((1 + 1) / 2 * 3); // 1 + 1 will be done first then 1 / 2 then * by 3
Correct.
I THINK THATS ALL WRONG ^ =/ like the comments
Why?

Subroutine that can accept different types of internal tables

Hey guys!
I'm creating a subroutine that takes input and sends it off to be converted but I am getting a syntax error: <tab> is not a STANDARD TABLE. I'm designating it with TYPE ANY TABLE, so I don't quite understand what is wrong.
Here is the relevant subroutine:
FORM conv_and_down USING name TYPE string tab TYPE ANY TABLE.
CONCATENATE cfd_name name INTO temp_str.
CLEAR tb_converted.
CALL FUNCTION 'SAP_CONVERT_TO_TEX_FORMAT'
 EXPORTING
 i_field_seperator = fid_char
 TABLES
 i_tab_sap_data = tab
 CHANGING
 i_tab_converted_data = tb_converted
 EXCEPTIONS
 CONVERSION_FAILED = 0
 OTHERS = 0.
ENDFORM.
Any help is appreciated, as I am still fairly new to ABAP.
Edited by: gilthan3 on Feb 9, 2012 4:31 PM

Nevermind, I figured it out

Difference between line type and table type

hi,
can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

hi,
Go through this blog, this might help you.
/people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
 "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
In a BSP when we need to work with a table we must always do the following:
1, in the Types definitions create a structure:
 types : begin of ts_reclist,
mso-bidi- style='mso-tab-count:2'> receiver type somlreci1-receiver,
mso-bidi- style='mso-tab-count:2'> style='mso-tab-count: 1'> rec_type type somlreci1-rec_type,
mso-bidi- style='mso-tab-count:2'> end of ts_reclist.
mso-bidi- <![if !supportEmptyParas]> <![endif]>
but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
class="MsoNormal"> types : tt_reclist type table of ts_reclist.
class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
 data: t_reclist type tt_reclist.
and creating the structure based upon the structure definiton:
<![if !supportEmptyParas]> <![endif]> data: s_reclist type ts_reclist.
as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
 s_reclist-receiver = '[email protected]'. "<-- change address
mso-bidi- <![if !supportEmptyParas]> <![endif]>
mso-bidi- s_reclist-rec_type = 'U'.
and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
 append s_reclist to t_reclist.
<![if !supportEmptyParas]> <![endif]>
the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1"> style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>
class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
 EXPORTING
style='mso-tab-count:2'> document_data = docdata
style='mso-tab-count:2'> DOCUMENT_TYPE = 'RAW'
style='mso-tab-count:2'> PUT_IN_OUTBOX = 'X'
style='mso-tab-count:2'> COMMIT_WORK = 'X' "used from rel.6.10
 TABLES
mso-bidi-font-size: style='mso-tab-count:2'> receivers = t_reclist
class="style1"> <![if !supportEmptyParas]> <![endif]>
<![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
<![if !supportEmptyParas]> when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.
Hope this helps, Do reward.

How can I get the program to recognize two different types of thermocouples?

I am using a PCI-4351 card with a TBX-68T terminal block. I was having trouble writing and finding a program that would give me more than one reading/sec. I found a program on the NI website called "435x_logger_triggering", and so far it is the only program that I have found that will actually collect data at 60 Hz. Unfortunately, this program only lets you specify one mode for your thermocouples. This is a problem because we are using two thermocouples, one is type K and the other is a type R, so we get bad readings from one of the thermocouples depending on which mode it is set on. I would like to know how I can program in a seperate mode for each channel in this program. Un
fortunately, some of the sub VI's in this program are password protected, so I don't know if this is possible. Everything is entered correctly in the Measurement and Automation explorer, so that isn't the problem. I will attach a copy of the program that I am using. I have modified it slightly from the one I got off the NI website, so that the thermocouple readings have a time stamp and are saved to disk. Any assistance you could give me would be greatly appreciated.
Thanks,
Jordan
Attachments:
Forest_Fire_Thermocouple.vi ‏140 KB
435xlogger_triggering.vi ‏110 KB

Jordan,
You should be able to sample two different thermocouples in the example that ships with the 435x driver called "Getting Started with multiple tranducers Continous". Simply put each type of thermocouple in a different index . Each index of the Transducer Group Array can have a different type and specify the channels that correspond to that type.
One way that you can speed this VI up is to place a wait inside of the while loop. This will reduce the number of times the software polls the card if it has available data(increasing the overhead). I would suggest about 500 ms. The data that you receive will all have the same delta t because the sampling clock is hardware driven not software, so it does matter when the data is polled.
You will not be
able to get 60 samples per second when you are measuring multiple channels anyway. The sample rate for multiple channels is about 9/(# channels). This is explained in the 435x Users Manual.
I looked at your code and noticed that you tried to change some of the enumeration controls. Unfortunately you will not be able to change these because they are password protected on the low level subVIs, which is where they are defined.
The way you select if you want the notch filter is in the 435x Config you specify fast or slow. If it is slow then it will select 10Hz as the nitch filter. If you select fast the it will select either 50 or 60Hz You would then use the function "435x Set power line frequency"
Good luck,
Mike

What are the different types of exits available?

hi all,
Can any explain different types of exits ? user exit ? menu exit etc?
can anyone explain me each exit with an real time scenario
regds
hari

Types of Exits 
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits 
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits 
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
 CASE okcode.
 WHEN 'BACK OR EXIT'.
 CASE sy-dynnr.
 WHEN '100'.
 SET SCREEN 0.
 LEAVE SCREEN.
 WHEN '200'.
Note that you can write any code that satisfy your needs. ****
But in this case, this was wrote as a sample code for reference sake. ****
And you can test it. ****
 SET SCREEN 100.
 LEAVE SCREEN.
 ENDCASE.
 ENDCASE.
Regards,
Pavan

What are the different types of parameters available in function builder an

What are the different types of parameters available in function builder and where do we use them.

The different type of parameters available in FM are
Import - They are used to pass the values to the function module.
Export- They are used by FM to pass the result back to the calling program.
Changing - The variables are passed to the FM and can be changed during the FM processing.
Tables - Internal tables can be passed to the FM (it works similar to changing parameter).

Different types of tables........Explain

Similar Messages

Maybe you are looking for