on 05-09-2016 1:59 PM
Hello,
We use few text values from batch characteristics in pricing determination. When creating pricing condition records for these, we are facing issues as system is not determining prices when the condition record is maintained in 'Mixed Case' and batch characteristic value is in 'UPPER CASE'.
for example batch value is "KAVERI", but the price is maintained for "Kaveri".
Is there any way to make the pricing determination to be 'not case sensitive' ?
Regards,
Tony.
Hi Tony,
In characteristic master data, is Case Sensitive checkbox ticked? If you tick this field, you will be able to enter both uppercase and lowercase values for this char.
How is your pricing table structured? Can you show access sequence field assignments? Additionally, how do you move batch char values to structure tkomp?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kıvanç,
The material characteristic is always entered in Uppercase.
The pricing table is where we have the issue. The access i have an issue with has "Plant\MaterialCharacteristic"
The material characteristic field is where we have an issue.
The values are provided during pricing using the userexit USEREXIT_PRICING_PREPARE_TKOMP in RF60AFZZ
Regards,
Tony.
,
User | Count |
---|---|
98 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.