cancel
Showing results for 
Search instead for 
Did you mean: 

Change Documents Adapter for CDS-based BOPF BO Objects

former_member383742
Participant

Hello SAP Experts,

Since the transactional/master data need to be versioned against any change on it, I am wondering how this aspect is working within ABAP Programming Model for SAP Fiori Applications.

System Information:

- SAP Netweaver 7.52 SP01 with S/4HANA 1709

Having some knowledge about Change Documents Adapter for BOPF, I tried to follow the related procedure in my case, but I figure out that for CDS-based BOPF BOs I am not able to achieve that, due to different issues:

1. In the Eclipse-based BOPF Editor is not possible to add sub-nodes for the root node as Business Object Representation Node (reference BO: /BOFU/CHANGE_DOCUMENT).

2. I tried with the transaction BOBX, but here the following message was triggered: "Please use the Eclipse-based BO editor (it will replace transaction BOBX)", so no chance to edit the BOPF BO here and for me is also fine since the only BOPF editor should be the Eclipse-based BOPF Editor.

3. I tried also with the transaction /BOBF/CONF_UI (I know is only for SAP internal use, but I wanted to see what happens) -> again another message: "Display mode only (Business Object is generated from CDS View)".

Does anyone have any idea how to deal with change documents for CDS-based BOPF BOs within the ABAP Programming Model for S/4HANA?

Moreover, as far as I know the function modules which are generated by the change document object (transaction SCDO) is a V2 function module with delayed start and to my knowledge such V2 function modules are not allowed within S/4HANA since affects the Ensure Zero Redundancy in Application Data rule.

Thanks in advance,
Catalin

Accepted Solutions (0)

Answers (2)

Answers (2)

custodio_deoliveira
Active Contributor

Hi chiuaru.catalin,

If you are still facing this issue, try to create the CD object and then linking it to your CDS Business Object via config table /BOFU/I_OBM_CDO.

I know those are the steps on the procedure you listed above, missing the node/association to your CDS BO, but I was facing the same issue and it worked here .

Cheers,

Custodio

0 Kudos

Hi Catalin,

I am looking for the same solution, did you get the answer for this?

Regards,

Gayatri