Best Of
New Document to a List Of Tokens and Expiration Time of Inbound Web Service for Mobile Connections
Although there is no out-of-the-box functionality to check for a list of tokens and expiration related to Inbound Web Service for mobile connections, this new KM document provides detailed steps to do so using custom logic. Doc ID 2973551.1. https://bit.ly/3RCvw8T
#SiebelCRM #Integrations
Re: Quick Credit Functionality in Invoice Workbench
Quick credit can be used on both PO and Non-PO invoices. It is designed to make a full reversal of the credited invoice so it's not able to be used in cases of partial credits. In case of partial credit you should be using the corrections button. This gives the option of doing a price correction, quantity correction, or amount correction. Price and Quantity corrections are used for PO matched invoices. A price correction will not affect the quantity billed on a PO as it will only affect the invoice price variance account(best used for price-variance credit memos). A quantity correction will change the quantity billed on the PO(best used for credit memos for returned/rejected items). An amount correction is generally used for non-PO-matched invoices and will simply create the credit memo distributions using the same distributions from the credited invoice.
PS - If this answers your question, please mark it as helpful or correct in order to assist other community members who may have the same question.
Checking DNS before patching ODAs
I ran across an interesting problem that caused an error during our patching from ODA 19.19 to ODA 19.20. After running this command:
odacli create-prepatchreport -d -i <db home id> -v 19.20.0.0.0
I got this error:
Internal error encountered: Failed to run create dbhome OraDB19000_homeXX : null.
I opened a ticket with Oracle support and they suggested I check the DNS servers in /etc/resolv.conf to make sure they are all responding. One way of checking them all is running:
/usr/bin/nslookup unknown-not-reachable-node
If one of the servers is not responding this command will hang. If this happens then remove the bad DNS server entry from /etc/resolv.conf before patching. This resolved my problem, and I ran the create-prepatchreport command again and it successfully completed.
I am going to add this to my ODA pre-patch checklist and am posting this out to the community in case anyone else runs into this issue.
Louis



