Actually, it is quite simple, and I have discussed this many times. The
user is assigned to an internal organization (using the UserPreference
entity). When a user creates an order, they are assigned to the order in
the role of ORDER TAKER and their internal organization is assigned to
the order in the role of INTERNAL ORGANIZATION. Finding orders by user
or by internal organization is easy.
-Adrian
On 3/5/2012 8:20 AM, Hans Bakker wrote:
Adrian it is much more than that, when he enters an order in ecommerce
the order should be for his company and not for him personally, he
should be able to see the data/oders of his company (also entered by
others) and there are many other cases......
On 03/05/2012 03:16 PM, Adrian Crum wrote:
There is no need to make it mandatory, just supply a default if one
isn't explicitly assigned (the "Company" internal organization for
example).
-Adrian
On 3/5/2012 8:13 AM, Hans Bakker wrote:
At the moment the system is focused being a b2c (business to
consumer) system. We are now getting more and more requests for
systems mainly for b2b (business to business)
The main difference is that in the b2c case the order/invoice is for
the person and in a b2b the order/invoice is for the related company
of that person.
In the registration process a person can register referring to a
company, a second person can register to the same company however
somewhere needs to be a approval process.....
I was thinking introducing a system parameter to make the related
company of a person mandatory or not....
any thoughts on this?
Regards,
Hans
