Different base value reference steps for same condition type

Dear Gurus
I have a scenario where I have single pricing procedure for normal sale and Intercompany billing.
Condition type GRWR should take the base value from step 350 in standard scenario
But in Inter company billing it should take the base value from a different step.
Want to check the possible way to determine these.
Regards,
Neeraj Srivastava

In the pricing procedure, in the step that you're interested in intercompany billing put in the subtotal field the indicator "carry over value to KOMP-KZWI". Make sure that the KOMP-KZWI field that you'll choose is not used in any other step.
Then with the help of an ABAPer you should maintain a routine (Tc VOFM -> Formulas -> condition base value) that in the case of intercompany billing (if billing-type is XXX ... etc) will take the KOMP-KZWI* value that you chose previously.
Then back in the pricing procedure, assign your new routine in the field "Alternative formula for condition base value" (BasType).
Agis

Similar Messages

Duplicate BP Reference Numbers for same document type -need check on orders

Version: (2007A)
Description of requirements:
The user is allowed to create two sales orders for the same customer that have exactly the same BP Reference. When the user invoices one of them and then tries to invoice another, they are warned that there is already a document of the same type with this reference number. The problem is, they ship the goods out physically before they actually create the invoice document, so that by the time they are entering the invoice in the system, the goods have already been shipped twice, when they should only have been shipped once, If they were warned when they were adding or updating the order, then this could be prevented from happening. Same thing for vendors. Our customers would like to have the check for duplicate BP references on the purchase order as well as on the AP Invoices.
Business needs: Our Clientsu2019 customers are receiving duplicate shipments and this has a negative impact on their business relationship as it creates costly extra work and inconvenience for all.
Examples: Would like the same check that is currently on AR and AP Invoices for the same BP reference number existing already on the same document type implemented on the sales order and purchase order. When the user is adding an invoice for a BP and there is already an invoice for the BP with the same BP reference number, the user is warned and asked if they want to continue.
Current Workaround: None. As our customers often physically ship the goods before creating an invoice from the order, there are duplicate shipments and this is most inconvenient and costly to our customers as well as their customers.
Proposed solution: see above. This is a high priority item for our customers.
Sally Weinrauch,
Senior Support Analyst
Coastal Range Systems Inc.
Recipients of: SAP's Partner of the Year 2007 & 2005,
North America's Top Ten 2008, 2007 & 2006.
200 - 6400 Roberts Street, Burnaby, BC, V5G 4C9

hi,
Use SP_TransactionNotification to block sales order & purchase order from adding having duplicate bp reference number.
SAP Note 1258097 - Can the Suppliers Reference number be
made unique? activated approval procedure also for ar invoice.
It may solve problem.
Jeyakanthan

Tax value is not picked up correctly for the condition type in SO creation

Hi All,
I have a issue in Picking up Tax value correctly for the condition type in SO Creation.
Actual Issue:
When creating the sales order manually,
tax value is picked up correctly for one condition type: ISS3.
When the Sales Order is created via Idoc using the function module 'idoc_input_orders', tax value is not picked for same condition type: ISS3.
We need to find out why the value for the condition type 'ISS3' is not picked in this way!
Can anybody solve this issue!
What can be the reason which is stopping picking up tax value for condition type: ISS3 when Sales Order is created via F.M 'IDOC_INPUT_ORDERS'! While it picked up the same while creating Sales Order manuallly.
Thanks in advance.
Thanks,
Deep.

Hi All,
Can anybody give the solution for above posted issue!
Working:
When creating the sales order manually,
tax value is picked up correctly for the condition type ISS3.
Actual Issue:
When the Order is created via Idoc using the function module 'idoc_input_orders',
tax value is not picked .
I need to find out why the value for the condition type 'ISS3' is not picked.
I have debugged the issue from WE19 but upto Conditions tab it is picking up tax value but then it is becoming zero again it remains zero after saving SO.
But Manually tax value is picked up for condition type ISS3 and remains same after saving order.
I have debugged it several times fro WE19 but not able to find route cause for the issue.
What can be the issue over here!
Can anybody give me solution for the same!
Thanks in advance.
Thanks,
Deep.

Same condition type different value fields

same condition type is used for
1. sale of product
2.scrap sales
3.spares sales
condition typr (pr00) should be assigned to three diff value fields
(revenue ,scrap revenue &spares revenue) ,because they should not be summed up (need separate value)

Hi,
Can u sum up what is ur exact question/problem?

The same condition type calculates different amount !

Hi there,
On the print out of an invoice (VF03) I have realized that two different rows at the end of the invoice with the same description (Min Freight Charge) display 2x different amount of freight, once I check the condition type, on the header level, I see the same condition type (ZS..) with two different amount. Can anybody explain how can the same condition type (Min Freight Charge) be found calculating 2x different amounts
Thanks
Kami

Hi,
Check your pricing procedure at SPRO-> sales and distribution -> Basic functions -> Pricing control ->Define and assign pricing procedures ->maintain pricing procedures.
There might be two condition types used to calculate the frieght value. Each might be assigned with different routines under Alternative formula for condition base value column. I assume only one frieght condition type is needed to calculate the final value with reference to another condition type. Check the settings.
Regards

Hide values for certain condition types in Quotation Saleorder and Invoice

Hi All,
I have written code to hide values for certain condition types in LV69AFZZ,
this works fine in the ITEM LEVEL.
But for the same condition types, I could not hide the values in the HEADER LEVEL.
Unless I hide it at header level also, this is useless.
Please guide me how to do it.
Thanks & Regards
Pradeep

Hi,
We have been using FORM USEREXIT_FIELD_MODIFICATION of LV69AFZz for item level & FORM USEREXIT_FIELD_MODIFIC_KOPF of LV69AFZZ for hiding heade level conditions.
I hope this helps,
Regards
Raju chiutale.

Same Condition type with different G/L Accounts

Dear All,
Our customer wants to maintain different set of G/L accounts with the same condition types in case of Service tax.
We have three different condition types for Service taxes.
JSV4 - Service tax
JES4 - ECS on Service tax
JSE5 - SECS on Service tax
We have Two different Services
1. R & D Services
2. IT Services
For these two services, service tax condition types are common but we need different G/L Accounts for different Services.
How to achieve this?
Regards,
Mullairaja

Create two tax codes in FTXP, one for R&D Service and another one for IT Services.
Now go to OB40, select the required Transaction, say for example MWS and assign these tax codes with the required G/L Account there.
Finally, in VK11, for tax condition type, assign these tax codes and save.
Now do one sales cycle for each scenario and update the forum.
thanks
G. Lakshmipathi

Function module to change the value for pricing condition type

Hello experts,
I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
I used many function modules but none are working.
Please kindly suggest a function module that will change the value for a condition type .
I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
Thank you.
CLEAR PRCD_COND.
     SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                          KSCHL = COND_TY.
IF SY-SUBRC = 0.
*    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
*    CLEAR L_COND_CHG-KBETR.
    L_COND_CHG-STUNR = PRCD_COND-STUNR.
    L_COND_CHG-KBETR = COND_PRC.
*    L_COND_CHG-KSCHL = COND_TY.
    INSERT L_COND_CHG INTO TABLE T_COND_CHG.
L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
L_ITEM_GUID = WA_ORDERADM_I-GUID.
INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
    CALL FUNCTION 'CRM_ORDER_READ'
     EXPORTING
       IT_HEADER_GUID                    = HEAD_GUID
       IT_ITEM_GUID                      = ITEM_GUID
     IMPORTING
       ET_ORDERADM_H                     = LT_ORDERADM_H
       ET_ORDERADM_I                     = LT_ORDERADM_I
       ET_PRIDOC                         = IT_PRIDOC_RD
       ET_DOC_FLOW                       = T_DOC_FLOW
*     CHANGING
*       CV_LOG_HANDLE                     =
*     EXCEPTIONS
*       DOCUMENT_NOT_FOUND                = 1
*       ERROR_OCCURRED                    = 2
*       DOCUMENT_LOCKED                   = 3
*       NO_CHANGE_AUTHORITY               = 4
*       NO_DISPLAY_AUTHORITY              = 5
*       NO_CHANGE_ALLOWED                 = 6
*       OTHERS                            = 7
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
INSERT L_PRI_COND INTO TABLE PRI_COND.
LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
L_PRIDOC_CHG-PRIC_COND = PRI_COND.
L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
ENDLOOP.
LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
INSERT L_HEADER INTO TABLE HEADER.
ENDLOOP.
LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
INSERT L_ITEM INTO TABLE ITEM.
ENDLOOP.
L_FIELD-FIELDNAME = 'STUNR'.
INSERT L_FIELD INTO TABLE FIELD.
L_FIELD-FIELDNAME = 'KBETR'.
L_FIELD-CHANGEABLE = 'X'.
INSERT L_FIELD INTO TABLE FIELD.
L_INPUT-FIELD_NAMES = FIELD.
L_INPUT-REF_KIND = 'E'.
L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
L_INPUT-OBJECTNAME = 'PRIDOC'.
INSERT L_INPUT INTO TABLE INPUT.
    CALL FUNCTION 'CRM_ORDER_MAINTAIN'
     EXPORTING
       IT_PRIDOC                     = PRIDOC_CHG
     IMPORTING
       ET_EXCEPTION                  = EXCEPT
     CHANGING
       CT_INPUT_FIELDS               = INPUT.
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
REFRESH EXCEPT.
CALL FUNCTION 'CRM_ORDER_SAVE'
EXPORTING
    IT_OBJECTS_TO_SAVE         = HEAD_GUID
*   IV_UPDATE_TASK_LOCAL       = FALSE
*   IV_SAVE_FRAME_LOG          = FALSE
*   IV_NO_BDOC_SEND            = FALSE
*   IT_ACTIVE_SWITCH           =
IMPORTING
   ET_SAVED_OBJECTS           = SAVED
   ET_EXCEPTION               = EXCEPT
   ET_OBJECTS_NOT_SAVED       = UNSAVED
* CHANGING
*   CV_LOG_HANDLE              =
* EXCEPTIONS
*   DOCUMENT_NOT_SAVED         = 1
*   OTHERS                     = 2
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK AND WAIT.

Hi,,
To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
Alternatively u can use this function module.
CRM_STATUS_DATA_SAVE_DB
BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

Same condition type used in MM , error?

Hi ,
I am (SD) using the same condition type which is used by MM and maintained different condition records in VK11. when I created STO , MM condition value is posting right , But with relevant to STO and Del , I create billing document , here The condition records what I maintained in vk11 are missing. I have check each and every step. where could be the error exists? cant we use the same condition type used by MM , though we maintained different acceess seq and condition records in VK11?
Thank you,
Kanna Palle.

Hi,
I copied the condition type and changed the name , but its already used by MM. Its a STO process .STO to DEL to IV Billing.I maintained condition records in vk11.In the combination of plant and material , I find different field name for material (but its still named as material and the data element is different from what MM material field). Its confusing I think.
Precisely , I created access seq for plant and material , they field names are z123 and zabc. when I maintained condition records in vk11 , condition record saved in ZAAA and ZBBB fields. now at the time of Billing document , system throws an error saying, * condition record is missing * The system checks z123 and zabc for condition records , which are not there becos they are in the fields ZAAA and ZBBB.
At the time of Acc Seq creation , I tried to pick the same field which it shows in billing document.but that is not available in SD , its available only in ALLOWED FIELDS in MM. Pls Throw some light on this.
Thanks,
Kanna Palle.
Any updates on this Pls?

Authorization for discount condition type

Hi Experts
1)when create a sales order client want flexibility for discount condition type
like 10% ,15% , 20% it should not be manual and end user can choose from drop down and
2) If they want to give excess discount there should be authorization any supervisor can give excess discount
how to map this authorization to condition type
Regards

hello again, friend.
go to IMG > SD > Basic Functions > Pricing > Pricing Control > Define Cond Types... here you will find the settings for the upper and lower limits. please note that the larger discount rates would be represented by the lower limit. for surcharges, the lower rate is the lower limit.
scales in pricing allows you to set different discount/surcharge rates or fixed amounts depending on either value, quantity, weight, etc. in the same pricing condition record (using VK11 or VK31). if you look inside your condition type using V/06, you will see under sub-tab Scales if this has been set.
example: condition type Z007, with Scale 'Quantity'
you can set a discount of 2% if item quantity is from 0 to 100 pieces
you can set a discount of 3% if item quantity is from 101 to 200 pieces, and so forth...
regards and thanks.

Main Item net value showing as zero by condition type R100.

Hi Experts,
I am configured free goods, maintained condition record for exclusive free goods.
but in sales order free goods item is not populating and when i see the analysis the requirement 55 not met.
I removed the requirement 55 and i saved it.
Still in the sales order the free goods exclusive item not populating.
and i find that main Item net value showing as zero by condition type R100.
Why system showing the main item amount as zero by condition type R100?
Thanks in advance.

HI ram reddy
you have to maintain R100 requirement -55 it should be there
also Alternative Condition Base value - 28(100% discount)
check your main pricing procedure having conditon type R100 or not if it is not there then maintain
conditon record in VBN1 for NA00 check all the setting(calculation rule)
activate free goods pricing correctly(NA0001)
save it now try
Regards,
Krishna.
Edited by: kris_hna on Jul 14, 2011 11:13 AM
Edited by: kris_hna on Jul 14, 2011 11:31 AM

Receiver determination doesn't work for same IDoc type but in differentSWCV

hi guys,
we have an emergency now. Receiver determination doesn't work for same IDoc type but in different SWCV.Please check below for detail.
1. The process flow is : R/3 IDoc -> XI -> Third party system
2. In previous release R13, IDoc ORDERS05 was imported and used in XI and software component version is R13. And receiver determination was created.
3. Now, in new release R17, IDoc ORDERS05 was imported from R/3 to XI again and software component version is R17. And in R17, the receiver determination created in R13 was used for both old interface(R13) and new interface in R17.
Then we encountered the problem, both interfaces doesn't work now, even we deleted the receiver condition(In R13, IDoc ORDERS05 was sent to system A, and in R17 IDoc ORDERS05 was sent to system B, RCVPRN was used as an condition).
Does anyone encounter this problem? really need and appreciate your help.
-Eddie

information from monitor:
Status Sender Service Sender Namespace Sender Interface
reschedul XXXCLNT100 urn:sap-com:document:sap:idoc:messages ORDRSP.ORDERS05
columns for "Receiver Service","Receiver Namespace", "Receiver Interface" are blank
And then double click records in monitor, go into detail information...
Normally there's lots of setps existed, such as
Inbound Message ( CENTRAL )
Receiver Identification
Interface Determination
Receiver Grouping
Message Branch According to Receiver List
Technical Routing
Call Adapter
But now there's only one setp -
"Inbound Message ( CENTRAL )" existed, no any another setp..., and payload in inbound message looks good.
And in SMQ2, I checked the queue information, found there's an error - "An exception occurred that was not caught." No any other detail information for this error.

Authorization object for manual condition type in sale order

Hi experts
I want ask them, If exist an authorization object for manual Condition type (KOMV-KSCHL) in the sales order (VA01/VA02), that the user don' t can create neither modify the sale orden with a specific manual condition type (payment term) by stardard way.
Best regards
John Angulo

HI John,
I would be surprised to know that someone uses the Payment terms as a condition in the Pricing procedure for sales orders. The payment terms define when the customer agrees to pay, (15, 20, 45 ,....days or 5 years or 10 years....whatever it be)
this detail for what i know is in the sales order header,and ideally has nothing to do with the Item level material price conditions.
its ok, If you mean something else by payment terms.....in principle you can have a conditon type restrcited such that manual entries on the condition are not possible. this cane be done in SPRO customizing, i am sure your functional consultants would know what to do (SPRO->Sales and Distribution->Basic Function->Condition Types), in the tab "Changes that can be made" have a value that says manual Processing is not allwowed
The ABAP route mentioned above is for a different scenarion and i dont think it is necessary for your requirement

Calculation formula userexit not working for multiple condition types

Hi,
we have a problem in the CRM ISA-B2B scenario where the custom user exit is only working for single condition type.
but we need it for multiple condition types .
the value of the subtotal is not being retrieved for multiple conditions. at a time only one condition value is being retrieved and shown in the webshop - shopping basket.
for ex:
we have scenario 1 where Y001 -Freight condition type is applicable for one customer.and Y002 is applicable for another customer.
when we are trying to show the subtotal condition value in the webshop by using a single custom user exit in the pricing procedure it is only working for either of the above 2 customers depending on the VMC cache status.
is there any problem if use the single user exit for both condition types?
and if it needs to be differentiated how exactly we can do that with the same logic in the java class.
Thanks in advance,
PSR.

Hi Arshi,
below is the code:
public class ZValFormula_ZZWI1 extends ValueFormulaAdapter {
     private static String zzwi = "ZZWI1";
     private static char zzwiC = '@';
     private static UserexitLogger userexitlogger = new UserexitLogger(
     ZValFormula_ZZWI1.class);
     public BigDecimal overwriteConditionValue(IPricingItemUserExit item,
               IPricingConditionUserExit condition) {
          ICurrencyValue val = condition.getConditionValue();
          userexitlogger.writeLogDebug( "value saved for " + zzwi + " (" + zzwiC + ") = "
                    + val.getValueAsString());
          item.setSubtotal( zzwiC, val.getValue());
          return val.getValue();
hope this would give more idea to look at the problem.
Thanks,
PSR

Restrict same condition type in pricing procedure

Is there a way to restrict the condition type so that there can only be one occurrence of the same condition type in a order item?
Example:
System reads condition type ZXXX from system, then a user adds the same condition type on the same order item. I would like the system to then give a error message saying ZXXX can only occur once.
Kind regards

Hi,
As this is manual condition and the user are inputing it by themselves then you won't like to change the way the manual changes are maintained/allowed.
What you want that is user have given it once then they should not be able to input is again in the same sales order item. For this you should take help of requirement. Preapre logic that before the condition system check if there is existing condition of this type in this sales order item.
Hope it helps ..

Different base value reference steps for same condition type

Similar Messages

Maybe you are looking for