Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Production Management

Request parameters

  • Last UpdatedAug 29, 2023
  • 4 minute read

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.

SubmitDataRecords section

Contains a set of data records to submit.

<SubmitDataRecords>

<SubmitDataRecord>

<Module>Inventory</Module>

<Location>Material Movements.Production to Silo</Location>

</SubmitDataRecords>

Parameter

Description

SubmitDataRecord

An individual data record, containing the necessary information to submit when using AMQP protocol. When passing XML schema, it is necessary to use <Records> instead of <SubmitDataRecord>.

Module

(Required) Module maps to one of the standard AVEVA Production Management modules and names the specified module in the request. This can be any module, such as Downtime, Production, Inventory.

Location

(Required) You provide the Location field. For most modules, this parameter specifies the exact reporting point that you are inserting into. Do not use the parent folder.

You can use different locations for different SubmitData records. In the case of Inventory, the location can be any movement configuration item, including the default AdhocMaterialMovement item or any Routine movement item in Studio. It can also be a dynamic material movement. In the case of an adjustment, the location is the relevant equipment.

RequestOrigin section

Contains the request origin that determines the origin of the webservice request.

<RequestOrigin>"2374987"</RequestOrigin>

Parameter

Description

RequestOrigin

This is an optional string value that determines the origin of the webservice request. This value can be checked as a property on the recordChangedEventArgs in code items to ensure the event wasn't triggered by the same origin to prevent infinite loops.

MergeCriteria section

If you do not provide an ID, provide a MergeCriteria with key field names. The values for these key field names are specified under Fields/Field Name/Value. If you are searching for fields that don't have a value, use the filter keyword "nothing". Field are required to be filterable for use as merge criteria. This section is optional.

<MergeCriteria>

<SetId>0</SetId>

<KeyFieldNames>

<FieldName />

</KeyFieldNames>

</MergeCriteria>

Parameter

Description

SetId

Identifies the unique record to update. This parameter maps to the row.id returned by GetData. If you provide an ID, no other information is required and the record updates.

If the record with the ID does not exist, AVEVA Production Management returns an error. If you don't know the SetId, you can find an existing record through the KeyFieldName filter. If a record cannot be found using the filter, AVEVA Production Management creates a new record.

To submit a new record, use ID=0

Circumstances

What happens

If SetId > 0

Request is handled as an Update, and no fields should be specified in MergeCriteria.

If SetId = 0, and no merge field is specified

Request is handled as an Insert.

If SetId = 0, and merge fields are specified

AVEVA Production Management tries to find the record that corresponds to merge criteria.

  • If only one record is found, the operation is handled as an Update.

  • If no record is found, the operation is handled as an Insert.

  • If multiple records correspond to the provided merge criteria are found, a business error occurs.

KeyFieldNames

Contains the set of key field names.

FieldName

The FieldNames element enables you to create filters to find existing records, when you do not know the SetId. This value matches a corresponding value below in the Field.Name element.

Fields section

Contains the set of fields to update. A single field contains a Name and Value element.

<Field>

<Name>Destination Lot</Name>

<Value>Lot1</Value>

</Field>

Parameter

Description

Name

The name of the field to insert or update.

Value

The value to submit for the named field.

Action section

Specifies the type of movement or adjustment to perform.

<Action>Movement</Action>

<ActionSpecified>true</ActionSpecified>

Parameter

Description

Action

Specifies the type of movement or adjustment. When you select Movement, Adjustment, Survey, or MaterialRequirement the action is performed in AVEVA Production Management immediately. When you select MovementEvent, AdjustmentEvent, or SurveyEvent the action is performed when the record is reprocessed. Most action types are relevant only for Inventory. MaterialRequirement is specific to Planning. This parameter is optional.

Valid options: Movement, MovementEvent, Adjustment, AdjustmentEvent, Survey, SurveyEvent, MaterialRequirement.

ActionSpecified

When submitting a movement, you need to specify ActionSpecified as True.

In This Topic
Related Links
TitleResults for “How to create a CRG?”Also Available in