Item Master Status

[Kumars]

Hi list!

My client want to incorporate item status in the item master. ie., they want to maintain preliminary/pilot/approved status for the item. They might create an item and hold/restrict transactions based on the status of the item.
Is it possible in ECO Module? Or any work around available?

Any suggestion is greatly helped.

 

[Krofire.com]

Good question. You are after a Product Lifecycle Management system aren't you? Gee. I wish that this was simple. This is the kind of thing that the big Pharma Business's would like to see as they have to control Product Release Country by Country as it gets licensed in each region. Such organisations use a sophisticated Document Management system interfaced into PDM, ie, Documentum, Agile, etc.

It usually results in a lot of modified code. I have seen Item Restrictions used to prevent certain Products from being Sold to Customers until it is ready. You can also put these Items into Inventory with the Inventory Status as non-blank and prevent all the other programs from seeing it.

Alternatively you could just use a Category Code.

There is nothing in ECO's that will help you as this only changes the Item's Issue/Version Ref and there is no coding behind that. This is usually the same as a Drawing Issue number or whatever. You could use this but it usually works A, B, C, D etc and is not a true status. It depends what you client wants to do with this status.

The nearest thing to your requirement exists in Equipment, Fixed Assets and Installed Base which uses an Equipment Status field. However, this works at Unit level and probably is not what you are after. Just a thought.

 

[Kumars]

You are right Mark!
I understand that there is no straight solution (probably)available in JDE to achieve this.
Thanks for your thought.

 

[Craig_Potter]

One potential work around is using to security to control who can access
this Item during it's different phases based on a Cat Code.

Not ideal, but may provide some hope.

Regards,

Craig



*********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager ( [email protected])
Important Notice: Berri Limited scans all incoming and outgoing
emails for possible inappropriate content. Procedures to rectify problems with the email system may result in others reviewing
the content of any incoming or outgoing email.
The Berri Limited Email system is for Business use only.
*********************************************************************



Craig Potte

 

[mns_cfpim]

Your business scenario is a fine example of the People - Process - System (technology) interface. Mark and Craig both offer some interesting thoughts. Here are some more that may lead to a workaround:

Create a "logical" Branch/Plant for Research & Development or Engineering, or test, or new product development. Call the new B/P whatever you want, and use it for new product "front end" stuff. Do not create B/P records in the "normal" B/Ps for the new item until it is ready for release.

Control the new item's "status" in the R&D B/P perhaps by some new Lot staus codes that you will define. The status codes can be updated as the item progresses through its life cycle until it is ready for "release". That whole new product development and introduction cycle can be predefined, montored, and controlled by use of the ECO routing process, including creation of regular B/P records after final approval.

This approach may require more discipline than most companies are willing to endure.

In my experience, some clients have attempted to control new product development via one or another 'third party" engineering/design software package. Interfacing that third pary data to JDE has always been a challenge.

A related issue to address involves the questions of who (functionally, not necessarily by employee name) owns and controls the Item master data set for the new item, when does that 'ownership" change, and to whom does it transfer?

Phrased differently, who has access to enter/change Item Master data, and what is the source that authorizes the specific data entry/change?

Clearly, whatever system solution you opt for, you will have to address the people (training & discipline) and process (procedural) requirements.

Good luck.

 

[Larry_Jones]

Here's how we handled this:

We use the Item Flash Status (IFLA) to communicate the status of an item definition / what stage it is at. So a new item starts out with status NI (New Item). If its a manufactured item its next status code will be BR (Bill Required), then RR (Routing Required), then RL (Pending LEadtime Rollup and Review), then CR (Cost Review/Rollup) and finally AA (Finished Item). There are other statuses but you get the picture. Only AA items can be sold / planned.

We have added IFLA to many of the Find/Browse forms so that different people/roles can filter based on Item Status and/or identify the queue of items working for their attention in the definition process.

Regards,

 

[Kumars]

Hi,
Thanks for the valuable ideas.