Best Of
Re: Processing options#4.25 in P4312 in JDE 9.2.9 - Significance and available documentation
Dear Mahesh
Thank you for your inputs , Is the processing option applicable to advanced requisitions or RSS requisitions or both?
Could you confirm?
Thanks in advance
Re: APP-PAY-51271: The assignment is not eligible for the element
Hi
It can only mean the creation of the link was not properly done. I don't see the reason for this message if it is done correctly. Perhaps double check yourself on that.
Regards
Motlatsi
Re: APP-PAY-51271: The assignment is not eligible for the element
Please refer the below documents for help.
Error "APP-PAY-51271: The assignment is not eligible for the element" When Creating Element Entry (Doc ID 2315724.1)
"APP-PAY-51271: The assignment is not eligible for the element" When Creating Element Entries for Any Elements (Doc ID 2247858.1)
Regards,
Vamshi
Re: APP-PAY-51271: The assignment is not eligible for the element
Hello @Yasir_Mushtaq
The MOS notes listed in Vamshi's update and also:
Error When Updating an Element Entry Value - APP-PAY-51271: The assignment is not eligible for the element. (Doc ID 1366024.1)
A pyupip on the form may also assist with identifying the root cause of the error.
Jan
Processing options#4.25 in P4312 in JDE 9.2.9 - Significance and available documentation
Dear All
In JDE 9.2.9.3 , I notice a new processing options in the process tab of P4312 as below
25. Reopen Requisition on Cancel or Close Purchase Order Line
Blank = Reopen the Requisition
1 = Do not reopen the Requisition
Kindly share the relevant Oracle documentation for the above feature , which would help to understand its significance and usage
Thanks in advance
Cleaning old Suggestions and request from F4611,F4600
I want to ask if there is any problem if i reduce the number of the record on F4600 and F4611 deleting all request and suggestions closed or cancelled and older than 2 Year.
Are there some procedure that still use these cloed requests and suggestions and can cause a problem ?
best regards
Andrea
F4311: Blank PDPN (Period Number) and PDFY (Fiscal Year)
Hi,
We're on JDE E1 9.2 with Tools Release: 9.2.8.4
I’ve noticed that the PDPN (Period Number) and PDFY (Fiscal Year) fields in the F4311 table are usually blank, although some records do contain values.
Could you please clarify:
*What drives the population of these fields? Are there specific criteria?
*Why are they blank for most records?
Thanks for your help!
Re: ODA 19.27 & APPLIANCE 23.8.0.25.04 GI CLONE DOWNLOAD FOR ODACLI/DCS STACK
Hello
Thanks for the information and the quick response!
Best regards,
Thomas Trakle
Re: Create Employee as a customer in AR EBS R12?
Thanks Bharat, yes i got that note as well. I was just wondering is this error due to patch only or some other setup which I am missing.
Regards
Tarika Jain
Re: node eviction and MAC ADDRESS FLAPPING IN SWITCH LOGS
Hi,
While your public (bond0.722) and private (bond0.797) interfaces share the same MAC address, this is expected behavior for VLAN sub-interfaces inheriting the address from their parent bonded interface (bond0) and is not, in itself, the misconfiguration. The flapping strongly indicates a Layer 2 misconfiguration, likely a mismatch between the server's NIC bonding/teaming policy (e.g., LACP mode) and the corresponding port aggregation configuration on the upstream physical switches. Given that your environment is a VxBlock system, this investigation must also include the virtualization layer, specifically the vSwitch teaming policies and uplink configurations. I recommend engaging your network and virtualization administrators to audit and align the end-to-end network path, ensuring the server's bonding mode is perfectly synchronized with the switch's port-channel settings. Resolving this configuration alignment is critical to eliminating the MAC flapping and ensuring the stability of your RAC cluster.
Cheers
Arsalan