[Home] [Help]
14102: LAST_UPDATED_BY,
14103: LAST_UPDATE_LOGIN )
14104: values(
14105: l_new_prop_relation,
14106: ENGECOBO.GLOBAL_CHANGE_ID,
14107: 'PROPAGATED_TO',
14108: 'ENG_CHANGE',
14109: p_change_id,
14110: ENGECOBO.GLOBAL_ORG_ID,
14106: ENGECOBO.GLOBAL_CHANGE_ID,
14107: 'PROPAGATED_TO',
14108: 'ENG_CHANGE',
14109: p_change_id,
14110: ENGECOBO.GLOBAL_ORG_ID,
14111: p_organization_id,
14112: null,
14113: null,
14114: sysdate,
15089:
15090: END;
15091: END IF;
15092: -- End changes for bug 3426896
15093: IF (ENGECOBO.GLOBAL_CHANGE_ID <> -1)
15094: THEN
15095: --relationship creation
15096: Create_Relation(
15097: p_change_id => l_eco_unexp_rec.change_id
15098: , p_organization_id => l_eco_unexp_rec.organization_id
15099: , x_Mesg_Token_Tbl => l_mesg_token_tbl
15100: , x_return_status => l_return_status);
15101: -- Fix for Bug 4517503
15102: -- Resetting the global value of ENGECOBO.GLOBAL_CHANGE_ID which is used to
15103: -- detaermine whether a relation is to be created or not.
15104: -- ECO BO is also being called by IOI in the same session when auto-enabling
15105: -- component items and since the value was retained , ended up creating a
15106: -- relationship for NIR.
15104: -- ECO BO is also being called by IOI in the same session when auto-enabling
15105: -- component items and since the value was retained , ended up creating a
15106: -- relationship for NIR.
15107: -- So as to avaoid this it has to be reset once the relation has been created.
15108: ENGECOBO.GLOBAL_CHANGE_ID := -1;
15109: -- End of Fix for Bug 4517503
15110:
15111: END IF;
15112: