What is the use of text elements in scripts

pls tell me what is text element?can we use this in any window or only in main window ?
pls explain briefly with some coading .and onbe more question what is the lement that is used in our abap editor

<a href="http://help.sap.com/saphelp_47x200/helpdata/EN/images/locate.gif">Text Elements of a Form</a>
SAPscript calls the individual text components of a form text elements. To achieve good structuring and readability, you assign a fixed name to each text element in the form. The print program then uses these names to access the elements. This name applies also for translated versions of a text element, while the contents of the text elements depend on the language.
Text elements are related to a window, that is, a print program can call for each window only those text elements that exist in this window. They are used in main and other windows.
The variables used within '&...&' are replaced by the system at output time
/E <element name>
UL &fieldnam& text text
Named element are written when driver program use
 CALL FUNCTION 'WRITE_FORM'
 EXPORTING
 ELEMENT = 'BOOKING'
 TYPE = 'BODY'
 WINDOW = 'MAIN'
Unnamed element are written once in MAIN windows, and each time in other windos.
Regards

Similar Messages

What is the Use of Text Module Radio buton in Smartforms

Hi all,
What is the Use of Text Module Radio buton in Smartforms T - code ? How can we link this to our form ?
Thanks in advance
KR

Text modules
Text modules are used to centrally store texts that are used frequently in forms in the system.
Text modules are included in forms using texts nodes. The text node can either refer to the text module or take its text. You can then change the text or add to it to suit the form.
Text modules have the following attributes:
They are client-independent
They are connected to the transport system
They are connected to the translation tools in the system
The third attribute means that a text module can be uniquely assigned to a language using the logon language. When including a text module, you can also access translations of the text module, for example, to include an English text module in a German form.
Reward Points if useful.

What is the use of MAIN WINDOW in SCRIPTS

what is the use of MAIN WINDOW in SCRIPTS, y we con't create a script w/o main window.
Title was edited by:
Alvaro Tejada Galindo

Hi
See this
What are the different types of windows in SAP Scripts?
Windows are defined in the Layout sets which define the position and the text to displayed.
The different types of windows are:
MAIN - Main Window
The main window is a continous window which can extend over several pages. If the text in the main window fills up a page, a new page is created.
Only one main window can be defined in the SAP Script whereas upto 100 instances of main window can be created in a page.
VAR - Variable Window
This window can have the variable contents displayed on them. The contents of the window cannot exceed the window size. The content can be formatted for each page.
CONST - Constant Window
The constant window can have a fixed content and is formatted only once.
Main Windows (MAIN)
Each form must have one window of type MAIN. Such a window is called the main window of the form. For SAPscript forms, the main window has a central meaning:
It controls the page break.
It contains the text body that may cover several pages.
It allows to fix text elements at the upper and lower margins of the allocated page window (for example, for column headings).
As soon as a window of type MAIN is full, SAPscript automatically triggers a page break and continues to output the remaining text in the main window of the subsequent page. Page windows of type MAIN have the same width throughout the form. The SAPscript composer thus avoids reformatting of the text after each page break.
Variable Windows (VAR)
The contents of variable windows is processed again for each page, on which the window appears. The system outputs only as much text as fits into the window. Text exceeding the window size is truncated; the system does not trigger a page break. Unlike constant windows, the page windows declared as variable windows may have different sizes on different form pages.
Constant Windows (CONST)
Starting with Release 4.0, the system internally processes windows of type CONST similar to windows of type VAR. Therefore, if you create a new window, always use type VAR.
<REMOVED BY MODERATOR>
Anji
Message was edited by:
Alvaro Tejada Galindo

What is the use of NACE transaction in scripts?

hi
what is the use of NACE transaction in scripts?
bye

NACE is the transaction code where you can maintain the output types for the applications...
NACE - Initial Customizing Screen
where your going to attach the layout which u have designed to the particular output type - Specifies the kind of output to be produced.
The output type can specify, for example, a printed form that you need for internal use or a form that you want to send to a customer or vendor (for example, an order confirmation). The output type can also be an internal electronic mail message that you want to send to staff in another department.
print program - If you want to inform a partner about changes to output that was already issued, you enter the name of a program and a routine in the Form routine field.
The routine in the program checks which changes should result in a changed output being sent.
regards

Use of text elements in wirte_form function module.

Hi guru's,
Could any one tell me what is the use of text elements in write_form functional module SAP SCRIPTS. As per my knowledge text elements are used for multi language purpose is there any other advantage other than that.
Thanks in advance.
Vardhan.

Hello.
A text element is a block in script that can be written several times in your document. You can put fixed texts, variables, include texts, images, etc etc
When you see WRITE_FORM, element 'X', you know that everything that is inside element /E X of your script is writen. It's very usefful to organize your script, and it eases to construct a very complex script.
It's also usefull to translations in SE63.
Best regards.
Valter Oliveira.
Edited by: Valter Oliveira on May 27, 2008 10:05 AM

Use of text element in function module

hi friends what is the use of text element i.e list headings, selection texts,text symbols in a function module. where a can see these things after giving some text into it and activated.
 kumar.

hi
Text Symbols
A text symbol is a named data object that is generated when you start the program from the texts in the text pool of the ABAP program. It always has the data type c. Its field length is that of the text in the text pool.
Text symbols, along with the program title, list headings, and selection texts, belong to the text elements of a program. Text elements allow you to create language-independent programs. Any text that the program sends to the screen can be stored as a text element in a text pool. Different text pools can be created for different languages. When a text element is changed or translated, there is no need to change the actual program code. Text elements in an ABAP program are stored in the ABAP Editor (see Text Element Maintenance).
In the text pool, each text symbol is identified by a three-character ID. Text symbols have a content, an occupied length, and a maximum length.
Examples for text symbols in an ABAP program:
ID
Contents
Occupied length
Maximum length
010
Text symbol 010
15
132
030
Text symbol 030
15
100
AAA
Text symbol AAA
15
15
In the program, you can address text symbols using the following form:
text-###
This data object contains the text of the text symbol with ID ### in the logon language of the user. Its field length is the same as the maximum length of the text symbol. Unfilled characters are filled up with spaces. You can address text symbols anywhere in a program where it is also possible to address a variable.
If there is no text symbol ### in the text pool for the logon language, the name text-### addresses the predefined data object space instead.
You can also address text symbols as follows:
... 'textliteral'(###) ...
If the text symbol ### exists in the text pool for the logon language, this is the same as using text-###. Otherwise, the literal 'textliteral' is used as the contents of the text symbol. This is only possible at positions in the program where a variable can occur. You can create a text symbol for any text literal by double-clicking the literal in the ABAP Editor and replacing the literal with the text symbol.
You should use text symbols in your program whenever they need to be language-specific - for example, in a WRITEstatement.
If you program a list whose layout depends on field lengths, you should be careful, since the field length of text symbols will be different in different languages. You should therefore set the maximum field length of the field symbol so that there is enough space to translate it into other languages. For example, the English word 'program' has seven letters, but its equivalent German translation 'Programm' has eight.
The following example shows the use of text symbols in WRITE statements.
SET BLANK LINES ON.
WRITE: text-010,
 / text-aaa,
 / text-020,
 / 'Default Text 030'(030),
 / 'Default Text 040'(040).
If the text symbols of the above screen shots are linked to this program, the output looks as follows:
Text symbols 020 and 040 have no text symbols. For text symbol 020, the system displays a space. This is only displayed in this case because the blank line suppression has been turned off (see Creating Blank Lines).
regards
ravish
plz reward if helpful

Purpose of text element in scripts

1. What is the purpose of text element in scripts. When do we use it ?
2. Is text element window specific or only pertaning to main window ?

Hi,
text elements control the output of all data in sapscript forms windows.
A text element starts with /E in the format column (switch to 'old' non-visual tect-editor to see) and has a name in the text line.
The print program will fill the variables used as &symbols& in sapacript and then call the function WRITE_FORM for the element.
In the main window, elements can be called repeatedly to output table-like data - usually the text elements are called something like ITEM_LINE then.
Every window has a so-called default text element that has no name and is triggered without function call when the window is displayed. The default text element is the first one in the window. It is not preceded by /E. In other words: What you find on top of the window, before the first /E text element, is the default text element and is output without WRITE_FORM function call.
It is quite well explained in documentation
<a href="http://help.sap.com/saphelp_47x200/helpdata/en/d6/0db44e494511d182b70000e829fbfe/frameset.htm">BC SAPscript: Printing with Forms</a>
Regards,
Clemens

What is the use of Standart text in SapScripts.

What is the use of Standart text in SapScripts?
How to Use in Forms?

Hi Puja Das,
Welcome to SCN,
As per knowledge, Standard text is mainly meant for Functional People
For eg : Try changing a Sale Order no. In VA02.
If you see the Header or Item details You will find Texts tab. In that you can see Form Header, Header Note1/2.
Here the Functional / User will enter some text according to their understand, when they print regarding they need that text on a FORM.
Thus these text will be stored in a Standard Text format.
And You can Use Standard Text in Script as follows:
/: INCLUDE DATE OBJECT TEXT ID ST
Regards,
Suneel G

What is the use of various text objects in text determination

Dear All,
What is the use of various text objects in text determination.e.g the sale document header object(In this what we define and where that text is copied further) and
other text objects i.e customer/accounting,billing header etc.
Regards,
Ashima

Hi,
To exchange information between the User and the System as well as between the objects (Ex: Customer to Sales document, Sales document to Delivery Document) SAP uses Text Determination to determine or to propose Text. Text can be determined for objects like customer master, all documents, condition records, customer material info records, etc...
hope it helps..
regards..
yogi..

I've downloaded PhotoShop Elements 12, and apparently am supposed to download also PhotoShop Elements 4.0   What is the use/purpose of the latter?

I've downloaded PhotoShop Elements 12, and apparently am supposed to download also PhotoShop Elements 4.0   What is the use/purpose of the latter?

apparently am supposed to download also PhotoShop Elements 4.0   What is the use/purpose of the latter?
That is not necessary. Where are you being asked to do that?
Have you bought an upgrade version of PSE12? Are you upgrading from PSE4?

IN TEXT DETERMINATION WHAT R THE TYPES OF TEXT IS THERE AND IN PRICING WHAT

HI EXPERTS
IN TEXT DETERMINATION WHAT R THE TYPES OF TEXT IS THERE ????
AND IN PRICING WHAT R THE PRICING ELEMENTS ???
THANKS

Dear Hanumanth,
Text types in the customer master for sales and Distribution
0001     Sales note for customer
0002     Shipping instructions
0003     Selection for shipping
0004     Marketing notes
0005     Competitor
0006     Potential reasoning
0007     Product proposal items
0008     Frequency visited
0009     Payment willingness
Standard Text types in the Sales document ,delivery and billing header text
0001     Form Header
0002     Header note 1
0003     Header note 2
0004     Header note 3
0005     Header note 4
001     Delivery text 1
0010     Form supplement text
0011     Terms of delivery
0012     Shipping instructions
0013     Terms of payment
0014     Warranties
0015     Penalty for breach of contract
0016     Contract riders (clauses)
0017     Selection
0018     Other contractual stipulations
0019     Customer order text
002     Delivery text 2
0100     Bill of lading information
0101     Export/import information
0102     Transport information
For more details please go through thid SAP help link
http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f993545a11d1a7020000e829fd11/frameset.htm
PRICING ELEMENTS
The standard system includes condition types for basic pricing elements, such as material prices, customer and material discounts, and surcharges such as freight and sales taxes. In the case of each element, you can use the standard version, modify the standard version, or create entirely new definitions to suit your own business needs. The sequence of activities is generally as follows:
Define condition types for each of the price elements (prices, discounts, and surcharges) that occur in your daily business transactions.
Define the condition tables that enable you to store and retrieve condition records for each of the different condition types.
Define the access sequences that enable the system to find valid condition records.
Group condition types and establish their sequence in pricing procedures.
For more details please go through thid SAP help link
http://help.sap.com/saphelp_47x200/helpdata/en/64/7836b39c8911d199aa0000e8a5bd28/frameset.htm
I hope this will help you,
Regards,
Murali.

What is the use of FOLDER NODE in SMARTFORMS?

what is the use of FOLDER NODE in SMARTFORMS?
please explain.

Hi,
By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
How to create a New smartfrom, it is having step by step procedure
http://sap.niraj.tripod.com/id67.html
Here is the procedure
1. Create a new smartforms
Transaction code SMARTFORMS
Create new smartforms call ZSMART
2. Define looping process for internal table
Pages and windows
First Page -> Header Window (Cursor at First Page then click Edit -> Node -> Create)
Here, you can specify your title and page numbering
&SFSY-PAGE& (Page 1) of &SFSY-FORMPAGES(Z4.0)& (Total Page)
Main windows -> TABLE -> DATA
In the Loop section, tick Internal table and fill in
ITAB1 (table in ABAP SMARTFORM calling function) INTO ITAB2
3. Define table in smartforms
Global settings :
Form interface
Variable name Type assignment Reference type
ITAB1 TYPE Table Structure
Global definitions
Variable name Type assignment Reference type
ITAB2 TYPE Table Structure
4. To display the data in the form
Make used of the Table Painter and declare the Line Type in Tabstrips Table
e.g. HD_GEN for printing header details,
IT_GEN for printing data details.
You have to specify the Line Type in your Text elements in the Tabstrips Output options.
Tick the New Line and specify the Line Type for outputting the data.
Declare your output fields in Text elements
Tabstrips - Output Options
For different fonts use this Style : IDWTCERTSTYLE
For Quantity or Amout you can used this variable &GS_ITAB-AMOUNT(12.2)&
5. Calling SMARTFORMS from your ABAP program
REPORT ZSMARTFORM.
Calling SMARTFORMS from your ABAP program.
Collecting all the table data in your program, and pass once to SMARTFORMS
SMARTFORMS
Declare your table type in :-
Global Settings -> Form Interface
Global Definintions -> Global Data
Main Window -> Table -> DATA
Written by : SAP Hints and Tips on Configuration and ABAP/4 Programming
http://sapr3.tripod.com
TABLES: MKPF.
DATA: FM_NAME TYPE RS38L_FNAM.
DATA: BEGIN OF INT_MKPF OCCURS 0.
INCLUDE STRUCTURE MKPF.
DATA: END OF INT_MKPF.
SELECT-OPTIONS S_MBLNR FOR MKPF-MBLNR MEMORY ID 001.
SELECT * FROM MKPF WHERE MBLNR IN S_MBLNR.
MOVE-CORRESPONDING MKPF TO INT_MKPF.
APPEND INT_MKPF.
ENDSELECT.
At the end of your program.
Passing data to SMARTFORMS
call function 'SSF_FUNCTION_MODULE_NAME'
exporting
formname = 'ZSMARTFORM'
VARIANT = ' '
DIRECT_CALL = ' '
IMPORTING
FM_NAME = FM_NAME
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
if sy-subrc <> 0.
WRITE: / 'ERROR 1'.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function FM_NAME
EXPORTING
ARCHIVE_INDEX =
ARCHIVE_INDEX_TAB =
ARCHIVE_PARAMETERS =
CONTROL_PARAMETERS =
MAIL_APPL_OBJ =
MAIL_RECIPIENT =
MAIL_SENDER =
OUTPUT_OPTIONS =
USER_SETTINGS = 'X'
IMPORTING
DOCUMENT_OUTPUT_INFO =
JOB_OUTPUT_INFO =
JOB_OUTPUT_OPTIONS =
TABLES
GS_MKPF = INT_MKPF
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
for Smartforms material
http://www.sap-basis-abap.com/sapsf001.htm
http://www.sap-press.com/downloads/h955_preview.pdf
http://www.ossincorp.com/Black_Box/Black_Box_2.htm
http://www.sap-img.com/smartforms/sap-smart-forms.htm
http://www.sap-img.com/smartforms/smartform-tutorial.htm
http://www.sapgenie.com/abap/smartforms.htm
How to trace smartform
http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
http://www.sap-img.com/smartforms/smart-006.htm
http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
Re: Need FAQ's
check most imp link
http://www.sapbrain.com/ARTICLES/TECHNICAL/SMARTFORMS/smartforms.html
step by step good ex link is....
http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
Reward all helpfull answers
Regards
Omkar

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 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 Activate GuiXT option

What is the use of Activate GuiXT option .

GuiXT is a frontend design tool that allows you to taylor SAP standard transactions without modifying the backend ABAP code. It is a part of SAPgui and runs on the client PC, based on script files either on the PC or a network drive.
Functionality of guiXT from the SAP help;
"You can insert default values in fields
You can hide fields and groups of fields
You can move fields
You can add and change texts
You can add input help
You can add new screen elements like checkboxes, pushbuttons, graphics, or documentation
You can customize tables
You can change field labels on a system-wide basis"
Regards,
Nick

What is the use of text elements in scripts

Similar Messages

Maybe you are looking for