Help for Control Level Events

Dear Friends
i had an internal Table Itab_emp
before saving from belowcode i want to check for a particular field
i had itab_otime which had value as time format for particular ids
so i want to add them for a id and check condition
output of itab_emp is
PERID Date OTIME
1      01.10.2007 013000
1      03.10.2007 001000
2      04.10.2007 000030
2      05.10.2007 001000
i want to add values for perid 1 and 2 and see the sum of that in a field in itab only so that i can apply condition
Hope u got my problem
Reflect changes in below code
i think control level events will help but How i dont know
SORT ITAB_EMP BY PERID.
LOOP AT ITAB_EMP WHERE MARK = 'X' .
    IF SY-SUBRC = 0.
MOVE-CORRESPONDING ITAB_EMP TO ITAB_OTAPP .
      ITAB_OTAPP-OBJID = 1.
      ITAB_OTAPP-TODTE = ZHR_PR_M_OTAPP-TODTE.
      ITAB_OTAPP-FRDTE = ZHR_PR_M_OTAPP-FRDTE.
      ITAB_OTAPP-IMMHD = ZHR_PR_M_OTAPP-IMMHD.
      ITAB_OTAPP-CRETM = SY-UZEIT.
      ITAB_OTAPP-CREON = SY-DATUM.
      ITAB_OTAPP-CREBY = SY-UNAME.
      APPEND ITAB_OTAPP.
    ENDIF.
ENDLOOP.
LOOP AT ITAB_OTAPP INTO WA_ITAB_OTAPP.
    MODIFY ZHR_PR_M_OTAPP FROM WA_ITAB_OTAPP.
ENDLOOP.
Hope will get answer as soon as possible
Please Help Out Genius
With Best Regards
Ruby

Similar Messages

TRANSFER FUNTION FOR CONTROL LEVEL

Hi
I was doing some calculos for a transfer of funtion.
But now I am not sure
How I can conect level Process?
Can you help me
files are attachments
Thanks
Mario
Attachments:
2.vi ‏416 KB

This board is only for asking for files to be converted. Conversion Board Rules!
You have an ordinary question and need to ask it in the LabVIEW board.
Also, when you post a message, please turn off your CAPS LOCK key. No need to yell the message in the subject line.

Actionscript Help for Simple Button Events

Hey everyone,
I'm pretty new to flash and I think this is a fairly simple animation, but I'm not quite sure how to write out the action script for it. I have a website that has very similiar animations to www.cookstreet.net. I have shapes and text that fly in from the bottom when a button is clicked, but I want to get them to fly back out of the top of the screen when any other button is clicked before any new content loads back in from the bottom. What should I add to the action script to tell flash to first check and see if there is content loaded on the screen when a button is clicked, and if there is, to go to the animation that flies that content out of the top and then return to the animation of the new content coming in from the bottom? What I currently have set up for my buttons is:
function handleClick( pEvent:MouseEvent):void
    if( pEvent.target == reel )
        gotoAndPlay("Reel");
    else if( pEvent.target == home)
        gotoAndPlay("Home");
    else if( pEvent.target == news)
        gotoAndPlay("News");
    else if( pEvent.target == film)
        gotoAndPlay("Film")
    else if( pEvent.target == about)
        gotoAndPlay("About")
    else if( pEvent.target == contact)
        gotoAndPlay("Contact")
reel. addEventListener(MouseEvent .CLICK, handleClick );
home. addEventListener(MouseEvent .CLICK, handleClick );
news. addEventListener(MouseEvent .CLICK, handleClick );
film. addEventListener(MouseEvent .CLICK, handleClick );
about. addEventListener(MouseEvent .CLICK, handleClick );
contact. addEventListener(MouseEvent .CLICK, handleClick );
Thanks for the help!
-Sofi

What you can probably do is have a variable that you use to keep track of who's present on the stage, starting it off as a null value. That way when you click a button if the value is null is skips processing a moving out scenario and jumps to the moving in one. So your event listeners would be calling a different handler function that first takes care of the moving out needs, if any, which in turn calls the moving in function after the moving out activity is done (or the timeline for moving out does... I don't know how you plan to implement the moving out stuff). If it is a functiob to function process, the moving out function could pass the event.target to the moving in function so that wouldn't have to change at all, except to add in somewhere wha the new variable value should be.
If what I just offered is one big ball of confusion... take your time and inch your way thru it.

RS485 Serial HELP for Low-level Read Queries

Hi,
I am trying to communication with some lab equipement (Ebara Turbopump) over rs485. Now I have a Blastronix 2 port RS485 PCI board connect with cabiling to the equipement. But when I try and use NI-VISA to communication, the read times out, which is not particularly useful information because I don't know what part of my query is wrong then.
Below, I've posted some images from their communication protocol, but I am very confused as to how to translate this into a Labview VI. So far I've tried using a String Constant with the example 8.1 (last image, with my slave ID: 001) but I get nothing. I've tried it in both ASCII and Hex with a carriage return at the end.
Any help is very appreciated!!

Okay, I tried creating to create the string using an u8 array, but still nothing. However, I am still very new to labview and not exactly sure how to create a proper array of u8/hex. I just created different u8 constant numbers and then fed them into the build array function and then to conversion from Byte to String and then to the Write of the Serial connection.
But how would I go about validating the cable?

CONTROL BRK EVENTS

what is the AT EVENT in CONTROL BRK EVENTS

Hi,
Check this out -
AT - Control breaks with internal tables
Variants:
AT NEW f.
AT END OF f.
AT FIRST.
AT LAST.
Effect
In a LOOP which processes an internal table, you can use special control structures for control break processing. All these structures begin with AT and end with ENDAT. The sequence of statements which lies between them is then executed if a control break occurs.
You can use these key words for control break processing with internal tables only if a loop is actively processing an internal table and reference is to the innermost currently active loop.
The control level structure with internal tables is static. It corresponds exactly to the sequence of columns in the internal table (from left to right). In this context, the criteria according to which you sort the internal table are unimportant.
At the start of a new control level (i.e. immediately after AT), the following occurs in the output area of the current LOOP statement:
All character type fields (on the right) are filled with "*" after the current control level key.
All other fields (on the right) are set to their initial values after the current control level key.
Between AT and ENDAT, you can use SUM to insert the appropriate control totals in the numeric fields (see also ABAP Number Types) of the LOOP output area (on the right) after the current control level key. Summing is supported both at the beginning of a control level ( AT FIRST, AT NEW f) and also the end of a control level ( AT END OF f, AT LAST).
At the end of the control level processing (i.e. after ENDAT), the old contents of the LOOP output area are restored.
Notes
   1. When calculating totals, you must ensure that the totals are inserted into the same sub-fields of the LOOP output area as those where the single values otherwise occur. If there is an overflow, processing terminates with a runtime error.
   2. If an internal table is processed only in a restricted form (using the additions FROM, TO and/or WHERE with the LOOP statement), you should not use the control structures for control level processing because the interaction of a restricted LOOP with the AT statement is currenly not properly defined.
   3. With LOOPs on extracts, there are also special control break control structures you can use.
Note
Non-Catchable Exceptions:
SUM_OVERFLOW: Overflow when calculating totals with SUM.
Variant 1
AT NEW f.
Variant 2
AT END OF f.
Compatible Work Area with Control Level Processing and Field Symbols Not Allowed as Control Level Criterion.
Effect
f is a sub-field of an internal table processed with LOOP. The sequence of statements which follow it is executed if the sub-field f or a sub-field in the current LOOP line defined (on the left) before f has a different value than in the preceding ( AT NEW) or subsequent (AT END OF) table line.
Example
TYPES: BEGIN OF COMPANIES_TYPE,
        NAME(30),
        PRODUCT(20),
        SALES TYPE I,
      END   OF COMPANIES_TYPE.
DATA: COMPANIES TYPE STANDARD TABLE OF COMPANIES_TYPE WITH
                     NON-UNIQUE DEFAULT KEY INITIAL SIZE 20,
      WA_COMPANIES TYPE COMPANIES_TYPE.
LOOP AT COMPANIES INTO WA_COMPANIES.
AT NEW NAME.
    NEW-PAGE.
    WRITE / WA_COMPANIES-NAME.
ENDAT.
WRITE: / WA_COMPANIES-PRODUCT, WA_COMPANIES-SALES.
AT END OF NAME.
    SUM.
    WRITE: / WA_COMPANIES-NAME, WA_COMPANIES-SALES.
ENDAT.
ENDLOOP.
The AT statements refer to the field COMPANIES-NAME.
Notes
   1. If a control break criterion is not known until runtime, you can use AT NEW (name) or AT END OF (name) to specify it dynamically as the contents of the field name. If name is blank at runtime, the control break criterion is ignored and the sequence of statements is not executed. If name contains an invalid component name, a runtime error occurs.
   2. By defining an offset and/or length, you can further restrict control break criteria - regardless of whether they are specified statically or dynamically.
   3. A field symbol pointing to the LOOP output area can also be used as a dynamic control break criterion. If the field symbol does not point to the LOOP output area, a runtime error occurs.
If you use AT within a LOOP with an explicitly-specified output area, the area must be compatible with the line type of the internal table so that it can be initialized properly (as described above) at the start of a new control level.
You can restrict control break criteria further, regardless of whether they were defined statically or dynamically, by specifying offset and/or length.
Note
Non-Catchable Exceptions:
AT_BAD_PARTIAL_FIELD_ACCESS: Invalid sub-field access when dynamically specifying the control break criterion.
AT_ITAB_FIELD_INVALID: When dynamically specifying the control break criterion via a field symbol, the field symbol does not point to the LOOP output area.
ITAB_ILLEGAL_COMPONENT: When dynamically specifying the control break criterion via (name) the field (name) does not contain a valid sub-field name.
Variant 3
AT FIRST.
Variant 4
AT LAST.
Effect
Executes the appropriate sequence of statements once during the first ( AT FIRST) or last (AT LAST) loop pass.
Example
TYPES: BEGIN OF COMPANIES_TYPE,
        NAME(30),
        PRODUCT(20),
        SALES TYPE I,
      END   OF COMPANIES_TYPE.
DATA: COMPANIES TYPE STANDARD TABLE OF COMPANIES_TYPE WITH
                     NON-UNIQUE DEFAULT KEY INITIAL SIZE 20,
      WA_COMPANIES TYPE COMPANIES_TYPE.
LOOP AT COMPANIES INTO WA_COMPANIES.
AT FIRST.
    SUM.
    WRITE:    'Sum of all SALES:',
           55 WA_COMPANIES-SALES.
ENDAT.
WRITE: / WA_COMPANIES-NAME, WA_COMPANIES-PRODUCT,
        55 WA_COMPANIES-SALES.
ENDLOOP.
ashish

Control level Staements

What are control level statements ? what is the use of this ?
can any one give sample examples for control level statements
points for sure...
Regards
Vijaya

Hello Vijaya,
Check out the code below
Processing Control Levels
When you sort an extract dataset, control levels are defined in it. For general information about control levels, refer to Processing Internal Tables in Loops The control level hierarchy of an extract dataset corresponds to the sequence of the fields in the HEADER field group. After sorting, you can use the AT statement within a loop to program statement blocks that the system processes only at a control break, that is, when the control level changes.
AT NEW <f> | AT END OF <f>.
ENDAT.
A control break occurs when the value of the field <f> or a superior field in the current record has a different value from the previous record (AT NEW) or the subsequent record (AT END). Field <f> must be part of the HEADER field group.
If the extract dataset is not sorted, the AT... ENDAT block is never executed. Furthermore, all extract records with the value HEX 00 in the field <f> are ignored when the control breaks are determined.
The AT... ENDAT blocks in a loop are processed in the order in which they occur. This sequence should be the same as the sort sequence. This sequence must not necessarily be the sequence of the fields in the HEADER field group, but can also be the one determined in the SORT statement.
If you have sorted an extract dataset by the fields <f1>, <f2>, ..., the processing of the control levels should be written between the other control statements as follows:
LOOP.
AT FIRST.... ENDAT.
 AT NEW <f1>....... ENDAT.
 AT NEW <f2>....... ENDAT.
 AT <fgi>..... ENDAT.
 <single line processing without control statement>
 AT END OF <f2>.... ENDAT.
 AT END OF <f1>.... ENDAT.
AT LAST..... ENDAT.
ENDLOOP.
You do not have to use all of the statement blocks listed here, but only the ones you require.
REPORT DEMO.
DATA: T1(4), T2 TYPE I.
FIELD-GROUPS: HEADER.
INSERT T2 T1 INTO HEADER.
T1 ='AABB'. T2 = 1. EXTRACT HEADER.
T1 ='BBCC'. T2 = 2. EXTRACT HEADER.
T1 ='AAAA'. T2 = 2. EXTRACT HEADER.
T1 ='AABB'. T2 = 1. EXTRACT HEADER.
T1 ='BBBB'. T2 = 2. EXTRACT HEADER.
T1 ='BBCC'. T2 = 2. EXTRACT HEADER.
T1 ='AAAA'. T2 = 1. EXTRACT HEADER.
T1 ='BBBB'. T2 = 1. EXTRACT HEADER.
T1 ='AAAA'. T2 = 3. EXTRACT HEADER.
T1 ='AABB'. T2 = 1. EXTRACT HEADER.
SORT BY T1 T2.
LOOP.
AT FIRST.
 WRITE 'Start of LOOP'.
 ULINE.
ENDAT.
AT NEW T1.
 WRITE / ' New T1:'.
ENDAT.
AT NEW T2.
 WRITE / ' New T2:'.
ENDAT.
WRITE: /14 T1, T2.
AT END OF T2.
 WRITE / 'End of T2'.
ENDAT.
AT END OF T1.
 WRITE / 'End of T1'.
ENDAT.
AT LAST.
 ULINE.
ENDAT.
ENDLOOP.
Rewards points if helpful.
Thanks,
Sachin

How to get search help for 2nd parameter based on the 1st parameter value

Hi all!
 I have 2 parameters (material no, revision level). I have created a search help for revision level. It has an importing parameter :material no. and one exporting parameter : revision level.When I checked it, it's giving the revision values only for the specified.
In my report , I have kept these 2 materials in my selection screen.For revision level , I have added the matchcode object which I have created. When I pressed F4 for revision level, it's giving all the values irrespective of the material no. in the first parameter. How to solve it? Please suggest.

Hi,
Try this code filling internal table fields,
DATA: BEGIN OF values,
 OID TYPE ZCL_OBJECT-OBJECTID,
 ODEC TYPE ZCL_OBJECT-OBJECT_DESC,
 END OF values,
 W_FIELD(10).
DATA: ZCL_PROJECT-PROJECTID type zcl_project-projectid,
 ZCL_OBJECT-OBJECTID(5).
DATA: progname TYPE sy-repid,
 dynnum TYPE sy-dynnr,
 dynpro_values TYPE TABLE OF dynpread,
 field_value LIKE LINE OF dynpro_values,
 values_tab LIKE TABLE OF values.
CALL SCREEN 100.
*& Module VALUE_PROJECTID INPUT
 text
*MODULE VALUE_PROJECTID INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
 EXPORTING
 tabname = 'ZCL_PROJECT'
 fieldname = 'PROJECTID'
 dynpprog = progname
 dynpnr = dynnum
 dynprofield = 'ZCL_PROJECT-PROJECTID'.
*ENDMODULE. " VALUE_PROJECTID INPUT
*& Module VALUE_OBJECTID INPUT
 text
MODULE VALUE_OBJECTID INPUT.
 CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = progname
 dynumb = dynnum
 translate_to_upper = 'X'
 TABLES
 dynpfields = dynpro_values.
READ TABLE dynpro_values INDEX 1 INTO field_value.
W_FIELD = FIELD_VALUE-FIELDVALUE.
SELECT OBJECTID
 OBJECT_DESC
 FROM ZCL_OBJECT
 INTO (VALUES-OID,
 VALUES-ODEC)
WHERE PROJECTID = FIELD_VALUE-FIELDVALUE.
 APPEND VALUES TO VALUES_TAB.
ENDSELECT.
 CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'OID'
 dynpprog = progname
 dynpnr = dynnum
 dynprofield = 'ZCL_OBJECT-OBJECTID'
 value_org = 'S'
 TABLES
 value_tab = values_tab.
ENDMODULE. " VALUE_OBJECTID INPUT
*& Module INIT OUTPUT
 text
MODULE INIT OUTPUT.
progname = sy-repid.
dynnum = sy-dynnr.
CLEAR: field_value, dynpro_values.
field_value-fieldname = 'ZCL_PROJECT-PROJECTID'.
APPEND field_value TO dynpro_values.
IF SY-UCOMM = 'BACK'.
 LEAVE program.
ENDIF.
IF SY-UCOMM = 'ANS'.
 LEAVE TO SCREEN '0'.
ENDIF.
ENDMODULE. " INIT OUTPUT
START-OF-SELECTION.
WRITE: / field_value-fieldvalue,
 W_FIELD.
LOOP AT VALUES_TAB INTO VALUES.
 WRITE / VALUES.
ENDLOOP.
if sy-subrc <> 0.
 WRITE / field_value-fieldvalue.
endif.
Plzz reward points if it helps

How to provide F4 help for a field in table control

Hi Friends,
I have requirement like below.
1.Create one custom transaction code with header and item information.
2.In item level, we will be designed table control to enter/display the data.
3.Table controls first field will be material number and next DOT number (Material may have many DOT numbers) and so on.
4.First user will enter material number in the table controls first rows first field and go to DOT number field.
5.DOT number has drop down option. If user selects drop down box of DOT number, he gets all the DOT numbers available in database. User selects one DOT number and double clicks on it then it will be populated in DOT number field box.
But for point number 5, business wants like when ever user enters material number in table control first field then select DOT numbers drop down then they want to see the particular materials DOT numbers only in the drop down list for selection. Not all DOT numbers available in data base. Same thing should happen for all item lines in table control.
Please see below example.
Assume data base table has 10 DOT numbers. But material number has only 2 DOT numbers. When ever user enters material number in item level table control and selects DOT numbers drop down then it should show only 2 DOT numbers which are related to particular material number. Not all 10 DOT numbers.
Could you please suggest me, how can we achieve this?

Hello,
Check this :-
For POV
Input Help in Dialog Modules
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON VALUE-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F4 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. The module <mod> is defined in the ABAP program like a normal PAI module. However, the contents of the screen field <f> are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These all have the prefix F4IF_. The most important are:
F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT DEMO_DYNPRO_F4_HELP_MODULE.
TYPES: BEGIN OF VALUES,
CARRID TYPE SPFLI-CARRID,
CONNID TYPE SPFLI-CONNID,
END OF VALUES.
DATA: CARRIER(3) TYPE C,
CONNECTION(4) TYPE C.
DATA: PROGNAME LIKE SY-REPID,
DYNNUM LIKE SY-DYNNR,
DYNPRO_VALUES TYPE TABLE OF DYNPREAD,
FIELD_VALUE LIKE LINE OF DYNPRO_VALUES,
VALUES_TAB TYPE TABLE OF VALUES.
CALL SCREEN 100.
MODULE INIT OUTPUT.
PROGNAME = SY-REPID.
DYNNUM = SY-DYNNR.
CLEAR: FIELD_VALUE, DYNPRO_VALUES.
FIELD_VALUE-FIELDNAME = 'CARRIER'.
APPEND FIELD_VALUE TO DYNPRO_VALUES.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE VALUE_CARRIER INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
TABNAME = 'DEMOF4HELP'
FIELDNAME = 'CARRIER1'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CARRIER'.
ENDMODULE.
MODULE VALUE_CONNECTION INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
DYNAME = PROGNAME
DYNUMB = DYNNUM
TRANSLATE_TO_UPPER = 'X'
TABLES
DYNPFIELDS = DYNPRO_VALUES.
READ TABLE DYNPRO_VALUES INDEX 1 INTO FIELD_VALUE.
SELECT CARRID CONNID
FROM SPFLI
INTO CORRESPONDING FIELDS OF TABLE VALUES_TAB
WHERE CARRID = FIELD_VALUE-FIELDVALUE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = 'CONNID'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CONNECTION'
VALUE_ORG = 'S'
TABLES
VALUE_TAB = VALUES_TAB.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The input fields have been adopted from the program fields CARRIER and CONNECTION. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
MODULE INIT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON VALUE-REQUEST.
FIELD CARRIER MODULE VALUE_CARRIER.
FIELD CONNECTION MODULE VALUE_CONNECTION.
When the user chooses input help for the individual fields, the following is displayed:
For the Airline field, the POV module VALUE_CARRIER is called. The function module F4IF_FIELD_VALUE_REQUEST displays the input help for the component CARRIER1 of the structure DEMOF4HELP from the ABAP Dictionary, namely the search help DEMOF4DE. The users selection is returned to the screen field CARRIER.
For the Flight number field, the POV module VALUE_CONNECTION is called. The function module DYNP_VALUE_READ transports the value of the screen field CARRIER into the program. The program then reads the corresponding values from the database table SPFLI into the internal table VALUES_TAB using a SELECT statement, and passes the internal table to F4IF_INT_TABLE_VALUE_REQUEST. This displays the internal table as input help, and places the users selection into the screen field CONNECTION.
For POH------------
Field Help
There are three ways of displaying field help for screen elements:
Data Element Documentation
If you place a field on the screen in the Screen Painter by copying a ABAP Dictionary field, the corresponding data element documentation from the ABAP Dictionary is automatically displayed when the user chooses field help (as long as the help has not been overridden in the screen flow logic).
For further information about creating data element documentation, refer to data elements.
Data Element Supplement Documentation
If the data element documentation is insufficient, you can expand it by writing a data element supplement
Data element supplement documentation contains the heading Definition, as well as the following others:
Use
Procedure
Examples
Dependencies
To create data element supplement documentation for a screen, choose Goto ® Documentation ® DE supplement doc. from the element list of the screen. A dialog box appears in which the system proposes a number as the identified for the data element supplement. You can then enter help texts for the above headings using the SAPscript editor.
Data element supplement documentation created in this way is program- and screen-specific. Any data element supplement documentation created in the ABAP Dictionary with the same number is overridden by the screen-specific documentation. You can link existing data element supplement documentation created in the ABAP Dictionary with a screen field by using the table THLPF. To do this, crate a new row in THLPF containing the following data: Program name, screen name, field name, and number of the data element supplement documentation.
To display data element supplement documentation, you must code the following screen flow logic in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> [MODULE <mod>] WITH <num>.
After PROCESS ON HELP-REQUEST, you can only use FIELD statements. If there is no PROCESS ON HELP-REQUEST keyword in the flow logic of the screen, the data element documentation for the current field, or no help at all is displayed when the user chooses F1. Otherwise, the next FIELD statement containing the current field <f> is executed.
If there is screen-specific data element supplement documentation for the field <f>, you can display it by specifying its number <num>. The number <num> can be a literal or a variable. The variable must be declared and filled in the corresponding ABAP program.
You can fill the variables, for example, by calling the module <mod> before the help is displayed. However, the FIELD statement does not transport the contents of the screen field <f> to the ABAP program in the PROCESS ON HELP-REQUEST event.
For further information about data element supplement documentation, refer to Data Element Supplements.
Calling Help Texts from Dialog Modules
If data element supplement documentation is insufficient for your requirements, or you want to display help for program fields that you have not copied from the ABAP Dictionary, you can call dialog modules in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON HELP-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F1 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. However, the contents of the screen field <f> are not available in the module <mod>, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. The field help should not be dependent on the user input.
The module <mod> is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
VAR(4),
INT TYPE I,
LINKS TYPE TABLE OF TLINE,
FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
WHEN 1.
VAR = '0100'.
WHEN 2.
VAR = '0200'.
INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
EXPORTING
DOKLANGU = SY-LANGU
DOKTITLE = TEXT-002
CALLED_FOR_TAB = 'DEMOF1HELP'
CALLED_FOR_FIELD = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
EXPORTING
DOKCLASS = 'TX'
DOKLANGU = SY-LANGU
DOKNAME = 'DEMO_FOR_F1_HELP'
DOKTITLE = TEXT-003
TABLES
LINKS = LINKS.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:
The screen fields DEMOf1HELP-FIELD1 and DEMOF1HELP-FIELD2 from the ABAP Dictionary and the program fields FIELD3 and FIELD4 are assigned to the input fields. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON HELP-REQUEST.
FIELD DEMOF1HELP-FIELD2 MODULE F1_HELP_FIELD2 WITH VAR.
FIELD FIELD3 MODULE F1_HELP_FIELD3.
FIELD FIELD4 MODULE F1_HELP_FIELD4.
The components FIELD1 and FIELD2 of structure DEMOF1HELP both refer to the data element DEMOF1TYPE. This data element is documented, and also has two supplements with numbers 0100 and 0200.
The following field help is displayed:
When the user chooses F1 on the input field for DEMOF1HELP-FIELD1, the data element documentation for DEMOF1TYPE is displayed, since the field does not occur in the PROCESS ON HELP-REQUEST event.
If the user chooses F1 repeatedly for the input field DEMOF1HELP-FIELD2, the data element documentation is displayed, along with the supplement documentation for either 0100 or 0200 alternately. The variable VAR is filled in the dialog module F1_HELP_FIELD2.
When the user chooses F1 on the input field for FIELD3, the data element documentation for DEMOF1TYPE is displayed, since this is called in the dialog module F1_HELP_FIELD3 by the function module HELP_OBJECT_SHOW_FOR_FIELD.
When the user chooses F1 on the input field for FIELD4, the SAPscript documentation DEMO_FOR_F1_HELP is displayed, since this is called in the dialog module F1_HELP_FIELD4 by the function module HELP_OBJECT.
Regards,
Deepu.K

How can I reference an external help file from context sensitive help at the control level?

My goal is to provide context sensitive help for each control displayed on the front panel using a help file created externally. I know that at the VI level I can specify a Help Path; I want the same behaviour for each control inside a VI. I also know about creating a custom control and specifying the Help Path in there, but it doesn't help in this situation, for I have hundreds of controls in my application and I cannot go back and replace each one with a unique .ctl. If I could override each instance of the custom control with unique path data that would do the trick, but that's not how it works.
Is there a way to add the Help Path information to regualr controls?
-euge
ne

This functionality is not yet built into LabVIEW.
About all you can do is cut and paste the help for each control into the description for the control. It is tedius but a finite task.

Acct X for trans./event key BSX is a K control account.

Dear Experts:
I am not so familiar with FI and one question need your help:
When I was trying to post a goods receipt against one purchase order I created earlier, I got an error message: "Account 199999 for trans./event key BSX is a K control account'
For account 199999, the account group is Recon. account and acct type is Vendors.
Can anybody let me know the solution to this issue? Thank you all in advance!
Best Regards!
Tim

Hi Eli:
Thanks for your reply. But if I delete the account in OBYC, I will get another error message: "Account determination for entry TDCC BSX 0001 ___ ZZXX not possible". If I maintain the entry: "0001 ZZXX 19999" in BSX in OBYC, I will get the error above.
Do you know how to resolve that?
Thanks~
Tim

Best way to author field level help for a CHM?

Hi
I have been asked to create an HTML help (CHM) system for a .Net application which will include context sensitive help at both page and field level.
I have used map ids for page level help before - i.e. assigned a map id to topics and given this list to a developer for implementation, but I have never created field level help.
I've been looking at the 'What's This?' help project wizard but am confused as to whether this is the best approach and how it fits with the project as a whole (or even if it compatible with .Net applications). Does this mean that I need two help projects for the application - one for the main help, and one for the field level help? Is there a way to create field level help without using the 'What's This?' wizard?
I am using Robohelp 7.
Any advice gratefully received!
Chloe

Hi, Chloe,
As Peter notes, even Microsoft has backed away from using field-level Help in the last few years, so it may be worth trying to determine whether your users will benefit from having it available to them. That's not to say that you can't deliver field-level Help, however, as all the required methods for calling it are still available to .NET developers.
To clarify, what Madcap Software calls "DotNet Help" is just a proprietary Help viewer that the company hopes will be more modern and appealing to writers than the older HTML Help (.chm) viewer. HTML Help remains the recommended format for Windows applications, whether .NET or not, and you can use any authoring tool that is capable of outputting a .chm file to create online Help for a .NET application.
The method that your developers use to call field-level Help determines how it should be authored. If they use the standard .NET method (the SetHelpString method of the HelpProvider class), each text string is embedded in the application code itself, and not retrieved from your .chm file. More information here:
http://msdn.microsoft.com/en-us/library/system.windows.forms.helpprovider.sethelpstring(VS .71).aspx
http://support.microsoft.com/kb/821777
http://helpware.net/mshelp2/demo2/h1xNET.htm
Alternatively, developers can use the old HTML Help API to retrieve the text string from a .chm file. See:
http://msdn.microsoft.com/en-us/library/ms670082(VS.85).aspx
http://helpware.net/htmlhelp/how_to_whatsthis.htm
http://support.microsoft.com/?kbid=317406
The drawback of both methods is that the Help popups are plain text only — no graphics, text formatting, hyperlinks, etc. To work around this, some people use the third-party KeyHelp control to create feature-rich HTML popups. See:
http://www.keyworks.net/keyhelp.htm
This allows you to deliver the type of Help that you mentioned in your second message ("is there a way to do this so that these topics open in a small popup, without the TOC / tri-pane structure?").
Pete

F4 help for a field on table control

Hi All,
I have to display F4 help for a purticular field on the table control depending on one of the value in the row if the table.
There will be multiple entries in the table control and the F4 help for the field should change according to the value of other field in the row.
Can anybdy help me out doing this.....
Edited by: Alvaro Tejada Galindo on Feb 21, 2008 10:46 AM

Check the FM: HELP_VALUES_GET_WITH_TABLE_EXT
Check the documentation for example code.
regards,
Ravi

Search help for Custom Item level field

Hi All,
I have two custom fields at Item level. Both of them has fixed values defined at domain. The fixed values have a short text also given with them.
The problem I am facing is when SRM provides default search help for these custom fields, for first field the 'Value' and 'Description' comes in the search result screen, but for second, only 'Value' comes in the search result.
When I try to debug, it shows the SHLPTYPE as 'SH' for first one and for the second as 'FV'.
What does this indicate?
My requirement is to display both value and description in the search result screen.
Please suggest.
Thanks
Nandalal

Hi
Sorry for the delay. My User got locked for some time.
I have seen the document you sent me on my email id.
 I noticed in the case where the Search help is working fine, there is no space in between the contents of the Fixed values and their short text under the value range tab of the Domain element.
But in the case, where there is a problem with the search help. There both the Fixed values and their short description is having a space in between the words.
Try maintaining COND_A instead of "COND A". Also with the short description use "COND_A" instead of "COND A".
I hope this will resolve the issue.
Update me once you have any issues.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Search help for a field in table control based on another field value

Hi,
I want to attach the Search help for a field in table control based on another field value.
Please help me asap.
Will be highly rewarded

HI,..
Check these links
search help in table control
Re: How to create Search Help for a field in Table control !!
How to create Search Help for a field in Table control !!
F4 Help In Table Control
Control table F4 help
Problem in F4 help in screen field
check this code
DATA: BEGIN OF it_value4 OCCURS 0,
 TEXTCODE LIKE ZXX-TEXTCODE,
 TEXTDESC LIKE ZXX-TEXTDESC,
 END OF it_value4.
progname = sy-repid.
dynnum = sy-dynnr.
 SELECT TEXTCODE TEXTDESC
 FROM xxxx
 INTO CORRESPONDING FIELDS OF TABLE it_value4
 WHERE LOSS_CODE = IT_VALUE1 .
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'TEXTCODE'
 dynpprog = progname
 dynpnr = dynnum
 dynprofield = 'ITVALUE-TEXTCODE' "-->UR 4 th filed value in screen
 value_org = 'S'
 TABLES
 value_tab = it_value4.
endmodule.
Message was edited by:
 veereshbabu ponnada

Search Help for a Field of a Table Control

I have designed a screen using 'Table Control' with fields like Date, BoxNo,Quantity etc. Kindly tell me how to go about providing a search help for the field 'BoxNo' of this table control so that the user is not required to scroll down the entire table/list for selecting a particular box no.
Thanx in advance,
Alok.

When you go to screen painer, in screen painter attributes window, there is an atribute called search help, fill it.
Another way is, after PAI put:
PROCESS ON VALUE-REQUEST.
FIELD box_no MODULE f1_help_box_no.
And gives logic in that module using FM F4IF_INT_TABLE_VALUE_REQUEST.
Regards.

Help for Control Level Events

Similar Messages

Maybe you are looking for