Our team is evaluating two approaches for automating daily sales reports that feed into our external analytics platform. We’re running JDE 9.2.1 and need to extract sales order data, customer information, and fulfillment status every morning.
Option 1 is using REST API calls to pull data in real-time throughout the day. This gives us immediate access to sales orders as they’re created, but I’m concerned about API gateway requirements and potential rate limiting issues during peak order entry periods.
Option 2 is leveraging Embedded BI Publisher to generate scheduled XLSX reports that our analytics team can import. This seems simpler from a security perspective since everything stays within our internal network, and BI Publisher already supports the XLSX format our downstream systems expect.
The complication is that we have some custom sales workflows that might need additional orchestration or scripting regardless of which approach we choose. Has anyone implemented similar sales reporting automation? What factors helped you decide between real-time API integration versus scheduled report generation?
You can actually do both - start with BI Publisher for your batch reporting needs and add REST API endpoints later for real-time use cases. They’re not mutually exclusive. We run BI Publisher for compliance reports and nightly data loads, while using REST APIs for our customer portal that needs live order status. The key is designing your data model so both approaches can coexist without conflicts.
We went with BI Publisher for similar requirements. The XLSX output integrates seamlessly with our data lake, and security was much simpler to implement since we didn’t need to expose API endpoints. However, we did sacrifice real-time visibility - reports run every 2 hours instead of pulling live data.
The decision really depends on your latency requirements. If your analytics platform needs up-to-the-minute sales data for operational dashboards, REST API is the way to go. But if daily or hourly reporting is sufficient, BI Publisher will save you significant infrastructure overhead. We use REST APIs but had to implement request throttling and caching to handle peak loads. The API gateway configuration alone took three weeks to properly tune for our sales volume.