Field Activity Completion
The system provides a staging table to use to upload and complete field activities. However, this staging table has limitations as described in
field activity completion considerations. For these reasons and to enable to support
integration through XAI, the base product provides a sample service (called CIPOASTP) that can be invoked by XAI to support completion of the all step types, including the "generic" step types and the "standard" step types. We provide an XAI Inbound Service, C1FACompletionWithSteps, defined to invoke this service. The sample service:
• Creates field activity upload staging and FA step upload staging records
• If meter read information has been provided, it creates a meter read record and its corresponding register reads.
• For any of the "generic" steps, the process updates or creates the appropriate record(s) and populates the id of the record updated as the foreign key for the FA step record. For example, for the Change Meter step type, the process updates the meter record with the information provided through XAI and links the meter id to the FA step record.
• The process then performs the standard "complete step" logic. For the "generic" step types, the FA step should simply be marked as complete because the foreign key is already linked. For the "standard" step types, the completion logic described in
FACOMPL - Upload and Complete Field Activities is performed.
Fastpath:
Refer to
Field Activity Completion Considerations for the list of "generic" and "standard" step types.
• Creates an FA log entry with a log type of Order Completion to indicate that the field activity has been completed by an external system.
• Standard FA completion logic is also performed. For example, completion algorithms are executed, etc.
Note:
The sample service provided by the system may not provide all the functionality your implementation requires for completing every "generic" step. For example, not all service point, meter or item fields are included in the list of fields that may be updated. If the sample process does not satisfy your needs, your implementers should copy the sample process and modify the new process as needed.
Characteristic limitation. The sample service limits the number of field activity characteristics that may be uploaded to 100.
Error Handling. If any error is found during step completion, this sample service backs out all changes and issues an error indicating the problem.
Parent topic