SAP Knowledge Base Article - Preview

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

Symptom

    Issue ID Error message
    Explanation and resolution
    1 Di Error: (-10) 10001071 - Customer 123 is inactive
    Business Partner of type Customer with ID "123" is inactive in SAP Business One
    2 Di Error: (-10) 10001069 - Item XYZ is inactive
    Material with ID "XYZ" is inactive in SAP Business One
    3 DI Error: (-2028) [OINV.GroupNum] , "No matching records found (ODBC -2028)"-The di call #1 did fail
    The payment term code is invalid. The default payment term code for cash transactions (-1) has to be entered in the Configuration of Customer Checkout in Integration -> SAP Business One -> General -> Payment terms.
    4 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.
    5 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.
    6 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.
    7 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.

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

    9 Di Error: (-10) Internal error (-10) occurred

    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
    10 Di Error: (-10) Account for cash payments has not been defined

    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)

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

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

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

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

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

    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.

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

    17 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 -> Integration -> SAP Business One -> Number Range Id for customer creation

    18 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.
    19 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.
    20 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’.

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

    22 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

    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.

    23

    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.

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

    25

    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.

    26 Exception : DI Error: (-10) Unbalanced cash flow assignment -The di call #1 did fail.

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

    27

    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 two known scenarios in which this issue may arise:

    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: Currently this issue has to be reported to SAP via an incident. It requires manual interaction from our side on database level.

    28

    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.

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

    30

    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.

    31

    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

    32

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

    34

    Invoice is already closed or blocked

    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.
    35 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.
    36 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.
    37 999 - DI Error: (-5002) 234102285 - Enter a tax amount that is less than or equal to the gross total-The di call #1 did fail
    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.
    38 999 - DI Error: (-10) Enter a valid value in &quot,Whse&quot, field [??????? 0-0]-The di call #1 did fail
    This error can occur in case an invalid warehouse was selected for sales item in the receipt.
    39 DI Error: (-5002) Tax amount cannot be negative [INV1.VatSum][line: 3]-The di call #1 did fail
    This error can occur when your B1i scenarios are between 3.4.74 and 3.5.79. The fix is available from scenarios version 3.5.80 onwards. See note 2163033.
    40 004 - SQL Error ( 0010000103): SAP DBTech JDBC: [339]: invalid number: [6930] attribute value is not a number
    This error can happen when the SAP Business One database is on HANA. Please check if one of the items in the receipt has an incorrect UoM or Quantity type code in the item master data. So first troubleshooting step could be to open the inconsistent receipt in the CCO Monitor in Edit mode. Then open the Sales Item details and check the field Quantity type code. If it contains an non-numeric value like EA you need to overwrite it with a numeric value.
    41 999 - Network is unreachable: connect (local port 63224 to address 0:0:0:0:0:0:0:0, remote port 2099 to address 0.0.8.51)
    This error is caused by an incorrect connection setting in the B1 integration framework. In the B1if go to the SLD tab then click on the Business One company database and check the entries you made in B1DI. Pay special attention to the diProxyHost field. It must contain the server name and not a port number.
    42 005 - B1 Error (...): 
    Exception : Invoke of: GetBusinessObjectFromXML
    Source:
    Description: CServiceData::SetPropertyValue failed, Value must be a whole number in property "CreditCard" of "PaymentCreditCard"
    This error and its resolution is described in KBA 2566878.
    43 Error: Automatic batch and serial number finding not available for returns
    Please refer to KBA 2719036.
    44 999 - Invoke of: GetBusinessObjectFromXML
    Source:
    Description: CServiceData::SetPropertyValue failed, Value must be numeric in property "Quantity" of "BatchNumber"
    -The di call #1 did fail.

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

    45

    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.

    46

    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.

    When multiple branch function is enabled in the B1 company database and every branch has its own series then every receipt with a payment item this error. Please refer to SAP Business One note 2833098 for details about the fix.
    47 DI Error: (-5002) 1320000257 – You are not assigned to selected branch ‘Frankfurt’ [USR6.BPLId][line: 1]-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.

    48

    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.

    BranchID in the transaction and warehouse used – no not match. Kindly assign the warehouse to the branch in SBO or correct the branch ID in SAP Customer Checkout or SAP Customer Checkout monitor.
    49 DI Error: (-5002) 1320000258 – Select business partner assigned to specified branch “Frankfurt”-The di call #1 did fail.
    Customer is not assigned to the branch which is used in the transaction.
    50 B1 Error (0010000108):  Exception : DI Error: (-5002) Account is not assigned to the same branch as the document [ORCT.CashAcct][line: 1] , “511402”- The di call #1 did fail
    PettyCash or GL Ledger account used is not assigned to branch.
    51 B1 Error (0010000108):  Exception : DI Error: (-5002) Ensure selected branch is the same as the branch of documents to be paid [ORCT.BPLId][line: 0] , “Swiss”
    When you try to pay an Invoice which belongs to a different branch. This is not supported by SAP Customer Checkout.
    52 Msg 260, State HY000: SAP DBTech JDBC: [260]: invalid column name: CreateCreditMemo
    • 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. Find in the server list the "CustomerCheckoutDb"
    3. Click on Test Connection
    • Make sure that the database user assigned in the JDBC section has authorization to execute Update/Alter/Create statements in the CustomerCheckout database
    53 005 - B1 Error (0010000100):
    Exception : DI Error: (-10) Confirmation amount must be greater than zero -The di call #1 did fail.
    This error happens in CCO scenarios 4.0.02 and lower. It happens when a credit note is fetched from Business One in a CCO receipt and a sales item is added to the receipt with the same positive amount. So the document total is zero. When the switch Allow receipt total gross amount of 0.00 by combination with business documents (manual clearing might be needed) is active / ON then this type of receipt should be posted to Business One. Due to a bug you may get above error message. The solution is to update your CCO scenarios according to note 2163033.
    54 999 - Automatic Batch Number Determination did not work as expected. Potential reasons can be: Not enough serial and batch number existing for assignment. ():
    This error happens when Automatic batch number determination or Automatic serial number determination are active but the receipt was rejected by Business One. The most common reason is that there is not enough stock in the warehouse for this batch or serial number item. After replenishing sufficient stock the inconsistent receipt can be released again from the CCO Monitor.
    55

    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)

    Refer to KBA #2876023
    56 999 - Cannot convert data-type void to reference
    This error does not come from CCO and needs to be handled in the Business One integration framework. For support this should be reported as an incident to the Business One team.


    Read more...

    Environment

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

    Product

    SAP Customer Checkout all versions

    Keywords

    IS-SE-CCO, CCOm, Customer Checkout Monitor, DI error, SAP Business One Integration Framework, B1if, SAP Business One, B1, CCO , 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.