Variant form standard report to z report

hi guys,
               I have copied a standard program to my z report.But when i execute the standard report its picking the variant from LTDX table and its working fine.But when i run my zreport its not showing the same output as in my standard progrom.So how i need to copy the same variant to my zreport

hi thanks a lot guys..Let me tell you my requirement.For tcode IW47, when it executed its not displaying the field OPRATION SHORT TEXT field (ltxa1).So i copied the IW47 to my z report and debugged the whole code.But still unable to get the field in output.Its getting populated in field catalog.Where might be the problem.???

Similar Messages

  • Variant in standard reports

    Dear Experts
    Good Morning
    I have query about creation of variant in standard reports
    1) i want to create variant which automatically change its date on next day
    2) one variant which can automatically pick the start and end date of month
    waiting for reply
    usefull answers are rewarded
    Thanks and warm regards
    Rajeev Garg

    Dear Rajeev Garg,
    please see documentation regarding this issue:
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/c0/980398e58611d194cc00a0c94260a5/frameset.htm
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/c0/98039be58611d194cc00a0c94260a5/frameset.htm
    Regards,
    Sabine

  • Hard-Code address on 1099 Forms (Standard Report)

    Hi All,
    We need to do the Hard-Code address on 1099 Forms (Standard Report) in Payables module.
    Is there any way do this?
    Thanks in advance.
    Thanks,
    Astik Mondal

    It allows only 30 characters of the address.
    Refer 5th question in the Note 110390.1 where they suggested a workaround.
    Regards,
    Srini

  • Standard report Variant creation

    Hi ,
    i am trying to create the dynamic variant for standard report   RKWTP_CPTD, which contains the period and fiscal year fields on
    selection screen, now i need to create variant as period has to  be current month -1 month i.e it has to show previous month
    and for year , the current  year has to result in dynamic variant.
    if any idea creating the variant please help me.
    Thanks
    SrInI

    First did you look for already available option in online help ?
    (e.g. ABAP Workbench Tools , Variant Maintenance , Variable Values in Variants, etc.)
    If none fulfills your requirement, you could create your own variant in TVARVC and update those in a report executed in a daily scheduled periodic job (You can copy some code from RVSETDAT)
    Regards,
    Raymond

  • How to get the output of a standard report  RFBILA00 in PDF form.

    hi,
    I have to get the output of the standard report RFBILA00 in the PDF form.
    Thanks.

    Hi Rao,
    you can run your report RFBILA00 in background  and in background  job you can add one more step, next in that step you can add custom  report like zsubmit .
    job should be set like
    step1:  RFBILA00 with variant.
    Step2:  zsubmit report with variant.
    In Zsubmit report  you can  read, your first step spool using FM GET_JOB_RUNTIME_INFO
    and pass that spool  in the FM  CONVERT_ABAPSPOOLJOB_2_PDF.
    when second  report run in job  you can set your target like download in the server or  send email etc.
    Regards,
    Prasenjit

  • Line Item Not dispaying in Payment Advice standard report

    Hi Experts,
    I have cleared line items of a vendor by making payment through F-53 and subsequently generated the Print Form spoon request through FBZ5. But in the print, line items (cleared Items) doesn't display in Payment advice report. But for the Fiscal Year 2009 line items (Cleared item) was displaying in the Payment Advice report which is now not displaying.Since it is a standard report no changes made. So please suggest how to achieve it.
    Thanks in Advance,
    Arabinda

    Hello,
    In tr. F-53 you post a payment document,
    but to print a check you need to use some check printing program.
    SAP-delivered program is RFFOUS_C and it processes only
    one bank line per payment document.
    Please check the following general information:
    The standard form (of the print program RFFOUS_C) prints the invoice
    items followed by the check.  If the item details overflow to the next
    page, then the first check (eg cheque no. 1) will be voided and you'll
    get the valid cheque on second page (eg cheque no. 2). This is standard
    functionality.
    Also I would request you to recheck your customising in FBZP i.e.
        -> Click on the 'Payment methods in company code' button
        -> Double click on the appropriate 'Pymt meth.'
           -> Click on the 'Pyt adv. ctrl' button
              ¦ Note to payee lines on the form  /               ¦
              ¦                                                  ¦
              ¦ O  restricted to                       98 Rows   ¦
              ¦ O  None                                          ¦
              ¦ O  as many as req                                ¦
              ¦__________________________________________________¦
    - The first option will restrict the number of lines on the form to a
    value from 1 to a maximum of 98.
    - The second option will restrict the number of lines on the form to
    zero.
    - The third option option will not restrict the number of lines on the
    form.
    You may test in the system which among the three options will suit your
    needs. There is a documentation available at the side of each button.
    Also please check whether the problem happens with the standard SAP
    program. You may wish to review the documentation for RFFOUS_C via
    transaction SE38 -> Enter program name -> Select 'Documentation' radio
    button -> Display -> scroll to 'Setting up and changing the SAPscript
    forms (layout sets)'.
    Also you can refer to the parameter `No form summary section' in the
    variant of RFFOUS_C. By setting this indicator, you can prevent the form
    summary section from being printed hence the overflow is avoided and
    thus eliminates the voided check issue. Please refer to F1 Help of this
    field for further information.
    Also please refer to the F1 help on the indicator "Indicator: Do not
    Void any Checks" in the selection screen of payment program RFFOUS_C.
    I hope this helps.
    BR,
    Raquel

  • Report Toolkit Standard Report Print Problem

    We are trying to print a label out on a Zebra QL220+ Thermal Printer.  Using the Report Generation Toolkit and selecting the Report Type as "WORD" it works fine.  However by ONLY changing the Report Type to "STANDARD REPORT" it still prints out the label OK, but then scrolls out another blank label - it's like some sort of form feed character/command is somehow being appended.
    We don't want to use the WORD Report Type, because I assume we have to install MS Office, which we don't want.
    As you can see from the attached VI, it is just some very basic text that we are writing to the Label.
    Is there some way we can see what data is actually being sent to the Printer for the two different Report Types?
    Chris
    Attachments:
    Zebra Label Print.vi ‏43 KB

    If your printer is networked you would open a TCP connection on port 6101 to the printer. If serial simply send the data via normal VISA commands.
    Here is the CPCL for the one example label in your code:
    ! 0 200 200 440 1
    TEXT 0 2 10 10 Date: <DATE>
    TEXT 0 2 10 30 Time: <TIME>
    TEXT 0 2 10 50 Operator: <INITIALS>
    TEXT 0 2 10 70 Location: <LOCATION>
    TEXT 0 2 10 90 Reason: <REASON>
    TEXT 0 2 10 110 Post Comment: <COMMENT>
    TEXT 0 2 10 130 S/N: <SN>
    TEXT 0 2 10 150 Dryness Fraction:
    TEXT 0 2 10 170 Signature:
    LINE 100 190 300 190 1
    PRINT
    In the above label you would programmatically replace the "<x>" fields with the actual data you wanted printed. For your multiple S/Ns you would use a loop to add the lines with each S/N.
    From the CPCL manual here are the pages for the elements I used above:
    TEXT Commands
    The TEXT command is used to place text on a label. This
    command and its variants control the specific font number
    and size used, the location of the text on the label,
    and the orientation of this text. Standard resident fonts
    can be rotated to 90° increments as shown in the example.
    Format:
    {command} {font} {size} {x} {y} {data}
    where:
    {command}: Choose from the following:
    TEXT Prints text horizontally.
    (or T)
    VTEXT Prints text (vertically) rotated 90
    (or VT) degrees counterclockwise.
    TEXT90 (Same as VTEXT above.)
    (or T90)
    TEXT180 Prints text (upside down) rotated
    (or T180) 180 degrees counterclockwise.
    TEXT270 Prints text (vertically) rotated 270
    (or T270) degrees counterclockwise.
    {font}: Name/number of the font.
    {size}: Size identifier for the font.
    {x}: Horizontal starting position.
    {y}: Vertical starting position.
    {data}: The text to be printed.
    LINE Commands
    Lines of any length, thickness, and angular orientation
    can be drawn using the LINE command.
    Format:
    {command} {x0} {y0} {x1} {y1} {width}
    where:
    {command}: Choose from the following:
    LINE Prints a line.
    (or L)
    {x0}: X-coordinate of the top-left corner.
    {y0}: Y-coordinate of the top-left corner.
    {x1}: X-coordinate of:
    - top right corner for horizontal.
    - bottom left corner for vertical.
    {y1}: Y-coordinate of:
    - top right corner for horizontal.
    - bottom left corner for vertical.
    {width}: Unit-width (or thickness) of the line.
    <!> {offset} <200> <200> {height} {qty}
    where:
    <!>: Use '!' to begin a control session.
    {offset}: The horizontal offset for the entire label.
    This value causes all fields to be offset
    horizontally by the specified number of
    UNITS.
    <200>: Horizontal resolution (in dots-per-inch).
    <200>: Vertical resolution (in dots-per-inch).
    {height}: The maximum height of the label.
    The maximum label height is calculated by measuring
    from the bottom of the first black bar (or
    label gap) to the top of the next black bar (or label
    gap). Then 1/16” [1.5mm] is subtracted from this
    distance to obtain the maximum height. (In dots:
    subtract 12 dots on 203 d.p.i printers; 18 dots on
    306 d.p.i. printers)
    {qty}: Quantity of labels to be printed.
    Maximum = 1024.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • How to call our smartform in standard report

    Hi friends,
    How to call Zee smartform from standard report without affecting stadard flow.
    Thanks,
    Yogesh

    Hi,
      do it this way.
    in the ALV function call
    give in
    exporting
    I_CALLBACK_USER_COMMAND = 'user_command '
    write a subroutine
    FORM user_command USING whatcomm TYPE sy-ucomm whatrow TYPE
    slis_selfield.
    case whatcomm.
    when 'print'.
    call 2 function modules here
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING FORMNAME = P_FORM "Your form name
    variant = ' '
    direct_call = ' '
    IMPORTING FM_NAME = FM_NAME
    EXCEPTIONS NO_FORM = 1
    NO_FUNCTION_MODULE = 2
    OTHERS = 3.
    IF SY-SUBRC 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    EXIT.
    ENDIF.
    calling the generated function module
    CALL FUNCTION FM_NAME
    EXPORTING
    ARCHIVE_INDEX =
    ARCHIVE_INDEX_TAB =
    ARCHIVE_PARAMETERS =
    CONTROL_PARAMETERS = CPARAM
    OUTPUT_OPTIONS = OUTOP
    USER_SETTINGS = SPACE
    MAIL_APPL_OBJ =
    MAIL_RECIPIENT =
    MAIL_SENDER =
    IMPORTING
    JOB_OUTPUT_INFO = TAB_OTF_DATA
    DOCUMENT_OUTPUT_INFO =
    JOB_OUTPUT_OPTIONS =
    EXCEPTIONS
    FORMATTING_ERROR = 1
    INTERNAL_ERROR = 2
    SEND_ERROR = 3
    USER_CANCELED = 4
    OTHERS = 5
    IF SY-SUBRC 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    endcase.
    endform.
    This is an example in the function gereated call give you own importing and exporting parameters.
    Regards
    Kiran Sure

  • Hw to use a variant in alv report

    Hi,
    How to create, use and give f4 functionality to a variant in alv report.
    Give an example.
    Regards,
    Madhu

    <b>In this  report  i had used the  FM ->  REUSE_ALV_VARIANT_F4  for F4 help and the Varient on it  .</b>
    REPORT Z_INVENTORY.
    * List of the materials inventory.                                    *
    TYPE-POOLS: SLIS.
    TABLES:MARC, MARD, VBAP, LIPS, EKPO, VBFA, EKBE, MARM, VBBE, MARA, MBEW.
    SELECTION-SCREEN BEGIN OF BLOCK SEL WITH FRAME TITLE TEXT-001.
    SELECT-OPTIONS: S_WERKS FOR MARC-WERKS, " Plant
                    S_MATNR FOR MARC-MATNR, " Material
                    S_MTART FOR MARA-MTART. " Material Type
    SELECTION-SCREEN END OF BLOCK SEL.
    PARAMETERS: P_VARI LIKE DISVARIANT-VARIANT. " ALV Variant
    CONSTANTS: FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE'.
    DATA: BEGIN OF INV OCCURS 100,
            WERKS LIKE MARD-WERKS, " Plant
            MATNR LIKE MARD-MATNR, " Material
            MTART LIKE MARA-MTART, " Material Type
            STPRS LIKE MBEW-STPRS, " Standard Price
            AVAIL LIKE MARD-LABST, " Available
            LABST LIKE MARD-LABST, " Unrestricted use
            INSME LIKE MARD-INSME, " Quality Inspection
            RETME LIKE MARD-RETME, " Returns
            TRANS LIKE MARC-UMLMC, " Stock in transit (calculated)
            UMLMC LIKE MARC-UMLMC, " Stock Transfer (plant)
            UMLME LIKE MARD-UMLME, " Transfer (SLoc)
            WESBS LIKE EKBE-WESBS, " GR Blocked Stock
            TRAME LIKE MARC-TRAME, " Stock in transit
            SPEME LIKE MARD-SPEME, " Blocked
            KWMENG LIKE VBAP-KWMENG, " Sales orders
            LFIMG LIKE LIPS-LFIMG, " Scheduled for Delivery
            MENGE LIKE EKPO-MENGE, " Open Purch. Orders
            VALUE LIKE MBEW-SALK3, " Stock Value (Calculated)
            MEINS LIKE MARA-MEINS, " Unit of measure
          END OF INV.
    DATA: FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,
          HEADING  TYPE SLIS_T_LISTHEADER,
          LAYOUT   TYPE SLIS_LAYOUT_ALV,
          EVENTS   TYPE SLIS_T_EVENT,
          REPNAME  LIKE SY-REPID,
          F2CODE   LIKE SY-UCOMM VALUE  '&ETA',
          G_SAVE(1) TYPE C,
          G_EXIT(1) TYPE C,
          G_VARIANT LIKE DISVARIANT,
          GX_VARIANT LIKE DISVARIANT.
    INITIALIZATION.
      REPNAME = SY-REPID.
      PERFORM INITIALIZE_FIELDCAT USING FIELDTAB[].
      PERFORM BUILD_EVENTTAB USING EVENTS[].
      PERFORM BUILD_COMMENT USING HEADING[].
      PERFORM INITIALIZE_VARIANT.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
      PERFORM F4_FOR_VARIANT.
    AT SELECTION-SCREEN.
      PERFORM PAI_OF_SELECTION_SCREEN.
    START-OF-SELECTION.
      PERFORM GET_MARD.
      PERFORM GET_UNIT_OF_MEASURE.
      PERFORM GET_MARC.
      PERFORM GET_EKPO.
      PERFORM GET_LIPS.
      PERFORM GET_VBAP.
      PERFORM GET_OPEN.
      PERFORM GET_PRICE.
    END-OF-SELECTION.
      PERFORM BUILD_LAYOUT USING LAYOUT.
      PERFORM WRITE_OUTPUT.
    *&      Form  INITIALIZE_FIELDCAT
    *       text
    *      -->P_FIELDTAB[]  text                                           *
    FORM INITIALIZE_FIELDCAT USING P_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV.
      DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
    * fixed columns (obligatory)
      CLEAR L_FIELDCAT.
      L_FIELDCAT-TABNAME    = 'INV'.
      L_FIELDCAT-FIX_COLUMN = 'X'.
      L_FIELDCAT-NO_OUT     = 'O'.
      L_FIELDCAT-FIELDNAME  = 'WERKS'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME  = 'MATNR'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
    * totalized columns
      CLEAR L_FIELDCAT.
      L_FIELDCAT-TABNAME   = 'INV'.
      L_FIELDCAT-SP_GROUP  = 'A'.
      L_FIELDCAT-DO_SUM    = 'X'.
      L_FIELDCAT-FIELDNAME = 'LABST'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'INSME'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'RETME'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'UMLME'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'WESBS'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'SPEME'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
    * columns with different description
      L_FIELDCAT-FIELDNAME = 'KWMENG'.
      L_FIELDCAT-SELTEXT_M = 'Sales Orders'.
      L_FIELDCAT-SELTEXT_S = 'Sales Or'.
      L_FIELDCAT-SELTEXT_L = 'Sales Orders Qty'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'LFIMG'.
      L_FIELDCAT-SELTEXT_M = 'Sched. Delivery'.
      L_FIELDCAT-SELTEXT_S = 'Schd. Del'.
      L_FIELDCAT-SELTEXT_L = 'Scheduled for Delivery'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'TRANS'.
      L_FIELDCAT-SELTEXT_M = 'Stk. in transit'.
      L_FIELDCAT-SELTEXT_S = 'Stk. trns'.
      L_FIELDCAT-SELTEXT_L = 'Stock in transit (sum)'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'AVAIL'.
      L_FIELDCAT-SELTEXT_M = 'Available'.
      L_FIELDCAT-SELTEXT_S = 'Avail.'.
      L_FIELDCAT-SELTEXT_L = 'Stock Available'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'MENGE'.
      L_FIELDCAT-SELTEXT_M = 'Open Orders'.
      L_FIELDCAT-SELTEXT_S = 'Open Ord'.
      L_FIELDCAT-SELTEXT_L = 'Open Purchase Orders'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
    * columns not displayed
      CLEAR L_FIELDCAT.
      L_FIELDCAT-TABNAME   = 'INV'.
      L_FIELDCAT-SP_GROUP  = 'A'.
      L_FIELDCAT-NO_OUT    = 'X'.
      L_FIELDCAT-FIELDNAME = 'MEINS'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'UMLMC'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'TRAME'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'STPRS'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
      L_FIELDCAT-FIELDNAME = 'VALUE'.
      APPEND L_FIELDCAT TO P_FIELDTAB.
    ENDFORM.                               " INITIALIZE_FIELDCAT
    *&      Form  BUILD_EVENTTAB
    *       text
    *      -->P_EVENTS[]  text                                             *
    FORM BUILD_EVENTTAB USING P_EVENTS TYPE SLIS_T_EVENT.
      DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
           EXPORTING
                I_LIST_TYPE = 0
           IMPORTING
                ET_EVENTS   = P_EVENTS.
      READ TABLE P_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                               INTO LS_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_TOP_OF_PAGE TO LS_EVENT-FORM.
        APPEND LS_EVENT TO P_EVENTS.
      ENDIF.
    ENDFORM.                               " BUILD_EVENTTAB
    *&      Form  BUILD_COMMENT
    *       text
    *      -->P_HEADING[]  text                                            *
    FORM BUILD_COMMENT USING P_HEADING TYPE SLIS_T_LISTHEADER.
      DATA: HLINE TYPE SLIS_LISTHEADER,
            TEXT(60) TYPE C,
            SEP(20) TYPE C.
      CLEAR: HLINE, TEXT.
      HLINE-TYP  = 'H'.
      WRITE: TEXT-101 TO TEXT+23.
      HLINE-INFO = TEXT.
      APPEND HLINE TO P_HEADING.
      CLEAR TEXT.
      WRITE: 'User: ' TO TEXT,
             SY-UNAME TO TEXT+6,
             'Date: ' TO TEXT+25,
             SY-DATUM TO TEXT+31,
             'Page: ' TO TEXT+50,
             SY-PAGNO TO TEXT+56.
      HLINE-INFO = TEXT.
      APPEND HLINE TO P_HEADING.
    ENDFORM.                    " BUILD_COMMENT
    *       FORM TOP_OF_PAGE                                              *
    FORM TOP_OF_PAGE.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
           EXPORTING
                IT_LIST_COMMENTARY = HEADING.
    ENDFORM.
    *&      Form  INITIALIZE_VARIANT
    *       text
    FORM INITIALIZE_VARIANT.
      G_SAVE = 'A'.
      CLEAR G_VARIANT.
      G_VARIANT-REPORT = REPNAME.
      GX_VARIANT = G_VARIANT.
      CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
           EXPORTING
                I_SAVE     = G_SAVE
           CHANGING
                CS_VARIANT = GX_VARIANT
           EXCEPTIONS
                NOT_FOUND  = 2.
      IF SY-SUBRC = 0.
        P_VARI = GX_VARIANT-VARIANT.
      ENDIF.
    ENDFORM.                               " INITIALIZE_VARIANT
    *&      Form  F4_FOR_VARIANT
    *       text
    FORM F4_FOR_VARIANT.
    <b>  CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
           EXPORTING
                IS_VARIANT = G_VARIANT
                I_SAVE     = G_SAVE
           IMPORTING
                E_EXIT     = G_EXIT
                ES_VARIANT = GX_VARIANT
           EXCEPTIONS
                NOT_FOUND  = 2.
      IF SY-SUBRC = 2.
        MESSAGE ID SY-MSGID TYPE 'S'      NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ELSE.
        IF G_EXIT = SPACE.
          P_VARI = GX_VARIANT-VARIANT.
        ENDIF.
      ENDIF.</b>
    ENDFORM.                               " F4_FOR_VARIANT
    *&      Form  PAI_OF_SELECTION_SCREEN
    *       text
    FORM PAI_OF_SELECTION_SCREEN.
      IF NOT P_VARI IS INITIAL.
        MOVE G_VARIANT TO GX_VARIANT.
        MOVE P_VARI TO GX_VARIANT-VARIANT.
        CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
             EXPORTING
                  I_SAVE     = G_SAVE
             CHANGING
                  CS_VARIANT = GX_VARIANT.
        G_VARIANT = GX_VARIANT.
      ELSE.
        PERFORM INITIALIZE_VARIANT.
      ENDIF.
    ENDFORM.                               " PAI_OF_SELECTION_SCREEN
    *&      Form  GET_MARD
    *       text
    FORM GET_MARD.
      SELECT MATNR WERKS LABST INSME RETME UMLME SPEME
             FROM MARD
             INTO CORRESPONDING FIELDS OF INV
             WHERE MATNR IN S_MATNR
             AND   WERKS IN S_WERKS.
        COLLECT INV.
      ENDSELECT.
      PERFORM FILTER_BY_MATERIAL_TYPE.
    ENDFORM.                               " GET_MARD
    *&      Form  FILTER_BY_MATERIAL_TYPE
    *       text
    FORM FILTER_BY_MATERIAL_TYPE.
      LOOP AT INV.
        CLEAR INV-MTART.
        SELECT SINGLE MTART
               INTO INV-MTART
               FROM MARA
               WHERE MATNR EQ INV-MATNR
               AND   MTART IN S_MTART.
        IF SY-SUBRC EQ 0.
          MODIFY INV.
        ELSE.
          DELETE INV.
        ENDIF.
      ENDLOOP.
    ENDFORM.                    " FILTER_BY_MATERIAL_TYPE
    *&      Form  GET_MARC
    *       text
    FORM GET_MARC.
      LOOP AT INV.
        SELECT SINGLE UMLMC TRAME
               FROM MARC
               INTO CORRESPONDING FIELDS OF INV
               WHERE MATNR EQ INV-MATNR
               AND   WERKS EQ INV-WERKS.
        IF SY-SUBRC EQ 0.
          INV-TRANS = INV-UMLMC + INV-TRAME.
          MODIFY INV.
        ENDIF.
      ENDLOOP.
    ENDFORM.                               " GET_MARC
    *&      Form  GET_EKPO
    *       text
    FORM GET_EKPO.
      DATA: WESBS LIKE INV-WESBS,
            SHKZG LIKE EKBE-SHKZG,
            MEINS LIKE EKPO-MEINS,
            LMEIN LIKE EKPO-LMEIN.
      LOOP AT INV.
        CLEAR: WESBS, SHKZG, MEINS, LMEIN.
        SELECT Y~WESBS Y~SHKZG X~MEINS X~LMEIN
               INTO (WESBS, SHKZG, MEINS, LMEIN)
               FROM EKPO AS X JOIN EKBE AS Y
               ON   X~EBELN = Y~EBELN
               AND  X~EBELP = Y~EBELP
               WHERE X~MATNR EQ INV-MATNR
               AND   X~WERKS EQ INV-WERKS
               AND   X~LOEKZ NE 'L'.
          IF SHKZG EQ 'H'.
            MULTIPLY WESBS BY -1.
          ENDIF.
          IF MEINS NE LMEIN.
            PERFORM CONVERT_UNIT_OF_MEASURE CHANGING INV-MATNR MEINS WESBS.
          ENDIF.
          ADD WESBS TO INV-WESBS.
        ENDSELECT.
        MODIFY INV.
      ENDLOOP.
    ENDFORM.                               " GET_EKPO
    *&      Form  GET_LIPS
    *       text
    FORM GET_LIPS.
      DATA: LFIMG LIKE INV-LFIMG.
      LOOP AT INV.
        CLEAR: LFIMG, INV-LFIMG.
        SELECT OMENG
               INTO LFIMG
               FROM VBBE
               WHERE MATNR EQ INV-MATNR
               AND   WERKS EQ INV-WERKS
               AND   VBTYP EQ 'J'.
          ADD LFIMG TO INV-LFIMG.
        ENDSELECT.
        MODIFY INV.
      ENDLOOP.
    ENDFORM.                               " GET_LIPS
    *&      Form  GET_VBAP
    *       text
    FORM GET_VBAP.
      DATA: KWMENG LIKE INV-KWMENG.
      LOOP AT INV.
        CLEAR: KWMENG, INV-KWMENG.
        SELECT OMENG
               INTO KWMENG
               FROM VBBE
               WHERE MATNR EQ INV-MATNR
               AND   WERKS EQ INV-WERKS
               AND   VBTYP EQ 'C'.
          ADD KWMENG TO INV-KWMENG.
        ENDSELECT.
        INV-AVAIL = INV-LABST - INV-INSME - INV-KWMENG - INV-LFIMG.
        MODIFY INV.
      ENDLOOP.
    ENDFORM.                               " GET_VBAP
    *&      Form  GET_UNIT_OF_MEASURE
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM GET_UNIT_OF_MEASURE.
      LOOP AT INV.
        SELECT SINGLE MEINS
               FROM MARA
               INTO INV-MEINS
               WHERE MATNR EQ INV-MATNR.
        MODIFY INV.
      ENDLOOP.
    ENDFORM.                               " GET_UNIT_OF_MEASURE
    *&      Form  GET_OPEN
    *       text
    FORM GET_OPEN.
      DATA: BEGIN OF XTAB OCCURS 10,       " Open orders table
               WERKS LIKE EKPO-WERKS,
               LGORT LIKE EKPO-LGORT,
               MATNR LIKE EKPO-MATNR,
               MENGE LIKE EKPO-MENGE,
               MENGK LIKE EKPO-MENGE,
             END OF XTAB.
      RANGES: L_WERKS FOR MARD-WERKS.
      LOOP AT INV.
        REFRESH XTAB.
        CLEAR: XTAB, L_WERKS.
        MOVE INV-WERKS TO L_WERKS-LOW.
        CALL FUNCTION 'MB_ADD_PURCHASE_ORDER_QUANTITY'
             EXPORTING
                  X_MATNR = INV-MATNR
                  X_MEINS = INV-MEINS
                  X_ELIKZ = SPACE
                  X_LOEKZ = SPACE
             TABLES
                  XTAB    = XTAB
                  XWERKS  = L_WERKS.
        MOVE XTAB-MENGE TO INV-MENGE.
        MODIFY INV.
      ENDLOOP.
    ENDFORM.                               " GET_OPEN
    *&      Form  GET_PRICE
    *       text
    FORM GET_PRICE.
      LOOP AT INV.
        SELECT SINGLE STPRS
               FROM MBEW
               INTO INV-STPRS
               WHERE MATNR EQ INV-MATNR
               AND   BWKEY EQ INV-WERKS
               AND   BWTAR EQ SPACE.
          IF SY-SUBRC EQ 0.
            INV-VALUE = INV-STPRS *
                      ( INV-LABST + INV-INSME + INV-TRANS + INV-SPEME ).
            MODIFY INV.
          ENDIF.
      ENDLOOP.
    ENDFORM.                    " GET_PRICE
    *       FORM CONVERT_UNIT_OF_MEASURE                                  *
    *       text                                                          *
    *  -->  P_MATNR                                                       *
    *  -->  P_VRKME                                                       *
    *  -->  P_QUANT                                                       *
    FORM CONVERT_UNIT_OF_MEASURE USING P_MATNR P_VRKME P_QUANT.
      DATA: UMREZ LIKE MARM-UMREZ,
            UMREN LIKE MARM-UMREN.
      SELECT SINGLE UMREZ UMREN
             INTO (UMREZ, UMREN)
             FROM MARM
             WHERE MATNR EQ P_MATNR
             AND   MEINH EQ P_VRKME.
      IF SY-SUBRC EQ 0.
        COMPUTE P_QUANT = ( P_QUANT * UMREZ ) / UMREN.
      ENDIF.
    ENDFORM.
    *&      Form  BUILD_LAYOUT
    *       text
    *      -->P_LAYOUT  text                                               *
    FORM BUILD_LAYOUT USING P_LAYOUT TYPE SLIS_LAYOUT_ALV.
      P_LAYOUT-F2CODE       = F2CODE.
      P_LAYOUT-ZEBRA        = 'X'.
      P_LAYOUT-DETAIL_POPUP = 'X'.
    ENDFORM.                               " BUILD_LAYOUT
    *&      Form  WRITE_OUTPUT
    *       text
    FORM WRITE_OUTPUT.
      SORT INV BY WERKS MATNR.
      CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
           EXPORTING
                I_PROGRAM_NAME     = REPNAME
                I_INTERNAL_TABNAME = 'INV'
                I_INCLNAME         = REPNAME
           CHANGING
                CT_FIELDCAT        = FIELDTAB.
      IF SY-SUBRC <> 0.
        WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_FIELDCATALOG_MERGE'.
      ENDIF.
      CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
           EXPORTING
                I_CALLBACK_PROGRAM = REPNAME
                I_STRUCTURE_NAME   = 'INV'
                IS_LAYOUT          = LAYOUT
                IT_FIELDCAT        = FIELDTAB
                I_DEFAULT          = 'A'
                I_SAVE             = G_SAVE
                IS_VARIANT         = G_VARIANT
                IT_EVENTS          = EVENTS[]
           TABLES
                T_OUTTAB           = INV.
      IF SY-SUBRC <> 0.
        WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_LIST_DISPLAY'.
      ENDIF.
    ENDFORM.                               " WRITE_OUTPUT
    reward  points if it is usefull.....
    Girish

  • Standard report that will allow monitoring of purchasing procedures

    Hello SAP Gurus,
    I am looking for any reports that will allow monitoring of our purchasing procedures for example:
    Reports identifying date of invoice v's date of order / requisition
    Thanks

    Hello,
    If the standard reports are not going to suffice your requirements, you can crete your own reports.
    Create a form using FSI4 - Refer standard forms available in FSI5 and FSI6.
    Create a report by using FSI1 (assign the form that you have created FSI4) - Refer standard reports available in FSI2 and FSI3.
    Please make sure that you have completed your Fiscal Year Variant in all respects.
    Regards,

  • Difference in GL Balances between two Standard Report fbl3n and fagll03

    Hi ,
    Mismatch of balances between two standard report ie.fbl3n and fagll03 . We are giving the complete example of what we are facing right now ... please go through the examples .
    ENTRY NO. 1
    We have posted one MIRO , Accounting Posting is as below : -
    PK         Description    Amount       
    86         GR/IR             1000.00               
    31         Vendor           -800.00
    50          TDS               -200.00
    ENTRY NO. 2
    We have Reversed the MIRO through MR8M , Accounting Posting was as below : -
    PK         Description     Amount       
    21         Vendor             800.00
    40          TDS                 200.00
    96          GR/IR            -1000.00
    But in Standard report FAGLL03 , .The line items of above twoi entries under GL " TDS " are showing in this way  : -
    Doc No.      PK      Ammount
    Entry 1       50          -200.00
    Entry 2       40          -200.00 -
    > ?????
    *OPEN ITEMS          - 400.00----
    > ?????
    Although in other Standard report FBL3N , the same are showing correctly as shown below
    Doc No.      PK      Ammount
    Entry 1       50          -200.00
    Entry 2       40          +200.00
    *OPEN ITEMS                0.00
    PLEASE HELP
    Regards
    Soumitra Bhattacharya

    Hi
    FAGLL03 - Display/Change Items (New)  - this report is related to ledger reporting purpose.  this reports is available after ECC 5.0.
    FBL3N - is line item display - this is only GL reports (not in ledger reporting)
    if you find any difference is values please check the report variant you are using and ledger you are activated.
    hope this will help you.
    Regards
    Ram

  • Cannot edit a field that is "Standard Report Column" when new row added

    Hi everyone,
    I have created a master-detail form from the wizard and within the detail report region source I have used apex_item.xxx API
    example;
    select C1, C2,
    CASE when C2 ='N' then
    apex_item.select_list_from_query(3, C3,'select a1 d, a2 r from table1', 'ENABLED', 'NO',null,null, 'f03_#ROWNUM#')
    else
    apex_item.select_list_from_query(3, C3,'select a1 d, a2 r from table1', 'DISABLED', 'NO',null,null, 'f03_#ROWNUM#')
    END C3
    from table;
    All columns C1,C2,C3 are defined as "Standard Report Columns".
    The results allows the column C3 field to be enabled or disabled for input depending on a condition.
    The problem is when you hit the default button "Add Row" to add a new row. The row is non-editable and is populated with null values.
    What I want is to allow input when a new row is inserted into the multi-row detail form.
    Can any one help?
    Is there a way to change the Display As field for the new row columns to "text field" from "standard report column" dynamically?

    I think you will need to use the old way of adding rows instead of the new one. I remember having headaches trying to get it working.
    Denes Kubicek
    http://deneskubicek.blogspot.com/
    http://www.apress.com/9781430235125
    http://apex.oracle.com/pls/otn/f?p=31517:1
    http://www.amazon.de/Oracle-APEX-XE-Praxis/dp/3826655494
    -------------------------------------------------------------------

  • In Standard Report Of ALV How Can Set PF Status.

    In Standard Report Of ALV How Can Set PF Status.
    Thanking in anticipation.

    in the call function module, you pass the PF status parameter.
      CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
        EXPORTING
          i_callback_program       = pgm
       <i> <u>  i_callback_pf_status_set = 'SET_PF_STATUS'</u></i>
          it_fieldcat              = fieldcat
          is_variant               = disvariant
          is_layout                = layout
          is_print                 = print
          i_save                   = 'A'
          it_events                = eventcat
          it_sort                  = sortcat
          i_callback_user_command  = 'USER_COMMAND'
        TABLES
          t_outtab                 = a_output
        EXCEPTIONS
          program_error            = 1
          OTHERS                   = 2.
    ENDFORM.                    "LIST_DISPLAY
    FORM SET_PF_STATUS *
    FORM set_pf_status USING extab TYPE slis_t_extab.
      SET PF-STATUS 'ZZSTD'.
    ENDFORM.                    "set_pf_status
    Here double Click on ZZSTD. IT will take you to a different screen and you have to set it.
    Ster.

  • SAP standard Report-PO, delivery Note, Bill of lading,Header txt,GR/GI slip

    Dear Firends,
    Kindly tell me the SAP standard Report which give the details of
    Po number, delivery Note, Bill of lading, Header text and GR/GI slip no.
    Thanks in advance.
    Regards,
    william

    Hi,
    You can get all these fields in MB51 report by selecting the relavant fields in the selection variant. If any of the required fields are not available than you can add those in img -going tothe Inv Mgt-Reporting - Define field selection for material document list.
    Dhruba

  • How to create a standard report that allows filtering?

    Hi Guys and Gals,
    Sometimes, the standard report is great because it gives the user the feeling of a grid. i.e. All of the values are editable on one page, kind of like a spreadsheet. That is sometimes very useful. But if there is a lot of data, a filtering mechanism is necessary.
    So will one of you Apex gurus please tell me how to create a standard report that also allows data filtering?
    Allowing the user to specify the number of rows displayed would be peachy-keen too.
    Thanks,
    Kim
    P.S. I'm running Apex 4.1 with Oracle 11g.

    Kim2012 wrote:
    Your idea sounds very promising, but I apparently need a nudge in the right direction. From "Create Page", I clicked on "Form" and then "Tabular Form". Why would you do this? The advice given was
    create a standard report page using the Create New Page wizardi.e. go to Home > Application Builder > Application > Create Page and click Classic Report, this was suggested because the original post said:
    >
    So will one of you Apex gurus please tell me how to create a standard report that also allows data filtering?
    >
    Nothing about forms. Tabular Forms, Tabular Forms. Despite many enhancements over the last few versions, tabular forms still cause problems, especially for novices trying to go beyond their own competence and the built-in capabilities of wizard-generated tabular forms.
    More good advice: Re: Newbie question-how does the tabular form work?  How to populate prim key? and&mdash;if based on decent database design&mdash;out of the box you have a usable and robust application. Use an Interactive Report or a custom report template and add some CSS and you can get something a lot more powerful, flexible and better looking than any tabular form. Spend the time you haven't wasted on frustrated hacking of tabular forms adding more features and enhancements to your app.

Maybe you are looking for