Output Type MLGR, 'Report Goods Receipt to Buyer' not proccessed correctly

Hi
We are using output type MLGR to send a doc 'Report Goods Receipt to Buyer' which is defined
under->Output Types->Mail title and texts.
Its 'Proccessing Routine' is: RSNASTSO
Form Routine is: SAPOFFICE_AUFRUF
All is well when we use MB02 MLGR,'Simple Mail',MP, UserName
It sends the email to SAPConect.
BUT the form comes with the definitions not with the actual values.
Like so:
INCLUDE MMIM_SE71_NEUER_EDITOR_MAIL2 OBJECT DOKU ID TX LANGUAGE EN
                                         $DATE$, $TIME$
$SGF$ oder $SGH$ $EKKO-ERNAM$ !
A goods receipt for your purchase order $MSEG-EBELN$
item $MSEG-EBELP$ has just been entered.
Material:           $MSEG-MATNR$ $EKPO-TXZ01$
Quantity delivered: $MSEG-ERFMG$
Vendor:             $MSEG-LIFNR$, $AM07M-NAME1$
Posting date:       $MKPF-BLDAT$
$MFG$
    $MKPF-USNAM$
Reg's
Edan

1. use variables '&' instead of '$'
2. In transaction M706 for output type MLGR, make sure you have maintained the include by going in the long text, Choose Goto -> Change Editior, and maintain the form here :
"A goods receipt for your purchase order &MSEG-EBELN&
item &MSEG-EBELP& has just been entered.
Material: &MSEG-MATNR& &EKPO-TXZ01&
Quantity delivered: &MSEG-ERFMG&
Vendor: &MSEG-LIFNR&, &AM07M-NAME1&
Posting date: &MKPF-BLDAT&
&MFG&
&MKPF-USNAM&"
Then in MN22, delete the earlier condition record and create a new condition record in MN21
Here in the Communication in the MENU select
Goto -> Execution Parameter. You reach the dialog box Change Execution Parameter. Here you maintain the following data for mail processing:
Execution type        U   Transaction with memory
Execution element     MB03
Memory ID                  MBN
Par name: RM07M-MBLNR      Parameter value: MSEG-EBELN
Save
Then create a PO (please remember to click on the GR message in the header), and create a GR against the PO.
In SBWP, you will get the values and not definitions this time for the message created.

Similar Messages

  • Output MLGR Report Goods Receipt to Buyer

    I have configured the Output MLGR but when i edit  the text to add information to the mail the buyer receive it dosnt work.
    I have added symbols but it dosnt work
    Any ideas? Thx

    Hi Luis,
    What symbols were added and where exactly ?
    Regards
    Ramesh Ch

  • MLGR to send a doc 'Report Goods Receipt to Buyer' proccessed wrong

    Hi
    We are using output type MLGR to send a doc 'Report Goods Receipt to Buyer' which is defined
    under->Output Types->Mail title and texts.
    Its 'Proccessing Routine' is: RSNASTSO
    Form Routine is: SAPOFFICE_AUFRUF
    All is well when we use MB02 MLGR,'Simple Mail',MP, UserName
    It sends the email to SAPConect.
    BUT the form comes with the definitions not with the actual values.
    Like so:
    INCLUDE MMIM_SE71_NEUER_EDITOR_MAIL2 OBJECT DOKU ID TX LANGUAGE EN
    $DATE$, $TIME$
    $SGF$ oder $SGH$ $EKKO-ERNAM$ !
    A goods receipt for your purchase order $MSEG-EBELN$
    item $MSEG-EBELP$ has just been entered.
    Material: $MSEG-MATNR$ $EKPO-TXZ01$
    Quantity delivered: $MSEG-ERFMG$
    Vendor: $MSEG-LIFNR$, $AM07M-NAME1$
    Posting date: $MKPF-BLDAT$
    $MFG$
    $MKPF-USNAM$
    Reg's
    Edan

    1. use variables '&' instead of '$'
    2. In transaction M706 for output type MLGR, make sure you have maintained the include by going in the long text, Choose Goto -> Change Editior, and maintain the form here :
    "A goods receipt for your purchase order &MSEG-EBELN&
    item &MSEG-EBELP& has just been entered.
    Material: &MSEG-MATNR& &EKPO-TXZ01&
    Quantity delivered: &MSEG-ERFMG&
    Vendor: &MSEG-LIFNR&, &AM07M-NAME1&
    Posting date: &MKPF-BLDAT&
    &MFG&
    &MKPF-USNAM&"
    Then in MN22, delete the earlier condition record and create a new condition record in MN21
    Here in the Communication in the MENU select
    Goto -> Execution Parameter. You reach the dialog box Change Execution Parameter. Here you maintain the following data for mail processing:
    Execution type        U   Transaction with memory
    Execution element     MB03
    Memory ID                  MBN
    Par name: RM07M-MBLNR      Parameter value: MSEG-EBELN
    Save
    Then create a PO (please remember to click on the GR message in the header), and create a GR against the PO.
    In SBWP, you will get the values and not definitions this time for the message created.

  • Output type settings for Goods receipt  slip form

    Hi gurus,
            I am new to SAP and i am trying to write a functional spec based on a Goods receipt slip template the company has given me.
    can anyone tell me the standard forms and programs associated with the Goods Receipt form.also i would appreciate if someone can help me do config settings for this.
    thanks and look for ward for suggestionas and help.
    Chris

    Dear Chris ,
    You can get all data needed into tcode NACU !
    Choose Application ME and messages WE01 until WE03. Inside this customizing you can see all details that you need.
    best regards,
    Carlos Moçatto

  • Output type MLGR

    hello, friends.
    i have set up output type MLGR, medium 7 for sending via SAP mail to an internal user account, for goods receipt.
    i execute the transaction and manually include the output type during change mode MB02 for the material document.
    the system sends a message to the user account, but there are no text messages despite entering the text.  the system issues message nr VN333.
    how do i go about solving this?  or could anyone refer me to the proper thread?
    many thanks.

    hello, friend!  i figured it out. 
    for those who sent in their ideas, many thanks just the same.

  • Grn report(goods receipt notice)

    hi to all sdn people can u pls give coding for this if u give the answer i will be greatful to u and i will reward point to all of u
    my report is as follows
    a report for grn details which shows the all details of goods receipt movements based on the purcahse order.
    and pls tell what is the pupose of this report and tables used

    Hi
    Use the Tables
    EKKO,EKPO --PO tables and
    MKPF and MSEG Tables GRN related.
    This report is useful to track the qty of ggods/materials received with respect to the PO's placed.
    see the sample code and change the output as per your requirement.
    *& Report  ZMM_PO_REPORT
    REPORT  ZMM_PO_REPORT message-Id yb
           NO STANDARD PAGE HEADING
           LINE-COUNT 60(1)
           LINE-SIZE 230.
           D A T A B A S E  T A B L E S   D E C L A R A T I O N
    TABLES: lfa1,           " Vendor Master
            t161,           " PO Doc Types
            t024,           " Purchase Groups
            ekko.           " PO Header
                   T Y P E S  D E C L A R A T I O N S
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_po,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            bstyp TYPE bstyp,           " PO Category
            bukrs TYPE bukrs,           " Company Code
            bsart TYPE bbsrt,           " PO Type
            lifnr TYPE lifnr,           " Vendor No
            ekgrp TYPE bkgrp,           " Purchase Group
            waers TYPE waers,           " Currency
            bedat TYPE etbdt,           " PO Date
            txz01 TYPE txz01,           " Material Text
            werks TYPE ewerk,           " Plant
            lgort TYPE lgort_d,         " Storage Location
            matkl TYPE matkl,           " Material Group
            menge TYPE bamng,           " PR Quantity
            meins TYPE bamei,           " UOM
            bprme TYPE bbprm,           " Price Unit
            netpr TYPE netpr,           " Net price
            peinh TYPE peinh,           " Price Unit UOM
            pstyp TYPE pstyp,           " Item Category
            knttp TYPE knttp,           " Account Assignment Category
           END OF s_po.
    Purchase Orders History Structure
    TYPES: BEGIN OF s_account,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            gjahr TYPE mjahr,           " Fiscal Year
            belnr TYPE mblnr,           " PO Invoice No
            menge TYPE menge_d,         " PR Quantity
            wrbtr TYPE wrbtr,           " Price in Local Currency
            dmbtr TYPE dmbtr,           " Price in Foreign Currency
            waers TYPE waers,           " Currency
            shkzg TYPE shkzg,           " Dr/Cr Indicator
           END OF s_account.
    Purchase Orders History Structure(Item Sum)
    TYPES: BEGIN OF s_inv_sum,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            menge TYPE menge_d,         " PR Quantity
            wrbtr TYPE wrbtr,           " Price in Foreign Currency
            waers TYPE waers,           " Currency
           END OF s_inv_sum.
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_rep,
            lifnr TYPE lifnr,           " Vendor No
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            bstyp TYPE bstyp,           " PO Category
            bsart TYPE bbsrt,           " PO Type
            ekgrp TYPE bkgrp,           " Purchase Group
            waers TYPE waers,           " Currency
            bedat TYPE etbdt,           " PO Date
            txz01 TYPE txz01,           " Material Text
            werks TYPE ewerk,           " Plant
            lgort TYPE lgort_d,         " Storage Location
            matkl TYPE matkl,           " Material Group
            menge TYPE bamng,           " PR Quantity
            meins TYPE bamei,           " UOM
            bprme TYPE bbprm,           " Price Unit
            netpr TYPE netpr,           " Net price
            peinh TYPE peinh,           " Price Unit UOM
            pstyp TYPE pstyp,           " Item Category
            knttp TYPE knttp,           " Account Assignment Category
            name1 TYPE name1,           " Plant
            orewr TYPE netpr,           " To be Invoiced Price
            curr  TYPE waers,           " Inv Doc Currency
           END OF s_rep.
               D A T A  D E C L A R A T I O N S
    DATA: gv_title1 TYPE sylisel,            " Report title
          gv_dial.                           " Color flag
                C O N S T A N T S  D E C L A R A T I O N S
    CONSTANTS: c_x                VALUE 'X',   " Flag X
               c_h                VALUE 'H',   " Debit
               c_vgabe TYPE vgabe VALUE '2'.   " Transaction Type
         I N T E R N A L  T A B L E S  D E C L A R A T I O N S
    DATA: i_po    TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
                                 " Purchase Order
          i_inv   TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
                                         " PO Invoice Values
          i_rep   TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
                                     " PO Invoice Values
          i_ekbe  TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
                               " PO Invoice Values
                     S E L E C T I O N  S C R E E N                      *
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
                    s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
                    s_bsart FOR t161-bsart,
                    s_ekgrp FOR t024-ekgrp,
                    s_bedat FOR ekko-bedat.
    SELECTION-SCREEN END OF BLOCK b1.
                      I N I T I A L I Z A T I O N                        *
    INITIALIZATION.
                  A T  S E L E C T I O N - S C R E E N                   *
    AT SELECTION-SCREEN.
    Validate the screen fields
      PERFORM validate_screen.
                   S T A R T - O F - S E L E C T I O N                   *
    START-OF-SELECTION.
    Fetch main data
      PERFORM fetch_data.
                   T O P - O F - P A G E                                 *
    TOP-OF-PAGE.
    Header of the List
      PERFORM header.
                   E N D - O F - P A G E                                 *
    Footer
    END-OF-PAGE.
      ULINE.
                   E N D - O F - S E L E C T I O N                       *
    END-OF-SELECTION.
    Display the Report Output data
      PERFORM display_data.
    At Line-Selection
    AT LINE-SELECTION.
    When double clicked on EBELN display the details of Purchase Doc
      PERFORM line_sel.
    *&      Form  validate_screen
    Validation of Selection Screen fields
    FORM validate_screen .
    Validation of Vendor Number
      CLEAR lfa1-lifnr.
      IF NOT s_lifnr[] IS INITIAL.
        SELECT lifnr UP TO 1 ROWS
            INTO lfa1-lifnr
            FROM lfa1
            WHERE lifnr IN s_lifnr.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Vendor'(002).
        ENDIF.
      ENDIF.
    Validation of PO Number
      CLEAR ekko-ebeln.
      IF NOT s_ebeln[] IS INITIAL.
        SELECT ebeln UP TO 1 ROWS
            INTO ekko-ebeln
            FROM ekko
            WHERE ebeln IN s_ebeln.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Document Number'(003).
        ENDIF.
      ENDIF.
    Validation of PO Document Type
      CLEAR t161-bsart.
      IF NOT s_bsart[] IS INITIAL.
        SELECT bsart UP TO 1 ROWS
            INTO t161-bsart
            FROM t161
            WHERE bsart IN s_bsart.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
        ENDIF.
      ENDIF.
    Validation of Purchasing Group
      CLEAR t024-ekgrp.
      IF NOT s_ekgrp[] IS INITIAL.
        SELECT ekgrp UP TO 1 ROWS
            INTO t024-ekgrp
            FROM t024
            WHERE ekgrp IN s_ekgrp.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
        ENDIF.
      ENDIF.
    ENDFORM.                    " validate_screen
    *&      Form  fetch_data
    Fetching the PO related data from Database Tables
    FORM fetch_data .
      CLEAR i_po.
      REFRESH i_po.
      SELECT a~ebeln            " PO No.
             b~ebelp            " PO Item
             a~bstyp            " PO Category
             a~bukrs            " Company Code
             a~bsart            " PO Type
             a~lifnr            " Vendor No
             a~ekgrp            " Purchase Group
             a~waers            " Currency
             a~bedat            " PO Date
             b~txz01            " Material Text
             b~werks            " Plant
             b~lgort            " Storage Location
             b~matkl            " Material Group
             b~menge            " PR Quantity
             b~meins            " UOM
             b~bprme            " Price Unit
             b~netpr            " Net price
             b~peinh            " Price Unit UOM
             b~pstyp            " Item Category
             b~knttp            " Account Assignment Category
        INTO TABLE i_po
        FROM ekko AS a JOIN ekpo AS b
        ON a~ebeln = b~ebeln
        WHERE a~ebeln IN s_ebeln AND
              a~lifnr IN s_lifnr AND
              a~ekgrp IN s_ekgrp AND
              a~bsart IN s_bsart AND
              a~bedat IN s_bedat.
      SORT i_po BY ebeln ebelp.
      break-point.
      IF NOT i_po[] IS INITIAL.
    Fetch the PO History/Invoice Details from EKBE Table
        CLEAR i_ekbe.
        REFRESH i_ekbe.
        SELECT ebeln           " PO No.
               ebelp           " PO Item
               gjahr           " Fiscal Year
               belnr           " PO Invoice No
               menge           " PR Quantity
               wrbtr           " Price in Local Currency
               dmbtr           " Price in Foreign Currency
               waers           " Currency
               shkzg           " Dr/Cr Indicator
         INTO TABLE i_ekbe
         FROM ekbe
         FOR ALL ENTRIES IN i_po
         WHERE ebeln = i_po-ebeln AND
               ebelp = i_po-ebelp AND
               vgabe = c_vgabe.
      break-point.
        IF sy-subrc = 0.
          SORT i_ekbe BY ebeln ebelp.
          LOOP AT i_ekbe.
            IF i_ekbe-shkzg = c_h.
              i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
            ENDIF.
            MODIFY i_ekbe.
          ENDLOOP.
      break-point.
    Sum up the Item wise Invoice totals
          LOOP AT i_ekbe.
            AT END OF ebelp.
              READ TABLE i_ekbe INDEX sy-tabix.
              SUM.
              MOVE-CORRESPONDING i_ekbe TO i_inv.
              APPEND i_inv.
            ENDAT.
            CLEAR i_inv.
          ENDLOOP.
          SORT i_inv BY ebeln ebelp.
            break-point.
        ENDIF.
      ENDIF.
    Move the Vendor Name and Invoice Values to I_rep Internal Table
      LOOP AT i_po.
        MOVE-CORRESPONDING i_po TO i_rep.
        CLEAR i_inv.
        READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
                                  ebelp = i_po-ebelp.
        IF sy-subrc = 0.
          i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
          i_rep-curr  = i_inv-waers.
        ELSE.
          i_rep-orewr = i_po-menge * i_po-netpr.
          i_rep-curr  = i_po-waers.
        ENDIF.
      break-point.
    Get the Vendor Name
        CLEAR lfa1-name1.
        SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
          WHERE lifnr = i_po-lifnr.
        IF sy-subrc = 0.
          i_rep-name1  = lfa1-name1.
        ENDIF.
        APPEND i_rep.
        CLEAR  i_rep.
          break-point.
      ENDLOOP.
      SORT i_rep BY lifnr ebeln ebelp.
      DELETE i_rep WHERE orewr LE 0.
      break-point.
    ENDFORM.                    " fetch_data
    *&      Form  display_data
    Display the Report Output data
    FORM display_data .
      DATA: lv_flag,               " New Flag
            lv_rec TYPE i.         " No of Records
      CLEAR lv_rec.
      IF i_rep[] IS INITIAL.
        MESSAGE e000 WITH 'No Data found'(022).
      ELSE.
        LOOP AT i_rep.
    Toggle Color
          PERFORM toggle_color.
          IF lv_flag <> space.
            NEW-LINE.
          ENDIF.
    At New Purchase Document
          AT NEW ebeln.
            WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
            lv_flag = c_x.
            lv_rec = lv_rec + 1.
          ENDAT.
          WRITE: 1 sy-vline,
                12 sy-vline,13(4)   i_rep-bsart,
                17 sy-vline,18(10)  i_rep-lifnr,
                28 sy-vline,29(35)  i_rep-name1,
                64 sy-vline,65(4)   i_rep-ekgrp,
                69 sy-vline,70(10)  i_rep-bedat,
                80 sy-vline,81(5)   i_rep-ebelp,
                86 sy-vline,87(40)  i_rep-txz01,
               127 sy-vline,128(9)  i_rep-matkl,
               137 sy-vline,138(1)  i_rep-pstyp,
               139 sy-vline,140(1)  i_rep-knttp,
               141 sy-vline,142(4)  i_rep-werks,
               146 sy-vline,147(4)  i_rep-lgort,
               151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
               165 sy-vline,166(3)  i_rep-meins,
               169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
               185 sy-vline,186(4)  i_rep-waers,
               190 sy-vline,191(5)  i_rep-peinh,
               196 sy-vline,197(4)  i_rep-bprme,
               201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
               217 sy-vline,218(4)  i_rep-curr,
               222 sy-vline,223(7)  i_rep-bstyp centered,
               230 sy-vline.
          NEW-LINE.
          hide: i_rep-ebeln.
        ENDLOOP.
        ULINE.
        FORMAT COLOR OFF.
        WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
                    lv_rec COLOR 3.
      ENDIF.
    ENDFORM.                    " display_data
    *&      Form  header
    Write the Report Header
    FORM header .
      FORMAT RESET.
    header
      WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
      SKIP.
      FORMAT COLOR COL_HEADING.
      ULINE.
      WRITE:/1 sy-vline,2(10)   'Pur.Doc.No'(006) CENTERED,
            12 sy-vline,13(4)   'Type'(007),
            17 sy-vline,18(10)  'Vendor'(008) CENTERED,
            28 sy-vline,29(35)  'Name'(009) CENTERED,
            64 sy-vline,65(4)   'PGrp'(010) CENTERED,
            69 sy-vline,70(10)  'Doc.Date'(012) CENTERED,
            80 sy-vline,81(5)   'Item'(011),
            86 sy-vline,87(40)  'Material Short Text'(024) CENTERED,
           127 sy-vline,128(9)  'Mat.Group'(013),
           137 sy-vline,138(1)  'I',
           139 sy-vline,140(1)  'A',
           141 sy-vline,142(4)  'Plnt'(014),
           146 sy-vline,147(4)  'SLoc'(015),
           151 sy-vline,152(13) 'Quantity'(016) CENTERED,
           165 sy-vline,166(3)  'UoM'(017),
           169 sy-vline,170(15) 'Net Value'(018) CENTERED,
           185 sy-vline,186(4)  'Curr'(019),
           190 sy-vline,191(5)  'Per'(020),
           196 sy-vline,197(4)  'Unit'(021),
           201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
           217 sy-vline,218(4)  'Curr'(019),
           222 sy-vline,223(7)  'Doc.Cat'(026),
           230 sy-vline.
      ULINE.
    ENDFORM.                    " header
    *&      Form  toggle_color
    This routine alters the color of the records in the list
    FORM toggle_color.
      IF gv_dial = space.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        gv_dial = c_x.
      ELSE.
        FORMAT COLOR 1 INTENSIFIED OFF.
        CLEAR gv_dial.
      ENDIF.
    ENDFORM.                    " toggle_color
    *&      Form  LINE_SEL
    *When double clicked on EBELN field display the details of Purchase Doc
    FORM line_sel.
      CASE sy-lsind.
        WHEN '1'.
          DATA: lv_field(20),
                lv_value(10),
                lv_bstyp like i_rep-bstyp.
          clear: lv_bstyp,lv_value, lv_field.
          GET CURSOR FIELD lv_field VALUE lv_value.
          IF lv_field = 'I_REP-EBELN'.
            IF NOT lv_value IS INITIAL.
              READ LINE sy-index FIELD VALUE i_rep-bstyp
                                       INTO  lv_bstyp.
             READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
              if lv_bstyp = 'F'.
                SET PARAMETER ID 'BES' FIELD lv_value.
                CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
              elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
                SET PARAMETER ID 'VRT' FIELD lv_value.
                CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
              elseif lv_bstyp = 'A'.
                SET PARAMETER ID 'ANF' FIELD lv_value.
                CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
              endif.
            ENDIF.
          ENDIF.
      ENDCASE.
    ENDFORM.                    " line_sel
    Reward points if useful
    Regards
    Anji

  • Detect output type of report

    Hello everybody!
    Is there a possibility to detect the chossen output type when rendering a report?
    I have created a list report which contains an image in the page header. This should only appear on PDF, RTF and HTML output types, in XLS it is not displayed and therefore should be skipped.
    Thank you for any assistance,
    Stefan Dase

    Hey Rainer,
    thank you for the good advice. Indeed I can determine the output type with the parameter $_xf. This works fine if we use the BI Publisher web interface or request a report by URL.
    Sadly it doesn't work if we use the BIP Webservice! Maybe it isn't possible to detect the output type if we use the Webservice? So I will use a explicit parameter instead and close this question as answered.
    Regards,
    Stefan
    P.S.: Just saw you use this as new tip for the German Community! ;-)

  • Movement type for a goods receipt for u201CRelease order for a PRqRel"

    There is an intercompany sales at our case. Plant B enters the customer order by VA01. The requirements rooting from the customer order are bought from plant A  by Plant B. u201CRelease order for a stock transfer requisitionu201D is created automatically by entering the customer order and later using the TCode MD02. By this way Plant A can see the reauirements fort he customer order at Plant B. For the test purposes, I want to make a goods receipt for the u201CRelease order for a stock transfer requisitionu201D. The receipr will be at the Plant A but the customer order is at the Plant B. By the way, I have to point out that Plant A and Plant B are assigned to different company codes. How can I make the goods receipt? I cannot use 561 E. Because customer order belongs to differen company code. I fact, production should be done for this aspect but I donu2019t have enough experience for producing the goods by myself. Which movement type should I use for making a goods receipt for the u201CRelease order for a stock transfer requisitionu201D at Plant A?
    Thanks in advance fort he answersu2026

    Hi,
    This is controlled by the schedule line category In VOV6.
    Just check which category is used in your scenarion and change the movement type here. (I think your entry is NC)
    They are determined by the item category and MRP type in SPRO - SD > Sales > Sales Documents > Schedule lines
    Steve B

  • Earmarked funds during goods receipt (GR) is not inherited from PO.

    Hi, Everybody u2026
    We are using Earmarked Funds relevant for FM updating, but, during goods receipt (GR) and invoice receipt (IR) it is not inherited from purchase order (PO).
    In ME21N the account assignment is F and the system ask us to enter the GL Account, Order and additional the Earmarked Funds. The system is deriving correctly the fund, the funds center and the commitment item from those entered in the Earmarked Funds.
    However, during goods receipt and invoice receipt, the Earmarked Funds is not inherited from purchase order (PO) besides the others account assignments (order, fund, funds center and commitment item ) in the coding block.
    Best regards,
    Thanks

    Hello,
    I will provide some hints:
    - If it is a service PO, please check the Note 972276 (Service Purchase orders only).
    - If the posting is related to Asset, please kindly check:
        a. Note 684659
        b. Check if you have a derivation rule in FMDERIVE with the function module FMDT_READ_MD_ASSET.
        c. Check in your FI-AA customizing if you have activated the account
          assignment element but you have not specified an account assignment type for
          account assignment object for APC balance sheet postings (see note 684659 for
          details).
    I hope it helps
    Best Regards,
    Vanessa Barth.

  • Goods receipt for credit note

    Hi,
    We received a credit note assigned to a purchase order. How can we post a corresponding credit goods receipt?
    Thanks and regards
    Aparna

    HI!
    You can  use T-code: FB65  and  MIRO for  Sub Debit/Credit note.(Creditnote)
    regards,
    Rup

  • UsersByGroup SS report crashing;Shared Services Users not removed correctly

    Apparently, there are not many experts on Shared Services – nor is there much documentation.
    We have an urgent need to get a Users By Group report successfully run from an Shared Services installation today (auditors!)! Opening a support ticket as well as making last ditch attempts to get more suggestions on how to resolve.
    It appears as those the users causing the problem (the UsersByGroup Shared Services reports crashes) are NTLM. Apparently, several users were removed – before they were de-provisioned. Now they are not appearing on the default area but are appearing in other areas within SS. An attempt to re-add them failed to sync them back up (likely gave them each a new SID). We believe it is likely that the two issues are related (the not quite completely deleted users and the User By Group report bombing out – due to a user – since the provisioning is there, but the user is not, for these instances). Two of the Users show under Admin also, which should not be the case.
    Any suggestions on next steps would be greatly appreciated.
    Thanks!

    Hi,
    You should have a look at using the Update Native Directory Utility, this will clear out any stale users in your OpenLdap.
    It should be situated in \Hyperion\common\utilities\SyncOpenLdapUtility
    There is a zipped file called UpdateNativeDir.zip
    It does have a read me on how to use it but it is pretty simple, on windows it is something like updateNativeDir.bat -cssLocation <location to your>CSS.xml
    e.g updateNativeDir.bat -cssLocation C:\Hyperion\deployments\Tomcat5\SharedServices9\config\CSS.xml
    You may need to update the bat file to include the correct location to your Java Home, you will get an error message anyway if it is not set correctly when you run the batch file.
    It will create a log of all stale users removed.
    Good luck.
    John

  • Single Report Goods Receipt to Vendor Payment ( GR-IV-vendor payment)

    Hi Friends,
    My client wants to asking the single report for GR to Vendor payment. Please let me know how to get the report?
    Regards,
    Chandra.

    Dear Chandra,
    To my knowledge, there is no standard report available for this.
    You can use the tables BKPF, BSEG, MKPF and MSEG for creating a report.
    Kindly close this thread in this forum and raise the same question in MM and FI. So you might get answers for your query.
    Best Regards,
    Raj

  • Valuation type change in goods receipts

    Dear Experts,
    We are creating the stock transfer through out bound delivery.
    In out bound delivery we are changing the valuation type.. But while creating the GR system is asking the old valuation  type which is present in the PO.
    We want new valuation type in the GR.
    Flow is as -
    PO with valuation type- outbound delivery( in this val type is changed)- Then GR ( wrf PO)
    please suggest.
    Thank you in advance.

    Hi,
    During GR system will not allow to change valuation type. since ur doing GR wrt to PO, u need to change it in PO only.
    One more option u need to try it out is ,
    create inbound delivery wrt PO and see u can change it in inbound delivery if u dont want to change it in PO, then u can do GR wrt inbound delivery.

  • Crystal report of label size is not printing correctly

    Hi,
    we have interated  crystal report CR4E version with our application and facing 2 issue when i am generating crystal reports from application.
    we are  having a crystal report designed for label size. 
    1.
    While generate the report from application with output as a pdf browser and print to label printer (DYMO Label Writer 400) all the records(for example:7) are getting printed in a single label .
    when the same report is generated from crystal report software and print to label printer (DYMO prinetr 400) all the records (For example:7 records) it is printing  each record per page (for example :7 pages).
    2.
    When i am generating crystal report of label size from my application and  getting the binary data . When  i am sending this binary data to a label printer(DYMO Label writer 400) i am getting an exception "printer's imageable width is too small".
    i am using CR4E crystal report version and java 1.5 verison.The paper size of the label printer (DYMO label Writer 400)" 30252 Address"
    can any one please help me on this issues.
    Advacne thanks
    Rajesh

    Hi Aasavari Bhave,
    Thanks for your Quick Reply.
    <<Also, when you see the report exported as PDF in the browser, are you seeing all records\labels on 1 page or are they separated across several pages just like in CR Designer>>
    when i export the report all the records are seperated across several pages. i am using adobe print to print the report.
    <<How are you printing the report, using Adpbe print or printoutputcontroller.printreport?>>
    I am printing the report using  in 2 different ways.
    1. Using adobe print
    I have designed the label report for 1.1 height and 3.5 width  in crystal report designer. but when i generate the report with pdf browser as output the report height and width are 11.0 height and 8.50 width.
    2. Using printoutputcontroller
    I am printing the report directly from the application using printoutput controller . when i print using print output controller i am getting an exception "printer's imageable width is too small".
    My application is developed in java. Please help me to display this report in my application as per the page size I mentioned and also how can i avoid the exception  "printer's imageable width is too small".

  • Discoverer Report opened from Portal does not show correct data

    Hi,
    When I try to open a Discoverer report from a portal that I created, it shows stale data but when I click on "Analyze", it shows all the data correctly.
    Does anyone know what the reason could be for this?
    Thank you,
    Santoshi

    I assume you used the Discoverer Portlet Provider. A discoverer portlet is never live data. When you define the portlet you specify how often to 'refresh' the data. If you skipped this step, then you just get the data as-of when you created the portlet.
    Generally you specify the refresh time to be sometime after your usual database load completes.

Maybe you are looking for