Okay. Let me try to explain the scenario.
1. I create a document A and then another document B to start with. Both will get created as master data and have status as 'DRAFT'.
2. Subsequently, I perform certain business processes on document A. Say, I create 4 records that has reference to document A. Currently, I perform some disaggregations required for those 4 records using the write back badi.
3. The disaggregated data is written to a custom infocube. At this point in time, my business requirement is that the status of the original document A which has been referenced in step 2 above should get changed from 'DRAFT' to 'POSTED'. So that the document A will be
1) Prevented from being used again for any other activity and 2) Various other reasons not relevant and hence unknown to me as of now.
-- So far, I attempted performing the disaggregation using WRITE BACK badi and it's getting saved in the cube as intended. But the status of the master data is not getting updated as POSTED. The data is not getting saved at all. I'm implementing if_uja_member_manager & if_uja_dimension_manager methods. On debugging, I found that the program is saving the record at some point in time and later marking as dirty record and reversing the changes made some where inside the standard code.
Looking forward Vadim...
Meanwhile, Work Status & BPF is certainly food for thought for me. Quick question on Work Status - Is there a limitation on the number of different statuses that could be utilized? I am yet to gain information on these and just started digging based on your input.
Thank you so much for taking your time out!