This transaction publishes invoice data that can be directed to an external accounts receivable system.
In environments that require an interface with accounts receivable systems, this transaction needs to be scheduled. This transaction raises an event for an invoice based on the following configuration at the following times in the order lifecycle:
Many of this transaction's elements and attributes are template driven. Refer to the XML for element level details.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | SEND_INVOICE |
Base Document Type | Order |
Base Process Type | Order Fulfillment |
Abstract Transaction | No |
APIs Called | getOrderInvoiceDetails() |
The following are the criteria parameters for this transaction:
Parameter | Description |
---|---|
Action | Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value. |
Number of Records To Buffer | Optional. Number of records to retrieve and process at one time. If left blank or specified as 0 (zero), it defaults to 5000. |
ColonyID | Required in a multischema deployment where a table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumInvoicesSent | Number of invoices sent. |
For this transaction the pending job count is the number of order invoices in created (“00”) status.
The following events are raised by this time-triggered transaction:
Transaction/Event | Key Data | Data Published | Template Support? |
---|---|---|---|
PUBLISH_INVOICE_ |
modifyOrder_dbd. |
YFS_getOrderInvoice |
Yes |
Additional events may be raised by the getOrderInvoiceDetails() API. For detailed information about the events, see the details provided under this API in the Sterling Selling and Fulfillment Foundation: Javadocs.