0% found this document useful (0 votes)
75 views3 pages

Unable To Move Bill of Exchange To Different Drawer - Missing Link Between Journal Entry and Original Boe

The document describes an issue where a bill of exchange cannot be moved between drawers in SAP Business One. There is a missing link between the journal entry and original bill of exchange transaction. The document provides steps to reproduce the issue and a suggested solution which involves upgrading to a newer version and running SQL queries.

Uploaded by

Dj Esel Official
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
75 views3 pages

Unable To Move Bill of Exchange To Different Drawer - Missing Link Between Journal Entry and Original Boe

The document describes an issue where a bill of exchange cannot be moved between drawers in SAP Business One. There is a missing link between the journal entry and original bill of exchange transaction. The document provides steps to reproduce the issue and a suggested solution which involves upgrading to a newer version and running SQL queries.

Uploaded by

Dj Esel Official
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SAP Business One Notes

2497057 - Unable to Move Bill of Exchange to Different Drawer - Missing Link Between Journal Entry and Original
BoE
Component: SBO-BK-OUT-BOE (Bill of Exchange), Version: 5, Released On: 16.06.2023

Symptom
When trying to move a Bill of Exchange (BoE) for which transactions exist from one drawer to another, one of the following error messages appears:

Reconciliation amount must be less than the balance due for this transaction XXXXXX
The bill of exchange does not exist [Message 3681-8]

Also, when clicking the arrow beside Origin BT in the Journal Entry of the BoE transaction, the following error message may appear:

No matching records found  'Bill Of Exchang Transaction' (OBOT) (ODBC -2028)  [Message 131-183]

 Image/data in this SAP Note is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Reproducing the issue

Prerequisites:
You are working in a localization with the Bill of Exchange functionality available.
You have enabled Use Bill of Exchange in Administration → System Initialization → Company Details → Basic Initialization.

Scenario 1:

1. Go to Sales A/R → A/R Invoice, and create an A/R invoice for a business partner.
2. Go to Banking → Incoming Payments → Incoming Payments, and pay the A/R Invoice with the Bill of Exchange type payment means. The Bill of Exchange No. will be 2, for
example.
3. Go to Banking → Bill of Exchange → Bill of Exchange Management. Choose Transact. Type: Incoming Payments, choose OK, and create a deposit for the BoE by moving it
from the Generated drawer to the Deposited drawer. The posted Deposit No. will be 6, for example.
4. Close SAP Business One and log in again.
5. Go to Banking → Bill of Exchange → Bill of Exchange Management. Choose Transact. Type: Incoming Payments, Status: Deposited, enter Deposit No. From 6 To 6, and
choose OK.
6. Move the BoE from the Deposited drawer to the Paid drawer. The Bill of Exchange Transactions window opens. The Transaction Number will be 8 and the Journal Entry No.
2294 (example).
 

 
7. Open the Journal Entry of the BoE transaction.

Expected behavior:

The Origin No. in the Journal Entry window is matched with the BoE Transaction No.

Actual behavior:

The Origin No. (7) does not match the BoE Transaction No. (8).
When clicking the arrow beside Origin BT, the following error message appears:

No matching records found  'Bill Of Exchang Transaction' (OBOT) (ODBC -2028)  [Message 131-183]

Scenario 2:

1. Go to Banking → Bill of Exchange → Bill of Exchange Management, and choose OK in the selection criteria.
2. Go to the desired drawer, and select the BoE transactions that are to be moved to another drawer.
3. Select the dropdown in the Move To field accordingly.
4. Choose Update.

Expected behavior:

The transactions are successfully moved to the chosen drawer.

Actual behavior:

The following error message appears:

Reconciliation amount must be less than the balance due for this transaction XXXXXX

Cause
There is a missing link between a Journal Entry and the original BoE transaction. This scenario was fixed in SAP Business One version 9.2 PL09. 

Solution
Before seeking help with legacy records, complete the following steps:

1. Execute the attached sizing_check_v2.sql query in SAP HANA Studio or Microsoft SQL Server Management Studio according to the customer's current version of the
database, on the production landscape in question, on a business day during peak hours.
2. Create a full system info dump from the customer's current version of the database as per SAP Note 1732157.
3. As a prerequisite for seeking help for legacy records, upgrade the database to SAP Business One 9.3 PL14 or SAP Business One, version for SAP HANA 9.3 PL14.
Note that if the issue is present, then upgrading to SAP Business One version 10.0 is advisable only after the analysis of the records.
4. Run the following query and save the results in a spreadsheet with headers:

SQL and SAP HANA:

SELECT T1."DataSource", T1."VersionNum", T1."CreateDate",


T0."AbsEntry", T1."TransId", T1."BaseRef"
FROM OBOT T0
INNER JOIN OJDT T1 ON t0."TransId" = t1."TransId"
WHERE T0."AbsEntry" <> T1."BaseRef" AND T1."TransType" = 182;

5. If the query does not return any results, collect the following field values for the affected transactions that you are unable to move between drawers:

SELECT T1."DataSource", T1."VersionNum", T1."CreateDate", T1."TransId", T1."BaseRef"


FROM OJDT T1 WHERE T1."TransId" IN (X, Y, Z, ...) (replace X, Y, Z, ... with the transaction numbers of the affected BoE records)

6. Log a support message through SAP Service Marketplace referring to this SAP Note and include all of the relevant information mentioned above.

Attributes

Key Value

Other Components SBO-FIN-JOE (Journal Entry)


Products
Products

SAP B1 10.0 FOR SAP HANA

SAP B1 9.2 FOR SAP HANA

SAP B1 9.3 FOR SAP HANA

SAP BUSINESS ONE 9.2

SAP BUSINESS ONE 9.3

This document refers to


SAP Note/KBA Title

1732157 Collecting diagnosis information for SAP HANA [VIDEO]

1491494 Mismatch Between Cumulative Account Balance and Balance Due

This document is referenced by


SAP Note/KBA Title

2483701 Overview Note for SAP Business One 9.2 PL09, version for SAP HANA

2483691 Overview Note for SAP Business One 9.2 PL09

Attachments

File Name File Size Mime Type

sizing_check_v2.sql 4 application/octet-stream

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy