on 05-02-2013 10:45 AM
Hi All,
First of all I am new to Open text so forgive if its a silly question
Sometimes the user gets "Suspected Duplicate" as their status for PO invoice ... Suggesting that an invoice document has already been generated.
Now If i see the code , for Post PO invoice , It does a BDC call to MIRO and then updates the open text tables, I checked that when user clicked the first time of Post PO invoice it actually generated the invoice however the open text tables were not updated (by seeing the timestamps on invoice document and workflow step ).
Now why these tables do no get updated if invoice was created is an issue, i checked the lock entries was fine at the moment , also going
through the code it does not have a condition where the table should not be updated ,
these has happened very rarely , I tried a little experiment , After the BDC is completed I exited the code manually
so that the tables do not get update , now the workflow step is still with me (as table were not updated) , so i again clicked
Post PO invoice which again created a invoice document and also updated it the tables ( NO suspected duplicate occur at this moment)
me down to the reason why exactly this suspected duplicates actually occur..
any suggestions what might be actually happening....
any ideas on the above status.. ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Instead of just asking about above status you could for example have added the exact error message to this "suspected duplicates", as this could be used for error analysis.
It is absolutely unclear if you have trouble with Open text storage, then MM would be the wrong forum, or if the error is earlier in invoice entry.
Always remember, the batch input cannot do the extra click by its own, that you can do if you run the batch input in foreground.
you talked as well about batch input. the batch input sessions have usually an error log in which you can see the message along with the message number. Duplicate invoice check is an indicator in vendor master and carried out according to the customizing settings where you define what has to be checked.
If that message requires a confirmation from a user (the batch input cannot do this for the user) then it is just a manually activity for the user. Someone has to monitor the batch inputs and has to care about the sessions with error.
Actually in opentext there is a BDC for MIRO , when user choses to post invoice , this BDC is called after which depending on the success of the BDC , the open text tables are updated with various things like the invoice document number....
what really happened in this scenario of suspected duplicate is that the acounting document for that PO is present already when user tried to post the PO invoice....I checked the accounting document its creation date + time is same as in the workflow log of the first time user executed the step post PO invoice... which gives us the suggestion that the first time user clicked on post po invoice it was successful, however it did not updated the open text tables...
I tried the same case , by successfully creating a invoice document after the BDC and skipping the updation of opentext tables, however i still did not get the suspected duplicate exception when i again tried to post po invoice the second time , it just posted it with a different number and updated it on the second time....
so wanted to know if someone actually knows how this suspected duplicate exception might occur or just have an other opinion what could have occured ... i hope it was clear this time...
BDC logs are saved in a table , however open text always keep the latest log and deletes the previous log , the user executed 3-4 times so the BDC log for the first time is already deleted which would have been helpful.....
one more thing you said that it depends on the vendor master customizing settings , would this setting be for all vendors or specific vendors ? , if only specific vendors are checked then may be i tried with a vendor for which this was unchecked ...
thanks for your help..
Hello,
That check is mandatory in our system, screen field validations over that...
However i was able to reproduce the same suspected duplicates ,
After the post po invoice (skipping the update of open text tables)...
If we run the business rule option it will give us a suspected duplicate and all process would be stopped for that DP document.
Repro'd it but not sure how the user got those errors and that too 2-3 in one month .... less chances of open text tables not being updated because there are not too much conditions over that after the BDC call.
User | Count |
---|---|
91 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.