Appropriation Request workflow cannot be copied?

[Former Member]

Hi Expert,

We implemented AR workflow where initially we use standard workflow WS00300022.

However, user requested several more changes like email content for approved item.

I copied the workflow and activate the event TO_BE_APPROVED for my custom workflow and deactivate it for standard workflow WS00300022.

However, if I use OITN transaction, it is as if the workflow is inactive because the t-code only display WS00300022 status but nevertheless the custom workflow is successfully triggered when I submit AR for approval.

After this activation, I notice that the behaviour of IMA11 is changed like the user exit is not triggered anymore and the system status button is not greyed out even though when I submit the AR for approval, my user is the applicant.

After further debugging, i found out that there is workflow precheck logic that only triggered if the program check that AR workflow is active.

Surprisingly, I found this code in SAP standard program while debugging :

* WF-Kopplung vorhd.

  CALL FUNCTION 'SWE_EVENT_REC_TYPE_READ'

       EXPORTING

            OBJTYPE       = 'BUS2104'

            EVENT         = 'TO_BE_APPROVED'

            RECTYPE       = 'WS00300022'

       IMPORTING

            TYPE_COUPLING = L_COUPLING

       EXCEPTIONS

            READ_FAILED   = 1

            OTHERS        = 2.

Is it true that we cannot use custom workflow for AR and the only way to customize the workflow is to change this SAP standard workflow WS00300022?

Please help to share your experience if any expert here encounter the same issue.

FYI, my system is in ECC 6.0 EHP 3.

Thank you.

Abraham

[ajeet_choudhary]

thanks for your response Abraham, it would be great if you could share some more details like how you have implemented the solution or some other link or anything which can help me here.

Our requirement beside standard workflow is , workflow should be approved via email(user want to approve workflow on the go from iphone /web mail without entering sap system) and all they should have all the necessary info as attachment at the time of approval.

[Former Member]

Hi Ajeet,

Once we change the standard workflow, we treat it the same as custom workflow.

Each workflow implementation will heavily dependent on requirement, available infrastructure, or SAP Netweaver version. For our case, we use abap webdynpro approval via UWL.

[ajeet_choudhary]

Hi Abraham,

we have same requirement, could you please let know what sap has recommended and the way for copying standard Appropriation Request workflow.

[Former Member]

Hi,

I asked OSS about this note 377177.

Below I quote their answer:

Dear Abraham,

It is correct that for the purpose of changing appropriation request

master data or plan values via BAPI the new business object BUS2204

should be used.

For the appropriation reques approval workflow, however,

the old business object BUS2104 is and will remain to be used.

(Please bear in mind that for just using the standard appoval workflow

the user does at no point need to know which bsuiness object is used

behind this feature.)

So basically the solution part of note 377177 is not correct:

It should rather be saying that it is almost certain that

business object BUS2104 will be further used.

As you can see, OSS response is the solution part for this note is not correct.

In the end, we decided to change the standard workflow instead of copying it.

[Former Member]

Hi,

Can you check below SAP notes.

675279

604337

604338

It was a SAP bug and fixed on later releases.

So the FM will not be a problem for you.

Also check the note 135803.

Thanks,

Viji.

[Former Member]

Hi Viji,

Thank you for your response.

I checked the 3 notes that you mentioned but still cannot see how it relate to appropriation request workflow.

675279 : WS20000263

604337 : IS-OIL / IS-MINE-specific note

604338 : only valid up to 4.7 and related to Data Retention Tool

Note 135803 related to AR but it is more on how to add standard workflow into SWE2.

I tried to find other SAP notes that related with this but not successful so far.

Please let me know if you happen found anything on this issue.

Thank you,

Abraham

[Former Member]

Hi

Those 3 notes are not directly related to AR workflow.

But its related to that function module 'SWE_EVENT_REC_TYPE_READ'.

For some other process also, the standard workflow passed to this FM and those notes explalins about the correction.

Whats the business object used in your custom workflow? Actually BUS2104 is obsolete and the standard workflow still using the same BO. In this case, You should change the BO to BUS2204.

Please check the note - 377117.

Thanks,

Viji.

[Former Member]

Hi Vijay,

Thank you for your information.

Reading the notes it seems like there is no conclusion yet on how to use the new business object.

Hence, i have raised message to OSS about this.

Let see how it goes.