Data Driven Delivery
In addition to the options to send report definition output to static printers and specific email addresses, you can direct output to recipients and printers based on an XPath field from the XML data. For bursted reports, the XPath value could be different for each recipient, depending on which XPath is used.
Three different combinations are possible with data driven delivery:
Data driven email only.
Data driven printers only.
Both data driven email and printers.
The system handles email to address book number and distribution list types differently than other recipient values. Data driven delivery for address book numbers and distribution lists relies on existing JD Edwards EnterpriseOne address book functionality. As a result, you only need to enter an XML field that contains address book numbers (such as <AddressNumber_ID1>) as the data driven recipient for report definition output.
In the case of data driven delivery to printers, you must first create a relationship between an appropriate XML field (such as <Company_ID5>, <CostCenter_ID7>, etc.) and a printer delivery mapping name. The XML field is also known as a delivery tag. Once the mapping name has been created, you associate different XML field values with the desired printer delivery name and assign a printer device to each field value as required.
To use both data driven email and data driven printer delivery for the same report definition submission, you must create a custom report variable (RV) in Report Design Aid and populate it with either an address book number (for email delivery) or an appropriate XML field (such as <Company_ID5>, <CostCenter_ID7>, etc.) for printer delivery. You would then enter the custom delivery tag as the delivery tag in the Report Definitions Printer Mapping application (P95621).