Visibility In ABO Bulk Request Processing
(Doc ID 818866.1)
Last updated on NOVEMBER 20, 2017
Applies to:Siebel Bulk Order Capture - Version 126.96.36.199 SIA  to 188.8.131.52 SIA  [Release V7 to V8]
Siebel eConfigurator - Version 184.108.40.206 SIA  to 220.127.116.11 SIA  [Release V7 to V8]
Information in this document applies to any platform.
### checked on Currency on 17.11.2014 ###
Customer is using Bulk Order Request Module. Workflow step 'Build User Asset' from 'ABO Bulk Request - Modify Sub-Process Workflow' calls business service 'ABO Bulk Request Processing Service', method BuildInstanceAsset. This method searches for assets with a search specification based on possition visibility for the assets.
Question: Is there any possibility how to change mode to AllVisibility?
Customer does not use position visibility for the assets for custom reasons. Instead visibility is based on accounts. Bulk order module works only on assets that were created by the user who creates the bulk requests. In customer's case most of the assets are created by SADMIN user as a part of the automated process when order is completed. The current visibility does not return all necessary assets.
When the asset is not found bulk ordering request status will be set to "Partially Complete" and it will have an exception that looks similar as follows:
“No Asset of Product = 'xxxxxx' Exists to delete for Account Id = '1-XXXXX'.”
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|