• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Moving Data from Common Library to Data Library

We are on J.D. Edwards version 8.1 cum 2 and have been asked to move the
following files from our Common library to our Data library:

F0016 Generic Text File
F00163 Generic Text Key Index File
F00164 Generic Text Key Index File (120 Character Key)

Has anyone done this on 8.1?
Does it cause any problems with upgrades or conversions?
Were these files originally located in the Data library on a versions
before 8.1?

-
James Johnson
Berry Plastics Corporation
PO Box 959
Evansville, IN. 47706
812-429-9556
Fax 812-433-5383
james_johnson@berryplastics.com
 
James;
As long as these files exist together as a group in the same library
you should have no
problems. Any upgrade should be able to find them as long as the
library list contains
the library they are in. I'm assuming that since you have been asked
to move them from
the COMMON library, that you will not be sharing the text files across
environments?


Bert R. Sternal
IT Business Analyst
Wabash National
(765) 772-2779 Voice
(765) 772-2299 Fax



James_Johnson
<James_Johnson@berrypla To: jdeworldml@jdelist.com
stics.com> cc:
Sent by: Subject: Moving Data from Common Library to
owner-jdeworldml@jdelis Data Library
t.com


05/30/2001 03:52 PM
Please respond to
jdeworld






We are on J.D. Edwards version 8.1 cum 2 and have been asked to move the
following files from our Common library to our Data library:

F0016 Generic Text File
F00163 Generic Text Key Index File
F00164 Generic Text Key Index File (120 Character Key)

Has anyone done this on 8.1?
Does it cause any problems with upgrades or conversions?
Were these files originally located in the Data library on a versions
before 8.1?

-
James Johnson
Berry Plastics Corporation
PO Box 959
Evansville, IN. 47706
812-429-9556
Fax 812-433-5383
james_johnson@berryplastics.com




--------------------------
 

SLewis

Member
Just make sure that you copy those files to all of your data libraries and
then remove them from the common library. We have no common library, all of
the common files are in the data libraries. This gives us better environment
control. The users can test by adding or changing data in the common files
without affecting production.


Stephen R. Lewis
Application Systems Administrator
CCL Custom Manufacturing
Rexdale Plant
11 Bethridge Road
Etobicoke, ON Canada
M9W 1M6
Phone: (416) 740-7400 ext155
Fax: (416) 743-5439
email: slewis@rex.cclcustom.com




Steve Lewis
CCL Custom Manufacturing
11 Bethridge Rd.
Toronto, ON Canada
M9W 1M6

A73 cum 8, 720 V4R4
 

Emad_S_Banoub33

Active Member
James,
These Generic text files are by design from JDE should reside in common
library. If you are planning for coexiistence with OneWorld, these files
must be moved from the common library into the data library. If you are not
planning for coexistence with OneWorld then the questions I have are:
Who asked you to move them? and Why?

Emad Banoub
626.568.6529
A7.3 Cum.12/X3 - Xe Sp 13.0





James_Johnson <James_Johnson@berryplastics.com>@jdelist.com on 05/30/2001
01:52:23 PM
 

Colin_Hugill

Reputable Poster
James,

Move the files and any related logicals from Common to Data ASAP. Note that
I said MOVE not copy. There will be no repercussions related to JDE now or
in the future

Regardless of what library these files were in when delivered from JDE, they
really should be moved to your data library. These files store memo text
data related to transactions, account masters etc etc. The usual way of
creating data in this file is via the F14 Memo Text function that is
available in many, many programs within JDE.

The major potential problem you face if you don't move these files is when
you have more than one environment (eg Production, CRP, Test, Development)
but all environments use your common library. Any entry of memo text in any
environment will be written to the F0016x files in common.

I have had the tedious chore of having to sort the above scenario (removing
memo text not related to production) - it is a nightmare best solved by a
pragmatic, ruthless, and energetic deletion of any record not obviously
relating to production data. Any excess deletions can be rectified by
copying back from a backup copy only if the users can present a sound
business case.

Regards...... Colin HUGILL




Colin Hugill
Consultant
 
Top