Why is the relation B2BCustomers2Approvers mapped to deployment table name empl2apprsrel?

[Former Member]

Hello,

I am just curious. Why is it mapped like this?:

     <relation code="B2BCustomers2Approvers" localized="false"
                       generate="true" autocreate="true">
         <deployment table="empl2apprsrel" typecode="10023"/>
         <sourceElement type="B2BCustomer" collectiontype="set"
                        cardinality="many" navigable="false">
             <modifiers read="true" write="true" search="true"/>
         </sourceElement>
         <targetElement type="B2BCustomer" qualifier="Approvers"
                        cardinality="many" collectiontype="set">
             <modifiers read="true" write="true" search="true"/>
         </targetElement>
     </relation>

The table name empl2apprsrel suggests that the relationship holds an employee to approvers relation but that is by the definition of the relationship impossible.

Best Regards

[arvind-kumar_avinash · Accepted solution]

That’s a good question. The answer is in the following relation defined in the same file (b2bapprovalprocess-items.xml):

 <relation code="B2BUnit2ApproverGroup" localized="false"
           generate="true" autocreate="true">
     <deployment table="unit2approverGrpRel" typecode="10021"/>
     <sourceElement type="B2BUnit" navigable="false"
                    cardinality="many">
         <description>The Parent B2BUnit</description>
         <modifiers read="true" write="true" search="true"
                    optional="false"/>
     </sourceElement>
     <targetElement type="B2BUserGroup" qualifier="ApproverGroups"
                    cardinality="many" collectiontype="set" ordered="true">
         <description>User groups associated to a B2BUnit that hold other employees who can approve orders</description>
         <modifiers read="true" write="true" search="true"/>
     </targetElement>
 </relation>

After going through the description of the targetElement, B2BUserGroup, you might have already understood the reasoning behind naming the deployment table like this.

For the sake of clarity for the general audience: the reason is that a B2B customer is an organization which has B2BUnits and the B2B users are basically employees belonging to one of the B2BUnits. Therefore, in contrast to B2C, where customers are end users and employees are store managers, merchandisers, cs agents, admins etc., the naming convention used for deployment tables in this file are aligned with the concept of B2B users.

Best Regards