Terminating event 'Created' in ABAP OO context

Hi,
I need a little help here. A lot of times I have used terminating event ‘Created’ for different BOR types – and asynchronous tasks where users are asked to create an object using call transaction from a work item.
Now I am struggling with the same in ABAP OO and have an issue:
The goal is to have a terminating event raised on a custom class - and received by a work item if a customer is fully created, that is the general part, the company code part and the sales area part.
Raising the event is working great. I have put in a class in trx. SWEC together with a function module which set the class as object type if the condition is fulfilled.
Then in trx. SWED I have entered another function module to set the key for class together with object_por-catid = ‘CL’.
Then when a customer master record is created I can see in the event trace that the event is raised with the correct key.
No I want to receive the new object into my asynchronous dialog task. I define the event as terminating event – and in the code call transaction XD01.
When the work item is created I find a waiting event linkage in trx. SWE3 – of cause without key; this is unknown until after creating.
But after executing the workitem and raising the event the workitem does not receive the event and is therefore not completed.
Is this approach not possible in ABAP OO – or do I miss something in the class definition / coding?
The event is defined as public instance – I have not coded any event handler method.
Thanks,
Claus.

Hello Claus,
Interesting question, unfortunately not with a simple answer.
The issue is that you are waiting for an instance event without a key. Your object raises an event with a key => No match.
If you raise the created event without a key, you won't be able to match up two near-simultaneous creations with their corresponding work items. Same thing if you wait for a static event.
So how does SAP do it with BOR events? By breaking the rules of course!
They do some hidden trickery to bypass this problem by doing an 'Export to Memory' of the work item ID, and the CREATED event raising code bypasses the usual event linking mechanisms and looks for it's creator by retrieving the memory variable. I don't have the exact spots of code in my head, but a bit of debugging should find it.
So what can you do? Given that you have full control of the class you could do something similar and maybe also create some kind of temporary key consisting of the Work Item ID and raise an event with that, or you could maybe skip the transaction concept completely and run the create GUI entirely within your WF step - maybe a custom screen gathering the initial data and then create the object via BAPI. Time to get creative!
Hope that helps,
Mike
Edit: Or you could do the quick and dirty solution and just use the BOR events for the step and instantiate the class during the binding back to WF...

Similar Messages

Terminating Event Generate an Error

Hi All.
My custom workflow has asynchronous task where the terminating events trigger from ABAP program and passed some data.
This task will completed upon custom event "ACCEPTED" raised in the system based on certain keyfield and continue next steps.
Terminating events tab contains element WIOBJECT_ID and my custom event "ACCEPTED".
Binding is use standard element Binding details as per standards, &_EVT_CREATOR& --> &INITIATOR and &_EVT_OBJECT& --> &_WI_OBJECT_ID&
I though this is the only step that I need to do and of course wait step.
However when I test this terminating event via SWUE with proper object key, event trace transaction reported event "ACCEPTED" for task TS95000052 not defined as start/end event.
I check in instance linkage transaction, linkage is activated for my object type, "ACCEPTED" and receiver type "WORK ITEM".
Event type linkages between event and my asynchronous task also active.
Will someone give me a clue, what should I do to resolve this issue?
Many Thanks

You cannot exit from a for loop until it is done. Use a while loop instead. Also, using the event structure in this case causes all kinds of exit problems. Try it and you will see what I mean. Instead, use the abort button itself. Put a case statement at the end to give the error output if the abort button was pressed. See attached vi.
- tbob
Inventor of the WORM Global
Attachments:
abortTesting.vi ‏45 KB

Terminating event and abap oo class

Hi, gurus,
I 'd like to know how the terminating event works.
for example, i define a custom abap oo class (which has been implemented the interface of IF_WORKFLOW), and i want to use it as the terminating event of a standard task.
could you please tell me how does it works?
1. there must be an instance defined in the container of the task?
which must be instanciated in the run time?
2. then in another abap report, i simply raise the event defined as the terminating event, using the same key, then the pending task will be terminated?
could you pls provide more information on this ?
thanks and best regards.
Jun

Hi Jun Zhang,
An event that is used to stop a workflow or task, or change the behavior of an already started workflow is called Terminating Event.
If the event linkage is active and the linkage rules are satisfied, the status of the work item is set to COMPLETED.
Defining Event Linkage Terminating event linkage consists of 2 parts.
Type linkage which specifies business object type, event name, generic name for event receiver (WORKITEM for terminating events of tasks or EVENTITEM for wait for event steps)
Instance linkage which identifies the particular receivers (I.e. work item Ids) per object instance.
Terminating event linkages can be seen in SWE3.
For terminating events, along with Business object and Event a Container Element should be specified that holds the Object Instance.
Terminating Event for Workflow is available from Release 6.10 only. This is defined in Basic Data of Workflow Builder.
Binding Definition is optional for Terminating Events. Binding can be defined b/n event container and workflow container to pass event information to the workflow if required. That is the only way of passing information from an asynchronous method to the task that started it.
Thanks and Regards,
Prabhakar Dharmala

ECC6.0 WebDynpro(ABAP) - raising terminating event

Hi, in ECC6.0 I have a custom WDA application with a custom workflow. The workflow is launched via an event that is raised in the WDA application. However, at one point workflow sends a link to one of the WDA pages, whereby the user clicks a button which raises what should be a terminating event for the workflow task. However, while this event is raised, as confirmed in SWEL, it doesn't terminate the task. The event is raised through a WDA assistance class. The object type, event and object key are all being set properly during the raising of the event. Viewing the event in SWEL confirms the proper setting of the key fields. So why isn't the step terminating?
Thanks in advance,
Kevin

Hi,
If the object that is waiting for event has no instance, the task will not be terminated when the event is created in the system (As I said). So now the reason is clear for you.
>The event is raised through a WDA assistance class
I am not sure what you mean by this. You raise the event from the WDA assistance class? Or you raise an event for the assistance class? (Or perhaps both?).
If you raise the event for the assistance class, you should have an instance of that class in the workflow container (which you would then bind from workflow container to the task container). So, now the question is: do you have an instance of the assistance class in the WF container (when you look it from log)? Or is it initial also?
Actually I don't really even understand how you have managed to combine the WDA assistance class and WF class? How do you actually start the workflow (with which kind of event)? Whatever event it is, it should most likely instantiate some class/object in the workflow. Then in your problematic task you should most likely use this same class in the terminating event (unless there is something really fancy in your workflow).
Regards,
Karri

Use abap class event as terminating event

Hi,
The class is say ZCL_WF_CLASS and the event END_WF.
What needs to be done to have this event used correctly as a terminating event of a workflow? Does this event require a parameter to hold the workitem id (or workflow id), as currently this event has no parameters?
Previous developer has developed the class and event and installed as a terminating event but the workflow is going into error not terminating correctly. I believe the incorrect development of the event and/or its use in the workflow is the issue. Note that nowhere is this event currently raised in any code of the workflow.
Cheers,
Ross

Hello,
Unless I'm mistaken, a terminating event for a workflow is just like any wait-for event in a workflow.
It can be based on any object or class and it can be used in various ways - to terminate a branch or terminate the workflow, for example.
The workflow listens out for the event and checks if there is a matching key. You could base it on the key of a workflow object but it makes more sense to base it on an object or class that's used in the workflow - e.g. the POSTED event of an object would be used to terminate a workflow seeking approval for the posting of an object.
It definitely won't work if the event has no parameters. I guess if you do base it on the workflow object then you would use the top-level workitem id. Try it with a test workflow and SWUE to generate the event.
regards
Rick Bakker
hanabi technology

Mapping context subnodes of WD ABAP with context of Interactive Form

Hi everyone,
I'm facing a problem here passing my WD subnodes to the context of the interactive form.
I managed to pass a node with only attributes but not with subnodes in it.
The code I used is really basic, here is a sample :
DATA t_affectation TYPE wd_this->elements_t_affectation.
DATA t_el_affectation TYPE wdr_context_element_set.
DATA nd_dropdown_project TYPE REF TO if_wd_context_node.
DATA nd_dropdown_customer TYPE REF TO if_wd_context_node.
DATA lt_dropdown_customer TYPE wd_this->elements_t_dropdown_customer.
DATA lt_dropdown_project TYPE wd_this->elements_t_dropdown_project.
LOOP AT t_el_affectation INTO el_affectation.
    nd_dropdown_project = el_affectation->get_child_node( name = wd_this->wdctx_t_dropdown_project ).
    nd_dropdown_customer = el_affectation->get_child_node( name = wd_this->wdctx_t_dropdown_customer ).
    nd_dropdown_project->bind_table( new_items = lt_dropdown_project ).
    nd_dropdown_customer->bind_table( new_items = lt_dropdown_customer ).
ENDLOOP.
But i get a dump telling me
Termination occurred in the ABAP program "CL_WD_ADOBE_SERVICES==========CP" -
in "NODE_2_DDIC".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 32
of the (Include) program "CL_WD_ADOBE_SERVICES==========CM00L".
and the dump occurs as soon as it explores the subnode:
   20 * depending on the cardinality, it either represents a structure or i
   21   if lr_node_info->is_multiple( ) = abap_false.
   22 *   it represents a structure
   23     lr_element = i_node->get_element( index = 1 ).
   24     node_elem_2_struct(
   25       i_element   = lr_element
   26       i_parent    = i_parent
   27       i_node      = i_node
   28       i_node_info = lr_node_info ).
   29   else.
   30 *   it represents a table
   31     lt_elements = i_node->get_elements( ).
------>     assign i_parent->* to <itab>.
   33     loop at lt_elements into lr_element.
   34 *     create a new line inside of the itab
   35       insert initial line into table <itab> reference into lr_data.
Does any of you has an idea ? I would be most grateful.
Thank you
Regards,
Alexandre

It's ugly, but it's true:
At this point in time, Web Dynpro for ABAP has only one Interactive-Forms-specific standard event (compared to the 2 in Java), which is the Submit event. I am hoping that both Web Dynpro worlds will be on the same level in terms of features in the next release.
Best regards,
Markus Meisl
SAP NetWeaver Product Management

Read workitem Container Value in Terminating event Check Function Module

Hi
I have some problems reading work item data / values of a work item container element in a check function module on a terminating event Do any of you know if this is possible, and if so, how its done ?
In My scenario I have created a multiline approval step for my business document, one task pr Line Owner. The Event Approved is defined as a terminating event for this task, and the line owner is passed to the task container.
Now, when I raise the event, with the line owner as an event parameter, I would like to check if the line owner on the raised event, matches the line owner in the task container in question in a check fm. But here I faced the problem, that only event data, and not work item data, are passed to the Check Function module.
Regards,
Morten Nielsen

Hello Morten, hello Arghadip,
in the instance linkage's check function module (entered via transaction SWEINST) you'll have the workitem-id in the system event parameter EVTRECEIVER_ID
With this number you can use the frame work in order to read the work item container.
This is a sample coding, how you access the correct work item container using SAP Enterprise and it's new OO frame work, which checks on the terminating event of BUS2105.Released the correct release code for a work item.
INCLUDE <cntn01>.
INCLUDE <SWFCNTN01>.
INCLUDE RSWEINCL.
*** Read workitem instance and container from event
       DATA: wi_id            TYPE swwwihead-wi_id.
       swc_get_element EVENT_CONTAINER evt_receiver_id wi_id.
       IF sy-subrc <> 0.
          MESSAGE E015(ZPREL) WITH evt_receiver_id
                                       RAISING wrong_call.
       ENDIF.
       DATA: lv_wi_handle    TYPE REF TO if_swf_run_wim_internal.
       DATA: ls_context      TYPE sww_wimctx.
       DATA: lv_wi_container TYPE REF TO if_swf_cnt_container.
*    - set context
       ls_context-do_commit = ' '.
       ls_context-called_btc = 'X'.
       ls_context-exec_user = sy-uname.
       ls_context-fbname     = 'Z_CHECK_RELEASE_CODE'.
       CLEAR lv_wi_handle.
       CALL METHOD cl_swf_run_wim_factory=>initialize( ).
       CALL METHOD cl_swf_run_wim_factory=>find_by_wiid
               EXPORTING
                  im_wiid             = wi_id
                  im_read_for_update = ' '
*                 im_enqueue_owner    = fb_name
*                 im_wait_for_enqueue = 'X'
                  im_context          = ls_context
               RECEIVING
                  re_instance         = lv_wi_handle.
*** This check is only done for workitem linkage TS90100081
       IF lv_wi_handle->m_sww_wihead-wi_rh_task <> 'TS90100081'. "#EC_SYNTEXT
          EXIT. "Let event pass, as this is an instance linkage to another workitem
       ENDIF.
       DATA: releaseCode_wi        TYPE t16fc-frgco.
*    - read releaseCode from workitem container
       lv_wi_container = lv_wi_handle->get_wi_container( ).
*    - perform binding event container -> workitem container
       swf_get_element lv_wi_container 'RELEASECODE' releaseCode_wi.
      DATA: e             TYPE REF TO cx_swf_run_wim.
      CATCH cx_swf_run_wim INTO e.
         RAISE WORKFLOW_RUNTIME_ERROR.
   ENDTRY.
*** From here on, the variable releaseCode_WI hold the
*** container element RelaseCode of the work item, that
*** is going to be terminated...
*** Further coding from here as appropriate...
Best regards,
Florin

Portal Eventing in Webdynpro ABAP

Hello,
I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
But still the value sent in Com1 is not displayed in the Com2 Inputfield.
Any help would be highly appreciated.
Thanks.

>
SAPEPDeveloper wrote:
> Hello,
>
> I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
>
> In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
>
> But still the value sent in Com1 is not displayed in the Com2 Inputfield.
>
> Any help would be highly appreciated.
>
> Thanks.
Hi I assume the following, please correct me if my understanding is not correct.
1.First of all you try this in Portal.
2.The moment you fire the event, the comp-2 view is active and subscribed to the portal event.
If the above are true then tell me if the portal eventing enter into the action ?Have you checked in bebug that your action is triggerred on portal_event ?
If portal event is action handler is called then if you have a importing parameter portal_event_parameter then your input value should be there.

Warning: "No terminating events defined for the task used"

Dear all,
I created a task with ABAP class and method as its object method. This task is a background task. The ABAP class inherits the IF_WORKFLOW interface but doesn't implement any method of the interface.
When I try to confirm the task settings in transaction SWDD, a message shows up "No terminating events defined for the task used" and I cannot continue the work. Does anybody have any idea what I should do?
Thanks + Best Regards
Jerome

Hi Jerome,
If you set a background task in your workflow, and if it is asynchronous, then you need some way to tell the template if it is finished and what happened. In this case you set terminating events - that is events which are published in the system as a result of your method (ie document.posted etc).
Either use a synchronous method for your task or set appropriate terminating events in your task setup.
Regards
Gareth

How to raise a Terminating Event for a Standard Task?

Hi Experts,
I have a standard task where I have defined the Terminating event to stop the workflow.
This Task/Workflow will be triggered by a batch program.
Also in a class method I am using function module SWE_EVENT_CREATE to raise a event which should complete the workflow. But somehow the work items are still in In Process status.
May be I am passing wrong parameters OR using wrong FM to raise a terminating event.
Request you to help me on this. Thanks in Advance.
Regards,
Sudhakar.

Hi Sudhakar,
Since there are entries in SWE3 which show link each time event is triggered. So I would suggest you will have to check the standard task you are using is working. So create a parallel branch with activity on one end and wait for event step on other. See if the the wait for event step works, when you create the event using create event. If it works then most likely your task binding has a problem. If not then event that is triggered does not getting picked by workflow. So based on the finding we can find a solution.
I notice that you are calling the event from an ABAP class, so in that case the code for calling event seems to be different. Check out the below SAP help documentation.
http://help.sap.com/saphelp_nw2004s/helpdata/en/a1/172437130e0d09e10000009b38f839/frameset.htm
Regards,
Kartik N.
Edited by: KARTIK Nayak on Dec 12, 2008 8:25 PM

Terminating Event Not Triggering

HI Guys,
I have added a custom task to call MRBR screen and set a Terminating Event for this task. It is a Asynch Method.
Through SAP_WAPI_CREATE_EVENT i am calling the terminating event but my task is not getting terminated.
I checked in SWEL i could see evnt log for my terminating event without Receiver type.
Kindly help me to sort out this issue.
Regards,
Dheepak

Hi
Where have you written the code for triggering the termination event?
Also in your task have you created an entry:
WIOBJECT_ID FIPP TerminatingEvent Name.
When everything is done properly in SWEL you would see the receiver as workitem.
Thanks and Regards
Aman

How can I trigger an event from an ABAP Program

Hi everyone,
I have a requirement, where I have to create an ABAP program, that has to execute (trigger) an event which belongs to a Process Chain. when I run the program, the Process Chain has to run.
So, how can I do it?
Thanks for your help, Federico

HI ,
The program can call function module BP_EVENT_RAISE to raise the event. you can create vent in sm64 and sm62 .There you give the parameter of the event same as what you will define in the event of start variant of your process chian ..
Regards,
shikha

Copy of task TS50000075 and EXTSRV - termination event not working

Hi,
We have done copy of TS50000075 and extended business object EXTSRV to ZEXTSRV
this was done to call function module ISR_CALL_FOR_CHANGE to open up adobe form in edit mode
it works well but the task is not terminated
if termination event is put just like TS50000075 like WIOBJECT, ZEXTSRV COMPLETED then workitem never ends and always stays in inbox
ZEXTSRV COMPLETED event is not triggered when the workitem is completed in the UWL
even if we trigger this event programatically , it does not find receiver and the task stays in-process
if termination event is put as _WORKITEM PROCESSED then it bahves like synchronous task ie even if the workitem is clicked and form is not completed, the workitem ends. so the user can click it only once
also i've tried following
1 - used the function module to complete the workitem in QISR BADI. but the workitem ID is not available inthe BADI. If I try to export it from business object method and import in BADI, it doesnt work
2 - find active workflows and derive workitem id and complete workitem using FM SAP_WAPI_WORKITEM_COMPLETE
     this FM doesnt work , step becomes logically deleted which is not desirable
3 - find active workflows and derive workitem id and complete workitem using other FM SAP_WAPI_SET_WORKITEM_COMPLETD
     work item is complete but there is workflow error - cannot determine succesor node
4 - find active workflows and derive workitem id and change a particular container element
    check this container element in complete workitem condition in activity step of dialog step of workflow of this task-
     workitem stays inprocess
    check this container element in parellel wait step to complete the workitem-
     parellel step executes but fork is not complete, workflow doesnt proceed
kindly help in this matter. the workitem does not get completed at all even if we force complete, workflow goes in error of - cannot determine succesor node.
is there anything specific to the EXTSRV-PROCESS method which makes the TS50000075 task to trigger EXTSRV-COMPLETED and end the workitem ?
help is much needed in this case
thank you,
b

Hi,
You need to see the event in SWEL, otherwise it will never work with workflow. Make sure that the event monitor is on (in transaction SWELS).
I cant see the event in SWEL. The vent monitor is on because if I create event in SWUE, it shows up.
How you actually create the event now?
There is BADI QISR which is always called to handle user action of PDF form. I have written the function modue to create event in the user action
>If i trigger it using funciton module -- then it doesnt find any receivere so it doesnt terminate the task. it is seen in SWEL with no receiver found. do i still need to do commit work ?
You need the COMMIT WORK always if you trigger the event in any program&function or whatever.
ok ill try doing commit work after the create event function module
Test your event with transaction SWUE. Make a test case first in a way that the task is waiting in the inbox/UWL. Then create the event in SWUE. Now, if the task gets completed, you will know that that event itself is working and your terminating event configuration is done properly. If this works, your only problem is in the event creation itself. And for that you need to tell exactly how you create the event. If you do it with your own custom code, use SAP_WAPI_CREATE_EVENT and don't forget to have COMMIT WORK after the function call.
I am doing exactly like you said. but it doesnt work ie even if I create the event in SWUE, the workitem doesnt get completed.
This event is seen in SWEL with no receivere found
I am able to infact set the workitem to complete using WAPI funciton module to complete teh task in the BADI.
but the workflow goes in to error saying , next node cannot be determined
Regards,
Karri

Termination occurred in the ABAP program "RK2APA00_POST" - in

Hi everybody...I have a cancelled job when run only in applications servers , I see a dump "message typeX" , but when job run in Central Instance not cancelled and finish ok.
The name Job is Zcupon and attach to continue dump info , sorry for extended but I want send all information possible.
know if you can add a file with the abstract and not have to paste the text of the dump, thanks for the help they can deliver.
Regards....Freddy Solar....
Errores tiempo ejec.   MESSAGE_TYPE_X
Fecha y hora           18.11.2008 06:35:30
Texto breve
The current application triggered a termination with a short dump.
¿Qué ha sucedido?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Anál.errores
Short text of error message:
RFC_ERROR 4 Conversation 93690218 not found / CPIC-CALL: 'ThSA
Technical information about the message:
Message classe...... "KE"
Number.............. 628
Variable 1.......... "RFC_ERROR"
Variable 2.......... 4
Variable 3.......... "Conversation 93690218 not found / CPIC-CALL: 'ThSA"
Variable 4.......... " "
Last error logged in SAP kernel
Component............ "SAP-Gateway"
Place................ "SAP-Gateway on host SCPAPP1 / sapgw03"
Version.............. 2
Error code........... 728
Error text........... "Conversation 93690218 not found"
Description.......... " "
System call.......... " "
Module............... "gwxxrd.c"
Line................. 6156
The error reported by the operating system is:
Error number..... " "
Error text....... " "
Notas para corregir errores
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
please use the following search criteria:
"RK2APA00_POST" "MESSAGE_TYPE_X"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Entorno sistema
SAP-Release 700
Application server... "SCPAPP1"
Network address...... "10.1.40.130"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "BALTICO"
Database type..... "DB400"
Database name..... "SCP"
Database user ID.. "R3SCPDATA"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jun 30 2008 00:10:07"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "DB4_53"
Patch level. 167
Patch text.. " "
Database............. "V5R3, V5R4, V6R1"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 159213920
Heap.... 0
Page.... 5660672
MM Used. 145143664
MM Free. 5680112
Usuario y transacción
Client.............. 400
User................ "ZUSRTARJETAS"
Language key........ "S"
Transaction......... " "
Program............. "RK2APA00_POST"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Info posición de cancelación
Termination occurred in the ABAP program "RK2APA00_POST" - in
"INSERT_CE4_FLUSH_BUFFERS".
The main program was "ZVI_CUPON ".
In the source code you have the termination point in line 100
of the (Include) program "RKEVRK2A_POST_COMMIT__FIX".
The program "RK2APA00_POST" was started as a background job.
Job Name....... "ZCUPON"
Job Initiator.. "ZUSRTARJETAS"
Job Number..... 02044200
Detalle código fuente
Lín.
Txt.fte.
70
subrc = sy-subrc.
71
CLEAR: g_t_ce4a_dbbuf[], g_t_ce4_dbbuf[].
72
73
case subrc.
74
when 1.
75
    Records were to be inserted into the acct.ref. table CE4xxxx_ACCT
76
    but the acct. reference numbers were already occupied. Most likely
77
    This problem is due to a explicit or implicit change to the
78
    number range COPA_OBJ (subobject is the operating concern)
79
    e.g. caused by illegally transporting the contents of CO-PA
80
    transaction data table contents (CE4xxxx / CE4xxxx_ACCT).
81
    Please check OSS for notes with keywords RKEVRK2A_POST, KF216
82
    and CE4XXXX_ACCT. If you do not find any applicable notes please
83
    log an OSS message.
84
MESSAGE x216(kf) WITH gc_ce4acct_name.
85
86
when 2.
87
    Records were to be inserted into the segment table CE4xxxx
88
    but the segment numbers were already occupied. Most likely
89
    This problem is due to a explicit or implicit change to the
90
    number range COPA_OBJ (subobject is the operating concern)
91
    e.g. caused by illegally transporting the contents of CO-PA
92
    transaction data table contents (CE4xxxx).
93
    Please check OSS for notes with keywords RKEVRK2A_POST, KF203
94
    and CE4XXXX. If you do not find any applicable notes please
95
    log an OSS message.
96
MESSAGE x203(kf).
97
98
when 3 or 4.
99
    Communication error in RFC-Call
>>>>>
message x628(ke) with 'RFC_ERROR' subrc msg_text.
101
102
endcase.
103
104
ENDFORM.
105
Edited by: freddy solar on Jan 2, 2009 8:39 PM

Hi,
it looks like you have some problem with RFC. It stopped on the following line:
* Communication error in RFC-Call
message x628(ke) with 'RFC_ERROR' subrc msg_text.
Ask your basis guy to check it. The job on application server tried to connect to the central instance and it failed. The job run on central instance does not need to make any RFC call. Hence there is no problem in this case.
Regards

Purchase Order Workflow - dialog step not receiving terminating event

Hi,
We have a scenario wherein based on the release groups and release strategies, different peope need to release the PO's.
I have been able to develop the workflow for this successfully, but here is where I am facing an issue.
After the PO has been created, based on the release group and strategy, it gets routed to the appropriate 1st approver. On their approval, the PO gets routed to the 2nd approver. Once the 2nd approver approves, the dialog step doesnt get completed and is still waiting for the terminating event. Event trace shows that the event is getting published, but there is no workitem to receive the terminating event. I am not sure why this is occuring for only 2nd approver onwards whereas for the 1st approver, the terminating event is received by the workitem.
I am using start conditions for my workflow to ensure only 1 instance of the workflow is triggered for a rel groups and rel strategy and release code, else I am multiple instances each time an approver approves the PO. I am not sure if the start conditions are causing this issue with the terminating events not being received with the workitems.
Any assistance is welcome.
Thank you,
Satish

From the information provoided it seems you are using PO that is subjected to Release of PO for multiple Release Code and each Release Code Release is being done by one approver. If that is the case then I think the Terminating event should get caught. Please check whether the Terminating event that is getting triggered is specific to the Release Code or not.
Thanks
Arghadip

Terminating event 'Created' in ABAP OO context

Similar Messages

Maybe you are looking for