Change in No. of Flexfields
From: Joe Swietlik [SMTP:Joe_Swietlik@wmg.com]
Sent: Thursday, 4 March 1999 6:01
Subject: Accounting FF Change...Any way to do it?
Hi All -
My client has a 7-segment AFF, and wants to switch to a 6-segment
structure,
without reinstalling. There is no 1-1 correspondence between the
two
structures, so a consolidation with a second set of books is not an
option.
I would like to alter the structure of the GL_CODE_COMMBINATIONS
table and
change the associate value sets. The environment is a 10.7 GUI SC
setup.
Apart from violating Oracle's Support agreement, what technical
gotcha's
might prevent me from doing this?
Regards,
Joe Swietlik.
Date: Sat, 20 Mar 1999 16:19:38 -0800 (PST) Change in size of Key Flexfields
--- John Lantz John7@worldnet.att.net wrote:
Date: Tue, 6 Apr 1999 10:42:53 -0700 (PDT) Value Sets - Deleting reference to a
From: mike ruff [SMTP:mikeruff@hotmail.com]
Date: Thu, 8 Apr 1999 09:45:40 +0530 Reporting on FF
From: Mohammed Haneef (haneef) haneef@sequent.com
Date: Mon, 29 Mar 1999 13:13:42 -0500
Date: Tue, 30 Mar 1999 04:07:03 -0800 (PST)
Date: Tue, 30 Mar 1999 11:11:45 -0500
Date: Thu, 1 Apr 1999 02:06:42 -0800 (PST) Security Rules
"Larry L. Leser" llesser@iquest.net wrote:
From: Roger Drolet [mailto:rdrolet@netscape.net]
Date: Thu, 8 Apr 1999 08:43:04 -0400
Date: Thu, 8 Apr 1999 09:14:20 -0400
Date: Thu, 8 Apr 1999 13:39:35 -0300
Date: Thu, 8 Apr 1999 17:31:34 -0400 Hang on compiling KFF
From: "Khandrika, Babu" Bkhandrika@tnpe.com
Date: Thu, 15 Apr 1999 11:02:59 PDT Duplicate Segments
From: Bill Keenan [mailto:bkeenan@goodegg.com]
Date: Thu, 15 Apr 1999 16:36:55 -0700
Date: Thu, 15 Apr 1999 21:05:24 -0400 Change in Flexfield Structure
From: Mehra, Varun (CAP, GECSI) [SMTP:Varun.Mehra@geind.GE.com]
Date: Mon, 17 May 1999 16:07:40 +0530
From: Debbie Griffin[SMTP:dgriffin@fnal.gov]
Date: Tue, 18 May 1999 22:12:50 +0530
Date: Tue, 18 May 1999 16:23:08 -0500
From: gangadhar andru
Subject: RE: Accounting FF Change...Any way to do it?
Hi Joe,
I may be answering rather late. We have implemented recently a
similar change in AFF with minimal impact on the systems.
If you need any info, please let me know at email:gangaa@hotmail.com
Gangadhar
Folks,
How difficult is it to change the size of one of the
segments in the Item
key flexfield?
Our current Item flexfield is made up of two (2)
segments: the first one is
8 characters and the second one is 4 characters in
length. There is,
however, a need to increase the size of the first
segment to 30 characters.
I have heard that this is a major task. Has anybody
ever done this? Can
anybody provide any advice?
We have been live with Oracle INV, OE, OSM, GL, AP,
AR, PO, & FA for almost
2 years now.
We are on Rel. 10.7 / Prod 16.1 SC (GUI).
Any help would be much appreciated.
Thanks,
John
From: siddhartha nandi sid_nandi@yahoo.com
Subject: Re: INV: Changing the Item Segment Size
John,
since you are increasing the length of the first segment (and not
decreasing), system will allow you to do so. The implecations of this
will be to check that any report or display might wrap or gets cut-off.
Thanks,
Sid.
From: April Stooksberry astooksb@csac.com
Subject: Re: Increasing the size of the Accounting KFF segment
I have helped clients do this and similar changes to the
Accounting flexfield including change the size of the
segment as well as add or delete segments.
The approach will depend somewhat on how you want to
handle your historical values - will they still be valid
or do you want to perform a "conversion" on them?
If the old values will still be valid and you want to, say,
expand the value set size for future entries, the change
should be relatively easy. If you want to "convert"
historical values to new values, then the change will be
more challenging :) !
I do have some documentation that might help - you can
call me direct at number below or email direct if you're
interested.
Thanks,
April
=============================================================
April Stooksberry Computer Systems Authority
Applications Practice Director 6380 LBJ Freeway Suite 181
(972) 960.0180 X264 Dallas, TX 75240
Sent: Wednesday, April 07, 1999 8:35 PM
Subject: Deleting ref. of Value Set
Hi,
One of our consultants attached a value set to the Items Flexfield and
compiled it. Later we realized that a value set need not be attached
to the System Items Flexfield.
We unfreezed the Flexfield, deleted the Value Set and compiled it
again.
so, whenever we try to enter transactions and we go to the Items field
it gives us this error: "Error in calling routine FDFRKS for
application 401 and code not found"
I checked up in the FND tables application 401 consists of all the 620
Inventory Flexfields.
Could any one tell me how to get over this problem?
TIA
Mike Ruff
Oracle Project Manager
Nexeon Inc.
From: B Bharat Bhaaradwaj bharatbh@wipsys.soft.net
Subject: RE: Flexfields Error
Hi
System item Flexfield supports only one structure. As far as my learning
goes one value set needs to be necessarily be attached to a Flexfield, I
was once told by support in a similar context that if any value set is
changed then the already contained data is wiped out. The compilation of
the flexfield would end in an error. A view on this may not be created.
Please check the compilation log, and the view that it had to create. If
this is missing then you have tracked the problem. I am oblivious of the
methods to correct this, only oracle support or any one else who have
done this may be able to help you.
I hope i have been clear in putting forth my suggestion.
Regards
Bharat
B.Bharat Bhaaradwaj
Wipro Infotech - ESD
40/A Bassappa Complex
Lavelle Road
Bangalore 560001
Ph.2215010 Ext.220/221
Sent: Monday, March 29, 1999 12:01 PM
Subject: Reporting on Flexfields
Can somebody point me on how to report on flexfield data using reports
2.5
Thanks
--Haneef
From: "Scott L. Frost" sfrost@noblestar.com
Subject: Re: Reporting on Flexfields
The easiest place to start is the Technical Reference Manual for the module
to identify the tables particular Flexfield values are located. Be careful
if you are reporting on HR/Payroll flexfields as most of the values are date
stamped and you need to identify the specific date ranges you are trying to
get values for.
Once the columns are identified using the TRM, you can create a report to
pull these values out using Reports 2.5.
Hope this helps!
Scott
From: Misa Gupta assimgupta@yahoo.com
Subject: Re: Reporting on Flexfields
The best way to report on Flex fields data is to use the user exits
provided by Oracle. Way suggested by Scott is also fine except that in
this case you will be hard coding the segments (used by your
implementation of this particular flexfield in the reports).
I personally always use the user exits and they work beautifully.
There is detailed literature on how to use these user exits, their
format and the whole cycle.
I have my own notes but unfortunately I do not have a soft copy
otherwise I would have sent you.
Assim Gupta
From: "Vallapareddy, Krishna" kvallapareddy@noblestar.com
Subject: RE: Reporting on Flexfields
Hi Craig,
You can find all the information on using user exits in reports 2.5 in
the Application Object Library Reference Manual
in the chapter on Reports. Also you can refer the Flexfields reference
manual in the chapter on using flexfields in
Reporting.You can also open any of the standard reports in Oracle
applications and see how they have used the
FND FLEXSQL USER EXIT.
From: Misa Gupta assimgupta@yahoo.com
Subject: Re: Reporting on Flexfields
Hi Craig
The user exits I am refering to are
FND FLEXSQL & FND FLEXIDVAL
Below I am attaching a small portion of Oracle User Guide which lists
what these user exits are good for:
Display any individual segment value, prompt, or description.
Display segment values, prompts, or descriptions from multiple
flexfield structures (or contexts) in the same report.
Display segment values, prompts, or descriptions from different
flexfields in the same report.
Display two or more flexfield segment values, prompts, or
descriptions, concatenated with delimiters, in the correct order.
This includes description information for dependent,
independent, and table validated segments.
Restrict output based upon a flexfield range (low and high values).
Prevent reporting on flexfield segments and values that users do not
have access to (flexfield value security).
Specify order by, group by, and where constraints using one or more,
or all segment columns.
As you can see from the above, these user exits are pretty flexible and
let you manipulate the data whatever way you want.
Oracle FlexField User Guide gives a detailed description of how to use
these user exits (besides giving lot of info on how to use flexfield
views for reporting).
If any body needs more detail on how to work with these, can get in
touch with a colleague of mine Meenakshi Agarwal at following address:
meenakshi_a@yahoo.com.
She has done a lot of work on these.
Assim Gupta
I need to try to find out if it is possible to:
In 10.7 character, can you attach GL Flexfield security rules to
Standard GL Reports (i.e. GL Detail report) that ask for Account
Flexfield ranges?
Has anyone done this? Can offer suggestion on this, or another
solution that provides this functionality?
Thanks in advance, for any assistance.
Sent: Wednesday, April 07, 1999 7:41 AM
Subject: Re: [GL: Flexfield Security and reporting]
Larry,
You can define Flexfield Value Security rules to restrict the set of values a
user can use during data entry. Flexfield Value Security lets you determine
who can use flexfield segment values and report parameter values. Based on
your responsibility and access that you define, Flexfield Value Security
limits what values you can enter in flexfield pop-up windows and report
parameters.
This functionality is very effective in providing security when you have
number of operating units using the same Set of Books. You can define
security rules (e.g. on the Company Segment) which will enable users to only
enter those Company values associated with their operating unit).
Roger Drolet
Managing Associate
Conley, Canitano
From: "Joe Maliszewski" jmaliszewski@csi.com
Subject: RE: [GL: Flexfield Security and reporting]
No, it does not work on Standard Reports.
Joe Maliszewski
Consultant
jmaliszewski@csi.com
From: "Lakdawala, M" M_Lakdawala@csx.com
Subject: RE: [GL: Flexfield Security and reporting]
No, it does not apply to it. However you can develop a routine for custom
reports based on the organization hierarchy. If you need more details call
me.
Thanks & Regards
MUZAFFER LAKDAWALA
E-mail M_lakdawala@csx.com mailto:M_lakdawala@csx.com
Web http://members.xoom.com/muzaffar/
Phone 904.366.4720
Date April 8, 1999 9:16 AM
From: Ken Heckbert kpheckbert@ihis.org
Subject: Re: [GL: Flexfield Security and reporting]-Reply
About 3 years ago, there was a paper presented at an OAUG
conference by Melanie Bock, called "Report Security". This excellent
paper covered a multitude of topics, including how to secure Standard
Reports, using security rules. Unfortunately, the OAUG website only has
on-line, papers from conferences in the last two years, so I'm not sure
how you would get a hold of it. If you are a member of OAUG, you may
be able to contact them for a copy of the paper. Anyway, however you
get a hold of it, it should answer your questions, and is well worth the
effort. Personally, I think Oracle should just purchase the rights and
include this paper, and Melanie's paper on designing your chart of
accounts, in the GL manuals.
Ken
From: Jeff Rausch jrausch@meetingexpectations.com
Subject: Re: [GL: Flexfield Security and reporting]-Reply
Ken -
You are correct. Melanie Bock's paper entitled, "Report Security" was
presented at the Fall 1996 Conference in San Diego, CA. While no longer
available using the OAUG Paper Database, you can purchase a copy of the
proceedings by visiting our web site at http://www.oaug.org/confer.html,
and following the links to the Primary Key Bookstore. The price is
US$30.
If you have any questions, please feel free to contact me.
Sincerely,
Jeff Rausch
OAUG
Jeffrey Rausch
Association Manager
OAUG
415 East Paces Ferry Rd., NE
Suite 200
Atlanta, GA USA 30305-2405
Tel: +1.404.240.0897
Fax: +1.404.240.0998
jrausch@meetingexpectations.com
Subject: REG: KEY FLEX FIELDS
Date: Thu, 15 Apr 1999 10:41:49 -0400 (EDT)
The Application hang-up when trying to compile a Key Flex Field.
Please Help!!
Thanks,
Babu
From: "carla pasos" carlapasos@hotmail.com
Subject: Re: REG: KEY FLEX FIELDS
There is a patch for rel 11.01 NCA that take care of the issue. I
would call Oracle and open a tar to get the patch from them.
Sent: Thursday, April 15, 1999 2:46 PM
Subject: HELP!!! Duplicate Segments??????
Hi,
I have a very strange occurance. I am in the process of setting up GL
11.02, and I just tried to look at my segment values, and when I did put in
Account for my segment in the "Find" screen, I get two segments, both called
Account. This happens with all segments. It looks like there are two of
each segments when I go to call up the segment values.
Has anyone ever seen this??
Any help would be appreciated.
Thanks,
Bill
From: Rama Krishna Rama.Krishna@hds.com
Subject: RE: HELP!!! Duplicate Segments??????
Hi Bill,
You would not have filled in all the other three
fields of this form. If you give the Application
Name, Flexfield Name, Structure Name then you
should not get the two segment name like you
are getting right now.
This is because the primary key for the
fnd_id_flex_structures is a combination of
Application_id, id_flex_code, id_flex_num.
In such circumstances an id_flex_num of
101 would exist multiple times for each
of the id_flex_codes.
Let me know what happends.
Rama Krishna
Applications Consultant
Fortuna Technologies
Sunnyvale , CA
From: "Bill Keenan" bkeenan@goodegg.com
Subject: Re: HELP!!! Duplicate Segments??????
Hi Rama,
Your were right. This was a very stupid one on my part. I just have to
enter the Structure name as well, and all is ok. Thank you very much for
your help, this is one I should have know or figured out immediately on my
own.
Thanks again,
Bill
Sent: Monday, May 17, 1999 2:11 PM
Subject: GL-Acctng Flexfield Structure
Hi everyone
My client is live since January 1999 on Oracle Financials Rel. 10.7 SC
Prod
16.1. The GL Accounting Flexfiled structure is as follows:
No.---Segment---- Data type---Size--Validation Type
1 Compnay Character 02 Independent
2 Location Character 02 Independent
3 Division Character 02 Independent
4 Activity Centre Character 04 Independent
5 Customer Character 04 Independent
6 Process Character 03 Dependent
7 Account Character 09 Independent
8 Sub-Account Character 03 Dependent
9 Blank1 Character 03 Independent
10 Blank2 Character 03 Independent
The blank segments have been populated with the default value of '000'
in
each of the code-combinations created thus far.
My query to all of you is related to a sudden change in requirements
here.
Is it recommended to change
a) the default size of the blank segment from 03 to 04 ? How do I ensure
data integrity with both retrospective and prospective effects kept in
mind.
b) the validation type of the segment 'PROCESS' (dependent on Customer)
from
'Dependent' to 'Independent' ?
I do not have a very positive feeling about doing either of the above
because of historical data already in the system. How would the
code-combinations table recognize the old data stored already and match
it
to the new structure? Or is creating a new Set of Books with a new
structure
the solution; in that case how do I map the flexfields segments in the
case
of the new, enlarged segment size or validation type.
Any information/pointers/leads would be greatly appreciated.
Many thanks
Varun Mehra
Consultant-Oracle Applications
GE Capital, India
From: "Bharat Bhaaradwaj" bharatbh@wipsys.soft.net
Subject: RE: GL-Acctng Flexfield Structure
Hi Varun
Increase of size is allowed in the value sets where as decrease is not
allowed, thank your stars that the client has not requested for a
decrease.
Coming to your question. The historical data will stay to exist but
without the fields 9 and 10 values. Meaning that these will be 000 till
the date the segments were entered with values. When you report on these
last 2 segments it will have irrelevant data for the previous period i.e
your historical data. Then you need to create new code combinations.
Then Apps might give problems with certian old data pending actions if
you disable code combinations or that default '000' values in the 9 and
10 segments. Further please take care that you test this before even
thinking of implementing in production. If the compilation fails when
you freeze the flexfield then you might lose all the existing data.
If any validation type is changed, think of data migration...It looks
like a tough problem, again the old data might get wiped out and you
might not be able to view old information or report on them. You need to
map each and every existing affected combination to the new codes that
has to be created with the new structure and values, practically every
combination might effect in one way or the other. All this is just with
theoretical knowledge that i am writing here. This is just some of the
problems or behaviours that can be expected by apps. There might be more
surprises.
All the best
Regards
Bharat
B.Bharat Bhaaradwaj
Wipro Infotech - ESD
40/A Bassappa Complex
Lavelle Road
Bangalore 560001
Ph.2215010 Ext.220/221
Sent: Tuesday, May 18, 1999 17:19
Subject: RE: GL-Acctng Flexfield Structure
Varun,
In answer to your question a):
We changed a future use segment from three characters to sixteen a few
years
ago. Our segment also had a defaulted "000" in all the code combinations.
We had no problem with the historical data, but in our case the segment
was
left justified with filled blanks after extending it to 16 characters.
Debbie Griffin
Fermilab
dgriffin@fnal.gov
630-840-8754
From: "Mehra, Varun (CAP, GECSI)" Varun.Mehra@geind.GE.com
Cc: "'dgriffin@fnal.gov'" dgriffin@fnal.gov
Subject: RE: GL-Acctng Flexfield Structure
Debbie/Bharat/Everyone,
Further to Bharat's pointers/leads I was waiting for an answer like
Debbie's. Thank you very much for the same. Debbie, could you please share
your approach of going ahead with this. My idea as of now, which I am
testing out, is to define another set-of-books with the new structure having
the Blank1 segment (present size 3) replaced with another segment, say B1
(new size 6). Then I am consolidating from this set-of-book to the new one,
defining the segment rule for the Blank1 segment as 'Single Value' into the
B1 Segment. This way past data captured in Blank1 as 000 will be captured in
000000 now. And going ahead I can use other values. All this has had a
smooth transition as on date. So where is the gotcha!!!
One is that if I have to get month-on-month data then I have to consolidate
as many number of times as I have data periods opened. Another, and more
importantly what happens to my subledgers - FA, AP, AR. How am I going to
change that set-of-book?? How did you resolve that?? The Client hasn't
shown great keeness to install the Multi-Org patch. Am I stuck???
Any further pointers/leads/ideas would be greatly appreciated.
Many thanks all the same
Varun Mehra
Consultant-Oracle Applications
GE Capital, India
From: "Debbie Griffin" dgriffin@fnal.gov
To: "Mehra, Varun (CAP, GECSI)" Varun.Mehra@geind.GE.com,
Subject: Re: GL-Acctng Flexfield Structure
We simply changed the length of the segment. Since our segment was left
justified, we did not update our code combinations, but just left "000
" (with13 blanks) as a valid code. That may be the one reason it was so
simple for us.
And at the time, we had no other modules in place but GL. We did have to
modify some of our interfaces that were hard coded for only the three
character segment.
However, we change segment values all the time here. I leave the subledgers
(we now have INV, AP,and PO with encumbrance) code combinations as they
were entered. After all data has been transferred to GL for the month, I
use the MassAllocations module to change the segment values.
Hope this helps.
Debbie Griffin
dgriffin@fnal.gov
Fermilab
630-840-8754