Best Of
Re: Remove Hard and Soft Commit
Hi,
So, you had incorrect Hard commit and soft commit quantities in F41021?
Do you also have some information in F41021WF?
If you didn't manually fix the F41021 via SQL, and you have information in F41021WF, you can roll back the F41021WF - see details here E1: 40: Manual Rollback Process of Item Location (F41021) File (P42210/R42210) (Doc ID 625445.1)
If your F41021WF is clear and your commitments are not OK in F41021, you would need to use R42995. However, this only works if you have an open sales order.
If you do not have any open sales order, you would need to create a 'dummy' sales order for that specific item so the program will correctly repost the quantities and amounts. The "dummy" order can then be cancelled after running the Repost Active Sales Orders (R42995) program.
Please see details in E1: 42: Repost Active Sales Orders (R42995) (Doc ID 625504.1) - section "What If No Actives Sales Order Exists Prior to Running the Repost Active Sales Orders (R42995)?"
This report will correct the F41021 commitments if they were created from sales orders.
Hope this helps,
Geanina
Re: Error p0010 "Company number invalid"
Hello,
Please open a service request for this issue.
Thank you!
Best regards,
Cezar
Re: WLS start with root user
Hello
It seems that the domain folder had been owned by oracle user and oinstall group.
So, you can run in the WLS domain folder, the following command to change the owner recursively. Please execute the command as root user.
chown -R oracle:oinstall *
or with a sudo-er user:
sudo chown -R oracle:oinstall *
Then tray to start the server. It should work
Thank you!
Best regards,
Cezar
Re: Export Oracle 19c
Yes, it is possible. The important thing is to run the export specifying the desired target version (12c). For example:
expdp your_user/your_password@your _19c_sid \ DIRECTORY=dp_dir \ DUMPFILE=your_export.dmp \ LOGFILE=your_export.log \ SCHEMAS=your_schema_name \ VERSION=12.2.0.1.0
Then you can do an import in the 12c database using impdp. Verify that the character sets of both databases are compatible to avoid data corruption during import and
be aware that certain features or object types introduced in 19c might not be supported in 12c. Data Pump will typically handle this skipping unsupported objects, but it's important to review the import log for any warnings or errors.
Re: Precedence of Destination Session Agent vs. DNS Query in SRS
Hi Daureen,
My understanding is also that the session agent works like a hosts file, so it shouldn’t be querying DNS.
Last week I confirmed the SRS was in service, but just now I saw it was out of service.
I simply changed the destination in the SRS settings to an IP address, and then everything worked normally.
Thanks
YyL
Re: ADI Error for TAG number
Hi Vidya
Check whether those deleted asset lines / Tag numbers exists in fa_mass_additions table.
When the assets are loaded, system validates both fa_additions_b as well as fa_mass_additions table
regards
Re: PUM 53 - Changes to EONC_NOTIFICATIONS.Notification App Package / Class Change Issue
Hello User,
While we wait for other to share if they have implemented the above scenario in their PUM 53, please have a look at the following Doc Id.:
Bind Variable Values are not displayed in Approval Email Notifications (Doc ID 2495424.1)
It was created for PEopleSoft HCM but it has information on how the variables get displayed.
When using bind variables (%1, %2, %3 and so on) in email notification templates, there must also be an SQL object that Approval Framework uses to populate the bind variables defined in the notification template. The first select field in the SQL object will be referred as %2 and second select field in the SQL object will be referred as %3 and go on.
By default, %1 which generates a component URL defined in the Configure Transactions page.
Re: mmon trace file
Hi Eileen,
The above message are informative and harmless and these messages were introduced from 11.2.0.2.
min active scn" introduced in 11g which is supposed to enhance delayed
block cleanout operations. Note : - Disabling min active scn optimization feature will not have any impact on database.
Issue was raised via bug 11891463 which was declared as not a bug from the development team and if you don't want these message then follow the below steps :-1) alter system set "_enable_minscn_cr"=false scope=spfile;
enable/disable minscn optimization for CR
2) Restart the database.
3) Check the issue is resolved or not-
In some cases it gets resolved and in some cases you have to apply the second solution .
Second Solution -
you can set in init.ora "_smu_debug_mode=134217728"
Best Regards
Ravikiran
Re: How is oracle golden gate license working for AWS RDS instances.
This is what I found:
GoldenGate is another data replication tool that is used for Extract ,Transform and load(ETL), database migrations, and DR. GoldenGate is a separately licensed feature for Oracle, which means it must be licensed for each database where it is in use. GoldenGate must be licensed on the source and target databases using the same metrics as the databases. For database migrations, GoldenGate licenses can be purchased as a 1-year term license if GoldenGate will not be used beyond the migration period. 1-year term licenses are 20% of a perpetual license cost and terminate one year from the date of purchase, You must still pay for support at the normal rate, but the cost of the license is much cheaper.
Source:
But licensing questions should be discussed directly with Oracle Sales, do not trust any answer from a forum.
Re: how we can secure customer master sales person , sales lead , sales manager, sales head wise
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
