06-18-2012 8:39 AM
Expert,
We have implemented Duplicate Check senario which checkes if same POS transaction should not posted twice.
Our clients uses two difrent POS system( diffrent POS Vendors) , so in this case how we will avoid same transaction numbers to be generated by diffrent POS system belongs to diffrent vendor. In this case, if these two POS system generate same POS trabsactions than it will not be called as Duplicate Check.
Any idea or thoughts here .
06-18-2012 11:10 AM
Duplicate check is POS specific or SAP specific scenario.If it is sap specific then spa finds any duplicate entry then it will not process idoc and you will see failure message.
If it is POS specific then you need to develop some custom check where it should check duplicate entry.Check with XI person if he able to insert logic to check duplicate records.
06-18-2012 11:10 AM
Duplicate check is POS specific or SAP specific scenario.If it is sap specific then spa finds any duplicate entry then it will not process idoc and you will see failure message.
If it is POS specific then you need to develop some custom check where it should check duplicate entry.Check with XI person if he able to insert logic to check duplicate records.
06-18-2012 11:33 AM
Hi Prashant ,
Duplicate check in POSDM is not only based on Transaction Number but it considers the other field like store number ,posting date etc.Most of the retalier do not use two different version of the POS at the same store.Hence I do not see the problem as highlighted by you.
Please reward point if useful.
Regards,
Ramki
06-18-2012 1:21 PM
Hi Prashant,
For your case you can use the approach mentioned below to address your issue.
you can enhance the Standard Duplicate check by adding endtime stamp check restriction for Duplicate check.
As the transaction number can be repeated from Different POS system/terminals,but the Start & End Time will not be same for same transaction numbers.
So in the Standard Duplicate check ABAP Code you have to enhance the logic based on END Time Stamp of the transaction to confirm weather the transaction is Duplicate or not ? and also in this logic you have to mention that the End Time Stamp will always be greater then Start Time Stamp of the Transaction.
So in the Standard Duplicate Check code the group key is having(Store ID, Business Date, Transaction Number & Start Time Stamp of Transaction), now to address your issue you have enhance the logic by adding Endtime Stamp into the group Key And validate Duplicate transactions with same numbers with the help of End time stamp of the two same transactions.
For more assistent you can write to me.
This logic will Definitely address your issue.
06-19-2012 8:57 AM
Thank you very much Sridhar , Ram and Anup for your useful answers.Points have been rewarded.
As Anup mentioned, we can change/alter standard Duplicate Check in POSDM and achieve desire results.
Changing ABAP code is good solution here.
Thanks,
06-26-2012 8:34 AM
Hi Prashant,
Hope your issue is resolved and you are done with the change of logic in standard duplicate check?
i hope that endtime stamp logic is working for u and it was was the correct logic?
Thanks,
Anup