Sales Order creation of adding new condition type to Item

Hi Expert,
The sales order has been created and need to add new condition type (Z601) to the first item(10). While adding the condition I am getting warning message like
"Item 000030 exists already; the entry will be ignored".
Where item 030 will be the last item.
I have cheked but it's a standard report SAPFV45P, we can't modify. Please let me know can we set any field in the sales order so that we wont be getting this message.
Regards,
Mahesh

Hello,
If you would like to add the Condition Type automatically for a specific Item based on some condition (Lets say, Item Category), then you can code a Pricing Routine in VOFM Transaction and it will be automatically assigned.
Thanks and Regards,
Venkat Phani Prasad Konduri

Similar Messages

Sales Order Unable to Use New Condition Tables for Tax Condition Type

Dear All,
I am currently working on SAP R/3 4.0. I have a new requirement for my tax where I need to create new condition tables other than the 4 standard SAP tables which are Customer/Material, Division/Customer, Departure Country/Destination Country, Domestic Taxes and Export Taxes. My new tables consists of Departure Country/Destination Country/Shipping Point/Tax Code. The requirement is that the tax code is based on the chosen destination country and shipping point. The problem I am facing now is that no matter what types of table I create or even I generate with reference to the standard table, the access sequence will only refer to the 4 standard SAP tables above. Even if I put my own table in the highest priority for the access sequence, the same thing happens. My sales order will only pick up date from the standard table.
I wonder if anyone encountered the same problem as me.
Kindly advise.
Thank you.
Regards,
Yvonne

Hi
Yvonne
I suggest fist check a simple thing ,whether u have successfully determined shipping point for each line item ,it is possible that just adding a line item will not trigger shipping point determination . So after u update the shipping point on line level u can rerun pricing and check agian if u r getting it .
Secondly for tax purposes I suggest Try to have Customer and material tax classification approach this allows to u have long term flexibiliy and also reduces your maintenance activity . As if u change or add number of shipping points and business changes using the sequence of shipping point ,the logic of just using shipping point will not work.
In Tax classification u cna add new condition table for each new tax category and use it in different access sequences.
This information can be passed on to FI using Different Tax code for Different combination.
I hope this helps
Regards
Mandar

Sales order Pricing for a particular condition type

Hi Folks,
I have a requirement that when i change the Shipping condition(VBAK-VSBED) in the Sales order The Pricing should be triggered and the price should be re-determined only for a particular condition type (ZFM1) . This condition type represents Freight charges.
I am trying to use user exit USEREXIT_NEW_PRICING_VBAP(include MV45AFZB) in the below fashion but the price is getting
re-determine for all the condition types. I have even tried by passing NEW_PRICING = 'H' but we have multiple condition types for freight and price would get re-determined for all these condition types. I want the price should get refreshed only for condition type ZFM1.
FORM USEREXIT_NEW_PRICING_VBAP CHANGING NEW_PRICING.
   IF VBAK-VSBED NE *VBAK-VSBED
      New_Pricing = 'B'.
   ENDIF.
ENDFORM..
So, do we have any function module which i can use to refresh only a specific condition type.
<Priority normalized by moderator>
Edited by: Vinod Kumar on Nov 3, 2011 1:35 PM

Hi
It's hardcoded. Go to include FV45PF0P_PREISFINDUNG and you can see when the userexit is called and how the report call other subroutine:
          perform userexit_new_pricing_vbap(sapmv45a)
                  changing da_pricing.
          if not da_pricing is initial.
             if da_pricing ne function_new_pricing.
                perform preisfindung using da_pricing.
             endif.
          endif.
In subroutine PREISFINDUNG is called the FM 'PRICING' with the value for DA_PRICING for CALCULATION_TYPE.
Regards
Eduardo

Get condition prices before sales order creation

Hi Experts,
I have a non-SAP system which needs price information from SAP.
As we know, in SAP after Sales order creation, the prices can be found in item condition tabs. All condition records and prices can be found.
Now, before the non-SAP system sends data to SAP for sales order creation, non-SAP needs the condition record and prices same as after sales order creation.
seems i have to write code in SAP for the logic of price determination. i assume that will be a big work.
so i'm supposing whether we can get the condition from the bapi for sales order creation. i can mask testrun = 'X', then get the conditions. but i tried creating sales order in code and found the condition - ORDER_CONDITIONS_IN is not populated.
anyone got a idea to solve this?
Thanks a lot.
Legend Lee.

Hi,
If you run the BAPI under the same conditions but without the text flag checked do you get anything returned? Are there any messages in the RETURN table?
There are a number of OSS notes on this BAPI e.g. 93091 if you search on service.sap.com. The answer may lie in the pricing configuration; that the BAPI is not designed to work how you want it to work or a parameter has not been specified correctly. You could look at FM SD_SALESDOCUMENT_CREATE and try and use that however it is not released. Unfortunately I canu2019t give you a definitive answer or solution.
Regards, David

Sales Order creation/ change date for the items

I have a unique scenario and i need to get a Report for this
A sales order is created for 4 line items.
Out of these , for 2 line items a delivery is created. I need the sales order creation date and time for these 2 items in a custom report
Now the other 2 items go in to some kind of block- Now these are released by going in the sales order VA02 and after releasing the delivery is created. Again for these two items , i need the sales order change date as after a user goes and changes the sales order to remove the block only then delivery is created for these two items
Also another scenario is the 2 line items go for back order and when we get stock at tht time system confirms the stock and then the delivery is created for these. So also for this when this change occured i need to get the date for these 2 line items
Can any one please suggest how to get this data from the scenarios?
I dont want to get the date when the delivery is created as i can get tht from the LIKP table. I need the sales order create and change dates for these.

You may be aware, any changes to a document will be recorded in CDHDR (for header changes) and CDPOS (for item changes). You can explore these two tables.
thanks
G. Lakshmipathi

Addition of Condition type in XKOMV programmatically - Sales Order creation

Hi,
I need to add a condition type ( a record with whole data like Amount etc,.) in XKOMV programmatically during a Sales order creation, so that the new condition type gets automatically saved along with other data in VA01. Please suggest the better way of doing this - through Userexits or Form routines.
Thanks in Advance,
Sirisha.
Edited by: hema Namuduri on Oct 20, 2011 5:12 PM
Edited by: hema Namuduri on Oct 20, 2011 5:13 PM

Hi E_Hinojosa / madhurao123,
I added the below code in FORM userexit_xkomv_bewerten_end ( of Include: RV61AFZB ) which will get triggered in 'Pricing' Function Module.
      FORM USEREXIT_XKOMV_BEWERTEN_END                              *
FORM userexit_xkomv_bewerten_end.
DATA: l_amt1 TYPE vbak-netwr,
            v_waerk TYPE waerk.
l_amt1 = '56000'.    " Let's say..
          READ TABLE xkomv WITH KEY kschl = 'ZF02 '.
          IF sy-subrc <> 0.
              xkomv-stunr = '012 '.
              xkomv-kschl = 'ZF02 '.
              xkomv-krech = 'B    '.
              xkomv-kwert = l_amt1.
              xkomv-kbetr = l_amt1.
              xkomv-ksteu = 'C'.
Select single waerk into v_waerk from vbak where vbeln = komp-vgbel.
              IF v_waerk <> space.
                xkomv-waers = v_waerk.
              ENDIF.
              xkomv-zaehk = 99.
              CLEAR: xkomv-kntyp,
                     xkomv-kstat,
                     xkomv-kolnr,
                     xkomv-knumh,
                     xkomv-kopos,
                     xkomv-kinak.
              xkomv-kherk = 'C'.
              xkomv-kvsl1 = 'ERL '.
              xkomv-drukz = 'X'.
              xkomv-kaend_loe = 'X'.
              xkomv-updkz = 'I'.
              APPEND xkomv. CLEAR xkomv.
              DELETE xkomv WHERE kschl = 'ZH00 ' OR kschl = 'ZF00 '.
              komp-netwr = l_amt1.
            ENDIF.
ENDFORM.                    "USEREXIT_XKOMV_BEWERTEN_END
Above is the main logic I am using, apart from other Export, Import statements etc,.The above code is getting triggered during every screen transition.
It is automatically adding condition type 'ZF02' with all values during the creation of sales orders for some contracts, but not for other contracts. I am trying to trace what is the difference in both scenarios.
Please suggest.
Regards,
Sirisha N.

Condition types in Sales order creation process

Hi Friends...
While creating the sales order with BAPI,
What is the condition type i have to pass for pricing procedure...
There many condition types for my pricing procedure, which one o have to select...
Some of them are mannual, and other reuired, which one I have to pass?
I want the information related to this condition types.., as here no SD consultant availble for me.
Sales order creation, Line item error
Thanks,
Naveen.I

Hi Friends...
Please let me know is it mandatory to give condtion type while creating the sales order...?
I am using BAPI_SALESORDER_CREATEFROMDAT2 to create my sales order...
http://www.sap-img.com/abap/bapi-salesorder-createfromdat2.htm
Thanks,
Naveen.I

Sales order - new condition type - account assignment

Hello all,
we need to create a new condition type for sales order. I know that this is the path to go in SPRO:
IMG - Sales and Distribution - Basic Functions - Pricing -Pricing Control - Define Condition type.
Also I have to assign it to a pricing procedure.
Now my question is, how can I determine an account (like a GL account) where the money goes when using this condition type? Background is, we want to create a sales order on a WBS element and there is no condition type available, so we want to create a new one. So where or how can we determine the account?
Thanks
Anne

The effect I would say is that you have to understand the business requirement in terms of how complex your account determination needs to be. For example, in current company I am with we only use two tables - C003 and C005. System looks at C003 first, if no entry it moves to C005. So, for applicable cases in C003 where we want to trump account determination in C005, we have entry that does reference account key from the line item of the condition type in the pricing procedure.
Last client I was at, we had 8 tables referenced in account determination. Very complex and specific in certain circumstances. Lots of well thought out logic in diagrams first and then the account determination in the system was completed. Revert back if you need more.
Thanks,
Jay

User Exit during Sales Order Creation - New Line Item needed

I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
I will definitely reward points for useful answers.
Clark

Hello Mahendra
The requirement is as follows :
PART 1:
Sales Order Enter:
1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check items where VRKME <> EA
2.     If VRKME = EA, go to MARM for MATNR.
3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
6.     Add a new line to VBAP for the same material with the case quantity. If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
PART 2:
Batch Job to run prior to the Delivery Due List:
1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed). Get all of the document numbers (VBELN).
2.     Go to VBEP for those document numbers to get the goods issue date for the order. There will be many records in VBEP for the same sales order. Look at all orders with a goods issue date (WADAT) of next day.
3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
4.     For customers who have more than one order in VBAK, search all line items (for all orders). If there are no duplicate materials across sales orders, do nothing.
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
5.     If there are duplicate materials, go through the same logic as in part 1. If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, Line Item Consolidation. If there is no remainder, update the qty on this item directly.
     Part 2 is relevant for order types ZOR, ZCA, ZSM
     This batch job will have to be run manually for Day Pick orders. The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
Business Justification:
The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking. This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material. In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

No accounting document generated while new condition type is added

Hi
I added a new condition type to the pricing procedure. While creating the invoice if i try giving a value to the new condition type then i get the message "No accounting document generated", but when i leave it as blank then there is no problem with the a/c docs.
I assume I haven't done the complete settings correctly. Pls help.
I am using RVAA01 as the pricing procedure for standard order.
Regards,
Sujai

Hi,
As I do not have access to your system, can not comment in details.
But if I have to add a tax codition in pricing, what I would do is :
Create a tax condition, assign it in tax procedure.
Copy it as sales pricing condition.
Assign it in pricing procedure.
Create condition record for tax condition in VK19.
Check tax code in FTXP & its assignment in OB40.
Create condition record for MWST.
I think you need to check the above configuration.
Savita

Creation of New Condition Type

Hello SAP Folks,
I have one issue related to pricing. See the case is i have to produce an extra cost in the Sales Order which is actually depended
upon the net price. This condition type is percentage based and calculation works in the following way:
Let the new condition type be Z123 and Net price be PR00.
So for year variation 1-2 year, the condition type Z123 will be 1.5 times of PR00
2-3 year, the condition type Z123 will be 2.0 times of PR00
3-5 year, the condition type Z123 will be 3.0 times of PR00
Can anyone throw light on how to configure this condition type ???
Regards,
Sarthak

Hi,
For Z123 Condition type make (V/06)
Cond. class A Discount or surcharge
Calculat.type A Percentage
Plus/minus A Positive
and all other settings are same as Discount condition Type
For making Z123 customize an Discont Condition Type (EX:K004,)
Then while creating the condition record give the percentage as 150% 1-2 yearin valid from and to date,
give the percentage as 200% 2-3 yearin valid from and to date, give the percentage as 300% 3-4 yearin valid from and to date, and save the record. (VK11)
In the pricing procedure For step z123 condition type from which you want the % that is step of PR00 should be mentioned in the FROM and TO column.(V/08)
This will result as per your requirement

Requirement of creation of new condition types and Account keys tax codes

Hi,
In what all possible scenarios will the requirement to create new Condition types and accont keys arise for the creation of new depreciation keys.
Thanks
Raja.
Edited by: Raja Gopal 345 on Aug 29, 2010 1:06 PM

Unless you use jurisdiction codes, and no external tax system, for
example with tax procedure TAXUSJ, there is no validity dates for the
condition records. You can see this differnce by comparing the tables
A003 without jurisdiction codes and A053 with jurisdiction codes. A053
contains the extra fields DATBI (key field) and DATAB. This is the
standard functionality.
Please have a look at the following part of note 418582:
" Changing past percentage rates has to be inhibited in order to avoid
database inconsistencies. For this reason, the functions which allow you
to transport time-dependent tax codes with percentage rates from the
past are not supported."

Creation of new condition type: MWST

Hi, Everyone.
I would like to ask for some help regarding this issue: Creation of new condition type: MWST with the following details:
1. For the country French Polynesia, Create a new VAT condition of 10%.
2. Create a new one called : Class : Z u2013 Designation : France : TOM corresponding to 10 % of VAT to be invoiced
and then associate this new VAT code u201CZu201D to the applicant Nr 221860
If you could provide me a step by step process on how to resolve this, it would be very much appreciated. Thank you so much.

Hello
What type of condition type you want.
It is always advisable to create a new conditon type copying a standard condition type.
For gross price condition types select PB00/PBXX
For freight charges, Copy FRA1/FRB1
Regards

Adding pricing condition type while complaint creation

Hi,
I want to add condition type , whille calim creation. I have written the Zpgm using crm_ordwer_maintian , we can do that.
But the problem is I need to put in some BADI, i tried order_Save and pricing_I badi.
But it gives dump 'maintian' bapi in the order_Save. I treid with 'multi_ow' but its not adding the condition type.
Please help me , where I need to put this code ?
Thanks,
Sushant

heyy, its working fine , some parameter missing.

Sales order creation is not possible for this notification type

Hello,
I want to create Sales Order through following menu:
Notification -- Functions - Sales order - CreateSelection of Order Type.
But I get following message:
'Sales order creation is not possible for this notification type'
The message says: No sales order type is assigned to the notification type.
But I did not find any such configuration where I can assign notification type to Sales Order document type.
Please help.
regards

Transaction OIM9
Menu Path
Customizing > Plant Maintenance and Customer Service > Maintenance and Service Processing > Maintenance and Service Notifications > Notification Creation > Notification Types > Define Order Types and Special Notification Parameters
Nomally CS (customer service) area use this function.
Regards
Luke

Sales Order creation of adding new condition type to Item

Similar Messages

Maybe you are looking for