Diff Between Elementary search helps

search helps

& Collective

1) Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help). 2) Collective search helps combine several elementary search helps. Collective search help thus can offer several alternative search paths. 3) An elementary search help defines the standard flow of an input help. 4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with collective search help. 5) A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field. 6) Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in collective search help, they are expanded to the level of the elementary search helps when the input help is called.

Lock mode
Defines how to synchronize table record access by several users. The following modes exist: Exclusive lock The locked data can be read or processed by one user only. A request for another exclusive lock or for a shared lock is rejected. Shared lock Several users can read the same data at the same time, but as soon as a user edits the data, a second user can no longer access this data. Requests for further shared locks are accepted, even if they are issued by different users, but exclusive locks are rejected. Exclusive but not cumulative lock Exclusive locks can be requested by the same transaction more than once and handled successively, but an exclusive but not cumulative lock can only be requested once by a given transaction. All other lock requests are rejected.

Technical settings:
The technical setting specifies how the table should handle by the SAP system. The main technical settings of a table are 1. Data Class 2. Size category 3. Delivery class 4. Buffering 5. Logging

Type group:
we use type groups to store the user-defined data types as well as constants in the abap dictionary. 1 Slis 2 Hktst

Aggregate Object
Views, Match Code and Lock objects are called aggregate objects because they are formed from several related table.

There are three different functions used in SAP Script:

1) 2) 3) OPEN_FORM WRITE_FORM CLOSE_FORM

What is use of using HASHED TABLE?

Hashed table is useful when you have to work with very big internal table and to read it with "READ TABLE WITH KEY ..." The time access is constant! Definition of a Hashed Table: "Defines the table as one that is managed with an internal hash procedure. You can imagine a hashed table as a set, whose elements you can address using their unique key. Unlike standard and sorted tables, you cannot access hash tables using an index. All entries in the table must have a unique key. Re: What is the role of an abapper in support project?What is the ticket concept in support project?Who raise the ticket and who resolve it?Let me know the complete procedure? In support project, abaper role is to support project. how means support people will raise tickets(problems occur in reports etc) and send to abapers with some id. abapers will do the work. and they contact to support people that id. In support project there should a SAP Support Team and the Team members had given an ID , If the user gets any errors he can issue the tickets to that iD for a particular Consultant.