Best Of
Re: Long Password
Hello,
Here are the answers:
A1. You need to restart the Enterprise Servers acting as Security Servers and the JAS servers. The Long Password feature is read by the E1 HTML instance during start-up and checks if *LPENABLE row exists in F98OWSEC
A2. The policies need to be changed after activating the Long Password. This is because after enabling the Long Password the policies will be stored in the BLOB filed of *LPENABLE row.
A3. Yes
A4. No. There is no feature which has to be enabled for long passwords for proxy/system users.
Starting with 9.2.4.3 tools release, the proxy/system users passwords may have 40 characters and it is case sensitive. So in P980001 passwords longer than 10 characters are accepted.
A5. Is not clear what you are asking. If you want to apply the long password for some of the users based on their groups, this is not possible. When enabling Long Password, all users will benefit of it.
NOTES:
1. The short passwords will still be accepted. It is not required to change the passwords after enabling Long Password feature;
2. The password policies will apply only when the password is changed by the users and they are never verified during the login process.
3. When Long Password feature is enabled, the passwords are case sensitive.
4. Once the Long Password feature is enabled, it cannot be disable and revert back to the classic short password, unless a backup of F98OWSEC is restored.
Thank you!
Best regards,
Cezar
Re: I want to un-remit receipts; user wrongly remitted in wrong bank account... there are total of 5200
Hello,
If the funds were collected for those receipts then a data fix to change status back to Confirm will not work.
You need to reverse the receipts and create them again.
Regards,
Nanzy
Re: I want to un-remit receipts; user wrongly remitted in wrong bank account... there are total of 5200
Hi
We can move them to Confirmed via datafix.
There is a script available : AR_DFS_RCT_RMT_TO_CONF.sql
You can refer to Note 2873187.1
Run the sql provided in the Note and see if same rows are returning.
Best Regards,
Bharat
Re: How to select multiple rows in form request without any filter with range e.g. first 100 records etc
Have you tried using the Maximum Records setting in the form request? It's under "Form Request Options."
Re: Possible business scenarios in Order Management
Oracle has supported most of the business flows when it comes to order fulfillment
Case 1: Ur warehouse needs material and ur other location warehouse has sufficient material to ship it to you. Use IR/ISO process.
Case2: Ur warehouse needs material against demand like a Customer SO. Ur warehouse at other location has material. U can request other warehouse to fulfill the customer order. - Direct Ship Process. No receiving into warehouse which has the customer demand. Other warehouse ships product directly to Customer.
Case 3: None of ur warehouses has material. Ur supplier or Third Party Vendor has material. Create a Drop order order if u want to ship directly from supplier to customer.
Case 4: None of ur warehouses has material. Ur supplier or Third Party Vendor has material. U do not want ur supplier to know the customer details. Create a Back to Back Order. A PO gets created against ur SO to supplier. Receive the PO and ship the parts to customer.
Hope I covered most of the scenarios. If u have any other scenario, which is not covered, let me know.
Note: All these processes have certain limitations.
Regards,
N
655919
Address Book Record Search Type WARNING
Our users are getting this error message. Can someone please advise what to check.
Issues (click each label for more information):
| Address Book Record Search Type WARNING
 |
|
||||||||||
|
An error has occurred on a hidden field (that is, a field that you cannot view). Please contact your system administrator.
WARNING . . . The address number currently being inquired upon is not a 1. supplier, if the inquiry is being made through "Supplier Master Information". or 2. customer, if the inquiry is being made through "Customer Master Information". This is only a Warning, press Enter to continue. | ||||||||||||
|
||||||||||||
Re: SBC sending INVITE directly to endpoint instead of ECB
Hi Yyl,
This happens because you have "route-to-registrar=disabled" on that sip-interface where SBC receives the problematic INVITE. This is old good known problem. Can you enable it?
Regards,
Daureen
