SAP Knowledge Base Article - Preview

2693418 - Overview of known errors in SAP Customer Checkout monitor when using SAP Customer Checkout with SAP Business One

Symptom

  • Di Error: (-10) 10001071 - Customer BIK2000 is inactive or Di Error: (-10) 10001069 - Item BIK1002 is inactive

Business Partner of type Customer with ID "BIK2000" is inactive in SAP Business One or Material BIK1002 is inactive in SAP Business One

  • Di Error: (-10) 10001069 Quantity falls into negative inventory [INV1.ItemCode][line:1]

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.

  • Di Error: (-10) 10000180 - Specify valid tax code

In SAP Customer Checkout the Tax code assigned to the item does not exists in SAP Business One. Either create the new Tax Code in SAP Business One or change the Tax Code for this item in SAP Customer Checkout and try to post again.

  • Di Error: (-10) 10000180 - Invalid VAT Group

In SAP Customer Checkout the Tax code assigned to the item is not valid for Sales (category output tax in SAP Business One). This tax code is most probably for Purchase (category input tax in SAP Business One) relevant transactions only and not sales relevant (category output tax in SAP Business One). Either change the Tax Code category in SAP Business One or change the Tax Code for this item in SAP Customer Checkout and try to post again.

  • Di Error: (-10) G/L account is not valid [VPM4.AcctCode][line:1]

In SAP Customer Checkout: Setting/Financials/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.

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.

  • Di Error: (-10) 1470000365 - Update the exchange rate, "GER"

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 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.

  • Di Error: (-10) Internal error (-10) occured

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

A) SAP Customer Checkout is configured to handle several currencies for payment. The currency used in payment is not available in SAP Business One.

B) 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: Setting/Currency/Exchange Rates/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

C) 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

  • Di Error: (-10) Account for cash payments has not been defined

In SAP Customer Checkout: Setting/Financials/Petty Cash

The Petty cash account is not available in SAP Business One (General Ledger Acount in Business One)

  • Di Error: (-10) Amount to be paid does not match existing transactions

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 environement. 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.

  • Di Error: (-10) Payment method not defined [RCT3.CrTypeCode][line:1]

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.

  • Di Error: (-10) Credit card code does not exist [RCT3.CreditCard][line:1]

The Credit Card Type Code assigned to the transaction/credit card doesn’t exist. In SAP Customer Checkout in Setting/Financial/Credit Card Type, different Credit card type codes can be maintained. These credit card type codes can then be used in Sales Transactions.

In Setting/Cash desk/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 Setting à Financial à Credit Card Type section. Correct the values if necessary.

These Credit card type codes should also exists 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.

  • Di Error: (-10) Journal entry has no open balance

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

CCO Package Version: 3.2.36 or higher
CCO Package Version UI: 3.2.36 or higher

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

  • Di Error: (-2028) Invalid BP code [OINV.CardCode], "POS2000"

Business Partner of type Customer with ID "POS2000" does not exists 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 – Settings à Cash desk à SAP Business One à Dummy business partner ID. Change the "Dummy business partner ID" to an existing customer ID from SAP Business One.

  • Di Error: (-2028) No matching records found (ODBC -2028)

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 Settings/Cash desk/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 Settings/Cash desk/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.

  • Di Error: (-4002) to generate this document, first define the numbering series in the Administration Module in system SAP Business One

You cannot create/ update data for Business PArtner first Name, LastName due to this DI Error.

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.

In SAP Business One

To find the information in SAP Business One, choose Tools à Queries à Query Generator.

In the Select field, enter ObjectCode as ObjectCode, DocSubType as ObjectSubType,Series as SeriesCode,SeriesName as SeriesName

In the From field, enter nnm1

In the Where field, enter ObjectCode ='2' and SeriesName = <Name of the number range> and choose the Execute button.

Retrieve the information from the SeriesCode column.

In SAP Customer Checkout

Now maintain the series code in

Settings/Cash desk/SAP Business One/Number Range Id for customer creation

  • Di Error: (-5002) 10001069 - Enter valid currency code [OINV.DocCur][line:1], "EUR" or Di Error: (-10) The document currency does not match the business partner"s currency. [OVPM.DocCurr][line: 1]

Business Partner used in the SAP Customer Checkout transaction is assigned a currency in SAP Business One different from the one used in the sales transaction or the incoming payment/out-going payment. Either change the currency in SAP Business One for the customer to the right currency or set the currency in SAP Business One for the customer to All currency.

  • Di Error: (-5002) 10001069 - [INV1.ItemCode][line:1], "Business partner catalog number linked to item not specified as sales item (1)"

The material in [line: 1] is not marked as "Sales Item" in SAP Business One. Change the material master data in SAP Business One and mark the item as sales relevant.

  • Di Error: (-5002) [INV1.SlpCode][line:1], Linked value 99 does not exist"

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’.

  • Di Error: (-5002) [OINV.OwnerCode], Linked value 99 does not exist"

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.

  • Di Error: (-5002) - Linked value 100 does not exist"

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

Settings/Cash desk à 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 exactely

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.

Settings/Cash desk/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.

  • Di Error: (-5002) 1470000365 - UoM specified is not assigned to item in row 1

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.

  • 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.

  • Error message in SAP Customer Checkout monitor in case central user management is enabled and you try to create an user

"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 Bussiness 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.

  • 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)

The error message indicates the Due Date as the offending date. In effect this means that the Due Date falls outside the defined due date range of the current posting period. To solve this error you have to access the posting period setting of the period where the document will be posted in SAP Business One. Go to Administration --> System Initialisation --> Posting Periods in SAP Business One. Click on the golden link arrow of the appropriate period. Update the Due Date range to cover the Due Date. After saving go back to the SAP Customer Checkout Monitor and repost the receipt.

  • Nested exception: com.sap.b1i.utilities.UtilException: UTE001 Nested exception: com.sap.engine.lib.xml.util.NestedException: Server side cannot respond your request (No scenario step (vBIU) assigned for step for sender system (SysId) [0009] [incoming identifier = &apos;PostInvoice&apos;])

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.

  • Invoice is already closed or blocked

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

  • Connect to Business One failed. (-107) Unable to connect with the specified username and or password {b1Server=DEWDFWSSC5034, company=SBODemoDE, licenseServer=DEWDFWSSC5034:30000, dbType=7, dbUser=sa, userName=B1i}

The userName or password in the SLD entry in SAP Business One Integration Framework (B1if) is wrong. Correct the password and check the connection using the Test Connection Feature of B1if.

  • Connect to Business One failed. (-111) Unable to access SBO-Common database {b1Server=DEWDFWSSC5034, company=SBODemoDE, licenseServer=DEWDFWSSC5034:30000, dbType=7, dbUser=sa, userName=B1i}

The dbPassword in the SLD entry in SAP Business One Integration Framework (B1if) is wrong. Correct the password and check the connection using the Test Connection Feature of B1if.


Read more...

Environment

  • SAP Business One
  • SAP Customer Checkout
  • SAP Customer Checkout Monitor
  • SAP Business One Intergration Framework

Product

SAP Customer Checkout all versions

Keywords

IS-SE-CCO, CCOm, Customer Checkout Monitor, DI error, SAP Business One Intergration Framework, B1if, SAP Business One, B1 , KBA , IS-SE-CCO , Customer Checkout , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.