Skip to Content

Outgoing Payment - No matching records found 'A/P Invoice' (OPCH) (ODBC -20280) [Message 131-183]

Hi Experts,

I have a problem with Outgoing Payment in SAP B1.

First, the database was marked 'Suspect' in the SQL Server. So, we tried retrieving it. Restoring to a recent backup was not an option because unknowingly the SQL scheduled backup stopped 5 months prior to the occurrence of the problem. We successfully restored the .mdf file to a separate server, and the operation continued.

When we tried printing Check Voucher (rpt format), we noticed that the header and details were not matched. I scan through the last outgoing payment made before the incident where the database went 'suspected'; and I've seen this document with no details. (Please see attached ss.)

Printing of Check Vouchers encoded before this transaction were successful. DocNums 2539, and so on has mismatched headers and details section.

I ran the queries below:

DBCC CheckDB ('database name') WITH NO_INFOMSGS, ALL_ERRORMSGS


Msg 8934, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). The high key value on page (1:3481) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (1:34653).
Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). Parent node for page (1:34653) was not encountered.
Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). Parent node for page (1:34654) was not encountered.
Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). Parent node for page (1:34655) was not encountered.
Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). Page (1:34772) is missing references from parent (unknown) and previous (page (1:50908)) nodes. Possible bad root entry in system catalog.
Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). Parent node for page (1:35337) was not encountered.
Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). Parent node for page (1:35338) was not encountered.
Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 8, partition ID 72057594313768960, alloc unit ID 72057594336706560 (type In-row data). Page (1:41962) is missing references from parent (unknown) and previous (page (1:18555)) nodes. Possible bad root entry in system catalog.
Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 2012078454, index ID 1, partition ID 72057594313310208, alloc unit ID 72057594336247808 (type In-row data). B-tree chain linkage mismatch. (1:35337)->next = (1:50640), but (1:50640)->Prev = (1:50448).
CHECKDB found 0 allocation errors and 9 consistency errors in table 'POR1' (object ID 2012078454).
CHECKDB found 0 allocation errors and 9 consistency errors in database 'LOTRIM_FINAL'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (LOTRIM_FINAL).


DBCC CHECKDB('LOTRIM_FINAL', REPAIR_REBUILD)


Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_PRIMARY'. The duplicate key value is (2714, 0).
Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_STATUS'. The duplicate key value is (O, 2714, 0).
Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_CURRENCY'. The duplicate key value is (PHP, 2714, 0).
Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_ACCOUNT'. The duplicate key value is (6-10010, 2714, 0).
Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_BASE_ENTRY'. The duplicate key value is (<NULL>, -1, <NULL>, 2714, 0).
Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_VIS_ORDER'. The duplicate key value is (2714, 0, 0).
Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_OWNER_CODE'. The duplicate key value is (1, 2714, 0).
Msg 1505, Level 16, State 1, Line 3
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.POR1' and the index name 'POR1_ITM_WHS_OQ'. The duplicate key value is (ANGLE BAR 6MM X 2 X 2 X 6M, 01, 6.000000, 2714, 0).
DBCC results for 'LOTRIM_FINAL'.

It is clear that the database has inconsistencies.

How do we fix this problem, considering we don't have the latest good backup.

Ideas would be very much appreciated.

Thank you.

Honey

error.png (48.5 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers