SAP OSS Notes

726762 SAP OSS Note - Workflow scheitert wegen Fehler bei FOPC_ACTIO








SAP OSS Note 726762 version 0002 contains details of a know issue related to Workflow scheitert wegen Fehler bei FOPC_ACTIO. This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 726762 Details:






When does this problem occur

Der Workflow kann nicht gestartet werden.

Description of problem

FOPC_ACTIO, Workflow, CGV, MIC

Cause of the problem and Pre-requisites

Der Workflow ruft das Business-Objekt auf, obwohl er nicht initialisiert ist.

Solution instructions

Übernehmen Sie die beigefügte Korrekturanleitung.

Note 726762 Correction instructions:



NOTE: Only source text changes are displayed here

*$*$----------------------------------------------------------------$*$*
*$ CORRECTION INSTRUCTIONS 0120061532 0000625480 $*
*$--------------------------------------------------------------------$*
*$ VALID FOR : $*
*$ Software Component CGVMIC CGVMIC (Management of internal cont$*
*$ Release 100 To SAPK-10004INCGVMIC $*
*$*$----------------------------------------------------------------$*$*
*&---------------------------------------------------------------------*
*& Object REPS RFOPC_ACTION
*& Object header PROG RFOPC_ACTION
*&---------------------------------------------------------------------*
...
begin_method execute changing container.
end_method.

get_property mt_recipients changing container.

*>>>> START OF DELETION <<<<<
if object-private-model is initial.
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
if object-key is initial.
* fallback problem, if the key is not maintained...
swc_set_table container 'mt_recipients' object-mt_recipients.
return.
endif.

if object-private-model is initial.
*>>>> END OF INSERTION <<<<<<
...
get_property m_object_txt changing container.

if object-private-model is initial.
object-private-model = cl_fopc_model_setup=>get_instance( ).
endif.

*>>>> START OF DELETION <<<<<
if object-m_object_txt is initial.
object-m_object_txt = object-private-model->read_text(
i_objtype = object-key-m_objtype
i_objid = object-key-m_objid
i_orgunit = object-key-m_orgunit ).
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
if object-key is not initial.
if object-m_object_txt is initial.
object-m_object_txt = object-private-model->read_text(
i_objtype = object-key-m_objtype
i_objid = object-key-m_objid
i_orgunit = object-key-m_orgunit ).
endif.
*>>>> END OF INSERTION <<<<<<
...
swc_set_element container 'm_object_txt' object-m_object_txt.
end_property.

get_property mt_user_admins changing container.

*>>>> START OF DELETION <<<<<
if object-private-model is initial.
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
if object-key is initial.
* fallback problem, if the key is not maintained...
swc_set_table container 'mt_user_admins' object-mt_recipients.
return.
endif.

if object-private-model is initial.
*>>>> END OF INSERTION <<<<<<
...
if object-private-model is initial.
object-private-model = cl_fopc_model_setup=>get_instance( ).
endif.

data: l_orgunit type fopcb_objectid.
*>>>> START OF DELETION <<<<<
if object-m_context_txt is initial.
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
if object-key is not initial.
if object-m_context_txt is initial.
*>>>> END OF INSERTION <<<<<<
...
l_orgunit = object-key-m_objid.
endif.
if l_orgunit is not initial.
object-m_context_txt = object-private-model->read_text(
i_objtype = fopcb_orgunit i_objid = l_orgunit ).
*>>>> START OF DELETION <<<<<
endif.
endif.

*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
endif.
endif.
endif.

*>>>> END OF INSERTION <<<<<<
...
*&---------------------------------------------------------------------*

Effected Objects:


(REPS) - RFOPC_ACTION

(REPS) - RFOPC_ACTION

Solution instructions


Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 726762 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 726762 has already been downloaded and is valid


To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 726762 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.



If note 726762 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)