Difference between fully-specified data types. and generic types

Hi,
Can anyone tell me the difference between fully-specified data types and generic types.
Thanks in advance.
Regards,
P.S.

HI
Generic table types
INDEX TABLE
For creating a generic table type with index access.
ANY TABLE
For creating a fully-generic table type.
Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic type INDEX TABLEincludes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
Fully-Specified Table Types
STANDARD TABLE or TABLE
For creating standard tables.
SORTED TABLE
For creating sorted tables.
HASHED TABLE
For creating hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
see this link
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb366d358411d1829f0000e829fbfe/content.htm
<b>Reward if usefull</b>

Similar Messages

Differences between the Portal Data Collector and the Activity Data Collect

Hello,
I want to know what are the differences between the Portal Data Collector and the Activity Data Collector?
Best Regards.
Pablo Mortera.

All of my SQL Server instances are sql server 2008r2 standard edition(10.50.2500). MDW is existing database, I try to setup collection sets for multiple instances and store data in one central MDW database
I create MDW in one instance, then run run configure Management Data Warehouse in target intance. collection sets were created successfully, but job failed with following error:
Executed as user: COCAD\INTDEPT01SQLAgentC10. The Management Data Warehouse version "00.00.0000.00" is not supported by the current data collector. Please upgrade the Management Data Warehouse by running the Management Data Warehouse Configuration
Wizard. Process Exit Code 5. The step failed.
Thanks
PAULqaz

Differences between operational systems data modeling and data warehouse da

Hello Everyone,
Can anybody help me understand the differences between operational systems data modeling and data warehouse data modeling>
Thanks

Hello A S!
What you mean is the difference between modelling after normal form like in operational systems (OLTP) e. g. 3NF and modelling a InfoCube in a data warehouse (OLAP)?
While in a OLTP you want to have data tables free of redundance and ready for transactions meaning writing and reading few records often, in an OLAP-system you need to read a lot of data for every query you do on a database. Often in an OLAP-system you aggregate these amounts of data.
Therefore you use another principle for these database scheme. This is called star schema. This means that you have one central table (called fact table) which holds the key figures and have keys to another tables with characteristics. These other tables are called dimension tables. They hold combinations of the characteristics. Normally you design it that your dimensions are small, so the access on the data is more efficent.
the star scheme in SAP BI is a little more complex than explained here but it follows the same concept.
Best regards,
Peter

Difference between earliest master data and master data change bonus

Hi,
Can anyone tell me what is the exact difference between earliest master data change and master data change bonus? Whenver any infotype is changed, why are the dates updated in both the fields? Is it not enough if only Earliest master data change field is updated? I was thinking that Earliest master data change bonus field is updated when IT267 is created, but even if i change the time data both the fields are getting updated. Please advise?
Thanks

Hi,
Earliest master dat change date is date beyond which no master data change can be put in for employee in infotype.
It is used to restrict any master data entry beyond certain date as restriction for employees that client has set and is moreover controlled at control record level but ocassionally used at employee level whenever payment was hold for long time and so on.
Master data change bonus date is date which gets automatically filled in whenever there is any master data change.
This date cannot be past earliest master data change date and will throw error if tried for employee to input.
Thanks,
Ameet

Difference Between Data type and message type

Hi,
    i have doubt on data type and message type.why we are mapping the message type why not data type?wht is the difference between data type and message type?

Hi Narayanana,
Data type defines the structure of your xml message.Message type is the wrapper of data type.You will be using your message type while mapping and not the data type.Its the abstraction concept used in oops
kanan thiyam
Posts: 28
Questions: 7
Registered: 1/8/07
Forum points: 24
   Re: What is deffernce b/w Data type and message type
Posted: Jun 13, 2007 8:05 AM    in response to: suresh k         Reply      E-mail this post
Hi Suresh,
Data Type defines the structure of the message and it will be wrapped under Message Type.
Hope the details below will clearify your doubts.
A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
The characteristic of columns and variables that defines what types of data values they can store.
Check out the details:
http://en.wikipedia.org/wiki/Data_type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
Details:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
kanan

Difference between message type and idoc type

Hi
difference between message type and idoc type
Regards
Rama

Hi,
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Example:
MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
Thanks,
Shankar

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.

Difference between a starting date and time and ending date and time

Hi All,
I need to bring out the difference between a starting data and time and ending date and time. Difference should be in time I mean it should be in hours or minus or seconds.
I am sure there must be a Function module for this, Has anyone of you been in search of this kind of FM, Kindly suggest me. It is urgent.
Thanks
Mahen

Hi,
Check this out.
data : date1 type dats ,   " System data type for Date (sy-datum)
       date2 type dats,
       time1 type tims,      " System data type for time (sy-timlo)
       time2 type tims,
       days type i,
       scd   type i,
       t_mt type i.
days = date1 - date2. " Diference in days.
Scd = time1 - time2. " diference in seconds.
t_mt = ( days * 24 * 60 ) + ( scd / 60 ).
total diference in minute
<b>Reward Points & Mark Helpful Answers</b>

Difference between IDOC Type and Message Type

Hi, please let me know the difference between IDOC type and Message Type?
Thanks

Hi,
Message type is business name for IDOC you are sending hiding all technical details of the IDOC.
IDOC type gives more technical information about structure of the IDOC.
You will be linking IDOC type to message type while processing IDOC in runtime. You will be specifying message type and IDOC type in WE20 trasaction which says which message will go to which partner whether it is outbound or inbound.
Best Regards,
Krishna

Disk Utility: Differences between "Zero Out Data" and "7-Pass Erase"?

I'm wondering if anyone knows if there's a significant difference between the "Zero Out Data" erase option in Disk Utility (specifically Disk Utility 10.5.5), and the "7-Pass Erase" and "35-Pass Erase" options in same software.
Here's why I'm asking: I have a co-worker with an iMac G5 20" 1.8GHz with 160GB internal hard drive. As a result of the power supply overheating a week ago due to dust, some hard drive problems resulted. I'm trying to assess whether these are 'soft' formatting problems that can be recovered from, or 'hard' problems requiring replacement of the hard drive and/or power supply.
Following the failure, I removed the dust and restored the iMac to servicable form. The power supply seems to be OK now. The next thing was to attempt to recover as much data as possible from the 160GB, as the last full backup was a week old. Carbon Copy Cloner, shell copy via 'sudo cp -p -R -v', Finder copy, and DiskWarrior recovery all met with problems. TechTool Pro identified a huge swatch of unreadable sectors during repeated surface scans. Unfortunately, these unreadable sectors were located midway in the OSX boot partition (an 80GB partition), and not in the other 80GB partition devoted to lower priority video data.
When I was satisfied I had backed up the data to the best of my abilities, I next set out to reformat the drive and see if the bad sectors could be eliminated or remapped out of existence. I did a "Zero Out Data" erasure in Disk Utility (with no errors during the erase), but TechTool Pro showed the bad sectors persisted in equal strength at the same location. I next executed a sixteen hour "7-Pass Erase" (again no errors, and confirming that it takes about an hour per 10GB). The next day when I ran TechTool pro, all of the sector errors had disappeared. I'm a bit perplexed as to why the "7-Pass Erase" seems to have recovered the use of the drive. Is it possible that there are simply thousands of bad sectors now remapped that I'm not seeing? [If so, how do I check for this?] TechTool Pro has not reported any S.M.A.R.T. issues to date on the drive. What am I to make of that?
There are some related threads I've checked into, but I'm not sure how to properly assess my situation based on this information:
<http://discussions.apple.com/thread.jspa?threadID=232007>
<http://discussions.apple.com/thread.jspa?threadID=138559>
<http://discussions.apple.com/thread.jspa?threadID=118455>
Since the iMac has three weeks left on it's one year warranty, and I've already moved the user to another machine temporarily, I'm thinking that the smart thing to so is to send it in to Apple to have them look at the power supply and hard drive. That way, when it returns, even if there is still a lingering hardware problem, at least it will be covered under warranty for another 90 days.
Any thoughts?
iMac G5 20" 1.8GHz Mac OS X (10.4.6) 1.25GB RAM, 160GB hard disk, SuperDrive

HI, Bret.
The only differences between "Zero Out Data", "7-Pass Erase", and "35-Pass Erase" are the number of times a binary zero is written to every bit on the disk. "Zero Out Data" writes a binary zero once, whereas the 7- and 35-Pass options write a zero seven and 35 times, respectively.
Technically, one pass with Zero Out Data should be sufficient to map bad sectors out of service, a process also known as sparing. If a bad sector is encountered, it is both marked as "in use" in the directory's allocation table and added to the directory's "bad blocks file."
My understanding is that the Surface Scan of Tech Tool Pro should identify bad sectors every time it is run unless the bad sectors have been locked out by the drive controller of the ATA drive itself. This is because Surface Scan checks the entire surface of the disk.
What may have happened is that running "Zero Out Data" spared the bad blocks from a directory standpoint, but did not result in the drive's controller locking out those sectors for reasons detailed in the "Surface Scan" section of the Tech Tool Pro manual. However, the 7-Pass Erase may have resulted in the drive's controller locking out the bad sectors and why Surface Scan did not pick them up after such.
Given the problems you described, I concur with your plan to have Apple check the affected computer. You might also want to consider purchasing an AppleCare Protection Plan for that Mac: I recommend and buy these for all my Macs.
For some additional information on bad sectors, see the "Bad Sectors" section of my "Resolving Disk, Permission, and Cache Corruption" FAQ.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Difference between sales order schedule line and item level data

Hi All,
Could you please let me know what is the difference between sales order schedule line and item level data?
Thanks,
Ramya

Hi Ramya,
Sales order schedule line contains del date, order qty, rounded qty, confirmed qty, delivery qty, schedule line category, purchase requisition etc., ie It contains the full details of sales order data with respect to the scheduled line of delivery. The total quantity of a sales order item can be subdivided into schedule lines that contain the various subsets with the corresponding delivering dates.
Sales order Item level data contains details of the item in the sales order like material code, net price, net value, UoM, PO details, reason for rejection if any, material group,billing date, plant etc., ie this
contains the full details of item irrespective of scheduled line.
Regards,
R. Senthil Mareeswaran.

Difference between P.O.date and P.O.created date

Hi,
Could you tell me difference between purchaseing doucment date and purchase order creaed date.
    Because some time in my org. po created after GR means in past date. So there is difference between
    po date and po created date. where this po created date is maintained in purchase order
           Thanks and Regards
                  Anil

Dear Anil,
Please check table EKKO with ta SE11.
Created Date => EKKO-AEDAT
Date on which the record was created
Document date => EKKO-BEDAT
Date on which the purchasing document was created
EKKO-AEDAT = Date on which the record was created
and also "Created By" also recorded automatically
by system.
Document date or EKKO-BEDAT normally default as
today when you create the PO via ME21N. This field
appear at top right of the screen. However this date
can be change to any date that required.
Thanks
Loke Foong

Difference between fully qualified name and Canonical name

CAn annyone xplain Difference between fully qualified name and Canonical name

If you dont know then don't replyYou were given a link directly to the answer. The state of my knowledge is therefore (a) irrelevant and (b) not proven by anything in this thread.
Who asked [you] to reply
You* did, when you posted here.
I know how to get from java language specificationClearly not, or you wouldn't still be posting here.
I need clarification for what is in java lang specification..It seems clear enough to me. What part of "A member class or member interface M declared in another class C has a canonical name if and only if C has a canonical name. In that case, the canonical name of M consists of the canonical name of C, followed by ".", followed by the simple name of M." didn't you understand?

Difference between using new Date() and new Date(System.currentTimeMillis()

Hi All,
I have seen many open source api's where they are updating dates with the following code
new Date(System.currentTimeMillis())
when i print the new Date() it prints the same
what is the difference between using new Date() and new Date(System.currentTimeMillis()) ??
Thanks,
J.Kathir

when i print the new Date() it prints the same
It does because of backward compatability. This constructor exists in version 1.3.1 but not in newer versions.Really ? Please point me to where you read that.
API doc 1.5 : new Date() (still there, not even deprecated)
A quick look at the code for this constructor:    /**
     * Allocates a <code>Date</code> object and initializes it so that
     * it represents the time at which it was allocated, measured to the
     * nearest millisecond.
     * @see     java.lang.System#currentTimeMillis()
    public Date() {
        this(System.currentTimeMillis());
    }

Difference between Invoice created date and billing date.

Hi Gurus,
I opened the Billing Document in display mode(T.Code:VF03).In header data I found two tabs one is Created On and another one is Billing Date. Here in the billing document the both dates were different.
Please let me know the difference between Created On date and Billing Date.
your afforts are highly appriciated.
JYothi.

Dear Jyothisd,
Invoice created date : Invoice created date is nothing but the date on which you have created the invoice.
Billingdate:Billing date is the date on which you suppose to do the billing for respective customer. Tease billing dates will be proposed to invoice from sales order if it is order related or else actual goods issue date is proposed to billing document as a Billing date if particular billing document is delivery related.
If you want you can change the Actual billing date the result is invoice created date.
Please revert if you want any further clarifications
Thanks&Regards

Difference between fully-specified data types. and generic types

Similar Messages

Maybe you are looking for