Error "Lock not set for: Generate index" while running process chain

SAP BI 7.0
SP 17
I am attempting to run a new process chain and the generate index steps are failing with the below errors:
"Lock NOT set forGenerate index"
"RSSM PROCESS INDEX terminated, because InfoCube/DSO object could not be locked."
The process chain just pauses. I let it finish once and it took 2 hours and then it gave the failure messages. I have looked in sm12 and can see the lock records when the process chain is running - unfortunately I can't make much of what's there - everything looks good to me. I also tried creating the indexes manually inside the cube and then re-ran, but still get the same error. Before running the process chain, I can get the indexes to check to green, but then after running the process chain they go back to red. I have attempted many things (including looking at other forum posts), but I still have the error. Please help. Thanks
Edited by: Brett Hutchinson on Feb 10, 2009 7:50 PM

Hello,
So Create index is getting failed in you PS right?
1)check if any other loads are running to the same CUBE(May be from other PC's also)
Goto Manage of the cube and check, some times it may happen if any Loads are running into cube I mean Load/DTP & roll up may be running.. if so wait till the others Loads(Jobs) get complete then Repeat the failed index
2) If the Create index is running for long time, then got RSDDV--> Select the CUBE then click on BIA index(Maintenance wizard), you can see a message if indexes are running , this will happen only when some one would have tried to generate the indexes manually and it may got failed due to some reason , since u are running it manually u couldn't identify whether it got failed or not unless you got to RSDDV and check. So delete the index here and then rebuild them through PC
Hope it helps!

Similar Messages

DTP error: Lock NOT set for: Loading master data attributes

Hi,
I have a custom datasource from ECC which loads into 0CUST_SALES. I'm using DTP & transformation which has worked for loading data in the past for this infoobject. The infopackage loads with a green status but when i try to load data, the DTP fails with an error message at "Updating attributes for InfoObject 0CUST_SALES Processing Terminated" & the job log says: "Lock NOT set for: Loading master data attributes". I've tried reactivating everything but it didn't help. Does anyone know what this error means? We're on SP7. Thanks in advance!

Hello Catherine
I have had this problem in the past (3.0B) --> the reason is that our system was too slow and could not crunch the data fast enough, therefore packets where loacking each other.
The fix: load the data into the PSA only, and then send it in background from the PSA to the info object. By doing this, only a background process will run, therefore locks cannot happen.
Fix#2: by a faster server (by faster, I mean more CPU power)
Now, maybe you have another issue with NW2004s, this was only my 2 cents quick thought
Good luck!
Ioan

Lock NOT set for: Archiving the data from a data target

Dear Expert,
I try to archive one of my info cube, when i start to write the Archive file the Free Space in the Archive folder not enough and it make the process error.
Then i try to changes the Archive folder to another path with enough free space. But when i start to write the archive file with new variant this error message came up :
==============================================================
An archiving run locks InfoProvider ZICCPS810 (archivation object BWCZICCP~0)
Lock NOT set for: Archiving the data from a data target
InfoProvider ZICCPS810 could not be locked for an archiving session
Job cancelled after system exception ERROR_MESSAGE
==============================================================
Please Help Me.
Wawan S

Hi Wawan,
If the earlier archive session resulted in error, please try to invalidate the earlier session in archive management and try running archive job again.
Hope this helps,
Naveen

Lock NOT set for: Loading master data attributes

Error when running Process chain on a load pls can you advise?
Thanks

Hi,
Probably some other job is running for the same tables,or activation change run is happening.
Check your monitor to see what other jobs are running or check in SM37. Wait till those jobs finish and then try again.
You can also use tcode SM12 to delete any lock entries as well.
Cheers,
Kedar

Error "Object 'DM' (APCO) of type 'Application' is not available in version 'A'" while transporting process chain to production system.

Hi Gurus,
Whenever I try to transport a process chain ZFI_0FIGL_C10 from dev. to qua. & prod. the error “Object 'DM' (APCO) of type 'Application' is not available in version 'A'” is displayed in the end of creating transport package.
The process chain was created to load data to 0figl_c10 and it works all right on all systems (dev. qua. prod.).
The process chain contains processes for:
- starting the process chain
- executing infopackage (for loading data to 0figl_o10),
- ACR (activate data in 0figl_o10)
- delete index 0figl_c10
- DTP loading data from 0figl_o14 to 0figl_c10
- executing infopackage 80FIGL_O10
- creating index in 0figl_c10
- building DB statistics
- rolling up aggregates in 0figl_c10
- deleting of requests from the changelog 0figl_o10
- deleting of requests from PSA (0fi_gl_10)
How to find what cause that error.
Regards,
Leszek

Hi,
A SAP consultant told me to ignore that error.
Indeed, after creating transport with some new process chains (again I was informed about that error "APCO ...") and transporting it to production everything works all right.
The problem is described in sap note: 883745.
Regards, Leszek

How to create process variant for delete index in a process chain

Respected all
I am creating a process chain, but unable to create process variant for the delete index. kindly tell me the
step by step proceure for creating the variant for delete index. also if we use variant which is previously prepared then will it be safe? will it affect the other running process chian.
pls reply
thanks
abhay

Hi,
Please do not use an already created variant for index deletion. It might delete indices of some other cube.
You can follow the following steps -
1. Open the chain in Edit mode and click on "Process Types" button
2. On the Left hand side you will have various process types. Choose "Data Target Administration" and expand it.
3. Choose the first process "Delete Index" (it will be marked with a trash bin sign) and drag it to your chain
4. It will ask you create a variant. Press the create Button
5. In new window enter the Process Variant technical name and description
6. Then in new window choose Object Type = Cube through dropdown and Object name via browsing. After choosing the cube name click on "Transfer Selections"
7. Save and return to your chain
8. It will automatically generate a create index step also after delete index.
9. You need to break the link between create and delete step and insert infopackage in between to get the following steps - delete index --> load cube --> create index.
Please let me know if this is helpful..
Regards
nishant

Error while running Process Chain

Hello all,
I am getting following error while running the process chain.
"Process Activate ODS Object Data, variant PROCESS PSA_TO_ODS_ZFIGL_O1 has status Canceled (instance )".
Due to this others are get affected..
Plz provide solution.
amit

Hello all,
I am getting following error while running the process chain.
"Process Construct Database Statistics, variant DB_STAT_0PY_C02 has status Canceled (instance) ".
Due to this others are get affected..
Plz provide solution.
amit

Lock NOT set for: Loading master data attributes error

Hi experts,
We were encountering this error before when trying to load master data. When we checked the system we could not find any locks at the time, and activation or kicking off the attribute change run failed again. We finally solved the problem running FM RSDDS_AGGR_MOD_CLOSE which sets the close flag to 'X' in table RSDDAGGRMODSTATE. I have read that it is possible this lock error happens when two change runs happen at the same time.
My question are:
1. is it possible to find out what process exactly "caused" the lock? the table RSDDAGGRMODSTATE does not have a reference to any object or job. I am curious as we are trying to find ways to avoid this in the future...
2. in our case, when we could not find any locks, is running this fm the only work around? is this a best practice?
mark
Message was edited by:
Mark Siongco
Message was edited by:
Mark Siongco

Hello Catherine
I have had this problem in the past (3.0B) --> the reason is that our system was too slow and could not crunch the data fast enough, therefore packets where loacking each other.
The fix: load the data into the PSA only, and then send it in background from the PSA to the info object. By doing this, only a background process will run, therefore locks cannot happen.
Fix#2: by a faster server (by faster, I mean more CPU power)
Now, maybe you have another issue with NW2004s, this was only my 2 cents quick thought
Good luck!
Ioan

Lock NOT set for loading masterdata/attributes - already locked

Dear all,
I've searched this forum for similar topics bu couldn't find a solution yet
I'm loading masterdata for 0PERSON but an error appears stating' Master data table or text table already locked'.
I've checked if there is an attribute change run active but there isn't anything, I've executed all of them where necessary.
Transaction RSRV is not showing problems for the info object (No SIDS missing etc)
There are no locked records in SM12/SR12.
I've tried to reload the infopackage and run the DTP again but without success.
Please advice how to unlock the table.
Regards
Markus

Hi,
Just check following
1. Whether there is any active job in SM37 for loading this master data ,if anything triggered manually
2. Check whether any R/3 job is active for this master data
3. Check whether any attribute change run job is active
4. Check whether any roll up /BIA job is running
5. Check consistency of table in SE14 and RSRV for master data
6. Try to manually activate and see if same error is coming?
Also check following thread
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0869e29-1405-2e10-27be-db1dad7703c5?QuickLink=index&overridelayout=true
Thanks and regards

Gr process is not completing for since 2006 while running batch job.

Hi,
we r running batch job and its not delivering material .in po history it showing not in Gr place. plz give reason and solution for this.
Thanks,
Sydanna

hi,
if you have alrady post that doc then pls check in migo- display & check th'r in thaty doc. batch is created or not or check storage location & plant plant also , it th'r is mistake while doing the migo then reverse./ cancle it
next go to in mm01--select that material no - select all the necessary subsereen inculuding plant/ data data store-1 & plant/data stor.1-screen -
click on batch management --& save
after that you do the grn againt of that po
thanks
santosh

Template for Test Scripts in running process chain

Hello all,
I am in urgent need of Test script Template...if any have that pls send one template.I will modify accordingly...
Thanks a lot in advance
my mail id [email protected]
-Venkat

Take a look at this link,not sure what you meant by test scripts...
http://help.sap.com/saphelp_nw04/helpdata/en/67/13843b74f7be0fe10000000a114084/frameset.htm

Temp folder was not set for RTFStringbuffer Error

Hi,
We are using CR XI 11.0.0.895 and CR XI JRC is been used to generate the reports in PDF and RTF format.
While generating report of more than 1000 pages in RTF format throws the below mentioned exception
temp folder was not set for RTFStringbuffer
However, Generating reports in PDF format generates the report.
Find below the environment details which would helpful for the analysis.
CR XI 11.0.0.895
IE 6.0
MS-office 2003
Windows XP SP2
Reports JRC application deployed on Weblogic 8.1.4
Please suggest us a solution for this problem.
Thanks in advance.

If you run [Process Monitor|http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx], do you see any file access errors when the JRC tries creating a temp RTF file?
I think I've recommended this before, but have you tried the newest version of the JRC?
[https://boc.sdn.sap.com/node/19020]
The XI Release 1 keycode will work with it.
Sincerely,
Ted Ueda

Using a Variable in SSIS - Error - "Command text was not set for the command object.".

Hi All,
I am using a OLE DB Source in my dataflow component and want to select SQL Query from the master table I have created variables v_Archivequery
String packageLevel (to store the query).
<Variable Name="V_Archivequery" DataType="String">
     SELECT a.*, b.BBxKey as Archive_BBxKey, b.RowChecksum as Archive_RowChecksum
     FROM dbo.ImportBBxFbcci a LEFT OUTER JOIN Archive.dbo.ArchiveBBxFbcci b
     ON (SUBSTRING(a.Col001,1,4) + SUBSTRING(a.Col002,1,10)) = b.BBxKey
     Where (b.LatestVersion = 1 OR b.LatestVersion IS NULL)
    </Variable>
I am assigning this query to the v_Archivequery variable, "SELECT a.*, b.BBxKey as Archive_BBxKey, b.RowChecksum as Archive_RowChecksum
FROM dbo.ImportBBxFbcci a LEFT OUTER JOIN Archive.dbo.ArchiveBBxFbcci b
ON (SUBSTRING(a.Col001,1,4) + SUBSTRING(a.Col002,1,10)) = b.BBxKey
Where (b.LatestVersion = 1 OR b.LatestVersion IS NULL)"
Now in the OLE Db source, I have selected as Sql Command from Variable, and I am getting the variable, v_Archivequery .
But when I am generating the package and when running I am getting bewlo errror
Error at Data Flow Task [OLE DB Source [1]]: An OLE DB error has occurred. Error code: 0x80040E0C.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E0C Description: "Command text was not set for the command object.".
Can Someone guide me whr am going wrong?
Please let me know where am going wrong?
Thanks in advance.
Thankx & regards, Vipin jha MCP

What happens if you hit Preview button in OLE DB Source Editor? Also you can use the same query by selecting SQL Command option and test.
Could you try set the Delay Validation = True at Package and re-run ?
If set the query in variable expression (not in value), then Set Evaluate As Expression = True.
-Vaibhav Chaudhari

Error "Lead selection not set for context node"

Hi everyone,
I've got a Tree control in WebDynpro ABAP and I've implemented an "expand all" button.
Here's the coding:
METHOD expand_node_rec.
DATA lo_el_child TYPE REF TO if_wd_context_element.
DATA lo_node_children TYPE wdr_context_child_map.
DATA wa_lo_node_children LIKE LINE OF lo_node_children.
DATA lo_nd_child TYPE REF TO if_wd_context_node.
DATA lo_kschl TYPE klschl.
DATA lv_has_children TYPE boolean.
lo_el_child = node->get_element( ).
lo_node_children = node->get_child_nodes( ).
node->get_attribute( EXPORTING name = 'KSCHL' IMPORTING value = lo_kschl ).
node->get_attribute( EXPORTING name = 'HAS_CHILDREN' IMPORTING value = lv_has_children ).
IF lv_has_children = abap_true.
    node->set_attribute( name = 'IS_EXPANDED' value = abap_true ).
ENDIF.
LOOP AT lo_node_children INTO wa_lo_node_children.
    lo_nd_child = wa_lo_node_children-node.
    me->expand_node_rec( node = lo_nd_child ).
ENDLOOP.
ENDMETHOD.
However I'm getting the error above: "Lead selection not set for context node".
Any suggestions?
Edited by: DEVELOPMENT THEMIS on Jul 7, 2011 6:34 PM

hi developement Themis,
I think u didn't diclare "node" as context node. So declare it as a context node before using as a context node..as below
DATA node TYPE REF TO if_wd_context_node.
or u can use "lo_nd_child " as ur context node in ur program in place of "node"
then I think this error will be removed.
thanks,
simadri

JWSDP1.5: wscompile error: "(should not happen): tie.generator.002

Hi all,
I'm working with a doc/lit webservice; I have a WSDL and I'm attempting to generate Java artefacts with wscompile. I'm using JWSDP1.5. I've had a range of errors (I'm updating an old WSDL for the Tentative Hold Protocol, see http://www.w3.org/TR/tenthold-2/). The latest, though, is problematic. The final error message is:
error: generator error: internal error (should not happen): tie.generator.002I have included the full output from wscompile at the end of this posting; I'll post the full WSDL in a reply. Any advice would be much appreciated!
Cheers,
--Tim West
Full output (from wscompile Ant task) - added linebreaks for readability
Buildfile: C:\common\eclipse-projects\thp\build.xml
wscompile-init:
ANEW-generate-server-binding:
[wscompile] command line: wscompile -d C:\common\eclipse-projects\thp\zant-build \
-features:documentliteral,wsi -g -gen:server -keep -verbose \
C:\common\eclipse-projects\thp\server-wscompile-config.xml -classpath (path omitted for readability)
[wscompile] [CustomClassGenerator: generating JavaClass for: userDefinedBody]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdHeader]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestAckHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyResponseChoiceHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyGrantHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdGrantHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyDenialHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdDenialHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationResponseHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusQueryHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseBody]
[wscompile] [CustomClassGenerator: generating JavaClass for: statusStructure]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: userDefinedBody]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdHeader]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdRequestAckHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdGrantHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyGrantHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdDenialHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyDenialHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyResponseChoiceHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdCancellationRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdCancellationResponseHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusQueryHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: statusStructure]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusResponseBody]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusResponseHdr]
[wscompile] error: generator error: internal error (should not happen): tie.generator.002
BUILD FAILED: C:\common\eclipse-projects\thp\build.xml:342: wscompile failed
Total time: 2 seconds

Hi again,
The offending WSDL is below. I should add that I Googled this and couldn't find anything useful. Axis is happy with the WSDL, as is the validator at http://www.soapclient.com/SoapTools.html (though I'm not sure of its quality). I'm now downloading IBM Websphere 6 to see how that goes.
Thanks again,
-Tim West
<?xml version="1.0" encoding="UTF-8"?>
<definitions
    name="TentativeHold"
    targetNamespace="http://www.w3.org/2001/08/thp/definitions"
    xmlns:tns="http://www.w3.org/2001/08/thp/definitions"
    xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema"
        xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
        targetNamespace="http://www.w3.org/2001/08/thp/schemas">
      
      
      
      
      
      
      
      
      <complexType name="holdHeader">
        <sequence>
          <element name="holdID" type="int"/>
          <element name="customerID" type="string"/>
          <element name="replyTo" type="string"/>
          <element name="comment" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
        
      <complexType name="userDefinedBody">
        <sequence>
          <element name="someRequestField" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdRequestHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdRequestAckHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="timeUntilResponse" type="duration"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdGrantHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="holdDuration" type="duration"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdDenialHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="reason" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdModifyRequestHdr">
        <sequence>
          <element name="modifiedHoldRequest" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdModifyGrantHdr">
        <sequence>
          <element name="modifiedHoldRequest" type="holdSchema:holdGrantHdr"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdModifyDenialHdr">
        <sequence>
          <element name="modifiedHoldRequest" type="holdSchema:holdDenialHdr"/>
        </sequence>
      </complexType>
      
      
      
      
      
      
      <complexType name="holdModifyResponseChoiceHdr">
        <sequence>
          <element name="grant" type="holdSchema:holdModifyGrantHdr"/>
          <element name="deny" type="holdSchema:holdModifyDenialHdr"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdCancellationRequestHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
          <element name="customerReason" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdCancellationResponseHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdCancellationNotificationHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
          <element name="cancellationReason" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdStatusQueryHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdStatusResponseHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="statusStructure">
        <sequence>
          <element name="itemHeader" type="holdSchema:holdHeader"/>
          <element name="holdState" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      
      <complexType name="holdStatusResponseBody">
        <sequence>
          <element name="holdItemsCount" type="int"/>
          <element name="itemList" type="holdSchema:statusStructure" minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </complexType>
      
      
      
      
      
      
      <complexType name="holdError">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="holdErrorType" type="int"/>
          <element name="holdErrorDesc" type="string"/>
        </sequence>
      </complexType>
      
      <element name="userDefinedBody" type="holdSchema:userDefinedBody"/>
      <element name="holdRequestHdr" type="holdSchema:holdRequestHdr"/>
      <element name="holdRequestAckHdr" type="holdSchema:holdRequestAckHdr"/>
      <element name="holdGrantHdr" type="holdSchema:holdGrantHdr"/>
      <element name="holdDenialHdr" type="holdSchema:holdDenialHdr"/>
      <element name="holdModifyRequestHdr" type="holdSchema:holdModifyRequestHdr"/>
      <element name="holdModifyGrantHdr" type="holdSchema:holdModifyGrantHdr"/>
      <element name="holdModifyDenialHdr" type="holdSchema:holdModifyDenialHdr"/>
      <element name="holdModifyResponseChoiceHdr" type="holdSchema:holdModifyResponseChoiceHdr"/>
      <element name="holdCancellationRequestHdr" type="holdSchema:holdCancellationRequestHdr"/>
      <element name="holdCancellationResponseHdr" type="holdSchema:holdCancellationResponseHdr"/>
      <element name="holdCancellationNotificationHdr" type="holdSchema:holdCancellationNotificationHdr"/>
      <element name="holdStatusQueryHdr" type="holdSchema:holdStatusQueryHdr"/>
      <element name="holdStatusResponseHdr" type="holdSchema:holdStatusResponseHdr"/>
      <element name="holdStatusResponseBody" type="holdSchema:holdStatusResponseBody"/>
      <element name="holdError" type="holdSchema:holdError"/>
    </schema>
</types>
<message name="HoldRequest">
    <part name="headerHoldRequest" element="holdSchema:holdRequestHdr"/>
    <part name="bodyHoldRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldRequestAck">
    <part name="headerHoldRequestAck" element="holdSchema:holdRequestAckHdr"/>
    <part name="bodyHoldRequestAck" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldGrantResponse">
    <part name="headerHoldGrantResponse" element="holdSchema:holdGrantHdr"/>
    <part name="bodyHoldGrantResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldDenialResponse">
    <part name="headerHoldDenialResponse" element="holdSchema:holdDenialHdr"/>
    <part name="bodyHoldDenialResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldModifyRequest">
    <part name="headerHoldModifyRequest" element="holdSchema:holdModifyRequestHdr"/>
    <part name="bodyHoldModifyRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldModifyResponse">
    <part name="headerHoldModifyResponse" element="holdSchema:holdModifyResponseChoiceHdr"/>
    <part name="bodyHoldModifyResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationRequest">
    <part name="headerHoldCancellationRequest" element="holdSchema:holdCancellationRequestHdr"/>
    <part name="bodyHoldCancellationRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationResponse">
    <part name="headerHoldCancellationResponse" element="holdSchema:holdCancellationResponseHdr"/>
    <part name="bodyHoldCancellationResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationNotification">
    <part name="header" element="holdSchema:holdCancellationNotificationHdr"/>
    <part name="body" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldStatusQueryRequest">
    <part name="headerHoldStatusQueryRequest" element="holdSchema:holdStatusQueryHdr"/>
    <part name="bodyHoldStatusQueryRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldStatusResponse">
    <part name="headerHoldStatusResponse" element="holdSchema:holdStatusResponseHdr"/>
    <part name="bodyHoldStatusResponse" element="holdSchema:holdStatusResponseBody"/>
</message>
<message name="HoldErrorResponse">
    
    <part name="bodyHoldErrorResponse" element="holdSchema:holdError"/>
</message>
<portType name="TentativeHoldServicePortType">
    <operation name="InitiateHold">
      <input message="tns:HoldRequest"/>
      <output message="tns:HoldRequestAck"/>
      
    </operation>
    <operation name="InitiateHoldModify">
      <input message="tns:HoldModifyRequest"/>
      <output message="tns:HoldModifyResponse"/>
      
    </operation>
    <operation name="InitiateHoldCancellation">
      <input message="tns:HoldCancellationRequest"/>
      <output message="tns:HoldCancellationResponse"/>
      
    </operation>
    <operation name="InitiateStatusQuery">
      <input message="tns:HoldStatusQueryRequest"/>
      <output message="tns:HoldStatusResponse"/>
      
    </operation>
</portType>
<portType name="TentativeHoldNotificationServicePortType">
    <operation name="NotifyHoldGranted">
      <output message="tns:HoldGrantResponse"/>
    </operation>
    <operation name="NotifyHoldDenied">
      <output message="tns:HoldDenialResponse"/>
    </operation>
    <operation name="NotifyServerHoldCancellation">
      <output message="tns:HoldCancellationNotification"/>
    </operation>
</portType>
<binding name="TentativeHoldSoapBinding" type="tns:TentativeHoldServicePortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
      <operation name="InitiateHold">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHold"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
      <operation name="InitiateHoldModify">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldModify"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
      <operation name="InitiateHoldCancellation">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldCancellation"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
      <operation name="InitiateStatusQuery">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateStatusQuery"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
</binding>
<service name="TentativeHoldService">
    <documentation> Mythical Tentative Hold Web service</documentation>
    <port name="TentativeHoldPort" binding="tns:TentativeHoldSoapBinding">
      <soap:address location="http://xyz.com/tentativeHold/"/>
    </port>
</service>
<service name="TentativeHoldNotificationService">
    <port name="NotificationPort" binding="tns:TentativeHoldSoapBinding">
      <soap:address location="http://xyz.com/tentativeHoldNotification"/>
    </port>
</service>
</definitions>

Error "Lock not set for: Generate index" while running process chain

Similar Messages

Maybe you are looking for