Basis Errors and Solutions

BPE-RUN: Inconsistent data after program termination

July 10, 2009 at 5:41 am

[019] [CANCELLED] [CHECK_PROCESS] [CONTRL] [cpu termination] [FILTER_EVENT_ITEMS] [IDEX] [inconsistent] [IS-U] [program data] [SWF_XI_INBOUND] [termination]

Termination when indexing Data Provider Services (DPS) dataSymptom When indexing Data Provider Services data, the termination “OBJECTS_OBJREF_NOT_ASSIGNED” occurs in the class CL_ESH_DPS_TOOLS method COMPLETE_MES_HANDL_ERR_PROV_DA. Other terms DPS, Data Provider Services, Enterprise Search Reason and Prerequisites See above. Solution o...
Termination when archived data is read from older releasesSymptom When archived data is read from older releases (3.0A up to 3.1G), terminations occur with the short dump CREATE_DATA_UNKNOWN_TYPE, for example. Other terms ADK, data archiving, CREATE_DATA_UNKNOWN_TYPE Reason and Prerequisites The...
Seassion termination with where-used listSymptom When you execute the where-used list, a session termination that cannot be reproduced occurs. You can see from the related C stack trace that the termination occurred in the routine sc_set_tok_att....
Termination in upgrade/EHP update: CREATE_DATA_UNKNOWN_TYPESymptom The termination described below may occur in the following upgrades or phases: Upgrades (for example, SCM 4.1 to SCM 5.0 Version SR2) phase_SHDRUN/ACT_UPG of the EHPI import, or Dictionary activation (for...
Termination in CL_WB_CROSSREFERENCE->SAVE_INDEX, COMMIT WORKSymptom In the method CL_WB_CROSSREFERENCE->SAVE_INDEX, a termination occurs. The exception “OS_COMMIT_WORK_FORBIDDEN” is triggered. Other terms Transaction CO60, find PI sheet, COMMIT WORK, printing, PDF Reason and Prerequisites This problem is caused by...
File display termination in 46C releaseSymptom You are not able to display Archivelink documents. Other terms Document display,Archivelink Reason and Prerequisites This occurs due to a program error. Solution Please implement the following code correction via SNOTE.Alternatively,you...

Symptom

Queues of the form XBQO$PE_WS* or XBPE_WS* are assigned the status SYSFAIL and error message SWF_XI_INBOUND 004: “Permanent error in BPE inbound processing”. You simulate the message delivery in the detailed views of the affected queued remote function call (qRFC) logical units of work (LUWs) and you determine that the delivery was attempted for a process instance that has already been deleted logically.
The affected process definitions use correlations and, immediately after the process start, they use a control step to terminate the process instance again.
Other terms

IS-U, IDEX, CONTRL, FILTER_EVENT_ITEMS, CHECK_PROCESS, SWF_XI_INBOUND 019, CANCELLED
Reason and Prerequisites

After the affected process definitions terminate, inconsistent data is left behind. In particular, the correlation instances of the process instance are not deleted.
Solution

Implement the correction instructions or import the Support Package that is specified in this note. The corrections affect only process instances that are started in the future.
Proceed as follows to correct existing inconsistences in the correlation instances:
1. Determine which process instances are affected.a) Call transaction SE16, enter the table SWWWIHEAD and select the work item type (WI_TYPE) ‘F’ and the status (WI_STAT) CANCELLED. Note the values in the WI_ID column.b) Call transaction SE16, enter the table SWFRCRLINST and select all entries in the WI_ID column that contain the values from step a). To do this, use multiple selection and select single values. This restricts the process instances identified in step a) to those whose correlation instances still exist. Note the values in the column WI_ID for the next step. These values correspond to the IDs of the affected process instances.2. Use transaction SARA and the archiving object WORKITEM to archive the process instances identified in step 1b). Alternatively, use transaction SWWL to delete the process instances.

Unlock the affected queues in status SYSFAIL.