Output format of a number/BISMT

Hi experts,
i want to have the follwing:
I have the BISTM of a material, when I show this in a textview it is shown like '04560214521'
But I want to display it as '04560 214 512' => BISMT(5) BISMT5(3) BISMT8(3)
How to achieve this (without making a new string field)?
Is there a way?
Thanks
Michael

Hi Michael,
I suggest to work at DDIC (SE11) level.
You should:
1. copy CONVERSION_EXIT_ALPHA_INPUT to CONVERSION_EXIT_ZBISMT_INPUT
2. copy CONVERSION_EXIT_ALPHA_OUTPUT to CONVERSION_EXIT_ZBISMT_OUPUT and modify it to apply the required formatting.
3. copy domain BISMT to ZSDN_BISMT attaching the newly created conversion exit (have a look your
   [http://screencast.com/t/ODZmYjlhMzEt|http://screencast.com/t/ODZmYjlhMzEt] )
4. reading the help of the field Convers. Routine you should get the idea
  Then WDA simply will use the conversion exit like SAPGui does.
Sergio

Similar Messages

  • Output Format of Product Number

    Hi,
    This is pertaining to issue with Product Number, I am CIFing numeric product.
    I am trying to CIF 8 digit Product code from ECC to APO and its getting CIFed as 18 digit code in /SAPAPO/MATMAP table in Extnr Material Number field, while displaying MAT1 its showing as only 8 digit.
    I then changed the settings to Field length 18 and activated the lexicographical check in spro in produt master data and also the same setting in OMSL transaction code.
    But when I activate the CIF queue with this setting it gives me an error that Product field length is less.
    I then changed the spro setting and configured the lenghth as 40 and in OMSL its 18, now the product is getting CIFed with leading zeroes and is also displayed with leading zeroes.
    My requirement is that the produt should get CIFed as 8 digit and should also be diaplayed in the table as 8 digit.
    Can someone please tell me what should be the setting in spro and OMSL transaction so that their are no leading zeroes displayed and also in SAP table its not stored with leading zeroes.
    When I create the product directly in APO their are no leading zeroes in table and display.
    Thanks & Regards,
    Sanjog mishrikotkar

    Hi Sanjog,
    The following are the settings where the output format of a
    product number will be maintained
    In R/3, the lexicographic setting will be done in spro>logistics-general>
    material master>basic settings>define output format of material numbers.
    In APO, it is done at spro>APO>Master data>Product>specify output format
    of product numbers.
    Hope this will resolve your issue.
    Please confirm
    Regards
    R. Senthil Mareeswaran.

  • How to get this output format in ALV report

    Hi.
    Can any one pls let me know how to get the following output format in ALV report.Following are the outputfields
    companycode   location     position     approver
    300    800       01    watson
    null   null        03     candy
    null   null        04     smith
    null   null        05     michael
    one empty line after this again
    300     800     01     ryant
    null      null    02     gyan
    null      null    03     fermi
    null      null    04     ogata
    *Note: Null     indicates  empty space .( i.e I need to get empty space in  output where ever null is there.)
            Thanks in advance.
    Kind Regards,
    samiulla.

    hi,
    u can use 'REUSE_ALV_LIST_DISPLAY'
                           or
    'REUSE_ALV_GRID_DISPLAY'  function modules.
    SAMPLE CODE :
    *& Report  Y101982CHD
    *                         TABLES
    TABLES: vbak.    " standard table
    *                           Type Pools                                 *
    TYPE-POOLS: slis.
    *                     Global Structure Definitions                     *
    *-- Structure to hold data from table CE1MCK2
    TYPES: BEGIN OF tp_itab1,
           vbeln LIKE vbap-vbeln,
           posnr LIKE vbap-posnr,
           werks LIKE vbap-werks,
           lgort LIKE vbap-lgort,
           END OF tp_itab1.
    *-- Data Declaration
    DATA: t_itab1 TYPE TABLE OF tp_itab1.
    DATA : i_fieldcat TYPE slis_t_fieldcat_alv.
    *                    Selection  Screen                                 *
    *--Sales document-block
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-t01.
    SELECT-OPTIONS: s_vbeln FOR vbak-vbeln.
    SELECTION-SCREEN END OF  BLOCK b1.
    *--Display option - block
    SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-t02.
    PARAMETERS: alv_list RADIOBUTTON GROUP g1,
                alv_grid RADIOBUTTON GROUP g1.
    SELECTION-SCREEN END OF  BLOCK b2.
    *file download - block
    SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-t03.
    PARAMETERS: topc AS CHECKBOX,
                p_file TYPE rlgrap-filename.
    SELECTION-SCREEN END OF  BLOCK b3.
    *                      Initialization.                                *
    *                      At Selection Screen                            *
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      CALL FUNCTION 'F4_DXFILENAME_4_DYNP'
        EXPORTING
          dynpfield_filename = 'P_FILE'
          dyname             = sy-cprog
          dynumb             = sy-dynnr
          filetype           = 'P'      "P-->Physical
          location           = 'P'     "P Presentation Srever
          server             = space.
    AT SELECTION-SCREEN ON s_vbeln.
      PERFORM vbeln_validate.
    *                           Start Of Selection                         *
    START-OF-SELECTION.
    *-- Fetching all the required data into the internal table
      PERFORM select_data.
    *                           End Of Selection                           *
    END-OF-SELECTION.
      IF t_itab1[] IS NOT INITIAL.
        IF topc IS NOT INITIAL.
          PERFORM download.
          MESSAGE 'Data Download Completed' TYPE 'S'.
        ENDIF.
        PERFORM display.
      ELSE.
        MESSAGE 'No Records Found' TYPE 'I'.
      ENDIF.
    *                           Top Of Page Event                          *
    TOP-OF-PAGE.
    *& Form           :      select_data
    * Description     : Fetching all the data into the internal tables
    *  parameters    :  none
    FORM select_data .
      SELECT vbeln
         posnr
         werks
         lgort
         INTO CORRESPONDING  FIELDS OF TABLE t_itab1
         FROM vbap
         WHERE  vbeln IN s_vbeln.
      IF sy-subrc <> 0.
        MESSAGE 'Enter The Valid Sales Document Number'(t04) TYPE 'I'.
        EXIT.
      ENDIF.
    ENDFORM.                    " select_data
    *& Form        : display
    *  decription  : to display data in given format
    * parameters   :  none
    FORM display .
      IF alv_list = 'X'.
        PERFORM build_fieldcat TABLES i_fieldcat[]
                               USING :
    *-Output-field Table      Len  Ref fld Ref tab Heading    Col_pos
       'VBELN'       'T_ITAB1'     10   'VBAP'  'VBELN'    ''            1,
       'POSNR'       'T_ITAB1'     6    'VBAP'  'POSNR'    ''            2,
       'WERKS'       'T_ITAB1'     4    'VBAP'  'WERKS'    ''            3,
       'LGORT'       'T_ITAB1'     4    'VBAP'  'LGORT'    ''            4.
        *CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'*
          *EXPORTING*
            *i_callback_program       = sy-repid*
    **        i_callback_pf_status_set = c_pf_status*
            *i_callback_user_command  = 'USER_COMMAND '*
    **        it_events                = t_alv_events[]*
            *it_fieldcat              = i_fieldcat[]*
          *TABLES*
            *t_outtab                 = t_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.*
      ENDIF.
      IF alv_grid = 'X'.
        PERFORM build_fieldcat TABLES i_fieldcat[]
                                 USING :
    *-Output-field Table      Len  Ref fld Ref tab Heading    Col_pos
         'VBELN'       'T_ITAB1'     10   'VBAP'  'VBELN'    ''            1,
         'POSNR'       'T_ITAB1'     6    'VBAP'  'POSNR'    ''            2,
         'WERKS'       'T_ITAB1'     4    'VBAP'  'WERKS'    ''            3,
         'LGORT'       'T_ITAB1'     4    'VBAP'  'LGORT'    ''            4.
        *CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'*
          *EXPORTING*
            *i_callback_program       = sy-repid*
    **        i_callback_pf_status_set = c_pf_status*
            *i_callback_user_command  = 'USER_COMMAND '*
            *it_fieldcat              = i_fieldcat*
          *TABLES*
            *t_outtab                 = t_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.*
      *ENDIF.*
    ENDFORM.                    " display
    *& Form        : vbeln_validate
    *  description : to validate sales document number
    * parameters   :  none
    FORM vbeln_validate .
      DATA: l_vbeln TYPE vbak-vbeln.
      SELECT SINGLE vbeln
        FROM vbak
        INTO l_vbeln
        WHERE vbeln IN s_vbeln.
      IF sy-subrc NE 0.
        MESSAGE 'ENTER THE VALID SALES DOCUMENT NO:' TYPE 'I'.
        EXIT.
      ENDIF.
    ENDFORM.                    " vbeln_validate
    *& Form       :build_fieldcat
    * Description : This routine fills field-catalogue
    *  Prameters  : none
    FORM build_fieldcat TABLES  fpt_fieldcat TYPE slis_t_fieldcat_alv
                        USING   fp_field     TYPE slis_fieldname
                                fp_table     TYPE slis_tabname
                                fp_length    TYPE dd03p-outputlen
                                fp_ref_tab   TYPE dd03p-tabname
                                fp_ref_fld   TYPE dd03p-fieldname
                                fp_seltext   TYPE dd03p-scrtext_l
                                fp_col_pos   TYPE sy-cucol.
    *-- Local data declaration
      DATA:   wl_fieldcat TYPE slis_fieldcat_alv.
    *-- Clear WorkArea
      wl_fieldcat-fieldname       = fp_field.
      wl_fieldcat-tabname         = fp_table.
      wl_fieldcat-outputlen       = fp_length.
      wl_fieldcat-ref_tabname     = fp_ref_tab.
      wl_fieldcat-ref_fieldname   = fp_ref_fld.
      wl_fieldcat-seltext_l       = fp_seltext.
      wl_fieldcat-col_pos         = fp_col_pos.
    *-- Update Field Catalog Table
      APPEND wl_fieldcat  TO  fpt_fieldcat.
    ENDFORM.                    "build_fieldcat
    *& Form        : download
    *  description : To Download The Data
    *  Parameters  :  none
    FORM download .
      DATA: l_file TYPE string.
      l_file = p_file.
      CALL FUNCTION 'GUI_DOWNLOAD'
        EXPORTING
          filename                = l_file
          filetype                = 'ASC'
        TABLES
          data_tab                = t_itab1
        EXCEPTIONS
          file_write_error        = 1
          no_batch                = 2
          gui_refuse_filetransfer = 3
          invalid_type            = 4
          no_authority            = 5
          unknown_error           = 6.
      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.                    " download
    HOPE IT WILL HELP YOU
    REGARDS
    RAHUL SHARMA

  • Query Output Formatting Help

    Hello All,
    I'm having problems trying to format the output of one of my queries. I'm new to SQL and I consider my writing the query a HUGE win.... but I can't seem to get the correct output format.
    Per the code below, it is outputting the Last Name (lname) of the employee, a count of what I want, and the overall rank.  I would like to concatenate the employee number (emp#) the first (fname) and last name (lname) together into the same column in the output.
    The concatenation code would be something like the below.
    Desired concatenation:
    emp# || ' - ' || lname || ', ' || fname AS EMPLOYEE
    I'm using Oracle 11g Express. Please let me know if you need any supporting information to assist you.
    I appreciate all your help!!! Thank you.
    Query
    SELECT EMPLOYEE, PREPARED,
    RANK() OVER (ORDER BY Prepared DESC) AS rank
    FROM (SELECT lname EMPLOYEE , COUNT(DISTINCT reportnum) PREPARED
          FROM employee
          LEFT OUTER JOIN faultreport USING (empno)
          GROUP BY lname
          ORDER BY Prepared DESC)
    WHERE rownum < 15;

    Hi,
    8bb7968b-e6ae-456c-8459-f418352e9e0a wrote:
    Hello All,
    I'm having problems trying to format the output of one of my queries. I'm new to SQL and I consider my writing the query a HUGE win.... but I can't seem to get the correct output format.
    Per the code below, it is outputting the Last Name (lname) of the employee, a count of what I want, and the overall rank.  I would like to concatenate the employee number (emp#) the first (fname) and last name (lname) together into the same column in the output.
    The concatenation code would be something like the below.
    Desired concatenation:
    emp# || ' - ' || lname || ', ' || fname AS EMPLOYEE
    I'm using Oracle 11g Express. Please let me know if you need any supporting information to assist you.
    Whenever you have a problem, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) for all the tables involved, and the results you want from that data.
    Explain, using specific examples, how you get those results from that data.
    Always say what version of Oracle you're using (e.g. 11.2.0.2.0).
    See the forum FAQ: https://forums.oracle.com/message/9362002
    I appreciate all your help!!! Thank you.
    Query
    SELECT EMPLOYEE, PREPARED,
    RANK() OVER (ORDER BY Prepared DESC) AS rank
    FROM (SELECT lname EMPLOYEE , COUNT(DISTINCT reportnum) PREPARED
          FROM employee
          LEFT OUTER JOIN faultreport USING (empno)
          GROUP BY lname
          ORDER BY Prepared DESC)
    WHERE rownum < 15;
    It looks like you've found the right way to concatenate the columns.  How to use that in your query depends on your data, and what you want the query to do with that data.
    If you GROUP BY lname, what do you want the concatenated value to be when different rows having the same lname have different fnames and/or emp#s?
    Do you want to GROUP BY the new concatenated employee instead of lname?

  • ALV output FORMAT

    HI
    I WANT OUTPUT FORMAT IN THIS WAY
    number         1___nar _  __1__REV____1________________1______________1
                        1   S  1   Q   1     S  1  Q  1              1            1        1               1
    Suggest me how to write this

    <b>is your problem solved????</b>
    u marked as solved..
    its ok kkk

  • Help : Complex Output Format

    Hi there
    Using Data in TAB_DTL for an APPID, I need to generate a Report in the following format.
    CREATE TABLE TAB_DTL
    APPDATE          DATE,
    AMOUNT          NUMBER(12,2),
    STATUS          VARCHAR2(1),
    RATE          NUMBER(5,2)
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '13/09/2011 10:50:45 AM','DD/MM/YYYY HH:MI:SS AM'), 500000, 'D', 13 );
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '09/11/2011 1:15:30 PM','DD/MM/YYYY HH:MI:SS AM'), 5000, 'R', 13 );
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '15/12/2011 3:20:31 PM','DD/MM/YYYY HH:MI:SS AM'), 5000, 'R', 13 );
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '05/01/2012 10:25:11 AM','DD/MM/YYYY HH:MI:SS AM'), 5000, 'R', 13 );
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '02/02/2012 4:23:34 PM','DD/MM/YYYY HH:MI:SS AM'), 5000, 'R', 13 );
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '05/03/2012 11:15:45 AM','DD/MM/YYYY HH:MI:SS AM'), 5000, 'R', 13 );
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '30/03/2012 11:55:10 AM','DD/MM/YYYY HH:MI:SS AM'), 5000, 'R', 13 );
    INSERT INTO TAB_DTL ( APPDATE, AMOUNT, STATUS, RATE ) VALUES TO_DATE( '31/03/2012 11:59:00 AM','DD/MM/YYYY HH:MI:SS AM'), 470000, 'B', 13 );
    OUTPUT FORMAT :
    APPDATE                    DR          CR     BALANCE          ACCAMT     DAYS     CUMM     
    13/09/2011 10:50:45 AM          5,00,000.00     0     5,00,000.00     10301     58     10301
    09/11/2011 1:15:30 PM          0          5000     4,95,000.00     6330     36     16631
    15/12/2011 3:20:31 PM          0          5000     4,90,000.00     3655     21     20286
    05/01/2012 10:25:11 AM           0          5000     4,85,000.00     4823     28     25109
    02/02/2012 4:23:34 PM          0          5000     4,80,000.00     5456     32     30565
    05/03/2012 11:15:45 AM          0          5000     4,75,000.00     4218     25     34783
    30/03/2012 11:55:10 AM          0          5000     4,70,000.00     334     2     35117
    31/03/2012 11:59:00 AM          0          0     4,70,000.00     35117Logic for computation of A) DAYS : Difference in Days from the next succeeding Date
                   B) ACCAMT : Balance * (Difference in Days from the next Date) * Rate / Days in the Financial Year
    Using CASE / LEAD SQLs, can the same be accomplished.
    Thanks

    # If appdate is 31-MAR-YYYY and time portion is > 11:59:AM THEN we will treat it as 01-APR-2012 otherwise the we will ignore the timestamp of appdate
    SELECT TO_CHAR (tab_dtl_vw.appdate, 'DD/MM/YY fmHHfm:MI:SS AM') appdate,
           CASE
               WHEN round(tab_dtl_vw.dr,2) < 10000 THEN to_char(round(tab_dtl_vw.dr,2))
               ELSE TO_CHAR(round(tab_dtl_vw.dr,2),'FM99,99,99,99,99,99,99,999.00')
           END dr,
           CASE
               WHEN round(tab_dtl_vw.cr,2) <10000 THEN to_char(round(tab_dtl_vw.cr,2))
               ELSE TO_CHAR(round(tab_dtl_vw.cr,2),'FM99,99,99,99,99,99,99,999.00')
           END cr,
           CASE
               WHEN round(tab_dtl_vw.balance,2) <10000 THEN to_char(round(tab_dtl_vw.balance,2))
               ELSE TO_CHAR(round(tab_dtl_vw.balance,2),'FM99,99,99,99,99,99,99,999.00')
           END balance,
           tab_dtl_vw.days,
           CASE
               WHEN tab_dtl_vw.days IS NOT NULL THEN ROUND ((tab_dtl_vw.balance * tab_dtl_vw.days * tab_dtl_vw.rate) / (tab_dtl_vw.daysinyear*100))
               ELSE SUM(ROUND((tab_dtl_vw.balance * tab_dtl_vw.days * tab_dtl_vw.rate) / (tab_dtl_vw.daysinyear*100)))
                       OVER(ORDER BY tab_dtl_vw.appdate)
           END accamt,
           CASE
               WHEN tab_dtl_vw.days IS NOT NULL THEN SUM(ROUND((tab_dtl_vw.balance * tab_dtl_vw.days * tab_dtl_vw.rate) / (tab_dtl_vw.daysinyear*100)))
               OVER(ORDER BY tab_dtl_vw.appdate)
               ELSE NULL
           END cummamt
    FROM
      ( SELECT appdate ,
                   CASE  WHEN status = 'D' THEN amount   ELSE 0  END AS dr ,
                   CASE   WHEN status = 'R' THEN amount  ELSE 0  END AS Cr ,
                   SUM (amount * CASE WHEN status = 'D' THEN 1 WHEN status = 'R' THEN -1 END) OVER (ORDER BY appdate) AS balance ,
                   CEIL (LEAD(appdate) OVER (ORDER BY appdate) - appdate ) AS days ,
                   rate ,
                   CASE 
                       WHEN (appdate >= '01-APR-' || TO_CHAR(appdate,'YYYY')  AND
                       TO_CHAR(LAST_DAY('01-FEB-' || (TO_CHAR(appdate,'YYYY') + 1)),'DD-MON') = '29-FEB')
                              THEN 366
                        WHEN TO_CHAR(LAST_DAY('01-FEB-' || TO_CHAR(appdate,'YYYY')),'DD-MON') = '29-FEB'
                               THEN 366
                        ELSE 365
                    END daysinyear
           FROM (SELECT CASE WHEN (TO_CHAR(TRUNC(APPDATE),'DD-MON') = '31-MAR' AND APPDATE > TRUNC(APPDATE - 1/2 - 60/86400)) THEN TRUNC(APPDATE) +1 ELSE TRUNC(APPDATE) END appdate,
                        status,
                        amount,
                        rate
                  FROM  tab_dtl
         ) tab_dtl_vw
    ORDER BY tab_dtl_vw.appdate ASC
    Output
    APPDATE              DR         CR         BALANCE                                        DAYS     ACCAMT    CUMMAMT
    13/09/11 12:00:00 AM 5,00,000.0 0          5,00,000.00                                      57      10123      10123
    09/11/11 12:00:00 AM 0          5000       4,95,000.00                                      36       6330      16453
    15/12/11 12:00:00 AM 0          5000       4,90,000.00                                      21       3655      20108
    05/01/12 12:00:00 AM 0          5000       4,85,000.00                                      28       4823      24931
    02/02/12 12:00:00 AM 0          5000       4,80,000.00                                      32       5456      30387
    05/03/12 12:00:00 AM 0          5000       4,75,000.00                                      25       4218      34605
    30/03/12 12:00:00 AM 0          5000       4,70,000.00                                       2        334      34939
    01/04/12 12:00:00 AM 0          0          4,70,000.00                                              34939
    {code}
    Edited by: Himanshu Binjola on Apr 24, 2012 11:18 AM
    Edited by: Himanshu Binjola on Apr 24, 2012 11:20 AM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Error When creating Broadcastings "Portal theme does not fit output format"

    Hi All,
    When i create a Broadcasting Settings i am getting an Error saying "Portal theme does not fit output format", and below is the detailed that we are getting,
    "Diagnosis
    You used separate portal themes to generate PDF or print formats (PS or PCL). The output format that you selected is not appropriate for the portal theme currently set.
    System Response
    The broadcast setting is not consistent and you cannot save or execute it.
    Procedure
    Change the output format or the portal theme correspondingly. (The portal theme is set to the first valid value for the current output format when you display the corresponding tab page).
    Procedure for System Administration
      Notification Number RSRD 640"
    Can anyone help how to resolve this issue?
    Regards,
    Muruganand.K

    Would you have chance to provide me the sollution...
    We are facing the exactly the same error message
    Thanks a lot in advance
    Regards
    Ivan

  • Anyone understand the purpose of Proxy render/output format?

    So I've done a couple of projects with X now and am fairly happy with the proxy workflow:
    1) Ingest, creating proxies, but no optimized - render format set to ProRes regular
    2) Edit in proxy
    3) In preferences, switch back to "Use original or optimized"
    4) Tweak edit
    5) Render and export
    However, I'm still not understanding the thinking behind the render/output format (full-resolution proxy) when you are editing in proxy. It seems to me that it SHOULD be:
    EITHER: When you're editing proxy, if you render/export, FCPX renders/outputs in proxy using the same low resolution as your proxy files. This would be great for early, quick samples for clients. No need to spend forever rendering full-res ProRes regular, or the pointless upsizing of pre-rendered lo-res proxies.
    OR: Even while you're editing from proxies, background rendering is done in your full-quality format (i.e. 1080 ProRes regular). This would save you from re-rendering when you switch back over to original/optimized.
    Ideally, there'd be a toggle to choose which of these you want. Even without a toggle, Apple should pick one of these it seems. The way it is now seems useless.
    SUMMARY:
    While editing in proxy, render/output should be either:
    1) 720x540 ProRes Proxy
    OR
    2) 1920x1080 ProRes Regular
    BUT NOT
    3)1920x1080 ProRes Proxy
    I was going to send an enhancement request about it, but figured I'd first see if anybody knows of a useful reason for it instead being this third, awkward format.
    Thoughts?

    I had hoped the summary would clear up the question. I guess not. Let's try this again:
    QUESTION - Would other people like the output, when in proxy mode, to be a low-res ProRes Proxy file - the same size as the files that are created when you tell FCPX to make proxies of your original files?
    DETAILS
    - When you create proxies of your original files, they are a low-resolution of "something"x540 (in my case 720x540)
    - If you output while in proxy, you get a proxy output file at 1920x1080 - this is 5.3 times as many pixels to render as 720x540.
    - Assuming a linear relationship between number of pixels and render time, this means it would take over 5 times as long to render the current form of proxy output, as compared to what I'm asking for.
    - I want a quickly-rendered format (like 720x540 Proxy) so I can quickly render/output, change things, re-render/output, sending multiple sample files to the client.
    - Of course, the ability to mark in/out on the timeline and export just that section is also important here, but that's another post and has already been discussed.
    - For further details, see my original post
    As for my workflow, I don't need to work with either/or. I work in proxy (which, if you're doing more than straight cuts, allows better playback before rendering, no matter what computer you're using) until I'm ready for the final tweaks to graphics or the edit that actually rely on fine detail, and want to output in 1080 Prores regular, at which point I change the preference back to original/optimized, like I said right at the start of the first post. No mind reading necessary. I then tweak, render and output. I'm not sure you're understanding the purpose of a proxy workflow.

  • APEX Report Output Formats

    In the SQL Workshop query builder can the output of these queries be changed to HTML or ASCII? We have WEBDB running and are able to change the output formats at run time.

    Hello Andy,
    The APEX Query Builder was not designed as a report generator. It’s main purpose is to allow novice users to create SQL queries in a bit more friendly manner. After testing the validity of the query, with the displayed format type, you should actually copy the generated SQL code into an appropriate page region, like a report region.
    The configuration options of this specific tool are very limited, and as far as I know, the kind of things you are asking for can’t be done in this version. One of the major additions to APEX 4.0 will be something (I don’t know the final name for it) that will allow you to do the sort of things you are asking for.
    >> Also cant he number of records that are displayed by increased to say 1000 or 4000 rather then 15?
    You can’t change the displayed number of records in the Query Builder. A possible work around can be to copy the SQL query into the SQL Commands. There you can control the number of displayed records.
    Regards,
    Arie.
    &diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
    &diams; Forthcoming book about APEX: Oracle Application Express 3.2 – The Essentials and More

  • Best Output Format for Slide Show?

    If I were to purchase Final Cut Studio...
    What would be the best output format to use for a simple slideshow intended for Web deployment? In other words, which encoding method will provide the best compromise between file size and video quality? The slideshow is a series of simple static images with some fade transitions and Ken Burns effects. There is also a soundtrack for background music.
    A 1.5 minute slideshow with soundtrack created using Adobe Flash is less than 2 MB in size (which is great for Web deployment), and it looks very good. If that same slideshow is exported from Flash to a QuickTime-compatible format, it balloons to over 20 MB!
    So what I'd really like to know is, if something like Final Cut Pro were used to create that same slideshow, would I be able to produce a web-ready video that rivals the Flash version in size?
    Thanks for any help and insight you can provide,
    -Steve

    Studio X wrote:
    Quicktime is a file wrapper that can contain anyone of a number of codecs.
    Yes, I understand that.
    H.264 is the prefered version for web/apple TV delivery.
    A 90s slideshow that was less than 2 MB as a SWF file became a 27 MB behemoth when exported using the H.264 codec. The exported file had the same frame rate and resolution (pixel dimensions) as the original Flash file. The audio was optimized as well. Why the dramatic difference? (I think I know why, but perhaps I'm missing something.)
    That being said, Final Cut Pro is a video editing program and is a waste of money if all you are doing is simple slideshows.
    Slideshows are not all I will be doing, but I will be doing them occasionally, and it's hard to justify purchasing Flash just to create slideshows that are optimized for the Web.
    Have you tried iMovie then converting the output to either Flash or (if you have Quicktime Pro) converting to h.264 QT?
    My tests indicate that anything but Flash format results in a monstrous file for a simple slideshow. I have a notion as to why this is, but I wanted to check to make sure that I'm not overlooking some way of creating smaller non-Flash files.
    The bottom line is that Final Cut Studio will be far more useful and versatile for what I need to do, and I would be much more proficient with that software; but if I can't output video files that rival those of Flash in terms of quality and file size, then I might have to get a copy of Flash after all.
    And yes, you can convert a QuickTime movie to flash, but it's just not the same in terms of file size as generating the same slideshow directly in Flash. I suspect this is because Flash is optimized for animation, whereas the QuickTime codecs are designed for video, and a simple slideshow is more of an animation than a video.
    So my real question is (and I suspect the answer is no), is it possible using Final Cut Studio to generate a simple slideshow which rivals the output from Flash in terms of file size for a given resolution?
    -Steve

  • Regular expression and output format

    hi all,
    i have following scenario-
    regular expression: [0-9]{3}-[0-9]{3}-[0-9]{4}
    generated value by the above regular expression: 123-234-6789
    output format to display the generated above value: xxx-xxx-$1
    now i need to display the generated value (123-234-6789) in the specified output format (xxx-xxx-$1) and the final output will be xxx-xxx-6789
    how is it possible?
    Note: here regular expression and output format can vary
    br,
    bashar

    Hi, Bashar
    You can solve this problem by using the Data Masking Technique.
    Masking data means replacing certain fields with a Mask character (such as an X). This effectively disguises the data content while preserving the same formatting on front end screens and reports. For example, a column of credit card numbers might look like:
    4346 6454 0020 5379
    4493 9238 7315 5787
    4297 8296 7496 8724
    and after the masking operation the information would appear as:
    4346 XXXX XXXX 5379
    4493 XXXX XXXX 5787
    4297 XXXX XXXX 8724
    The masking characters effectively remove much of the sensitive content from the record while still preserving the look and feel. Take care to ensure that enough of the data is masked to preserve security.
    It would not be hard to regenerate the original credit card number from a masking operation such as: 4297 8296 7496 87XX since the numbers are generated with a specific and well known checksum algorithm.
    Best Regards,
    Mahfuz Khan

  • How to get multiple output formats for each execution of the report?

    Hi,
    Is it possible to get multiple output formats for each execution of the report? If so can you provide some details?
    Thanks

    In Reports 6i, Reports Distribution was introduced. This allows you to run the report once and output to a number of destinations with a different format. It also allows you to distribute individual sections within a report to different destinations in different formats.
    The Destinations for a Report to distribute to are defined either in a distribution file and passed on the command line or inside of the report definition.
    To add a destination to the the report definition, bring up the property palette against the report object and then select the "Distribution" property under the "Report" node. This will bring up a dialog that allows you to create a distribution list. You can then test this list by selecting "file->distribute" from the menu.
    To run a report that is to be distributed through rwrun60, you need to add "distribute=yes" to the command line. It will pick up the destinations from the report definition. If you add "destination=<filename>" then it will pick up the destinations from the specified "<filename>" and ignore the destinations in the report definition.
    Note: if "distribute=yes" is specified on the command line then the destype/desname/desformat parameters will be used to format the report (ie: which printer/display to use during formatting for sizing objects) but will be ignored when the report is sent to the destinations.

  • Pstack output format details

    can anybody tell me where can i find a detailed information about the output format of the pstack utility ?
    pstack proc (1) - proc tools
    e.g. on my machine
    uname -aSunOS dxcsxi 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-Enterprise-10000
    i
    pstack outputs something like this:
    pstack 1020810208: xterm
    fef19884 poll (ffbeef70, 2, ffffffff)
    feecc968 select (5, 0, fef3b1dc, 474c4, 47544, ffbeef70) + 2cc
    0001ab4c in_put (1, 0, 44cd8, 44cdc, 400, 474c4) + 3d8
    000191d0 ???????? (44c00, 588d8, 2bdb4, 0, 0, 0)
    0001c8b8 VTRun (48c00, 58860, 29818, 0, 0, 48c85) + 324
    0001665c main (2, 48c00, 47400, ffbef31c, 58860, 588d8) + bf8
    00015780 _start (0, 0, 0, 0, 0, 0) + b8
    What is the meaning of the numbers in braces and the meaning of the number after + ???
    Thanks in advance.

    can anybody tell me where can i find a detailed information about the output format of the pstack utility ?
    pstack proc (1) - proc tools
    e.g. on my machine
    uname -aSunOS dxcsxi 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-Enterprise-10000
    i
    pstack outputs something like this:
    pstack 1020810208: xterm
    fef19884 poll (ffbeef70, 2, ffffffff)
    feecc968 select (5, 0, fef3b1dc, 474c4, 47544, ffbeef70) + 2cc
    0001ab4c in_put (1, 0, 44cd8, 44cdc, 400, 474c4) + 3d8
    000191d0 ???????? (44c00, 588d8, 2bdb4, 0, 0, 0)
    0001c8b8 VTRun (48c00, 58860, 29818, 0, 0, 48c85) + 324
    0001665c main (2, 48c00, 47400, ffbef31c, 58860, 588d8) + bf8
    00015780 _start (0, 0, 0, 0, 0, 0) + b8
    What is the meaning of the numbers in braces and the meaning of the number after + ???
    Thanks in advance.

  • Pstack output format

    can anybody tell me where can i find a detailed information about the output format of the pstack utility ?
    pstack proc (1) - proc tools
    e.g. on my machine
    uname -aSunOS dxcsxi 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-Enterprise-10000
    i
    pstack outputs something like this:
    > pstack 10208
    10208: xterm
    fef19884 poll (ffbeef70, 2, ffffffff)
    feecc968 select (5, 0, fef3b1dc, 474c4, 47544, ffbeef70) + 2cc
    0001ab4c in_put (1, 0, 44cd8, 44cdc, 400, 474c4) + 3d8
    000191d0 ???????? (44c00, 588d8, 2bdb4, 0, 0, 0)
    0001c8b8 VTRun (48c00, 58860, 29818, 0, 0, 48c85) + 324
    0001665c main (2, 48c00, 47400, ffbef31c, 58860, 588d8) + bf8
    00015780 _start   (0, 0, 0, 0, 0, 0) + b8
    What is the meaning of the numbers in braces and the meaning of the number after + ???
    Thanks in advance.

    This is the call of local function with unknown (stripped) name.
    To see all known name type
    /usr/ccs/bin/nm -D /usr/openwin/bin/xterm
    See the following. In this case ???????? is equal to local
    function which starts at 0x19154
    $ xterm &
    1718
    $ pstack 1718
    1718:     xterm
    ef31d8c8 poll (effff030, 2, ffffffff)
    ef2cd540 select (5, 0, 0, effff040, 474c4, effff030) + 348
    0001ab4c in_put (1, 0, 44cd8, 44cdc, 400, 474c4) + 3d8
    000191d0 ???????? (44c00, 5f380, 2bdb4, f6950848, f6b5e938, fc152b80)
    0001c8b8 VTRun (48c00, 5f308, 29818, 0, 0, 48c85) + 324
    0001665c main (2, 48c00, 47400, effff3e4, 5f308, 5f380) + bf8
    00015780 _start   (0, 0, 0, 0, 0, 0) + b8
    $ dis /usr/openwin/bin/xterm > /tmp/xterm.dis
    $ cat /tmp/xterm.dis
    ...... skipped
         19140: 00 00 01 60 unimp      0x160
         19144: 00 00 09 88 unimp      0x988
         19148: 00 00 0c dc unimp      0xcdc
         1914c: 00 00 0c dc unimp      0xcdc
         19150: 00 00 07 44 unimp      0x744
    ----->     19154: 9d e3 bf 58 save      %sp, -168, %sp
         19158: 05 00 01 23 sethi      %hi(0x48c00), %g2
         1915c: 03 00 00 af sethi      %hi(0x2bc00), %g1
         19160: c4 00 a0 84 ld      [%g2 + 132], %g2
         19164: 84 00 a0 78 add      %g2, 120, %g2
         19168: c4 27 bf fc st      %g2, [%fp - 4]
         1916c: 84 00 61 b4 add      %g1, 436, %g2
         19170: c4 27 bf f8 st      %g2, [%fp - 8]
         19174: 05 00 01 1d sethi      %hi(0x47400), %g2
         19178: 40 00 a4 2a call      setjmp
    ...... skipped
         1c58c: 81 c7 e0 08 ret      
         1c590: 81 e8 00 00 restore      
    VTRun()
         1c594: 9d e3 bf 80 save      %sp, -128, %sp
         1c598: 31 00 01 23 sethi      %hi(_sys_nerr), %i0
         1c59c: f2 06 20 84 ld      [%i0 + 0x84], %i1
         1c5a0: 84 06 60 78 add      %i1, 120, %g2
         1c5a4: c4 27 bf fc st      %g2, [%fp - 4]
    ...... skipped
         1c8ac: 80 90 00 08 orcc      %g0, %o0, %g0
         1c8b0: 12 80 00 04 bne      0x1c8c0
         1c8b4: 01 00 00 00 nop      
    +324     1c8b8: 7f ff f2 27 call      0x19154
         1c8bc: 01 00 00 00 nop      
         1c8c0: 40 00 04 27 call      HideCursor
         1c8c4: 01 00 00 00 nop      
         1c8c8: c6 07 bf fc ld      [%fp - 4], %g3
    ...... ommited

  • E72 - How to format the phone number on contact

    I can't figure out a easy for formatting my contact number to be like (xxx) xxx-xxxx or xxx-xxx-xxxx on e72 instead going to outlook make the changes and re-sync again. I find xxxxxxxxxx hard to read. I thought I found out how to add hypen "ctrl+(" but that basically long dash rather than short dash which you get an error if you try to send message with the phone number having the long dash. It is fine when you call. It is smart enough to strip out non-numerical value. But it is sms is not smart enough to remove it.

    ozidug wrote:
    The sad thing is that there is an international standard for phone numbers (+xxx) xxx-xxxx which everyone ought to recognise and use. It allows localisation and shortened dialling, but Nokia just want a number string. It's just lazy on thepart of the programmers; since it's a standard, they should have developed the program code once and just inserted it into every phone they produce, and that's not hard.
    A poor reflection on Nokia, I'm sad to say.
    AFAIK the international standard for telephone numbers (E.164) does not say anything about using spaces, dashes, or brackets in a telephone number.
    This may of course make it more "human readable", but claiming that what you want is a standard doesn't make it a standard, and I don't think Nokia (or any other phone manufacturer) should/could implement every single user-specific wish...

Maybe you are looking for