Error in consignment consumption

Hi All,
I had done 411k to transfer stock from consignment to unrestricted. now i m doing 201k and is giving error msg "Deficit of VC Unrestricted-use 1 nos : 300000010 FORG SCON K".

Hi
consignment to consumption direct do 201k no need to take into own stock,
we you take into own stock with 411k do it with 201.no need of 201k movement type here
hope solve the problem.
Regards,
Varun

Similar Messages

  • Error in consignment settlement

    Hi,
    I am getting the error for consignment settlement as follows:
    Document 5100000007 MUL does not exist in fiscal year 2009
    MUL is company code.
    Pls guide.
    Regards.

    Hi,
    Go to OMBT, check whether you have maintain number range as year Specific or maintain year 9999.
    if you have maintain year specific then maintain for 2009.
    but basically it not year specific as i think then go to MB03 and check ur doument for which year it is created.
    Now, may be you have posted that stock before april. then change to 2008 and go the settlement.c
    if this is accounting document then go to FBN1 and maintain year specific number range
    Regards,
    Pardeep malik

  • Cogi error - Pipeline/consignment movement posted without value

    Hi
    I am getting a Cogi error Pipeline/consignment movement posted without value
    This particular material was not having problem till last week and now all the time when confirmation of production order happens it goes to cogi with error
    Price is maintained in info record
    Please suggest

    Dear friend,
    some theory:
    You always have 2 options - delete or process your COGI record.
    Before to make a decision you need to analyse/find a reason why this error has happened.
    run COGI;
    tick your eror;
    hit F6 (display errors) - bell icon
    now you are able to see the reason.
    depends on a reason (information you see now) you do your next steps
    say, for instance, you did something to fix the reason,...
    then
    if you want to process, tick your error and Save
    if everything is okay - system will POST it (cogi record will go away)
    or , say, you do not care about the error -
    tick your error and Delete
    some practice:
    please have a look at your material - probably someone changed it very recently - look at last changes using MM04 or MM03
    good luck

  • Error while doing consumption posting

    Dear all,
    There is sufficient amount of quantity for particular batch,but while posting consumption it is showing error.
    Error is: Deficit of BA Unrestricted use.
    please guide me to solve this issue.
    Regards,
    santosh.

    Dear Santosh,
    You are not able to see the radio button that our friends are suggesting because in the configuration at
    SPRO-> Logistics - General->Batch Management->Specify Batch Level and Activate Status Management Execute-->Click on Batch Status Management is Inactive
    Now coming back to your main problem of error of Deficit........
    Pls check that to stock you are looking for is available in correct Plant--Storage Location. And if you are WM managed then in correct bin as well.
    Then check the reservations also if the batch is already reserved against something else then also this happens.
    And fially check the dates also in the posting document, and check that the same stock - batch combination available in that date.
    Even after that if the error remains than pls elaborate your transaction.
    Regards,
    Shyamal

  • GRN error for Consignment PO

    Hi,
    I have created consignment info record and created consignment PO.
    but at the time of GRN I am getting the error " the purchasing info record not created for Purchase organisation"
    message no M7 165..
    Why I am getting the error even after maintaining the Info record.
    thanks in Advance

    also check whether the Consignment info record is created for Standard Purchase organisation ?
    If not created the same under Standard Purchase organisation .

  • LSMW error in material consumption value upload

    Hi Guys,
    I am using standard program RMDATIND for creating LSMW to upload consumption value for materials , i am getting error consumption period can not be determined, can anybody tell me what period format should be used?
    Thanks and regards
    Thamizhchelvan G

    Hi,
    It would be helpful if you have identified the issue.
    Please let us know the resolution, which would help me.
    I am facing the same issue.
    Thanks
    Sudheer

  • Dump Error in MAterial Consumption Report

    Hi all Gurus
    [1] I need help from your side i am doing one material consumption report in that i did all thing but it is giving me dump error while i was using sort  in to ALV
    so please any one help me out this .......
    [2] I am Printing sum of quantity in Header area of smartform it is printing with using comma e.x 43,000 but in body area it is showing with decimal point
    e.x 43.000
    Following is my ALV reports code please check it it is giving me short dump while using sort ..............
    I am very much in neeed
    Thanx for your suggestion in advanc.....
    and god bless you............
    *& Report  ZCONSUM
    REPORT  ZCONSUM.
    *& Report  ZCONSUMPTION
    TYPE-POOLS : SLIS.
    TABLES:marc,
           mara,
           makt,
           mard,
           mbew,
           mseg,
           mkpf.
    TYPES:
            BEGIN OF s_mseg,
                mblnr LIKE mseg-mblnr,
                mjahr LIKE mseg-mjahr,
                zeile LIKE mseg-zeile,
                bwart LIKE mseg-bwart,
                matnr LIKE mseg-matnr,
                werks LIKE mseg-werks,
                menge LIKE mseg-menge,
                budat LIKE mkpf-budat,
                mtart LIKE mara-matnr,
                matkl LIKE mara-matkl,
            END OF s_mseg,
            BEGIN OF s_t001w,
                werks LIKE t001w-werks,
                name1 LIKE t001w-name1,
            END OF s_t001w,
            BEGIN OF s_mara,
                matnr LIKE mara-matnr,
                mtart LIKE mara-mtart,
                matkl LIKE mara-matkl,
            END OF s_mara,
            BEGIN OF s_makt,
                matnr LIKE makt-matnr,
                spras LIKE makt-spras,
                maktx LIKE makt-maktx,
            END OF s_makt,
           BEGIN OF s_calc,
                matnr       LIKE mara-matnr,
                mtart       LIKE mara-mtart,
                matkl       LIKE mara-matkl,
                maktx       LIKE makt-maktx,
               menge_t     LIKE mseg-menge,
               menge_t1    LIKE mseg-menge,
                menge_con_261   LIKE mseg-menge,
                menge_con_262   LIKE mseg-menge,
                menge_con1_261  LIKE mseg-menge,
                menge_con1_262  LIKE mseg-menge,
                menge_ret_291   LIKE mseg-menge,
                menge_ret1_291  LIKE mseg-menge,
                menge_ret_292   LIKE mseg-menge,
                menge_ret1_292  LIKE mseg-menge,
                menge_unit_301  LIKE mseg-menge,
                menge_unit1_301 LIKE mseg-menge,
                menge_unit_302  LIKE mseg-menge,
                menge_unit1_302 LIKE mseg-menge,
                menge_sub   LIKE mseg-menge,
                menge_sub1   LIKE mseg-menge,
                menge_oth   LIKE mseg-menge,
                menge_oth1  LIKE mseg-menge,
            END OF s_calc,
            BEGIN OF s_data,
                matnr       LIKE mara-matnr,
                matkl       LIKE mara-matkl,
                mtart       LIKE mara-mtart,
                maktx       LIKE makt-maktx,
                menge_t     LIKE mseg-menge,
                menge_t1    LIKE mseg-menge,
                menge_con   LIKE mseg-menge,
                menge_con1  LIKE mseg-menge,
                menge_ret   LIKE mseg-menge,
                menge_ret1  LIKE mseg-menge,
                menge_unit  LIKE mseg-menge,
                menge_unit1 LIKE mseg-menge,
                menge_sub   LIKE mseg-menge,
                menge_sub1   LIKE mseg-menge,
                menge_oth   LIKE mseg-menge,
                menge_oth1  LIKE mseg-menge,
            END OF s_data.
    DATA:   w_mseg TYPE s_mseg,
            i_mseg TYPE s_mseg OCCURS 0,
            w_t001w TYPE s_t001w,
            i_t001w TYPE s_t001w OCCURS 0,
            w_mara TYPE s_mara,
            i_mara TYPE s_mara OCCURS 0,
            w_makt TYPE s_makt,
            i_makt TYPE s_makt OCCURS 0,
            w_calc TYPE s_calc,
            i_calc TYPE s_calc OCCURS 0,
            w_data TYPE s_data,
            i_data TYPE s_data OCCURS 0.
    DATA:   line_cnt TYPE i,
            v_temp TYPE p DECIMALS 2.
    ALV DATA DECLERATION
    DATA : IT_FIELD TYPE SLIS_T_FIELDCAT_ALV,
           WA_FIELD TYPE SLIS_FIELDCAT_ALV.
    DATA : IT_LAYOUT TYPE SLIS_LAYOUT_ALV.
    IT_LAYOUT-ZEBRA = 'X'.
    IT_LAYOUT-TOTALS_TEXT = 'Grand Total'.
    IT_LAYOUT-SUBTOTALS_TEXT = 'Sub Total'.
    IT_LAYOUT-INFO_FIELDNAME = 'LINE_COLOR'.
    DATA: WA_COMMENTRY TYPE SLIS_LISTHEADER.
    DATA: IT_COMMENTRY TYPE SLIS_T_LISTHEADER.
    DATA: WA_COMMENTRY1 TYPE SLIS_LISTHEADER.
    DATA: IT_COMMENTRY1 TYPE SLIS_T_LISTHEADER.
    DATA: WA_EVENT TYPE SLIS_ALV_EVENT.
    DATA: IT_EVENT TYPE SLIS_T_EVENT.
    WA_EVENT-NAME = 'TOP_OF_PAGE'.
    WA_EVENT-FORM = 'TOP'.
    APPEND WA_EVENT TO IT_EVENT.
    DATA : WA_SORT TYPE slis_sortinfo_alv,
           IT_SORT TYPE SLIS_T_SORTINFO_ALV.
    CLEAR WA_SORT.
    WA_SORT-SPOS = '1'.
    WA_SORT-FIELDNAME = 'MATKL'.
    WA_SORT-TABNAME = 'I_DATA'.
    WA_SORT-SUBTOT = 'X'.
    APPEND WA_SORT TO IT_SORT.
    CLEAR WA_SORT.
    WA_SORT-SPOS = '2'.
    WA_SORT-FIELDNAME = 'MTART'.
    WA_SORT-TABNAME = 'I_DATA'.
    WA_SORT-SUBTOT = 'X'.
    APPEND WA_SORT TO IT_SORT.
    DEFINE MAC1.
    WA_FIELD-TABNAME = 'I_DATA'.
    WA_FIELD-FIELDNAME = &1.
    WA_FIELD-COL_POS = &2.
    WA_FIELD-SELTEXT_L =&3.
    WA_FIELD-DO_SUM = &4.
    APPEND WA_FIELD TO IT_FIELD.
    END-OF-DEFINITION.
    MAC1 'MATKL'        '1'  'MATERIAL GROUP' 'X'.
    MAC1 'MTART'        '2'  'MATERIAL TYPE' 'X'.
    MAC1 'MATNR'        '3'  'MATERIAL NO'  'X'.
    MAC1 'MAKTX'        '4'  'DESCRIPTION' 'X'.
    MAC1 'MENGE_CON1'   '5'  'CONSUMPTION FOR PERIOD' 'X'.
    MAC1 'MENGE_CON'    '6'  'CONSUMPTION FOR CUMULATIVE' 'X'.
    MAC1 'MENGE_RET1'   '7'  'RETURN FROM DEPT. FOR PERIOD' 'X'.
    MAC1 'MENGE_RET'    '8'  'RETURN FROM DEPT.CUMULATIVE' 'X'.
    MAC1 'MENGE_UNIT1'  '9'  'INTER UNIT FOR PERIOD' 'X'.
    MAC1 'MENGE_UNIT'   '10'  'INTER UNIT CUMULATIVE' 'X'.
    MAC1 'MENGE_SUB1'   '11' 'SUB CONTRACTOR FOR PERIOD' 'X'.
    MAC1 'MENGE_SUB'    '12' 'SUB CONTRACTOR CUMULATIVE' 'X'.
    MAC1 'MENGE_OTH1'   '13' 'OTHERS FOR PERIOD' 'X'.
    MAC1 'MENGE_OTH'    '14' 'OTHERS CUMULATIVE' 'X'.
    MAC1 'MENGE_t1'     '15' 'TOTAL FOR PERIOD' 'X'.
    MAC1 'MENGE_t'      '16' 'TOTAL CUMULATIVE' 'X'.
    SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE text-001.
      PARAMETERS: p_werks LIKE t001w-werks DEFAULT '1023' OBLIGATORY.
      select-options: s_matkl     FOR mara-matkl,
                      s_mtart     FOR mara-mtart,
                      s_matnr     FOR mara-matnr,
                      s_budat     FOR mkpf-budat OBLIGATORY.
    PARAMETERS: year(4) DEFAULT '2007'.
      SELECTION-SCREEN:END OF BLOCK B1.
      START-OF-SELECTION.
      SELECT lk~mblnr
             lk~mjahr
             lk~budat
             lp~zeile
             lp~bwart
             lp~matnr
             lp~werks
             lp~menge
             ma~mtart
             ma~matkl
             INTO CORRESPONDING FIELDs OF TABLE i_mseg
             FROM MSEG AS lp INNER JOIN MKPF AS lk
             ON lkmblnr EQ lpmblnr
             AND lkmjahr EQ lkmjahr
             INNER JOIN mara AS ma
             ON mamatnr EQ lpmatnr
             WHERE lp~werks EQ p_werks
               AND lp~matnr IN s_matnr
               AND lk~budat LE s_budat-high.
          clear line_cnt.                         "Count line of i_table i_mseg
          DESCRIBE TABLE i_mseg LINES line_cnt.
          IF  line_cnt GT 0.                      "If i_mseg has records
              SELECT matnr                        "Collect material description
                     maktx
                     spras
                     INTO CORRESPONDING FIELDS OF TABLE i_makt
                     FROM makt
                     FOR ALL ENTRIES IN i_mseg
                     WHERE matnr EQ i_mseg-matnr
                       AND spras EQ 'E'.
                CLEAR line_cnt.
                DESCRIBE TABLE i_makt LINES line_cnt.
                IF line_cnt GT 0.
                   SORT i_makt BY MATNR ASCENDING.
                   DELETE ADJACENT DUPLICATES FROM i_makt COMPARING matnr.
                ENDIF.
              SELECT werks                        "Collect plant name
                     name1
                     INTO CORRESPONDING FIELDS OF TABLE i_t001w
                     FROM t001w
                     FOR ALL ENTRIES IN i_mseg
                     WHERE werks EQ i_mseg-werks.
                CLEAR line_cnt.
                DESCRIBE TABLE i_t001w LINES line_cnt.
                IF line_cnt GT 0.
                   SORT i_t001w BY werks ASCENDING.
                   DELETE ADJACENT DUPLICATES FROM i_t001w COMPARING werks.
                ENDIF.
               LOOP AT i_mseg INTO w_mseg.        "Move recored into data i_tab
                w_calc-matnr  = w_mseg-matnr.
                w_calc-mtart = w_mseg-mtart.
                w_calc-matkl = w_mseg-matkl.
                READ TABLE i_makt WITH KEY matnr = w_mseg-matnr INTO w_makt.
                 IF sy-subrc = 0.
                    w_calc-maktx = w_makt-maktx.
                 ENDIF.
                IF w_mseg-bwart EQ '261' .
                   w_calc-menge_con_261   = w_mseg-menge.
                   IF w_mseg-budat GE s_budat-low.
                      w_calc-menge_con1_261   = w_mseg-menge.
                   ENDIF.
                ENDIF.
                IF w_mseg-bwart EQ '262' .
                   w_calc-menge_con_262   = w_mseg-menge.
                   IF w_mseg-budat GE s_budat-low.
                      w_calc-menge_con1_262   = w_mseg-menge.
                   ENDIF.
                ENDIF.
                IF w_mseg-bwart EQ '291' OR w_mseg-bwart EQ '201'.
                   w_calc-menge_ret_291 = w_mseg-menge.
                   IF w_mseg-budat GE s_budat-low.
                      w_calc-menge_ret1_291   = w_mseg-menge.
                   ENDIF.
                ENDIF.
                IF w_mseg-bwart EQ '292' OR w_mseg-bwart EQ '202'.
                   w_calc-menge_ret_292   = w_mseg-menge.
                   IF w_mseg-budat GE s_budat-low.
                      w_calc-menge_ret1_292   = w_mseg-menge.
                   ENDIF.
                ENDIF.
                IF w_mseg-bwart EQ '301'.
                   w_calc-menge_unit_301   = w_mseg-menge.
                   IF w_mseg-budat GE s_budat-low.
                      w_calc-menge_unit1_301   = w_mseg-menge.
                   ENDIF.
                ENDIF.
                IF w_mseg-bwart EQ '302'.
                   w_calc-menge_unit_302   = w_mseg-menge.
                   IF w_mseg-budat GE s_budat-low.
                      w_calc-menge_unit1_302   = w_mseg-menge.
                   ENDIF.
                ENDIF.
                IF w_mseg-bwart EQ '543'.
                   w_calc-menge_sub   = w_mseg-menge.
                   IF w_mseg-budat GE s_budat-low.
                      w_calc-menge_sub1   = w_mseg-menge.
                   ENDIF.
                ENDIF.
                    COLLECT w_calc INTO i_calc.
               ENDLOOP.                           "ENDLOOP of Move recored into data i_tab
              LOOP AT i_calc INTO w_calc.
                w_data-matnr   = w_calc-matnr.
                w_data-mtart   = w_calc-mtart.
                w_data-matkl   = w_calc-matkl.
                w_data-maktx   = w_calc-maktx.
                v_temp = w_calc-menge_con_261 - w_calc-menge_con_262.
                w_data-menge_con    = v_temp.
                CLEAR v_temp.
                v_temp = w_calc-menge_con1_261 - w_calc-menge_con1_262.
                w_data-menge_con1   = v_temp.
                CLEAR v_temp.
                v_temp = w_calc-menge_ret_291 - w_calc-menge_ret_292.
                w_data-menge_ret    = v_temp.
                CLEAR v_temp.
                v_temp = w_calc-menge_ret1_291 - w_calc-menge_ret1_292.
                w_data-menge_ret1    = v_temp.
                CLEAR v_temp.
                v_temp = w_calc-menge_unit_301 - w_calc-menge_unit_302.
                w_data-menge_unit    = v_temp.
                CLEAR v_temp.
                v_temp = w_calc-menge_unit1_301 - w_calc-menge_unit1_302.
                w_data-menge_unit1   = v_temp.
                CLEAR v_temp.
                w_data-menge_sub    = w_calc-menge_sub.
                w_data-menge_sub1   = w_calc-menge_sub.
                v_temp = w_data-menge_con + w_data-menge_ret + w_data-menge_unit + w_data-menge_sub.
                w_data-menge_t      = v_temp.
                CLEAR v_temp.
                v_temp = w_data-menge_con1 + w_data-menge_ret1 + w_data-menge_unit1 + w_data-menge_sub1.
                w_data-menge_t1      = v_temp.
                CLEAR v_temp.
                APPEND w_data TO i_data.
              ENDLOOP.
          ENDIF.                                  "ENDIf i_mseg has records
    Display_ALV
    END-OF-SELECTION.
      DATA : DATE(85),
             DATE_LOW(10),
             DATE_HIGH(10),
             MSK TYPE STRING,
             DATE1(10),
             date2(10).
    WA_COMMENTRY-TYP = 'H'.
    WA_COMMENTRY-INFO = 'Material Consumption Report'.
    APPEND WA_COMMENTRY TO IT_COMMENTRY.
    CLEAR WA_COMMENTRY.
    CONCATENATE S_BUDAT-LOW6(2) '/' S_BUDAT-LOW4(2) '/' S_BUDAT-LOW+0(4) INTO DATE1.
    CONCATENATE S_BUDAT-high6(2) '/' S_BUDAT-high4(2) '/' S_BUDAT-high+0(4) INTO DATE2.
    CONCATENATE 'Material Consumption Report :' DATE1 'To' date2 INTO DATE SEPARATED BY SPACE.
    WA_COMMENTRY-TYP  = 'S'.
    WA_COMMENTRY-INFO = DATE.
    APPEND WA_COMMENTRY TO IT_COMMENTRY.
    CLEAR WA_COMMENTRY.
    *SORT I_DATA BY   MTART MATKL .
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
       I_CALLBACK_PROGRAM                = SY-REPID
       I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
       I_BACKGROUND_ID                   = 'ALV_BACKGROUNG'
      I_GRID_TITLE                      = 'STOCK LEDGER SUMMARY'
       IS_LAYOUT                         = IT_LAYOUT
       IT_FIELDCAT                       = IT_FIELD
      IT_SORT                           = IT_SORT
      I_SAVE                            = 'X'
       IT_EVENTS                         = IT_EVENT
      TABLES
        T_OUTTAB                          = I_DATA.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    FORM TOP .
    CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
      EXPORTING
        IT_LIST_COMMENTARY       = IT_COMMENTRY
      I_LOGO                   = 'INOXLOGO'
      I_END_OF_LIST_GRID       =
      I_ALV_FORM.
    REFRESH IT_COMMENTRY.
    ENDFORM.                    " TOP-OF-PAGE

    It is giving me error on sort statement 
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_CALLBACK_PROGRAM = SY-REPID
    I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
    I_BACKGROUND_ID = 'ALV_BACKGROUNG'
    I_GRID_TITLE = 'STOCK LEDGER SUMMARY'
    IS_LAYOUT = IT_LAYOUT
    IT_FIELDCAT = IT_FIELD
    IT_SORT = IT_SORT  <<<<<<<<<<<<<<<<<<<<<<<<<<<
    I_SAVE = 'X'
    IT_EVENTS = IT_EVENT
    TABLES
    T_OUTTAB = I_DATA.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

  • Error in consignment PO

    Hi gurus.
    when the user is trying to create a consignment PO, they get the following error message
    "pricing date category only allowed for items with invoice receipts.
    Message no: MEPO003
    Can anybody please help me with this
    Thanks
    Anusha

    we got this error, becuase somehow on the default setting button in the PO there is a field called price date,in this field somehow the user had a past date and whenever a new consignment inforecord got populated in the PO the system checkled the price validity against that date and then it threw the error. This only happened with that one vendor, other vendors we did not have the problem. once we got rid of the date in that field, the error also went away.
    Thanmks ofr your help
    Thanks
    Anusha

  • Error in consignment  settllement

    Hi all
    When i am trying to settle consignment PO using MRKO i am getting error message as: "First create the jurisdiction code at state level (3300000001)" . can anyone please help me regarding this error message?
    In PO I gave jurisdiction code as IL0000000 but the error message is showing jurisdiction code as 33000001.

    Hi,
    There is a link between the Tax Code (you have mentioned in the Consignment Info record) and the Jurisdiction code; in the area of FI/CO configurations.
    Please check these settings with the help of your FICO consultant and carry out the modifications required.
    Regards,
    Narayana.

  • PPM error with bucket consumption

    Hi,
    I am having a bit of trouble with the PPDS PPMs. Every time I regenerate the PPM for a specific product-location and run the PPM Check Plan, I get the error "You cannot use unit for bucket consumption of res..." and "Assign a value to at least one bucket consumption..." so what I am doing to temporarly solve it is to manually fill in the Bucket Consumption field from every resource of every operation contained in the PPM.
    But this is very time-consuming and I would like to find another way to do this. Is there a special configuration from the R/3 side?
    Thank you in advance,
    Fernando

    Hi Fernando,
    If you are creating a PPM directly in APO then you need to follow these steps and maintain the UoM for Variable bucket consumption.This is required to arrive at resource capacity consumption based on the order quantity of the planned/Production order for that specific product.
    But if you don't want to maintain this field manually everytime for all/new codes then you can have a setup where you define the PPM related data in R/3 i.e.BOM, Routing data and Production Version that,when CIFed to APO will automatically create the PPDS PPM with all consumption parameters you setup in routing. Then you can also automate the process to generate a SNP PPM with reference to this PPDS PPM.
    Hope this helps to clarify..
    Regards,
    Digambar

  • Error in WebServices Consumption - There are multiple root elements

    hi,
    I am working on consuming webservice which has a WSDL to get the RouteDetails with a structure like:
    <Source>
    <HouseNumber>1</HouseNumber>
    <Street>XYZ</Street>
    <City>Hyderabad</City>
    <Country>India</Country>
    <PostalCode>500018</PostalCode>
    </Source>
    <Destination>
    <HouseNumber>2</HouseNumber>
    <Street>X1Y1Z1</Street>
    <City>Bangalore</City>
    <Country>India</Country>
    <PostalCode>500067</PostalCode>
    </Destination>
    When I am calling the method RouteDetails of the proxy I created, I am getting the error 'There are multiple root elements in line 1 column 178 and the column is indicating <HouseNumber> in <Destination> node.
    Please let me know how to overcome this.
    Thanks for the help
    Githa

    Its now resolved. Thanks,
    Githa

  • Error while Sales posting in ISR , Inbound WPUUMS

    Hi,
      While posting the sales in ISR , through inbound IDOC im getting a error : Pipeline/consignment movement posted without value for a article.
    Although the Purchase info record is correctly maintained.
    Pls let me know what could be the possible reasons for this error & how to resolve it?
    Regards,
    Priyanka.

    The system has determined a consignment/pipeline price of 0.00.
    Possible reasons:
    The system could not find any valid condition for the posting date in the consignment/pipeline info record.
    A price of 0.00 was defined in the info record.
    check whether the conditions or the price has been defined correctly in the info record, if necessary. If there is a condition with a price other than zero, check whether the posting date of the movement lies within the condition's validity period.

  • Consignment settlement output title

    Hi,
    we print a KONS output (MR_PRINT form) for consignment settlements (triggered by trans. MRKO). On the paper ouput we need to slighly rephase the name of the document printed in French language. For example - from "Consignment invoice" to 'Consignment consumption settlement". Please advise where are stored texts for titles in different languages.
    Thanks a lot
    Kind regards
    Marcela

    Interesting - I've always known the t-code and have not tried to access through the SAP menu so can't tell you differently.
    In the end SAP standard is not designed to output consignment documents via MR90 so you will need to make adjustments to your user profiles and processes to use MR91.
    Regards,
    Sandra

  • PO Price and Consumption Price Difference

    I want to develop a report functionality that shows the price difference for consignment orders. For example, if I place a consignment PO for a material I want to know the price that a certain element (i.e. silver) of the material costed at the time of PO creation and the cost when the consignment consumption movement was performed. Is there any way to crete this link?

    Hi,
    due to the fact that the price is only in the info record you need to set up a report look at the condition of the info record depending on the validity period.
    on this page you'll find the required tables:
    http://www.erpgenie.com/sap/abap/tables_mm.htm
    regards, Paul.

  • Consignment PO - Info record not found

    Hi Experts,
    I have an urgent issue to resolve.
    A consignment PO was created on 30.01.2004. Still there are open items for that PO(as on date). Info records were removed from PO line items (automatically, the reason not known to anybody from business). The materials present in the PO have a source list and they are MRP relevant.
    Now being MRP relevant, these kind of POs are causing problem to the planning department.
    When i tried to delete/block the PO line items using ME22N, i get ERROR msg "Consignment info record does not exist". The consignment info records are there but with validity periods starting from 15.07.2004. I extended the validity from dates to 01.01.2004. When i returned to PO in ME22N, i am still having the problem with deleting the line items of PO.So i am not able to close these kind of POs which were created in the past but still open.
    Please anybody who has some idea about this kind of scenario, please let me know.
    Points will be rewarded to solution providers.
    Thanks & Regards,
    Pratap reddy M.

    Hi,
    Check the Validity period in the Consignment Info record, when is the to date.
    While closing the PO the info record should be active on the date, as the validity may be causing the problem to your PO,
    So extend the new validity period for that Consignment info record till the PO deletion.
    rgds
    Chidanand

Maybe you are looking for