|1333 day(s) ago||#242|
Date: 2016-12-14 02:09:35
Freqently Asked Questions on JDE E1 Work Center MessagesFrequently asked questions on JD Edwards’s (Release 8 and above)– Work Center Messages
Q1 - How are Work Center Messages Stored?
If the message is an ACTIVE message, the message will be in the F01131 Message Control Table, F01133 Message Detail Table and F01131T Message Attachment Tag File and the records will all have the same SERK or Key Value Serial Number.
If the message is a MULTI-LEVEL message, the way they are displayed in the Work Center and ultimately how they get deleted with the purge program is done with a parent/child type of relationship. These types of multi-level messages are stored in the F01131M Multi Level Message Table. The first F01131M record that is written will have the same SERK number as the parent F01131 record. That same record has an additional SERK number in the same F01131M record. This second SERK number is the "CHILD" and points to the next F01131M PARENT. It is this recursive relationship that makes it possible to have one F01131 record and many F01131M records. We use this same recursive relationship for deciding which F01131M records get deleted when running the purge process.
A UBE has an error and it creates a F01131 record with the number 100 as its SERK number.
Record 1 = SERK 100
Multiple F01131M records can be produced for detailing what that error was:
Record 1 = Parent SERK 100 Child SERK 200
Record 2 = Parent SERK 200 Child SERK 300
Record 3 = Parent SERK 300 Child SERK 400
Record 4 = Parent SERK 400 Child SERK 500
Record 5 = Parent SERK 500 Child SERK 600
Each additional parent SERK (records 2, 3, 4, and 5) that is created has a record in the F00165 Media object table that displays text just like a F01131 record, but these records do not exist in the F01131 table because they are not needed. So although there are five parent SERK numbers in the F01131M there is only one true parent in the F01131 used for the starting point. The actual text of the message is encoded and stored in the F00165 media object table using the GT01131 data structure with GDTXKY as the key. For example, if there is a record in the F01131 with ZZSERK = 32526, the actual text of the message is in the F00165 where GDOBNM=GT01131 and GDTXKY = 32526.
Q2 - Why do some Messages have Unrelated Detail Attached to Them?
This may be caused by ORPHANED records appearing in the Work Center tables.
Q3 - How do I Purge Work Center Messages?
The batch process R01131P - Purge Completed Tasks can be used to purge messages in the Work Center. To ensure that orphan records are not created in the F01131M by the R01131P, apply the appropriate ESU prior to running.
Q4 - Why do Work Center Messages Need to be Purged?
Many processes within EnterpriseOne software send messages to the Work Center including workflow processes and UBE completion messages. The message tables get LARGE quickly. Messages in the work center need to be purged regularly. This will improve PERFORMANCE.
Q5 - How can EnterpriseOne software be Set Up to Send Messages to External Mail Rather than to the Work Center?
By adding the appropriate JDE.INI setting in the [JDEMAIL] section of the client and server jde.ini and also defining the appropriate e-mail preference and e-mail address for address book records within EnterpriseOne.
Work center messages can be sent to an external mail system such as Outlook, Lotus Notes, or GroupWise.
Q6 - Is it Possible to Send Some Work Center Messages to External Mail and Define Other Messages to be Sent to the Work Center?
Within EnterpriseOne software, an e-mail preference can be established by user address book record of either external mail or work center. However, this preference applies to ALL messages sent to that user. There is NOT a way to specify a different preference for certain types of messages for one user.
Q7 - Are Multi-Level Error Messages Sent to External Mail?
Multi-level drill down messages created by certain Batch Applications within EnterpriseOne are ALWAYS sent to the Work Center. Currently the functionality does not exist to send these type of drill down messages externally. If the user`s e-mail preference is external, they will receive a message that the UBE process completed with errors, however the specifics of the error messages will need to be viewed through the work center. SAR 5352970 exists in the system requesting an enhancement to send full detailed error messages to external mail.
Q8 - Can the UBE Completion Messages be Disabled?
There is NOT a way at the system level to disable the completion messages sent whenever a UBE report completes. There is an available API that can be used in a business function that is called within an individual report to disable the UBE messages. The API is "BOOL ubeReport_DisableSendMessage(LPBHVRCOM pBhvrCom)". A business function calling this API can be hooked up on any event in a report and this would disable the job completion messages for this specific UBE report.
Q9 - Can I Set Up the Work Center to Allow a User to View Messages of Another User?
There are a COUPLE different methods available to allow a user to view another user`s Work Center messages. Security can be defined within the Queue Security application (P01135) to allow a user access to another user`s messages within specific queues. An administrator can use the Employee Queue Manager Application (P012501) to view all queues and all messages for a user.
Q10 - When Sending a Shortcut with an External Message, How do I Specify the Type of Shortcut to Send (Windows Client or HTML Client)?
Beginning with service pack seventeen, when sending a shortcut with an external message, this shortcut can be either a shortcut for a Windows application or a shortcut for an HTML application. To specify which type of shortcut is sent with external messages, you must modify the JDE.INI file. If a EnterpriseOne user is sending a shortcut from a fat client, you must modify the jde.ini on the client workstation. If an EnterpriseOne user is sending a shortcut from a thin client or through a function that is executed on the server, you must modify the jde.ini file on the enterprise server. To specify the application shortcut type, modify the following section of the jde.ini file:
ClientType=Windows (Default) Message will contain a Windows application shortcut
ClientType=ActiveX Message will contain a Launch application attachment that opens a Web application in a new session of the Web client in Microsoft Internet Explorer.
ClientType=URL Message will contain a URL for a Web application shortcut.
When the preference is an ActiveX or URL application shortcut, you need to also modify the [JAS PREFERENCE] section of the jde.ini with the JasServer, Port, and Servlet information.
|Disclaimer:||Most of the posts in this blog cater solutions/suggestions/workaround to issues for specific tools release or JDE E1 version and are just information only. Please be carefule while applying it in your environment. JDEthread will not be responsible for any data loss or spec corruption (if any).|
Copyright © 2010 - 2020 JDEthread.in