BDOC Error : "BDoc stored before update task (intermediate state)"

Hi Experts,
I have stuck BDOCs under BDOC type "BUS_TRANS_MSG" and the error msg as "BDoc stored before update task (intermediate state)". The error occurs when BDoc Message was not written to qRFC queue. I checked the update tasks in transaction
SM13 and could find the entries there. I opened one of the entry and was able to spot the error in one of the function module.
The error was encountered at some later point in time and is been fixed. I now want to re-send the update so that the new update is written and the BDOCs are processed.
Kindly guide me through the steps that need to be performed in order to re-process the BDOCS.
Thanks,
Chaudh

Hi,
BDocs were stuck at time when we really had a problem; now the problem is re-solved. I have checked SM13 we have entries highlighting the problem, but i really don't know how to re-update the error entries in SM13.
I believe once that is done then i might possibly be able to re-process the BDOCs in SMW01.
Thanks,
Chaudh

Similar Messages

BDoc stored before update task (intermediate state)

Hi Experts,
I see every month 2 to 3 messages in SMW01 with status I04. I have cheked many blogs and they suggest to check in SM13. But on our system i don't see any messages in SM13. Also these messages doesnot display what the error is through Tcode SM13.
Can you please help me to find a solution for this messages.
regards,
Vicky

Hi Rohit,
Thanks for the information. I need some more info.
These are all :mBDoc Notification
We have not received any update error so far for any BDocs which can relate to these messages.
But these messages keeps on failing. I am still confused, if the update was done successfully how can these BDocs failed?
Or is it like these are just warning messages and its says that your inbound BDocs were successfully stored in the database but since these inbound BDocs were stored before the update operation could be performed, the system generates this warnings?
If so can you please help me understand the followings:
1. How come BDocs getting processed successfully if the update only fails? Are these two different things. I wanted to know the flow of message.
example:
message -> CRM ->update operation -> Data save to CRM database or others like mobile database.
How the flow of message is when it enters CRM system?
2.Also you have mentioned that there will be an inbound BDocs too for the same message. Do the inbound BDoc will have same BDoc Message ID or how can i verify that the BDoc corresponding to all these BDocs with I04 status has been successfully processed. I check with the BDoc message ID and it has only one BDoc in SMW01 i.e these errors.
Thanks,
Vicky

BDOC Stored before update task error

Hi Experts,
I am using FM CRMXIF_PRODUCT_MATERIAL_SAVE to update one of the custom aatributes in COMMPR01.
once i run this FM i see an entry of bdoc in SMw01 with the below error
"BDOC stored before update task(intermediate state).
I checked ST22 and i saw no dumps, i checked Sm13 and i didnt see any update tasks. Cananyone help me?
Thanks!

HI Divya,
BDoc Message was not written to qRFC queue, yet. Search for update tasks in transaction
SM13. The sender creates a BDoc message to post data to the receivers. The application
calls the messaging flow.
Detection:
Check if there are any update terminations which occurred in the update task
by using transaction SM13. Check if there are inbound messages related to
that outbound message, double-click u2018Original BDocu2019 field to display the
original inbound message. Typically the inbound message (s-BDoc in flow
context SI1 or m-BDoc in flow context MI0) is already on a final state F02, i.e.
the validation was successful but the asynchronous update failed. The
original inbound message in final state might have been already reorganized.
Solution:
Solve the problem with the open update tasks and then execute them again
in SM13. Check whether after succesful reexecution in SM13 the BDoc state
has been changed.
If not, or if you donu2019t find any open updates, but you do find a corresponding
original message, proceed as following:
· Variant 1: Try to reprocess the inbound message to check if the newly
created outbound message has also status I04. If BDoc is processed, no
retry of the failed BDoc is allowed. Set the message as deleted.
Reprocessing the related inbound message is sometimes not possible,
because the state is final. In this case copy the inbound message using
transaction SMW19 and set the new state of the copied message to I01.
Then you can reprocess it.
· Variant 2: Use the solution from SAP notes 876855 (CRM 3.X) or 835761
(CRM 4.0) to convert the inbound s-BDoc into an error state E09.
Advantage is, that in this state the inbound message does not get
reorganized. More important, it also allows you to restart the inbound
processing after the error situation has been resolved. However, in that
case you need to delete the already pending update tasks from the
previous run in transaction SM13.
When there are no open update tasks anymore, check whether the data
changes according to the inbound BDoc message have actually been posted
to the CRM online application tables. If the changes are present (i.e. a new
application object was succesfully created), you should not use variant 2,
because you might get a problem of posting the same data again (i.e. getting
an "insert duplicate record" situation).
For more info about error analysis. please refer to
http://saptricks.com/wp-content/uploads/2010/05/BestPractice-BDoc-Analysis-V2.pdf
Cheers, Satish

Error Handling for Background/Update Tasks (Transfer Order creation) - How?

Hi,
I have a standard process for creating a Transfer Order and 2 user-exits that I have implemented.
The user exits are used to transfer information during Transfer Order creation.
However, the user-exits also check data in table TVARV and other. As such, error handling needs to be implemented, since the T.O. might or might not go through, depending on data validation and related.
However, the user-exits are implemented during creation, which is an update task that runs in the background. This makes it impossible to output any information or error messages.
What else can be done in regards to outputting a message, since the user will need to see some sort of message that the process failed, that the T.O. didnu2019t confirm? Can an SAP inbox message be created and how?
Please help.
Thank You,
John

Hi,
Please check the following link for all the function modules and user exits on TOs.
http://help.sap.com/saphelp_erp2005/helpdata/EN/c6/f83a294afa11d182b90000e829fbfe/content.htm
Reward points if it was helpful.
Regards
Abhishek
Edited by: Abhishek Raj on May 29, 2008 10:20 AM

Getting Error when Trying To Update Task Payload

Hi,
I am calling updateTask() operation of TaskService to update one of my task's payload...
url : http://host:port/integration/services/TaskService/TaskServicePort
request payload :
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/taskService">
<ns1:updateTask xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/common" xmlns:ns3="http://xmlns.oracle.com/bpel/workflow/task">
<ns2:workflowContext>
<ns2:credential>
<ns2:login>weblogic</ns2:login>
<ns2:password>weblogic11g</ns2:password>
</ns2:credential>
</ns2:workflowContext>
<ns3:task>
<ns3:title>task for PUR Req 700</ns3:title>
<ns3:payload>
<NewBusinessObject
xmlns="http://xmlns.oracle.com/bpm/bpmobject/NewModule/NewBusinessObject">
<pur_sk_seq>700</pur_sk_seq>
<comment>modified comment</comment>
</NewBusinessObject>
</ns3:payload>
<ns3:systemAttributes>
<ns3:taskId>97c2ec0c-0c45-46be-92d5-9a8527f2ae69</ns3:taskId>
</ns3:systemAttributes>
</ns3:task>
</ns1:updateTask>
</soap:Body>
</soap:Envelope>
But I am getting below error in response :
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:env:Receiver</faultcode>
<faultstring/>
<faultactor/>
<detail>
<operationErroredFault
xmlns="http://xmlns.oracle.com/bpel/workflow/taskService">
<faultInfo
xmlns="http://xmlns.oracle.com/bpel/workflow/taskService">UPDATE</faultInfo>
</operationErroredFault>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
Please note : my task parameters are editable.
Can someone please help on this issue?
Thanks,
Debdeep

This issue got resolved using the below payload...basically you will need to update the task with all other task details that you will get in response from getTaskDetailsById() or getTaskDetailsByNumber()...
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/taskService">
<ns1:updateTask xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/common" xmlns:ns3="http://xmlns.oracle.com/bpel/workflow/task">
<ns2:workflowContext>
<ns2:credential>
<ns2:login>Niloy</ns2:login>
<ns2:password>welcome1</ns2:password>
<ns2:identityContext></ns2:identityContext>
</ns2:credential>
</ns2:workflowContext>
<task xmlns="http://xmlns.oracle.com/bpel/workflow/task">
<title>Order approval/ Rejection task</title>
<payload>
<process xmlns:ns1="http://xmlns.oracle.com/SOAPOC/HTTest/OrderFetcher" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns="http://xmlns.oracle.com/SOAPOC/HTTest/OrderFetcher">
<ns1:OrderId>122122</ns1:OrderId>
<ns1:Ordername>Ravi Kishore</ns1:Ordername>
<ns1:OrderDate>02-Sept-1952</ns1:OrderDate>
</process>
</payload>
<taskDefinitionURI>default/HTTest!1.0*soa_a3451776-9472-47f1-968c-9498feeefc65/OrderDecider</taskDefinitionURI>
<creator>weblogic</creator>
<ownerUser>weblogic</ownerUser>
<priority>3</priority>
<identityContext>jazn.com</identityContext>
<processInfo/>
<systemAttributes>
<assignedDate>2012-08-30T20:22:05+01:00</assignedDate>
<assigneeUsers>
<id>niloy</id>
<displayName>niloy</displayName>
<type>user</type>
</assigneeUsers>
<createdDate>2012-08-30T19:40:46+01:00</createdDate>
<customActions>
<action>APPROVE</action>
<displayName>Approve</displayName>
</customActions>
<customActions>
<action>REJECT</action>
<displayName>Reject</displayName>
</customActions>
<digitalSignatureRequired>false</digitalSignatureRequired>
<displayInfo>
<applicationName>worklist</applicationName>
<hostname>jcapsmigration</hostname>
<httpPort>7001</httpPort>
<httpsPort>0</httpsPort>
<uri>/workflow/HTForm/faces/adf.task-flow?_id=OrderDecider_TaskFlow&_document=WEB-INF/OrderDecider_TaskFlow.xml</uri>
</displayInfo>
<fromUser>
<id>weblogic</id>
<displayName>weblogic</displayName>
<type>user</type>
</fromUser>
<hasSubTasks>false</hasSubTasks>
<inShortHistory>false</inShortHistory>
<isGroup>false</isGroup>
<numberOfTimesModified>5</numberOfTimesModified>
<passwordRequiredOnUpdate>false</passwordRequiredOnUpdate>
<pushbackSequence>INITIAL_ASSIGNEES;1</pushbackSequence>
<secureNotifications>false</secureNotifications>
<shortHistory>
<task>
<state>ASSIGNED</state>
<updatedBy>
<id>weblogic</id>
<type>user</type>
</updatedBy>
<updatedDate>2012-08-30T19:40:46+01:00</updatedDate>
<version>1</version>
<versionReason>TASK_VERSION_REASON_INITIATED</versionReason>
</task>
<task>
<state>ASSIGNED</state>
<updatedBy>
<id>weblogic</id>
<type>user</type>
</updatedBy>
<updatedDate>2012-08-30T19:47:34+01:00</updatedDate>
<version>2</version>
<versionReason>TASK_VERSION_REASON_UPDATED</versionReason>
</task>
</shortHistory>
<state>ASSIGNED</state>
<substate>REASSIGNED</substate>
<systemActions>
<action>UPDATE_COMMENT</action>
</systemActions>
<systemActions>
<action>VIEW_SUB_TASKS</action>
</systemActions>
<systemActions>
<action>DELEGATE</action>
</systemActions>
<systemActions>
<action>SUSPEND</action>
</systemActions>
<systemActions>
<action>UPDATE</action>
</systemActions>
<systemActions>
<action>UPDATE_ATTACHMENT</action>
</systemActions>
<systemActions>
<action>ESCALATE</action>
</systemActions>
<systemActions>
<action>VIEW_PROCESS_HISTORY</action>
</systemActions>
<systemActions>
<action>REASSIGN</action>
</systemActions>
<systemActions>
<action>VIEW_TASK</action>
</systemActions>
<systemActions>
<action>CUSTOM</action>
</systemActions>
<systemActions>
<action>INFO_REQUEST</action>
</systemActions>
<systemActions>
<action>VIEW_TASK_HISTORY</action>
</systemActions>
<taskId>e1d269a0-a9ae-4ad5-b52d-e5a381d32f15</taskId>
<taskNumber>200040</taskNumber>
<updatedBy>
<id>niloy</id>
<displayName>niloy</displayName>
<type>user</type>
</updatedBy>
<updatedDate>2012-08-30T20:34:31+01:00</updatedDate>
<version>5</version>
<versionReason>TASK_VERSION_REASON_UPDATED</versionReason>
<taskDefinitionId>default/HTTest!1.0*soa_a3451776-9472-47f1-968c-9498feeefc65/OrderDecider</taskDefinitionId>
<taskDefinitionName>OrderDecider</taskDefinitionName>
<workflowPattern>Participant</workflowPattern>
<isTestTask>false</isTestTask>
<participantName>Order Master</participantName>
<assignees>
<id>niloy</id>
<displayName>niloy</displayName>
<type>user</type>
</assignees>
<rootTaskId>e1d269a0-a9ae-4ad5-b52d-e5a381d32f15</rootTaskId>
<systemStringActions>PUSH_BACK,sharePayload</systemStringActions>
<stage>Stage1</stage>
<isTemplateTask>false</isTemplateTask>
<taskViewContext>Transferred</taskViewContext>
<taskNamespace>http://xmlns.oracle.com/SOAPOC/HTTest/OrderDecider</taskNamespace>
<actionDisplayName>Task Updated</actionDisplayName>
<componentType>Workflow</componentType>
<thread>0</thread>
<parentThread>0</parentThread>
</systemAttributes>
<systemMessageAttributes/>
<callback>
<id>OrderFetcher/OrderDecider.TaskService</id>
<converstationId>urn:27E63DC0F2D211E1BFFD9DA87F46F90F</converstationId>
</callback>
<isPublic>false</isPublic>
<sca>
<applicationName>default</applicationName>
<componentName>OrderDecider</componentName>
<compositeDN>default/HTTest!1.0*soa_a3451776-9472-47f1-968c-9498feeefc65</compositeDN>
<compositeInstanceId>110001</compositeInstanceId>
<compositeName>HTTest</compositeName>
<compositeVersion>1.0</compositeVersion>
<ecId>11d1def534ea1be0:-d4d1dba:13978b478c7:-8000-0000000000000800</ecId>
<parentComponentInstanceId>bpel:70001</parentComponentInstanceId>
<parentComponentInstanceRefId>70001-BpInv0-BpSeq1.6-2</parentComponentInstanceRefId>
<compositeCreatedTime>2012-08-30T19:40:09.461+01:00</compositeCreatedTime>
</sca>
<taskDefinitionId>default/HTTest!1.0*soa_a3451776-9472-47f1-968c-9498feeefc65/OrderDecider</taskDefinitionId>
<correlationId>e1d269a0-a9ae-4ad5-b52d-e5a381d32f15</correlationId>
<mdsLabel>soa_a3451776-9472-47f1-968c-9498feeefc65</mdsLabel>
<creatorDisplayName>weblogic</creatorDisplayName>
<ownerUserDisplayName>weblogic</ownerUserDisplayName>
<customAttributes>
<customAttributeNumber1>0.0</customAttributeNumber1>
<customAttributeNumber2>0.0</customAttributeNumber2>
</customAttributes>
</task>
</ns1:updateTask>
</soap:Body>
</soap:Envelope>

Mutating error : row level BEFORE UPDATE trigger

Hi,
I had an issue on mutating terror(was trying to write a row level BEFORE update trigger), however i got it resolved after refering tom kytes web site. I thought i would share it with everyone, might be helpful for a few... Thanks!
I will be more than happy to learn on further better ways of resolving this issue.
Below I have posted the trigger that was causing this error and the work around for that issue, I created a package and three other triggers to replace row level BEFORE update trigger:
++trigger that was causing this issue:++
CREATE OR REPLACE TRIGGER C_F_BI
BEFORE INSERT ON CONTACT_FUNCTION FOR EACH ROW
declare
cursor function_code_cur ( cur_contact_id CONTACT.Contact_Id%type,
cur_function_type_code CONTACT_FUNCTION.Function_Type_Code%type)
is
select
cft.function_type_code,
cft.multiples_permitted
from
CONTACT_FUNCTION cf,
CONTACT c,
CONTACT_FUNCTION_TYPE cft
where
c.acct_id = (select acct_id from contact where contact_id = cur_contact_id)
and c.contact_id = cf.contact_id
and cf.function_type_code = cft.function_type_code
and cft.function_type_code = cur_function_type_code;
v_function_type_code contact_function_type.function_type_code%type;
v_multiples_permitted contact_function_type.multiples_permitted%type;
E_Multiples_Not_Permitted Exception;
begin
if not function_code_cur%isopen then
open function_code_cur(:new.contact_Id,:new.function_type_code);
end if;
loop
fetch function_code_cur into v_function_type_code, v_multiples_permitted;
exit when not function_code_cur%found;
end loop;
** if the fetch returns a v_multiples_permitted of 'Y' or no record is found, then it is
** ok to add the record. Otherwise raise an error because that function_type is already
** being used at the current acct.
if v_multiples_permitted = 'N' then
raise E_Multiples_Not_Permitted;
end if;
close function_code_cur;
EXCEPTION
when E_Multiples_Not_Permitted then
raise_application_error( -20001,'Multiples not allowed for function type ' ||
v_function_type_code || '. sqlerrm - ' || sqlerrm );
when others then
raise;
end;
++solution for above issue :++
create or replace package state_pkg
is
type ridArray_rec is record(rid rowid, cont_id number, cont_fn_type varchar2(20));
type ridArray is table of ridArray_rec index by binary_integer;
newRows ridArray;
empty ridArray;
end state_pkg;
create or replace trigger contact_function_bu1
before update on contact_function
begin
state_pkg.newRows := state_pkg.empty;
end;
create or replace trigger contact_function_bu2
before update ON CONTACT_FUNCTION FOR EACH ROW
DECLARE
I NUMBER:=0;
begin
I := state_pkg.newRows.count+1;
state_pkg.newRows( I ).rid := :new.rowid;
state_pkg.newRows( I ).cont_id := :new.contact_id;
state_pkg.newRows( I ).cont_fn_type := :new.function_type_code;
end;
create or replace trigger contact_function_bu
after update ON CONTACT_FUNCTION
declare
cursor function_code_cur ( cur_contact_id CONTACT.Contact_Id%type,
cur_function_type_code CONTACT_FUNCTION.Function_Type_Code%type,
rid2 rowid)
is
select
cft.function_type_code,
cft.multiples_permitted
from
CONTACT_FUNCTION cf,
CONTACT c,
CONTACT_FUNCTION_TYPE cft
where
c.acct_id = (select acct_id from contact where contact_id = cur_contact_id)
and c.contact_id = cf.contact_id
and cf.function_type_code = cft.function_type_code
and cft.function_type_code = cur_function_type_code
and cf.rowid = rid2;
v_function_type_code contact_function_type.function_type_code%type;
v_multiples_permitted contact_function_type.multiples_permitted%type;
E_Multiples_Not_Permitted Exception;
begin
for i in 1 .. state_pkg.newRows.count loop
if not function_code_cur%isopen then
open function_code_cur(state_pkg.newRows(i).cont_id, state_pkg.newRows(i).cont_fn_type, state_pkg.newRows(i).rid);
end if;
loop
fetch function_code_cur into v_function_type_code, v_multiples_permitted;
exit when not function_code_cur%found;
end loop;
** if the fetch returns a v_multiples_permitted of 'Y' or no record is found, then it is
** ok to add the record. Otherwise raise an error because that function_type is already
** being used at the current acct.
if v_multiples_permitted = 'N' then
raise E_Multiples_Not_Permitted;
end if;
close function_code_cur;
end loop;
EXCEPTION
when E_Multiples_Not_Permitted then
raise_application_error( -20001,'Multiples not allowed for function type ' ||
v_function_type_code || '. sqlerrm - ' || sqlerrm );
when others then
raise;
end;
/

It seems you could have solved the issue otherwise:
CREATE OR REPLACE TRIGGER c_f_bi
   BEFORE INSERT
   ON contact_function
   FOR EACH ROW
DECLARE
   v_function_type_code        contact_function_type.function_type_code%TYPE;
   v_multiples_permitted       contact_function_type.multiples_permitted%TYPE;
   e_multiples_not_permitted   EXCEPTION;
BEGIN
   BEGIN
      SELECT cft.function_type_code, cft.multiples_permitted
        INTO v_function_type_code, v_multiples_permitted
        FROM contact c, contact_function_type cft
       WHERE c.acct_id = (SELECT acct_id
                            FROM contact
                           WHERE contact_id = :NEW.contact_id)
         AND c.contact_id = :NEW.contact_id
         AND cft.function_type_code = :NEW.function_type_code;
   EXCEPTION
      WHEN NO_DATA_FOUND
      THEN
         v_function_type_code := :NEW.function_type_code;
         v_multiples_permitted := '?';
   END;
** if the query returns a v_multiples_permitted of 'Y' or no record is found, then it is
** ok to add the record. Otherwise raise an error because that function_type is already
** being used at the current acct.
   IF v_multiples_permitted = 'N'
   THEN
      RAISE e_multiples_not_permitted;
   END IF;
EXCEPTION
   WHEN e_multiples_not_permitted
   THEN
      raise_application_error (-20001,
                                  'Multiples not allowed for function type '
                               || v_function_type_code
                               || '. sqlerrm - '
                               || SQLERRM
   WHEN OTHERS
   THEN
      RAISE;
END;
/:p

Bdoc Error

Hi All,
We are using CRM 4.0. Since last few days, Bdoc of type BUS_TRANS_MSG has started failing.It is in the state Technical Error(incomplete).
In the error log, it is giving below error
"Document Not Found" (CRM_ORDER000)
"Service that caused the error: CRM_UPLOAD_BW_SRV" (SMO8047)
What is the issue behind this? I am not able to investigate. Please HELP.
Regards
Shailesh Jadhav

Hi Shanthala,
Thanks for your suggestions.
Yes the documents are distributed to R/3. This functionality is there since day one . But ealier, if the document is locked then we used to check the Bdoc and it used to be in "Intermediate" state. Once the Bdoc is processed then then document was editable.
But now the Bodc is going in error state and not able to reprocess. I have already tried to unlock the document using report CRM_CHECK_DISTRIBUTION_STATUS. The document get unlocked. Then again if I make any changes to the document and save it, it again generated the new Bdoc and it goes in error state making the document locked again.
Where are we suppose to set the Distribution Flag at header level? I don't know. Can you please tell me.
I want to know that for my knowledge.
Also I think that the my client needs the document to be distributed in R/3 hence they might have activated the distribution.
Regards,
Shailesh Jadhav

OIM: Error while updating Task Attributes

Hi All,
I am trying to use PeopleSoft User Management using OIM connector.
I am facing an error saying "problem in updating Task Attributes" while scheduling a task on OIM design Console. I am trying to update and save PSFT Base Non Trusted User Reconciliation. following is the log message displayed in server command prompt.
ERROR,11 Apr 2008 05:02:53,287,[XELLERATE.SERVER],Class/Method: tcTSA/eventPostU
pdate encounter some problems: problem in updating Task Attributes
com.thortech.xl.scheduler.exception.SchedulerGenericException: problem in updati
ng Task Attributes
at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.updateTaskA
ttributes(Unknown Source)
at com.thortech.xl.scheduler.ejb.SchedulerControllerBean.updateTaskAttri
butes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerControllerSession.updateTask
Attributes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl.upd
ateTaskAttributes(SchedulerController_z4f4d2_EOImpl.java:478)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl_CBV
.updateTaskAttributes(Unknown Source)
at com.thortech.xl.dataobj.tcTSA.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Sourc
e)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl.save(tcTSA_u3xmy2_EOImp
l.java:1437)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
bleServerRef.java:90)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by [Nested Exception]:
java.lang.NullPointerException
at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.updateTaskA
ttributes(Unknown Source)
at com.thortech.xl.scheduler.ejb.SchedulerControllerBean.updateTaskAttri
butes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerControllerSession.updateTask
Attributes(Unknown Source)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl.upd
ateTaskAttributes(SchedulerController_z4f4d2_EOImpl.java:478)
at com.thortech.xl.scheduler.beans.SchedulerController_z4f4d2_EOImpl_CBV
.updateTaskAttributes(Unknown Source)
at com.thortech.xl.dataobj.tcTSA.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Sourc
e)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl.save(tcTSA_u3xmy2_EOImp
l.java:1437)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
bleServerRef.java:90)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
ERROR,11 Apr 2008 05:02:53,287,[XELLERATE.SERVER],Class/Method: tcDataObj/save E
rror :Data Update Failed
ERROR,11 Apr 2008 05:02:53,302,[XELLERATE.DATABASE],Class/Method: tcDataBase/rol
lbackTransaction encounter some problems: Rollback Executed From
java.lang.Exception: Rollback Executed From
at com.thortech.xl.dataaccess.tcDataBase.rollbackTransaction(Unknown Sou
rce)
at com.thortech.xl.dataobj.tcDataObj.rollback(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.doRollback(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.ejb.databeansimpl.tcDataObjectBase.save(Unknown Sourc
e)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl.save(tcTSA_u3xmy2_EOImp
l.java:1437)
at com.thortech.xl.ejb.beans.tcTSA_u3xmy2_EOImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(Activata
bleServerRef.java:90)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
I am facing above error when try to update any task in the task scheduler.
Can anyone please suggest me where i am going wrong?
Thanks,
Uma.

I would assume you are missing the jar file for your scheduled tasks. Try and create a new scheduled task with the same class name, if it won't let you save, this is your answer. You'll want to make sure you have the connector scheduled task file in the ScheduleTask folder in your OIM directory.
-Kevin

Bdoc error : Message no. COM_PRODUCT701 Language ( is not allowed

Hi Guys,
I am in the process of downloading the material master from r/3 to CRM 7.0. I have been getting this bdoc error "Bdoc error : Message no. COM_PRODUCT701 Language ( is not allowed ".
Anybody can help me in fixing this issue? Really appreciate that.
Regards,

I havent received solution on this but i need to post a new thread & since i have 10 open theards, system is not allowing me to post the same.

Function module with UPDATE TASK

All,
Have a look at the below code. While debugging the control is not going inside the function module called using call function ...... in update task statement.
I believe the function module is not executed immediately, but is scheduled for execution in a special work process (update work process). For this purpose, the name of the function module including the passed actual parameters is stored as a log record in the database table VBLOG. If the statement is executed during the update task, the addition IN UPDATE TASK is ignored.
The actual execution is triggered by the statement COMMIT WORK which is not happening in this case. The formal parameters of the function module receive the values of the actual parameters from table VBLOG. How can I read the entries in VBLOG? Why the function module is not executed? Please suggest.
PERFORM bte_publish ON COMMIT LEVEL 9.
* syncron update
 COMMIT WORK AND WAIT.
* Publish business transaction events. The function module have
* to call as last update module!
FORM bte_publish.
IF NOT gvt_nodes IS INITIAL.
 CALL FUNCTION 'CUSTOMER_HIERARCHY_THROW_BTE' IN UPDATE TASK
 EXPORTING
 ffi_valid_on = knvh-datab
 fti_event_list = gvt_nodes
 fti_event_listx = gvt_nodesx.
ENDIF.
ENDFORM. " BTE_PUBLISH
Thanks,

Right Naren. But I need to check inside the update function module, whether it is calling the BTE function module I had configured and the code which I had put in it. Any ideas?
The COMMIT WORK is returning 4 and hence I believe it is not popping up another debuggin session in which the update FM runs.
Thanks,
Message was edited by: Somen

BDoc error in Delta Update for CRM_SRV_IBASE_ATTR

Hi Gurus,
I'm having troubles with the delta queues in CRM 6.0 (2007) , I really appreciate if you can help me out.
I'm using the extractor CRM_SRV_IBASE_ATTR to get the installed bases. I have no problems with the INIT but at the moment of updating deltas there are always 0 records in the DELTA UPDATE, (even after creating new IBASE's).
I was cheking the transaction SMW01 and noticed that the BDocs are being created with status in RED (Incomplete), I guess that's the reason which I don't see any record (LUW) in RSA7 for this extractor and therefore the reason which I get always 0 records in the DELTA UPDATE.
The BDoc error message reads:
14.10.2008 14:36:18 Outbound call for BDoc type CRM_IBASE_MESS to adapter module CRM_UPLOAD_TO_OLTP failed.
Area: SMW3. Nº: 5
14.10.2008 14:36:18 Service that caused the error: SMW3_OUTBOUNDADP_CALLADAPTERS
Area: SMO8. Nº: 47
I've been reading SAP documentation but have no clue so far about this issue.
Have you got any idea about what could be happening? I really appreciate your Help...!!
I'll give you points.!!
Regards,
Carlos

hi,
The problem may be due to adapter object is set to inactive, while in administration console, the all business transaction mesg is subscribed. So try settimg the adapter object to active and re-process the bdoc.
after reprocessed the error bdocs, then automatically queue to BW started to piling up .
hope this helps you ..
Reagrds,
Shikha

Bdoc Error"You must activate partial deliveries before you can specify "

Hi
While doing the downloads of customers from ECC to CRM, I am getting an error in Bdoc "You must activate partial deliveries before you can specify a max. number" .We are running on CRM 6.0 connected to ECC 5.0 .I have checked the Note 1338378 but it is only applicable for ECC 6.0 .Please provide your Inputs to overcome the issue .
Regards
Vipul Singh

Hi Vipul,
This is a master data issue. In ECC system go to Tr. XD02 select your customer go to sales area data -> go to shipping tab and in partial delivery block correct the data. If you have selected partial delivery per item = C i.e only complete del. allowed then take out the value from the field max. partial delivery. Save your changes.
Then you will get another Bdoc error " partner with GUID XXXXXX does not exist" ignote it.
Bring the customer using the request load.. and you should be good.
Thanks,
Vikash.

Reprocess Bdoc with status I04 (Intermediate state)

Hi All,
I have problems to reprocess Bdoc's with status I04 (Intermediate state).
In a batchprogram I created businesstransactions. But when a central blockade was set on the businessparter, no businesstransaction appear.
In the SM13 I have Update-errors (SAPSQL_ARRAY_INSERT_DUPREC).
In the SMW01 I have Bdoc's (BUS_TRANS_MSG) with status I04.
I'm having problems to reprocess the Bdoc's.
After uncheck all central blockades, the reprocess of the bdoc failed.
After changing the status of the Bdoc from I04 to I01, the bdoc will be reprocessed (green), but the data in the Bdoc will not be written to the database (CDB).
What could be a solution to reprocess the Bdoc's with an update of the CDB (and the businesstransaction appear)?
Thanks!

Hi G. van Doom,
You got a system error: SAPSQL_ARRAY_INSERT_DUPREC, this means that the running process tried to insert to the DB a records that is already existing. Hence it raised this system error.
Reprocessing the BDoc won't solve the issue since you will again try to insert record that already exist.
I would suggest you to maybe check the task you set in the BDoc from your batchprogram, if the records was already existing then you should rather do an update, by using Task = 1. Therefore you must have a logic in your program which can find if the record exist or not in order to set the appropriate task.
Task:
1 - Update
2 - Insert
3 - Delete
Hopping this help.
Sincerely,
Alain Gauthier

BUPA_REL bdoc error

Hi,
In SMW01 i can see some BUPA_REL bdoc which are in error state and some are in intermediate state(I04).
For the failed bdoc error showing are
1. Service that caused the error: /1CRMGC/CONGEN_OBJ_WRT_CDB
2. Technical error occured: Service , BDoc type CONGEN_OBJ_WRT, Message Select for Update failed: Update error in table SMOKVBEZ7: row SFAKVBEZ7=49B.
3. Service that caused the error: BP_REL_CRM_TO_CDB
We are using Mobile Sales also and hence i have checked the Tcode SMW3FDCUST for bdocs BUPA_REL the Active checkbox is marked but Mobile Bridge is unchecked.
Also i can see everyday many BUPA_REL bdocs are successfully processed without any issue.
Can anyone tell me how to process those failed and pending bdocs and what would be the issue.
Regards,
Shobhit

Hi Shobhit,
I have applied the note 1528032, this is a manual correction. I have copied the correction from this note for your reference.
The function module BP_REL_CRM_TO_CDB is only relevant for the mobile scenario.
Since you are not using the mobile scenario, the FM should not be called.
Check in Transaction SMW3FDCUST for the BDoc Type "BUPA_REL" and the Function Name BP_REL_CRM_TO_CDB.
Remove the 'X' from the active field for all of these entries.
By unchecking this field the data will not be sent to CDB.
Please note that the mobile bridge is active once the 'active' flag has been set - even if the 'mobbridge' field has not been filled.
Thank you and Regards,
Niranjan

Bdocs error data SMW01 (PRODUCT_MATERIAL)

After running some replication we have a lot of bdocs error with the following logs :
"Data for set BBPM_PR_GENERAL may only be changed in the original system SIDCLNT050 (our crm logical system)"
"Validation error occurred: Module COM_PRODUCT_MAT_VALIDATE, BDoc type PRODUCT_MAT."
we have found the corresponding note 786409 but eveni if our system is update, the bug is not fixed (we had the same function module wgich triggers problem)
I checked some tables with a not the right logical system (logsys) but we tried to change it from one product id and it does not work.
Any help will be rewarded.
Thomas

Hi,
Which CRM release are you using?
You may try re-generating the Bdoc (PRODUCT_MAT) services using trx.
SMOGGEN
. Then try reprocessing one or the error Bdocs or run the delta load once again.
If no success, you may have to debug the CRM inbound queue and the validation service module
com_product_mat_validate
Good luck! Reward if helpful.
- Sudipta.

BDOC Error : "BDoc stored before update task (intermediate state)"

Similar Messages

Maybe you are looking for