High-Volume Interval Data Push Create references

This service has the following prerequisite:

• Before the interval data can be exported at high-volume it has to be received and undergone validation, estimation, and editing. The interval reads have to be stored in the readings table with the appropriate reading status.
• After daily reading imports are completed and the data is stored, the high-volume billing export can be scheduled. The high-volume billing export is put on a recurring schedule and the exact time of the export has to be defined.
• If not all interval data is exported on a daily basis the subset of service point channels that should be exported has to be defined before the web-service can be kicked off.

This service fails if one or more of the following conditions apply:

• Profile Allocation ID must be defined in IEE MDUS.
• The SAP Interval Data Export flag must be set to True. If this is set to False, then this service point will not be included in ADE group list, and the ADE export will fail.
• The AMI Data Export task must be configured and running.
  • The Output Format is not defined correctly on the AMI Data Export task. Set the Output Format to either SAP Web Service Writer or SAP File Writer. For integration with SAP, use the Web Service Writer.
  • The SAP External System is not configured correctly on the AMI Data Export task. The External System is configured in IEE External System Code table, and then it is specified in the Requesting System field on the AMI Data Export task Processing Tab.
  • The Entity Type and ID are not defined correctly on the AMI Data Recurring Request task.

For more information about configuring the ADE task templates, see the IEE User Interface Help or the IEE Configuration Guide.

Other conditions might also cause the service to fail. This list is intended to help with troubleshooting and is not intended to be comprehensive.