Duty Values flowing negative on saving Billing Doc

Hi,
In Billing Document inVF01, the duty values are flowing correctly,where as,while on saving billing and in change mode I get duty value is changed and SHE cess is negative.We have used rounding routine 17 in our Pricing proce.This happens only for a particular line item.
Can anybody tell why it happens and how to overcome this problem?
Regards
Vadiraj

Hello ,
firstly use "/h" on VF01 t-code before saving document, with on debugging mode use menu bar breakpoint at statement and write this statement "CALL CUSTOMER FUNCTION" , when you see that statement,double click them and you can go that function modules, activate begin charachter Z* customer namespace customer exits which is in function modules ,use breakpoint in this customer include programs,and activate them. you can again run with debugging mode VF01 t-code and save document  during you see VBRK-VBELN billing number,test your program be carefully ,
regards,
Ugur Baris Turkeli
SAP Certified ABAP Consultant

Similar Messages

  • Net value showing negative in excise billing for free goods items

    Dear All,
    Need value suggestions in business scenario.
    While issuing Free goods to customer in excise billing ,Net  value of ZTNN item showing negative
    Inserted R100 % condition type above Tax condtions.
    MRP is statistical and accessable value is calculated on MRP.
    How to  solve the above issue.
    Due to the Net value showing negative for Free of charge in excise billing,qty value  displaying twice the unit price value in printing
    Thanks & Regards
    H V Kumar.

    Hi
    It is depends on your pricing procedure how you defines.
    Kindly check once again in your pricing procedure.
    Test the cycle once again without entering the R100 condition type in sale order line item and check the next value.
    After enter the R100 condition type check the base value to calculate the Amount.

  • Find out user exits which should trigger while saving billing doc.(VA01)

    Hi All,
    please can u help me to find out user exits which should trigger while saving billing documents for VA01 transaction...I have already z report to find the user-exit for any transaction.I have tried in that also.
    Reply
    Ulhas

    Hi
    Try these
    USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)                    
    The internal number range used in the standard system is specified                
    in the billing type table and can be changed in this user exit. This              
    user exit is only called when the billing documents is created.                                                                               
    USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program                       
    RV60AFZZ)                                                                         
    In this user exit additional fields for account determination that                
    are not provided in the standard system are copied into                           
    communication structure KOMKCV (header fields).                                                                               
    USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)                               
    In this user exit additional fields for account determination that                
    are not provided in the standard system are copied into                           
    communication structure KOMPCV (item fields).                                                                               
    USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program                     
    RV60AFZC)                                                                         
    Depending on the number range, table TVFKD is used to set the                     
    billing date (country-specific requirments in Italy).                             
    USEREXIT_NUMBER_RANGE is automatically deactivated when this user                 
    exit is being applied.                                                                               
    USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)                  
    This user exit is only called when the billing document is created.               
    It is used to provide the header and the item of the new billing                  
    document with deviating or additional data.                                       
      USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)                    
      Printing the item line of a billing document can be supplemented or             
      changed.                                                                               
    USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)                     
      Printing the header line of a billing document can be supplemented              
      or changed.                                                                               
    User exits in program RV60AFZD                                                  
      Short descriptions of the user exits are contained in the program:                                                                               
    -   USEREXIT_RELI_XVBPAK_AVBPAK                                                                               
    -   USEREXIT_NEWROLE_XVBPAK_AVBPAK                                                                               
    -   USEREXIT_NEWROLE_XVBPAP_AVBPAK                                                                               
    e following user exits are available in report SAPLV60B for transfer              
    accounting (function group V60B):                                                                               
    EXIT_SAPLV60B_001: Change the header data in the structure acchd                
      You can use this exit to influence the header information of the                
      accounting document. For example, you can change the business                   
      transaction, "created on" date and time, the name of the person who             
      created it or the transaction with which the document was created.                                                                               
    EXIT_SAPLV60B_002: Change the customer line ACCIT                               
      You can use this exit to change the customer line in the accounting             
      document. This exit is processed once the ACCIT structure is filled             
      in with data from document header VBRK.                                                                               
    EXIT_SAPLV60B_003: Change the customer line in costing                          
      The customer line is filled in differently for costing. You can use             
      exit 003 to influence the ACCIT structure.                                                                               
    EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add          
    information to a GL account item (such as quantity specifications)     
    with this exit.                                                                               
    EXIT_SAPLV60B_005: User exit for accruals                              
    Once all relevant data for accruals was entered in the GL account      
    item, you can add to this data with this exit.                                                                               
    EXIT_SAPLV60B_006: Change the control line ACCIT                       
    You can use exit 006 to add information to the control line.                                                                               
    EXIT_SAPLV60B_007: Change the installment plan                         
    You can use exit 007 to add information to the installment plan        
    parameters in the GL account item.                                                                               
    EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and      
    ACCHD                                                                  
    After the accounting document is filled in with data, you can use      
    exit 008 to change the document once again.                                                                               
    EXIT_SAPLV60B_010: Item table for customer lines                       
    You can use exit 10 to influence the contents of customer lines        
    before they are created.                                                                               
    EXIT_SAPLV60B_0011: Change the parameter for cash account              
    determination or reconciliation account determination                  
    You can use this exit to change inbound parameters in order to         
    influence account determination.                                       
    >                                                                      
    Thanks
    Shiva

  • How to retrieve value of VBRK-VBELN ie. billing doc number on save of VF01

    Hi friends,
    I am working on a scenario where I need to update my custom table with values of Sales org, billign date and Billign document number on saving of VF01. I have tried using RV60AFZC include and user exit: USEREXIT_FILL_VBRK_VBRP.
    But on debugging when I save VF01, I am able to retrieve values VKORG and billing date FKDAT, but I am not able to retrieve VBRK-VBELN field. This is the billing document number.
    Can you kindly suggest me how can I retrieve my values for I can update my custom table.
    Regards
    Dolly Arora

    Hello ,
    firstly use "/h" on VF01 t-code before saving document, with on debugging mode use menu bar breakpoint at statement and write this statement "CALL CUSTOMER FUNCTION" , when you see that statement,double click them and you can go that function modules, activate begin charachter Z* customer namespace customer exits which is in function modules ,use breakpoint in this customer include programs,and activate them. you can again run with debugging mode VF01 t-code and save document  during you see VBRK-VBELN billing number,test your program be carefully ,
    regards,
    Ugur Baris Turkeli
    SAP Certified ABAP Consultant

  • Value flows to COPA through Billing

    Hi!
    we have defined Operating concern as Costing based.
    We have assigned value fields to SD conditon types which are related to different revenues.
    By mistake one of the revenue GL is not defined as revenue element, so values are not flowed to COPA.
    Now , how to rectify values in COPA.
    whether we need to post manually the value to copa to that specific value field by arriving amount by other method?
    or can we repost Billing document to rectify the values in COPA? what is the best method to follow?
    we have another problem of cost of goods sold. we are treating VPRS condition type in Billing as Cost of goods sold.
    But my doubt is even though there will not be any cost element with respective to VPRS condition type, the value will flow to COPA or not?
    we have not defined cost of goods sold as cost element and don't want to flow the value from this GL account which is coming from PGI to COPA.
    How can we get VPRS cost to COPA ?
    regs,
    ramesh

    ajay,
    KE4SFI, is only to transfer FI documents ( directly posted in FI) to COPA, so, this is not required for us.
    Of course I tried by entering billing accounting document numbers, but not posting.
    secondly, our scenario is now we have to adjust copa values for already posted Billing documents.  For example we have two types of revenues _ direct revenue and pallet revenue. direct revenue already flowed to COPA, where as pallet revenue is not flowed because, we have forgotten to create that GL account as cost/revenue element.
    Now If I use KE21N, I am not able to give reference Billing document number, there by I can get report for each billng document wise.
    Secondly if i use KE4S, if i ticked Update control with "check for existing records", system is not posting any thing ( In this I want to transfer only pallet price to COPA not any other values).
    If  I ticked update control with "Posting with out check", system is generating COPA document i.e it is posting all the values again. SO, for the same billing document we will have to copa document which will duplicate the values which are already posted, which is not correct.
    I think now I have explained my situaiton.
    can you suggest to pass only pallet price to copa with reference to billing document?
    regs,
    ramesh

  • Billing doc cancelled

    Dear Friends,
    We are facing a major issue which is as follows:
    A bill doc was cancelled. The doc flow of the original billing doc shows:
    Delivery (Archived)-> Sale Invoice (Completed)-> A/cing doc (Not Cleared)
    The cancelled doc is not coming in the above doc flow. What can be the reason that cancelled doc is not coming in the doc flow?
    On the other hand the doc flow of the Cancelled doc shows:
    Delivery (Same as above) (Status Archived)->Cancel Inv (S1) Status- Missing export data. (Transaction is domestic). Here also the original bill doc is not coming in the doc flow of S1. However the original doc is coming in the Assignment field in the header of S1. Again what can be the reason? We also want to clear the A/cing doc of the original Billing document. How is this possible?
    Is there any T.Code for displaying J1ID?
    Plz hep to solve these issues.
    Thank you very much.

    Go to VA03, key in the sale order reference and check the document flow.  Let me know whether you could see the original billing document that was cancelled.  If not, check in copy control whether you have ticked the box "Update document flow".
    Is there any T.Code for displaying J1ID?
    What do you mean by this ??  J1ID itself is a standard TCode.
    thanks
    G. Lakshmipathi

  • Billing doc - control field to post values to accounting

    IN PROFORMA INVOICE THE VALUES WILL NOT BE POSTED TO ACCOUNTING
    WHEREAS IN STANDARD BILLING DOC F1 AND F2 VALUES WILL BE POSTED WHERE IS THE CONTROL KEY FOR THIS
    THANKS

    Hi kishore dhanekula , my sur name also dhanemkula
    as per your question the main key setting is in billind document type
    (T.code VOFA )
    for F2: there is revenue account determination procedure is there
    but for F5 or F8 there is no revenue account determination procedure is available
    and one more key settingis document catogory for f2 is M
    and for F8 is O for proforma invoice
    i think it can helps u , if it is reward me
    Thanks& Regards
    Venkat.Dhanemkula

  • Billing doc is not getting saved.

    Hi All,
    I am doing  billing with ref to Delivery in VF01. Billing doc is processed but when I click on save button to create document..its not saving and redirecting to initial billing overview screen.
    I assume this is some system setup issue and needs to be looked by Basis. Is this Basis issue or an SD Consultant can solve this one.
    what needs to be setup properly to resolve this one.
    Your inputs are appreciated.
    Naveen

    Gampa,
    During invoice creation, please sit with a technical guy and debug the process. In 10minutes you should be able to find out hte actual problem, as there can be many reasons why the invoice creation is coming back to VF01 screen.
    My hunch goes to Number ranges. The number range can be completely exhausted and because of this, it is not able to assign a number to the newly created document. If you debug it, you should be able to find out the correct reason.

  • Excise duty values not flowing from PO to MIGO

    All SAP Gurus,
    We have created a PO and used excisable tax code in it.
    Excise duties are calculated correctly in PO.
    When we go for Goods receipt against the PO, excise tab appears, but there are no values in excise fields (fiels are blank).
    System allows us to enter the Excise duty values manually.
    Further excise entries and register updates are happening correcetly.
    We do not undersatnd why the Excise duty values are not flowing automatically from PO to GR (MIGO).
    Please help.
    Regards,

    hi
    chekc following
    path: spro>logistic general >tax on goods movements>india >basic settings>determination of excise duty >maintain excise defaults >
    here give appripriate conditions for ur procedure as per BED   cess and other
    regards
    kunal

  • Wrong excise value is calculated in billing doc. = VF01.

    Dear All ,
    I have created a billing doc for a STO , now my price of 1 ton is Rs 57328.94 & in billing the Con for exc is JEXP it is for,14 % but the exc cal culating as Rs 8329.61 , instead of Rs 8026.05 here the wrong calculated Rs 8329.61 is 14.529 % of Rs 57328.94 .so i m in VF03 now selected the cond type & clicked on detail icon here what i see that the a screen opens for header cond. details , here in cond details tab the amount coming as 14 % , Cond base value is Zero & Cond value is Rs 57328.94 , After this on the same scren i had clikced on Go to -
    > cond record --> here also 14 % is given then how the system is calculating 14.529 % instead of 14 % .
    Rgds
    sap12

    in the STO under cond tab at item level i had clicked on analysis tab then the con appearing are as under --->
    Condition type     Message     Description
    P101     213     Amount copied from material valuation data
    FRB1     207     Condition has been found (without condition record)
    FRC1     207     Condition has been found (without condition record)
    FRA1     207     Condition has been found (without condition record)
    Y017     207     Condition has been found (without condition record)
    Y018     207     Condition has been found (without condition record)
    Y019     207     Condition has been found (without condition record)
    Y020     207     Condition has been found (without condition record)
    Y015     207     Condition has been found (without condition record)
    Total Cost     200     Subtotal
    Here there is no JEXP , now as u wrote thjat to check the excise rate in J1ID -
    > there is no excise rate made for this material , after this ---> in exceptional exc rate there are no entries., now pl guide that what to check .
    Rgds
    sap12

  • Rebate: Differ "Scale Base Value" between "Statistics" and "Billing Doc"

    Dear SD Expert,
                After I go with Transaction Code :"VOB3" (run report RV15B002), I found that "Scale Base Value" have different value between "Statistics" and "Billing Doc". And the correct value is "Billing Doc". However, the value which shows in my rebate condition now is "Statistic". Thus, my question is
                How can I configure my rebate condition based on "Billing Doc" Value instead of "Statistic"? (I don't want to "Correct backlogs" anytime in changing scales based value.)  Anyone please feel free in suggestion.
    Thanks,
    Prach

    HI,
    This may be useful to you.
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/5612d8545a11d1a7020000e829fd11/content.htm
    Vrajesh

  • Duty value is not flowing in import at the time of capturing j1iex,

    Hi freinds,
    duty value is not flowing in import at the time of capturing j1iex, after miro for planed del cost
    please let me know what are the possible reasons
    Regards,
    Balu

    HI,
    Have u given the inputs in J1ID.Have u given the details in Chapter id,Chapter id& Material.cenvat determination etc.
    Have u created all the 7 conditions as Planned delivery cost in Cond type.
    murugan

  • GL account posting when billing doc saved

    Hi to all,
                  Please make sure the term. How GL account posting when billing document saved or it release to accounting?
    Thanks.

    Hi,
    If your question is how the GLs are picked up while the billing doc is released to accounting, then-
    GL accounts are derived from the automatic account determination maintained at VKOA.
    Regards,
    Mike

  • Difference in Billing doc value & MCSI report

    Hi Gurus,
    What could be the difference in value between the billing value & the MCSI report?
    Regards,
    Kumar

    Hello,
    MCSI is based on infostructure and updated on the execution of transaction.If at the time of creation of billing document ,you have not configure the billing doc type,item category and not assign the proper update group to them then MCSI will not be updated and later on you will find the difference in MCSI nad total billing value.
    Sunil

  • How to get the value of bill doc after creating it using tc VF01.

    hi,
    i want to get the bill doc no after  creating it using BDC tc VF01.
    with that no i have to update the ztable.

    hi,
    i tried with the above mentioned method to get the created delivery no.but i am unable to get the created billing doc no using bdc tc VF01.any idea about this...
    REFRESH       tt_bdcdata.
      PERFORM bdc_dynpro      USING text-005 text-006.
      PERFORM bdc_field       USING text-008
                                    text-017.
      PERFORM bdc_field       USING text-009
                                    text-011.
      PERFORM bdc_field       USING text-017
                                    wa_worklist-del_no . "wa_created-document_numb.
      PERFORM bdc_dynpro      USING text-006 text-007.
      PERFORM bdc_field       USING text-008
                                    text-018.
      PERFORM bdc_field       USING text-009
                                    text-019.
      CALL TRANSACTION c_t_bill USING tt_bdcdata
                                                MODE c_m
                                                UPDATE c_u
                                                MESSAGES INTO tt_bdcmsgcoll .
      SORT tt_bdcmsgcoll BY msgtyp.
      READ TABLE tt_bdcmsgcoll INTO wa_bdcmsgcoll WITH KEY msgtyp = c_e.
      IF sy-subrc EQ 0.
        LOOP AT tt_bdcmsgcoll INTO wa_bdcmsgcoll WHERE msgtyp = c_e.
          CALL FUNCTION 'FORMAT_MESSAGE'
            EXPORTING
              id        = wa_bdcmsgcoll-msgid
              lang      = text-010
              no        = wa_bdcmsgcoll-msgnr
              v1        = wa_bdcmsgcoll-msgv1
              v2        = wa_bdcmsgcoll-msgv2
              v3        = wa_bdcmsgcoll-msgv3
              v4        = wa_bdcmsgcoll-msgv4
            IMPORTING
              msg       = v_msg
            EXCEPTIONS
              not_found = 1
              OTHERS    = 2.
          IF sy-subrc <> 0.
          ENDIF.
          WRITE :/ v_msg.
        ENDLOOP.
      ELSE.
        READ TABLE tt_bdcmsgcoll INTO wa_bdcmsgcoll WITH KEY msgtyp = c_s.
        IF sy-subrc EQ 0.
          CALL FUNCTION 'FORMAT_MESSAGE'
            EXPORTING
              id        = wa_bdcmsgcoll-msgid
              lang      = sy-langu
              no        = wa_bdcmsgcoll-msgnr
              v1        = wa_bdcmsgcoll-msgv1
              v2        = wa_bdcmsgcoll-msgv2
              v3        = wa_bdcmsgcoll-msgv3
              v4        = wa_bdcmsgcoll-msgv4
            IMPORTING
              msg       = v_msg
            EXCEPTIONS
              not_found = 1
              OTHERS    = 2.
          IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
          MOVE wa_bdcmsgcoll-msgv1 TO v_billno.
         wa_epit-bill_no =  v_billno .
         MODIFY TABLE  tt_epit FROM  wa_epit TRANSPORTING bill_no.
         UPDATE zsd_dt_epit SET bill_no = v_billno where del_no = wa_created-document_numb .
         IF sy-subrc EQ 0.
         ENDIF.
          MOVE: v_billno TO wa_worklist-bill_no .
          READ TABLE tt_epit INTO wa_epit WITH KEY epi_id = wa_worklist-epi_id epi_sr = wa_worklist-epi_sr.
          IF sy-subrc EQ  0.
            MODIFY tt_epit FROM wa_worklist TRANSPORTING bill_no WHERE epi_id = wa_worklist-epi_id AND epi_sr = wa_worklist-epi_sr.
          ELSE.
            APPEND wa_worklist TO tt_epit.
          ENDIF.
        ENDIF.
      ENDIF.
    please suggest me..its urgent

Maybe you are looking for