0% found this document useful (0 votes)
36 views2 pages

INC1663090. INC1663090 Already Yesterday But There Has Not Been An Update On It, Please Review and Advise

The document discusses a critical production issue affecting order processing, requiring urgent resolution and prioritization from the relevant teams. It mentions a scheduled call to address the problem, ongoing updates, and the need for a stable fix to prevent future occurrences. Additionally, it outlines upcoming deployment tasks and deadlines for the V25.2A CHR Release planned for January 9, 2025.

Uploaded by

kittugrepthor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views2 pages

INC1663090. INC1663090 Already Yesterday But There Has Not Been An Update On It, Please Review and Advise

The document discusses a critical production issue affecting order processing, requiring urgent resolution and prioritization from the relevant teams. It mentions a scheduled call to address the problem, ongoing updates, and the need for a stable fix to prevent future occurrences. Additionally, it outlines upcoming deployment tasks and deadlines for the V25.2A CHR Release planned for January 9, 2025.

Uploaded by

kittugrepthor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Thank you @R. Vigneshwaran do you have an ETA of when this will be fixed.

This is a major
production issue as hundreds of orders come through this process. Any update? This issue needs to
be resolved urgently. We are working on it.We will provide you an update on the same.
Please advise. Can you please update on below request. can we get someone to look at this with
priority please Thanks for diving in and finding the culprit. Fingers crossed that the orders run with
no issues now.
I scheduled a call to address the issue It may take a few hours to catchup

Apparently, this scenario was never tested. . This weekly issue needs to stop happening as it affects
our performance to the customer.
Can you please check from your end, if the requests were processed from source system ? And if
required please setup a call with required team, hope priviously you have co-ordinated all relavent
team. So that we can verify end to end flow and will fix the issue .
which are not processed to Oracle Who owns the technical flow end to end? This needs to be
reviewed and a more stable fix put in place immediately. I don’t remember these issues with Q2C

any fix applied from your end ? or reprocessed the requests again ?
Can you check and reprocess them again VP of Operations for awareness of the issue.
Need your support prioritizing the activities to resolve this issue.
Why is this issue happening with more frequency ? this is impacting our ability to recover the plant
Service level and ultimately increasing our Back order value

Can you please confirm if the issue persists? If yes, have you received an error message in your
inbox?
why it got failed as logs were purged from the server.
We have rescheduled once again now.
what was the cause of the block and what can we do to stop this from happening in the future?
Can you get this addressed

we need someone to look at this with priority please INC1663090.


we have not received anything since last Saturday and I created ticket#INC1663090 already
yesterday but there has not been an update on it,

Please review and advise.


Why do we continue to struggle with this flow? Who on the Secure Power side is working this?

We are working on priority and update to you asap.

Any update on this? Need this resolved urgently as this will affect our performance.
Please join the V25.2A CHR Release Feb'25 final gate review to finalize the scope.

Update your CHR & CD status in NRT campaign before the gate review and confirm if any
issue/dependencies moving the changes to production in this weekend.

Production deployment will be scheduled on 9th Jan’25 (Sunday)starting from 8:00 AM IST.

Please check it and let me know if anything is required.


Kindly fill your deployment task details in the below confluence link before EOD ,
so that it can be validated by delivery leads, architects and service owners
before the CAB call.
Note : Kindly make sure you update the JIRA story and deployment task to the
right status and update release version in fix version field (Deployment task).
Make sure that all the documents are uploaded in PI projects folder and also
attached with the deployment task.

Please find attached the final DNP & scope of “V25.2A CHR Release Feb'25” which is planned in this
weekend.

Check and confirm if any technical/functional dependencies, also let us know if any transport
requires downtime.

NRT passed, code review check complete and technically validated changes will be deployed to
production on 9thFeb’25 starting from 8:00 AM IST (Sunday).

You might also like