Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Procurement - EBS (MOSC)

Why our supplier attached to a PO Req purged?

Apr 6, 2016 8:23AM edited Apr 16, 2016 5:01AM in Procurement - EBS (MOSC) 2 commentsAnswered

Dear Procurement Guru:

We are on EBS release 12.1.3

Our purge criteria is to purge records that are older than 31-DEC-2005 last update date....

We implement the Oracle out of the box purge process for AP/PO and supplier this past Sunday, 4/3/2016 in our production.

We had run the same process in our 2 of non production instance before deploying and implementing this process in our production instance.

We came to know on Monday, 4/4/2016 that our business had few PO Requistions that the supplier assigned to them are purged.

We have opened 2 SR SEV1 with Oracle support and have not received the ROOT Cause as of yet.

Tagged:

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month