Error when release to accounting document

Hi there:
After finish creating the invoice via vf01 based on the outbound delivery and I am abou to release to accounting document,I encountered below error that I have never seen before:
Document type RX not defined,and when I click release to accounting document again,it popped up below error message:
Requested function FKFR is not available here.
What do above two error message mean? Help.

Hi,
While defining the billing document type for ex., F2 in VOFA for the field Document Type = RV-(Billing doc transfer).
Kindly check for your billing document type what is maintained.If it is maintained as RX then check it in OMBA whether it is existing there or not.
Regards,
Gopal.

Similar Messages

  • Error when creating billing / accounting document with VF01

    Hi All,
    When I use VF01 to create an invoice with reference to a LF D/N, I got the following error after saving.
    "An exchange rate type is not defined for country CN
    Message no. FF 802". And billing document is created but with no accounting document.
    I checked the exchange rate type is defined. but I can not find the place where I can assign to the specific country.
    Best Regards
    Jean

    Thanks for your help.
    Hi Dave,
    I checked in S_BCE_68000174, it has been already assigned.
    Hi Ferry,
    In FTXP, the tax code has been maintained.
    And you are right, when I maintain the field KURST in table T005, it is ok. But I am confused in 4.6C, the field KURST can be maintained by T-code OY01, but in 470, exchange rate type cannot be found in OY01. Where can I set in 470?  And why in 470, even field KURST is empty in table T005, but there is no such error when creating billing document?
    Many Thanks
    Jean

  • Error RW 022 when releasing a Billing Document to Accounting

    Hi,
    The issue is about releasing a Customer Invoice to Accouting. The error belongs to the RW class, its number is 022 and its message is "the balance in transaction currency must be zero for each logical operation before being transfered to RW interface. A balance of xEURO has been determined for the logical operation."
    After some investigations, the balance amount which the error message is talking about does correspond to the Logistic Cost of the invoice. Moreover, this cost is not included in the corresponding sales order. Here are the propositions to understand the issue:
    - it comes from the dis-match between the sales document amount and the invoice amount. As long as their amounts are different, the system won't let it go.
    - the account determination for logistic costs is not properly set up. The system does not know "what to do" with these Logistic Costs when releasing to accounting. In this case, the gap between the sales document amount and the invoice amount is not a problem.
    Are those two hypothesis worth investigating and, if yes, what would be the steps to go deeper? Do you have any other ideas?
    Many thanks for your support,
    Stanislas

    Hi,
    I do not think we have an account determination error here. This message is coming from far behind the point when the account determination was carried out. You can check this easily in VF03, enter invoice number, then Environment -> Account determination analysis --> Revenue accounts. If there would be an account determination error, you would not get an RW.... message, because the accounting interface (RW) would not be called up at all.
    I think the GL accounts are well known here (they may be incorrect from a business point of view, but at last technically, they are set up), the only problem is that you have a balance in transaction currency.
    Hope that helps, points welcome
    Csaba

  • Error when releasing billing to Accounting

    Hi All,
    I get the following error when releasing the billing to accounting in T-code VFX3....
    Tax code   in procedure TAXSL is invalid
    Message no. FICORE704
    Diagnosis
    The tax code entered is not defined in the country for this company code.
    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).
    1. Check whether the required tax determination procedure is assigned to the relevant country. the Procedure field is in the detail screen.
    2. Create a new tax code if required
    Pls note that in the error message it does not mention a particular tax code which is invalid, it jus shows tax code   in procedure TAXSL is invalid.
    I have done the following customization both in FI and SD.
    I have maintained condition record MWST both in FI and SD. Maintained all necessary tax codes in FTXP.
    Note that in the billing, we enter the condition type MWST in the Header Level and enter the relevant percentage manually. According to my understanding since the condition is maintained at header level there is no need of maintaining condition records through T-Code VK11.Therefore the tax code is not picked from the condition record as its not maintained in the item level.
    Pls advice me on how to overcome this error ASAP since its critical.
    Thanks in Advance,
    Maleeq

    Hi,
    Yes I have maintained tax codes in FTXP. but the error message shows that "tax code __ is missing in tax procedure TAXSL". To my knowledge it is not possible to create a tax code "blank"!!!!
    I have not maintained condition records in VK11 as we maintain the MWST condition in the Header level. Condition records are picked only from ITEM level and NOT from HEADER level.
    Maleeq

  • Error while releasing the Billing document

    Hi Everyone,
      Encountering an error with the description 'Balance in Transaction currency' while trying to release the Billing document from VF02 transaction, still didnt come across the right oss note that can remove this error, can any one give me a clue on this,
    Rgds,

    hi,
    We are facing similar problem, when releasing the billing document to accounting.
    Have you been able to find the solution to this problem. If so, kindly suggest the answer
    Thanks
    Dinesh

  • Not able to release to accounting Document

    Hi Friend
    Billing document created, but subsequently not able to release to accounting document.
    Error messgae: Acct determin error  (message# VF051)
    Please advise.
    Rgds
    RG

    Dear R G,
    Check the v/08 settings. The relevant conditions on the billing documents should be linked to account keys which are mapped in vkoa. It is not only revenue keys that may be affected. Check whether there are other conditions (like rebate, discounts, etc) on your billing documnet, and make sure that they are mapped to the appropriate accounts.
    You may want to have a look at the wiki posting "How to trace Account Determination for SD billing " This may help you while you are at VKOA with reference to your billing document to trace what is missing. Check at https://www.sdn.sap.com/irj/sdn/wiki today's recent posting.
    Beside that
    Plz check 2 things.
    1. Check a/c determination in VKOA
    2. SPRO - SD - Basic functions - A/c Assgmnt/Costing - Revenue a/c determination - Define and assign a/c determination procedure - Define a/c determination
    In KOFI00, See in condition, assign 3 for KOFI and KOFK
    rgds,
    nanthakumar

  • Error when releasing a transport

    Hello experts,
    I am getting an error when releasing a transport. The error message is telling me that
    Object DTPA DTP_009C8T81IIB6H4UFC7FQUVRFL was set to 'inactive'   
    The detailed error message isnt very helpful. The performance assistant gives the error message RSO 407.
    I found another thread,  scn.sap.com/thread/3428031
    The answer in this thread appears to be very close to a solution for me, I just need a little more information I think. As it says, I have looked in the table RSTRAN for the transformation that this DTP processes. There are three rows, with a different OBJVERS. A and M are both set to ACT, but OBJVERS = D is set to OBJSTAT = INA.
    I suspect that this is the problem with the releasing of my transport. Do you agree?
    If so, how do I go about getting this activated?
    Many thanks.

    Hi Simon,
    The D version will be always inactive as it indicate SAP Delivered version of the transformation.
    I will suggest just have a look at any existing transformation, you will find same status i.e D version INA also check last change it will be SAP also under content column you will find info for D version.
    I still say, just go ahead and release your transport by ignoring the message, it should work. You are all set to move your transport.
    Rest upto you.
    I have tried releasing transport by ignoring messages many times.....and worked all time
    Thank-You.
    Regards,
    VB

  • Error While Releasing the Billing Document Msg No. KE/AD 243

    I am getting error while releasing the billing document
    Error No KE/AD 243
    This error comes in particular billing document only others are posted correctly.
    Rgds
    Dhiraj

    Dear Anil
    We had applied EHP3 enhancement, before EHP3 is working fine with no transfer sign assignment but after EHP 3 it gives the error and not in all billing document but in particular document only. so i think there is no changes required in KE4I.
    Rgds
    Dhiraj

  • Unable to display tree view; Error when parsing an XML document (Premature end of file.)

    Hi folks,
    I am using a cascaded mapping in my OM. I have a graphical mapping followed by the Java mapping. It is a flat file to IDOC mapping. Everything works fine in Dev but when I transport the same objects to QA, the Operation mapping though it doesn't fail in ESR testing tool, gives the following message and there is no output generated for the same payload which is successfully tested in DEV. Please advise on what could be the possible reasons.
    Unable to display tree view; Error when parsing an XML document (Premature end of file.)

    kalyan,
    There seems to be an invalid xml payload which causes this error in ESR not generating the tree view. Please find the similar error screenshot and rectify the payload.
    Mutti

  • Error when creating link to documents from material

    Hi all,
    while creating the purchase order the error message "Error when creating link to documents from material 61260224060" is displayed.
    why this error message is displayed.?
    Regards,
    GaneshRaja

    Hello Ganesh
    Please check material master - view 'Bases data 2'.
    There is checkbox 'No link'. You can activate this checkbox if you are not storing any drawing/designe docuemnt for this material.
    Try to do this and check out again.....
    If this helps you in resolving your issue, i would appreciate if you reward the answer with suitable points.
    Best Regards
    Avinash

  • Error when parsing the XML document

    hi all.
    i have the next problem.
    the sender sistem send to XI an XML. some tags send a '#' caracter.
    Sender Service send:
    Torre B1 - B#Unimev
    when Im traying to test XML inbound, XI show the next error:
    Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x14(:main:, row:1, col:992))
    XML:
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ZDEBMAS6>
    -   <IDOC BEGIN="1">
    -      <EDI_DC40 SEGMENT="1">
             <TABNAM>EDI_DC40</TABNAM>
             <MANDT>300</MANDT>
             <DOCNUM>0000000000339708</DOCNUM>
             <DOCREL>640</DOCREL>
             <STATUS>30</STATUS>
             <DIRECT>1</DIRECT>
             <OUTMOD>2</OUTMOD>
           </EDI_DC40>
    -      <E1KNA1M SEGMENT="1">
              <MSGFN>009</MSGFN>
              <REGIO>07</REGIO>
              <STCD1>20147972750</STCD1>
              <FITYP>01</FITYP>
              <STCDT>80</STCDT>
              <STCD3>0</STCD3>
    -         <Z1KNA1M SEGMENT="1">
                 <MSGFN>009</MSGFN>
                  <KUNNR>0001000563</KUNNR>
                  <ZZSOCRCV>3100</ZZSOCRCV>
                  <ZZGBDAT>00000000</ZZGBDAT>
              <b> <ZZAD_STREET_CO>Torre B1 - B Unimev</ZZAD_STREET_CO></b>
                  <ZZAD_ROOMNUM_CO>PB</ZZAD_ROOMNUM_CO>
                  <ZZAD_FLOOR_CO>E</ZZAD_FLOOR_CO>
                  <ZZAD_PSTCD1_CO>M5521AAR</ZZAD_PSTCD1_CO>
                  <ZZAD_CITY1_CO>Mendoza</ZZAD_CITY1_CO>
                  <ZZAD_REGIO_CO>07</ZZAD_REGIO_CO>
               </Z1KNA1M>
               <Z1ADRCM SEGMENT="1">
                  <MSGFN>009</MSGFN>
                  <KUNNR>0001000563</KUNNR>
               <b><STREET>Torre B1 - B Unimev</STREET></b>
                  <FLOOR>PB</FLOOR>
                  <HOUSE_NUM2>E</HOUSE_NUM2>
                  <CITY1>Mendoza</CITY1>
                  <POST_CODE1>5521</POST_CODE1>
                  <COUNTRY>AR</COUNTRY>
                  <REGION>07</REGION>
                  <LANGU>S</LANGU>
              </Z1ADRCM>
          </E1KNA1M>
        </IDOC>
    </ZDEBMAS6>
    Message was edited by: Rodrigo Pertierra
    Message was edited by: Rodrigo Pertierra

    Hi Rodrigo,
    Do you use a specific "encoding" like UTF-8 or ISO-8859-1 in your Sender CC.
    Try changing the Transfer mode to Binary instead of Text.
    Also go through these links:-
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    Invalid char in XML from inbound IDoc
    Hope this provides a solution.
    Regards.
    Praveen

  • When releasing a billing document for accounting getting error in VF02

    hi,
    when releasing a document for accounting in the transaction code VF02 we are getting the following error
    <b>" Prof.segment for Prim.cost elements not advisable for costing-based CO-PA"</b>
    Regards,
    Murali

    Hi Murali,
    Please do default setting for co- object- t code OKB9.
    hope it will serve ur purpose.
    Reward points if it helps.
    Regards
    Karan

  • Error when releasing billing to accounting document

    Why we tried to release the billing to accounting document. There is the below error.
    Could someone please kindly help?
    Message Identification: F5
    System Message Number: 358
    Output type: E
    The Diagnosis is 'This document refers to a document which contains an invoice reference.
    The Procedure is 'Enter a different document as the invoice reference'.
    Thanks,

    You might be creating the billing document for a flow where there might be original invoice and/or credit memo also.
    So check that the original invoice and/or credit memo has an invoice reference to itself (i.e. the invoice reference = the accounting document number) than there is an incorrect referencing.
    Remove this reference via FB02 in the original invoice and/or credit memo and it should work
    Regards,
    Gaurav

  • Error During Releasing of Billing Document to Accounts Department

    Hi,
    Kindly help me, we have just finished the upgradation from 4.6 version to 6 version. when we are releasing the billing document to accounts department error message is coming like this.
    No entry has been made in the assignment table for condition type P001.
    I verified this one through KE41 transaction, as already maintained the combination of condition type and value field both options (tick and untick of transfer +/-).
    Billing type is ZIV.we are getting this error message only for this billing type.
    kindly suggest me any SPA notes required to be implemented in order to release the same.
    Regards,
    Vasu S

    hi,
    once your order is created and also delivery, there is no problem in the data of the material.
    the only possibility is that you must have skipped the post goods issue step or if PGI is mandatory for delivery creation then there must not be appropriate stock for that item.
    you can check the stock of that particular material in the specific plant by t.code MMBE.
    regards,
    Siddharth.

  • Currency Type error when releasing billing docs to Accounting

    When I am trying to release the billing documents to accounting following error is displayed :
    company code ABC has currency type 31. the currency type has the currency key INR in the Fin. Accounting application. The same currency type is conveyed to fin. accounting accross the accounting interface with currency key CAD.
    System is also showing the tip :
    This is a system error in the calling application. Currency type 31 in company code ABC must have currency key 'CAD' when the data is transmitted.
    Please let me know if I have to do anything in Tcodes SCC4 or OB22. Detailed answer will be of help.
    Regards
    RK

    Hi Ravi,
    From the discription of the error what you have given what i umderstood is that in FI documents are posted with Currency INR, while the Cur. type 31 is transferring Cur. Key CAD to FI.
    Since there is a diff in the Cur the error is coming.
    Try to maintain Add. local cur in OB22 and then check.
    regards
    JS

Maybe you are looking for