Posting a transaction data of 0 is not the same as deleting the transaction record. You need to remove that record, completely, from the database. This means you need to do a lite optimization using the 0 compression.
However, its not only deletion of the transaction data. You also need to ensure that the member is not referred anywhere, for example, in the BPFs.
we are creating a dummy wbs members with values and need to copy that value sto th e original once teh budget got approved .after copying the values the DUMMy wbs need to deleted.
So i am using the badi custom logic and in the ct_data making the dummy as 0 and the copying the value to th eoriginal .
then using the save method with row flag eq D and using Process method to automaticaly procedd teh dimension.
You will reuse the dummy members in the next planning cycle.
In theory you can include cube compress with zero elimination in your code but it will take significant amount of time to process. I can't recommend this approach.
LOOP AT ct_data ASSIGNING <ls_rec> . <ls_result_rec> = <ls_rec>.
READ TABLE <fs_members_result_table_cx> ASSIGNING <fs_member_attr_wa_cx> WITH KEY ('ID') = <fs_project>. IF sy-subrc EQ 0 . ASSIGN COMPONENT 'PROJECT_NEW' OF STRUCTURE <fs_member_attr_wa_cx> TO <fs_prjnew>.
IF <fs_prjnew> IS NOT INITIAL .
ASSIGN COMPONENT 'SIGNEDDATA' OF STRUCTURE <ls_result_rec> TO <fs_signeddata>. lv_value = <fs_signeddata>. CONDENSE lv_value. CLEAR <fs_signeddata>. APPEND <ls_result_rec> TO <lt_final>. for zero
<fs_signeddata> = lv_value. <fs_project> = <fs_prjnew>. APPEND <ls_result_rec> TO <lt_final>. for new value
ELSE. APPEND <ls_result_rec> TO <lt_final>.for existing value ENDIF.
I suggest that you reassign the hierarchy parent to an 'Archived WBS' node. This will separate from your WBS members from SAP, and your 'Plan / Dummy WBS' that were created only in SAP BPC.
Once this is reassigned to a new parent, users will need to refresh their master data (you can do this via the EPM Add-in under 'More' or create a button for hte user to use VBA; then they should see the amount.
If there is truely no data (your ABAP has offset / deleted the data against the member you currently plan to delete) then an administrator can delete them weekly or monthly with ease if you have a lite optimise (with zero elimination) scheduled daily.
The issue because of the BADI UJR_WRITE_BACK. I am using this badi for the same model .so when running this DM the write_back badi is executing and all the data is got refreshed.
Is ther any way to get the running DM name .so i can put the check inside the badi .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.