Using SAP BusinessObjects Planning and Consolidation (BPC), version for NetWeaver and an ABAP Business Add-In (BAdI), you can implement UJR_WRITE_BACK BADI, which is an enhancement spot designed for BPC. Using this pre-process enhancement spot, you can insert your own logic to manipulate data. Inside this BAdI, you can call CL_UJO_WRITE_BACK to write back data to a different model. Further, if you have to work with a write-back that was implemented with CL_UJK_WRITE, see what problems you will face and find out how to resolve them. This article provides analysis, an architect’s view, and actual code to correct the problems.
Reading this article, you will:
- Understand the limitation of using CL_UJK_WRITE in custom ABAP logic to write back data
- Learn the problems you may have after writing data to different models while you are in a write-back Business Add-In (BAdI) of one the SAP BusinessObjects Planning and Consolidation (BPC) models and how to resolve them
UJR_WRITE_BACK is an enhancement (called a Business Add-In [BAdI]) that SAP provides as a pre-process coding block before the SAP standard program writes data into SAP BusinessObjects Planning and Consolidation (BPC) models.
SAP BusinessObjects Planning and Consolidation (BPC), version for NetWeaver, provides a Business Add-In (BAdI) to support custom logic before the standard program writes data back to BPC models. In this BAdI, you can have your own code to write data to other models. The first issue is that while CL_UJO_WRITE_BACK is the preferred class to use, some developers may choose to use CL_UJK_WRITE to do this task. There are problems and limitations using CL_UJK_WRITE. The second issue is that if in your write-back BAdI you have to call a colleague’s code in which CL_UJK_WRITE is used, it causes problems. I explain what the problems are and how to resolve them so that you have a better understanding of the architecture design of a BPC write-back.