Inbound BOD usage
This table shows the incoming BODs that Optiva can accept. It also indicates, when possible, what area of Optiva shows the processed inbound data.
| Verb | Noun | Destination of processed data in Optiva |
|---|---|---|
Process
|
BillOfMaterials
|
Formula object |
Acknowledge
|
BillOfMaterials
|
This scenario occurs only if data cannot be imported by Optiva. |
Sync
|
CustomerPartyMaster
|
Company object
If the customer does not exist in Optiva, then a Company object is created for that customer. If the customer does exist in Optiva, then the Company object is updated with the most recent address and contact information. |
Sync
|
ItemMaster
|
Item object |
Acknowledge
|
ItemMaster
|
This scenario occurs only if data cannot be imported by Optiva. |
Sync
|
SupplierPartyMaster
|
Company object
If the vendor does not exist in Optiva, then a Company object is created for that vendor. If the vendor does exist in Optiva, then the Company object is updated with the most recent address and contact information. |
Sync |
SecurityUserMaster |
User object. If a user does not exist, it is created. Once the user is created, or if it already exists, we then adjust the Roles on the User to match what is sent in the BOD. |
Sync |
CodeDefinition |
Enumerated list. If an enumerated list does not exist, then the missing enumerated list is created. If the enumerated list does exist, it is updated with the most recent values from the BOD. |