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.

Install, Upgrade, Clone, Patch - EBS (MOSC)

Clarifications regarding translation synchronization patches.

Oct 9, 2014 4:56AM edited Oct 16, 2014 10:02AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 3 commentsAnswered

Hi,

We would like to get below clarifications regarding translation synchronization patches.

1) TSPs are basically to synchronize the US language file versions with the other languages ie in other words

applying all those patches which we applied on US language in the form of single TSP patch for each language.

Please confirm the same.

2) Recently we applied 8 patches on pre-prod instance and we generated manifest file and have got 15 TSP patches which we are going to apply

in preprod instance.Can we use same TSP patches on production instance or do we need to generate manifest on PROD instance again?

Tagged:

EBS-ATG-Patch

1

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