When using following command to copy request: ksc_copy_request FROM_REQUEST_ID="[TEMP_REQFROM]" REQUEST_TYPE_ID="[TEMP_REQTYPE]" WORKFLOW_ID="[TEMP_WF]" COPY_FIELDS="N" COPY_NOTES="N" CREATE_REFERENCE="Y" REFERENCE_RELATIONSHIP="Child of this Request" SUBMIT="Y"
(all tokens are populated properly for sure – see below)
The following message appears in log:
Beginning command: KSC Copy Request Running PL/SQL procedure KCRT_REQUEST_UTIL.COPY_REQUEST Summary of parameters: FROM_REQUEST_ID=30337 REQUEST_TYPE_ID=30431 WORKFLOW_ID=30573 COPY_FIELDS=N COPY_NOTES=N CREATE_REFERENCE=Y REFERENCE_RELATIONSHIP=Child of this Request STATUS_NAME= SUBMIT=Y PROCESS_RULE=N Request copied successfully with new ID = 0
And the request is not being created.
FROM_REQ, REQ_TYPE and WORKFLOW exist for sure (partial results – not all columns shown):
select * from kcrt_requests r WHERE request_id = 30337 REQUEST_ID CREATION_DATE CREATED_BY LAST_UPDATE_DATE LAST_UPDATED_BY ENTITY_LAST_UPDATE_DATE REQUEST_NUMBER REQUEST_TYPE_ID 30337 05-11-2010 14:32:31 104329 05-11-2010 14:32:31 104329 05-11-2010 14:32:31 30337 30431
select * from kcrt_request_types t WHERE request_type_id = 30431 REQUEST_TYPE_ID CREATION_DATE CREATED_BY LAST_UPDATE_DATE LAST_UPDATED_BY 30431 05-11-2010 06:45:06 100304 05-12-2010 09:27:10 104329
thank you for your reply. I have seen your solution in previous posts. I am considering this as a workaround if everything else fails. I want to ensure why this solution is not working in one of our environments (in other works fine). I have already submitted case in HP, but sometimes (often) Forum response is faster ;)
hey, are you trying to copy a request which uses Field Groups : PFM Proposal or PFM Projects. If so try disabling financial summary, staffing profile and Approved Proposal Snapshot in your target request type and it will work. Let me know..
I had a similar problem a couple of days ago. Do you have installed a language Pack? In this case you must change the REFERENCE_RELATIONSHIP to a localized value. However additional to your command I set the STATUS_NAME.
thank you for your replies. I've tried to add Administrators security group to step where ksc_create_request command is used and additionally add STATUS_NAME (with value) to this command, however commands executed by workflow_timeout_service still do not properly execute and request is not being copied.
Did you ever get a satisfactory answer from HP on the case that you sumbmitted on this issue?
I am hitting the same issue. I have a workflow that uses the ksc_Copy_Request command. The same step can be used to create different request types. Out of three (3) request types that the step can create, two of them are created without an issue, the third always fails.
All three request types use the same header which uses the Demand SLA and Demand Scheduling groups fields.
We had the same problem. Only one request type could not be created. We finally noticed that the parent and child had one detail field in common that were incompatible. In the parent, it was defined as Text Area - 1800 and assigned to Parameter41. In the child request, the assignment type was also defined as Text Area - 1800 but it was assigned to Parameter2 which is limited to 200 characters. When the value in the parent request was longer than 200 characters, the child was not created.
Just to confirm, there was one field that shared parameters but used different validations. There were both dropdown validations but one used TRUE/FALSE in the 'code' column and the other used Y/N. Enough of a difference to cause the ksc_copy_request to fail.
sorry for the delay in response but I was out of office. Our problem was quite different - we use timeout to create requests on regular basis (e.g. once per week). In that case these new requests are being created by workflow_timeout_service user. Unfortunately this user does not have rights (licenses, access grants) to perform such operation. HP classified this as a bug. As a workaround you can add liceses and access grants for this user directly in DB, as it cannot be done in Workbench.