sap.POS.CreateUpdateTab is not updating CustomerCheckout Database

[m_baccar]

Hi There

I successfully updated my SAP CCO scenario Package from 3.3.64 to 4.0.17 as described in the SAP Note 2163033.

After finishing all the steps, I still have the error message "Invalid Column name : CreteCreditMemo".

I checked my CustomerCheckout Database and I didn't find the two fields supposed to be added after this Update to the "PointOfSaleReceipt" table : "CreateCreditMemo" and "BPLId".

Could you help me out Please?

[kvbalakumar]

Hi,

Are you using SQL or HANA?

[m_baccar]

Hi balakumar.viswanathan2,

I'm using SQL (further information SAP B1 9.2 PL 7 and Customer Checkout 2.0 FP 06 PL08.

[anderson_schmitt]

Hello Mohamed,

In the B1if go to SLD and find the CustomerCheckoutDb and click on Test Connection. Is the connection working fine?

Does the user used in the JDBC connection has authorization to create and update tables in the SQL Server?

Regards,
Anderson

[m_baccar]

Hello Anderson,

Thank you for your response.

The connection is working fine and the user used in the JDBC connection is 'sa' which is the database owner.

[anderson_schmitt]

Hello Mohamed,

In this case, I suggest you to open an support incident.

Regards,
Anderson

[Klaus_Frick]

Hello Mohamed

Have you directly updated from 3.3.64 to 4.0.17? As nowhere stated in 216033 the CreateUpdateTab routine might not be backwards compatible. So you could try to update following the rules and update from 3.3.64 to 3.4.74 to 3.5.80 to 3.7.92 to 3.8.83 to 3.9.96 to 4.0.17.

[m_baccar]

Hello Klaus,

Thank you for your response.

I did directly update from 3.3.64 to 4.0.17 as it is the latest and only version available. I tried this update on other servers and it worked fine, the CreateUpdateTab step made the database changes.

[JoergAldinger]

Hello Mohamed,

I have noticed the same in previous occasions. In order to proceed I checked the correct column definition in a newer installation and created the columns manually.

You should however open an incident for this so SAP support can try to locate the root cause for this issue.

Hope this helps,

Joerg.

[m_baccar]

Hello Joerg,

Thank you for your response.

I Tried the same trick,but the problem is that i still have the error message which forces me to update my CCO scenario packages "DI Error: (-5002) Tax amount cannot be negative [INV1.VatSum][line: 1]".and the SAP Note 2693418 says that this error is fixed by updating CCO scenario packages according to Note 2163033.

Any other suggestions please?

[Arne_Timmermann1]

m.baccar I would suggest to open an sap support incident so the support and development can solve this issue for everyone, if it is a general problem.