ABAP_to_the_Future

8
Business Object Processing Framework (BOPF)
8.2.10 Tracking Changes in BOPF Objects
One feature of the SAP system that most users (and especially auditors) love is the
fact that it’s possible to get a complete history of who changed the value in data
fields, both in master data and tran sactional data. This is called the change document
mechanism. Thanks to this handy functionality, if someone were to change
the bank details of your largest supplier to his own personal bank account and
then change the vendor open items for that supplier to be $100 billion just before
a payment run, it would be really obvious whodunit.
Naturally, when you create business objects for custom entities like monsters, the
end users will be expecting to have an option in which they can request a list of
changes for a given monster record; using that option, up will come a list of who
changed what and when. Traditionally, when creating a DYNPRO program to create
and change a custom business object, you would create a custom change document
object using Transaction SCDO (Figure 8.30).
Figure 8.30 Creating a Change Document Object
As it turns out, you still have to do this for your BOPF object if you want to track
changes, so please go ahead, call Transaction SCDO, and make the settings shown
in Figure 8.30. You will notice that in addition to the monster header and item
tables you also need to add structure /BOFU/CDTCEXTID, which you need to add
here in order to get the external ID (monster number in this case) of the business
object to appear in the change log together with the GUID.
Then, click the Insert Entries button, followed by Save. You have in effect
clicked the Save button twice, so you might think you have created the change
342