Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Rushi Joshi
    19D Transaction Console
    Topic posted November 8, 2019 by Rushi JoshiSilver Medal: 2,000+ Points, tagged Approvals, How-To, Requisition Processing 
    93 Views, 11 Comments
    Title:
    19D Transaction Console
    Summary:
    I am trying to generate a test case for each of the status in Transaction Console
    Content:

    Hi,

    Can anyone help me with a test case for a requisition approval so that the approval workflow would fail and eventually end up under Failed status in Transaction Manager. ( Please find Attachment)

    Image:

    Comment

     

    • Ashok

      Hi Rushi

      I will revert on this early next week. I have noted the request and will see what documentation might help assist here.

    • Judy Hamner

      I am interested in the response to this question as well. 

      Judy

    • Maithily Kohale

      Hi Rushi,

      In order for a failed requisition transaction to show in the transaction admin console, the composite instance should encounter what is termed as a "Remote Fault". Unforunately, there is no "functional" way to recreate/ simulate this kind of a fault. It is caused due to technical conditions where the fault occurs and it exhausts all the refresh attempts (5) within the time out period configured internally.

      Thanks,

      Maithily.

    • Rushi Joshi

      Hi Maithily, Thanks for the update.

      Interestingly out of the blue, I was able to see a few transactions under failed status, but it also led to minor confusion since on the left side filter panel it was under "Failed" status but hovering to the red icon it showed "errored", are both the same? (See Screen Capture)

      So these transactions are change orders. From your explanation in the last comment, I am assuming this went into error after it failed technical clearance attempts for more than 5 times (refresh), I am not sure, can that be a reason?

      And so now my question is, what is the refresh frequency between each refresh? I have a transaction (see Screen Capture) which was submitted on 5/11/19 that showed up in the console, to my observation, on 12/5/19!

      Regards,

      Rushi

    • Maithily Kohale

      Hi Rushi,

      1) Yes, the alternate text reads "Errored" for failed transactions - they mean the same - faulted transactions.

      2) These are PO transactions - I cannot be hundred percent certain - but in all likelihood the problem could be the same, meaning an underlying fault that could not get resolved by the system

      About the transaction - Did you mean the transaction was submitted on 5/11 (Nov 5) and came up in TAC as failed on 12/11 (Nov 12)?

      The refresh is kind of cumulative and follows a geometric progression - like 30 mins, an hour... upto 16 hours. This timeout however, is configurable as per my knowledge. I will confirm.

      Thanks,

      Maithily

    • Rushi Joshi

      Hi Maithily,

      I am pretty convinced with the first two points. Many thanks.

      About the transaction - Yes, I suspect that is the case! Is it possible? Because Issue Date and Submitted On date for all the three transactions are the same, however. 

      Regards,

      Rushi

    • Maithily Kohale

      Hi Rushi,

      I confirmed the "configurable" part for development and they informed that it is not configurable.

      Thanks,

      Maithily.

    • Rushi Joshi

      Hi Maithily,

      Thanks,

      Waiting for an update on the "About the transaction " part.

      Regards,

      Rushi

    • Maithily Kohale

      Hi Rushi,

      So, to understand properly - 

      there is a 7 day gap between these transactions submitted and appearing in the TAC portal - and you want to know if this is possible?

      Are you sure they did not appear by the 6th of Nov? As in you viewed them only on 12th?

      I cannot certainly comment unless we have monitored it everyday - isnt it?

      Thanks,

      Maithily.

    • Rushi Joshi

      Hi Maithily,

      Okay! So let me brief you on how we reached this conclusion.

      For the two transactions submitted on 5/11 and 6/11 in the above screenshot, we got exactly the same BPM notifications as in TAC on 12/11 that it has FAILED. Of course, we didn't check every day in TAC before 12/11 but was pretty sure it was not there before. 

      Because our client has not seen any such case earlier before in production, they want to understand two things;

      1) From the description, why this error has occurred.

      2) Why it is notified after a week gap and not anytime earlier?

      We have logged an Oracle SR as well SR 3-21551485701 : Transaction Console - Purchasing Document Approval errors and have an OWC session today along with the business users joining the call. We could reach the solution faster if you can also join the call, if possible since you also actively involved in this.

      Many Thanks,

      Rushi

    • Maithily Kohale

      Hi Rushi,

      Thanks for the explanation - I did not mean to question the info - but definitely wanted to make sure that that was the case :)

      I cannot think of an explanation of the time gap in that case now.

      Thanks,
      Maithily.