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

Similar Messages

  • 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-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

  • 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

  • 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

  • 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

  • Error when doing MIRO

    Hi,
    We get the error as below while doing MIRO.
    'Customization for GM1 j_1iindcus missing in table'
    How do we proceed?
    Regards

    hI,
    You maintain the customization data in following path as metioned below
    SPRO>Logistics General>Tax On Goods Movements>India>Basic Settings>Maintain Company Code settings
    1.Company Code - your company code
    2.Cenvat Document Type - ED
    3.Utl FI Document Type - ED
    4.Select check box Debit account override
    5.Select Automatic Balance adjustment indicator check box
    6.Select Immediate credit on capital goods check box
    7.Select First Month as April
    8.Excise selection days 30
    9.No of Excise Invoices 10
    10.Excise Invoice Selection procedure FICO or LIFO as per client requirement
    11.Select Rounding duty on procurement
    12.Select Rounding duty on removal
    13.Excise rate for CVD - M
    14.Exchange rate type for exports - M
    15.CVD Account - Assign your CVD account
    this will solve your problem.
    bye
    Sridhar Thota
    We get the error as below while doing MIRO.
    'Customization for GM1 j_1iindcus missing in table'
    How do we proceed?

  • Error while doing ABGL Asset Credit Memo

    Hi Friends,
    I am getting the below error while doing Asset Credit Memo in ABGL. Please help me in fix this issue.
    Balance for transaction type group 10 negative for the area 01
    Note:In Asset Explorer Fiscal year start Asset value is 98,425.45 and Change is 4768.19. So total Asset value as of now is 1,03,193.64.
    Now we are trying to do ABGL with 12,790.23 value (Transaction type is 105). System is giving the above highlighted error.
    If we give the amount 4768.19 in ABGL transaction, system is not giving any error. If we give more that that system is giving error.
    Why system is giving error even the asset has balance of 1,03,193.64? Please help me on this..
    Thanks
    Sunil

    Hi,
    If the asset has been capitalized during earlier years, use ABGF to post credit memo.  ABGL is meant for assets capitalized during the year.
    Best Regards,
    Madhu

  • 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

  • Error while doing EHP4 upgrade in downtime phase

    HI .
    Iam facing the below error while doing the EHP4 upgrade , in downtime phase.
    Checks after phase MAIN_SWITCH/STARTSAP_TRANS were negative!
    Last error code set: RFC call to subst_get_uvers failed with key RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 >
    Connect to SAP gateway failed Connect_PM GWHOST=Hydhtc4526D, GWSERV=sapgw04, SYSNR=04  LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.136.162.30:3304' not reached TIME Mon Jun 06 18:17:46 2011 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.136.162.30:3304 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER System start failed
    Please help me in resolving this error.
    Sanketh.

    Hi,
    Upgrade tool is trying to start the system but system is not coming up. Try to start system manually and see if system comes up or not. If not then check logs in work directory for why system is not coming up.
    Thanks
    Sunny

  • Error while doing  GR for scheduling aggrement

    Dear Experts,
    We are facing error while doing GR for scheduling aggrement.
    we have done the following steps.
    1) Scheduling aggreement in ME31L
    2) Released in ME35L
    3) Mainatined Sch.Agmt Schdule in ME38 for todays and date 200 qty and other line is 800 qty.
    When we are trying to do GR in MIGO system is giving the following message.
    Document 5500000152 does not contain any selectable items
    can I know what I have missed in the above steps.
    Please guide me to resolve this.
    Regards,
    Prasad

    Hi,
    Please check Please check if Gr is already done against this document.  Also please check whether you have attached SA in the source list with line items.
    T-code:ME01
    Enter Mat.code & Plant.
    In the next screen pl.do the following:
    Valid from - commencement date of the SA
    Valid to - End date of the SA
    Vendor - Vendor on whom the SA is released
    POrg - Your purchase organisation
    PPL - Leave it blank(This is only for interplant)
    OUn - Ordering unit
    Agreement - SA number
    Item - 1
    I hope this will resolve your issue. Thanking you

  • Error  While doing ABT1N transaction

    Hi,
    I am facing the below error while doing ABT1N in Asset Accounting.Please help me in fixing this Issue.
    Error Message -No depreciation area for receiving the revenue
    Message no.AAPO149
    Diagnosis
    You tried to post a retirement on asset 1000 100007-0.You entered transaction type 300,in which the retirement with revenue indicator is not set
    You tried to transfer asset 1000 100007-0.According to transfer variant 0001,none of the areas on the asset uses a transaction type for retirement with revenue
    In  both of these cases, you are not allowed to enter revenue or make specifications for the determination of revenue.
    Proceedure
    Check the transfer variant  and check your entry
    please do the needful
    Thanks
    Supriya

    Hello,
    You will have a check box for the same.
    Double click on transaction type, you will see the check box for revenue.
    Otherwise, tomorrow I will get back to you once I am in front of the system.
    Regards,
    Ravi
    Edited by: Ravi Sankar Venna on May 5, 2009 7:53 PM

  • Error while doing F-90 Asset Acquisation

    Hi,
    I am getting the below error while doing F-90 Asset Acquisation scenario. Please help me to fix this issue.
    Tax code V1 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.
    Thanks
    KB

    Hi,
    you need to maintain Tax Code A0 & V0 in t.code OBCL t.code.
    and also ensure to check whether you have created tax code V1 or not in FTXP t.code. If not, create V1 tax code and assign GL on that in the right Transaction event keys in OB40.
    Try.... if not working let me know....
    Regards,
    MOhan.

  • Error while doing AIAB Settlement

    Hi I am facing the below error while doing AIAB during AUC settlement. Please do the needful.
    Data for determination of capitalization not managed in area 01
    Message no. AW507
    Diagnosis
    You have chosen a depreciation area, which does not carry the depreciation data from table COEPBR.
    Procedure
    Choose a different depreciation area.
    Thanks
    KC

    Hi,
    This message could be helpful:
    Error AW507
    Please check the field T082AVIEWB-AUTHORITY. If it is not on 2 this is the reason.
    In this case, you can change the value in T093-VIEW1 using the coding as per SAP note 29706 which you have already discovered. There will be no risk involved in changing this value.
    regards Bernhard

Maybe you are looking for

  • Droid bionic's touch screen doesn't work properly with firefox have to use opera

    once on Firefox, I have to tap on the screen links many times until it recognizes the touch. the screen will zoom in and out only. scrolling is slow but it functions. it's the touch that doesn't work

  • How do I compress my itunes MP3s to 192kb

    How do I compress my whole itunes library MP3s to 192kb? I want to make some space on my HD

  • WLS 6.1 SP5 changed behaviour with OracleThinClob?

    Hi, while trying to update a Weblogic 6.1 server installation to SP5, I noticed the following change in behaviour: Apparently, SP5 will return an instance of class oracle.sql.CLOB for Clob column value from Resultset, whereas previous versions return

  • Mail loosing settings

    g'day all, Everytime I reboot my computer and restart mail, it looses my mail settings. I'm using the webmail patch, and it seems to work fine except for this error. All the mail is still being stored on the computer, but it always gets me to set it

  • [Solved] Warcraft screen freeze

    I few weeks ago before I moved to Arch I had sidux on my computer. I had Wine running Warcraft III fine for months. So then I also wanted to play Starcraft (which doesn't work so well on Wine) so I installed virtualbox with Windows XP. I forget how e