I used the model on page 146
and the example agreementID 10002
since the Agreement has the product agreement, the service matches the
product agreement productID and updates the orderitem orderterms(page
128) and table 4.9(page 129) . an SECA checks that the order terms can
be accepted based on the order, like a promo may be disqualified based
on the order terms.
=========================
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>
Jacopo Cappellato sent the following on 7/2/2010 3:26 AM:
When an order is initiated, it is possible to select an agreement that will
govern the orders (OrderTerms are cloned from AgreementTerms, if the agreement
has a price list then the agreement prices are used in place of ProductPrice);
however the agreementId is only added to the cart but it is lost when the order
is saved.
This causes issues if the order is edited: the agreement is lost and the system
is unable to apply the agreement prices to the edited order.
The solution I am proposing is to add the agreementId field to OrderHeader
entity.
What do you think?
Jacopo
