Condition type splits in billing

Hello, We are using condition type to charge minimum price of $20 every time we ship from an order. Sometime we ship partial instead of the full order , whenever we ship partial system splits the condition type value in half. For example, if we have order of 10 and we ship 5 system will charge $10 instead of $20 because shipment is for half. We want system to charge $20 every time we ship. Doesn't matter how many deliveries we have system should charge $20 every time we ship from the order. How to achieve this? Regards,

Hello saila
It seems your freight condition type is configured based based on qty.you can either create a new condition type for freight with Fixed amount and replace the new condition with your old freight condition from pricing procedure.
Or
You can change the configuration of existing condition type directly in v/06 change it to fixed instead of quantity. (Make sure that this condition type is not being used by any other pricing procedure)
For reporting purpose or not to impact any other business processes, I suggested you to create new condition type.
Let us know if it works, if not then please share screen shot of configuration of your condition type and pricing procedure.
Thanks
Amit

Similar Messages

SQ01 to show condition types for the Billing doc

Dear Friends,
I need to show 3 cost condition types from a invoice in SQ01
For eg
The Query has   for eg
Billing Doc     Material     Net value     ZT07     ZT08     ZT09
The ZT07/8/9 are conditiontypes
I need to link these at item level in SQ01, which tables should be linked
Please help
Kind Regards Ravi Kumar Rath

Hi Ravi
Please use the following tables for SQ01
KONV     Conditions (Transaction Data)
KONP     Conditions (Item)
VBRP   Billing Item data
T685
Regards
Srinath

Changing condition type values in Billing Doc Line Items

Hi All,
I want to change the value of condition types JLST and JCST to zero in the line items of proforma invoices. How can I do this?
Any function module or BAPI? Should I go for BDC?? I tried to find user exits. What can be the optimal way to do this?
Please help.
Thanks in Advance
- Neha.

Hi Neha,
You pass 0 (zero) to the field COND_VALUE in CONDITIONSIN table alongwith other relevant data.
And pass 'X' to the field COND_VALUE in CONDITIONSINX.
hope it helps.
saroj

Create Credit Memo referenced to Billing Document - Condition Types

Hello,
I need help on this particular situation, your help would be greatly appriciated.
I try to create a Credit Memo(VA01) with reference to the Billing Document, but I don't want to see on my Credit Memo a particular Condition Type from the Billing Document. Configuration solution or ABAP solution? and how?
What the system does now is, it copies all the Condition Types from the Billing Document to the newly created Credit Memo.
Thank you all

Hi,
Create a new pricing procedure without the condition type you donot wish to appear in the credit note. create/ use a different document pricing procedure for the credit note, do the required assignments.. this will meet the requirements
Regards,
Ajit

Why not all billing documents are posted to CO-PA for condition types?

Hello!
I have following problem.
In transaction KE4I I have configured several condition types to post for specific value fields.
For some billing types it works but for some doesn't work.
For all domestic invoices it works but for abroad invoices it doesn't work.
Billing documents for abroad invoices are also posted to CO-PA but for another value fields, not for that I expect.
Where is problem?
I am waiting for help.
Best regards
Bogdan

Hi.
In both pricing procedures there are same condition types. The only difference was check box "Condition is used for statistics".
After marking this check box it still doesn't work.
There are placed the same condition types in all billing documents (domestic and abroad) . So I am supprised that for domestic billing documents field value in CO-PA is calculated for condition types placed in KE4I.
But for abroad billing documents the same field value is not calculated for the same condition types placed in KE4I.
Where is a problem?
I need help.
Best regards
Bogdan

Billing Document Not releasing to Accounting because of Condition Type

Hi,
We have used Sales Condition Type ZSCM(Which is a statistical condition type) in Billing Documents and they are already released to Accounting.Today we have created one more Billing Document with same Condition type ZSCM.But this billing document is not getting released to Accounting?
What could be the reason? Why it was released to Accounting before with the same condition type ZSCM and why it is not getting released to Accounting this time.
I am breaking my head to find the possible reasons...kindly help me out to find the problem.
1.Billing document 90005889 - has value 64.48462- and It has only 2 Items and it was released to accounting
2.Billing document 90005729 - has value 217.87960- and It has only 21 Items and it was not released to accounting and asking to activate +/- sing in KE4I transaction for the ZSCM condition type.
Why billing document 90005889 is released for accounting and why 90005729 was not released to accounting?
Thanks
Supriya

Hi,
There can be following possible reasons fo the samed :
1. If the specific GL account is not getting any assignment to CO object.
2. Also you need to check assignment with VKOA that whichever GL is assigned as per business process of Sales (the account which is going to be credited) and all relevant settings in VKOA.
3. Pls check all substitutions and validations if any connected with that condition type and GL. Becuase sometimes it may happen that because of calling some other application (for ex. Set or substitution as generally transportation of this element happen with entire hierarchy if you add your substition in the node.) at he time of posting of billing document. This has already happen with our business scenario.
4. Also check if this sales revenue GL is assinged to any set and if that set is called through any substitution ot validation.
Pls check all these possibilities and revert.
Thanks & Regards,
Taral Patel

Tax Code in Billing Document Condition Type

Hi Experts,
We have found a below issue in our system, could you please guide me if you have any inputs:
Case1:
When a Billing document is generate for a condition type ZABC ( Discount Condition Type) which is manually entered in the order ,it has the tax code populated.
This can be seen in the condition type display in Billing document and in the accounting document generated.
I have not maintained any condition record for this condition type.
Case 2:
I have a similar condition type Z123 ( again Discount condition type) though for a different pricing procedure but for this
tax code is not populated. No condition record is maintained for this too, it is manually entered.
It can not bee seen against this condition type in Accounting document.
I have compared and check if there is any routine and also the properties of both the condition types.
Also i have checked the copy control.
When I debug it , I see that tax code is fetched from KOMV table.
My Questions:
Is KOMV table updated even if the condition type is entered manually?
From where does the tax code appear in Billing document for a condition type?
Please help me or guide me where to check on this.
Thanks for your help.
Regards,
Venkat

Hi Venkata, the tax code you see here comes from the FI setting in OB40..
however, it depends on transaction in OB40. This is what I know..it's more of an FI concept.
Can you just check if the Z123 is marked as statistical ?
Regards,
Raghu.

Debit Memo for condition type

Dear All,
We need to create a Debit memo (L2) against Regular Billing Doc.(F2).
Billing Doc F2 contains many condition types, from there we need to create Debit memo for the value of condition type (ZCT).
Pl. help us.
Regards,
Sarran

Hi Dayananda Murthy,
Thanks for your reply.
We have the following condition type in our Billing.
Base Price--ZBP
3500.00
CST 2%----ZCST
70.00
Diff CST----ZCE
437.00
Here we need a Debit memo for the value (437.00) of Condition type: Diff CST----ZCE,
this condition is statistics condition in Billing doc. How to create debit request for the same.
Pl. help us.
Regards,
Sarran

CONDITION TYPE VPRS

Dear All,
While determining the cost condition type VPRS in billing we know that it is derived from goods issue .Where do we maintain the goods issue information.
Secondly when you click on item condition detail the condition control and condition origin is defined as 'A' and 'A' respectively.
How are these values derived????.
Soliciting your valuable feedback in this regard.
Regards

Hi Sen,
Condition control- A- adjust for quantity variance. it indicates the prices for conditions can be fixed or changed into what way. For example- the pice is adjusted when you increse or decrease quantity 'A'.
Condition Origin- From where the condition originated either system determined or it is mannually.
if it's A- it is determined by automatically from system.
thanks
Hemant

Reference condition type wrt IV01 and PI01..

Hi PPL,
Can u plz explain Referrence Pricing condition wrt to the condition types :
IV01 and PI01,
Both are condition tyres pertaining Inter company ,IV01 has a Reference condition Type PI01 assigned to it.
What does it mean in the inter company scenario.Points for sure..:-)
Best Regards,
Subbz..

Hi,
PI01 condition type represents costs to Ordering company code (in other words revenue to supplying company code).
It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
Hope this provides you with your answer,
Regds,
Rupali

PI01-Condition Type

Hi Friends,
STO between two plants of different company codes.
US-Receving Company Code
India-Supplying Company Code
The scenario is like this:
Sales order is created in US.
Based on the Sales order, US will generate Purchase Order(STO) to India.
Plant(India) will transfer(VL10B/VL02N)the goods to Plant(US).
Plant(India) will raise the Intercompany invoice to Plant(US).
*Condition type IV01 is the Revenue and Cond.type VPRS is the Cost to INDIA*
****Pricing PRocedure is ICAA01***
MIGO and MIRO in US Company.
As the goods were received in US plant they will deliver the goods to the Customer in US w.r.t. Sales Order.
Then Billing to Customer in US by US Company.
**Cond. type PI01 is the Cost to the Receving Company Code(Revenue to the Supplying Company Code which is having cond.type IV01 copy of Cond.type PI01)
****Pricing Procedure is RVAAUS**
1)I want to know that if cond.type PI01 is the cost to receving co.code(US) then cond.type VPRS is?
2)In Pricing Procedure RVAAUS do we need to have Cond.type PI01 and VPRS?
with regards
Azeez.Mohd

Hi,
PI01 condition type represents costs to Ordering company code (in other words revenue to supplying company code).
It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
Hope this provides you with your answer,
Regds,
Rupali

Condition type VPRS missing in billing doc while batch split delivery.

Dear Gurus,
We are facing problem of condition type VPRS (COST) missing in billing doc while batch split delivery,
Please let us know what can be problem or cause for this,
Regards,
Sai

Hi,
Check copy controls from Delivery to blling document - VTFL is there any thing missing Header as well as item level, at what lelvel your determining the price. pricing at main item level or batch level.
Pricing should be at main item level
There will be two items 1 is main item 2. is Batch item
chek cumulate cost has checked on main item or not
and also gothrough the related Notes:
Regards,
MH

Condition Type VPRS not appearing on some billing items

Hi,
I have a discrepancy between COPA and postings on the FI account. In COPA in transaction ke4i I have assigned the SD condition type VPRS - Internal price to the COPA value field VRPRS u2013 Stock Value.
The problem arises when the outbound delivery is split on several batches. In this case the condition type VPRS does not appear on the invoice for the split billing item and the amount 0 is loaded into to the COPA filed VRPRS for this billing item instead of value that should appear in the VPRS field. And this causes discrepancies between COPA and FI.
Do you know how to solve this problem? Is it possible to make the condition type VPRS always appear on the invoice, also in case when the delivery is sent in many batches?
Best regards,
Marcin

Hi
Welcome to the confusing world of Invoice *** batch split.. The situation you are facing is due to incorrect customization of your position types in SD during billing of the batch split. Plz check note 77414
You can grossly summarize it as below -
When you have batch split - the line items in Out bound delivery and biling can be divided into 2 types HPOS and UPOS i.e. Main Line items and Sub line items.. The note describes of 3 situations.. Your SD consultant will have to decide which situation you fall in... based on that config changes have to be made in SD....
If your billing is done at HPOS level (Main Item) and not at Item splits level or Vice Versa - Then T codes VOV7 and VTFL, you have to make settings accordingly in the fields "Biling Relevance" and "Cost"..
Also, the item category of HPOS and UPOS has to be different - One has to be relevant for billing/Cost and the other not
Apart from VOV7 and VTFL, check your settings in T code 0184.. Your Item catg has to be assigned against :
Delivery Type / usage Type= CHSP/ Item category Group = "Norm"
To correct the invoices already posted, cancel them and repost after making the config changes...
Regards
Ajay M

COPA - Split of Value from condition type into different value fields

Dear All,
Customer is having several free schemes to customer the same is set up by SD and Cost of free goods is attached to One Z condition type, this flows along with Main product as characteristic. So we have Main product cost in VPRS and Scheme cost in Z Condition and there is possibility of more than one scheme cost flowing in one Z condition for single billing document. Whereas customer request is to see the each scheme cost separately in COPA. Since Value from SD will be flowing through only one condition type , it will be difficult to me to Split this in COPA. We have given a thought of having more than one condition type from SD ( one Z condition for one scheme) but this resolve our issue at hand. If we look at long term whenever customer introduces new Scheme new condition type need to be created and related COPA changes etc, Which doesn't seem to be working out.
Request Experts help in this, thanks in advance for the help.

Hi Santosh
Having a Z cond type for each scheme is preferrable.... This would address the issue with Standard SAP itself...
Reason being, if you dont do that, then you will have to maintain a mapping somewhere in a Z Table where by system would come to know of the ratio between the schemes... This will be more cumbersome to develop and maintain... Still you wanna do that, here is the logic....
Maintain the schemes in a Z Table... Where each scheme will have a scheme ID - The ratio applicable to various schemes and also the relevant value fields of COPA to be updated for each scheme....
Now, add a Custom Field to the Sales Order and while creating the SO this field needs to be updated with the scheme ID(Relevant Exit to make it mandatory MV45AFZZ / ZB).... If Scheme ID is populated, your Billing should read the Split from Z Table using Exit RV60AFZZ and Update COPA using Exit COPA0002
br, Ajay M

Pricing Condition Type should split the Value

Hello Gurus,
I am working on Billing Plan for Contracts. In the contract I enter the condition type with Rs.24000. The same net value should split in the billing plan by months for 12 months as Rs2000.00. Any inputs on this?
Regards
Venkat

Hello,
In v/06 make a new condition type for 'Monthly Value'.Eg. ZP00
Cond. class   A Discount or surcharg
Calculat.type A Percentage
maintain vk11 for ZP00 as 8.333%
In the pricing procedure , add the new condition type after main price condition as below.
STEP    CNTR CTyp         DESCRIPTION                     FROM    TO    MAN MDT             STAT
100             0     PR00     Price                                                               CHECK         CHECK
200          0     ZP00     Monthly Value     100
please check the same and revert back.
Thanks & Regards,
Hegal

Condition type splits in billing

Similar Messages

Maybe you are looking for