Best Of
Depot Repair: Return Portal - Basic Setup
The Returns Portal is new feature of Depot Repair introduced in R12.2.2 which provides an effective and efficient way to enable customers to return products. Customers may exchange or return products for service, testing, calibration or trade-in credit. The Returns Portal allows customers, business partners, and retail associates and distributors to request returns directly via a web portal.
Here are the basic setup which needs to be enable to use Return portal. It can be modified further based on business needs for example rule can be enabled for Return Parameter value.
Return Portal Repair Type
==========================
Depot Repair > Setup > Returns Portal > Return Types > define a new return type and association of rejection reason
Descriptive Flexfield
==========================
System Administrator > Flexfield> Descriptive > Segment > Enable Freeze Flexfield definition flag of DFF "Additional Information for Agents" and compile the same.
Return Parameter and Values
==========================
1. Depot Repair > Setup > Returns Portal > Return Parameters
2. Depot Repair > Setup > Returns Portal > Return Parameter Value
Please refer the attached image for both steps
Profile Option
==========================
It can be set up at responsibility level and is required to default the values to create service request.
1. CSD: Returns Portal Mode = Store Returns (to display customer related field)
2. CSD: Default Service Order Inventory Org
3. CSD: Default Service Request Owner for Bulk Receiving
4. CSD: Default Service Request Severity for Bulk Receiving
5. CSD: Default Service Request Status for Bulk Receiving
6. CSD: Default Service Request Type for Bulk Receiving
7. CSD: Default Service Request Urgency for Bulk Receiving
8. CSD: Default Service Type for Bulk Receiving
9. CSD: Default Service Request Summary for Bulk Receiving - Free Text so you can enter "Return Repair" as an example.
10. CSD: Default Subinventory for Bulk Receiving (This can be set using preference option available at responsibility level i.e. Edit > Preferences > Profile and this is due to values are dependent on profile option CSD: Default Service Order Inventory Org)
Cache Clear
==========================
1. Using Functional Administrator responsibility navigate to Core Services > Caching Framework > Global Configuration
2. Click on "Clear All Cache" button
3. Answer Yes
4. Wait for the message indicating that the cache has been cleared
5. Logout
6. Re-logon and navigate to Returns Portal
Jai Soni
ANNOUNCEMENT: Changes to Open Authentication (OAuth) for EM patching
Authentication changes at the Oracle side require that customers who perform patching operations through Enterprise Manager (EM) make configuration changes to their EM environment.
Beginning with EM 13.5 Release Update 19, for EM to comply with the move of OAuth from OAM (Oracle Access Manager) to IDCS (Oracle Identity Cloud Service), the EM configuration requires changes in order to authenticate to the IDCS OAuth endpoint. You can find the details in this document:
- Release of Fixes to Support OAuth move from OAM to IDCS (Doc ID 2998693.1)
In Case You Missed it: Advisor Webcast for Troubleshooting Project Accounting Budgetary Control
The Advisor Webcast for EBS Projects: Troubleshooting Project Accounting Budgetary Control was presented and recorded on January 23. The slides and recording are available on Doc ID 2992745.1. https://bit.ly/4alJgf2
Re: Submit Accounting vs Create Accounting
1) ARTERRPM module: Revenue Recognition Master Program
2) ARTERRPW module: Revenue Recognition with parallel workers - could be numerous
3) ARREVSWP - Revenue Contingency Analyzer
4) XLAACCPB module: Create Accounting
5) XLAACCUP module: Accounting Program
5) GLLEZL module: Journal Import
but Create Accounting will just run Create Accounting
submit Accounting runs Revenue Recognition before spawning Create Cccounting.
Create Cccounting does not process invoices with rules until Revenue Recognition is run.
So if Create Accounting is run after an invoice with rules is created then it will fail.
But if you run Submit Accounting then the system will run Revenue Recognition then Create Accounting.
Regards
Michele
Re: How to stop further use of a project on requisitions.
Hello, Helen,
There are a couple of things that can be done, with some caveats.
The main approach is to set transaction controls for each expenditure category or type with chargeable = Yes and end-date = date after which you don't want new requisitions. This will stop new EXPENSE requisitions being created with dates later than the end date on the control. Notes on inventory below.
Inventory requisitions and POs don't check transaction controls (standard functionality). You can create personalizations on the requisition and purchase order forms to check the transaction controls on Inventory destination distributions. Be aware that if you import requisitions or POs, the form personalizations won't fire (since the user isn't on the form).
You can also consider updating the PO approval workflow to check the transaction controls and reject with an appropriate message if the task can't accept the cost.
Don't put an end-date on the task itself. While that end date will stop new reqs, it will also make any onhand inventory invisible to the inventory/WIP/planning modules so you can't pick/build/ship/receive against it. You could put end dates on tasks if you first check that there is no inventory, open PO, open AP invoice, WIP job, etc. related to it.
If you put in a transaction control that says that expenditure type ET1 is chargeable until 01-Feb-24, receipts that arrive after that date will still be accepted because inventory receipts don't check transaction controls. Even if you set the whole project to status Closed, inventory transactions such as receipts will still come through. In this particular case, this works in your favor since setting a date won't block transacting any pre-existing POs but it's also something to be aware of if you had hoped to be able to fully stop transactions on a project.
Regards,
J
Re: OEM OMS Update 13.5.0.17 Patch 35460709 - ADF_FACES Error Incidents
Oracle Enterprise Manager 13c Release 5 Update 19 (13.5.0.19) for Oracle Management Service Patch 35861059 or later appears to have the fix for this issue. I have not applied it yet, as we are waiting for all the Weblogic etc patches to be available so that they can all be applied at the same time instead of taking multiple outages to fix this.
Re: Client Installation returns ' The java.library.path system variable is missing or invalid'
Please try to install the following lib:
yum install libnsl.x86_64
and retry the installation.
BR
Jörg
