Best Of
Re: Java version installed within the Oracle Database 19c Standard Edition ORACLE_HOME is covered under
Hi,
As far as I understand, no additional license is required to use the Oracle JVM. As shown below, the Oracle JVM is included with Oracle Database, and the license guide contains no specific additional notes.
the Oracle JVM is embedded within Oracle Database and introduces a number of new concepts
Regards,
asahide
Re: INACTIVE_ACCOUNT_TIME - How often does the database check for inactive accounts
I unlocked some inactive accounts yesterday afternoon and they were locked again by this morning.
I unlocked them again at about 09:30 and the unused accounts were locked again by 14:00.
The database checks frequently for inactive accounts and locks them. It doesn't matter if they have never logged in.
My question is how often does the database do the checking?
Re: PeopleSoft on Docker
PeopleSoft does not certify Docker or other similar systems and there is no official communication from Oracle on Peoplesoft certification for Docker. Please refer to : E-DPK: Is It Possible To Deploy Peoplesoft DPK In A Docker Container? ( https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?parent=CHATBOT&sourceId=AppsULonCloud_sigIdPSFTOciDocker&id=2364663.1 ) HOWEVER, Customers should be able to run PeopleSoft on Docker containers. This should work. We have plans on publishing Peoplesoft in Docker containers, but there are no committed dates as of yet.
DaveT
Re: INACTIVE_ACCOUNT_TIME - How often does the database check for inactive accounts
Hello,
according to Doc ID 2879524.1 "When does INACTIVE_ACCOUNT_TIME lock the account?" I tend to think that the unlocked account will remain unlocked until the next login and only at this point the counter of "inactive_account_time" days will run again…
Easy to test, but, unfortunately, as the minimal value for "INACTIVE_ACCOUNT_TIME" is 15, the test will take some time ;-)
Still the doc is a bit unclear, so a test might be necessary ;-) Indeed, we see an example in Doc ID 2373950.1 "INACTIVE_ACCOUNT_TIME Doesn't Work After DB Restart" of an account that gets locked although there was no prior "login"…
Best regards,
Bruno Vroman.
INACTIVE_ACCOUNT_TIME - How often does the database check for inactive accounts
If I unlock a user account but the user does not login immediately, how soon can the account become re-locked by the database?
Re: How to add new line for the existing po via interface
Hi @User_WW4B4
Vision Demo - How To Import Standard Purchase Orders Using the Purchase Document Open Interface PDOI (12.2 and 12.1.3 Enhanced PDOI) (Doc ID 2014101.1)
if still has issue — please validate the table po_interface_errors
How To Diagnose Problems With Importing Standard Purchase Orders (Doc ID 781351.1)
Thanks
Nirmal Kumar N
Re: How to add new line for the existing po via interface
Hi -
Fine, in your header interface table just insert as 1001 (any unique number) in batch_id column along with other data and then try submitting the program from the request window
While submitting check if the Batch LOV shows this 1001 and then submit the program
Check the results and we will decide accordingly
regards.
Ananth
Re: how to update the existing po lines in oracle (interface)
Hi,
You can also use the following
Business Service Object Web Service to Create and Update Purchase Orders (Doc ID 1573389.1) | |
|---|---|
Technical Brief : Using WebADI Spreadsheets In Buyer Work Center Orders (Doc ID 2039629.1) |
Regards,
Sirisha
Re: how to update the existing po lines in oracle (interface)
Hi,
It is not possible to update the PO in interface. You need to use api to update
PO_CHANGE_API1_S.update_po
Sample code to update
set serveroutput ON;
DECLARE
l_result NUMBER;
l_api_errors PO_API_ERRORS_REC_TYPE;
BEGIN
-- This needs to be changed according to your environment setup.
FND_GLOBAL.apps_initialize ( user_id => XXXX,
resp_id => XXXXX,
resp_appl_id => XXX );
mo_global.init('PO'); -- need for R12
l_result := PO_CHANGE_API1_S.update_po (
X_PO_NUMBER => &po_num,
X_RELEASE_NUMBER => Null,
X_REVISION_NUMBER => &rev_num,
X_LINE_NUMBER => &line_num,
X_SHIPMENT_NUMBER => &shipment_num,
NEW_QUANTITY => 25,
NEW_PRICE => Null,
NEW_PROMISED_DATE => Null,
NEW_NEED_BY_DATE => Null,
LAUNCH_APPROVALS_FLAG => 'N',
UPDATE_SOURCE => 'API',
VERSION => '1.0',
X_OVERRIDE_DATE => Null,
X_API_ERRORS => l_api_errors,
p_BUYER_NAME => Null,
p_secondary_quantity => Null,
p_preferred_grade => Null,
p_org_id => &org_id
);
dbms_output.put_line ('l_result' || l_result);
IF (l_result <> 1) THEN
-- Display the errors
FOR i IN 1..l_api_errors.message_text.COUNT LOOP
dbms_output.put_line ( l_api_errors.message_text(i) );
END LOOP;
END IF;
END;
commit;
Hope this helps