Best Of
Re: Web database timeout
Hello,
This is not an error. Is an informational message because debug logging is on. The value is taken from ResultSet Timeout (resultSetTimeout) setting.
Best regards,
Cezar
Re: Web database timeout
Hello,
Transaction Timeout under JDBj Runtime Properties represents the time (in milliseconds) before a transaction will timeout. A transaction will timeout if it has not had any operations for the specified period of time. If this timeout is set to a -1, then the transaction timeout feature is disabled.
In case the timeout is occurring you might see in the log a message sequence like this:
com.jdedwards.database.base.JDBException: [TRANSACTION_TIMED_OUT] Transaction timed out due to inactivity. com.jdedwards.database.base.JDBException: [TRANSACTION_TIMED_OUT] Transaction timed out due to inactivity.
JDBj transaction commit failed. See logs for more details.
Best regards,
Cezar
Re: Issue in redirection between Public and non-public web domains
Matheswaran - Creating two separate websites may not work well since both sit under the same domain but use different web profiles and sites. That setup gives you no real control and introduces unnecessary security complexity.
It’s better to stay with a single web domain and handle MFA within the normal login flow. In other words, once the user’s credentials are verified (%PSAuthResult = True), you can trigger the MFA process directly from Signon PeopleCode by redirecting to your custom MFA page using SetAuthenticationResult
by passing &resultdoc. Make sure you look at signonresultdoctext.html
SetAuthenticationResult( True, &user, &resultDoc, False, 0);
The caveat with this approach is that it isn’t true MFA. Once credentials are accepted and the user is routed to the MFA page, a simple browser refresh or using the deep link in a new tab could bypass the MFA check. It can also interfere with tools like ExcelToCI or 3-tier App Designer.From a security standpoint, it’s better to place MFA at the proxy layer and since you already have F5, that’s the ideal place to implement it. F5 can integrate directly with Microsoft Entra ID (Azure AD) and use the Microsoft Authenticator app, which is where most organizations are heading.
What you’re attempting is the older, application-level MFA pattern, and while it works technically with flaw, it’s not considered a best practice under current enterprise security standards.
-Velu
Re: Implement MFA (Multi factor authentication) using Microsoft ENTRA proxy
Hi – I’ve set this up for a few clients and it’s been working well. In our case, PIA login runs through Entra ID with header-based authentication, while ExcelToCI still uses LDAP.
The document I shared earlier comes directly from Microsoft. I’m not sure what you meant by “file size limits,” but essentially the setup just needs a proxy in front of the web server to insert the username header. The Signon PeopleCode then reads that header and authenticates the user.
The first document is fairly high-level, so I’m also sharing another, more detailed one from Microsoft. Hence asked op to send a DM to guide him further.
-Velu
New Document Explains How Cobol Should Be Compiled/Deployed After Applying Tax Updates
This new PeopleTools document explains the best practices for how Cobol src files should be compiled/deployed after applying Tax Updates.
Doc ID 3101884.1. https://bit.ly/3W83vXw
Re: CVE-2025-61884
For Release 12.2, customers who run the ojspCompile.pl command to compile all JSPs may encounter an error. To fix that issue, apply Patch 38502365:R12.TXK.C in hotpatch mode.
Re: table and field name for Life Cycle in fixed asset module
Hi,
The Life Cycle segment refers to a specific segment of the asset cost account code combination, often used as part of your chart of accounts to track asset life cycle stages (such as acquisition, depreciation, disposal, etc.).
Storage Details:
- The cost account code combination for each asset is stored in the FA_ASSET_DISTRIBUTIONS table, in the column CODE_COMBINATION_ID.
- The details of each account segment (including the Life Cycle segment, assuming such a segment exists in your chart of accounts setup) are stored in GL_CODE_COMBINATIONS. Each segment is captured in columns like SEGMENT1, SEGMENT2, ..., SEGMENTn, depending on your accounting flexfield structure.
How to Find the Life Cycle Segment:
- From FA_ASSET_DISTRIBUTIONS.CODE_COMBINATION_ID, join to GL_CODE_COMBINATIONS.CODE_COMBINATION_ID.
- In GL_CODE_COMBINATIONS, extract the relevant SEGMENT column (e.g., SEGMENT3 or whichever corresponds to your Life Cycle segment in your accounting flexfield configuration).
Example (in pseudo-SQL):
SELECT fad.ASSET_ID, gcc.SEGMENT3 AS LIFE_CYCLE_SEGMENT -- Replace with your actual segment numberFROM FA_ASSET_DISTRIBUTIONS fad JOIN GL_CODE_COMBINATIONS gcc ON fad.CODE_COMBINATION_ID = gcc.CODE_COMBINATION_IDWHERE fad.ASSET_ID = :your_asset_id;
(Replace SEGMENT3 with the segment that represents Life Cycle in your instance.)
Summary:
- Life Cycle segment value is found in the appropriate SEGMENT column in GL_CODE_COMBINATIONS, as referenced by the CODE_COMBINATION_ID stored in FA_ASSET_DISTRIBUTIONS (or other accounting-related FA tables, depending on context).
Re: Any setup to prevent the P4205 to create the partial shipment lines in Sales Order
Hi Ankur Patel,
Noted with many thanks.
We decide to set the backorder split line with next status 999 if not able to prevent the creation of the split line.
Thanks.
Regards,
Maggie