2015 Jul 08 11:19 PM
Hi All,
I am trying to update Cost Centers using BAPI_COSTCENTER_CHANGEMULTIPLE. It is working as expected with the fields are having values. If I change one field value to INITIAL, it is retaining the old value after the updation. The case is same with both the normal fields and the custom additional fields.
I could see that it is happening in K_COSTCTR_BAPI_CHECKMULTIPLE -----> CALL METHOD go_application->change -----------> CALL METHOD lcl_services=>make_struct_to_fvtab.
IF ( NOT p_keep_empty_fields = true AND
<source> IS INITIAL ).
CONTINUE.
ENDIF.
Here p_keep_empty_fields is always true and when the field is Initial, this condition is true and the rest of the code is skipped. Any work around is highly appreciated.
Regards,
Asha
2015 Jul 09 7:16 PM
Got the Answer - Mark the fields with initial values with '!' before calling the BAPI. The BAPI_COSTCENTER_CHANGEMULTIPLE, will make this initial.
Regards,
Asha
Hi All,
I am trying to update Cost Centers using BAPI_COSTCENTER_CHANGEMULTIPLE. It is working as expected with the fields are having values. If I change one field value to INITIAL, it is retaining the old value after the updation. The case is same with both the normal fields and the custom additional fields.
I could see that it is happening in K_COSTCTR_BAPI_CHECKMULTIPLE -----> CALL METHOD go_application->change -----------> CALL METHOD lcl_services=>make_struct_to_fvtab.
IF ( NOT p_keep_empty_fields = true AND
<source> IS INITIAL ).
CONTINUE.
ENDIF.
Here p_keep_empty_fields is always true and when the field is Initial, this condition is true and the rest of the code is skipped. Any work around is highly appreciated.
Regards,
Asha
2015 Jul 09 7:16 PM
Got the Answer - Mark the fields with initial values with '!' before calling the BAPI. The BAPI_COSTCENTER_CHANGEMULTIPLE, will make this initial.
Regards,
Asha
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |