SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

Changes in installation facts

Former Member
0 Kudos

Hi experts,

I have to update one installation fact through an abap-program, but the customer requests to track the changes made on this installation fact.

Do you know if f.m. BAPI_UTILINSTALLATION_CHANFACT or ISU_INST_FACTS_UPDATE activate the changes track? Do you know any other f.m or program to achieve that?

What I need is if changes made are written also in tables CDHDR and CDPOS.

Thanks.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi David

The function ISU_INST_FACTS_UPDATE doesn't meet your requirements, because it doesn't update the applocation log tables CDHDR, CDPOS.

You can use function BAPI_UTILINSTALLATION_CHANFACT.

Personally, I'm not a big fan of BAPI functions, because the field names don't match the fieldnames of the underlying tables. You will find the function ISU_S_INSTLN_CHANGE inside, which is also used for the data migration workbench for migrating FACTS.

Also in your case you want to select all the existing information of the installation, ideally in the format used for the ISU_S_INSTLN_CHANGE (see parameters X_AUTO/X_OBJ). This can easily be done via function ISU_S_INSTLN_PROVIDE:

call function 'ISU_S_INSTLN_PROVIDE'

* Do your changes

call function 'ISU_S_INSTLN_CHANGE'

commit work.

Yep

Jürgen

View solution in original post

1 REPLY 1

Former Member
0 Kudos

Hi David

The function ISU_INST_FACTS_UPDATE doesn't meet your requirements, because it doesn't update the applocation log tables CDHDR, CDPOS.

You can use function BAPI_UTILINSTALLATION_CHANFACT.

Personally, I'm not a big fan of BAPI functions, because the field names don't match the fieldnames of the underlying tables. You will find the function ISU_S_INSTLN_CHANGE inside, which is also used for the data migration workbench for migrating FACTS.

Also in your case you want to select all the existing information of the installation, ideally in the format used for the ISU_S_INSTLN_CHANGE (see parameters X_AUTO/X_OBJ). This can easily be done via function ISU_S_INSTLN_PROVIDE:

call function 'ISU_S_INSTLN_PROVIDE'

* Do your changes

call function 'ISU_S_INSTLN_CHANGE'

commit work.

Yep

Jürgen