This website is not affiliated with, sponsored by, or approved by SAP AG.

Update Release Status on Pricing Record

Development (ABAP Development WorkBench, ABAP/4 programming)

Moderators: Snowy, thx4allthefish, YuriT, Gothmog

Update Release Status on Pricing Record

Postby sapfans_user » Mon Oct 12, 2015 9:19 am

I'm trying to get a BAPI or any other std. way to update the KFRST (release status) on a cond. rec.
Its present on the A tables, but BAPI_PRICES_CONDITIONS seems to only have KFRST at the item ti_bapicondit
Could anyone please help?
sapfans_user
 
Posts: 200
Joined: Thu Oct 05, 2006 12:50 pm

Re: Update Release Status on Pricing Record

Postby Gothmog » Mon Oct 12, 2015 10:19 am

I think this release status is usually derived from the Processing status (KONP-KBSTAT), I'm not sure if you can update it directly.
However, it's part of the key in the condition table, hence in the VARKEY field in TI_BAPICONDCT.
68 74 74 70 3a 2f 2f 74 69 6e 79 75 72 6c 2e 63 6f 6d 2f 62 64 6f 37 6d 77 67
Gothmog
 
Posts: 1943
Joined: Wed Sep 12, 2007 4:46 am
Location: Probably not home

Re: Update Release Status on Pricing Record

Postby sapfans_user » Mon Oct 12, 2015 10:42 am

Yes, it is derived from KBSTAT (and the relation can be got by SD_COND_T686E_SELECT )
So, my question would be "how do I programmatically release any blocked condition" ?
(either by updating the KBSTAT or KFRST)... I was hoping there'd be a direct BAPI or FM
sapfans_user
 
Posts: 200
Joined: Thu Oct 05, 2006 12:50 pm

Re: Update Release Status on Pricing Record

Postby sapfans_user » Mon Oct 12, 2015 10:54 am

Update: I don't see KBSTAT in any of the fields in BAPICONDCT, BAPICONDHD, BAPICONDIT
sapfans_user
 
Posts: 200
Joined: Thu Oct 05, 2006 12:50 pm

Re: Update Release Status on Pricing Record

Postby Gothmog » Tue Oct 13, 2015 4:07 am

Neither can I.
Note that this BAPI is not released (at least in the ECC6 EHP7 I'm looking at).

I've had problem when using it, especially for modifications of existing conditions.
Mainly, it didn't delimit the existing records in the condition table based on the date, leading to several simultaneously valid conidion records (and VK11/12/13 errors).
68 74 74 70 3a 2f 2f 74 69 6e 79 75 72 6c 2e 63 6f 6d 2f 62 64 6f 37 6d 77 67
Gothmog
 
Posts: 1943
Joined: Wed Sep 12, 2007 4:46 am
Location: Probably not home


Return to ABAP

Who is online

Users browsing this forum: No registered users and 5 guests





This website is not affiliated with, sponsored by, or approved by SAP AG.