Hello,

1.  In regards to MOAC, Oracle Sales (ASN) allows the users to view opportunities created in all orgs - this is by design. 

• Development has made changes in release 12 relating to Multi Org Access Control (MOAC).  In release 12 we now populate the org id for as_leads_all and as_lead_lines_all, but not for as_accesses_all.  Now, when a new opportunity is created, the Opportunity and the opportunity line should have the default OU populated to MOAC defaulting rules.  This is what the MOAC profiles control - not the actual access to leads and opportunities. 
• In order to control access levels for leads and opportunities, you'll need to review the Sales security setup and the resource/group setup in Territory Management.  When users log into sales, it is looking for customers that they are on the sales team for the object and what resource group they are members of to see what they are able to view - regardless of the MOAC profile options. 

You can review the Sales Security access for Opportunities and Leads in:  Oracle® Sales Implementation Guide Release 12.1 Part No. E13440-02 p4-22 About Sales Security section

Oracle Sales security is controlled by a set of profile options that are grouped into the following categories:

• Customer Access Security
• Lead Access Security
• Opportunity Access Security
• Forecast Security

Additionally, security differs based on whether the user is a sales representative or a sales manager.

The following are the profile options that effect this:

ASN: Customer Access Privilege profile

ASN: Lead Access Privilege profile

ASN: Opportunity Access Privilege profile

2.  If the MO: Security Profile, gives the User access to 3 Operating units, then the Items mapped are restricted to the Inventory Organizations attached to those 3 Operating Units.

• The product search by itself does not restrict items related to the Inventory Organization of the Operating unit.  The Product Search can be personalized to disply only the items related to the Opertaing unit to which the user has access via a personalization by responsibility.  In the Personalization page, you can set the 'Rendered' Property to 'True'. 
• The Product Search by itself does not restrict items related to the Inventory Organization of the Operating Unit. The Product Search can be personalized to display only the items related to the Operating Unit to which the User has Access. You can do this via personalizations by responsibility.  In the Personalization page, set the “Rendered” Property to True. 
• If the MO: Security Profile option give the user access to 3 Operating units, then the items mapped are restricted to the Inventory Organizations attached to those 3 Operating units.

3.  If you want users to be able to select the Operating Unit for the products, you can do this via personalizations - you need to change the "Message Choice: Operating Unit Read Only = False" at the responsibility level. I have documented a test case scenario for you below to add this (I did mine at the Organization level - you can do this by responsibility also)

    Log into Sales Dashboard > Opportunities > Open Opportunity
    Click on Products Tab
    Click Personalize Page
    Personalize Page: Add Product
    Select Personalization Level = Organization Vision Operations
    Content Tab
    Click on Pencil Icon next to Product

    Scope  Page: Add Product
    Document Name  /oracle/apps/asn/common/webui/PrdtLovSelPG
    Organization  Vision Operations

    Message Choice: Operating Unit > Click on Pencil Icon
    Changed:
    Rendered = "True" for Organization: Vision Operations
    Read Only = "True" for Organization: Vision Operations

    Click Apply and return to application
    For Sales User responsibility > Organization: Vision Operations > shows default  

• The Opportunities are filtered by Org Id attached to them. The Opportunity Access Profile Options are used by Oracle TeleSales but not by Oracle Sales.  The ORG_ID attached to the Opportunity is passed from the UI screens based on the Security profile defined (there is no current functionality to allow the user to select which Org ID they want to create the lead or opportunity for)
• When adding products to an opportunity, the product search by itself does not restrict items are related to the Inventory Organization of the Operating Unit. The Product Search can be personalized to display only the items related to the Operating Unit to which the User has Access. In the Personalization page, set the “Rendered” Property to True.  Therefore it is possible to add products from multiple operating units to a single Opportunity. But when the Opportunity is converted into a Quote, the Operating Unit specified decides which Operating Unit the Quote should be assigned to and hence two Quotes will be created – one for each Operating Unit having the Product assigned to that Operating Unit.
• So basically, the Ord_ID Attached to the opportunity is there for 2 reasons - even though Sales does not use it inside the application, when you convert the opportunity to a quote, the org_id attached determines which ORG_ID is put on the quote - and if the opportunity has more then one org_id attached to the lines, 2 quotes will be created.  The second reason is that while Sales does not use it, TeleSales does use the org_id, so therefore the org_id has to be on the opportunity if you are using both products

Thank you,

Bobbi