Person Relationship Type Sequence

When the price assignment search algorithm searches effective price item pricing at the parent customer level, the system determines the parent customer's person to person relationship type whose price item pricing should be considered. The person to person relationship type sequence indicates the order in which relationship type should be considered while searching for effective price item pricing at the parent customer level. For example, if a customer has two parents - Parent 1 with the relationship type set to "Subsidiary" and Parent 2 with the relationship type set to "Franchise Owner", and the following person to person relationship type sequence is defined in the system:

In the above example, the system will inherit effective price item pricing (if available) from Parent 1 or within its hierarchy. If the effective price item pricing is not available in the Parent 1 hierarchy, the system will inherit effective price item pricing (if available) from Parent 2 or within its hierarchy. If the effective price item pricing is not available in the Parent 2 hierarchy, an error message occurs indicating that the effective price item pricing is not available.

While searching effective pricing at the parent customer level based on the person to person relationship type sequence, the system will use the depth first search mechanism. Let us understand this with the help of an example.

In the above example, if the effective pricing is not available at the account or customer level, the system will search effective pricing at the parent customer level in the following order:

• P1 (because the first relationship type in the sequence is Subsidiary)

• P2 (grandparent of P1 irrespective of the relationship type)

• P3 (because the second relationship type in the sequence is Branch)

• P4 (because the second relationship type in the sequence is Branch)

• P6 (grandparent of P4 irrespective of the relationship type)

• P5 (because the third relationship type in the sequence is Franchise Owner)

The system provides you the flexibility to define person to person relationship type sequence:

• For each division, price item, and price item parameters combination

• For each division

• In the C1_​PER_​REL feature configuration

The system will first check whether the person to person relationship type sequence is defined for the division, price item, and price item parameters combination. If the person to person relationship type sequence is defined for the division, price item, and price item parameters combination, the system will search effective price item pricing at the parent customer level based on the sequence defined for the combination. However, if the person to person relationship type sequence is not defined for the division, price item, and price item parameters combination, the system will check whether the person to person relationship type sequence is defined for the division. If the person to person relationship type sequence is defined for the division, the system will search effective price item pricing at the parent customer level based on the sequence defined for the division. However, if the person to person relationship type sequence is not defined for the division, the system will consider the person to person relationship type sequence defined in the C1_​PER_​REL feature configuration and accordingly search the effective price item pricing at the parent customer level.

To enable the system to search person to person relationship type sequence at different levels, you need to create an algorithm of the C1-CUSRLALGT algorithm type and attach it to the Person Relationship Type Sequence Algorithm parameter in the price assignment search algorithm. The C1-CUSRLALGT algorithm type has the following parameters:

• Check on Division, Price Item and Price Item Parameters Combination - Used to indicate whether you want the system to search person to person relationship type sequence defined for the division, price item, and price item parameters combination. This is a mandatory parameter. The valid values are:

  • Y

  • N

  By default, the value is set to N.

• Check on Division - Used to indicate whether you want the system to search person to person relationship type sequence defined for the division. This is a mandatory parameter. The valid values are:

  • Y

  • N

  By default, the value is set to N.

• Check on Feature Configuration - Used to indicate whether you want the system to consider the person to person relationship type sequence defined in the C1_​PER_​REL feature configuration. This is a mandatory parameter. The valid values are:

  • A - Used when you want to consider all person to person relationship types defined in the feature configuration (in the specified sequence).

  • F - Used when you want to only consider the person to person relationship type defined with the lowest sequence in the feature configuration.

  • N - Used when you do not want to consider the person to person relationship type sequence defined in the C1_​PER_​REL feature configuration.

  By default, the value is set to F.

Related Topics