Skip to main content

Hello,

The Quality Team has requested to store some data that in the standard environment doesn't exist.
In details they want to manage the daily repairs they do during the production.
The repairs are connected to an existing MRB case (Quality Management->Quality Assurance->Material Review Board->Case->MRB Case).

What they need to store (and of course put in a report that will be developed later) is:
1.MRB Number
2.Part number
3.User ID
4.Date

There could be many part numbers in many dates for the same MRB Number. Each of them represent a single row of the table.

For doing this it is necessary to create a new LU, isn't it ?

The new LU has to be inserted into a new tab in the MRB Case LU, taking the field [1] from the header: how to obtain it ? As a parameter ? As a read-only field ?

The field[2] has to be taken from the components of the shop order written in the header: my thought is to create a field type "Reference", but how to select only the rows belonging to the order ?

And finally, how to store the UserID and the system date automatically ?
I know that are a lot of questions.

buongiorno Luca

Custom LU → Yes

You include a field in the LU which is plain text, with the name “MRB_NO” or similar.  Note this has to be plain text, not a reference.  This is the link to the header (defined when you set up the custom tab).

Part number - yes you can make it a reference field.  There is no way to make it only show the parts in the order.  (You can actually, using a saved search on startup, but it is not ideal).

User ID - have a plain text field that defaults to #USER_ID#

Date - have a plain text field that defaults to TO_CHAR(SYSDATE,’yyyy-mm-dd’).  Note that you would ideally make this a date field, but if you do that then you don’t have the default capability.

Thank you Paul, everything is ok now.

Reply


Terms & ConditionsCookie settings