7 Replies Latest reply: Mar 1, 2012 7:29 PM by Brian Patterson RSS

Error existing in processed Bdoc

Marry SAP
Currently Being Moderated

Hi Guru's

 

We have Processed Bdoc in the inbound flow and it has errors.

 

Can anyone let me know how is it possible that processed Bdoc can have errors? is there any fucntionality from SAP for those?

 

Thanks and regards,

marry.

  • Re: Error existing in processed Bdoc
    Shanthala Kudva
    Currently Being Moderated

    Hello Marry,

     

    Processed BDocs means BDoc in Green State?

    What exactly is the error message?

     

    Best Regards,

    Shanthala Kudva.

  • Re: Error existing in processed Bdoc
    Brian Patterson
    Currently Being Moderated

    Hi Marry,

    Can you let me know the specific stat of the BDoc, the BDoc type and also the errors given? Please inculde the full error text ad the code. (I've heard various explanations of this type of behaviour, but never one that fully satisifed me.)

     

    By the way, are you sure there wasn't an additional error or errors, in addition to the ones oyu see now, before the BDoc went to processed?

     

    Best regards,

    Brian.

    • Re: Error existing in processed Bdoc
      Marry SAP
      Currently Being Moderated

      hey Brian, How are you?

       

      State of the Bdoc is F02.

      Error says "No revenue account determined for bill doc 1678809 / item 0000000030 / cond. type ZKMP

      BEA_ACD 007.

       

      I am not sure.. i may had additional errors. But how is it possible that Errorded bdoc in F02 status?

       

      Besr regards,

      Marry

      • Re: Error existing in processed Bdoc
        Brian Patterson
        Currently Being Moderated

        Hi Marry,

        I'm good thanks.  Hope you are too.

         

        From the middleware point of view, it shouldn't happen that a BDoc with state F02 has an error. States F01-F04 are all green. But F01 would be rejected and can therefore have an error.

         

        For any of F02-F04 to show and erorr, this must be an issue with the application logic. In this case, the application responsible is CRM-BE-FI, I believe.I'm assuming the the BDoc type is BEABILLDOCCRMB. Is this correct? I'm not an expert on this application, but I did find the following explanation from a developer in an old case, describing why BEABILLDOCCRMB BDoc's can have state F02 and still show errors.

         

        "The transfer of the CRM billing document to accounting works according

        to a request-response mechanism. This works as follows:

         

        ==>BDoc type BEABILLDOCCRMB for flow context MO1 is sent when you

           save the billing document or via the Transfer billing documents

           to accounting transaction, this triggers the FI/CO transfer.

         

        ==>At the same time, a billing document which is released for the

           transfer to accounting is indicated with the value B = Billing

           document is in transfer in the transfer status (TRANSFER_Status).

         

        ==>After the update of the FI/CO document in the R/3 system, a

           further BDoc type BEABILLSTACRMB is sent for the status update of

           the billing document.

         

              - In the case of success, the billing document is indicated with

                status C = Billing document has been transferred.

         

              - In the case of an error, the billing document is indicated

                with status not transferred and with an error code in the

                'Transfer error' field.

         

        This Bdoc BEABILLSTACRMB will be green status once it updates the status

        and the error information from r/3.

        Monitoring these Bdocs are not ideal scenario.

        Always you can check the transfer_status from the transaction

        /n/bea/crmb11.

        Which can also be checked from the Web UI in the "Search Billing

        documents",Transfer to Accounting Status, you can find which are all

        not transferd,and also the corresponding error messages."

         

         

         

        I think you should be able to resolve the error by maintaing the account assignment for the relevant sales organization / condition / expens type in IMG:

         

        CRM -> Billing -> Integration ->

        Transfer to Accounting -> Transfer to FI AR/AP -> Enh. Account

        Determination -> Assign symbolic account key

         

        Please restart transfer via /BEA/CRMB12 once the missing entry is added.

         

         

        Best regards,

        Brian.

        • Re: Error existing in processed Bdoc
          Marry SAP
          Currently Being Moderated

          Hello Brian,

           

          Thanks for the explanation.

           

          Can you please explain bit more on how application can be responcible for such issue.. you can take BUPA_MAIN as an example. coz we have such issues happening for bupa_main also.

           

          regards,

          Marry.

          • Re: Error existing in processed Bdoc
            Brian Patterson
            Currently Being Moderated

            Hi Marry,

            I did find one middleware note that corrects an isse with BDoc's wrongly set to F04, even though they have errors. The note number is 933868. Maybe that could be relevant to some of your BDoc's?

             

            Another possilbe explanation would be if someone manually set the BDoc to 'deleted' in SMW01.

             

            If neither of the above applies, it would again be helpful to know the state with full error text. Please be sure to add the error code and function module.

             

            Best regards.

            Brian,

Actions