Genealogy A genealogy is a parent-child relationship between the lot or serial number of the assembly and the lot or serial

number of the components. Setup Create an assembly item . Assembly has to be a predefined serial controlled item. Create component item. Component can be either predefined or dynamic at receipt serial control. Create BOM and Routing for the assembly. Create a wip discrete job Building Genealogy. The child serial numbers can be linked to the parent serial when issuing material and at backflush operations. For eg. While doing a WIP component issue associate the parent Serial with the child serial number.

After WIP component issue is done, the serial genealogy looks like this.

Here the association of the child serial SH1 with the parent serial SP1 can be viewed in Parent Details tab. So far genealogy for the parent serial SP1 is not built in table mtl_object_genealogy (MOG). Querying on the parent serial SP1 will show its children serials, namely , the serials associated at the time of component issue.

On performing completion transaction, genealogy for parent serial SP1 also gets built.

Now the parent of the assembly serial SP1 is the job number. Breaking genealogy If genealogy is built during WIP component issue, similary genealogy should be broken While returning the component back to inventory ie during a WIP component return. This is done by end - dating the genealogy record in table mtl_object_genealogy. Now the serial can be associated with a different parent serial or the same parent serial and genealogy gets built accordingly. This functionality was handled in ER 2821257 Tracking Genealogy For proper tracking of genealogy the profile INV:Restrict Receipt of serials should be set to yes. This profile will restrict the re-use of serials. For example if this profile is set To yes and a serial has been issued out of stores through WIP component issue, the serial can be brought back to inventory through WIP component return only. The serial cannot be re-used through misc receipts. If this profile is not set to yes there could be duplicate records in MOG which might cause problems in Installed Base.

Refer bug 1481445 for details on this profile. Table Information The table mtl_object_genealogy is used for storing genealogy information. Some important columns are
select OBJECT_ID , OBJECT_TYPE , PARENT_OBJECT_TYPE , PARENT_OBJECT_ID , START_DATE_ACTIVE , END_DATE_ACTIVE , ORIGIN_TXN_ID , GENEALOGY_TYPE , GENEALOGY_ORIGIN from mtl_object_genealogy

Here object_id is the gen_object_id from mtl_serial_numbers and parent_object_id is the Object_id of the parent serial number. The column end_date_active is populated when genealogy is broken. Table mtl_object_events which was used for storing information about major events on the serial is no more used in 11.5.9 . ARU 2751179. Code Code for inserting genealogy is handled in inltis.ppc. Pseudo code looks like If ( WIP component issue) then MTL_OG_UTIL_PKG.GEN_INSERT() Else if ( WIP assembly completion) then INV_GENEALOGY_PUB.INSERT_GENEALOGY() Else if ( WIP component return ) mtl_og_util_pkg.gen_update() MTL_OG_UTIL_PKG -- INVOGUTS.pls INV_GENEALOGY_PUB -- INVPVCGB.pls The code corresponding to inltis.ppc in java is handled in SerTrxManager.java