Error while doing MIRO-Perform Plan price

Hi ,
We are on ECC 6 and we are getting error as "Perform Plan price for the material" while doing MIRO.
*Information:*
Price is different in Purchase requisition and PO&GR.MM03 is having proce control as "S" and the M Master is having both Moving price and standard price.
I tried changing the price through MR21 but still didn't worked.
Pl let me know if you need more info..
Thanks a lot in advance for early reply.
Govind

Hi,
Thanks for the reply. Since we are not using GR feature and we have not reversed the GR anytime.
Regards,
Lovkesh

Similar Messages

  • Error while doing MIRO-Overflow for arithmetical operation (type P) in prog

    Hi ,
    I am getting the error while doing the MIRO  as below-
    Runtime Errors         COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    Date and Time          20.05.2009 10:07:03
    Short text
         Overflow during the arithmetical operation (type P) in program "SAPLMRMC".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLMRMC" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
          caught in
         procedure "MRM_AMOUNT_QUANTITY_PROPOSE" "(FUNCTION)", nor was it propagated by
          a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
    Please let me know how can this be removed.

    Hi,
    There can be some problem with tolerances set in the customizing.
    In my case, I was getting this error because of delivery date variance. The difference between delivery date maintained in PO and invoice date was huge and hence the multiplication of price of PO and difference  of delivery date was huge and that was the reason for error.
    Similarly in your case also, there will be some tolerance limit problem.
    Please check your tolerance limits set in customizing.
    Regards,
    Mihir Popat

  • Account dertermination error while doing MIRO for third party PO

    Hello,
    This is regarding error message while doing MIRO (IR)
    There is already a PO in the system with item category S ( Third Party ) &
    Acc assignment object u2013 C (Sales order).
    For this PO , I could find 10 invoices already posted in the system.
    Between when these invoices were posted , there were some changes done to the PO.
    But even after those changes , many invoices were posted in the system,
    But now , when I try to post the invoice , I am getting the below error message.
    the error message is ** Account determination for entry SKPL WRX 0002 _ 1020 not possible** while posting.
    Message no. M8147
    Diagnosis
    The system did not find an account for this transaction. This means that the account determination for key SKPL WRX 0002 _ 1020 is not maintained in MM Customizing (Valuation). The key is made up of:
    u2022 Chart of account
    u2022 Transaction key (= Posting transaction)
    u2022 Valuation grouping code
    u2022 Account grouping code
    u2022 Valuation class
    System Response
    The system cannot update a G/L account for this transaction. You cannot post the transaction.
    Procedure
    Contact your system administrator.
    If you have the authorization, check the Account determination in Customizing for Valuation.
    Proceed
    Note
    The relevant posting transaction can be found in Table T030A.
    I have checked the entry in OMWD, where valuation grouping code is maintained against the valuation area & company code.
    PLEASE SUGGEST ME SOME SOLUTION.
    Thanks,
    Vinoth

    Hi Raman,
    Yes, still i am getting error.
    before when the invoice is posted , there is no error.
    there are some 10 invoices posted already , but there are some changes done in the PO , after that they could post two invoices but for the third invoice , i am getting this error.
    when the invoive is posted without error , these are the account movements that are hit
    Here
    441510 is a vendor account
    61799410 is a WBS element G/L account
    27411000 is a G/L for tax.
    What could have pulled out this WRX error (Account determination for entry SKPL WRX 0002 _1020 not possible ) for me????
    can u suggest me some solutions.
    Thanks,
    Vinoth

  • Error while doing miro of network purchase order ( no funds center entered/

    Hi,
    we are facing one problem while doing miro of network  service purchase order. System is giving message 'No funds center entered/derived in item 00030'.
    We have activated funds management in Jul'10. The said network service PO belong to previous year. Also we have changed
    commitment item of GL account related to concerned service order in Jul'10 & posted GRN one in apr'10 & one aug'10.
    System is not allowing to cancel the service entry sheet.
    Can anybody help on this.
    regards
    abhishek

    we had activated the trace facility for FMDEIRIVE & found that all FC/Commitment item derived correctly. But while posting the document it is throwing an error.
    Regards
    Abhishek

  • Error while doing MIRO

    Hello Everybody,
    I am trying to do MIRO for a Purchase Order.
    But I see the following error while doing that -
    "G/L account  is not defined in chart of accounts 1000".
    Can someone tell me whats going wrong and where do I have to check to set the following conditions right for a MIRO posting to be done?
    Please help. All the help is appreciated.
    Thanks,
    Sneha.

    Hello Sneha singh
    In addition to Mr.srinath's suggestions please check whether you have maintained Reconsallation account for your vendor in the Vendor masterdata in XK01 in the company code level
    have you maintained properly the OBYC settings (take the help of your MM or FI consultant for this) and also check in OMWD whether the valuation grouping 0001 code is assigned to your plant
    Mostly along with Mr.Srinath's suggestions  Reconsallation account checkings in the Vendor masterdata in XK01 should solve your issue
    Regards
    Raja

  • ABAP RUNTIME ERROR WHILE DOING MIRO

    Runtime Errors                                                       MESSAGE_TYPE_X                              
    Date and Time                                                       23.02.2011                    17:07:24          
    Short dump has not been completely stored (too big)                                                                                     
         Short text                                                                                
                   The current application triggered a termination with a short dump.                                                                      
         What happened?                                                                                
                   The current application program detected a situation which really                                                                      
                   should not occur. Therefore, a termination with a short dump was                                                                      
                   triggered on purpose by the key word MESSAGE (type X).                                                                      
         What can you do?                                                                                
                   Note down which actions and inputs caused the error.                                                                      
                   To process the problem further, contact you SAP system                                                                      
                   administrator.                                                                      
                   Using Transaction ST22 for ABAP Dump Analysis, you can look                                                                      
                   at and manage termination messages, and you can also                                                                      
                   keep them for a long time.                                                                      
         Error analysis                                                                                
                   Short text of error message:                                                                      
                   Error creating the document in Profitability Analysis                                                                      
                   Long text of error message:                                                                      
                    Diagnosis                                                                      
                        An error was found while the system was processing the FI/CO                                                                      
                        document in Profitability Analysis.                                                                      
                    System Response                                                                      
                        The document cannot be processed any further.                                                                      
                    Procedure                                                                      
                        Contact your system administrator.                                                                      
                   Technical information about the message:                                                                      
                   Message class....... "KE"                                                                      
                   Number.............. 476                                                                      
                   Variable 1.......... " "                                                                      
                   Variable 2.......... " "                                                                      
                   Variable 3.......... " "                                                                      
                   Variable 4.......... " "                                                                      
         How to correct the error                                                                                
                   Probably the only way to eliminate the error is to correct the program.                                                                      
                   If the error occures in a non-modified SAP program, you may be able to                                                                      
                   find an interim solution in an SAP Note.                                                                      
                   If you have access to SAP Notes, carry out a search with the following                                                                      
                   keywords:                                                                      
                   MESSAGE_TYPE_X " "                                                                      
                   RK2RF001 or "RKEVRK2R_FIX"                                                                      
                   MOVE_VALUE_FIELDS_FI                                                                      
                   If you cannot solve the problem yourself and want to send an error                                                                      
                   notification to SAP, include the following information:                                                                      
                   1. The description of the current problem (short dump)                                                                      
                      To save the description, choose "System->List->Save->Local File                                                                      
                   (Unconverted)".                                                                      
                   2. Corresponding system log                                                                      
                      Display the system log by calling transaction SM21.                                                                      
                      Restrict the time interval to 10 minutes before and five minutes                                                                      
                   after the short dump. Then choose "System->List->Save->Local File                                                                      
                   (Unconverted)".                                                                      
                   3. If the problem occurs in a problem of your own or a modified SAP                                                                      
                   program: The source code of the program                                                                      
                      In the editor, choose "Utilities->More                                                                      
                   Utilities->Upload/Download->Download".                                                                      
                   4. Details about the conditions under which the error occurred or which                                                                      
                   actions and input led to the error.                                                                               
    System environment                                                                                
                   SAP-Release 701                                                                      
                   Application server... "FPELECCPRD"                                                                      
                   Network address...... "192.168.0.24"                                                                      
                   Operating system..... "Windows NT"                                                                      
                   Release.............. "6.0"                                                                      
                   Hardware type........ "16x AMD64 Level"                                                                      
                   Character length.... 16 Bits                                                                      
                   Pointer length....... 64 Bits                                                                      
                   Work process number.. 1                                                                      
                   Shortdump setting.... "full"                                                                      
                   Database server... "FPELECCPRD\FTP"                                                                      
                   Database type..... "MSSQL"                                                                      
                   Database name..... "FTP"                                                                      
                   Database user ID.. "ftp"                                                                      
                   Terminal.......... "PUNE143"                                                                      
                   Char.set.... "C"                                                                      
                   SAP kernel....... 701                                                                      
                   created (date)... "Feb 24 2009 23:27:20"                                                                      
                   create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"                                                                      
                   Database version. "SQL_Server_8.00 "                                                                      
                   Patch level. 32                                                                      
                   Patch text.. " "                                                                      
                   Database............. "MSSQL 9.00.2047 or higher"                                                                      
                   SAP database version. 701                                                                      
                   Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                                                                      
                    NT 6.0"                                                                      
                   Memory consumption                                                                      
                   Roll.... 16192                                                                      
                   EM...... 29328880                                                                      
                   Heap.... 0                                                                      
                   Page.... 221184                                                                      
                   MM Used. 20281392                                                                      
                   MM Free. 664288                                                                      
         User and Transaction                                                                                
                   Client.............. 900                                                                      
                   User................ "FABUPLO"                                                                      
                   Language key........ "E"                                                                      
                   Transaction......... "MIRO "                                                                      
                   Transactions ID..... "1C413FE0E2E7F1C88D54E61F1346F073"                                                                      
                   Program............. "RK2RF001"                                                                      
                   Screen.............. "SAPLMR1M 6000"                                                                      
                   Screen line......... 34                                                                      
         Information on where terminated                                                                                
                   Termination occurred in the ABAP program "RK2RF001" - in                                                                      
                    "MOVE_VALUE_FIELDS_FI".                                                                      
                   The main program was "SAPLMR1M ".                                                                      
                   In the source code you have the termination point in line 2749                                                                      
                   of the (Include) program "RKEVRK2R_FIX".

    Hi
    Normally what we understand is we should not have a COPA doc in case of MIRO unless and untill one has got the Purchase Price Variance in the entry  and for the same the OKB9 setting has been made while the GL account either doesnot have cost element for the period or the PA structure is not complete.
    The above can be the probable reason for the dump. I hope if you try to investigate the problem on the above line you will find out the solution to the problem
    regards
    Debashis

  • Error while doing "Visulaize Plan"

    Hi,
    Before i did Visualize plan many times without any problem.Now I am getting error while doing so.
    I was able to run "Explain Plan" successfully.
    I am on HANA revision 60.
    I saved above error log and the log information is given below:
    I can identify invalid XML tag <TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved> but how to fix this issue?
    I gone through various blogs related to Visulaization Plan but not found related to this issue.
    <Plan xmlns="http://www.sap.com/ndb/planviz" ID="ID_0" Type="Estimated">
    <SQL><![CDATA[SELECT KOKRS, BELNR, PERIO, SUM(MEGBTR)
    FROM "_SYS_BIC"."raj/AN_VIZ"
    GROUP BY KOKRS, BELNR, PERIO]]></SQL>
    <CompileTime>
      <Start Unit="us">1401281467643661</Start>
      <End Unit="us">1401281467658329</End>
    </CompileTime>
    <RootRelation ID="ID_0" TypeName="PROJECT" Status="Finished">
      <Name>Project</Name>
      <ExecutionType>Row Search</ExecutionType>
      <Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)]]></Summary>
      <Location>hanasp7:30003</Location>
      <EstimatedCost>
       <Exclusive Unit="us">2.12902e+06</Exclusive>
       <Inclusive Unit="us">2.64021e+06</Inclusive>
      </EstimatedCost>
      <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
      <Details><![CDATA[{"Projected Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)","Project column0":"NString(4, 0)  __trex_field_NVarchar3__() ....... [3]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [0]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [1]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 0 ....... [2]:LOAD:<4/5 (4B)>:","Project column1":"NString(10, 0)  __trex_field_NVarchar3__() ....... [8]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [5]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [6]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 1 ....... [7]:LOAD:<4/5 (4B)>:","Project column2":"NString(3, 0)  __trex_field_NVarchar3__() ....... [13]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [10]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [11]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 2 ....... [12]:LOAD:<4/5 (4B)>:","Project column3":"Decimal(18, 3)  __typecast__() ....... [23]:076:<10/12 (16B)>:
      /1/ Fixed16(18, 3)  __trex_field_Fixed16__() ....... [19]:043:<6/8 (16B)>: 
         /1/ void*  \"__rids__\" ....... [15]:NOP:<0/1 (8B)>:
         /2/ int32_t(10, 0) const := 0 ....... [16]:LOAD:<3/4 (4B)>:
         /3/ int32_t(10, 0) const := 3 ....... [17]:LOAD:<4/5 (4B)>:
         /4/ int32_t(10, 0) const := 3 ....... [18]:LOAD:<5/6 (4B)>: 
      /2/ int32_t(10, 0) const := 18 ....... [21]:LOAD:<8/9 (4B)>:
      /3/ int32_t(10, 0) const := 3 ....... [22]:LOAD:<9/10 (4B)>:"}]]></Details>
      <Child ID="ID_8" >
      </Child>
    </RootRelation>
    <Relation ID="ID_8" TypeName="TREX_SEARCH" Status="Finished">
      <Name>Column Search</Name>
      <ExecutionType>Column Search</ExecutionType>
      <Summary><![CDATA[Aggregation on a single table]]></Summary>
      <Location>hanasp7:30003</Location>
      <EstimatedCost>
       <Exclusive Unit="us">511194</Exclusive>
       <Inclusive Unit="us">511194</Inclusive>
      </EstimatedCost>
      <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
      <TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved>
      <LogicalPlan ID="ID_11" Type="Estimated">
       <RootRelation ID="ID_11" TypeName="PROJECT" Status="Finished">
        <Name>Project</Name>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
        <Child ID="ID_12" >
        </Child>
       </RootRelation>
       <Relation ID="ID_12" TypeName="GROUP_BY" Status="Finished">
        <Name>Aggregation</Name>
        <Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO\nSUM(raj/AN_VIZ.MEGBTR)]]></Summary>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
        <Details><![CDATA[{"Grouping Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO","Aggregation Cols":"SUM(raj/AN_VIZ.MEGBTR)"}]]></Details>
        <Child ID="ID_13" >
        </Child>
       </Relation>
       <Relation ID="ID_13" TypeName="TABLE" Status="Finished">
        <Name>Column View</Name>
        <Schema><![CDATA[_SYS_BIC]]></Schema>
        <ObjectName><![CDATA[raj/AN_VIZ]]></ObjectName>
        <Location>hanasp7:30003</Location>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>682404</EstimatedOutputCardinality>
       </Relation>
      </LogicalPlan>
    </Relation>
    </Plan>
    Regards
    Raj

    Hi,
    To solve this you must update your studio. In lower studio versions (PlanViz) does not allow "unknown" XML tags sent by higher version servers. A fix for this issue was made so that PlanViz parser can simply skip unknown tags.
    Please go to version 74, if possible.
    Regards,
    Michael

  • While doing MIRO, i am getting error:-Tax code V0 country IN does not exist

    hi frds,
    while doing miro. i am getting this error:-
    pls correct me
    Tax code V0 country IN does not exist in procedure TAXINN
    Message no. FF713
    Diagnosis
    You entered a tax code which is not defined for the country of the company code to be posted to in the tax calculation procedure.
    System Response
    Procedure
    Check and, if necessary, correct the entry.
    Procedure for System Administration
    If it is not an input error, check and possibly change the system settings.
    To do this, choose Maintain entries (F5).
    Check whether the company code is assigned to the correct country and whether the correct tax calculation procedure has been entered for the company code country.
    Create a new tax code if necessary.
    Caution:
    Since it is possible that the tables in question are being updated at a different time on another computer, it can take a certain amount of time for the tax code to be on all local machines in client server architectures after saving the new code.
    regards,
    william

    hi
    go to ftxp choose tax code v0
    here in first input field give 00
    then select that field and click on gl acct tab
    here mention a gl or go to ob40 and mention gl for the acct key of that field
    try finding
    Tax code country IN does not exist in procedure TAXINN
    on SDN u will get many threads
    Tax code XX country IN does not exist in procedure TAXINN (MIRO Error)
    conclusion is u must get acct for at least one condition in the tax code
    regards
    kunal

  • Getting error while doing sales planning in COPA

    Hello Friends,
    While i m doing the sales planning in COPA via KEPM, I am getting the dump for ABAP Feilds regarding Volume and Weight.
    Error has been stated below.
    Runtime Errors CONVT_OVERFLOW
    Except. CX_SY_CONVERSION_OVERFLOW
    Date and Time 19.03.2008 16:16:40
    Short dump has not been completely stored (too big)
    Short Text
    Overflow when converting from "1.12036e+12"
    What Happned?
    Error in the ABAP Application Program
    The current ABAP program "SAPLKEAB" had to be terminated because it has come across a statement that unfortunately cannot be executed.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not caught in
    procedure "GET_WEIGHT_AND_VOLUME" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
    The reason for the exception is:
    When attempting to convert the value "1.12036e+12", an overflow occurred.
    As i m getting the ABAP Error while making the sales planning for Finished Product

    My guess - because I don't know your system - is the system is looking for one particular type of value, but is being fed a different one. While trying to convert, the value foes into data overflow.
    Check:
    1. If the planning is in Alternative Units of measure and this alternative is well defined in the material master.
    2. If a standard conversion routine has been assigned to any of the values and the conversion routine is not consistent with the data type / data element.
    3. Check your upload file / data. Is there a column defined there that should contain data of a specific type (decimals, or number formats, etc.) but is not the case.
    4. If all else fails, you need an ABAPer to decode the error for you.
    Cheers.

  • MIR4- Perform Planned Price change

    Dear All,
             I have an issue during mir4.
            When doing simulate and posting for a invoice in mir4, the system shows the error,
             "Perform planned price change for the material <matnr> <plant>"
               Message No.M8394
    Could anybody help me to resolve this issue ?
    Thanks & Regards,
    S Sridhar

    Dear Meruta,
                 Thank you for your quick reply.
    Could u please guide me how to check the points as you said (As I 'm new to this module ) ?
    Regards,
    S Sridhar

  • Error while creating Rough cut planning profile

    Facing the following error while creating rough cut planning profile (mc35) in SOP for product group. "Work center x plant y does not exist for task list type 3". pls advise- do i need to create tsk list for product group? pls advise with tcode to be used.

    pls check the (task list ) usage you have maintained in the Work center.
    In OP45 , pls ensure that for the usage ,
    task list type 3 (Rough cut planning profile) is included.
    If it is not included there , pls include the TL type 3 for your usage and now the prob will get solved.
    Regards.,
    Sheik

  • Error while doing J1IH (Excise JV) - TR6 Challan posting

    I am getting the following error while doing,  J1IH (Excise JV) - TR6 Challan posting
    Please assist....
    Short text
        The COMMIT WORK processing must not be interrupted.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLFACS" had to be terminated because it h
        come across a statement that unfortunately cannot be executed.
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    Error analysis
        During the COMMIT WORK statement, the following are executed:
        - the routines registered with the statement PERFORM .. ON COMMIT,
        - the registered methods for the events of the object services
          and
        - possibly the local update (SET UPDATE TASK LOCAL).
        An exception was raised and caught. The normal sequence of the routines
        was interrupted by this resulting in the program being continued before
        the call of COMMIT WORK. As this can lead to inconsistencies, the
        processing cannot be continued in the normal way.

    Thanks Milind...
    I am also getting the following error:
    Balance in transaction currency
        Message no. F5702
    Diagnosis
        A balance has occurred in transaction currency 'INR' with the following
        details:
        Exchange rate '00', amount '       500,000.00' and currency key 'INR'.
        The data in the transaction currency were transferred from the calling
        application.
    System Response
        Your data cannot be processed in FI.
    Procedure
      The error is probably in the calling application.
    Please assist

  • I am getting error while doing MFBF for semifinisg good

    Hi,
    i am getting error while doing MFBF for semifinisg good
    Existing standard cost estimate cannot be used
    Message no. RM175
    Diagnosis
    This error appears under the following circumstances:
    The existing standard cost estimate cannot be used for backflushing activities as the repetitive manufacturing profile was not maintained correctly when the standard cost estimate was carried out.
    The standard cost estimate must come from product costing. Other cost estimates (such as base object controlling) are not possible.
    Procedure
    The repetitive manufacturing profile assigned to the material at the time of the planned cost estimate must be a profile for repetitive manufacturing with product cost collector.
    Use product costing to create the standard cost estimate.

    I had already check REM profile repetitive mfg profile final backflush w. activities.
    this particular material is semifinish material attached in BOM of finish material.
    backflush of finish good is possible but now new requirement is to do production booking for the semifinish material.
    i had assign production version , done routing and maintain REM profile,
    created material cost with quantity structure ck11n then run the costing in ck40n.
    still getting the error what else is to done to able to book this thru MFBF.

  • Error while commit is performing

    Hi
    I am using jdev11.1.1.5.0
    I am getting following error while commit is performing...
    java.sql.SQLException: ORA-01086: savepoint 'BO_SP' never established
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1079)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
         at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3937)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1535)
         at oracle.jbo.server.OracleSQLBuilderImpl.rollbackToSavepoint(OracleSQLBuilderImpl.java:1582)
         at oracle.jbo.server.DBTransactionImpl.rollbackToSavepoint(DBTransactionImpl.java:3133)
         at oracle.jbo.server.DBTransactionImpl.restoreTmpPostState(DBTransactionImpl.java:1865)
         at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:3109)
         at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:2093)
         at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2374)
         at oracle.adf.model.bc4j.DCJboDataControl.commitTransaction(DCJboDataControl.java:1608)
         at oracle.adf.model.binding.DCDataControl.callCommitTransaction(DCDataControl.java:1416)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1437)
         at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2149)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:740)
         at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:402)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:210)
         at com.jagran.in.stmjobassignview.MBean.StmJobAssignMBean.confirmStm(StmJobAssignMBean.java:263)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.el.parser.AstValue.invoke(Unknown Source)
         at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
         at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256)
         at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
         at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:902)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:313)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:186)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    <Utils> <buildFacesMessage> ADF: Adding the following JSF error message: ORA-01086: savepoint 'BO_SP' never established
    java.sql.SQLException: ORA-01086: savepoint 'BO_SP' never established
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1079)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
         at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3937)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1535)
         at oracle.jbo.server.OracleSQLBuilderImpl.rollbackToSavepoint(OracleSQLBuilderImpl.java:1582)
         at oracle.jbo.server.DBTransactionImpl.rollbackToSavepoint(DBTransactionImpl.java:3133)
         at oracle.jbo.server.DBTransactionImpl.restoreTmpPostState(DBTransactionImpl.java:1865)
         at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:3109)
         at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:2093)
         at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2374)
         at oracle.adf.model.bc4j.DCJboDataControl.commitTransaction(DCJboDataControl.java:1608)
         at oracle.adf.model.binding.DCDataControl.callCommitTransaction(DCDataControl.java:1416)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1437)
         at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2149)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:740)
         at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:402)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:210)
         at com.jagran.in.stmjobassignview.MBean.StmJobAssignMBean.confirmStm(StmJobAssignMBean.java:263)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.el.parser.AstValue.invoke(Unknown Source)
         at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
         at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
         at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256)
         at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
         at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:902)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:313)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:186)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    There is any help regarding this.

    ORA-01086: savepoint 'BO_SP' never establishedpoints to a missing or invalid ps_txn table where such save points are normally stored. Check your configuration (DB which you connect to) if you find the ps_txn table in there and that the user you use has the right to write into this table.
    If you don't see the table then you have to create it (scripts for this are delivered together with jdev). Or ask the db admin to grants create table rights to your user.
    Timo

  • Termination error while doing me31k

    HI Experts,
    This is the sincere apology for the previous thread which was in capital letter subject" termination error while doing me31k 
    Posted: Mar 6, 2012 2:56 AM          
    HI while performing transaction ME31K I'm getting follow error
    Runtime error: DYNPRO_NOT_FOUND
    What Happened?
    Error in the ABAP application Program
    The current ABAp program "SAPLXM06" had to be terminated because it has come across a statement that unfortunately canont be executed.
    Error Analysis
    The system attempted to use dynpro 0201 in program "SAPLXM06".
    This dynpro does not exist.
    Trigger Location of Run TIme Error
    Program: SAPLXM06
    Include: MM06E00C_CUSTSCR1_HEAD_SET_DAT
    ROW: 10
    There is a Edit button, that allows you to change the subject
    Edited by: Jürgen L. on Mar 6, 2012 8:41 AM

    Dear MM user,
    Follow the documentation of this enhancement (see transaction SMOD):
    Within the documentation of enhancement MM06E005, via TA SMOD, it specifically states that if you use the enhancement you must generate six listed dynpros (screens), even if you are not using them.
    So you may goto transaction CMOD and enhance the same.
    For example, the dynpro area should be like the following:
    Calling screen No. Area Called screen No. ShortTxt
    SAPMM06E 0101 CUSTSCR1 SAPLXM06 0101 Subscreen: PO header
    SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111 Subscreen: PO item
    SAPMM06E 0201 CUSTSCR1 SAPLXM06 0201 Subscreen: agreement
    Regards,
    ian Wong Loke Foong

Maybe you are looking for