Depot sales pricing error

hi all,
we do the depot sales, while in particular oder, i did the depot sale for the trading material,
in that  sales order , in the condition tab, the value of the  VBRS cost , system not taken the updated cost .it take the old cost
we maintain the V for teh material
we want to know that from where the system pick the VBRS cost and how to control the system to pick the updated cost for the material. we have to any config for that.

Hi Shibu,
Check the condition type settings :
Cond. class   A Discount or surcharge
Calculat.type A Percentage .
also check that amount/percentage field is check in v/06. Once this setting is maintained chcek you have the condition records maintained for the required combination. and the final check is in pricing procedure this condition type are not marked as maintained manually.
If these settings are maintained the system will determine the condition types automatically in the order .
Hope this will help you !!!
Regards,
Krishna O

Similar Messages

  • Depot Sales Pricing

    HI Experts,
    We configured Depot sales, while doing pricing Excise duty, Education Cess and Higher Education is not showing in Conditions.
    we got one solution through which we are not satisfied.Tthe solotion is that we went to condition tab and clicked on update button and selected " C ".
    Our requirement is that we need excise duty, Education Cess and Higher Education cess should be shown in the condition tab as  soon as we enter the plant into the shipping tab./
    Please give me proper solution
    Shibu

    Hi Shibu,
    Check the condition type settings :
    Cond. class   A Discount or surcharge
    Calculat.type A Percentage .
    also check that amount/percentage field is check in v/06. Once this setting is maintained chcek you have the condition records maintained for the required combination. and the final check is in pricing procedure this condition type are not marked as maintained manually.
    If these settings are maintained the system will determine the condition types automatically in the order .
    Hope this will help you !!!
    Regards,
    Krishna O

  • Sd depot sales pricing from me21n to vfo1

    i want automatic pricing at vf01 through me21n.
    pricing should flow from me21n to vf01

    Hello Prasanna,
    In Stock Transfer Cases there is no Sales document in SD, but still the basic Sales Order Functions like Item Category Determination, etc happens.
    This is due to Default Order Type assigned to Delivery Type (NL or NLCC). Thus system uses settings in Sales Doucment Type DL to determine basic SD Functions.
    Now coming to your question, in the copy control records Price Source is not required to maintain becase you are purely using SD Pricing Procedure itself.
    In Billing Type, the Pricing Procedure will be simply SD Pricing Proceure with normal Price Detemination settings. But when it comes to maintaining Condition Records (in VK11) you will not be able to do so. This is because you have set Reference Condition (& aplication) in Condition Type (V/06).
    The use of this setting is that you cannot maintian Condition Records in Sales Module, but System will access the Condition Record of the Referred Condition Type & Application (M - Purchasing). Thus if the Price components (Basic Price + Tax + etc) are exactly same in SD & MM Pricing, then values can be copied from MM Pricing. Means say for Basic Price (ZR00) you have set Reference Condition Type as ZN00 which is defined in MM Schema (Pricing Procedure), then system will search value for ZR00 in Condition Records of ZN00.
    We are using this in Sales Order & Shipment Document. We have a requirement that the Freight paid to Shipment Vendor should be eaxtly same as one charged to Customer in Sales Order / Invoice. Thus Reference Condition is a perfect solution here without any Z-Development.
    Hope I have managed to clarify your doubt to some extent.
    Thanks,
    Edited by: Jignesh Mehta on Feb 15, 2012 1:11 PM

  • Depot sales

    Hi All,
       Please provide me the solution on the following.
    Use of routine 356 in depot sales pricing procedure
    (ii) Steps involved in depot sales (right from the STO i.e. plant to depot & from depot to cust)
    (iii) Excise transaction type for scrap sales
    (iv) Where do we define ETTs
    (v) Scrap sales excise invoice is created through which t.code
    (vi) In system landscape client 800 called as
    (vii) Use of different payment terms at company code data & sales area data in XD01
    (VIII) MTO & MTS for single material code is configured. At VA01 system not considering un-restricted stock and while doing MRP Run requirements are get generated for sales order total quantity
    Regards
    Chowdary

    hi
    i sto process: vao1-vl01n-vf01-j1iin it foe sd process ofter mm people doing migo- j1ig ,  it means when u create the migo document stock can transfer to depo plant and storage location . ofter j1ig can capture. its for closing the sto
    foter depo sales: va01-vl01n-j1ij-vf01.
    it si for depo process .
    i n sto can use deferent  process so based on your requirment .
    in use of 356 ; routine
      INCLUDE FV64A356                                                   *
    data: begin of t_rg23d occurs 0.
            include structure j_1irg23d.
    data: end of t_rg23d.
    APPL COUNTRY SPECIFIC
    form frm_kondi_wert_356.
    For depot sale : picks the excise value from RG23D
    This formula when in the billing or proforma document, picks up the
    excise value posted for the delivery if the excise has been posted.
    In case the excise is not posted, then it continues with the excise
    value calculated in the system . It shows the calculated value in
    the sales order also
      TABLES : J_1IRG23D.
      DATA : tline type i,
             ZKOMV LIKE KOMV,
             LAND1 LIKE T001-LAND1,
             KALSM LIKE T005-KALSM.
      DATA : result type f.
      DATA : zvbrp like vbrp .
      if komk-vbtyp = 'M' or komk-vbtyp = 'U'.
        billing document or proforma document
        read table t_rg23d with key vbeln = komp-vgbel
                                    posnr = komp-vgpos.
        if sy-subrc ne 0.
           refresh t_rg23d.
        endif.
        describe table t_rg23d lines tline.
        if tline eq 0.
        select * from j_1irg23d into table t_rg23d
            where vbeln  = komp-vgbel
            and   posnr  = komp-vgpos
            and   status <> 'B'.
        if sy-subrc ne 0.
           exit.
        endif.
        endif.
        if j_1iexcdef-j_1itaxcal is initial.
    get customisation parameters
          select single land1 from t001 into land1
               where bukrs = komk-bukrs.
         select single kalsm from t005 into kalsm
               where land1 = land1.
          select single * from j_1iexcdef
                 where j_1itaxcal = kalsm.
        endif.
    get the condition names
          clear xkwert.
    get the excise value
          loop at t_rg23d.
            case xkomv-kschl.
              when j_1iexcdef-j_1icbedar.
                xkwert = t_rg23d-exbed + xkwert.
              when j_1iexcdef-j_1icsedar.
                xkwert = t_rg23d-exsed + xkwert.
              when j_1iexcdef-j_1icaedar.
                xkwert = t_rg23d-exaed + xkwert.
    *NCCD changes start
              WHEN J_1IEXCDEF-J_1ICNCCDAR.
                XKWERT = T_RG23D-NCCD + XKWERT.
    *NCCD changes end
    *ECS changes start
              WHEN J_1IEXCDEF-J_1ICECSAR.
                XKWERT = T_RG23D-ECS + XKWERT.
    *ECS changes end
              WHEN J_1IEXCDEF-J_1ICCESAR.
                xkwert = t_rg23d-cess + xkwert.
            endcase.
          endloop.
          exit.
      elseif  komk-vbtyp = ' '.
    saving the document, get the value from the internal table XKOMV
        read table xkomv into zkomv
           with key kschl = xkomv-kschl.
        xkwert = zkomv-kwert.
       elseif komk-vbtyp = 'H'.
        billing document or proforma document
        read table t_rg23d with key vbeln = komp-vgbel
                                    posnr = komp-vgpos.
        if sy-subrc ne 0.
          refresh t_rg23d.
        endif.
        describe table t_rg23d lines tline.
        if tline eq 0.
          select single * from vbrp into zvbrp where vbeln = komp-vgbel and
          posnr = komp-vgpos .
          if sy-subrc ne 0.
            exit.
          endif.
          select * from j_1irg23d into table t_rg23d
            where vbeln  = zvbrp-vgbel
            AND   POSNR  = KOMP-VGPOS
            and   status <> 'B'.
          if sy-subrc ne 0.
            exit.
          endif.
        endif.
        if j_1iexcdef-j_1itaxcal is initial.
    get customisation parameters
          select single land1 from t001 into land1
               where bukrs = komk-bukrs.
          select single kalsm from t005 into kalsm
                where land1 = land1.
          select single * from j_1iexcdef
                 where j_1itaxcal = kalsm.
        endif.
    get the condition names
        clear xkwert.
    get the excise value
        loop at t_rg23d.
          case xkomv-kschl.
            when j_1iexcdef-j_1icbedar.
              result = t_rg23d-exbed / T_rg23d-MENGE .
              xkwert = result * komp-mglme .
            when j_1iexcdef-j_1icsedar.
              result = t_rg23d-exsed / T_rg23d-MENGE .
              xkwert = result * komp-mglme .
            when j_1iexcdef-j_1icaedar.
              result = t_rg23d-exaed / T_rg23d-MENGE .
              xkwert = result * komp-mglme .
    *NCCD changes start
            WHEN J_1IEXCDEF-J_1ICNCCDAR.
              result = t_rg23d-NCCD / T_rg23d-MENGE .
              xkwert = result * komp-mglme .
    *NCCD changes end
    *ECS changes start
            WHEN J_1IEXCDEF-J_1ICECSAR.
              result = t_rg23d-ECS / T_rg23d-MENGE .
              xkwert = result * komp-mglme .
    *ECS changes end
            WHEN J_1IEXCDEF-J_1ICCESAR.
              result = t_rg23d-cess / T_rg23d-MENGE .
              xkwert = result * komp-mglme .
          endcase.
        endloop.
        exit.
        else.
    document other than the billing or the proforma
          exit.
        endif.
    endform.
    this for standerd routine at vofm
    5) __scrap scales excise invoice t.code j1iin__
    6) payment terms use based on customer ,  u can differentiate to the customer . it whole sale customers , retail customer s.
    7) in mto  u can maintain the  requirement type kek- so it means it is for special stock ,
    so material u can define with mrp views, u can maintain the schedule line  CP,
    This is mto, scenario,
    on MTS scenario  u can maintain  deferent requirement type ,
      U  CHECK THE setting in availabulity cheek
    8)With in CIN the account  determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types.  The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
    Edited by: bojjasivasankarreddy on Dec 15, 2011 7:08 AM

  • CIN - Depot Sales and Export Sales

    hi all
    i have few queries assosiated with cin
    1. Depot Sales Process:  As Depot sales pricing procedure will not have excise condition types in that, how we are going to pass the excise amounts to our customers so that they can take the excise credit.
    2. Can anyone please tell me the link where in i can get all the process configurations related to cin. For Example Factory Sale, Depot Sale etc, i mean to say like best practices.
    3. What is the difference between Exports under Bond, LOU and No Bond.
    regards
    rag

    HI
    Go to the below meantioned link you will get the idea of related to your questions.
    http://help.sap.com/saphelp_47x200/HELPDATA/EN/09/ebf138cdd78a4be10000000a114084/frameset.htm
    Thanks & Regards,
    E.vasu
    Edited by: Vasu Enaguthi on Jul 17, 2009 7:02 AM

  • Rajesh/Sadhu= Pricing Proc. Difference between Factory and Depot Sales ?

    Hi,
      What is the diff. between the Pricing Proc of Factory and Depot Sales ?
      CIN Version.
    Regrds,
    Binayak
    Message was edited by:
            Binayak Ghosh

    Hi,
    We was into the depot sales project.We have done till excise duty.
    That means,first we are created a sales order and then outbound delivery for that.So based on the outbound delivery number normally we do billing.
    But here after outbound delivery we are in to assigning excise duty tothe delivery.In j1ij we have given and done all the things its working fine by FIFO method.It will first show the first procurement.We will select and this process got over.RG23D table is filled up with the values.
    But after this i gone for doing billing in VF01.But when i give the delivery number,it shows the condition typea and values but it didnt show any thing about excise duty which we are giving,So can anyone plz help me in this issue.
    Whether any configuration we want to do,or any thing we want to do internally.
    Routine 356, which transfer this from j1ij to billing is not happening, Since it is direct procurement of traded items , excise duties need to be passed on to customer directly, Here I hope there is no point of calcualting the excise duty, Since the excise duty would have inventorised.
    UTXJ condition record are maintained.

  • Depot Sales-Error in J1IJ

    Hi Experts,
    We are trying to do Depot sales configuration.
    we have configured stock transfer first . scenario i would explain below.
    we created Purchase order with the help of ME21N then we have done the delivery with the help of T code VL10B, VL02N then we created invoice with the help of VF01 and created Excise invoice with the help ofJ1IIN,   then did  MIGO for Good receipt after that we Used T code J1IG  here we are ending the stock transfer process.
    then we started to do sales from Depot.
    we created sales order VA01 then we delivered the item with the help of VL01N after that we are trying to create excise invoice with the help of J1IJ for RG23D, BED and CEss are not appearing in the " Select Excise Invoice for Delivery"  view 
    Let me explain how i used the Tcode of J1IJ :---  We enter the t code J1IJ then went to delivery menu and selected RG23D selection while system required to enter Delivery no, Excise group and series group then i enter while we entered into "Select Excise Invoice for Delivery" view where we coudnt find the Basic Excise Duty BED, Education Cess and Higher Education cess in particular coloumn. i believe that the same BED and Cess amount of J1IG should be shown in while creating J1IJ but BED and Cess is not capturing in J1IJ.
    Advanced thanks
    regards
    Shibu Chandran

    Possibilities:1. In DEPO Pricing procedure check the Calc ty routine 356 for excise condition types
    and In SPRO LG -  For ETT GPRO  2. Specify Excise accounts  per excise transacton and  3. Specify GL accounts per Excise Transaction
    Removed by Moderator
    Edited by: Lakshmipathi on Aug 19, 2010 8:23 PM
    Please avoid adding this comment

  • BOS problem in Sales Order (Pricing error)

    Hello every one,
    In my project i am getting scenerio of BOS- Bill of services. Now in that when i am creating sales order i m puting material and everything. Now at item level in am selecting "SERVICE" tab. When i am putting service there i am getting one pricing error that is "Conditions for service price determination incomplete". This is scenerio of bill of services. Kindly help me in this.
    Regards
    Abhishek

    Hi,
    Have you maintained the item level pricing?
    regards,
    raja

  • Pricing ERROR in SALES ORDER

    HI Guys,
      I am Using BAPI BUS2032 to migrate all the Sales Order from Legacy to SAP through LSMW.
       When I process the Idocs I get Error. Processing Terminated. Pricing Error.
    (KOMP-FXMSG = 801). The status is 51.
       But the Pricing Procedure is maintained in OVKK for the corresponding Sales Organisation combination and the record is maintained in VK11 too.
        I have also checked the A900 table where the material also exists.
        Can you sort me out what the problem is. Client is very specific in doing things through LSMW.
    Regards,
    Jack.

    Hi Jack!
    Did u get any solution to it? Because even I am facing similar problem while updating a sales order through BAPI - BAPI_SALESORDER_CHANGE.

  • Pricing Error in Sales Order - How to Maintain...

    I am newbie in SD and having issue, I have a sales order where I enter material and get "Pricing error: Mandatory condition PB00 is missing". Now I know this condition is set for manual entry if it is not found via procedure. But where do I maintain this manual entry, I have checked everywhere and cannot find where I can manually enter or edit the PB00 condition at the item order level?

    GaryGrewal ,
    In SD we use PR00 Condition type and not PB00. For PR00 you maintain datas in various combinations. Customer/ Materila or Material or Price list catgeory/ currency/material. This condition can be either kept manual or maintained as manadatory.
    Can you explain us why you are using PB00 - Gross- Price Only if you have some special  scenario...
    You rename PB00 to ZPB0 and include in the pricing procedure.
    This codition type does not have access sequence so you enter data manually during sales processing.
    Which means moment you create sales order by entering sold to party, po no, material and the qty. Then Double click Item details --> Choose Condition tab.  OR Choose the line item and then Click GoTo --> Item --> Conditions
    In Condition Type column enter "ZPB0"
    In Amount Column enter the value.
    That's it check the value. click save
    Please visit
    [www.sap-img.com ] Choose sales and Distribution  and go through the concepts i hope it will help you understand the basic principle and the process
    Regards
    Sathya
    Edited by: Sathya Pavan Yedavalli venkata on May 5, 2009 9:41 AM

  • Pricing procedure for Depot Sales(CIN Version)

    HI,
    Can anyone explain me TAXINJ and
    The Pricing procedure for Depot Sales(CIN Version)
    alongwith the Condition Types like JMOD,JECS,JECX etc.
    Points will be given
    Regrds,
    Binayak

    Hi Binayak.
    JMOD is a FI Tax condition which gets the Basic Excise duty from calculation formula 352. JEX2 is a copy of JMOD and is a Sales pricing condition. The value of JEX2 gets posted for Excise account key. This ensures that the cost accounting of excise value paid is done correctly. In cases where commercial invoice is created after utilization the condition value formula 353 ensures that the actual MODVAT utilized is accounted as excise.
    Similarly JAED is a FI Tax condition which gets the Additional Excise duty from calculation formula 352. JEXA is a copy of JAED and is a Sales pricing condition. The accounting is done for the value of JEXA.
    JSED is a FI Tax condition which gets the Special Excise duty from calculation formula 352. JEXS is a copy of JSED and is a Sales pricing condition. The accounting is done for the value of JEXS.
    JCES is a FI Tax condition which gets the CESS from calculation formula 352. JCED is a copy of JCES and is a Sales pricing condition. The accounting is done for the value of JCED.
    So, Conclusion :---->
    JMOD  -- >  Basic Excise duty condition  for FI side.
    corresponding to it,
    JEX2 is the Basic Excise duty condition  for SD side.
    That's why
    account key to  JMOD is linkes in TAXINJ.
    and     
    account key to  JEX2 is linkes in JDEPOT.
    Hope this certainly helps you.
    Please reward points if found useful to you.
    Let me know if you have any other doubt.
    Regards,
    Gaurav Raghav.

  • While Creating Sales order Item pricing error is coming........

    HI Friends,
    I  have just given all values in VA01  not saved at tht time and before saving i go the Extras -->Output ---> Header -> Print Preview----> i got the form then i  back to the screen ... now i save sales order but it giving error " Item Pricing error" if  i click on item pricing error button it goes to the  sap first screen.
    could you please help me in this......
    Regards
    Venkat boddu

    May be fault items where there is no pricing or so.
    Check all items and reprice them before save. if they are ok then go to MV45AFZZ and check save document prepare and save document user exits for the message. Also check form and print program.
    Last but not least, get the message number and class for the message then go where used list for that message.
    Mostly, this message is populated in user exits.

  • Pricing procedure for Depot Sales

    Hi SAP Expert,
    Is Tax procedure TAXINN must use Pricing Procedure JINDEP for DEpot Sales ?
    If we use JINDEP, how do we configure for the excise duty value flow from J1iJ to VF01 ?

    Hi SAP Experts,
    Any comment or advice on the subjected post ??

  • Pricing Error on Sales order :Critical:

    Hi all,
    I'm creating a sales order,  where in I'm getting Pricing Error.
    Condition record is maintained for PR00 in USD
    It is getting populated but showing red signal.
    VPRS also showing Red signal. If I go in analysis of VPRS , it shows message exchage rate error. But Company code currency & document currency is same USD.
    so It should not give this error.
    But If I go to customer master & in sales area tab & maintain currency as USD, then there is no error in Sales order. All is fine.
    But logically , system should not ask the exchage rate as Company code & document currency both are USD.
    I expect some quick replies as we are now in impact analysis & on verge of go live next month.

    Thats what I mention in previous post that
    Its a standard beheviour, Document currency is proposed/determined in sales order or billing doc on the bases of customer master record of the Sold-to Party.
    And exchange rate for same currency is out of question.
    Thats why, when maintain curreny in customer master (Sold-to Party), you don't get error.
    As, system is able determine/propose a currency for document currency.
    Further, what you can do is press F1 button on the following fie,lds for more clarification.
    > Sales Order - Header  - Sales Tab - Pricing & Statistics Section - Doc. Currency Field
    > Customer Master - Sold-to Party - Sales Data - Sales Tab - Currency Field
    I hope that clarifies.
    Regards
    JP

  • Depot sales error

    Hi All
    In depot sales - Depot Excise Invoice(T.Code-j1ij) not reflect in ED and Ecess and S & H Education Cess. Plz help me.
    Regards
    Chandra

    Hi
    C Reedy
    Check whether u have maintain the ECS and SH&ECS rate     in J1ID. Or check in table J_1IEXCTAX the % for ECS and SH&ECS agsinst thech id. of the material If not then pl maintain and try.
    Thx.

Maybe you are looking for