Unable to find the source of changes in BOM tables

[Former Member]

Hi,

We have a client who updates data in their ITT1 table but sometime later the data changes on them. They suspect that our add-on is doing it, but our addon doesn't do anything like what is going on. The there are two user-defined fields involved: one is an alpha-numeric with valid values of 'Y' and 'N' with a default of 'N' and the other is an image field. The first field is set to 'Y' but later is changed to 'N'. The second field is set a file name but later it is changed to an empty string. We have other clients using the same add-on without this type of issue; this client is the only one with this issue. I think the fields are being changed via some other operation.

I've tried analyzing the AITT and ATT1 tables but they don't give the time of the day things happen. Also there is no way these tables show the source of the changes. Is there any other information that might exist in the database that would shed any more light on what is going on?

Thanks,

Mike

[Former Member]

What you may try is adding an user alert to monitor the ITT1 table changes. Create a query so that any new updates within a short period can be displayed and tied that query to user alert.

Thanks,

Gordon

[former_member201110]

Hi Mike,

If I've understood your issue correctly, there are entries in the ATT1 table that show that the value has changed but it isn't clear exactly what causes the change.

Things to check:

1) Any formatted searches on the BOM master form?

2) Anything in the SBO_SP_TransactionNotification proc that makes changes to these UDFs (strictly speaking that would be a big no-no but someone might have put something in).

What other addons or integrations are running on-site? Any chance they could be updating BOMs?

There is one bit of information in the AITT table that might help track down the issue. The DataSource field in this table will show O if the update was via the DI API and I if it was the interface.

Kind Regards,

Owen

[Former Member]

Hi Owen,

1. There are two formatted searches but only one that updates a field but the field is not the same as any of the fields here. The other one involves one of the fields here but it is just a report u2013 nothing gets updated.

2. There is added code in the SBO_SP_TransactionNotification proc, but it doesnu2019t involve the BOM object (u201866u2019).

3. There is another add-on that handles bins but bins are not relevant to BOMs. I think that this add-on uses the SBO_SP_TransactionNotification proc.

4. All the other add-ons appear to be SAPu2019s.

5. All the data source indicators are u2018Ou2019. I thought that u2018Iu2019 meant the change was due to the user updating an item on a form, but that appears not to be the case. As a test, I updated a line field on the BOM form, but the data source indicator said u2018Ou2019. So what does the u2018Iu2019 really mean then?

Thanks,

Mike