We are working on BIVc4.

Please clarify, I am new to EDM.

We create all items as E-items & then copy these items to item master, through EOBM copy method.

After going live for 10 months , when we open session tiedm1101m000 (Maintain Engineering Item Revisions), there are manufactured items with first revision as base revision & the subsequent revisions through ECO & the ECO number is mentioned against every revision.

The problem is that there are some revision released without an ECO as shown in attached file.

Is this a standard functionality ?

I think system should not allow any change to be done in a EBOM/PBOM without an ECO, once the base revision has been released. Otherwise what is the use of doing ECO for some changes.

I may be wrong, please clarify......

EDM has two areas where changes can be made. Manual or by ECO.
The reason for using ECO is that you can update multiple BOMs with one ECO. You can manually create the EBOM and copy over without an ECO.

Baan IVc3

It is possible to release and copy the revision (of an EBOM) manually. If the user :-

1. Creates new (Manufactured) E-Item revision.
2. Creates EBOM for E-Item Revision.
3. Releases E-Item Revision.
4. Copies E-Item to Item.
5. Generates E-BOM copy data for E-Item/E-BOM Revision.
6. Finalises Engineering data for E-Item Revision. (Finalisation Method - Without ECO)

The above procedure will copy Revisions and BOMs to Standard Items/P-BOMs without an ECO.

Hopes this helps

Thanks for all replies..

My query is why system allows to change EBOM/PBOM without an ECO ?

I think this is debatable in any case !!!!!

You need the ability to make revision changes without ECO's. We use this for numberic-revision items that aren't yet released to production (and therefore aren't under ECO control), but for which we still want control and visibility to change.

I'm not sure, but I think this may be required if you're using small projects, as well, and you're not controlling through ECO's. All revisions originate in EDM. Period.

However, I must agree with your comment. Don't know why I never thought of that myself. Once an item is revised through an ECO it would make sense to restrict all subsequent changes to ECO-only changes.

User access comes into play too. Other than a couple of super users, we only have one or two people with maintenance access to EDM. You should be able to trust those that you've given this access to.

Dear amarpreet,

What you could do is hide all the sessions that allow manual revision release and manual PBOM update from users. One of the most obvious session to hide is "Generate E-BOM copy data (multi-level)". By hiding this, users can only generate such data through "Generate E-BOM copy data by ECO", hence effectively restricting PBOM update to ECO procedure only.

If you'd like, you can even go even further by restricting the access rights to "print/display only" for several other manual revision control sessions such as "Engineering item revisions" and "Engineering BOMs". This would force users to use only their ECO counterparts.

Rgds.
Paul