What's the use of description of a bookmark? Find Bookmark in Bookmark-Tree? FavIcons on second synced devide?

1. I'm a little bit confused about the useage of descriptions of a bookmark.
For what can I use it after I filled something in?
Is the intention to open the booksmark property to see what I have filled in a long time ago?
Maybe I could be useful to add this to the Bookmarks tooltip?!
2. I have many Bookmarks in many Subfolders.
But sometimes I don't find a Bookmark. So I try to find it over the awesome-Bar and I find it.
Is it possible to see in the awesome-bar/SearchFunktionInBookmarkLibrary where I have the Bookmark in my Bookmarktree?
3. I have synced my Bookmarks to a second PC. Is it possible to load all favicons an this device?

# The description field provides additional information about a bookmark. From what I can see, it's only visible in the Library. The field is automatically filled in when you bookmark a page that contains a description, e.g.
#* http://www.w3schools.com
# The following add-ons make locating bookmarks easier in the Library and the sidebar.
#* https://addons.mozilla.org/firefox/addon/show-parent-folder/
#* https://addons.mozilla.org/firefox/addon/go-parent-folder/
#* https://addons.mozilla.org/firefox/addon/sidebar-bookmarks-search-plus/
# You can try the Favicon Reloader add-on to reload missing site icons.
#* https://addons.mozilla.org/firefox/addon/faviconreloader/

Similar Messages

What is the use of jsp when compare with Struts

what is the use of jsp when compare with Struts

JSP Tag Libraries are great for reusable content formatting and ligic.
For example, let's say you have this Shopping site. Each item you sell is stored in a database, and you get them out depending on Catagories, creating a List of ItemBeans. You allways want to display the items with a catagory header, then a <table> with the item number, the description and the price.
Instead of creating a bunch of logic in the JSP that does this, you can pass it on to a Tag that might look like this in your JSP:
<shopping:itemTable catagory="${selectedCatagory}" items="${itemsForCatagory}" />
This would make the JSP easier to read and work with.
The actual uses are incredible. Have you used the <jsp:useBean ...> tag? That is an example of a use of the Custom Tag Libraries.
Furthermore, look into JSTL (JSP Standard Tag Libraries). They are a collection of tags (API by Sun, coding by Apache) used to do many of the standard actions you might want/need to do in JSPs, like a conditional tag (c:if only do something if the test is true), multiple-conditional tags (c:choos c:when c:otherwise) like an if [else if] else construct. Looping through an array or Collection (c:forEach), storeing values in scopes (c:set) formating numbers and dates (the fmt library), xml transformations (xml library), and lots of other things that you could replace scriptlet code with.

What is the use of security-constraint tag in web.xml

what is the use of following tag , and how to use that, and where to use that tag.
<web-resource-collection>
<web-resource-name>SecureOrderJSP</web-resource-name>
<descrip<url-pattern>/order/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name></role-name>
</auth-constraint>
</security-constraint>tion>Protect the Order JSP Pages </description>

Hi,
You can refer this link
http://www.whizlabs.com/tutorial/scwcd/j-scwcd-7-5.html
give the complete description of your doubt
Thanks,
Snigdha Sivadas

What is the use of change pointer concept in ale?

what is the use of change pointer concept in ale?
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Creation of IDoc:
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

What is the use varients in sap?

what is the use varients in sap?

Hi Prashanth, this will clear ur doubt.
You can create any number of selection sets (variants) for a program. The variants are allocated to the program uniquely.
Creating variants makes sense when you frequently start a program with the same selection default values.
You can mark Start with variants in the program attributes. Users (system, services, reporting) can then start the program only with a variant.
If the program uses several selection screens, you can choose to create a variant for all the selection screens or individually for each selection screen.
Naming conventions and transporting variants
"SAP&xxx" are supplied by SAP
"CUS&xxx" are created by customers (in client 000)
Variants that follow these naming conventions are client-independent and will automatically be transported along with the report. If these naming conventions are not followed, an entry for a request (task) must be added to the object list: LIMU VARI .
You have to assign a name and a description to each variant. By default, variants are available for both online and background processing. You can also define a variant exclusively for use with background processing.
You can protect the variant itself and the individual selection criteria and parameters against unauthorized changes. If you select Display only in catalog, this variant will not be displayed in the general value help (F4).
The type of a selection is determined in its declaration: Type s for SELECT-OPTIONS, type p for PARAMETERS. If you select Selections protected, then the field(s) will not be ready for input. You can use the hide attribute to suppress selection criteria and parameters on the screen, if required, resulting in a less cluttered selection screen.
When you use selection variables, there are three basic ways of supplying your selections with values at runtime:
From table TVARV (type T)
Date fields using dynamic date calculation (type D), such as today's date
User-specific variables (type B); Prerequisite: The selection must be declared with the MEMORY ID addition.
kindly reward if found helpful.
cheers,
Hema.

WHAT IS THE USE OF COPY/MATCH OPTION IN BUISNESS CONTENT

WHAT IS THE USE OF COPY/MATCH OPTION IN BUISNESS CONTENT GIVE DETAILS

Hi,
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
Example of an automatic match
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if
¡        the match indicator is not set and
¡        the install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
                            a.      Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
                            b.      Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties which are taken into account when versions are matched are now listed.
When referring to InfoObjects it is important to differentiate between:
§         Characteristics
§         Time characteristics
§         Key figures and
§         Units
Valid for All InfoObjects Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        Texts
·        Description
If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
·        Attribute only (flag)
·        Short and long text (description)
·        Time dependency of attributes
·        Transfer routine
Valid for Characteristics
Properties Matched Automatically:
Properties Matched Manually:
·        Compounding
New InfoObjects are included in compounding
·        Referenced characteristic
Reference characteristics are transferred automatically. A warning is issued.
·        Attributes / navigation attributes
New attributes are included.
If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
·        Application components
If the entry for the active version is initial, the delivery version is used.
·        BEx display
·        Characteristic constants
·        Default member
·        Authorizations (flag and field)
·        Selection (CHASEL)
·        InfoObject is document attribute
·        Data type
·        Length
·        Output length
·        Conversion routines
·        Lower case allowed (flag)
·        Contains master data (flag)
·        Master data is authorization relevant (flag)
·        Export DataSource (Flag)
·        F4 query design
·        F4 query runtime
·        Check ODS object
·        Contains text tables (flag)
·        Texts are language-dependent (flag)
·        Short, medium and long texts exist (each with flag)
·        Default currency
·        GIS attribute
·        Hierarchies exist (flag)
Valid for Key Figures
Properties Matched Automatically:
Properties Matched Manually:
·        Type of key figure
·        Fixed unit
·        Fixed currency
·        Aggregation
·        Exception aggregation
Valid for Units
Properties Matched Automatically:
Properties Matched Manually:
·        See the table above (Valid for Characteristics), if these properties are also relevant for the units.
When referring to InfoProviders it is important to differentiate between:
¡        MultiProviders
¡        InfoCubes
¡        ODS Objects and
¡        InfoObjects
InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
Valid for All InfoProviders Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoObjects
If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for MultiProviders
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoProviders
If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for InfoCubes
Properties Matched Automatically:
Properties Matched Manually:
·        New dimensions
If dimensions in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed. Manual matching is not necessary.
With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed. Manual matching is not necessary.
·        Active Version Available
In this column, the following display options are available:
¡        : The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
¡        Date symbol: The object is already available in an active version. However, the active version belongs to an older Content release. SAP recommends that you install the latest version.
¡        Gray symbol: An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version). If this is not enough to change the object status from inactive to active the object has to be postprocessed. You find notes on postprocessing in the activation log.
Postprocessing: An inactive object status may also occur for an InfoObject if changes are made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
¡        No indicator: The object is not available in an active version.
7. Make Settings in the Selection List and Install.
Make the required settings in the Install selection list:
Installation Type
Installation Type
Information
Simulate installation
The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (and not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
Install
The selected objects are installed immediately.
Install in background
The selected objects are installed in the background.
Install and transport
The selected objects are installed immediately and then written to a transport request.
SAP recommends you use the Install in background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time to complete. Make sure that when you install objects in the background that the versions are not matched. It is always the delivery versions that are installed. These are not matched with any available customer versions.
Refer
Business Content (Versions)
http://help.sap.com/saphelp_nw04/helpdata/en/c1/ea683cc5e8ca68e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a66d5e07211d2acb80000e829fbfe/frameset.htm
Thanks,
JituK

What is the use of hot key...

what is the use of hotkey in elementary search helps...how to use this in elementary search helps...can anybody send any navigations on these ..

Creating Elementary Search Helps
Procedure
In the initial screen of the ABAP Dictionary, select object class Search help, enter the name of the search help and choose Create.
A dialog box appears in which you must select the type of search help.
Select Elementary search help and choose .
The maintenance screen for elementary search helps appears.
Enter an explanatory text in the field Short text.
You can for example find the search help at a later time using this short text.
In the Definition tab page enter the selection method of the search help.
You can enter the name of a table or a view (database view, projection view or help view) here. If you enter a table that has a text table, the name of the text table is automatically entered in the corresponding field.
Using the input help (F4 help), select fields of the selection method as parameter in the Search help parameter area. Select the fields that should be used in the dialog box for value selection or in the hit list.
If the selection method is a table that has a text table, both the fields of the table and the fields of the text table are offered in the input help.
The data element of the parameter is automatically copied from the selection method. The data element defines the output attributes and the F1 help of the parameter in the hit list and in the dialog box for value selection.
You can assign the parameter another data element. To do so, select the Mod flag. The Data element field is now ready for input. Then select a data element with the input help (F4 help). Only data elements whose data type, length and number of decimal places is the same as those of the previous data element can be assigned.
This removes the link between the data element of the search help parameter and the data element of the selection method field having the same name. If you cancel the Mod flag, the data element of the assigned table field is used again.
Define the attributes of the search help parameters.
Select the IMP flag if it is an import parameter. Select the EXP flag if it is an export parameter.
You can define the dialog for the input help with the fields LPos, SPos and SDis. Enter the parameter position in the hit list in LPos. If you enter nothing or the value 0 here, the parameter is not displayed in the hit list.
Enter the parameter position in the dialog box for value selection in SPos. If you enter nothing or the value 0 here, the parameter is not displayed in the dialog box for value selection.
Set the SDis flag if the parameter should be a pure display field in the dialog box for value selection. The user is thus informed that the contents of the parameter restrict the value, but he cannot change this restriction. This makes sense for example when the parameter is an import parameter or if it has a default value.
You can assign the parameter a default value in the Default value field.
Select the dialog type of the search help.
The dialog type defines how the hit list is displayed in the input help.
Save your entries.
A dialog box appears in which you have to assign the search help a development class.
Choose .
Do not forget to link the search help to a screen field. The search help attachment is not part of the search help definition; it is part of the object definition to which the search help is attached.
Result
The search help is activated. You can find information about the activation flow in the activation log, which you can display with Utilities ® Activation log. If errors occurred during activation, the activation log is automatically displayed.
Other Options
Assign a hot key: If the search help is to be accessed with a hot key, you must enter a one-place ID in the Hot key field. All the elementary search helps contained in a collective search help should have different short cuts.
Assign a search help exit: In exceptions, you might have to change the standard flow defined by the search help with a search help exit. In this case enter the name of the search help exit in the corresponding field.
Test the search help: You can test the flow of an input help defined by the elementary search help with . A dialog box appears in which you can simulate the behavior of the search help under different conditions. You can obtain information about the options provided in this window with .
See also:
Example for Search Helps
Each customer of a carrier (see Flight Model) or of a travel agency has a customer number. You want to find a search option for this customer number.
The user must be offered two different search paths.
The user should be able to search for the customer number using the customer data, such as the name and address.
The user should be able to search for the customer number using existing customer bookings.
You can provide the required search option by creating a collective search help SCUSTOM. Two elementary search helps SCUSTOM_NAME (for searching with the customer data) and SCUSTOM_BOOK (for searching with the existing bookings) are created for the actual search paths. These elementary search helps are included in the collective search help.
Elementary Search Help SCUSTOM_NAME
This elementary search help should enable you to search for the customer number using the name and address (street, city, country). All this data is contained in table SCUSTOM. Table SCUSTOM must therefore be selected as the selection method of the elementary search help.
You now have to decide which fields of the selection method are needed for the input help process. These are the fields that should appear either in the dialog box for restricting values or in the hit list.
In the dialog box for restricting values, the user should be able to restrict values with the customers name and address, i.e. the fields for the street, city and country. These fields as well as the customers number (the information to be found must always be in the hit list) should appear in the hit list. The fields ID, NAME, STREET, CITY and COUNTRY of table SCUSTOM must be included in the search help as parameters.
The parameter ID is declared to be an import parameter. A pattern entered in the corresponding field of a screen template can therefore be used directly for the value selection. Restrictions for the other parameters of the search help must be entered in the dialog box for value selection.
All the parameters of the search help are declared to be export parameters. As a result, all the parameters of the hit list can be returned to the screen template if the corresponding fields are available there.
Elementary Search Help SCUSTOM_BOOK
This elementary search help should enable you to search for the customer number using existing customer bookings. The flight data for the booking (flight number, date of flight, city of departure, city of arrival) and the name of the customer should be used for the search here. This data is distributed on the tables SBOOK (bookings), SCUSTOM (name) and SPFLI (cities of departure and arrival). The following graphic shows the relationship between the relevant tables, that is the existing foreign key relationships.
In this case a database view SCUS_BOOK must be created on these three tables (see Example for Views) as selection method. The tables in the view (join) are linked as defined by the existing foreign key relationships (see Foreign Key Relationship and Join Condition).
In the dialog box for restricting values, the user should be able to restrict the search for booking data with the carrier ID, customer name, city of departure and city of arrival The flight date and of course the customer number should also be displayed in the hit list. Fields CARRID, FLDATE, CUSTOMID, NAME, CITYFROM and CITYTO of view SCUS_BOOK must be included in the elementary search help as parameters of the search help.
The parameter CUSTOMID is declared to be an import parameter. All the parameters of the search help are export parameters.
Collective Search Help SCUSTOM
The two elementary search helps are now included in the collective search help. You must now allocate the parameters of the elementary search helps to the parameters of the collective search help.
The parameter ID of the collective search help is marked as an import parameter. All the parameters are export parameters. The values can thus be copied from the hit list to the screen template.
Attaching the Search Help
In order to be able to use the search help SCUSTOM in screen templates, the attachment of the search help (see Attaching Search Helps with Screen Fields) must be defined.
Attaching to the Check Table SCUSTOM
The search help should be available for all the fields that are checked against table SCUSTOM. The search help therefore must be attached to table SCUSTOM. The search help parameters must therefore be assigned to the key fields of table SCUSTOM.
The parameter ID of search help SCUSTOM is here assigned to the field ID of table SCUSTOM in this field assignment. No assignment is possible for all other parameters of the search help (NAME, CITY and COUNTRY) since table SCUSTOM does not contain this information as key fields.
Attaching to a Field of Table SCUSTOM
In order that the search help is available when the field SCUSTOM-ID is directly copied to the input template, you have to attach the search help to this field.
With this type of attachment, all the parameters of the search help can be assigned to the corresponding fields of the table.
Structure of an Elementary Search Help
An elementary search help defines the standard flow of an input help. You can define the following components of this flow in the search help:
where does the data displayed in the hit list come from (selection method)
what information should be displayed in the dialog box for value selection and in the hit list (search help parameters)
what field contents can be taken into account for hit list selections and which values in the hit list can be returned to the screen fields (search help parameters)
what dialog steps should be executed in the input help (dialog behavior)
Selection Method
The possible input values displayed for a field in the hit list are determined at runtime by database selection.
If all the data required in the hit list comes from one single table, you only have to select this table (or a projection view on this table) as selection method. If there is a text table for the table, its fields are also available in the input help. A table entry is linked with the corresponding text by the existing foreign key.
If the data needed in the hit list comes from more than one table, you must link these tables with a view (database view or help view). This view must be defined as the selection method.
If the underlying tables are client-specific, the client field must be contained in the view. Otherwise selection for the input help would be for all clients.
Search Help Parameters
A search help has an interface consisting of parameters. These parameters define the fields of the selection method that should be used in the input help.
A parameter of the search help must correspond to each field in the dialog box for value selection and to each field of the hit list. The parameters are copied from the corresponding selection method, that is they always have the same name as the corresponding field of the selection method.
If the search is restricted with a parameter of the search help, this is used in the data selection for formulating a WHERE condition for the field of the selection method with the same name. Vice versa, the parameters of the search help are assigned the contents of the fields of the selection method having the same name.
The search help should not contain any parameters for the clients. In the input help, selection is automatically in the logon client of the user.
A data element must be assigned to each search help parameter, that is a type is always defined for the search help parameters.
A search help can contain further parameters that do not correspond to any field of the selection method. This is normally only necessary if the standard flow of the input help described by the search help still has to be modified by with a search help exit.
Import and Export Parameters
When an input help is called, the entries that the user already made in the input template are taken into consideration. For example, if a user calls the input help for the flight number and already specified the carrier, of course only the numbers of flights of this carrier should be offered.
On the other hand, if the user selects one row of the hit list, more than one field of the input template might have to be filled with data from the selected row of the hit list. For example, if the flight number is obtained from the hit list, the city of departure and the destination should also be returned in the screen template.
The interface of a search help defines the context data that can be used in the input help and the data that can be returned in the input template.
A parameter of a search help can be classified as:
Import parameters: Parameters with which context information from the processed input template (screen) may be copied to the help process.
Export parameters: Parameters with which values from the hit list may be returned to the input template.
A parameter can simultaneously be an input and an export parameter. A search help can also contain parameters that are neither import nor export parameters. Such parameters could be required for the internal input help process, for example.
When you attach a search help, you must define where the import parameters of the search help get their values from and the fields in which the contents of the export parameters are returned. See also Value Transport for Input Helps.
Description of the Online Behavior
The online behavior defines the steps executed in the input help process and the structure of the hit list and dialog box for value selection.
The dialog type defines whether or not the dialog box for value selection should be displayed. If you want to skip the dialog box for value selection, the hit list is displayed directly after calling the input help.
When you define an elementary search help, you can define how the dialog box for value selection and the hit list should look. For example, you can define the position of a parameter in the dialog box for value selection here. The column position in which the values of a parameter are displayed in the hit list can also be defined here
Please reward points..
regards

What is the use of spool?

HI
what is the use of spool?
is it possible to send a mail with out spool?
thanks,
sap-abap.

FORM SEND_TO_SPOOL.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING DESTINATION            = 'LOCL'
            COPIES                 = COUNT
            LIST_NAME              = 'FBL1N'
            LIST_TEXT              = 'SUBMIT ... TO SAP-SPOOL'
            IMMEDIATELY            = ' '
            RELEASE                = ' '
            NEW_LIST_ID            = 'X'
            EXPIRATION             = DAYS
            LINE_SIZE              = 170
            LINE_COUNT             = 58
            LAYOUT                 = 'X_58_170'
            SAP_COVER_PAGE         = ' '
            COVER_PAGE             = ' '
            RECEIVER               = 'SAP*'
            DEPARTMENT             = 'System'
            SAP_OBJECT             = 'RS'
            AR_OBJECT              = 'TEST'
            ARCHIVE_ID             = 'XX'
            ARCHIVE_INFO           = 'III'
            ARCHIVE_TEXT           = 'Description'
            NO_DIALOG              = 'X'
IMPORTING OUT_PARAMETERS         = PARAMS
            OUT_ARCHIVE_PARAMETERS = ARPARAMS
            VALID                  = VALID.
IF VALID <> SPACE.
SUBMIT RFITEMAP USING SELECTION-SET VARIANT
TO SAP-SPOOL
    SPOOL PARAMETERS PARAMS
    ARCHIVE PARAMETERS ARPARAMS
    WITHOUT SPOOL DYNPRO
    AND RETURN.
ENDIF.
ENDFORM.

What is the use of this form?

Hi all,
What is the use of this form in include RV61B901?
How does this code send any information to the program calling it? Is Sy-subrc global so that main program will know the reuslts?
Code:
FORM KOBED_901.
DATA : l_anzpk LIKE likp-anzpk.
SELECT SINGLE anzpk FROM likp
                      INTO l_anzpk
                      WHERE vbeln = komkbv2-vbeln.
IF l_anzpk NE 0.
    sy-subrc = 4.
    exit.
ENDIF.
sy-subrc = 0.
ENDFORM.
Thanks,
Charles.

Hello,
This form sets the value of sy-subrc(which is global) based
on the value of l_anzpk.
Regards
Greg Kern

What is the use of additon in up to 1 rows in SELECT statement

Hi All,
         What is the use of up to 1 rows in select statement.
for example
SELECT kostl
      FROM pa0001
      INTO y_lv_kostl UP TO 1 ROWS
      WHERE pernr EQ pernr
      AND endda GE sy-datum.
    ENDSELECT.
I'm unable to get in wat situations we hav to add up to 1 rows
please help me out...
Thanks,
santosh.

Hi,
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Regards,
Bhaskar

What is the use of Alternative Calculation Type =2 and 4

Dear Friends
In pricing procedure in gross value, Net value for Item and Net value has Alternative calucation type is 2.
What is the use of it?
Without using it these value line are also fetching net value then what is the work of it. Please give me detail information with its effects in pricing condition tab page in sales document.
Thanking You
Arun

Arun biswal,
Correct Biswal. We have at varoius stages within Pricing procedure the "net value" which is calculated. Not only the alternative calculation type "2" is used if you notice carefully they are stored as subtotals at various levels.
For Ex Gross Value --> Subtotal =1 --> Calc type = 2
similarly for Net value for Item --> Subtotal =2 --> Calc type = 2
Net value 2 --> Subtotal =3 --> Calc type = 2
See, these are used to calculate the net value at various levels in pricing. The calculation Type has got a set of routines that will facilitate us in pricing. SAP has provided certain clauclated formulas or routines to facilitate us during calculation within pricing . Here the "2" is used for calculation without tax and store it as subtotal and display it or use it for further calculations.
We can use this "netvalue" amount for further calculations. It is used for clarity purpose when you issue a statement to customer. (like Confirmation order) at various levels like discount amt involved, Freight involved, Rebate amount invloved.....
Even without this Calc type or using sub total u can proceed....
Finally we have TOTAL --> Subtotal =A --> Calc type = 4
In the above line we have Calc type as 4, which means when you use TAX this calc type is used .
Routines are used to facilitate your process....
Regards
Sathya

What is the use of Serializable Interface in java?

Hello friends,
I have one dout and i want to share with u guys:
Why Serializable interface made and actully
what's the use of it?
At which place it become useful ?
It is not contain any method then why it is made?
If anyone have any idea about this then please reply.
Thanks in advace
Regards,
Jitendra Parekh

t is not contain any method then why it is made?To point out to the user of a class (and the programs) that the design of this class is conforming to certain restraints needed for Serialization.

What is the use of Data packet dim with Virtual cube with services

Hi Friends,
Could anybody tell me what is the use of Packet dimension in Virtual cube with services , It cannot contain data persistently ,Just fetch at runtime,Then there is no Physical load happening,Then why it should be automatically created for this??
Message was edited by: Pradeep choudhari

Hi Maik,
Unit dimension will not be created automatically until and unless you have keyfigure referning units..
But my question is : Why should we have data pack dimension , which is useless in this case of Virtual cube with services.It should not be created automatically!! What do you say??

What is the use of Withholding tax identification number field?

Hello SAP Experts,
I posted this question earlier but had to close because of no replies from anybody. Posting it again to see if I am lucky to get some answer this time.
Can someone tell what is the use of field Withholding Tax Identification Number? Does it help with the reporting? Where does it get populated on the report if given at vendor or master record or within the withholding tax customization for company code? What is the difference between creating it in the customization for withholding tax information for company code and vendor/customer master record?
As per SAP: Withholding tax identification number
This is a number issued by the tax authorities per withholding tax type.
This number must be specified in Customizing either:
(a) As part of the withholding tax information defined for the company code, or
(b) As part of the withholding tax information defined in the customer or vendor master record.

Hi Pete,
The only thing that I could check is the content used in US:
See content of this field for US:
LFA1-STCD1 Social security number
LFA1-STCD2 Employer identification number
LFBW-WT_WTSTCD Withholding tax identification number for WT Type
In order to populate it, please kindly check the following:
The reason why you cannot fill in the field WT_WTSTCD in transaction
Fk02 however you can do it in XK02 (Change vendor centrally) can be due
to wrong customizing of the field status group.
Kindly check the following:
SPRO->
Finantial accounting -> Accounts receivable and accounts payable ->
Define screen layout per activity (vendors) -> Change Vendor(Accounting)
Company code data -> W/holding tax data, w/h tax 2 ->
FIELD Withholding tax code,w/h tax 2 will be probably just available to
display. Please, change it to optional entry.
I hope I could be of assistance.
Kind Regards,
Fernando Evangelista

What is the use of HTTPS 8181 port

Hi,
I am wondering what is the use of the port 8181 on the EE5 application server.
the second question. Why the application server open so many port on the same local machine. I agree that for security raison it is a good idea. But does application serveur use tcp connection to communicate between the server thread ?
So it is possible to add a thread in the serveur application to process some internal work. And of course it is possible to include this new thread in the communication process of the server ?
Can we have the map of all the tcp trhead use by the server application.
Regards
Herve Terrolle.

Your app has to run as root to listen on ports up to 1024,
also, some other app (apache?) may already be listening on port 443.
AFAICT port 8181 is just arbitrarily chosen, it might as well have been port 4430, or any other free port above 1024.

What's the use of description of a bookmark? Find Bookmark in Bookmark-Tree? FavIcons on second synced devide?

Similar Messages

Maybe you are looking for