on 2023 Feb 15 9:54 AM
Dear Experts,
The matter captioned was recently experienced with in one of customer's environment and want to know how this was happened and how to get rid of this in future transactions . This had happened for several sales . The version they are using is (2.0 FP14 PL02 and Scenario package version is V4.0.46) .
The receipt id is same and date time also same for the seconds .
Please advice .
Thanks and Best Regards,
Tharindu.
Request clarification before answering.
Hi Richard ,
Many thanks for your support given on this so far and yes it sounds good and shall do the needful .
Thanks and Best Regards,
Tharindu .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi tharindu
This is as fair as I can assist with the understanding of the receipt processing mechanism overview.
For a more detailed diagnosis as to what is occurring in your environment you will need raise a support ticket with SAP.
Thanks
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard ,
Greetings for another successful day ..!
Have you got our point and is there any solution and reason for the mentioned matter .
Best Regards,
Tharindu .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard ,
Thanks for your prompt response again . We got the point that you are highlighting is ok but here it's different story . Which is all those duplicate entries were hit after posting the actual receipt and when error message checked all duplicated batches had the same message ,
As you may seen in our screen shot the internal ID is beyond than the already released transaction's internal ID . It seems all other entries hit after posing the original entry successfully . In the screen shot it shows same date and time but in the detail view it shows different times and all duplicate entries with above error message been created after the original receipt which released successfully .
So What do you guess happened here to hit duplicates after posting the original receipt correctly . We guess this is uncommon situation that's why we wanted to highlight it and seek for a solution not to have this kind of matter in future .
Really great if can give a solution on this .
Thanks and Best Regards,
Tharindu .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tharindu Wijesinghe
If you check the cancelled receipts, they will have details as to why they failed to process correctly the first time.
Receipts go through this status process “New -> Released” – and shows a B1 doc ID if successful. With no issue due to Negative Stock, wrong tax code etc.
If the receipt is not successful they will go “New –> Inconsistent” when the Inconsistent transaction is retried it sets the Inconsistent transaction to Cancelled.
Creates a “New” transaction for posting then depending if it is possible to integrate to B1 you will get either “Released/Inconsistent”
Hope this helps with your understanding?
Thanks
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
It's noted and Appreciate your quick response on our query .
But client is asking and we are willing to know why are these duplicate entries are creating because one entry is enough for the posting (Yes those all other are cancelled but why) . And this is not happened for all transaction but few that's why we were confused . So Could you kindly explain us as you mentioned why the system behavior like this for few entries only .
Thanks and Best Regards,
Tharindu .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi tharindu
That is the correct behaviour, if you look on the left receipt status for these duplicate receipts is cancelled, these will keep the same Receipt ID until the status is "Released"
Regards
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
19 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
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.