Customer Expected price::Condition type EDI1 and EDI 2

what is the trigger point when you enter a customer expected price in a sales order
Is there any enchancement/ routine that runs when you enter customer exepected price in a sales order.

Routine 8 is used is for these condition type to compare, say, when ever the EDI1 price is is higher then expected in compare to base price. Then system will blocked the sales order.
FYI - For automatic determination of these condition type in sales order you get inbound iDoc from customer.
You use condition segment E1EDP05 under E1EDP01 for IDOC ORDERS04, price field VPREI.
As I already mention in absence of IDoc, you can manually maintain the same.
Regards
JP

Similar Messages

Condition type EDI1 and EDI2

Dear all,
we have to a requisition that we will receive confirmations of order (ORDRSP) from our suppliers in the future.
In OSS note 456127 (FAQ EDI MM) question 14 it says that prices will only overtaken in the purchase order,
if the condition types EDI1 and EDI2 are part of the calculation schema.
In our calculation schema we do not use EDI1 and EDI2 so far.
I can not find a manual that says what to do.
RM0000 does not contain these two condition types either.
In which way do we have to add EDI1 and EDI2 to our calculation schema?
Thank you for your help in advance!

Check these Schemas
RM2000 - STO scenarios
RMMP00 - Market Price Scenarios
Define Calculation Schema
In this step, you define the calculation schemas.
In the MM area, a calculation schema - a framework of steps used to calculate or determine something - is used among other things to calculate costs, prices, period-end rebates, and taxes.
Note
This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.
In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence.
In the price (or cost) determination process, the SAP System automatically determines which calculation schema is valid for a business transaction and takes into account, one after another, the condition types it contains.
Standard settings
The following calculation schemas are predefined in the standard system. You should not change these schemas.
RM0000 and RM1000
Control the price determination process in POs, quotations, and scheduling agreements.
Both calculation schemas require 2 condition types for the gross price: one for automatic price determination (standard: PB00) and one for manual maintenance (standard: PBXX).
RM0001 and RM1001
Determine which condition types you can enter in purchasing document headers with time-dependent conditions (e.g. contracts).
RM0002, RM1002
Determine which additional condition types you can enter in purchasing document items with time-dependent conditions or in the purchasing info record.
RMMP00
Defines the condition type for determining the market price which can be entered for each material.
RM2000
Controls the delivery cost determination process in stock transport orders and stock transport scheduling agreements.
Note
In the calculation schemas RM0000, RM1000, RM0001, and RM1001, the field "Subtotal" must contain the following values in the following lines:
Gross value: 9
Effective value: S
If the interim total 'S' is not set, the PO values cannot be updated in the Purchasing Information System (PURCHIS).
Actions
1. Check to what extent you can use the calculation schemas provided in the standard SAP System.
2. Create new calculation schemas by copying similar existing ones and changing them.
Enter a key (length max. six characters) for the schema you wish to create, and a descriptive text.
For each schema, specify the condition types in the order of their usage, and maintain the relevant data.

Condition type EDI1 in PO: Condition ignored (requirement 053 not fulfilled)

Hi,
I am trying to change price in condition type EDI1 of a line item, but I am getting following error:
PO has AB confirmation and GR also has been done. Still getting this error. Please suggest how to rectify this.
Thanks and Regards,
D. Krishna Bharadwaj.

Hi,
The condition types EDI1 and EDI2 are used when the vendor send the price change and is accepted automatically. Refer the note: 456127 - FAQ: Electronic Data Interchange (EDI) in purchasing Question number 14.
Regards,
AKPT

Condition Types EDI1 EDI2 For Purcahse Order

Hi All,
The vendor sends a price change(855) that can be accepted automatically. The IDoc is updated but the purchase order is not updated with the confirmed price.
I found the below from SAP Market Place
Answer:
Prerequisites for the use of the price update are:
a) Condition types EDI1 and EDI2 must be maintained in the condition schema.
b) The price transfer must be activated in the confirmation control key.
I have configured EDI1 and i can see a different Vendor Price in in INBOUND IDOC Seg E1EDP01 -VPREI AND THE 855 is posted the Application and i see the Order Ack on the PO
T-Code M/06 : Condition Type
Cond. class   B Prices
Calculat.type C Quantity
Cond.category d Confirmed purchase net price/value
Manual entries      B Automatic entry has priority
Manual entries      B Automatic entry has priority
Amount/Percent , Qty Relation ,Item Condition , Deletion check Boxes are Selected
Question 1 ) Acess Sequence is Blank
              2) PricingProc is Blank ( i believe we are using ZM000 PricingProc)
T -Code M/08
Step 90 ( Its the last Step)
Counter     0
Condition Type EDI1     Vendor Price
Print = X
Another question is
1) Do i need to do anything at Vendor Level
After getiing the 855 , if i do an analysis on Pricing ,
I see EDI1     207     Condition has been found (without condition record)
I Don't see the Vendor Price Any where in PO
I would appreciate if anyone can provide any help
Thanks
Venki
Thanks

Hi Venki,
please check the notes 109273 and 456127.
Please see also the attachment in note 456127.
Could you please check if the condition formula for net price in the
pricing schema is set to 2 in your system. Transaction M/08 ->
select pricing schema (RM0000)-> in line for net price the field
V_T683S-KOFRM (AltCTy) should be set to 2.
Note 456127 Question 23:
23. Question:
Which settings are necessary to ensure that prices are copied from the
ORDRSP to the purchase order item?
Answer:
Consider the attachment of this note. In the attachment, all steps for
standard price schema RM0000 are documented.
Regards,
Edit

Condition types EDI1 & EDI2

How are Condition types EDI1 & EDI2 used?

dear venkat
EDI1 AND EDI2 (Customer expected price):
In normal business process, business charges certain price for particular material but customer expects certain price. Customer expected price can be entered manually or through EDI (Electronic Data Interchange). Someone in the business may accept or reject customer expected price. So that system has to block the billing document by considering sales document as a incomplete one so that the document can be released by using transaction code V.25 by accepting or rejecting customer expecting price.
Condition type EDI 1 is used to compare the net price for each item whereas condition type EDI2 is used to compare the overall item value (net price * quantity)
For EDI1, calculation is = 8; for EDI2, calculation is = 8 make it as a manual/statistical.
In V/08, include EDI1 and EDI2 as last steps.
Go to VA01, raise the sales order
Go to item condition screen, now include EDI1 as 40/- and EDI2 as 40/-
Raise delivery and invoice. System block invoice
Now go to V.25 and click on release and now raise the invoice
The customer expected price is differ from the automatically determined price or value by more than the maximum difference allowed then the system will look this order as incomplete when it is saved .
The blocked sales order should be released by concern person through work list traction code: V.25
     logistics
     S d
     sales
     Information. System
     Work listV.25 release customer expected price.
Select the sales order click on release, save and exit.
rewards pls
siva

Condition type EDI1 is not populating in XKOMV for BOM Header Item

Hi All,
We have assgined EDI1 and EDI2 condition types in pricing procedure, and creating orderd through Idoc, and checking for customer expected price.
EDI1 and EDI2 are correctly populating for standard items, but NOT for BOM header item.
I checked in XKOMV and observed that EDI1 is not coming for BOM header item.
Please advise what to do.
Regards

Hi,
In case your pricing procedure is similar to standard SAP then probably you use calculation routine 8 for EDI1 and EDI2.
8 is represented by routine FV64A008. Inside this routine there is the following check:
check: komp-prsfd = 'X'.
Verify if your BOM header item category has switched on Pricing indicator (TVAP-PRSFD). If you have blank value there then this is the reason why EDI1 / EDI2 condition don't receive value in your case.
Best regards
Witek Prawecki

Reg customer expected price

Hi guru's,
In customer expected price we raise the sales order with EDI1&EDI2 condition types.we specify either price or value.we save the incomplete document.we raise the delivery and billing.billing will be blocked due to price error.autorization person in the business either release or reject it.if he reject the document wat is the status.already we delivered the goods.how do we get back from the customer?by return order or debit note.
my requirement is instead of blocking the document at billing level i want to block at delivery level.wat are requirements i need to do?
Thanks&regards,
srikanth..
[email protected]

Hi Srikanth;
This can be done using Copy Controls. As of now you are letting the system create a delivery even if the SO is incomplete. This is happening because we are not checking the incomplete status here. Pls make changes to the routine 001 in the copy control and assign it to Order requirements.
This would prevent from deliveries being created.Pls refer to VTLA t.code. This is where you need to put in the code.
Regards,
Mani

Condition type MVK0 and MVK1 in Purchase order

Hi Experts,
In my purchase order, line item for an article (material) there is a condition type MVK0 (Sales Price inc. Tax) and MVK1 ( Sales price excl tax) which appears in Red in IS-Retail server.
The pricing analysis says that the condition has been found without the condition record.
The details for condition type MVK1 is
Condition class:- Prices (B), Calc type:- C (QTY),
Condition category J ( Customer Expected price)
There is no access sequence for this condition type.
Manual entries D Not possible to process manually
The details for condition type MVK1 is
Cond. class B Prices
Calculat.type C Quantity
Cond.category W Expected sales price (including tax)
Access Sequence: Not maintained
Manual entries D Not possible to process manually
I wish to know how to populate values for these condition type.
Also could someone throw light on the condition category Wand J.
what is the importance of MVK0 & MVK1 condition types and How it is linked with SD pricing?
if we want this condition types values in PO what settings needs to be done?
Any Input is highly appreciated.
thanks in advance

How did you resolve this problem? I am currently facing the same issue.

( customer expected price)

Sap R/3 Customer expected price formula 9 is used, with stastical l entry.
system compares expected price of a line item with net price computed by system .if system net price is not with value range 0.05 customer expected price then item is blocked.
If we copy this formula & keep our own value range tolerance expected price less than equal to -50.
What shall be the outcome & with examples.

Assuming that the condition value formula-routine that you assign is coded correctly and works like the standard (#9), then status of the expected price is set to u201CBu201D when the EDI1 price is not within your specified tolerance.
Sales order item-level incompletion procedures can be configured so that such a situation renders the sales document u201Cincomplete.u201D Subsequent document processing is not possible until the expected price status is changed to u201CA Expected price correctu201D or u201CC Expected price not correct, but released.u201D
Incomplete SD documents can be processed with transaction V.02.
Transaction V.25 allows for the release of orders having invalid expected prices.
Regards,
Ken

KMANU field value download from R/3 to CRM for price Condition type

Hi
We done changes for KMANU field in R/3 - price condition type and that changes have to download from r/3 to CRM. I was tried below object adapters to update field value (R/3 u2013 table name: T685A - KMANU) from R/3 to CRM (Table :PRCC_COND_CT u2013 KMANU). Could you any one tell me how to resolve it. Its urgent plz
u2022         DNL_CUST_CNDALL
u2022         DNL_CUST_CND
u2022         DNL_CUST_PRC
u2022         DNL_CUST_FGD
u2022         DNL_CUST_PRICE
Appreciate your help...........
Regards
Sri

Hello Sri,
Ideally object DNL_CUST_CNDALL should get all changes done to customizing setting in R/3 to CRM.
Did you check the logs in txn CND_MAP_LOG_DISPLAY in CRM?
You can get some hints there, if any error has occured during the download.
Best Regards,
Shanthala Kudva.

Condition type PB00 and PBXX, coming in the same PO Item

Hi,
In the PO (created with reference to Outline Agreement), condition types PB00 and PBXX are coming in the same line item.
In the PO output, the PB00 value is also showing up and PBXX value is also showing up. User entered PBXX value as 350000 dollars which is right, however system is picking 1.2 million dollar of PB00 from outline agreement which is not intended here. As a result of that the output going to Vendor is exceeding more than 1.2 million dollar instead of 350,000 dollars. I cannot change or delete any othe condition types.THis is a production problem.
Has anyone faced this problem. I appreciate your reply in advance.
Thanks,

Well, thanks Saurav and Prabhakaran, however the problem still stays.
The contract is created for services (1 lot), so the dollar amount can vary depending upon the service rendered by the consultant.
That mean user will only enter the service amount.
Saurav, system should not copy down PB00, it should come by itself when user enters the specific amount. And it comes from contract. PBXX should only appear if there is no PB00 maintained in the contract. This is not the case. The service amount is maintained in the contract. Also, I don't think that PBXX and PB00 should come in one line item together as normal system behaviour & as a normal business process too. Moreover, it is not happeniing in the other two line items - line item 20 and line item 30 are fine. The pricing analysis shows both the conditions as found - PB00 and PBXX, so I could not take any clue from analysis too.
Prabhakaran, system is only behaving incorrectly for line item 10. It is behaving as expected (good ) for other line items and other PO's. So, we cannot touch the pricing procedure as that will affect other line items.
Regards

CIN condition type J1CV and JCDB not appearing in PO history

The 2 above mentioned condition types are appearing in PO conditions tab.
however, after GR was posted, the amount from J1CV and JCDB condition types was not showing up in the PO history tab.
and these 2 condition types did not have their statistic box ticked so by right it should be appearing.
however there's no problem with other condition types like JCV1, JECV, JEDB...etc
anyone can advice?

Hi,
Condition types J1CV and JCDB are stand for what pricing conditions?
There may be any causes for above.
Option-1----- >JCDB (IN Basic customs) is used for Basic Custom duty and this may be added to inventory account of material, so no separate entry in GR document.
Option-2----- >May be J1CV and JCDB (IN Basic customs) condition types have no value and during PO creation, this condition types may be deleted.
Option-3----- > Check J1CV and JCDB (IN Basic customs) condition types are there in MM Calculation Schema.
Regards,
Biju K

What is the difference between Condition Type PB00 and PBXX

Hallow all,
Can anybody please explain, What is the Difference between Condition type PB00 and PBXX in Materials Management Pricing?
And also please explain control or Application of both on Price determination ??
Thanks in Advance !!!!!

Hi,
PB00 condition type is used for automatic pricing in PO
PBXX condition type is used for manual pricing in PO
In Pricing access sequence play a vital role . If you need pricing automatic in the PO, you have use of Access Sequences and Schema Group of Vendor.You can see the difference in both standard condition type PB00 and PBXX, where as PB00 is assigned to Access sequence(0002)but in case of PBXX no access sequense assigned.
Regards,
Biju K

Condition type EK02 and VPRS.

Hi Everyone,
In our pricing procedure there are two condition types EK02 and VPRS at header level. The profit margin we are getting is in negative. Can any one through some light about the use of EK02 and VPRS condition types and how system picks the values for the condition type EK02 ?
Thanks
Raksha.

Hi,
VPRS condition type is a Statistical Condition Type that returns the cost price of material from material master. It is basically used for comparison purpose. If you want to add it in the pricing procedure, make sure you add it at the last i.e. after adding of all the condition types.
EK02 is also a Statistical Condition Type and used for comparison purpose.
regards,
Sagar

Condition type PB00 and PBXX

Dear Gurus,
When system pick condition type PB00 and when it picks PBXX ?
I have made one scheduling agreement having 20 line items. For some line items it has picked condition type PB00 and for rest it has picked PBXX. Why system is picking PB00 for some line items and PBXX for rest ?

Hi,
If you create an Info Record manually or automatically the gross price is entered or adopted is assigned to condition type PB00.
When PO is created with reference to a contract or a quotation a vendor`s gross price for a material is adopted from the Info Record condition. (or where appropriate from PO price history) as default value for condition type PB00.
If no valid info. record condition exists and no order price history can be found, the R/3 system is not able to suggest a price and requires the manual entry of price and a manual entry of net price. The manually entered price is assigned to the condition type PBXX.
These two condition type for the gross price must be available in the calculation schema assigned to the standard PO. In the standard system these are the condition type PO00 and PBXX. An access sequence is assigned to PB00 so that the price determination process can be carried out for this condition type. No access sequence is assigned to PBXX . PB00 must come before PBXX in the calculation schema. You can also use your own comparable condition type in place of PB00 and PBXX.
At the time a PO is created, is the system finds a condition record belonging to PB00 with valid condition, PBXX is irrelevant. PBXX is taken into account only if requirement 6 is fulfilled. Requirement 6 checks the condition exclusion indicator (KOMP-KZNEP).
Hope this lengthy answer clears your doubt(s)!!
Reetesh

Customer Expected price::Condition type EDI1 and EDI 2

Similar Messages

Maybe you are looking for