cancel
Showing results for 
Search instead for 
Did you mean: 

How to stop Custom Business Object in work flow

0 Kudos

Dear Experts,

We have used Business Object ZAPPR_DOC(Which is Deligated from standard Business object APPR_DOC) in HR PMS.

My Requirement is stop mails incase of Employee seperation, We have Implemented Logic Inside the Custom Business Object.

Now My Requirement is to stop the Custom Business Object in Debugging Mode, Can any Body suggest.

keohanster
Active Contributor
0 Kudos

Hi Ankamma,

I am not sure I understand the question. Do you want to prevent end users from debugging code within a business object? Can you give us a scenario where this is likely?

For example, I understand that in the case of termination, you may not want to send out emails. But are you concerned that a user is somehow going to go digging around (and debugging) to find out more details about an appraisal?

Sue

Accepted Solutions (0)

Answers (4)

Answers (4)

keohanster
Active Contributor

Hi Ankamma,

Depending on your business requirements, you also have some choices to make.

You can use a Check Function Module to prevent the workflow from starting in the first place - perhaps by looking up the person in the PA* tables - assuming you are using HR - and if they are delimited or do not have an active status, raise the event NO_WORKFLOW and prevent your workflow from starting.

If the person leaves the company while the workflow is in process, you can use Terminating Events. Again, assuming you use HR, there are Function Modules like HR_EVENT_RULES_PA0001 which you can enhance to a Z-Version to contain your own business logic, so if you can detect that the person has left the company, you could raise a corresponding terminating event, which would cause your workflow to end.

These are both standard 'best practices' for controlling workflow. However, I don't know your system landscape, so it's up to you to check these out.

Good luck,

Sue

sbl
Active Contributor

Hi

As Rob said you just have to instanciate your buniesse object in SWO1 and put some breakpoint.

However you do not really stop a business object you stop a workflow (via an event or a condition)

You can however change the logic of your business object (well of you method to be more exact)

Best regards

Stephane

former_member186746
Active Contributor

Hi,

Use the technical workflow log to figure out the values that are sent to the method.

Then in SWO1, place your break-point in the code that you're interested in. Then just instantiate the custom business object and execute the method and debug the code.

At what point in the above given instructions are you struggling?

Kind regards, Rob Dielemans

0 Kudos

My Requirement is once employee separated from Organization then mail should not trigger to Respective HOD.

But In My scenario, Still Mails are Triggering to HOD(after employee separation) even though Logic have Changed in My Business Object (ZAPPR_DOC Delegated from standard Business Object APPR_DOC)

I want to debug the Custom Business object, How to to debug the same.

Can anybody suggest me how to approach.

Please let me know if any additional Clarification require from My end.

Regards,

Ankamma.