Change the role sequence number for a role

Hi All,

 

Below are the steps to change an existing role to have a higher role hierarchy.

1. In P0092 Work With User/Role Profile, from the Form Exit Menu, select Role Sequence.
2. In the Work with Role Sequence screen, use the mouse to drag and drop a role to a desired position i.e. up or down in the role sequence tree.  The lower the role appears in the tree, the higher the sequence number.
3. It is easier to drag a role of a lesser sequence number down to replace one with a higher sequence number.
4. Click on the "Set Sequence".  This will refresh the roles with a new role sequence number based on their position in the Role Sequence tree.
5. To undo step 3, select Close Without Set Sequence.

Regards,

JDE Help

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks

______________________________________________________________________

Cannot save a Media Object from JAS Server to Deployment Server

Hi,

 

If user is assigned to start the web services as a local account will get error.

Changed this to a valid Domain user with administrator privileges.  
Mapped a Network Drive to the Deployment Server Share folder E812 (where mediaobj directory resides) on the JAS server.
Also make sure that 'UseMOWinNTShare' is set to TRUE under [OWWEB] section of jas.ini.

 

Regards,

JDE Help

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks

______________________________________________________________________

Change Password through webclient

The problem was attributed to incorrect PO Values for the P98OWSEC.

Verify the PO values for P98OWSEC logging from a Webclient. Login to Webclient, Fast path IV, select P98OWSEC and select the default ZJDE0001 version and see it has correct PO Values specifically for the password policy. Change if necessary. If the issue still exists try the below workaround.

Customer changed the PO Values for P98OWSEC to default values and this resolved the issue.

PO Values changed to:
Default tab - 1 0 0 01 0
Password tab - blank 4 0 0 0 0

Regards,

JDEHelp

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks

______________________________________________________________________

How To Delete UBEs and UBE Versions from EnterpriseOne

Hi

 

It is important to determine all the environments a UBE exist in. One way to make this determination is to use UTB and view the table F9861 - "Object Librarian-Status Detail". In the F9861, enter the report ID into column SIOBNM and the environments (column SIPATHCD) where the UBE template exists will display. If a record displays with a workstation ID in the column SIMKEY, this indicates that the object is currently checked out to that workstation.

To delete the UBE and the associated UBEVERS from the environments, use OMW. For example, this is an example where a UBE and the associated UBEVERs exist in DV812, PY812 and PD812 and explain the steps to do the delete in OMW and how OMW will use the appropriate Transfer Activity Rules (TARs).
 
1. Sign onto the development environment and create a project that has a status of 21. Add to the UBEs that needs to be deleted to your project. Note, the UBEVERs will not need to be added to the project because when the UBE is deleted the system will automatically delete the associated UBEVERs.
 
2. Highlight each UBE and click the Delete button. In the [Delete of...] form check: "Delete Object from Server" and "Mark Object To Be Deleted From Transfer Location". Note, the delete object from server will delete from the location defined in the TAR for a project status of 21 and object type of UBE and action 02-delete. We ship the TAR to delete from DV812 (this means the UBE will be deleted from DV812 Central Objects).

3. With each UBE deleted,  promote the project to status 26 and this promotion will delete the UBE from PY812 Central Objects and will also delete all the associated UBEVERs in the F983051 of PY812. This is based on the TAR we ship for a transfer from 21 to 26.

4. Promote the project status to 28, then to 38 and the promotion will delete the UBE from PD812 Central Objects and will also delete all the associated UBEVERs in the F983051 of PD812.
 
5. Please note the above steps only affected Central Objects for each environment, the F983051 for each environment and the F9860 and F9861. The local spec on fat clients, terminal servers and enterprise servers will not be updated. The next time a full package is built and deployed to the fat clients, terminal servers and enterprise servers the spec for the UBEs and UBEVERs will be removed. Don't worry about the spec remaining because the UBE cannot be used without the F983051.

 

Regards,

JDEHelp

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks

______________________________________________________________________

Web-only Batch Versions

Hi

 

Web-Only versions is a workaround solution until full batch versions are available on the Web client and there is no longer a distinction between windows versions and web-only versions.   This functionality is available beginning with the 8.98_200 Series Tools Release for application release 8.12.  This application release 8.12 does require an ESU for SAR 8663474 TT-812 Enable Full BV on Web.

This functionality is not available for earlier application releases.

 

Regards,

JDEHelp

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks

______________________________________________________________________

Recompress Full Client Parent Package in E1 8.12 release

Hi

 

In E1 8.12 release, for integrity reasons, package revision is not allowed for deployed packages.

The following steps can be performed to recompress a full client parent package:

1. Go to GH9083 then  Package build History Application (P9622).
2. Find the full client parent package and expand the package folder in the following manner:

         Packagename
             -> Time and Date
                      -> CLIENT
                             ->Compression Options
3. Highlight the directory you want to compress and select Row Exit "Reset Status".
4. In  Reset Build Status screen (W9622C), set both the "Spec Build Status" and "Pack Build Status" fields to
     01 - Not Built.
5. Press the RESET button to save the changes.
6. Repeat steps 3 to 5 to select the directories that need to be recompressed.
     Note: To recompress all directories under Compression Options, you can highlight on "Compression
     Options" and click the Row Exit "Reset Status" then in Reset Build Status screen set Spec Build status and
     Pack build status to 01-Not Built.
7. Highlight "CLIENT" and click Row Exit "Resubmit Build". The system will recompress the directories files
    selected.
8. When prompted with the following pop-up message, Press Cancel.
                 Generate NER
                 If you would like to generate NER, press OK. Otherwise, press Cancel.

Regards,

JDEHelp

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks

______________________________________________________________________

Solution for ER Debugger Issue(Debugger not working from web client)

Hi All

 

Please follow the steps as mentioned below to resolve ER debugger problem.

Minimum requirements:-

Install jdk-1_5_0_18-windows-i586-p.exe (Setup launcher)

Restart the fat client and follow these steps.

a) Steps to be followed while using ER Debugger:-

1)      Always take remote session by MSTSC /CONSOLE

2)      Before login into JDE fat client, go to Task Manager->Processes and check for java.exe and rdpclip .exe

3)      If processes java.exe and rdpclip.exe exists end these processes.

4)      Login to JDE fat client and open Debugger.exe from fastpath.

5)      If multiple objects are added then rebuild DIA for that object before debugging.

 

b) If Debugger doesn't work follow these steps:-

1)      Logout of JDE fat client.

2)      Go To Task Manager->Processes

3)      Delete processes java.exe and rdpclip.exe.

4)      Login to JDE fat client and can use debugger.

c) Still if debugger doesn't work: - Contact your CNC team.

Regards,

JDEHelp