Bulk Materials Ideas
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
If a user forgets they already entered and posted an Operation and turned around and re-keys the same entry in again, the error message we get directs the user to view some exception journal. If the user is trying to post what amounts to a duplicate record - the error message should clearly indicate this. Better yet, if duplicates are not permitted, Apex should not allow the entry to be saved in the first place. I get a couple calls a month on this problem - and it's always the same - attempting to post a duplicate entry. screen shots attached.
2
Will not implement
Just tried again.
Ran the posting with preview and received the error as expected (Below)
[cid:image001.png@01D45C9C.CC1DDDF0]
I click OK on this message and I am returned right back to the posting screen.
No report/journal screen is automatically displayed.
[cid:image002.png@01D45C9C.CC1DDDF0]
Yes there is something missing. The screenshot you sent was of the Posting Journal not the Exception Report. When you go to File/Select Journal, you won't find the Exception Report there. We do keep a copy in the Journal folder but you can't reprint from the menu.
Here is the process I did, see how yours differs.
Screenshot from posting. Make sure you click the lightning bolt with the magnifying glass.
Then if there is a duplicate, the very next screen I get is:
It is the posting journal and you can see Operation Already in History.
You will only get this report when pressing the lightning bolt (or lightning bolt with the magnifying glass).
Good morning Kristy.
Appreciate the response.
My test entry still exists in our test system, so I tried to post to the screen.
Got the same error as before – as expected.
I didn’t see the exception journal automatically come up.
I did File/Select Journal and the Operation Posting Journal is selected.
I then did File / Reprint Journals – and there is an entry there for my test this morning.
Select Print to Window and select OK.
Here is what I was presented with.
Nothing on here to indicate the problem (Duplicate)
I may be missing something on the way this is to work.
Rich
[cid:image002.png@01D45C8D.FEABC0C0]
Apex posting processes use the exception journal to notify the user of issues. For any posting, there could be more than one exception so that is why exceptions are printed on the journal instead of on the screen.
For consistency, all posting programs work the same way. For example, trying to post a duplicate ticket in Ticket Posting would also produce an exception journal to inform the user that a duplicate ticket is trying to be posted.
One suggestion I would offer is to preview the posting of Plant Operations so if there is an exception, the journal prints on the screen instantly vs. printing to a printer or just saving to a journal file that a user would have to go and find. Posting to the screen will show you all exceptions to that specific posting right at that moment.