The addInvoice(), updateInvoice(), and removeInvoice() methods of the InvoiceManager all generate JMS messages of class atg.commerce.invoice.messaging.InvoiceMessage. This class includes the following properties:
repositoryId(String)
orderId(String)
paymentGroupId(String)
profile(RepositoryItem)
invoiceNumber(String)
PONumber(String)
requisitionNumber(String)
billingAddress(atg.core.util.ContactInfo)
preferredFormat(String)
preferredDeliveryMode(String)
balanceDue(Date)
paymentDueDate(Date)
paymentNetDays(Integer)
paymentDiscountDays(Integer)
paymentDiscountPercent(Double)
The inclusion of basic invoice properties in the message allows you to build scenarios that are invoice-driven, while the inclusion of the orderId and paymentGroupId allows more complex Oracle ATG Web Commerce-based message sinks to retrieve the invoice using the InvoiceManager and perform any required data transformation (such as translation to XML) before passing the invoice information on to external systems.
By default, invoice messages are sent to the Scenario Manager via Local JMS, but you can change your configuration to use SQL JMS if your system requires perfect reliability (see the Dynamo Message System chapter in the ATG Platform Programming Guide for more information on JMS and its alternatives in the Oracle ATG Web Commerce platform, and on the Patch Bay).
