Invoice Split bassed on Condition Type

Hi ,
For the invoice split issue, PFB the functionality required:
1.       1) Sales order created where the item condition tab would have the Standard price as well as a condition type for the freight charges.
2.       2) Create a delivery for this sales order.
3.       3) At present, we get an invoice for the above sales order created with the standard price and the freight charges on the same invoice.
Requirement:
We need 2 invoices, where one invoice has the standard price and the other has the freight charges printed separately for the above Sales order scenario.
if this requirement is feasible?
I have search in SDN i have found the below links
http://scn.sap.com/thread/3476396
The Above link he has Confirmed is feasible. He provided the SAP Note and he told write the routine in VOFM. I refer the SAP Note they have provided the header level split.
Can you please tell how can i atcheive that? if Any one done the same previously please tell how you done that?
Thanks,
Dhina..

Hi Fred,
There is no problem in that SAP note. I just want to know how can i atcheive that?
if any one done the requirement previously how they done that? i need the each and every steps.
Thanks,
Dhina.

Similar Messages

  • Invoice document against PO condition type

    Hello,
    I am developing a landed cost sheet of a Import PO in which i have to display the exchange rate and total value against condition types(in PO). This exchange rate and value is to be taken from the invoice document against the relevant condition type. [Purchase Order History tab is displaying the associated Invoice(RE) against the condition types. How r the invoice kept against condition types in SAP ? and how can i retrieve these values against a cond type thru abap code...  ?
    Hope i am comprehendable and sumone can provide me a reasonable solution ?
    Thanks,
    Shehryar Dahar

    Hi
    You need to fetch the data from EKBE and KONV tables
    Table EKBE has the invoice Number  and PO number etc
    Take KNUMV field of this table and pass to KONV-KNUMV table
    and take the related Rate(KBETR) and Amount(KWERT) fields for the related Condition type and use
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Invoice document against PO condition types

    Hello,
    I am developing a landed cost sheet of a Import PO in which i have to display the exchange rate and total value against condition types(in PO). This exchange rate and value is to be taken from the invoice document against the relevant condition type. [Purchase Order History tab is displaying the associated Invoice(RE) against the condition type. How r the invoice kept against condition types in SAP ? ... Hope i am comprehendable and sumone can provide me a reasonable solution ?
    Thanks,
    Shehryar Dahar

    Hi,
    When you post an invoice you can indicate if this relates to the items, the delivery costs (conditions) or both. You do this by selecting the correct option from the "pull down list" in the centre of the MIRO screen.
    So if you select delivery costs only, then the invoice relates directly to the condittion types on the PO for the delivery costs.
    Steve B

  • Block Invoice creation for missing condition type

    Hi,
    We need to put a chek on the Invoice process, wherein if particular condition type is missing in the relation to sales order, than the Invoice should not get created.
    For example-
    If Order A - has condition type PR00 which gets fecthed from the condition record (VK11)
    And while creating Invoice for the Order A, if someone has deleted the condition record , the invoice gets created without condition type PR00.
    Now at this step a block has to be placed which can block the invoice from being created if PR00 is missing.
    Please let me know what will be the best appraoch of IMPLEMENTING  such check and how to do that.
    Regards,
    Gaurav

    Hi Gaurav,
    first if some deletes the condition record for a paricular condtion record,then ask ur users to uopdate the prices by goin to the condition screen.
    second create a pricing procedure determination for your billing type in t code ovkk
    and in that pricing procedure just maintain the settings as per mentioned by Mr.Lakshmipathy.
    Revert if helpful
    l
    Mohit Singh

  • How to reactivate cancelled Invoice, Avoid Duplicate Manul Condition Type

    Salute!! Masters,
    I am sending detail about error, please provide solution for it.
    I shall thankful to you.
    1. How to reactivate cancelled Invoice for which Excise Invoice has been created.
    Reason is; user has created commercial Invoice first then Excise Invoice subsequently. Afterwards cancelled Commercial Invoice, by the time all detail has been posted to different department & paid Excise charges to the respective department.
    Now commercial Invoice detail is required to be maintaining at book level at factory as excise has been paid for the same.
    User canu2019t create new commercial Invoice as for this have to maintain Excise Invoice too & pay.
    2. How it is possible to restrict it ME21N Stock Transfer Order at order level only to not to allow 0 value & repeat entry for the same condition type?
    While making a stock transfer (purchase order) by ME21N from supplying plant (Factory) to other plant (depot), if user make mistake & donu2019t put value for Manual condition type ZMRP, system accept & save the order.
    Afterwards when he realizes the same or immediately come to know about not putting value & put again, system take that second line entry also & create double entry.
    When invoice come then it pick the value from first line & show in negative.
    I have triedu2026.
    a). At pricing procedure, there ZMRP is required entry.
    b). Condition Type - ZMRP, there is C No Limitations
    We can not put D Not possible to process manually or fix this condition type as then we have to maintain condition record & prices are varies depot to depot & day by day.
    c). Since this is a Header Condition, so canu2019t restrict at Access Sequence level.
    This is only has to put manually by user according to the instruction of sales department. 
    Got Suggestion to change at user exit level to put check at delivery to not to allow printing or invoicing by putting 0 value/without any value.
    Please suggest at configuration level only as itu2019s difficult to create User Exit for all requirement.
    3. PGI should not happen for forward date; user can put only either current date or back date.
    Rgds.
    Srivastav
    +91-9694096833
    Edited by: Srivastav100 on Jun 14, 2010 11:22 AM
    Edited by: Srivastav100 on Jun 14, 2010 11:24 AM

    Unsolved, Closed.

  • Invoice split with same document type

    Hi Experts,
    Kindly suggest on following issue:-
    Currently we are using two billing types ZBBL  for division 11 & ZDBL for division 12.
    Whenever we do invoice with billing type ZBBL(manual entry) with reference to delivery for 12, system gives error message i.e. ZBBL can not be processed with division 12 & vice versa.  This is OK .
    But if we do VF01 for two delivery document one with division 11 & other with division 12-billing document ZBBL(manual entry) , system splits the invoces. It create two invoices. Again its a standard process.
    So my problem is system is creating two different invoices , one for division 11 & other for 12-but with same billing type.
    How can I make setting so that if system splits into two invoices ,it should create one invoice with ZBBL & other with ZDBL.
    Please advise.
    Thanks in advance.
    Regards,
    Dharminder dalal

    There can be many reasons why your invoices with same sales area are getting split. It many based on:
    - Billing type
    - Billing date
    - Payer
    - Billing unit
    - Terms of payment
    - Incoterms
    - Letter of credit
    Further, if you want analysis, on what bases system is splitting these in invoice. Try following steps:
    - Try using Tcode VF04. Opt for delivery related billing.
    - Select the desired delivery docs in Billing due list. (Press Ctrl Key from keyboard to select multiple lines).
    - Then click on simulation button.
    - Billing Doc Simulate: Billing Doc Overview Screen
    - Select all lines.
    - There first go for Logs, by pressing Log button.
    - If log is fine then, click on Split Analysis button to get split analysis.
    For further reference on Invoice split. Refer SAP Note 11162 - Invoice split criteria in billing document
    So, how to handle this?
    Based on the split analysis amend your copying control for Delivery to Billing in TCode VTFL.
    There many be a possibility that you might need to create customized routine with help of a tech consultant to suffice your requirement.
    Also, refer link - multiple delivery but single invoice for reference/understanding.
    Then to combine the billing. Follow following steps:
    1. Use Tcode VF04. Opt for delivery related billing.
    2. Select the desired delivery docs in Billing due list. (Press Ctrl Key from keyboard to select multiple lines).
    3. Then click on Collective Billing button.
    Regards
    JP

  • Invoice split due to hierarchy type for pricing A

    Hi,
    Gurus
    The invoice are getting splited. If i see the split analysis it tells that due to hierarchy Type for pricing A.
    Guide me gurus.
    Regards
    Anand

    Hi Anand,
    >> ... any field will be there as hierarchy type for pricing A at delivery level?
    I don't think so, Deliveries in SAP have usually no pricing information. Everything (except quantities) comes from the Sales Order.
    >> I can also tell to my technical person to write one routine to not consider hierarchy type for pricing A for collecting one or
    >> more delivery in one invoice.
    >> After he wrote were i want to assign the routine in copying control? weather in header level or item level?
    You can usually change header level (VBRK) data in the item level data transfer routine.
    Before doing that and I like to to have 100% control, I would personally check the reason for the system behavior.
    Check customizing for pricing settings for sales order and billing documents involved.
    Regards,
    Franck

  • Condition Type in an Invoice for Output tax

    Hi,
    In our Invoice we have different condition types for Output tax. These are the condition types :- MWST, IDM2, ZVLT and IDM3. All thse condition tpye refer to Output tax, although only MWST holds the actual value. But there is certain setting (i guess structure ikomv) which is sending all the condtion types in the IDOC. As the remaining conditon types are not required it is further giving an Error in XI. Please tell us which is the transaction that configures these condtions  and also the required changed in our configuration.
    regards,
          Milan Thaker

    I think this can be handled by adding a filter by condition type in the distribution model. See transaction BD64.

  • Suppress condition types in Invoice

    Hi,
    I want to suppress some condition types in Invoice.
    For example Condition type PR02 should be available in the sales order, but it should be suppressed in the Invoice.
    How can i do this?
    Regards
    M. Lakshmi Narasimhan

    Hi
    I have a suggestion that determine a new Pricing Procedure in Invoice which will be copy of the Pricing Procedure which is determined in Sales Order with same Condition Type except PR02 which will not be avavilable in Pricing Procedure determined at Billing.
    To determine the new Pricing Procedure you will have to maintain  "B" as Pricing Type at Item Level in Copy Control VTFL. And also maintaon OVKK with Document pricing Procedure of your Billing Document Type.
    OR
    Write a routine for your Condition Type PR02 so that in transaction VF01 it should get suppressed.
    Regards
    Amitesh Anand

  • Adding the tax condition type after customer pays

    Hi,
    I have a strange situation.
    The customer has payed the invoice amount and evrything is cleared and the complete Order to Cash cycle is complete.
    Now my client wants to charge the customer with the tax amount (implemented later) on the invoice that is already been cleared.And that amount should as usual go to the tax G/L account. There are not many Condiiton types but just the base price condition type and tax condition type.
    I have maintained a necessary condition record for MWST.
    SAP transaction wise I am thinking to create a normal sales order of the invoice amount (Base + Tax condition type) and then complete the order to cash cycle.And once it is completed I would create a debit memo request and subsequent debit memo for the base price which would be adjusted later.
    This will solve my basic purpose of Tax amount goin to the tax account.
    This is only for few SO in the production
    Please let me know in case anyone has a better idea.

    Hi ronaldo
    You create a sales order with document type L2 ( debit process) . so you create the sales order with reference to billing . Now manually you enter the tax condition type (MWST) at the sales order level and then do billing.Make sure that in the tax condition type details you have maintained the option C "Manual entries are possible" .So that you can enter the the tax condition type manually at the sales order level.
    So some additional taxes are being charged to the payer.So he will be paying some extra taxes as he has already paid for the billing document that has been passed to FI
    Regards
    Srinath

  • Check the condition type

    hi
    there is a condition type in the name of "octroid" which is calculating in the sales order properly, now the issues is that the same octroid condition should not apper in the invoice or u can say at the time of commercial invoice so is there any way how can i make the invoice with out the condition type "octroid" . is there any kind of setting to be made in copy control
    waiting for ur reply
    regards
    subhrangshu

    Hi Subhrangshu,
    You can assign 2 different price procedure in the sales document and the billing document.
    In the second one, just take out the condition you don't want to appear.
    Another possibility would be to create a condition formula and add it in the single price procedure, so that the price condition is excluded in the billing document.
    You can take an example on the condition formula used for rebate conditions, they are only valid for billing documents, not sales order. As you want the reverse, just change the logic!
    Best Regards,
    Franck
    Freelance Logistics SAP Consultant

  • Condition Types in Price Determination Process

    Hi
    Can any one explain me about in Detail about the VARIOUS TABS that  work in the CONDITION TYPE  of PRICE DETERMINATION PROCESS
    Thanks & Regards,
    Senmani.

    hi
    hi
    control data 1 :
    Condition Class is a grouping that lets you control each condition type differently.
    For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
    Condition category (examples: tax, freight, price, cost)
    A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
    Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
    Calculation type
    Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
    The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
    Rounding rule
    The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
    Example
    In the standard rounding rule '_', values are rounded off according to business standards:
    10.454 -> 10.45 DEM
    10.455 -> 10.46 DEM
    In rounding rule 'A', values are always rounded up:
    10.459 -> 10.46 DEM
    10.451 -> 10.46 DEM
    In rounding rule 'B', values are always rounded down:
    1045.9 -> 1045 LIT
    1045.1 -> 1045 LIT
    In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
    Structure condition
    controls whether the condition type should be a duplicated condition or a cumulated condition.
    This control is only helpful when you use bill of materials or configurable materials.
    Aduplicated condition is duplicated into all assigned items.
    A cumulated condition contains the net value of all assigned items.
    control data 2 :
    promotions
    Specifies that the condition type in question is only valid for Promotions.
    Use
    Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
    Accrual (e.g. Freight)
    Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
    Use
    If you mark this indicator, the condition appears in the document as a statistical condition.
    Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
    Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
    Solution: For this reason more indicators are being set up in 4.0 for the condition type:
    'Variant condition' (KVARC)
    'Internal costing condition' (KFKIV)
    The characteristic values O and I for the condition category must no longer be used.
    For more information, see the note 93426.
    inv.list condi
    Condition for invoice list
    Marks the condition type as relevant for internal costing.
    Quantity conversion
    This field controls the quantity conversion during determination of the condition basis.
    The field is only relevant for calculation rule 'C' (quantity- dependent.
    It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
    Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
    Rounding errors can occur during quantity conversion.
    Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
    Condition for inter-company billing
    Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
    Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
    Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
    Scale :
    Scale basis indicator
    Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
    Checking rule for scale rates
    Indicates whether the scale rates must be entered in ascending or descending order.
    Scale Type
    Indicator that controls the validity of the scale value or percentage:
    From a certain quantity or value (base scale)
    Up to a certain quantity or value (to-scale)
    Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
    Formula for scale base value
    Formula for determining the scale base value.
    Use
    You can use this formula to specify calculation methods that are not provided in the standard system.
    reward points if helpful
    thanks and regards
    ravikant dewangan

  • Condition type JTX1 missing

    Hi,
    I'm practicing on home pc IDES 4.7. I have done copy client from 000 to 800 to use CIN in IDES, and now I can see the calulation procedure TAXINJ assigned to country IN which was not there before coping the client.
    I have done the customization for CIN ( yet to test ) also. But now Im getting one error while creating CMR & MMR i.e. tax condition JTX1 not defined. I can see the condition default in CMR & MMR but not classification value and while doing so in "Define tax determination rules" it is giving the error that "Condition type JTX1 is not defined for taxes" although I can see it assigned to country IN but if u click enter it will throw the error.
    So my query is that how come these conditions are missing as these are default condition type and can we create these conditions manually & if yes which access sequence should we assign to it and what are other settings for it ?
    Plz help me out I'm a SAP learner and unable to create CMR & MMR bcoz of this error.

    Hi Lakshmipathi,
    Thanks for your answer.
    I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.
    The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".
    Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?
    Thanks for your always great help,
    VL

  • Condition type EK01 missing in pricing procedure A V (error message V1206)

    Hi gurus,
    We get error message "condition type EK01 missing in pricing procedure A V" when creating a Billing request from a SErvice Order through TX-DP90.
    We reviewed customizing regarding this issue:
    ODP4 - SD Document linked to condition EK01 (this condition shall bring the actual cost in the order)
    ODP1 - Dinamyc item profile to create Billing Request.
    Pricing procedure: sales area assignments, condition types (including EK01)
    but error still shows.
    Any idea what additional setting is necessary in customizing so EK01 is transfered to the SD doc in DP90?
    Thanks,
    VL

    Hi Lakshmipathi,
    Thanks for your answer.
    I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.
    The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".
    Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?
    Thanks for your always great help,
    VL

  • Splitting Invoices according to VAT conditions

    HI All,
    We have a requirement that if a sales order has 2 materials and if one of the material is relevent for tax and the other is not then when the invoice is being created there should be seperate invoices created, any ideas?

    Hi,
    You can very well acheive this by using the split criteria in the billing document header.
    You can use some field or data in order to pass into the split criteria.
    Suppose, you have tax indicator in material master as X - taxable & Y - non taxable.
    Further you need to write a routine with the help of your ABAPer.
    For this goto tcode - VOFM - Data transfer - Billing Documents, here you write a routine as under:
    FORM DATEN_KOPIEREN_807.
    IF LIKP-VKORG = '5000'.
    TABLES :  MARC.
    DATA: BEGIN OF ZUK,
          MODUL(3) VALUE '801',
          EKGRP LIKE MARC-EKGRP,
          END OF ZUK.
    SELECT SINGLE MATNR  FROM LIPS  INTO LIPS-MATNR
               WHERE  VBELN = LIPS-VBELN
               AND   POSNR  = LIPS-POSNR.
    SELECT SINGLE  WERKS FROM LIPS  INTO LIPS-WERKS
               WHERE  VBELN = LIPS-VBELN
               AND   POSNR  = LIPS-POSNR.
    SELECT SINGLE EKGRP  FROM MARC INTO MARC-EKGRP
               WHERE MATNR = LIPS-MATNR
               AND   WERKS = LIPS-WERKS.
    IF MARC-EKGRP = 'MFG'.
    *ZUK u2013 EKGRP = MARC-EKGRP.
    VBRK-ZUKRI = MARC-EKGRP.
    CONDENSE VBRK-ZUKRI NO-GAPS.
    ENDIF.
    ENDIF.
    ENDFORM.
    you can also pass the condition type in the ZUKRI field.
    Finally you enter this routine number in copy control betn delivery & billing documents.
    This should be entered in item details in "Data VBRK / VBRP"
    Now when you create billing from delivery your invoices will be splited.
    Hope this helps you.
    Regards,
    Dhananjay

Maybe you are looking for