Forgot to put ZPNT (Penalty condition type) in sales order

Dear Expert,
We have created sales order and billing document has been sent to customer,after that we came to know tht we forgot to put ZPNT Condition type in sales order. Now i want to create another sales document with reference to billing document, in which only ZPNT Condition type will be appear (not other condition) and thn will create billing document with reference to new sales order so that ZPNT amount goes to the right ledger A/C......Is it the right process to solve this problem if yes thn please advise me how to fonfigure the system.
Regards
Parul Deshwal

hi Parul,
rather than doing this which is quite complecated process
saying complecated because, when u do Copy from billing to sales document all condition will appear and might be there r some mandatory conditions in pricing procedure which you can not remove.
Above all, IF your condition ZPNT value is based on some other conditions then also it will not be possible for you to calculate it correctly.
there is one more possible way by creating DEBIT NOTE with reference to sales order but again you might have to face above mentioned problems
So better you follow standard and easy method
1. Reverse the billing document if PAYMENT is not posted
2. Reverse the Delivery (if any)
3. add your condition type to sales order for line item and create it
Regards

Similar Messages

How to Avoid Duplicate Pricing Condition Types In Sales Order and Billing

Hi SAP Gurus
I have a requirement in Pricing (Sales and Distribution). We have issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
I want make them inactive duplicated Condition type in Sales order and Billing Documents.
Please advice me how to make inactive status to duplicated Condition types
Thanks in Advance.
Ravikanth

Hi
You can use Exclusion Group
You can define 2 Groups and include 1 condition type in each
and define exlusion procedure
A   Best condition between condition types
B   Best condition within the condition type
C   Best condition between the two exclusion groups
D   Exclusive
E   Least favorable within the condition type
F   Least favorable betweent the two exclusion groups
you can use Exclusive to set your condition type or as per your requirement
Regards
Jitesh

How can prevent duplication of condition types in sales order??

How can prevent duplication of condition types in sales order.
While we want Amount field Changeable by user.
Please give me solution.

Dear Rohit,
Can you explain your scenario in detail with an example or any screen shot so that we will help you in easy way ...
Regards,
C.B Reddy

About hide special condition type in sales order condition screen

Hi all,
    I have such requirement:
    Customer want to hide some condition type in sales order condition screen.
    I have tried the authrization object :V_KOND_VEA but it only controll the master data level
    and the special still show on the condition table.
    I have also find any user exit in SD module:
    USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
    But it looks like a system modification, and need the modification key.
    So, is there any solution such as enhancement or configuration to meet this requirement?
Many , thanks.

Check this thread where similar requirement was discussed
[Condition Type |Condition Type]
thanks
G. Lakshmipathi

Manual Condition type in Sales Order

Hi,
i need to enter a manual condition type in sales order which should come in % and the value should not come or it should come as zero, Is there any way to make that manual condition value as Zero in sales order.
Ragu

Raghu,
Pls check the OSS notes 392668, that will solve your problem.
The same pasted here for your reference. However, I advise you to download it and then read due to inconsistent formatting here.
Reward if this helps.
When you create documents in which the standard pricing is used to determine condition records as well as to calculate a pricing result, the display and entry of manual entries is not clear in the relevant condition screen (screen 6201 in the SAPLV69A or SAPMV61A programs for releases prior to 4.6A).
This note explains the interaction of manual entries with the attributes maintained in the pricing procedure and in Customizing of the condition type.
Other terms
KAUTO, V/06, V/08, KAEND fields, KOZGF, PRICING_CHECK, LV61AU08, XKOMV_ERGAENZEN_MANUELLE, LV61AA53, manual entries, MANU
Reason and Prerequisites
In the pricing Customizing, the following fields affect the manual entry of complete condition lines or individual condition rates:
Description        Technical name              Maintenance transaction in SD
Access sequence    KOZGF                  V/06 and V/07
'Manu'            KAUTO                  V/08
Depending on the characteristic of the mentioned fields, the pricing condition screen appears as follows:
KAUTO   | KOZGF    | Condition record existing on DB? | Result
Initial | Initial   | -                                | (1)
Initial | Existing | No                              | (2)
Initial | Existing | Yes                              | (3)
Set     | Initial   | -                                | (2)
Set     | Existing | No                              | (2)
Set     | Existing | Yes                              | (4)
Result (1)
A condition line is set for the relevant condition type [KSCHL]. The 'Condition rate' field [KBETR] does not contain a value, but is ready for input. The displayed line serves as an input help or a template for the manual entry.
Result (2)
No relevant condition line is set on the pricing condition screen, in other words, the condition type is missing.
If you enter the condition type manually without entering a condition rate in the same processing step, you get a 'template line' as described in (1).
Result (3)
A suitable condition record that exists on the database is set with amount (= normal, automatic determination).
Both the 'Condition origin' indicator [KHERK] and the 'Condition control' indicator [KSTEU] are set to 'A'.
If you create another line with this condition type and enter a condition rate not equal to zero, a line is set with this condition rate.
The 'Condition origin' indicator [KHERK] as well as the 'Condition control' indicator [KSTEU] has characteristic 'C'.
If, on the other hand, you create another line and enter a condition rate of zero (or do not enter any condition rate) and the condition record that exists on the database has a scale, the system sets the condition rate according to the achieved scale level. If zero is to be set as the condition rate even if scales exist, then use modification Note 179354. If no scale is maintained, then the system always sets zero as the condition rate.
In these cases, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] characteristic 'A'.
Result (4)
No relevant condition line is set on the condition screen, even though a condition record suitable for the access sequence exists on the database. The pricing analysis displays the message "Manual condition (Condition record exists)". If you enter the condition type manually without entering a condition rate in the same processing step, the record that exists on the database is set. If a condition record has a scale, the system sets the condition rate of the first scale level independently of the achieved scale level.
In this case, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] has characteristic 'A'.
Thus, the setting variant leading to result (4) serves to suppress the setting of automatically found condition records into a pricing result. However, you can add the maintained record to the already determined pricing result by entering the relevant condition key.

Flowing of the Condition type from Sales Order to invoice

Dear All,
I'm facing a problme in the copying the condition types from Sales order to Invoice.
The details are as mentioed below:
I have a Condition type CONC and made the Copy of the Condition typs as ZDIS.So that CONC's value will be debited and ZDIS' value will be credited in the FI..
But ALL the condition types which i have mentioed including tax and discounts condition types are copying from Sales order to invoice.Except CONC.
I have checked all the copy controls,i'm sure those are OK.Bcoz other condition types are working perfectly fine.
What could be the reason for this???
Will be any setting for on condition type level for copy controls???
Please Guide me its URGENT.
Thanks
Vinay

hi
from which condition type u have copied this CONC , can u pl elaborate more on this.
and just write what is exact scenario and whats going wrong?
in copy controls check for pricing source and pricing type.
regards
mandar

User Exit for eliminating double condition type in sales order

Sir,
In SE38, Program SAPMV45A, I am using user exit ( Userexit_pricing_prepare_tKomp ) to avoid double entry
of condition type like PR00 in sales order . But i am not getting how to write code.
Please, help me how to write code in user exit.
thanks,
Manoj.

Thanks for replay.
Sir, I want to impliment it in sales order (VA01 OR VA02 )
for pricing . Here I want to avoide double condition types like PR00, packing forwarding, frieght ....etc
in sales order pricing.
Here i want to give logic that codition type is already exit and you canot enter same condition type
again. means if condition type is already exit then system should not allowed to enter again the same condition type
in sales order pricing.
Thanks
Manoj.

Condition type in sales order - enhance extractor

Can anyone help me in enhancing field condition type for sale flow. I need to filter sales orders with condition type 'minimum order surcharge' in BI.
There is KONP table having condition type field.
Do I need to enhance VAHDR or VAITM. Please help.
Thanks

If orders are to be filtered then both Order Header (VAHDR) and Order Item (VAITM) should be enhanced.
But I'd strongly recommend not to filter out the orders at the time of extraction/loading (in info-pkg).
It is better to do the filtering in the report itself.
Hope this helps.

Manul condition type in sales order - default condition pricing unit

Hello!
Is it possible when manually adding a condtion type in a sales order item to change the default pricing unit? This works only if we have maintained the condtion type in VK11 and put the correct default pricing unit. When we manually add a condition type which is not in VK11 and enter only CnTY and Amount, then press Enter - system always come up with Per 1 kg - we want it to default come up with 1000 kg.
Please see link for furter description
http://img408.imageshack.us/img408/8318/zprkxt9.jpg

Hi Simon,
I feel the best option is to go to V/06 and against your condition type - in field ( Changes which can be made = C )
So this means even if you had condition records maintained against this condition type in VK11, you can still edit it in the Sales Order.
Now againt your condition type - condition records, maintain quantity = 1000, so the system defaults the same.
And you can make this condition type - manual and mandatory in your pricing procedure.
I think this should help.
Let me know your feedback.
Reward points if it does.
Regards
Ravi

How to restrict duplicate condition type in sales order

Hi All
Is there any standard method to restrict user for adding a particular discount condition type more than once in sales order. condition type is manual and its records are also being maitained manually.
Else would I will have to create userexit at sales order level or a routine in pricing procedure. I doubt on creating a rotuine in pricingprocedure because in pricing procedure there is already a restirction to add similar condition type more than once.
Thanks

create a routine and add this routine to the discount condition type only.

To add a new condition type in Sales order programatically

Hello,
I want to add a condition type (ZXXX) with an amount in sales order programatically.
I want to add the condition type in the item.
I am able to add the price (amount) and condition type (ZXXX) manually in the sales order through t code crmd_order.
I know it can be done though FM crm_order_maintain.
If you can give the code for the same it be very helpful.
is there any other FM do this operation?

Abilash,
Please check the following FM - CRM_ISAI_BASKET_SETITEMS_MPRIC. This FM does add pricing condition manually. Use this function module only as a template for your requirement.
Later use CRM_ORDER_MAINTAIN to update the business transaction.

Condition type in Sales Order

Hi experts,
Is there any way to limit a specific condition type can be entered by an authorized person?
i.e. A can enter condition HA00, while B cannot
Can it be set in user profile? Thanks
Points will be awarded for useful answers.

Hi,
Generally development and maintenance of condition records in VK11 is done by core team members only.
Its better to leave this authorization to them.
Still if you feel this scenario is there, you can limit the values in which the condition type can be limited, like the upper and lower limit of a particular condition type.
regards,
Siddharth.

Not able to save pricing condition type in Sales order

Hi
I have created a SO and there is a condition type pb00 that I have to enter manually. when I save it and come back and reopen the SO, the condition type vanishes. It does not give out any error and i tried different ways of updating like 'carry out new pricing', 'copy manual pricing' etc but it doesnot work. Please let me know how I can save this condition type in SO.
Thanks
Princeoflight

Hi Prince,
Go to conditons analysis and check the access sequences and what is the message it giving for this condition type.
Check it once and revert back.
Best Regards
Sri

Regarding the Discount condition type in sales order

Hi All
I have 3 key combinations in my Discount Condition Type. I have maintained records at all the 3 key combinations and all the records are relevant for a sales. In my sales order all the relevant records (all 3 records) getting displayed, but for calculation all the three discounts are considered. I do not want use exclusive concept in access sequence.
But when i use the same access sequence for Base Price, it is behaving deferrently, where whatever record is found at the last is getting considered for calculation.
Please give your valuable comments.
Your inputs are appreciated.
Thanks and Regards
Prasad

Dear Friend,
If you have specified the various Discounts under the three access Sequence .
There your pricing system condition type will have three records.
To achieve the best result you might use the requremnets routine in the access sequence determination.
But if you consider this......
Take Three discount Condition types for that matter....
Now to find out the best conditions out of conditions you can use the functionally of Condition exclusions
which you will find in the Basic Functions --> Condition Exclusions.
This methord you will not be required to maintain any routine.
regards,
SAP SD

To display condition types in sales order

Hi Gurus,
When the condition records are maintained for the condition types they are displayed in the sales order,here user has to create the condition records, without knowing the condition types he cannot create the records.
One method is creating condition records for all materials with zero amount. other than this method is there any possibility to display cond types in the sales order.
Thanks
Chetan

Dear Chetan,
Goto order - item - condtion - analysis
As soon as you have gone inside , on right side you will find overview which will give you all condition type
Now , you can decide which has to be maintained and which not required.
saravanan

Forgot to put ZPNT (Penalty condition type) in sales order

Similar Messages

Maybe you are looking for