Hello,
For new functionality development purposes we use BAPI_ACC_DOCUMENT_REV_POST in such way:
DATA wa_rev TYPE bapiacrev.
DATA lv_bus_act TYPE bapiache09-bus_act.
DATA lv_obj_type TYPE bapiacrev-obj_type.
DATA lv_obj_key TYPE bapiacrev-obj_key.
DATA lv_obj_sys TYPE bapiacrev-obj_sys.
DATA lt_return TYPE bapiret2_t.
wa_rev-obj_type = 'BKPFF'.
CONCATENATE p_belnr p_bukrs p_gjahr INTO wa_rev-obj_key_r.
wa_rev-reason_rev = '01'.
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
IMPORTING
own_logical_system = wa_rev-obj_sys
EXCEPTIONS
own_logical_system_not_defined = 1
OTHERS = 2.
lv_bus_act = 'RFBU'.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_REV_POST'
EXPORTING
reversal = wa_rev
bus_act = lv_bus_act
IMPORTING
obj_type = lv_obj_type
obj_key = lv_obj_key
obj_sys = lv_obj_sys
TABLES
return = lt_return.
The accounting interface BAPI behaves different than the online reversal transaction FB08. Table values at reversal document BKPF-STGRD, PSGLFLEXA-DRCRK are different.
After FB08: Reversal reason BKPF-STGRD = 01 filled at reversed document.
PSGLFLEXA-DRCRK = S in all reversal document line items
After BAPI: Reversal reason BKPF-STGRD = 01 filled at reversal document.
PSGLFLEXA-DRCRK = H for one line and S for another
FS10N shows incorrect amounts after BAPI: credit amount increase, but after double click at this amount, message apear MSITEM033. No line items meeting your selection criteria could be read.
We need posting method after which we will be able to rollback several postings. So "Call transaction 'FB08'" is not very
nice choise.
Dear abapers, can you suggest any problem solving method ?
Thanks in advance !
Bluesky
