GetReportingPointAssociations request message
- Last UpdatedSep 06, 2023
- 1 minute read
This is an example of the full structure of a GetReportingPointAssociations request.
<GetReportingPointAssociationsRequestMessage xmlns="http://www.citect.com/Ampla/Inventory/2010/03">
<Request>
<Credentials>
<Password>********</Password>
<Session />
<Username>User</Username>
</Credentials>
<Filter>
<WorkCenter>Enterprise.Coal Site 1.ROM Stockpile</WorkCenter>
<Material>Material Class.Raw Coal</Material>
</Filter>
</Request>
</GetReportingPointAssociationsRequestMessage>
Request parameters: Credentials section
The Credentials section contains the security details for authentication. You can provide the Username and Password values to use the Basic security method. If you do not provide explicit security values, Web services will attempt to use Integrated authentication. You must provide either Basic credentials, Integrated credentials, or a Session ID.
<Credentials>
<Username>User</Username>
<Password>********</Password>
<Session />
</Credentials>
|
Parameter |
Description |
|---|---|
|
Username |
The login name of the AVEVA™ Production Management user. This is a string value. Username and Password together are mutually exclusive with Session. |
|
Password |
The password that is associated with the AVEVA Production Management user. This is a string value. Username and Password together are mutually exclusive with Session. |
|
Session |
A GUID string value that identifies the session. This is a string value. Mutually exclusive with Username and Password. |
Request parameters: Filter section
Contains optional filter elements.
<Filter>
<WorkCenter>Enterprise.Coal Site 1.ROM Stockpile</WorkCenter>
<Material>Material Class.Raw Coal</Material>
</Filter>
|
Parameter |
Description |
|---|---|
|
WorkCenter |
The name of a valid work center to filter results by that work center. |
|
Material |
The name of a valid material to filter results by that material. |