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.
Similar Messages
-
Duplicate condition type in sales order
hi.,
I will enter the rate for particular material in PR00.agian i will enter the rate for same material.the system will allow the two condition record in manually.
I want should not enter the seconfd time.
lakshmananhi
yes it is possible.
when u raise the sales orde double click the lin item goto CONDITION TAB
enter Ctype PR00 it values save t
regards
krishna -
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.
RavikanthHi
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 -
How to restrict header text changes in sales order level
Dear Experts,
how to restrict header text changes in sales order level change mode
thanksHello Chandu,
how to restrict header text changes in sales order level change mode
In order to restrict changes to Sales Order Header Text, the appropriate User Exit would be USEREXIT_MOVE_FIELD_TO_TVCOM_H. With the help of ABAPer, you can include the simple logic on the basis of Header Text type such that whenever any changes are incurred on the Sales Order header text, updates would be prevented.
Please try out this approach and let us know your latest observation on this issue.
Regards,
Sarthak -
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 Deshwalhi 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 -
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. -
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.
RaguRaghu,
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
Vinayhi
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 -
Restrict duplicate condition type in va01
Hello Experts.
I want to restrict user from entering duplicate condition types in tcode va01, how can I go about it?
Is there any user exit or BADI available, if yes please let me know how to go about it
Thanks in Advance...HI deven,
Check any one from the below :
Enhancement
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
SDAPO001 Activating Sourcing Subitem Quantity Propagation
V45A0001 Determine alternative materials for product selection
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45P0001 SD customer function for cross-company code sales
V45L0001 SD component supplier processing (customer enhancements)
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45E0001 Update the purchase order from the sales order
Business Add-in
BADI_SD_SCH_GETWAGFZ Scheduling Agreement: Read WAGFZ from S073
Regards
Abhii -
How to update the condition price in sales order while creating the invoice
Hi,
How to update the condition price in the sales order to carry out the new price while creating the invoice?
While creating the invoice it should update the condition price in sales order.
Thanks,
BalaramNo, pricing is not there in delivery.
I found an exit for VF01transaction where we can update the price in order.
Can you please tell me how to update the price if I have the order, material numbers and conditions number?
Thanks,
Balaram -
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.
ThanksIf 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. -
How to get pricing conditions while creating Sales Order
Hi Guys,
When we create sales order using VA01, price is automatically determined using pricing condition configured.
My requirement is, I need to know what would be the price of a particular item.Say i put one item A with quantity x,can I get which price conditions will be applied and what value will come for them.I need this because I need to validate this price with some other price put in a file .I would suggest to use the Exit because that will be less efforts and you can implment and debug it easily. Moreover, you can restrict it by any condition e.g. order type, order reason because all the internal tables are available at that point.
Whereas, accessing the access sequence is cumbersome process. You need to go to all the combinations (tables) in the access sequcen and try to find out the suitable match .
Regards,
Naimesh Patel -
Discount Condition type in sales order screen
Hi Experts,
I have a requirement like ,While the creation of Sales order ,we need to add discount for each line item on the main sales order screen ,for that i need an extra field near to order quantity field,and it must be updated at the pricing procedure too for the corresponding line item.Please show me some light on how i can accomplish this.
Thank you all in advanceHanumant,
In the sales order screen and in at the top - right corner of item details screen there is "Configuration" tab click it, it is using standard settings we can create customised setting too. Similarly we have under the conditions tab you can ask your ABAPer to check through th screen and create new one.
The price condiion type is picking from structure KOMV - KSCHL for condition type you can add fields just check with your Abaper.
Regards
Sathya
Maybe you are looking for
-
First off, my computer had to be wiped clean back in early January. All my programs was gone and that included my CS6 program. So I re-installed them. Then one day, I see this Adobe update and it had the Adobe Creative Cloud App. I think I did someth
-
We have a the following relationship: Application <-*> Card -> Status The star means that we have a one-to-many relationship where the Application has many cards. First we load up the application and display the card (just one for this case) with it'
-
Web-based utility will not load on new wet54g ethernet bridge
I just got a WET54g ethernet bridge to connect my bluray player to my existing network (wrt54gs router). I cannot get the setup cd to recognize the bridge connected to the laptop or the router. I thought that it would be no problem, just use web-ba
-
Solved! Go to Solution.
-
Hello, In a jdeveloper project I'm using jakarta poi (http://jakarta.apache.org/poi/) to generate microsoft excel files. The jar files are included in my project as user libraries. If I run the application in the jdeveloper environment everything wor