Duplicate pricing conditions printed in the invoice

The values returned in the table parameter "TKOMVD" of the function module "'RV_PRICE_PRINT_HEAD"used in the program RVADIN01, causing some duplicate pricing conditions in the script printing.
Also this table parameter is not always returning the same set of values. Only at the first time print of the invoice (via the job schedule of the program RSNAST00) this parameter is filled with some values, so when i reprint the invoice via VF03, it prints fine.
I searched some notes to resolve the problem. But in the below mentioned note it says that, it is the standard behaviour of the function module. But if it is the standard behavior, then the function module should return the same set of values always. (I am working on SAP 4.7)
(Note Number : 68057
Symptoms:
If conditions are revealed in the totals block for order confirmations or billing documents, conditions are only accumulated if the condition rate or the condition percentage rate is identical.
Example : Billing document with            Item      Condition    Condition rate
           10        PR00         100
           20        PR00          10
           30        PR00         100
If condition PR00 is printed in the totals block, the following two lines appear :
           Price     100 per piece    200
           Price      10 per piece     10
Additional key words
Invoice printout, RVADOR01, RVADIN01
Cause and prerequisites
Standard behavior
Solution
To achieve a summarization of conditions with identical condition keys but with different condition rates or condition percentage rates, you can change the standard behavior by using a user exit as described below.)

Hi..
If you are talking about proforma invoice that needs to be printed and is required to be changed.Then i would suggest you to look at one of the output type for the std proforma invoice FUPI has aprogram linked to it RVADAUS1 that determines the output with print parameters fetching from NAST table.
You can devlope the log or can incorporate the new requirements you wanted to be changed
Just check if this is the thing you are looking or let me have more clarity from you about your issue.
Thanks
Saurabh.

Similar Messages

Pricing Conditions and how the pricing date is determined

Hi all,
Small question, i ahve some pricing conditions that use the Serives Rendered date and others that use the Pricing Date from an order, how is the condition decided on what date it uses?
Hope i have expplained this ok, if not and you need more info let me know.
Regards
Steve

Hi
There is a difference between Service Rendered Data and Pricing Date.
Normally Freight Conditions are maintained on Service Rendered Date so the freight will be picked on the basis of date on which the Actual Delivery done, whereas Pricing date is used for other conditions so that price will be based on the date on which the document created and the Pricing Date maintained in that.
In the same way there is a Billing Date which came in Invoice so price will be based on the date of Invoicing.
If you maintain the record in VK11 and test a cycle you will be able to find the difference easily.
Regards
Amitesh

SUPPLEMENT DESCRIPTION OF MATERIAL - printed on the invoice and sales docum

Hi,
Exists in the master materil some field where we can include complement the description to be printed on the invoice and sales document?

Hi
You can use this Function Module GET_SERNOS_OF_DOCUMENT can be used to retrieve serial numbers corresponding to any of the following documents.
   1. Delivery
   2. Sales order
   3. Material document
Input parameters which needs to be passed changes based on the type of document.
Following are required fields to be passed as input parameters to get respective document serial numbers
1. Delivery
KEYDATA-TASER = 'SER01'
KEYDATA-LIEF_NR - delivery number
KEYDATA-POSNR   - delivery item number(optional)
After getting the output you can get it print on the invoice
By linking LIKP-VBELN to vbrp-vgbel (delivery number)
regards
Prashanth
Edited by: Prashanth@SD on Oct 27, 2010 3:00 PM

Unable to print / preview the invoice

Hi Friends,
I am unable to print / preview the invoice output i.e in VF02 > Billing Document Tab> Issue--> print preview, there is no response from the system inspite of output being assigned.
When I tried to Check the same in VF31 T.code the message is " Message Cannot be processed: objects(s) blocked" . and the message No is " VN073"
Regds
Rajiv

Hi Rajiv,
This is an authorisation issue. Please ask your BASIS person to check your user authorisation for billing related programs. This will help you.
Award points if useful.
Regards,
Emaya

How can we make the value of pricing condition flow to the sales invoice?

At an intercompany process, we have the condition type PBXX at the purchase order. On the other hand, at the sales invoice (which is created by VF01) of the sames process, there exists the condition type PR00. The calue of the condition types PBXX and PR00 should be the same. How can we make the value of PBXX flow to the sales invoice? I can create new pricing procedures if needed. I can change the types of the pricing conditions (such as PBXX or PR00) included at the procedures (by customization) if needed. All I need is to have the value of the price at the purchase order the same with the sales invoice at the same process. The transaction codes used at this process are:
ME21N - Create purchase order
VL10D - Create delivery
VF01 - Create invoice
Thanks in advance for the answers...

Yes, i verified that the config item id in the pricing table and the cz_config_items table are the same (once we save the configuration).
The reason we have to do this is coz I have to pass additional parameters, which are item speciific (captured at confiugurator runtime session) while making a call to the pricing engine.
Hence, we are capturing some additional pricing parameters (during a runtime configurator session) in a custom table, and plan to link those to the corresponding items in the 'CZ_Pricing_Structure' table thru the config_item_id.

Duplicate pricing conditions due to contract supplements

Hi all,
 
We want our pricing conditions to appear automatically on a normal purchase order and on a purchase order with reference to contract, but they should only be on the purchase order once. We're experiencing difficulties since the condition is fetched and displayed twice (once coming from the condition supplement via the contract and a second time via the standard purchasing procedure).
 
Let me sketch the scenario.
 
We have two procedures used for purchasing: 
- procedure ZM0000 as standard purchasing procedure 
- procedure ZM000S as contract supplements procedure
 
Both procedures contain conditions ZA00, ZR01, ZR02, ZR03, ZR04, ZR05 and these conditions are not indicated as a manual condition.
 
For condition type ZA00 the pricing procedure ZM000S is defined so that condition supplements can be added in the purhcase contract. There is also an Access Sequence for this condition to prevent it from appearing twice on a purchase order with reference to a purchase contract.
 
When we create a normal purchase order, we get all conditions from the ZM0000 procedure without any problem.
But when we create a purchase order with reference to a contract with condition ZA00 and condition supplements ZR01, ZR02, ZR03, ZR04, ZR05; then we see these ZRxx condition appearing twice instead of once. 
It's displayed once coming from the ZM0000 procedure and a second time due to the ZM000S procedure.
 
I've had a look at the standard procedures, at sap notes and searched on the forums and can't find a feasible solution for this.
 
One way it is commonly solved is to make the ZRxx conditions a manual condition but that means the user will have to add these conditions manually to the purchase order. When we're talking about 50 or more conditions then it becomes a cumbersome to add all these conditions (if required) manually one by one for each purchase order that the user creates --> not feasible.
 
I guess another solution would be to create an access sequence for all ZRxx conditions based on purchase order type and then create condition records for all ZRxx conditions for the purchase documents without reference to a contract. That way the condition will be displayed once (from the condition record) on a normal purchase order and once (from the contract, since the condition record can't be found) in case of a purchase order with reference to a contract. When we're talking about 50 or more conditions and more then 2 document types, then maintaining all these condition records is quite some task --> not really feasible, not the prefered solution.
 
As an alternative to SAP standard we've found the following enhancement point in LV61AA11 where we could possibly delete the "duplicate" condition from KONV if the condition origin (KONV-KHERK) is not equal to "Condition supplement" (F) in case of purchase document type that references to a contract... but this is not the prefered solution.
 
----- 
get pricing result from database table 
ENHANCEMENT-SECTION KONV_EINLESEN_02 SPOTS ES_SAPLV61A. 
select * into table hkomv 
 from konv 
 where knumv = komk-knumv 
 order by primary key. 
END-ENHANCEMENT-SECTION. 

 
Also, it's not a feasible solution to put a requirements formula on all these ZRxx condition because we're talking about more then 50 conditions.
 
Does anyone know a solution to this problem? 
How can we make sure the condition is displayed only once? (be it on the standard purchase document or on the purchase document with reference to the contract) 
Is there a standard approach for this?
 
Thanks in advance for your time.
Edited by: Kevin Coquel on Apr 15, 2010 3:34 PM

Bernhard, 
Thank you, but as I mentioned in my starting post, this is not feasible as this is concerning over 50 conditions (some of which already have other requirements formulas). 
Using requirement routine for all is an option we want to avoid at all costs. 
It would mean we need to have edit our existing requirement routines to also include routine 15 (as you can only have one requirement routine per condition in a pricing procedure). 
 
Hardik, 
Thank you for pointing us to EXIT_SAPMM06E_013. 
Preferably we would like to solve this using SAP standard before turning to ABAP development. 
 
I'm a bit surprised not being able to find a SAP standard solution to this problem. Since it's not possible to define a different pricing procedure per purchasing document type I would expect a) there is a way to avoid duplicate conditions (coming from the contract supplements) when you're in a purchase document with reference to a contract and b) that the conditions will appear by default in a normal purchase document (instead of having to add them manually one by one when you use "Manual" in the pricing procedure).

Duplicate pricing condition records in Billing

Helllo evry one,
I have an issue with an Invoice document, Where the pricing condition records is appearing twice both at the item level and header level.
It is appearing as
Condition Type     Condition base value        Condition value
ZABC                               20.00                                       200.00
ZABC                                20.00                                      200.00
Any clue at what level is might happen and how can we avoid such issues
Regards,
Ganesh
Edited by: Tcode on Dec 15, 2009 5:56 PM

Hi,
Check Whether the CONDITION TYPE is a HEADER CONDITION
Goto V/06 and check the HEADER DISCOUNT filed is activate for the condition type, if yes then it will copy to Item also.
Please check and revert back.
regards,
santosh

Duplicate Pricing Conditions

Hi everyone,
When we create a sales order (VA01) with reference to an existing order, the pricing conditions in the document are getting duplicated.
Even forcing a pricing update (via the conditions tab) does not get rid of the duplicate condiations.
Does anyone have experience with a similar issue?
Any ideas on how to isolate where the duplicates are being generated would be appreciated.
Thanks,
- Suresh

I would check analysis from the pricing screen to see how your conditions were determined (based on what keys/tables). Another place to loock at - access sequence for your conditons, does it have multiple accesses and EXCLUSIVE checkbox non-selected ? Also, I would check requirements in the access sequence.
Do you have any code which tweaks XKOMV during order processing - it may cause problems as well.

How to access/display custom pricing condition values in the webshop (eg. o

Hello,
we are using B2B with IPC-pricing, using our own pricing conditions. Calculation of the prices works fine (can be verified when enabling the price analysis link).
Now we need to show some of these own pricing condition's values (not the ones available in the salesdocument header/item like getNetValue, getTaxValue,..) in the shopping basket (order.jsp).
How can we achieve this (eg. get the IPC to transfer these values back to the shop or read them somewhere)?
Thanks for any hint
Kind regards,
Manuel

Hi all,
We've found the solution according to the post from Rajinikanth G and Sateesh Chandra (http://scn.sap.com/thread/2046477). That will work (return any pricing information/details like custom pricing conditions, subtotal1 - 6 etc. as in pricing analysis) for order.jsp (display shopping basket), order_change.jsp and orderstatusdetail.jsp (display order), but not for confirm.jsp (order confirmation / print order).
<%@ page import="com.sap.isa.businessobject.header.HeaderSalesDocument" %>
<%@ page import="com.sap.isa.businessobject.ipc.IPCBOManager" %>
<%@ page import="com.sap.isa.core.UserSessionData" %>
<%@ page import="com.sap.spc.remote.client.object.IPCClient" %>
<%@ page import="com.sap.spc.remote.client.object.IPCDocument" %>
<%@ page import="com.sap.spc.remote.client.object.IPCException" %>
<%@ page import="com.sap.spc.remote.client.object.IPCItem" %>
<%@ page import="com.sap.spc.remote.client.object.IPCPricingCondition" %>
<%@ page import="com.sap.spc.remote.client.object.IPCPricingConditionSet" %>
<%
 String priHdrCondTxt = "";
 String priItmCondTxt = "";
 HeaderSalesDocument hsDoc = ui.header;
 UserSessionData usd = UserSessionData.getUserSessionData(request.getSession());
 IPCBOManager ibom = (IPCBOManager) usd.getBOM(IPCBOManager.NAME);
 IPCClient ipcClient= ibom.getIPCClient();
 if (ipcClient == null)
 ipcClient = ibom.createIPCClientUsingConnection(hsDoc.getIpcConnectionKey());
 ipcClient.getIPCSession().setCacheDirty(); // important to get the correct data
 ipcClient.getIPCSession().syncWithServer(); // important to get the correct data
 IPCDocument ipcDocument = ipcClient.getIPCDocument(hsDoc.getIpcDocumentId().getIdAsString()); //getIpcDocumentId: null without setCacheDirty and syncWithServer
 try{
 // Header
 priHdrCondTxt += " ------HEADER--------";
 IPCPricingConditionSet hPriCondSet = ipcDocument.getPricingConditions();
 IPCPricingCondition[] hPriCond = hPriCondSet.getPricingConditions();
 for(int i=0; i<hPriCond.length; i++)
 priHdrCondTxt += hPriCond[i].getConditionTypeName() + "(" + hPriCond[i].getDescription() + ")" + hPriCond[i].getConditionValue() + " // ";
 //Item
 IPCItem[] ipcItems = ipcDocument.getItems();
 for(int i=0; i<ipcItems.length; i++)
 priItmCondTxt += " ------ITEM--------";
 IPCPricingConditionSet iPriCondSet = ipcItems[i].getPricingConditions();
 IPCPricingCondition[] iPriCond = iPriCondSet.getPricingConditions();
 for(int x=0; x<iPriCond.length; x++)
 priItmCondTxt += iPriCond[x].getConditionTypeName() + "(" + iPriCond[x].getDescription() + ")" + iPriCond[x].getConditionValue() + " // ";
 }catch(IPCException e) {
 %>
 <%=priHdrCondTxt%> 
 <%=priItmCondTxt%>
In confirm.jsp there is no IPC-document available (<HeaderSalesDoc>.getIpcDocumentId()/getIpcConnectionKey() are null). Also BOM -> getBasket()/getOrder()/getCustomerOrder()/getQuotation() are empty. Here we've transferred the necessary pricing informations from basket to confirmation through the UserSessionData.
Set data in order.jsp:
<%
 String itemId = "Item-" + item.getProductId() + "SomeValue";
 HashMap pricesForConfirm = new HashMap();
 pricesForConfirm.put("Header-SomeValue", "Val1");
 pricesForConfirm.put(itemId, "Val2");
 UserSessionData usd = UserSessionData.getUserSessionData(request.getSession());
 usd.setAttribute("pricesForConfirm", pricesForConfirm);
%>
Show data in confirm.jsp:
<%
String itemId = "Item-" + item.getProductId() + "SomeValue";
UserSessionData usd = UserSessionData.getUserSessionData(request.getSession());
HashMap pricesForConfirm = (HashMap) usd.getAttribute("pricesForConfirm");
s2 += pricesForConfirm.get("Header-SomeValue");
s2 += pricesForConfirm.get(itemId);
%>
That whole solution does work fine also when pricing analysis is disabled in XCM. (Note that we've enabled "doItemCalls" in backendobject-config.xml according to note https://service.sap.com/sap/support/notes/1004533, but we did not use the ExtensionData-mechanism to transfer data from/to ABAP, because that would need changes on ABAP- (to fetch and fill) and Java-side (to read and display) and because we could not find/access relevant pricing information from IPC at the time the BAdI is called. Also the BAdI CRM_ISA_HDR_PRICING mentioned in the note does apply for the web catalog. We've used that to give IPC more information to calculate the netValue using additional pricing conditions for the catalog.)
We've also implemented note https://service.sap.com/sap/support/notes/892761 to show a different price (eg. grossValue) in the mini basket (total items and price in basket).
If there's a need to display a different price in the catalog, there note https://service.sap.com/sap/support/notes/1022962 could be implemented.

Irrelevant Data getting printed on the Invoice Generated

Hi SAP Billing Gurus
I have facing a printworkbench issue..i will be glad if anyone can provide me with the solution or any other help
With TCode EA40(Display Invoice) I am able to get the correct data in output in the print preview . The Process states that this data needs to be send to the spool in the form of RDI output which in turn will be sent to the application server via program by formatting it .The formatted data will be downloaded by the third party vendor for generating invoice.
My problem is that the print preview is getting generated correctly but the invoice that is printed and sent by third party vendor contains irrelevant data due to which wrong invoice is getting generated and sent.
The problem occured sometimes in the past so the Spool RDI File is not available so i am not sure if the incorrect spool file was generated and sent to the application server because the file on the application server contains that irrelevant data .
did anyone came across such a problem ..I will appreciate any help in this regard
Thanks in advance
Gaurav

Hi all My issue is resolved ..Thanks to all of the community

SRM 7.0 pricing conditions mapping to the backend system

Experts,
I am new to SRM & working in SRM 7.0. I have a serious problem in distributing the pricing conditions.
I need to distribute/map the pricing conditions in SRM 7.0 to the backend ECC system. I need step by step procedure for the same. Plz help me.

Hi,
with the help of SDN, i have done the mapping part of pricing conditions as below.
field-symbols:
 <ls_be_item> type BBPS_CTR_ITEM,
 <ls_be_cond> type BBPBAPICONDCT,
 <ls_be_cond_bapi> type BBPBAPICONDIT.
loop at ct_be_items assigning <ls_be_item>.
 if <ls_be_cond>-COND_TYPE = '0100'.
 <ls_be_cond>-COND_TYPE = 'PB00'.
 elseif <ls_be_cond>-COND_TYPE = '01CT'.
 <ls_be_cond>-COND_TYPE = 'PBXX'.
 elseif <ls_be_cond>-COND_TYPE = '01RA'.
 <ls_be_cond>-COND_TYPE = 'RB00'.
 elseif <ls_be_cond>-COND_TYPE = '01RP'.
 <ls_be_cond>-COND_TYPE = '01RP'.
 ENDIF.
 if <ls_be_cond_bapi>-COND_TYPE = '0100'.
 <ls_be_cond_bapi>-COND_TYPE = 'PB00'.
 elseif <ls_be_cond_bapi>-COND_TYPE = '01CT'.
 <ls_be_cond_bapi>-COND_TYPE = 'PBXX'.
 elseif <ls_be_cond_bapi>-COND_TYPE = '01RA'.
 <ls_be_cond_bapi>-COND_TYPE = 'RB00'.
 elseif <ls_be_cond_bapi>-COND_TYPE = '01RP'.
 <ls_be_cond_bapi>-COND_TYPE = '01RP'.
 ENDIF.
endloop.
But the problem is, when i put the external break point in the above code, its not getting triggered. Can any plz tell me how to debug the code.

Manual pricing condition to overwrite the Net price

Hi ,
We have a wrong price scenario for Russia where the Sales order was created in one month and the delivery created in next subsequent month. Delay is due to some customs clearace
Now the scenario is , we have a cost price (VPRS) which will have the cost from the material master
and based on which the net price is calculated which is 15% of the VPRS
If the VPRS is 100
Base price is 115
and the discount is 10
Net price is 105
Tad is 3% which is 108.15
Now the delivery will happen after getting the customs clearance and the material price might have changed to 120
Now due to this the user will change the price manually in the sales order on which the tax will be calculated
Let say, he will maintain the Net price as 128 after deducting the discount 10 as well
and now the tax should be calculated as 3 % on the 128
I am trying to se PN00 and PMIN condition type from standard but those condtions are de actving the remaining condition includig the tax as well
Please let me know if tere is any condtion which will just ovrwrite the netprice after the discount and TAX should be calculated on that
regards,
santosh

Hi Santosh,
Surely, you have seen them, but read these notes and related notes:
Note 1365939 - VPRS logic and Customizing settings in SD
Note 201830 - Calculation of the net price of an item
Note 547570 - FAQ: VPRS in pricing
Note 201830 will help you with some examples.
I think that the use of VOFM would be the last resort.
I hope this helps you
Regards
Eduardo

Pricing condition type and the procedure it belongs to

Hello Experts,
Pricing is found in basic function in spro.
Under this we maintain the condition types.
But how does the SAP system know for which pricing procedure a condition type belongs?
Is a condition type uniquely usable by 1 pricing procedure only?
Am i right to say the pricing procedure is set in the condition type properties screen?
Have a nice day.
regards
Tom

But how does the SAP system know for which pricing
procedure a condition type belongs?
System recognizes a condition type for which pricing procedure it belongs to, based on the document pricing procedure assignment you set in OVKK.
Is a condition type uniquely usable by 1 pricing procedure only?
No as long as the data maintained in V/06 is same, you can assign to en number of pricing procedures. For example, you cannot have a different data maintained under the tab "Control data 1" in V/06 for one scenario and another value for another scenario.
thanks
G. Lakshmipathi

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

Unit price in the Invoice not printing right value

Our customer is using RVAJUS for pricing procedure. We using ctypes, PR00, K007, ZRMS, and shipping cost condition types. No tax calculation.
However in the invoice print outs, the Unit/1000 price is the Net value for item that gets printed. Which is actually (PR00- K007)+ZRMS +SHipping cost values. My question is what configuration setting controls the value for unit/1000 on the invoice. We would want the value from PR00 to be printed on the invoice. In the pricing procedure we have X applied to Gross value, K007 and ZRMS . All of this is are item conditions.
A response will be appreciated

Hi susan
Maintain For net value feild X in your pricing procedure
Regads
Srinath

Duplicate pricing conditions printed in the invoice

Similar Messages

Maybe you are looking for