orders and contracts

[hans_bakker]

We need to be able to relate contractual information with an order.

Contractual information could be stored in the agreement related
enities. However I do not see a way to link agreements with a specific
order.

Add the orderId to the agreement Entity?

any opinions here?

--
Ofbiz on twitter: http://twitter.com/apache_ofbiz
Myself on twitter: http://twitter.com/hansbak
Antwebsystems.com: Quality services for competitive rates.

[David E. Jones-2]

What's the cardinality of the relationship?

If you add an orderId to the Agreement entity you'd basically have many agreements for one order, but you could not have more than one order per agreement.

It would probably be better to follow the same *Appl entity pattern, even used for some Agreement* entities, that structures a many-to-many relationship.

-David


On Jun 9, 2010, at 12:22 AM, Hans Bakker wrote:

> We need to be able to relate contractual information with an order.
>
> Contractual information could be stored in the agreement related
> enities. However I do not see a way to link agreements with a specific
> order.
>
> Add the orderId to the agreement Entity?
>
> any opinions here?
>
> --
> Ofbiz on twitter: http://twitter.com/apache_ofbiz
> Myself on twitter: http://twitter.com/hansbak
> Antwebsystems.com: Quality services for competitive rates.
>

[hans_bakker]

i David,

thanks for the reply, people work with standard contracts, so a single
agreement can be for many orders. On the other hand i expect that there
can be several different contracts for a single order (item)

It looks probably here the best way to enter a new entity following the
appl pattern as you mention:

AgreementOrderAppl:
        agreementId
        agreementItemSeqId
        orderId
        orderItemSeqId

I will add it when we get to it here and no further comment follow

Regards,
hans


On Wed, 2010-06-09 at 01:01 -0600, David E Jones wrote:

> What's the cardinality of the relationship?
>
> If you add an orderId to the Agreement entity you'd basically have many agreements for one order, but you could not have more than one order per agreement.
>
> It would probably be better to follow the same *Appl entity pattern, even used for some Agreement* entities, that structures a many-to-many relationship.
>
> -David
>
>
> On Jun 9, 2010, at 12:22 AM, Hans Bakker wrote:
>
> > We need to be able to relate contractual information with an order.
> >
> > Contractual information could be stored in the agreement related
> > enities. However I do not see a way to link agreements with a specific
> > order.
> >
> > Add the orderId to the agreement Entity?
> >
> > any opinions here?
> >
> > --
> > Ofbiz on twitter: http://twitter.com/apache_ofbiz
> > Myself on twitter: http://twitter.com/hansbak
> > Antwebsystems.com: Quality services for competitive rates.
> >
>

--
Ofbiz on twitter: http://twitter.com/apache_ofbiz
Myself on twitter: http://twitter.com/hansbak
Antwebsystems.com: Quality services for competitive rates.

[BJ Freeman]

I  used the layout on page 145-146 of vol one.


=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


Hans Bakker sent the following on 6/8/2010 11:22 PM:

> We need to be able to relate contractual information with an order.
>
> Contractual information could be stored in the agreement related
> enities. However I do not see a way to link agreements with a specific
> order.
>
> Add the orderId to the agreement Entity?
>
> any opinions here?
>