CUS603 - Subgroup Segmentation

As of 7.5.2, this new batch process is used to handle employee segmentation. In the past, committees, corporate relationships, etc. were combined into a single batch process, CUS600, and there was no way to run the process for just one of those groups. By splitting the groups into separate batch process, you can choose a different time to run the batch process for each group. In addition, the purpose of these batch jobs are to maintain who is in each group.

The batch process adds customers with active membership orders for products linked to the subgroup, as detailed below. All customers who do not meet this criteria are removed from the subgroup segment.
Order_Detail.LINE_STATUS_CODE = ‘A’ and
Order_Detail.FULFILL_STATUS_CODE in (‘A’, ‘G’, ‘T’, ‘X’) and
Order_Detail.PRODUCT_ID = Mbr_Product.PRODUCT_ID and
Order_Detail.CYCLE_BEGIN_DATE <= current date and
Order_Detail.GRACE_DATE >= current date and

Mbr_Product.SUBGROUP_MAST_CUST, SUBGROUP_SUB_CUST = Customer.MASTER_CUSTOMER_ID, SUB_CUSTOMER_ID of Subgroup Customer ID parameters

For example, a staff member at APA has just entered a subgroup record, along with 20 new subgroup member records. Ideally, he/she should have created the subgroup and then created the subgroup as a web segment, before creating the individual subgroup records, but since he/she did not, the CUS603 batch process will need to be run in order to create the individuals as members of the subgroup’s web segment.  

When determining when to schedule this batch process, some items you should take into consideration include the following:

·            Creating:
After you first create a segment for an EXISTING committee, company, or subgroup, you want to run this process to establish who is already part of the group.

·            Adding:
Personify has triggers in place that pick up most new committee members and employees; however, segment members are NOT automatically added to a group. First, the MBR900 to update the fulfill status of membership orders and to populate a reporting table called Cus_Current_Membership_Info. Next, the CUS603 process needs to be run to maintain the segment based on who is currently in the subgroup.

·            Removing:
Usually, a constituent's involvement in a group is time-based and there is no trigger that the system can use to remove someone from the group (i.e., a record is added, updated, or deleted). When a particular date is reached, such as the end date for a committee member’s position, an employment relationship, or a chapter membership, there is no change in the database that tells the system to react. Therefore, a batch process is provided that searches for group member(s) to remove. To figure out a schedule on when to run the batch process, consider your organization's turnover for individuals belonging to a chapter. Ask yourself the following questions and based on your answers, is how often you should schedule the batch process:

o           Are chapter memberships on an annual or anniversary cycle? This can impact how often this batch process is run. For example, annual memberships start and end on the same date, so when you run the batch process would be determined based on how often new members join mid-year or existing members cancel.

o           How often are group managers expected to work with their chapter? For example, if the group manager arranges weekly happy hours for local chapter members, he/she will want a more current list than group managers that only interact with their chapter members on a monthly or quarterly basis.

If you are using Chapter Management on the web and you need to change the ship-to line on a membership order midway through the cycle, do NOT simply change the ship-to line customer ID. This would not result in a true picture of what happened for a chapter manager. Rather, the proper process is to cancel the first customer’s order line and create a new line. Any payment on the first line can be transferred to the new line if desired. See Group Management Controls for more information.

Parameters