Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Appendix C Troubleshooting : A successfully processed record has extra rows in the database

A successfully processed record has extra rows in the database
Symptom
The adapter successfully processes a message. The data appears correctly in the database. However, there is an extra row at the child level.
Probable Cause
The adapter does not trim the extra rows at the child level. Therefore, if a record has two rows at the child level but the incoming data has one row, then one row will be updated (as long as the keys match). When the user logs into PeopleSoft the user will still see two rows. The following example illustrates this situation:
Example  Suppose a particular PRODUCT has two rows, one is effective dated with 01/01/1900, the other is effective dated with 09/24/2001. The incoming data specifies the same PRODUCT with only one child row effective dated with 09/24/2001. The data processes successfully and in the database you will see that PRODUCT with two effective dated rows.
Solution
If you want the remaining rows to be deleted, you need to issue a delete command with the keys for that row. Applying this requirement to the example above, you would specify EFFDT='01/01/1900' and set OPRN_CODE='D'.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved