Can you provide a little more detail on what you are trying to do?
The Project Details tab in the Project Summary page is actually a demand request with an associated workflow. Within the workflow you can create a workflow step that spawns another demand request by using the ksc_copy_request command.
I have done something very similar, but used the ksc_copy_request special command instead. Behind the scenes, it uses the same utility, so this should work. That utility does make the Reference associatioin with the Request entity for the Project, but not the Project entity. This code after the utility code will create the Project reference:
UPDATE KNTA_REFERENCES SET REF_RELATIONSHIP_ID = 403 , SOURCE_ENTITY_ID = 6 , SOURCE_ID = PROJECT_ID , ORIGINAL_SOURCE_ID = PROJECT_ID WHERE SOURCE_ID = P_FROM_REQUEST_ID AND PARAMETER1 = TO_CHAR(O_REQUEST_ID);
UPDATE KNTA_REFERENCES SET REF_RELATIONSHIP_ID = 400 , TARGET_TYPE_CODE = '6' , PARAMETER1 = TO_CHAR(PROJECT_ID) WHERE SOURCE_ID = O_REQUEST_ID AND PARAMETER1 = TO_CHAR(P_FROM_REQUEST_ID);
Isn't there a field group for Project Reference that has to be added to the Request Type Header to allow the reference between the project and the request? What if you added the field group for Project Reference and then populated the field with the project number? Would that create the reference you are looking for?