2008 Nov 15 8:26 AM
Dear all,
I'm using FM BAPI_PRICES_CONDITIONS to perform the condition update. Where the actual update is on fields "Valid to" and "Valid from".
I'm in version 4.7 and using OPERATION = '004' <--Change: Message contains changes
This is my scenario:
Existing record
Valid to = 99991231
Valid from = 20090101
Condition rec no = 0000281909
I want change the above to:
Valid to = 20201231
Valid from = 20100101
Condition rec no = 0000281909
With the above, i'm succeed the execution of the FM. But the result is out of expection. Because instead of changing Condition rec 0000281909's valid to and from date, it created a new entry in my condition table. By knowing that the "Valid to" field is part of the key field in condition table, so in technical point of view it can not match the old record and it proceed to create a new entry.
I might need your advice on how should achive the above by changing existing condition rec's "Valid to" and "Valid from" date without creating a new entry.
Your opinion is highly appreciated.
2008 Nov 15 2:11 PM
Dear all,
I'm using FM BAPI_PRICES_CONDITIONS to perform the condition update. Where the actual update is on fields "Valid to" and "Valid from".
I'm in version 4.7 and using OPERATION = '004' <--Change: Message contains changes
This is my scenario:
Existing record
Valid to = 99991231
Valid from = 20090101
Condition rec no = 0000281909
I want change the above to:
Valid to = 20201231
Valid from = 20100101
Condition rec no = 0000281909
With the above, i'm succeed the execution of the FM. But the result is out of expection. Because instead of changing Condition rec 0000281909's valid to and from date, it created a new entry in my condition table. By knowing that the "Valid to" field is part of the key field in condition table, so in technical point of view it can not match the old record and it proceed to create a new entry.
I might need your advice on how should achive the above by changing existing condition rec's "Valid to" and "Valid from" date without creating a new entry.
Your opinion is highly appreciated.
2008 Nov 15 2:11 PM
2008 Nov 15 3:39 PM
Hi Ajay,
Thanks for your reply and i've read through the url link before. Yes, we can proceed with the idea of 1st delete the existing condition and then follow by create a new one with the new validity date.
Perhaps the deletion(003) function from the FM is just only mark "X" to deletion indicator, field KONP-LOEVM_KO but NOT the physical delete. So in order to achieve physical delete we need to apply OSS note 1101523.
Am i correct? Please comment.
2008 Nov 15 6:56 PM
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |