on 05-03-2011 1:50 AM
We have configured the consensus finding tolerance check for date and it is working. When we create confirmation from PO worklist by changing the price and the delivery date, it goes for manual approval if the date change is outside tolerance. Once the confirmation is approved by the buyer we are getting two Idocs in SAP. One is ORDRSP-ORDERS05. This one has the new price, but does not change the price in the PO. It only creates confirmation. The other one is PORDCH-PORDCH02. This one does not have the new price. It only changes the delivery date in the PO line item. We want one single IDOC which will change price (if price is changed), change delivery date and create confirmation. is that possible? If yes, what IDOC type would that be?
Thanks for your help.
Soumen
Hi Soumen
Can you please check whether the below settings are available on ERP side
SPRO-MATERIAL MANAGEMENT-PURCHASING-CONFIRMATIONS-SET UP CONFIRMATION CONTROL
select your confiramtion control line
lets say ZICH, select the confirmation sequence on left hand side
for your order acknowledgement,XX
check the field "Price"
and give the allowed tolerance values in fileds
Permitted Price Overrun in % (Inbound EDI/SOA)
Permitted Price Shortfall in % (Inbound EDI/SOA)
Now resend the data.... it will work
ORDRSP-ORDERS05 should work this time
Best Regards
Vinod
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vinod
I checked the price box in PO confirmation and manitained a range of 10% for price change. Then I had I got a short dump while processing the ORDRSP Idoc. I implemented OSS note 1332378 to get rid of the short dump. Now the ORDRSP IDOC is posting but creates only the confirmation. The price is not getting changed. Although I see that it is checking the 10% price change tolerance as I get a warning message in the Idoc if the price chnage is more that 10%.
I noticed that the E1EDP01 segment of the IDOC is missing the line item number (POSEX) and the action field. I tried adding them manually in We19 and created a new Idoc. Still the price is not changing. The process code we are using for ORDRSP is ORDR_SUS. Is that correct?
Anything else you can think of?
Thanks or your reply.
Soumen
Hi Soumen
Please use process code ORDR
Define it for the logical system inbound parameters
ORDRSP-MESSAGE TYPE in we20 transaction
Now regarding the segment,
The data now should be visible E1EDP01 SEGMENT
FIELD -VPREI
I hope you have created approval profile,
Rule for price confirmation-01 price confirmation allowed for PO's in your SNC system and assgined the same to your business partner
Now try sending fresh data, it should work
Best REgards
Vinod
Hi Vinod,
The VPERI field is populated now with the item number and I have changed the process code to ORDR. Now the Idoc fails to process with the following error.
Confirmed price cannot be set in document conditions
Message no. ME609
Diagnosis
A condition type with condition category 'd' is not included among the
document conditions.
System Response
Procedure (system administration)
Maintain the condition types for the confirmed price and the associated
value variance in calculation schema RM0000.
Does it make any sense to you?
We have created an approval profile in SNC and assigned to the supplier (customer and product blank). We also checked the price change box for the confirmation control in ECC. The new price is coming in ORDERS05 Idoc. If I change the process code to ORDR_SUS, the Idoc gets processed but does not change the price. Only creates confirmation.
Thanks
Soumen
Hi Soumen
You need to use ORDR Process Code
Now regarding the error it makes complete sense.
Take help of MM and Finance consultant and fill out the condition types
ERP-SPRO-MM-Purchasing-Conditions-Define Price Determination Process
-Define Conditon Types
-Define Calculation Schema
like condition types
EDI1-Confirmed Price
EDI2-Value variance
And for schema RM0000 you need to add the above conditon types in control data
Best Regards
Vinod
User | Count |
---|---|
11 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.