on 2020 Mar 12 3:28 PM
bothreceipts.pngHI SAP experts,507182.png
Currently, i have an issue where sometimes CCO is sending duplicated receipts to SAPB1.
Next, i show you an example
I can see the receipt POS Receipt:BIB1000001002_BIB1100001384 in the monitor with two different id B1, however both are delivered (pictures 507164 and 507182), i dont know what was the reason because the monitor didn´t duplicate any of them and for this error both receipts are in SAP B1 with different No Invoice(picture both receipts). I checked the query SELECT "DataSource" FROM OINV Where "DocEntry" =, and for both receipst the result is 'O' , so for me this error can be a bug because the monitor should differenciate the receipts. The workaround normally is make a Credit Note but i would like to know is someone knows any solution.
I have the following scenario
Cloud Control Center Managment
Version SAPB1: SAP Business One 9.2(9.20.183) PL:0507164.png8 HOTFIX3(64bit)
Version SCCO: 2.0 FP07 PL02
Version SCCO Manager: 2.0 FP07 PL02
Best Regards
Request clarification before answering.
Hello Jhon,
Can you confirm which version of the integration scenario package you are using? There was recently a correction to improve duplicate detection.
Best regards,
Joerg.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I have a client with a new version of CCO.
Any Idea why there are duplicates in the CCO Monitor? This client has plenty duplicates in the CCO monitor
capture.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jhon,
There were some enhancements in the B1if customer checkout scenarios to avoid duplicate receipts in SAP B1.
Please refer to SAP Note #2163033 for further details.
Regards,
Anderson
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.