Custom Workflow Process Similar To "SIS OM Edit Complex Asset Workflow" Does Not Set Action Code As Expected (Doc ID 846757.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Configurator Runtime, SPE - Version 8.0.0.3 SIA [20416] and later
Siebel eConfigurator - Version 8.0.0.3 SIA [20416] and later
Information in this document applies to any platform.
***Checked for relevance on 12-Aug-2011***
***Checked for Relevance on 06-Oct-2014***


Symptoms


A custom workflow process similar to "SIS OM Edit Complex Asset Workflow" does not work as expected.

The basic workflow process steps are:

Version A:
1. Load the original asset using EAI Siebel Adapter.Query method.
2. Load the modifications to this asset from existing open orders using SIS OM PMT Service.Find Orders method.
3. Apply these changes to the original asset using SIS OM PMT Service.Apply method.
4. Calculate the delta using SIS OM PMT Service.Delta method.

Version B:
1. Load the original asset using EAI Siebel Adapter.Query
2. Load the modifications to this asset from existing open orders using EAI Siebel Adapter.Query
3. Convert the modified line item to asset using SIS OM PMT Service.Convert Product Instance (so that both integration objects are of type SIS OM Asset)
4. Create Delta between the original asset and the modified asset

Neither of these workflow processes produces the correct result.

Result from Version A:
When loading the changes from existing open orders, the line item with action code "Delete" is not present in the result, so this change is not propagated with the Apply method to original asset.
Here is an example:

1. Original complex asset

- Complex Product
|_ Component 1

2. Create a modification order from this asset replacing the Component 1 by Component 2. This results in:

- Complex Product
|_ Component 2 (Action Code: Add)

3. Applying this modification to the original asset using the Apply method results in:

- Complex Product
|_ Component 1 (Action Code -)
|_ Component 2 (Action Code Add)

4. Creating the Delta between product instances from step 1. and 3. results in:

- Complex Product
|_ Component 1 (Action Code -)
|_ Component 2 (Action Code Add)


Result from creating the Delta in Version B:
This approach set correctly the action codes on added and deleted components but it also changed the action codes on every component that were not changed to "Modified".

Using the previous example the result from step 4. was like this:

- Complex Product (Action Code: Modified)
|_ Component 1 (Action Code Deleted)
|_ Component 2 (Action Code Add)


The expected result is:

- Complex Product
|_ Component 1 (Action Code Delete)
|_ Component 2 (Action Code Add)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms