2693418 - Known errors in SAP Customer Checkout monitor when using SAP Customer Checkout with SAP Business One

The material in [line: 1] is marked as "Stock Item" in SAP Business One but the warehouse sent along with the item data has no inventory in SAP Business One. Either change the item to non-stock or change the inventory count for this warehouse in SAP Business One or change the warehouse in SAP Customer Checkout Monitor. Now try to post the transaction again.

Note: There can be cases where the line number from the error message is not pointing to the item that has insufficient inventory. This is the case where items are Bill of Materials of type "Sales" in B1. Then you need to consider each child / component item of the BoM in the "calculation" of the affected article.

In SAP Customer Checkout under Configuration > Accounting > Financial Transaction Types

The code maintained in the Financial Transaction Types and used in the current transaction should exist as a GL account in SAP Business One.

If the SAP Business One is configured to use Segmentation Accounts, in the CCO, it is necessary to enter the value of the AcctCode from the table OACT of your SAP B1 database.

select * from OACT

To now post the current transaction successfully, you need to change in SAP Customer Checkout Monitor the account for this transaction or maintain the code as a GL account in SAP Business One.

In SAP Customer Checkout, the currency used in the SALES ITEM (basically the main currency in SAP Customer Checkout) "GER" in this example message, is not available in SAP Business One or an exchange rate for this currency is not maintained in SAP Business One.

Maintain the currency or exchange rate in SAP Business One and try to post it again.

If the currency code itself is wrong, then you can change the currency code in SAP Customer Checkout monitor and try to post it again.

If changing currency in SAP Customer Checkout Monitor is not possible (because the field is read only in monitor or the currency is used several times in the same transaction), then you need to cancel this transaction from the SAP Customer Checkout monitor. Maintain the appropriate mapping for this currency in SAP Customer Checkout (Settings à Cash desk à Field Mapping) and post this transaction again from the SAP Customer Checkout receipt details screen.

This is a very generic error message and can occur for several reasons. Some of the known reasons are documented here.

• SAP Customer Checkout is configured to handle several currencies for payment
  => The currency used in payment is not available in SAP Business One.
  
  
  
• SAP Customer Checkout is configured to handle several currencies for payment and a foreign currency was used for payment. The Exchange rate posting setting for SAP Customer Checkout is different from the setting in SAP Business One.
  => In SAP Customer Checkout, the setting should be the same as Business One. Either in system the value should be "Direct" or "Indirect".
  => In SAP Business One: Administration/System Initialization/General Settings/Display/Exchange Rate Posting
  => In SAP Customer Checkout: Configuration/Integration/SAP Business One/Exchange Rate Posting
  Procedure:
  To now post the current transaction successfully, you need to change in SAP Customer Checkout Monitor the exchange rate send in the transaction to 1/Exchange rate sent in the transaction.
  Example: If the exchange rate sent in transaction is 2, then it needs to be changed to ½ = 0.50
  
  
  
• In the field mapping, PAYMENT_FORM_CODE entries are changed or deleted
  => In the payload that is sent from SAP Customer Checkout to the B1if scenario the PaymentMeans is missing.
  => In the payload for PostInvoice in "CashFlowAssignments" the PaymentMeans tag is missing or not correct.
  => In the default configuration we have pre-delivered these values in the field mapping for PAYMENT_FORM_CODE.
  => These values should not be changed or deleted.
  => Setting – Cashdesk – Field Mapping

In SAP Customer Checkout: Configuration -> Accounting -> Petty Cash

=> Make sure the account set for Petty cash ID is available in SAP Business One (General Ledger Account in Business One)

You are facing the above mentioned DI Error using SAP Customer Checkout 1.0 when running a Cash-In / Cash-out transaction. The receipts are displayed as inconsistent in SAP Customer Checkout Monitor (Tab: Cash Transactions). The main cause could not be clarified and is not reproducible in our test environment. A possible reason for this behavior could be a bug in the software or the use of a Plugin.

A solution is known. To transfer the receipts, follow these steps:

1. Tab 'Cash Transactions'
2. Click on the 'internal ID' of your receipt
3. Edit
4. Click on 'Details' of the Position
5. Copy the value of the 'Amount paid' field to the 'Gross Amount' field and save your changes
6. Release your receipt again

Now the receipt should be transferred.

Credit Card payment Methods has not been defined in SAP Business One. Credit Card payment Methods is not sent from SAP Customer Checkout but used from the existing one in SAP Business One. If no Credit Card payment Methods is defined, you get the mentioned exception.

To now post the current transaction successfully, create a Credit Card Payment Method in SAP Business One and try to post this transaction again from the SAP Customer Checkout Monitor.

1. The Credit Card Type Code assigned to the transaction/credit card doesn’t exist. In SAP Customer Checkout in Configuration => Accounting => Credit Card Type different Credit card type codes can be maintained. These credit card type codes can then be used in Sales Transactions.
2. Is a plug-in (e.g. Pepper Treibauf) used for EFT credit card transactions? Check in Configuration => Plug-Ins => Settings if an invalid card type ID is entered in any of the fields.
3. Configuration => POS System => Field Mapping: In this section of SAP Customer Checkout mappings for credit card type codes can be maintained. Most likely the values used in the mapping are not the same as used in the Configuration => Accounting => Credit Card Type section. Correct the values if necessary.
4. The Credit card type codes must also exist in SAP Business One.

To now post the current transaction successfully, either create this new credit card type code in SAP Business One or change the credit card type code to appropriate value in the SAP Customer Checkout Monitor and try to post this transaction again from the SAP Customer Checkout Monitor.

This is a known issue and solved with updating the SAP Business One Integration Framework (B1if) scenario packages to

CCO Package Version: 3.2.39 or higher
CCO Package Version UI: 3.2.39 or higher

Details are described in KBA 2596260.

Please update your SAP Business One Integration Framework (B1if) scenario packages according SAP Note 2163033.

Business Partner of type Customer with ID "123" does not exist in the SAP Business One system.

A) Customer with ID POS2000 was created in B1 and synchronized into SAP Customer Checkout. However later in B1 the Customer ID was changed. For this transaction, change the Customer ID to the correct ID in the SAP Customer Checkout Monitor and try to book this transaction again from the SAP Customer Checkout Monitor. To avoid this issue again, perform a synchronization of Customers in SAP Customer Checkout and in future transaction use the correct customer ID in SAP Customer Checkout.

B) No Customer was selected in the transaction so SAP Customer Checkout used the default customer to post this transaction. The default customer is maintained in SAP Customer Checkout –> Configuration -> Integration ->  SAP Business One -> Dummy business partner ID. Change the "Dummy business partner ID" to an existing customer ID from SAP Business One.

This is a very generic error message and can occur for several reasons. Some of the known reasons are documented here.

A) The Sales Person code assigned to the transaction doesn’t exist in SAP Business One.

To now post the current transaction successfully, you need to change in SAP Customer Checkout Monitor the sales person code (or make blank) assigned to the transaction and try to post again.

In SAP Customer Checkout

Settings/User Configuration – For the users maintain the right ‘Sales Person ID’.

B) One of the Material/Article ID used in the transaction does not exist in the SAP Business One system.

Material/Article was created in B1 and synchronized into SAP Customer Checkout. However later in B1 the Material ID was changed. For this transaction change the Material ID to the correct ID in the SAP Customer Checkout Monitor and try to book this transaction again from the SAP Customer Checkout Monitor.

To avoid this issue again, perform a synchronization of Materials in SAP Customer Checkout and in future transaction use the correct Material ID in SAP Customer Checkout.

C) The Credit Card account assigned to the transaction/credit card doesn’t exist in SAP Business One system.

In SAP Customer Checkout in Configuration -> Integration -> SAP Business One -> Credit Card the credit account to be used for Credit Card can be maintained. This is the default value for the credit card account.

In Configuration -> POS System -> Field Mapping

In this section you can maintain the credit card accounts for respective credit card type codes. If an account is maintained here then this account is sent to the external system instead of the default credit card account.

These Credit card accounts should also exist in SAP Business One.

To now post the current transaction successfully, either create this new credit card account in SAP Business One or change the credit card account to appropriate value in the SAP Customer Checkout Monitor and try to post this transaction again from the SAP Customer Checkout Monitor.

D) If you are running SAP Business One 9.3 PL04 or higher, please check KBA 2650591.

E) Your SAP Business One has mutli-branch activated and the B1DI user is not assigned to this branch

Please check if the B1i user is assigned to this branch, detailed step-by-step description can be found in KBA 2884690

F) Your SAP Business One is running on a MENA localization, please review the KBA 3075050 and KBA 3133909

You cannot create / update data for Business Partner in the SAP Customer Checkout

For creating Business Partner (Customer) from SAP Customer Checkout in SAP Business One, you need to define a number range series in SAP Business One and maintain the Series number in SAP Customer Checkout. SAP Customer Checkout sends this series number while creating the Business Partner in SAP Business One.

Once you have created the number range series in SAP Business One, you need to know the Series number to maintain in SAP Customer Checkout.

To identify the correct Number range ID, run the SQL Statement below in the SAP B1 database:

select * from nnm1
where ObjectCode ='2'

Retrieve the information from the Series column.

In SAP Customer Checkout, it is necessary to maintain this number range ID.

Go to Configuration > Integration > SAP Business One > Number Range Id for customer creation

The Sales Person ‘99’ code assigned to the item doesn’t exist in SAP Business One.

To now post the current transaction successfully, you need to change in SAP Customer Checkout Monitor the sales person code assigned to the [line: 1] item for this transaction and try to post again.

In SAP Customer Checkout: Settings/User Configuration - For the users maintain the right ‘Sales Person ID’.

The Owner code assigned to the transaction doesn’t exist in SAP Business One. The cashier who performs the transaction in SAP Customer Checkout is mapped as the owner. However this mapping only happens if an employee ID is maintained for this user in SAP Customer Checkout

Settings –> User Configuration -> Employee ID

To now post the current transaction successfully, you need to change or make blank in SAP Customer Checkout Monitor the owner code assigned to the transaction and try to post again.

In SAP Customer Checkout

Settings/ User Configuration – For the users maintain the right ‘Employee ID’ or make this field empty.

The Distribution Rule assigned to the sales item in this transaction doesn’t exist in SAP Business One. Maintain the correct distribution Rule in SAP Customer Checkout

Configuration-> SAP Business One -> Distribution Rule

To now post the current transaction successfully, you need to change or make blank in SAP Customer Checkout Monitor the distribution rule assigned to the items of the sales transaction and try to post again.

Di Error: (-5002) Invoice &amp, receipt must be paid exactly

The payment term that is used in the receipt (AR Reserve Invoice) is maintained in the SAP Customer Checkout configuration. This is the payment term that is sent with every receipt that is created.

Configuration/Integration/SAP Business One/Payment Terms

Error is caused by wrong payment terms setup in SAP Business One. In the SAP Business One – Payment Terms set-up for this payment term the ‘Open Incoming Payment’ value is set to Cash (No, Cash, Cheque, Credit etc. are the various options). This should be set to No.

Now transaction paid in cash, credit card, etc. should work again.

To now post the current transaction successfully, after changing the payment terms set-up in SAP BusinessOne, try to post this transaction again from the SAP Customer Checkout Monitor.

The UoM Group (which in turn has several allowed UoM Entry/codes) assigned to the article in SAP Business One does not allow the UoM Entry/code selected in SAP Customer Checkout. This can happen when the UoM Group assigned to the article in SAP Business One was changed after data was already synchronized to SAP Customer Checkout. And synchronization was not triggered in SAP Customer Checkout after that. Possible solutions:

A) Change the UoM Group in SAP BusinessOne to allow the value sent from SAP Customer Checkout.

B) Change the UoM Entry/code in SAP Customer Checkout Monitor for this transaction and try to post again.

To avoid this issue in future transaction perform a synchronization of materials in SAP Customer Checkout. This will assign the correct UoM Entry to the material in SAP Customer Checkout.

Di Error: (-5002) Invalid value [OINV.GroupNum][line:1]

The payment term that it sent with the transaction from SAP Customer Checkout is not available in SAP Business One. Maintain the correct Payment term in SAP Customer Checkout.

Settings/Cash desk/SAP Business One/Payment Terms

To now post the current transaction successfully, you need to change in SAP Customer Checkout Monitor the payment term for this transaction and try to post again.

This error can happen in receipts with payments in foreign currency (FC). Please make sure to have identical exchange rate posting directions in B1 and CCO:
 
1) in B1 the setting Administration -> System Initialisation -> General Settings -> Display -> Exchange Rate Posting -> Direct or Indirect?
2) in CCO Configuration -> Integration -> SAP Business One -> General -> Exchange rate posting -> Direct or Indirect?

In both applications it should be either Direct or Indirect.

To correct inconsistent receipts in the CCO Monitor please edit the payment item lines and update the Exchange Rate to its inversed value (1/X).

Exception : DI Error: (-10) Base document card and target document card do not match. [VPM2.DocLine][line: 1]-The di call #1 did fail.

There are currently four known scenarios causing this error:

Scenario 1:

Customer overpays by Credit Card in Foreign Currency and gets cash change in Local Currency. In that case please go to Business One -> Administration -> Setup -> Financials -> Currencies and find the line with the foreign currency: Is an amount maintained in the fields Incoming Amt Diff. Allowed & Outgoing Amt Diff. Allowed? If yes: Please - either temporarily or permanently - remove these amounts. Then try to release the inconsistent receipts again from the CCO Monitor.

Scenario 2:

Customer pays exact amount by Credit Card in Foreign Currency but due to rounding a 0,01 cash change (outgoing payment) difference amount may be calculated.

For example:

Home currency EUR / Foreign currency GBP / Exchange rate 1.11

Sales receipt 5.60 EUR

Now create a cash payment item and change the currency to GBP. The calculated expected amount in GBP would be 5.05 according to the software. We enter 5.05 GBP, but then the software shows a rounding amount of -0.01 EUR. I click on Ok and finish the receipt. One cent is returned to me.

In detail: 5.05 * 1.11 = 5.6055, rounded 5.61.

Solution:

1. In B1 integration framework go to Scenarios => Setup
2. Select Scenario Package Identifier = sap.CustomerCheckout
3. Push button Data Mgt.
4. Select Global Table Name = Table: vTbl.IncludeList.xml
5. In the table pop up find the SAP Step Extension Point = sap.POS.POSTInvoice_SkipSmallPay
6. In the blank field enter the payment amount that you want to skip, for example 0.05

Now all payment amounts below the entered amount will not be posted to SAP B1. The receipt should no longer run into this error message in CCO Monitor.

Scenario 3:

1. Prerequisite: POS Screen setting Allow combination of payments on credit with other payment items = ON
2. Create a CCO sales receipt, total EUR 100
3. Payment items: 80 On Credit, 40 Credit Card (overpayment)
4. Pay out by cash: 20
5. Post receipt => it gets inconsistent in CCO Monitor with this error

Di Error: (-5009) Item number is missing, specify an item number

One of the Material/Article ID used in the transaction does not exist in the SAP Business One system.

Material/Article was created in B1 and synchronized into SAP Customer Checkout. However later in B1 the Material ID was changed. For this transaction change the Material ID to the correct ID in the SAP Customer Checkout Monitor and try to book this transaction again from the SAP Customer Checkout Monitor.

To avoid this issue again, perform a synchronization of Materials in SAP Customer Checkout and in future transaction use the correct Material ID in SAP Customer Checkout.

"No reply from URL received:/B1iXcellerator/exec/ipo/vP.001sap0013.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNCXPT.ipo/proc?action=CreateUser&msglog=true&setvar=false. Error...

This error occur in the case that the file  CCOMTool.jar is missing in following File in the B1iXcellerator WEB-INF lib-folder. In SAP Note 2407021 - Error in SAP Customer Checkout Monitor while creating an user you will find an information how to insert the file into the folder and also the file attached.

Receipt or invoice are stuck in SAP Customer Checkout monitor with status "New" and are not posted to SAP Business One

There is no error message.

Procedure:

The issue is introduced with SAP Business One 9.2 PL04. Business One integration Framework (B1if) changed something and this caused the problem. Business One integration Framework (B1if) provided a fix for this issue and you need to follow the below steps to solve the problem.

1. Follow steps in Business One integration Framework (B1if) Hot fix for B1 9.2 PL04: SAP Note 2366991.

2. Re-import the SAP Customer Checkout scenario steps in Business One integration Framework (B1if). For this you can follow the steps in SAP Note 2163033

Additionally please note, if you have partner extension concept used and have assigned your extension point to our services, there is a change in SBusiness One 9.2 PL04. The note 2163033

is updated with this change. Here it is meant to only high-light this change.

We are in touch with the SAP Business One team so that the check-box mentioned below is checked by default.

Go to "Scenarios" and then select "Import".　 
Now in ‘Scenario Package or Step ZIP File Name’ click on the Browse and select the scenario package that you downloaded from the SAP Note, vPac.sap.CustomerCheckout.zip. 　 　　With SAP Business One 9.2 PL04, you need to additional select a new check-box "Import Individual Global Tables" and then click on "Submit".　If you do not select the　check-box "Import Individual Global Tables", the table with list of extension point that we provide in the set-up->Data Mgt ->　"Table: vTbl.IncludeList.xml" will be empty.

Also review the KBA #2793679 for further information about this issue.

Error message when using Batch or Serial Number:

Receipts or Invoices with Batch or Serial numbers are not posted in SAP Business One. They are stuck in SAP Customer Checkout Monitor with following error message:
999 - Invoke of: GetBusinessObjectFromXML Source: Description: 20070001 is a bad date in property InDate

The issue introduced with SAP Business One 9.2 PL04. SAP Business One added a new validation which allows only the date format like 20070001. The issue is described in SAP Note 2370493.

Hence the SAP Customer Checkout B1iF Scenario needs to adapt so that the date is send in the right format.

We have provided a new version of the SAP Customer Checkout B1if Services which fixes this problem. Version 3-0.21 and higher fixes this. The services are available in our standard SAP Note 2163033

Date deviates from permissible range (Document Name - offending date) (Message 173-11)

sap.CustomerCheckout scenario package is inactive or the package itself does not exists or the scenario step that is called doesn’t exists.

If sap.CustomerCheckout scenario package is inactive - Activate the scenario Packages from SAP Business One Integration Framework (B1if).

If sap.CustomerCheckout scenario package/step is not present - check that the customer is using the correct version of B1if. Example BusinessOne 9.0 PL14 for SAP Customer Checkout SP02.

Exception : DI Error: (-10) Invoice is already closed or blocked -The di call #1 did fail."

Scenario 1:

This error message can occur in case an AR Invoice with already paid installments is fetched into SAP Customer Checkout. This is a limitation. SAP Customer Checkout does not support AR Invoices with installments. For more information refer to KBA 2624575.

Scenario 2:

Receipt with total amount of 0,00 and payment items:

1. Create sales receipt and pay with credit card
2. Create a return for the receipt and select "Copy Payment Items" so that the credit card payment is refunded
3. Add a sales item of equal value to the return receipt so that the receipt total becomes 0,00
4. Add a credit card payment for the sales item to balance the receipt total of 0,00

Solution to scenario 2:

One way to avoid this from happening is not to select "Copy payment items" in the return receipt. If you want to have this checkbox removed by default you can select this in Functions => Configuration => POS System => Sales Screen => Enable 'copy payment items' during return by default = OFF

OR

Create A/R invoice manually in B1. Then create Incoming + Outgoing payments manually in B1. Finally, in CCO Monitor mark the inconsistent receipt and set it to Cancelled (hit the Cancel button).

1. This error can be down to an outdated version of the CCO scenarios. The solution is to update your CCO scenarios according to note 2163033.
2. This error may occur in case discount on item level was applied. In this case the following workaround can be considered: In the Customer Checkout Monitor remove the discount from each sales item. Instead enter the discount on the header level. Then release the receipt.

This error can occur when your B1if Customer Checkout scenarios are between 3.4.74 and 3.5.79. The fix is available from scenarios version 3.5.80 onwards. See note 2163033.

An enhancement was done in the B1if Customer Checkout scenarios version 4.0.31 to solve this issue. See SAP Note 2163033

This error can happen in scenarios when

1. the feature Automatic batch number determination is activated
2. and when a CCO receipt contains a quantity X of a sales item for which exactly this quantity X is available in Business One for this batch number sales item

A fix was provided in version 4.0.01 of the CCO packages in B1if (see note 2163033).

DI Error: (-5002) Specify an active branch [OINV.BPLId]-The di call #1 did fail.

When multi-branch is activated in SBO, but no branch ID is maintained in SAP Customer Checkout or wrong branch ID is maintained in SAP Customer Checkout, then in SAP Customer Checkout monitor this error message is shown.
SAP Customer Checkout supports multi-branch only from Release 2.0 FP07. If lower version then kindly update. If already on the right version than maintain or correct the branch ID in SAP Customer Checkout.

This concept was introduced via B1if scenario version 3.4.74, see SAP Note 2163033. Via SAP Note 2163033 you can also find some bug fixes related to this topic, so,
ensure your scenarios are always up to date.

It is NOT possible to modify or edit the branch ID in SAP Customer Checkout monitor. This is as planned. We do not allow modifying system ID and branch ID in SAP Customer Checkout monitor. In this case the partner needs to change the Branch ID, this needs to be done in SAP Customer Checkout monitor DB directly.

Example:

Login to the database

1) Change the branch for one receipt

select BPLId from PointofSaleReceipt where PosKey = 'xxx'

update PointofSaleReceipt set BPLId = x where PosKey = 'xxx'

2) Change the branch for all receipts

select BPLId from PointofSaleReceipt where CashDeskID = 'xxx'

update PointofSaleReceipt set BPLId = 7 where CashDeskID = 'xxx'

After the change the receipt has to be released in SAP Customer Checkout monitor.

005 - B1 Error (0010000100): Exception : DI Error: (-5002) Cannot add transaction, numbering series assigned to another branch [ORCT.BPLId] , "PAYMENTSERIES"-The di call #1 did fail.

You are assigning customers to branch. However the user which is used for creating this customer is not assigned to the branch used. By default for SAP Customer Checkout, the integration user B1if is used. Hence this user should be assigned to the branch – you want to use.

By defaults when customers are created by SBO. They are created for all branches to which the logged in user(like manager) is assigned. Which means for our B1if services, it will be created for all branches to which integration user “B1if” is assigned.

DI Error: (-5002) Warehouse is not assigned to the same branch as the document [INV1.WhsCode][line: 1] , “201”-The di call #1 did fail.

• If the B1if Customer Checkout scenarios are lower than 3.7.92. Update the scenarios according to the SAP Note 2163033
  Make sure to execute the step #9 of the SAP Note 2163033
  
  
• Check/Test the connection of the "CustomerCheckoutDb"

1. Open the B1if and go to SLD
2. In the list of databases find "CustomerCheckoutDb"
3. Scroll down to the JDBC area
4. Click on Test Connection

NOTE: Make sure that the database user assigned in the JDBC section has authorization to execute Update/Alter/Create statements in the CustomerCheckout database. Switching the user to SYSTEM can be a good workaround to execute step #9 of note 2163033 successfully. This can be done temporarily, only for the purpose of this update. You can afterwards switch back to the previous database user.

If you want to create a HANA database user with the same privileges as the default SYSTEM user refer to the official SAP documentation for guidance. Step-by-step description:

1. Review the official SAP HANA documentation for creating a new user:

   • For SAP HANA 2.0, you can refer to the SAP HANA Security Guide

2. Follow the instructions in the documentation to create a new user. During the user creation process, ensure that the new user is assigned the same privileges as the SYSTEM user.

3. To assign the privileges to the new user, you can refer to the documentation section on granting privileges. Here are the relevant links:

   • For SAP HANA 2.0

Msg 257, State HY000: SAP DBTech JDBC: [257] (at 13): sql syntax error: incorrect syntax near """: line 1 col 13 (at pos 13)

com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: com.sap.b1i.bizprocessor.BizProcException: BPE001

Nested exception: com.sap.b1i.utilities.UtilException: UTE001 Nested exception:

com.sap.engine.lib.xml.util.NestedException: Msg 257, State HY000: SAP DBTech JDBC: [257] (at 13): sql syntax error:

incorrect syntax near """: line 1 col 13 (at pos 13)

We know of 3 scenarios when this error happens:

Scenario 1: Refer to KBA #3058951

Scenario 2: This issue might also happen if the B1if Customer Checkout scenarios version are lower than 4.0.31. See SAP Note #2163033 and update the scenarios if you are running a version lower than 4.0.31.

Scenario 3: The receipt has a positive quantity but a negative unit price. To solve this you need to update the positive quantity to a negative quantity in CCO Monitor, then release the receipt.

Make sure that the batch/serial number is assigned to the item.

This issue might also happen if there is UoM conversion for the item.
Unit of measure conversion and automatic batch number handling specially with UoM conversion is not straight forward use-case.
(1 Box is 4 packet or 10 packet or 25 packet is fine but when 1 box is 26 packets or 13 packets) then, there can be rounding differences between how the different systems handled it. We are using the round to 4 digits function provided by xslt.
SAP Business One is not flexible there, it does not take the value calculated by external system and calculates again. And if the value from external system calculation do not match the value calculated from SAP BusinessOne then the receipt is rejected. In such cases a manual posting will be needed.
It is recommended to test all customer use-cases for such not straight forward use-case.
Refer to the SAP Note 2163033 version 4.0.37 and 4.0.38

999 - DI Error: (-5002) One of the base documents has already been closed [INV1.BaseEntry][line: 1]-The di call #1 did fail.

The receipt was created based on a Sales Order fetched from the SAP B1. This issue happens if the sales order is already closed in the SAP B1.

To identify the Sales Order, refer to the steps below:

1. In the CCO monitor, find the inconsistent receipt and click on the Internal ID
2. Under Sales item, select the Item and click on Details
3. Check the field "Source document ID", the value stored is the ID of the Sales Order
4. Go to your SAP B1 > open the Sales Order > Search for the Sales order ID
5. Check the status of the Sales order

DI Error: (-5002) Internal error (-5002) occurred

This error may happen when there is an over payment in credit card and change in cash

E.g.:

Receipt amount = 100 EUR
Payment in credit card = 105 EUR
Change in cash = 5 EUR

The cause of this issue is a bug in the SAP B1 10 versions lower than 2105. Refer to the SAP Note 3035558 for additional information

999 - DI Error: (-5002) 1250000103 - Row without tax was found-The di call #1 did fail.

This issue happens if the sales person assigned for the receipt and/or the sales person assigned for the sales items is inactive in the SAP B1.
In the CCO monitor, under General Data > Sales Person, you can identify the sales person assigned in the receipt level and under Sales Items details, you can identify the sales person assigned in the item level.

To solve this issue, maintain an active sales person ID and release the document again.

999 - DI Error: (-5002) 234103406 - Base document price mode and target document price mode do not match-The di call #1 did fail.

You will receive this error in the following scenario:

1. In Business One the flag Company Details -> Basic Initialization -> Enable Separate Net and Gross Price Mode is active
2. In Business One you create a sales document (Sales Order, Sales Quotation...) in Price Mode = Net
3. In Customer Checkout you fetch this sales document and finalize it

The reason why you get this error is explained in note 2163033 for scenario version 4.0.41: From this version onwards only sales documents with Price Mode = Gross are supported when the flag Enable Separate Net and Gross Price Mode is active.

Exception: Invoke of: GetBusinessObjectFromXML

Description: Invalid item name "" in Enum "BoRcptInvTypes". The valid names are: "it_AllTransactions"-"-1", "it_OpeningBalance"-"-2", "it_ClosingBalance"-"-3", "it_Invo

1. Make a note of the receipt ID and CCO POS cash desk ID
2. Mark the receipt in CCO Monitor and hit the button "Cancel" to set the status to Cancelled
3. Logon to the CCO where the receipt was created
4. Find the receipt using the receipts search
5. Hit Display and show the receipt details
6. Hit the Repost button and select ERP
7. You should now find the receipt under in CCO Monitor under Cash Transactions where it should get status "Released"

999 - DI error: A COM exception has been encountered

At Invoke of: GetBusinessObjectFromXML

Description: The server threw an exception.