Removing HZ_PARTY records from Workflow Roles

This workaround was originally suggested in the WorkflowFAQ forum by 67_eb_in_619, but I’ve moved it into the blog for more people to look at.

Within eBS, the default definition of the Workflow roles always includes the HZ_PARTY records, as well as those linked to people and users. The problem with this is that if you aren’t using email, then if the notification is sent to the role linked to the party record, then no-one is going to see it!

This is also really bad from a user-friendliness point of view. If you are reassigning a notification, then do you need to transfer it to the user called “SEARLE, Mr. Matthew” or “Mr. Matthew Searle” (in a recent project the first of these was the right one and the latter was for my party record). Potentially, the party record and the user record could have the same display name as well, making it pretty much pot-luck which one the user chooses.

So, how do you remove the records from the view?

There are two ways that you can do this – one supported, one not.

Firstly, you can make the party record inactive. The method that I have been recommended by Oracle to use is:

Navigate: Sales Online Responsibility > Customer Tab > Person Sub Tab
1. Query the person record.
2. Once the person details are displayed, you will see a Status field.
3. Select the status to be Inactive
4. Save

If you don’t use sales, then this is still probably the best place to do it, by all accounts!

Secondly, update the records through SQL:
UPDATE ar.hz_parties
SET    status='I'
WHERE  party_id IN ( SELECT party_id
FROM hr.per_all_people_f );

As ever, make sure you know what you are doing before you commit the changes – I’d be inclined to use the GUI to make the change, but if there are lots of records to fix, or you aren’t fussed about support anyway, then try the second one. I’m not taking any responsibility for it though!

By continuing to use the site, you agree to the use of cookies. more information

In common with almost all professionally run websites, this website logs the IP address of each visitor in order to keep it running reliably. This is also essential for protecting the website and its visitors from malicious attacks, including infection with malware.

This website provides information as a service to visitors such as yourself, and to do this reliably and efficiently, it sometimes places small amounts of information on your computer or device (e.g. mobile phone). This includes small files known as cookies. The cookies stored by this website cannot be used to identify you personally.

We use cookies to understand what pages and information visitors find useful, and to detect problems such as broken links, or pages which are taking a long time to load.

We sometimes use cookies to remember a choice you make on one page, when you have moved to another page if that information can be used to make the website work better. For example:
- avoiding the need to ask for the same information several times during a session (e.g. when filling in forms), or
- remembering that you have logged in, so that you don’t have to re-enter your username and password on every page.

You can prevent the setting of cookies by adjusting the settings on your browser (see your browser Help for how to do this). Be aware that disabling cookies will affect the functionality of this and many other websites that you visit.