How I can see my interactive button on a tablet or smartphone?

Hey folks - sry for my english...
How I can see my interactive button, created in InDesign CC on a tablet or smartphone. It runs well on the computer but on tablet or smartphone i can't see the button. I save the InDesign file as Interactive PDF but it seems, there must be other things to know. Would be great you guys could help me :-)
Greets!

Moving this discussion to Reader IOS
Regards,
Ajlan Huda.

Similar Messages

How we can see the abap memory data

How we can see the abap-memory data
fine the code below
import lsind
         report_title
         table_name
         report_field
         change_display
         show_hide
         conversion_exits
         table_description
         form_program
         select_form
         update_form
         line_size
         line_count
         records[]
         fields[]
         header_fields[]
         select_fields[]
         xrep[]
         from memory id 'LZUT5U11'.
Regards
santhosh
mail-id : [email protected]

Dear Santosh,
ABAP MEMORY:
A logical memory model illustrates how the main memory is distributed from the view of executable programs. A distinction is made here between external sessions and internal sessions .
An external session is usually linked to an R/3 window. You can create an external session by choosing System/Create session, or by entering /o in the command field. An external session is broken down further into internal sessions. Program data is only visible within an internal session. Each external session can include up to 20 internal sessions (stacks).
Every program you start runs in an internal session.
All "squares" with rounded "corners" displayed in the status diagram represent a set of data objects in the main memory.
The data in the main memory is only visible to the program concerned.
CALL TRANSACTION and SUBMIT AND RETURN open a new internal session that forms a new program context. The internal sessions in an external session form a memory stack. The new session is added to the top of the stack.
When a program has finished running, the top internal session in the stack is removed, and the calling program resumes processing.
The same occurs when the system processes a LEAVE PROGRAM statement.
LEAVE TO TRANSACTION removes all internal sessions from the stack and opens a new one containing the program context of the calling program.
The ABAP memory is initialized after the program is called. In other words, you cannot transfer any data to a program called with LEAVE TO TRANSACTION via the ABAP memory.
SUBMIT replaces the internal session of the program performing the call with the internal session of the program that has been called. The new internal session contains the program context of the called program with which it is performed.
When a function module is called, the following steps are executed:
A check is made to establish whether your program has called a function module of the same function group previously.
If this is not the case, the system loads the associated function group to the internal session of the calling program as an additional program group. This initializes its global data.
If your program used a function module of the same function group before the current call, the function module that you have called up at present can access the global data of the function group. The function group is not reloaded.
Within the internal session, all of the function modules that you call from the same group access the global data of that group.
If, in a new internal session, you call a function module from the same function group as in internal session 1, a new set of global data is initialized for the second internal session. This means that the data accessed by function modules called in session 2 may be different from that accessed by the function modules in session 1.
You can call function modules asynchronously as well as synchronously. To do so, you must extend the function module call using the addition STARTING NEW TASK ''. Here, '' is a symbolic name in the calling program that identifies the external session, in which the called program is executed.
Function modules that you call using the addition STARTING NEW TASK '' are executed independently of the calling program. The calling program is not interrupted.
To make function modules available for local asynchronous calls, you must identify them as executable remotely (processing type: Remote-enabled module).
There are various ways of transferring data between programs that are running in different program contexts (internal sessions). You can use:
(1) The interface of the called program (standard selection screen, or interface of a
subroutine, function module, or dialog module)
(2) ABAP memory
(3) SAP memory
(4) Database tables
(5) Local files on your presentation server.
For further information about transferring data between an ABAP program and your presentation server, refer to the documentation for the function modules WS_UPLOAD and WS_DOWNLOAD.
Function modules have an interface, which you can use to pass data between the calling program and the function module itself (there is also a comparable mechanism for ABAP subroutines). If a function module supports RFC, certain restrictions apply to its interface.
If you are calling an ABAP program that has a standard selection screen, you can pass values to the input fields. There are two options here:
By using a variant of the standard selection screen in the program call
By passing actual values for the input fields in the program call
If you want to call a report program without displaying its selection screen (default setting), but still want to pass values to its input fields, there is a variety of techniques that you can use.
The WITH addition allows you to assign values to the parameters and select-options fields on the standard selection screen.
If the selection screen is to be displayed when the program is called, use the addition: VIA SELECTION-SCREEN.
Use the pattern button in the ABAP Editor to insert a program call via SUBMIT. The structure shows you the names of data objects that you can complete with the standard selection screen.
For further information on working with variants and further syntax variants for the WITH addition, see the key word documentation in the ABAP Editor for SUBMIT.
You can use SAP memory and ABAP memory to pass data between different programs.
The SAP memory is a user-specific memory area for storing field values. It is available in all of the open sessions in a user's terminal session, and is reset when the terminal session ends. You can use its contents as default values for screen fields. All external sessions can access SAP memory. This means that it is only of limited use for passing data between internal sessions.
The ABAP memory is also user-specific, and is local to each external session. You can use it to pass any ABAP variables (fields, structures, internal tables, complex objects) between the internal sessions of a single external session.
Each external session has its own ABAP memory. When you end an external session (/i in the command field), the corresponding ABAP memory is released automatically.
To copy a set of ABAP variables and their current values (data cluster) to the ABAP memory, use the EXPORT TO MEMORY ID statement. The (up to 32 characters) is used to identify the different data clusters.
If you repeat an EXPORT TO MEMORY ID statement to an existing data cluster, the new data overwrites the old.
To copy data from ABAP memory to the corresponding fields of an ABAP program, use the IMPORT FROM MEMORY ID statement.
The fields, structures, internal tables, and complex objects in a data cluster in ABAP memory must be declared identically in both the program from which you exported the data and the program into which you import it.
To release a data cluster, use the FREE MEMORY ID statement.
You can import just parts of a data cluster with IMPORT, since the objects are named in the cluster.
In the SAP memory, you can define memory areas (SET/GET parameters, or parameter IDs), which you can then address by a name of up to 20 characters.
You can fill these memory areas either using the contents of input/output fields on screens, or using the ABAP statement:
SET PARAMETER ID '' FIELD .
The memory area with the name now has the value .
You can use the contents of a memory area to display a default value in an input field on a screen.
You can also read the memory areas from the SAP memory using the ABAP statement GET PARAMETER ID FIELD . The field then contains the value from parameter .
The link between an input/output field and a memory area in SAP memory is inherited from the data element on which the field is based. You can enable the set parameter or get parameter attributes in the input/output field attributes.
Once you have set the Set parameter attribute for an input/output field, you can fill it with default values from SAP memory. This is particularly useful for transactions that you call from another program without displaying the initial screen. For this purpose, you must activate the Set parameter functionality for the input fields of the first screen of the transaction.
You can:
(1) Copy the data that is to be used for the first screen of the transaction to be called to the parameter ID in the SAP memory. To do so, use the statement SET PARAMETER immediately before calling the transaction.
(2) Start the transaction using CALL TRANSACTION or LEAVE TO
TRANSACTION . If you do not want to display the initial screen, use the AND
SKIP FIRST SCREEN addition.
(3) The system program that starts the transaction fills the input fields that do not already have default values and for which the Get parameter attribute has been set with values from SAP memory.
The Technical information for the input fields in the transaction you want to call contains the names of the parameter IDs that you need to use.
Parameter IDs should be entered in table TPARA. This happens automatically if you create them via the Object navigator.
Programs that you call using the statements SUBMIT , LEAVE TO TRANSACTION , SUBMIT AND RETURN, or CALL TRANSACTION run in their own SAP LUW, and update requests receive their own update key.
When you use SUBMIT and LEAVE TO TRANSACTION , the SAP LUW of the calling program ends. If no COMMIT WORK statement occurred before the program call, the update requests in the log table remain incomplete and cannot be processed. They can no longer be executed. The same applies to inline changes that you make using PERFORM … ON COMMIT.
Data that you have written to the database using inline changes is committed the next time a new screen is displayed.
If you use SUBMIT AND RETURN or CALL TRANSACTION to insert a program and then return to the calling program, the SAP LUW of the calling program is resumed when the called program ends. The LUW processing of calling and called programs is independent.
In other words, inline changes are committed the next time a new screen is displayed. Update requests and calls using PERFORM ... ON COMMIT require an independent COMMIT WORK statement in the SAP LUW in which they are running.
Function modules run in the same SAP LUW as the program that calls them.
If you call transactions with nested calls, each transaction needs its own COMMIT WORK, since each transaction maps its own SAP LUW.
The same applies to calling executable programs, which are called using SUBMIT AND RETURN.
The statement CALL TRANSACTION allows you to
Shorten the user dialog when calling using CALL TRANSACTION USING .
Determine the type of update (asynchronous, local, or synchronous) for the transaction called. For this purpose, use the addition CALL TRANSACTION USING UPDATE 'update_mode', where update_mode can have the values a (asynchronous), L (local), or S (synchronous).
Combining the two options enables you to call several transactions in sequence (logical chain), to reduce their screen sequence, and to postpone processing of the SAP LUW 2 until processing of the SAP LUW 1 has been completed.
When you call a function module asynchronously using the CALL FUNCTION STARTING NEW TASK ' ' statement, it runs in its own SAP LUW.
Programs that are executed with a SUBMIT AND RETURN or CALL
TRANSACTION statement starts their own LUW processing. You can use these to perform nested (complex) LUW processing.
You can use function modules as modularization units within an SAP LUW.
Function modules that are called asynchronously are suitable for programs that allow parallel processing of some of their components.
All techniques are suitable for including programs with purely display functions.
Note that a function module called with CALL FUNCTION STARTING NEW TASK is executed as a new logon. It, therefore, sees a separate SAP memory area. You can use the interface of the function module for data transfers.
Example: In your program, you want to call a display transaction that is displayed in a separate window (amodal). To do so, you encapsulate the transaction call in a function module, which you set as to Remote-enabled module. You use the function module interface to accept values that you write to the SAP memory. You then call up the transaction in the function module using CALL TRANSACTION AND SKIP FIRST SCREEN. You call the function module itself asynchronously.
Type ‘E' locks for nested program calls may be requested more than once from the same object. This behavior can be described as follows:
Lock entries from function modules called synchronously increment the cumulative counter, And are therefore successful.
Lock entries from programs called with CALL TRANSACTION or SUBMIT
AND
RETURN is refused. The object to be locked by the called program is displayed as already Locked by another user.
Programs that you call using SUBMIT or LEAVE TO TRANSACTION cannot come into conflict with lock entries from the calling program, since the old program ends when the call is made. When a program ends, the system deletes all of the lock entries that it had set.
Lock requests belonging to the same user from different R/3 windows or logons are treated as lock requests from other users.
Regards,
Rajesh.
Please reward points if found helpful.

How I can see the data of my message after processing?

Hi guys,
My scenario is XI -> R/3 (asynchronous) using ABAP Proxy.
When a try to send a message the flag code is ok and the message enters in R/3 inbound queue, so it means that everything ok!
I want to know how I can see my data in queue or better how it enters in proxy and how I can see? In proxy method I put a break point... but can't stop there!!!
What I need to do to make a little test and verify that really works?
Anybody could help?
Thanks in advance,
Ricardo.

Hi Ricardo
If you want to do Debug Asyn Inbound proxy. Do the following steps.
1. Get the Queue-Id from MONI.
2. Deregister the Queue for your message (SMQR).
3. Now resend the message. The message will be stopped in the Deregistered Queue.
4. Start Transaction SMQ2 and select your specific Queue. Double clicking will take you to the detailed level.
5. Press F8 to start the Debugger. And now you can debug the whole Proxy mehtod for Inboud proxy method.
Check the file 'How to Debug XI Applications' for more information.
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
Regards
Paresh

How we can see the data in import id 'LZUT5U11'

HI
Plz observe below code carefully
import lsind
         report_title
         table_name
         report_field
         change_display
         show_hide
         conversion_exits
         table_description
         form_program
         select_form
         update_form
         line_size
         line_count
         records[]
         fields[]
         header_fields[]
         select_fields[]
         xrep[]
         from memory id 'LZUT5U11'.
sy-lsind = lsind.
when i was trying to import the data to above mentioned fields
from memory id 'LZUT5U11' getting dump due to length difference between memory id 'LZUT5U11' and field 'lsind'.
how we can see the field length in memory id 'LZUT5U11'.
Regards
santhosh
[email protected]

For Finance the standard datasources are
0FI_GL_4
0FI_AR_4
0FI_AP_4
Go to R/3 lbwe
select these datasources
click on manage
you will get a window with fields. here in the right hand corner there is a drop down which giives table names
OR
Goto RSA3 and give the datasource name

How I can see what accounts I created with my family pack in my old mobileme account?

Any ideas how I can see what accounts I created with my family pack in my old mobileme account?
i updated it when we need to migrate and all emails are active and being used.
i need to update an email address. we use this for my personal company and need to keep the email in
the same format so it matches the others in the company. i dont see it anywhere in my account now.
i am using a .mac format. thanks.

In order to see which devices are authorized on your account:
Open iTunes
Click Store
Click Account
Click View Account
Enter your password
Look in the second section iTunes in the Cloud
To the far right you'll see Manage Devices
Once it's clicked you will see all of the devices currently authorized in iTunes/on your account
I was going to say, "Hope this helps," but based on the above, I'm pretty sure it did!
Thanks guys...

How we can get an interactive report in alv grid display?

Hi experts
Plz tell me how we can get an interactive report in alv grid disply pls send me one sample code to understand this
thanks in advance

hi,
check this one
*& Report ZALV_FIELD_GRID1
REPORT ZALV_FIELD_GRID1
        NO STANDARD PAGE HEADING.
TABLES MARA.
type-pools :slis.
TYPES : BEGIN OF TMARA ,
        MATNR LIKE MARA-MATNR,
        MEINS LIKE MARA-MEINS,
        ERSDA LIKE MARA-ERSDA,
        color(4) type c,
        SEL type c,
        LIGHT TYPE C,
        END OF TMARA.
TYPES: BEGIN OF TMAKT,
       MATNR LIKE MAKT-MATNR,
       MAKTX LIKE MAKT-MAKTX,
       MAKTG LIKE MAKT-MAKTG,
       SEL TYPE C,
       COLOR(4),
       END OF TMAKT.
DATA: ITAB TYPE TMARA OCCURS 0 WITH HEADER LINE,
       ITAB1 TYPE TMAKT OCCURS 0 WITH HEADER LINE,
       wa_fieldcat type slis_fieldcat_alv,
       fieldcat type slis_fieldcat_alv occurs 0,
       i_layout type slis_layout_alv,
       WA_LISTHEADER TYPE SLIS_LISTHEADER,
       i_LISTHEADER TYPE SLIS_LISTHEADER OCCURS 0,
       V_EVENTS TYPE SLIS_T_EVENT ,
       WA_EVENT TYPE SLIS_ALV_EVENT,
       I_TITLE_MARA TYPE LVC_TITLE VALUE 'FIRST LIST DISPLAYED',
       I_TITLE_MAKT TYPE LVC_TITLE VALUE 'SECONDRY LIST DISPLAYED',
       SORT TYPE slis_t_sortinfo_alv WITH HEADER LINE,
       PRINT_CONT type slis_print_alv.
SELECTION SCREE
selection-screen begin of block screen1 with frame title TEXT-001.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN COMMENT /32(35) COMM1.
SELECTION-SCREEN ULINE /27(35).
SELECTION-SCREEN SKIP.
SELECT-OPTIONS MATNR FOR MARA-MATNR.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN ULINE.
SELECTION-SCREEN COMMENT /30(50) COMM2.
SELECTION-SCREEN ULINE /27(40).
SELECTION-SCREEN SKIP.
SELECT-OPTIONS ERSDA FOR MARA-ERSDA.
SELECTION-SCREEN SKIP.
selection-screen end of block screen1.
    INITIALIZATION
INITIALIZATION.
MATNR-low = '23'.
MATNR-high = '1000'.
MATNR-option = 'BT'.
MATNR-sign = 'I'.
APPEND MATNR.
ERSDA-low = '20030124'.
ERSDA-high = '20050302' .
APPEND ERSDA.
PERFORM FILLFIELD.
PERFORM FILLLAYOUT.
PERFORM build_print_params.
PERFORM FILL_SORT.
PERFORM EVENT_CALL.
PERFORM POPULATE_EVENT.
        SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN OUTPUT.
comm1 ='SELECT MATERIAL NUMBER RANGE'.
comm2 ='SELECT MATERIAL CREATION DATE'.
           START-OF-SELECTION
START-OF-SELECTION.
PERFORM READDATA.
PERFORM POPDATA.
*&      Form READDATA
      text
FORM READDATA .
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      INPUT = MATNR-LOW
    IMPORTING
      OUTPUT = MATNR-LOW.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      INPUT = MATNR-HIGH
    IMPORTING
      OUTPUT = MATNR-HIGH.
SELECT MATNR
         ERSDA
         MEINS
         FROM MARA
         INTO CORRESPONDING FIELDS OF
        TABLE ITAB
        WHERE MATNR IN MATNR AND ERSDA IN ERSDA.
LOOP AT ITAB.
    data id_color type i VALUE 1.
    data id_colors(2) type c.
    IF ITAB-MATNR < '000000000000000100'.
      ITAB-LIGHT = '1'.
    ELSEIF ITAB-MATNR < '000000000000000150' AND ITAB-MATNR >
   '000000000000000100' .
      ITAB-LIGHT = '2'.
    ELSE.
      ITAB-LIGHT = '3'.
    ENDIF.
    id_color = id_color + 1.
    if id_color > 7.
      id_color = 1.
    endif.
    id_colors = id_color.
    concatenate 'C' id_colors '10' into itab-color.
    modify itab.
    CLEAR ITAB.
endloop.
ENDFORM.                    " READDATA
     Form FILLFIELD
FORM FILLFIELD .
WA_FIELDCAT-FIELDNAME = 'MATNR'.
WA_FIELDCAT-KEY = 'X'.
WA_FIELDCAT-COL_POS = '1'.
WA_FIELDCAT-outputlen   = 20.
WA_FIELDCAT-HOTSPOT = 'X'.
wa_fieldcat-seltext_m = 'MATERIAL NUMBER'.
*WA_FIELDCAT-EMPHASIZE = 'C210'.
APPEND WA_FIELDCAT TO FIELDCAT.
clear wa_fieldcat.
WA_FIELDCAT-FIELDNAME = 'MEINS'.
WA_FIELDCAT-COL_POS = '2'.
*WA_FIELDCAT-EMPHASIZE = 'C510'.
WA_FIELDCAT-outputlen   = 10.
wa_fieldcat-seltext_m = 'UNIT'.
APPEND WA_FIELDCAT TO FIELDCAT.
clear wa_fieldcat.
WA_FIELDCAT-FIELDNAME = 'ERSDA'.
WA_FIELDCAT-COL_POS = '3'.
WA_FIELDCAT-outputlen   = 15.
*WA_FIELDCAT-EDIT_MASK = 'DD.MM.YYYY'.
*WA_FIELDCAT-EMPHASIZE = 'C710'.
wa_fieldcat-seltext_m = 'CREAT DATE'.
APPEND WA_FIELDCAT TO FIELDCAT.
clear wa_fieldcat.
ENDFORM.                    "FILLFIELD
      Setup print parameters
form build_print_params.
PRINT_CONT-reserve_lines = '3'.   "Lines reserved for footer
PRINT_CONT-no_coverpage = 'X'.
endform.                    " BUILD_PRINT_PARAMS
     Form POPDATA
FORM POPDATA .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
I_INTERFACE_CHECK                 = ' '
I_BYPASSING_BUFFER                = ' '
I_BUFFER_ACTIVE                   = ' '
     I_CALLBACK_PROGRAM                 = sy-repid
I_CALLBACK_PF_STATUS_SET          = ' '
     I_CALLBACK_USER_COMMAND            = 'USER-COMMAND'
     I_CALLBACK_TOP_OF_PAGE             = 'TOPPAGE'
I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
I_CALLBACK_HTML_END_OF_LIST       = ' '
I_STRUCTURE_NAME                  =
I_BACKGROUND_ID                   = ' '
     I_GRID_TITLE                       = I_TITLE_MARA
I_GRID_SETTINGS                   =
     IS_LAYOUT                          = I_LAYOUT
     IT_FIELDCAT                        = fieldcat
IT_EXCLUDING                      =
IT_SPECIAL_GROUPS                 =
    IT_SORT                           = SORT[]
IT_FILTER                         =
IS_SEL_HIDE                       =
I_DEFAULT                         = 'X'
I_SAVE                            = ' '
IS_VARIANT                        =
     IT_EVENTS                          = V_EVENTS
IT_EVENT_EXIT                     =
   IS_PRINT                          = PRINT_CONT
    TABLES
      T_OUTTAB                          = ITAB
EXCEPTIONS
   PROGRAM_ERROR                     = 1
   OTHERS                            = 2
ENDFORM.                    " POPDATA
     Form TOPPAGE
FORM TOPPAGE.
REFRESH I_LISTHEADER.
DATA: ld_lines type i,
        ld_linesc(10) type c,
        I_DATE(10) TYPE C,
        I_INFO LIKE WA_LISTHEADER-INFO.
WA_LISTHEADER-TYP = 'H'.
WA_LISTHEADER-INFO = 'MATERIAL DETAIL'.
APPEND WA_LISTHEADER TO I_LISTHEADER.
CLEAR WA_LISTHEADER.
WA_LISTHEADER-TYP = 'S'.
WA_LISTHEADER-KEY = 'DATE :'.
CONCATENATE SY-DATUM+6(2) '.'
                       SY-DATUM+4(2) '.'
                       SY-DATUM(4) INTO I_DATE.
WA_LISTHEADER-INFO = I_datE.
APPEND WA_LISTHEADER TO I_LISTHEADER.
CLEAR WA_LISTHEADER.
describe table ITAB lines ld_lines.
ld_linesc = ld_lines.
concatenate 'TOTAL NUMBER OF RECORD SELECTED: ' ld_linesc
                    into I_INFO separated by space.
WA_LISTHEADER-TYP = 'A'.
WA_LISTHEADER-INFO = I_INFO.
append WA_LISTHEADER to I_LISTHEADER.
clear: WA_LISTHEADER , I_INFO.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY = I_LISTHEADER
      I_LOGO             = 'ENJOYSAP_LOGO'.
ENDFORM.                    "TOPPAGE
     Form FILLLAYOUT
FORM FILLLAYOUT .
i_layout-zebra = 'X'.
i_layout-info_fieldname = 'COLOR'.
i_layout-box_fieldname = 'SEL'.
I_LAYOUT-lights_fieldname = 'LIGHT'.
I_LAYOUT-EDIT ='X'.
I_LAYOUT-colwidth_optimize = 'X'.
I_LAYOUT-window_titlebar = 'EXAMPLE FOR ALV GRID'.
I_LAYOUT-no_totalline = 'X'.
ENDFORM.                    "FILLLAYOUT
    Form FILL_SORT
FORM FILL_SORT .
SORT-DOWN = 'X'.
SORT-SPOS = 1.
SORT-FIELDNAME = 'MATNR'.
SORT-tabname = 'MARA'.
APPEND SORT.
ENDFORM.                    " FILL_SORT
     Form EVENT_CALL
FORM EVENT_CALL .
DATA: I_EVENT LIKE V_EVENTS.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      I_LIST_TYPE = 0
    IMPORTING
      ET_EVENTS   = V_EVENTS.
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " EVENT_CALL
    Form POPULATE_EVENT
FORM POPULATE_EVENT .
READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'USER_COMMAND'.
IF SY-SUBRC EQ 0.
    WA_EVENT-FORM = 'USER_COMMAND'.
    MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
    WA_EVENT-NAME.
READ TABLE V_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE
                                      INTO WA_EVENT.
IF SY-SUBRC = 0.
   move 'END_OF_PAGE' to WA_EVENT-FORM.
   MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
   WA_EVENT-NAME.
endif.
ENDIF.
ENDFORM.                    "POPULATE_EVENT
FORM END_OF_PAGE.
write: sy-uline(50).
skip.
write:/40 'Page:', sy-pagno .
ENDFORM.
*&      Form USER_COMMAND
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
RS_SELFIELD TYPE SLIS_SELFIELD.
CASE R_UCOMM.
    WHEN '&IC1'.
      CASE RS_SELFIELD-FIELDNAME.
        when 'MATNR'.
          read table itab with key matnr = RS_SELFIELD-VALUE.
          if sy-subrc = 0.
            PERFORM DATA_RETRIEVAL_MAKT USING RS_SELFIELD-VALUE.
            PERFORM BUILD_FIELDCATLOG_MAKT.
            PERFORM FILLLAYOUT_MAKT.
            PERFORM DISPLAY_ALV_MAKT.
            CLEAR RS_SELFIELD.
          ENDIF.
      ENDCASE.
ENDCASE.
ENDFORM.                    "user_command
     Form DATA_RETRIEVAL_MAKT
FORM DATA_RETRIEVAL_MAKT USING TMATNR .
SELECT MATNR
         MAKTX
         MAKTG
         UP TO 100 ROWS
         FROM MAKT
         INTO TABLE ITAB1
         WHERE SPRAS = 'EN' AND MATNR = TMATNR.
LOOP AT ITAB1.
    data id_color type i VALUE 1.
    data id_colors(2) type c.
    id_color = id_color + 1.
    if id_color > 7.
      id_color = 1.
    endif.
    id_colors = id_color.
    concatenate 'C' id_colors '10' into itab1-color.
    modify itab1.
    CLEAR ITAB1.
ENDLOOP.
ENDFORM.                    "DATA_RETRIEVAL_MAKT
     Form FILLLAYOUT_MAKT
FORM FILLLAYOUT_MAKT .
CLEAR I_LAYOUT.
i_layout-zebra = 'X'.
i_layout-info_fieldname = 'COLOR'.
i_layout-box_fieldname = 'SEL'.
I_LAYOUT-EDIT ='X'.
I_LAYOUT-colwidth_optimize = 'X'.
I_LAYOUT-window_titlebar = 'EXAMPLE FOR ALV GRID'.
ENDFORM.                    " LAYOUT_MAKT
    Form BUILD_FIELDCATLOG_MAKT
FORM BUILD_FIELDCATLOG_MAKT .
REFRESH FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'MATNR'.
WA_FIELDCAT-KEY = 'X'.
WA_FIELDCAT-COL_POS = '1'.
*WA_FIELDCAT-EDIT_MASK = 'DD.MM.YYYY'.
WA_FIELDCAT-EMPHASIZE = 'C510'.
wa_fieldcat-seltext_m = 'MATERIAL NUMBER'.
APPEND WA_FIELDCAT TO FIELDCAT.
clear wa_fieldcat.
WA_FIELDCAT-FIELDNAME = 'MAKTX'.
WA_FIELDCAT-COL_POS = '2'.
WA_FIELDCAT-EMPHASIZE = 'C710'.
wa_fieldcat-seltext_m = 'MATERIAL DESCRIPTION'.
APPEND WA_FIELDCAT TO FIELDCAT.
clear wa_fieldcat.
WA_FIELDCAT-FIELDNAME = 'MAKTG'.
WA_FIELDCAT-COL_POS = '3'.
WA_FIELDCAT-EMPHASIZE = 'C210'.
wa_fieldcat-seltext_m = 'MATERIAL DESCRIPTION'.
APPEND WA_FIELDCAT TO FIELDCAT.
clear wa_fieldcat.
ENDFORM.                    " BUILD_FIELDCATLOG_MAKT
     Form DISPLAY_ALV_MAKT
FORM TOP-OF-PAGE.
REFRESH I_LISTHEADER.
DATA: ld_lines type i,
        ld_linesc(10) type c,
        I_DATE(10) TYPE C,
        I_INFO LIKE WA_LISTHEADER-INFO.
WA_LISTHEADER-TYP = 'H'.
WA_LISTHEADER-INFO = 'MATERIAL DESCRIPTION FOR SELECTED NUMBER'.
APPEND WA_LISTHEADER TO I_LISTHEADER.
CLEAR WA_LISTHEADER.
WA_LISTHEADER-TYP = 'S'.
WA_LISTHEADER-KEY = 'DATE :'.
CONCATENATE SY-DATUM+6(2) '.'
                       SY-DATUM+4(2) '.'
                       SY-DATUM(4) INTO I_DATE.
WA_LISTHEADER-INFO = I_datE.
APPEND WA_LISTHEADER TO I_LISTHEADER.
CLEAR WA_LISTHEADER.
describe table ITAB1 lines ld_lines.
ld_linesc = ld_lines.
concatenate 'TOTAL NUMBER OF RECORD SELECTED: ' ld_linesc
                    into I_INFO separated by space.
WA_LISTHEADER-TYP = 'A'.
WA_LISTHEADER-INFO = I_INFO.
append WA_LISTHEADER to I_LISTHEADER.
clear: WA_LISTHEADER , I_INFO.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY = I_LISTHEADER
      I_LOGO             = 'ENJOYSAP_LOGO'.
I_END_OF_LIST_GRID       =
I_ALV_FORM               =
ENDFORM.                    "TOP-OF-PAGE
*&      Form DISPLAY_ALV_MAKT
      text
FORM DISPLAY_ALV_MAKT .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM     = SY-REPID
      I_CALLBACK_TOP_OF_PAGE = 'TOP-OF-PAGE'
      I_GRID_TITLE           = I_TITLE_MAKT
      IS_LAYOUT              = I_LAYOUT
      IT_FIELDCAT                       = fieldcat
    TABLES
      T_OUTTAB               = ITAB1
    EXCEPTIONS
      PROGRAM_ERROR          = 1
      OTHERS                 = 2.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " DISPLAY_ALV_MAKT
Rewards points

How i can see the calendar appoinments one year ago.

How i can see the appoinments one year old, thanks.

Scroll through the calendar back in time and look at them.

How we can see logged in portal user

hello SAP EP gurus,
How i can know how man users are logged on my EP Portal and which user is using which report.Is there any way to find out this thing.?
Also how we can see the performance of our portal?
Waiting for earliest reply.
regards
Neeraj Pandey

Hi,
You can use " portal Activity Report" for this purpose.
alternatively, if you have access to server you can check this through visual admin
simply open visual admin,open on your servernode --services,click on Performance Tracing,click on JARM and choose what you want to see.
its easy to use standard portal Activity Report.
else you can use third party reports loke "google analytics" which will give the number of users logged in, what the navigation of each user, from which geographical area the user has logged in and all about the user logged into the portal and portal performance.
you need to login with your gmail id and password and download the code and use it in you portal application... its very easy to use.
https://www.google.com/analytics/home/
PradeeP

How we can see when the condition records created.

Hi,
How we can see when the condition records created ( Valid from and Valid to ) ? And also how we can see the changes made in the Condition records?
Regards,
jyothi.

Hello,
you can display the condtion records in transaction VK13.
Here you have the posibillity to display the changes of the condtion records.
Please goto VK13
> Enter your selection criteria
> Enviroment
> changes
But you can also create a condtion list. and the you can display more than one condition record:
Please have a look at the transation V/LD - Pricing Report
For example: conditon list 14 for taxes.
Here you get an overview of tax condtions.
I hope that the information are helpful.
Regards
Claudia
If you are satisfied with the answer, please give Reward Points.

How we can see the data related to finance ??

Hi Gurus,
I have attend for one interview and faced one question is that how can we see the finance related data in r/3?
they asked the same question.
can you please let me know how we can see the data for perticular module like HR,FInance...
Points 'll be assigned..
Regards,
Syam

For Finance the standard datasources are
0FI_GL_4
0FI_AR_4
0FI_AP_4
Go to R/3 lbwe
select these datasources
click on manage
you will get a window with fields. here in the right hand corner there is a drop down which giives table names
OR
Goto RSA3 and give the datasource name

How i can see a page without logon to the portal

Who knows how i can see a pge without logon to the portal?
Thanks anyway

i don't understand your, but
my users login to page by portlet on all pages or custom login page.
pl/sql portlet on all page:
put pl/sql portlet on page
pl/sql text:
begin
if portal.wwctx_api.is_logged_on then
htp.p('<center>logout<center><br>');
else
htp.p('<table BORDER="1" WIDTH="100%" CELLPADDING="2" CELLSPACING="0" class="RegionBorder">
<tr><td class="RegionHeaderColor" WIDTH="100%"><script TYPE="text/javascript">

</script>
<form ACTION="PORTAL.wwptl_login.login_url" METHOD="POST" name="LoginForm" AutoComplete="Off" onSubmit="loginsubmit()">
<input TYPE="hidden" NAME="p_requested_url" VALUE="http://your.curent.name">
<input TYPE="hidden" NAME="p_cancel_url" VALUE="http://your.curent.name">
<input TYPE="hidden" NAME="uname" VALUE="">
<input TYPE="hidden" NAME="pwd" VALUE="">
<table ALIGN="center">
<tr>
<td><font class="PortletText1">name</font></td>
<td><input TYPE="text" NAME="ssousername" SIZE="10" MAXLENGTH="80" style="font-size:10px;"></td>
</tr>
<td><font class="PortletText1">password</font></td>
<td><input TYPE="password" NAME="password" SIZE="10" MAXLENGTH="255" style="font-size:10px;"></td>
</tr>
</table>
<center>
<input TYPE="submit" VALUE="Registration">
</center>
</form></td></tr></table>');
end if;
end;
set show directly in page.
good luck ?:(

Does any one know how i can see the percentage of battery left on my iphone

Does any one know how i can see the percentage of battery left on my iphone? at the moment i can only tell by looking at the small battery symbol in the corner of the screen. How ever this does not indicate a percentage!

No, it won't.
Apple is keeping that feature for the new iPhone 3GS ONLY.
if you have an iPhone or an iPhone 3G, you will not get this feature.

HT201274 how I can see my devices in the Itunes

I can' t see my devices in the iTunes only the store or the players, how I can see my device to have control and sync.

Topherinduont wrote:
I can see my purchases (movies specifically) in the ITunes Store when I filter to purchased but when I try to down load the movie it starts to down load and then says Unable to Download Error Code 5105. Can anyone help?
Hi, I had this problem when I first went to use iTunes with iCloud. using Windows 8 OS. Everytime I tried to download from iCloud error 5105 came up... not sure this will work for everyone, but pretty simple, I closed iTunes and restarted it and everything worked fine

HT201317 how i can see the photos on i clouds

How i can see my deleted pictures from iphone which is not sync to back up

You can't see photos on iCloud. If they are photo stream photos you can only see them on a device that is signed into your iCloud account with photo stream turned off.
If the deleted photos were in your camera roll when you last backed it up, restoring the entire backup would recover them.

How we can see application log

i have created a application log and put messages in that..
how we can see that application log..
thanks and regards......

Hi Sharada,
Use   CALL FUNCTION 'BAL_DSP_LOG_DISPLAY' to display the application log. Displaying application log can be possible in many ways, as a popup window, as normaal one ,as tree. YOu can play around with APPLICATION with these standard programs.
SBAL_DEMO_01
SBAL_DEMO_02
SBAL_DEMO_03
SBAL_DEMO_04
SBAL_DEMO_04_*
SBAL_DEMO_05
Still if you any need any more on this , let me know.
<b>Example Program</b>
* create a log where all message should be added to
PERFORM log_create.
* Add information that this is a check for passenger flights
* this informnation can be added as a free text
PERFORM msg_add_free_text USING text-002.
    PERFORM msg_add_free_text USING text-003.
* display log file
PERFORM log_display.
* FORM LOG_CREATE
FORM log_create.
DATA:
    l_s_log TYPE bal_s_log.
* define some header data of this log
l_s_log-extnumber = 'Application Log Demo'.             "#EC NOTEXT
l_s_log-aluser    = sy-uname.
l_s_log-alprog    = sy-repid.
* create a log
CALL FUNCTION 'BAL_LOG_CREATE'
       EXPORTING
            i_s_log = l_s_log
       EXCEPTIONS
            OTHERS = 1.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.
* FORM MSG_ADD_FREE_TEXT
FORM msg_add_free_text USING value(i_text) TYPE c.
* add this message to log file
* (I_LOG_HANDLE is not specified, we want to add to the default log.
* If it does not exist we do not care =>EXCEPTIONS log_not_found = 0)
CALL FUNCTION 'BAL_LOG_MSG_ADD_FREE_TEXT'
       EXPORTING
*           I_LOG_HANDLE =
            i_msgty       = 'S'
            i_text        = i_text
       EXCEPTIONS
            LOG_NOT_FOUND = 0
            OTHERS        = 1.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.
* FORM LOG_DISPLAY
FORM log_display.
DATA:
    l_s_display_profile TYPE bal_s_prof,
    l_s_fcat            TYPE bal_s_fcat.
* get a prepared profile
CALL FUNCTION 'BAL_DSP_PROFILE_POPUP_GET'
       IMPORTING
            e_s_display_profile = l_s_display_profile
       EXCEPTIONS
            OTHERS              = 1.
IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* show log file with modified output profile
* - we specify the display profile since we created our own
* - we do not specify any filter (like I_S_LOG_FILTER, ...,
*   I_T_MSG_HANDLE) since we want to display all messages available
CALL FUNCTION 'BAL_DSP_LOG_DISPLAY'
       EXPORTING
*           I_S_LOG_FILTER         =
*           I_T_LOG_CONTEXT_FILTER =
*           I_S_MSG_FILTER         =
*           I_T_MSG_CONTEXT_FILTER =
*           I_T_LOG_HANDLE         =
*           I_T_MSG_HANDLE         =
            i_s_display_profile    = l_s_display_profile
       EXCEPTIONS
            OTHERS                 = 1.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Regards,
Raghav

How I can see my interactive button on a tablet or smartphone?

Similar Messages

Maybe you are looking for