Agile (MOSC)

MOSC Banner

Agile revisions longer than 3 digits

edited Dec 28, 2017 7:39PM in Agile (MOSC) 3 commentsAnswered

Hello all,

Our business team is exploring options to address a process where they were having some issues. We currently have item revisions of 3 digits (ex. A00) and one of the potential solutions that could help to address the issues was to use a revision number longer than 3 digits. For ex, revision like A00.1. This rule/revision would not be needed on all parts all revisions but only on a small subset.

We are running Agile 9.3.4 connecting to Oracle ERP 12.2.4 via the iLink interface. We ran a few tests in our non-production systems and find them to be working fine. Our interface seems to have inbuilt logic to trim down the revisions to 3 digits and transfer it to Oracle. So Oracle didn't complain. So for a given part, Agile would show the revision as A00.1 and Oracle would show it as A00 only. But we were wondering if anybody out there is using something similar and if any issues were noticed, mainly long term issues.

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center