Resubmissions of MassAllocation
Original Message:
In our current implementation of release 10.7 NCA Government financial
applications, we have numerous MassAllocations that need to run on a nightly
basis. Unfortunately, the concurrent process to generate MassAllocations is
called via a form and not the standard request submissions. I am curious if
anyone has ever automated the MassAllocation process to be submitted on a
nightly/recurring basis. If you have could you please share your
experiences with me.
Thanks in advance,
Michael F. Blunck
Managing Principle Consultant
ARIS Corporation - Denver
303-675-4313 (Direct)
800-632-2705 (Pager)
Date: Thu, 6 May 1999 14:47:50 -0600
From: "Rahman, Milan" milan_rahman@nrel.gov
Cc: "'michael.blunck@aris.com'" michael.blunck@aris.com
Subject: RE: Resubmissions of MassAllocation
You can do this via PL/Sql and using FND_REQUST.SUBMIT_REQUEST by mimicking
what the form does. I did a presentation on RMOUG Training Days in 1998 on
automating nightly batches and this was part of the presentation. My
presentation was for 10.7 SC. I don't believe that the mechanics of this
submission is significantly different between SC and NCA.
Core processing requires that a row be inserted into GL_ALLOC_HISTORY with
the ALLOCATION_BATCH_ID from GL_ALLOC_BATCHES (where the BATCH_NAME is the
name of the Allocation you want), BATCH_NAME from GL_ALLOC_BATCHES,
SET_OF_BOOKS_ID as appropriate, REQUEST_ID is the Request_ID from the
FND_REQUEST.SUBMIT_REQUEST, RUN_STATUS='S', FROM_PERIOD_NAME from
GL_PERIOD_STATUSES.PERIOD_NAME, TO_PERIOD_NAME as appropriate, TO_PERIOD_NUM
from GL_PERIOD_STATUSES.PERIOD_NUM, TO_PERIOD_YEAR from
GL_PERIOD_STATUSES.PERIOD_YEAR. LAST_UPDATE_DATE, CREATED_BY,
CREATION_DATE, LAST_UPDATE_LOGIN is defaulted from GL_ALLOC_BATCHES.
This should get you going, and if you need further help, get in touch with
me.
Milan Rahman
Oracle Apps DBA
Softec Solutions, Inc.
Current Client: NREL
Inserting historic data
--- David Moore dmoore@UATC.com wrote:
When we converted to Oracle Applications originally,
in late 97, we
converted data from our legacy system starting with
the final period in 96,
and all of 97, as well as the early periods in 98,
up to the date we went
live. Now, someone has realized we should have
converted 95 and 96 as well
(which will include the last period of 94). Is this
possible? Can we go in
and add older data to our system? We are on 10.7
Gui, and have PO, AP, GL,
and FA running. Has anyone had any experience with
this?
Thanks in
advance.
David Moore
DBA, United Artists Theatre Circuit, Inc.
303.792.8816
Date: Fri, 7 May 1999 11:49:17 -0700 (PDT)
From: rajendra nagaraju rnagaraju@yahoo.com
Subject: Re: Data Conversion Questions
David,
We had a similar problem.
But, it has to be done behind the scenes.
You have to open up the periods in GL_PERIOD_STATUSES and update the
latest_period_opened field in GL_SETS_OF_BOOKS.
Then insert and update opening balances for the earliest period you
need to load in GL_BALANCES.
Then start moving forward until you get to the earliest period you have
know.
Regards,
Raj Nagaraju
x-------------x
Date: Fri, 18 Jun 1999 10:43:49 -0600
Date: Fri, 18 Jun 1999 12:44:03 -0500
From: "Logan, Ernie" Ernie_Logan@bmc.com
Subject: RE: Data Conversion Qs Revisited - Consolidation?
Yes, you could create a "history" set of books, and load the older data into
that SOB. You could then use a consolidated SOB for the longer term view
(reports, inquiry, etc). If you don't have AP, etc to worry about, you could
even use that consolidated SOB as the only SOB from that point forward by
posting directly to it, and ceasing to use the two original SOBs. I would
recommend consolidating with transaction detail if you decide to take that
route.
If you have AP, AR etc, then you would not want to change the posting SOB as
that would mean re-implementing those subsidiary applications.
Reversing Journals
From "Madhavi Ghodke" madhavi@pn2.vsnl.net.in
Subject GL-Reversing Journals-URGENT!
Date Thu, 13 May 1999 114704 -0400 (EDT)
Hi All,
We are on 10.6,we are getting the following errors during reversing
journal
entries
APP-00251-An assignment does not exists for these parameters.
SHRD-0014-GLPREV-Process exiting with error.
What could be the reasons?
Please help,
TIA
Madhavi
From Akshay Bhatt [SMTPakshayobhatt@hotmail.com]
Sent Saturday, May 15, 1999 844 AM
Subject Re GL-Reversing Journals-URGENT!
Check the period status of the reversing period.
Akshay
From Chetan Banglorewala ChetanB@allied-medical.co.ae
Subject RE GL-Reversing Journals-URGENT!
Date Saturday, May 15, 1999 312 PM
Madhavi,
Is document sequence required. If yes, you need to specify automatic
sequence for the category of journal which you are reversing.
Hope this helps.
Chetan
Date Sun, 16 May 1999 090624 +0530
From "Madhavi Ghodke" madhavi@pn2.vsnl.net.in
Subject Re GL-Reversing Journals-URGENT!
Hi All,
Thanks a lot for your help.
The error was solved by assigning document sequences for Reversal category
as 'Partially Used'.
Thanks once again
Madhavi
cc: (bcc: Dominic Dicondina/Wayne/Recovery)
Subject: Re: GL-Reversing Journals-URGENT!
v
Tia,
We found that we were unable to reverse journal entries that had an
apostrophe in the journal batch name or the journal name. So far this is
the only character that we've found that causes this. You might want to see
if this is your problem.
Good Luck
Rose
Date: Mon, 28 Jun 1999 08:32:25 -0400
From: ddicondina@SUNGARDRS.COM
Subject: Re: GL-Reversing Journals-URGENT!
We applied patches 568653 and 522782 to address this problem. We are 10.7
character, 7.3.4, SunSolaris.
Dominic DiCondina
GL Consolidation
From: rob merryman [mailto:rob_merryman@hotmail.com]
Sent: Monday, May 17, 1999 3:23 PM
Subject: GL Consolidation - Multi Segments to One Segment
Hi,
I'm working on setting up consolidation rules from an 11 segment chart of
accounts to 7 segment chart of accounts in 10.7 NCA. The issue is that
multiple segments from the subsidiary books map to one segment in the parent
books. Using the Account option to map subsidiary combinations to parent
combinations seems like a nightmare, as there are a few hundred thousand
code combinations.
Has anyone encountered this situation and come up with an efficient
solution? Does anyone have any ideas?
Thanks for you help!
Date: Tue, 18 May 1999 12:18:04 -0500
From: "Krzes, Joe" JKrzes@smith.com
Subject: RE: GL Consolidation - Multi Segments to One Segment
Message-ID: F5021D11EE9FD211916C0008C78C5E980E91DD@siihardy-msg03.corp.smith-intl.com
Rob,
Are you performing a consolidation or a conversion?
We convert from an operational chart of accounts to a reporting chart of
accounts that has fewer segments. We had three options to accomplish this,
1-use sql, 2-use the consolidation feature, 3-use FSG. After looking at all
three, the simpliest (without ISD involvement) was FSG. We simply wrote a
report who's rows could contain any combination of code ranges (standard FSG
row definition), but the description for the row is the reporting account
combination that we want to convert to. When the report is run, we get an
output that has the reporting account combination and an amount. We just
FTP down the output and send it in.
Additional benefits include the ability to run the report for any time
period, actual or plan, mth or ytd and can even use content sets and filters
(all standard FSG functionality). I know it's really a low-tech solution,
but it has been working so well that we just leave it alone. Anyone in the
department can run it and maintain it since it's FSG. No big expense or
long waits for ISD to come up with a solution (sorry ISD types).
Good Luck,
Joe
Running MassAllocation and G/L Posting
Date: Thu, 20 May 1999 12:45:37 -0400
From: "Haughwout, Rod" rod.haughwout@lmco.com
Subject: GL: RUNNING MASSALLOCATION AND G/L POSTING
I currently have the need to automate my clients' MASSALLOCATION Process. We
are currenlty running version 10.7 Character Mode.
I need to write something to initiate the MassAllocation routines then Post
the journals that it creates. There are approx 18 MassAllocations
and Postings in the entire process.
Can the Run MassAllocations ( GLAMAS ) routine be submitted from a UNIX
script and if so what are the required parameters ?
I also need to execute the Posting routine from this script. Is this routine
Posting ( GLPPOS ) capable of being run from a UNIX script
and if so what are the required parameters. If anyone has a routine that
works I certainly appreciate any help.
Thank You Very Much,
Rod Haughwout
Date: Thu, 20 May 1999 13:05:54 -0400
From: Mohan Thanikanti mthanika@camail2.harvard.edu
Subject: Re: GL: RUNNING MASSALLOCATION AND G/L POSTING
Hi,
We also have the similar requirement and i got the following response
from Oracle Support.
May this be helpfull for you.
Thanks,
MOHAN.
Prerequisites:
1) The batches that you are running MassAllocations for should already
have been validated when you define them in Define MassAllocations
Form and when you run the Validation program.
2) The Generate MassAllocations Form will let you pick ONLY the validated
batches. The form also does other validation on the period range that
you select for generation. Finally it inserts data into GL_ALLOC_HISTORY
table for generating batches. If you do not use the Generate Form for
running MassAllocations and insert directly into GL_ALLOC_HISTORY table,
you need to make sure that the data in GL_ALLOC_HISTORY table is valid.
If you insert INVALID data in GL_ALLOC_HISTORY table, the MassAllocations
program will NOT check for the validity of the data and you might get
INCORRECT results.
Development will NOT support the inaccurate results which might be obtained by
running Massallocations using invalid data.
Steps:
1) Populate GL_ALLOC_HISTORY table. You can do that through either one of
the following methods.
a) Insert data directly through SQL*Plus.
- In SQL*Plus, describe GL_ALLOC_HISTORY.
- Insert valid values for all required columns. For the
request_id column insert a 0, since the MassAllocation program
will only pick up those batches which correspond to a request_id
of 0 in GL_ALLOC_HISTORY table. You can insert multiple batches
in GL_ALLOC_HISTORY, all having a request_id of 0 and the program
will generate all of them in a single run.
OR
b) Utilize concurrent request hold.
- Submit the MassAllocation request through the form as usual.
- On the Requests form, Hold the MassAllocation request that you
just submitted, and note the request id (e.g. 1234). You may
want to use the profile option Concurrent: Hold Requests to
hold your request if needed.
- Update request_id in GL_ALLOC_HISTORY to 0 for the held request.
For example:
UPDATE gl_alloc_history
SET request_id 0
WHERE request_id 1234;
2) From the command line, issue the following command:
a) For releases prior to 10.7:
GLAMAS username/pwd 0 Y set_of_books_id incremental_ma_flag debug_flag
b) For release 10.7, and 11:
GLAMAS username/pwd 0 Y set_of_books_id incremental_ma_flag
average_journal_flag debug_flag
Parameter Legend:
----------------
username/pwd -------- username and password for the database.
set_of_books_id -----corresponding set of books id for your
responsibility.
incremental_ma_flag --- flag to indicate whether to run
MassAllocations
in incremental mode.
average_journal_flag --- flag to indicate average journal used by
Average Daily Balances Consolidation set of
books.
debug_flag ----------flag to indicate whether to run
MassAllocations in debug mode.
If you specify any value for the debug flag, the program will be
run in debug mode.
Examples:
--------
Prior to release 10.7:
GLAMAS apps/apps 0 Y 2 N
vs.
GLAMAS apps/apps 0 Y 2 N Y -- This will run MassAllocations
in debug mode.
Release 10.7, 11:
GLAMAS apps/apps 0 Y 2 N N
vs.
GLAMAS apps/apps 0 Y 2 N N D -- This will run MassAllocations
in debug mode.
*******************************************************************
* Janice L. Godfrey Oracle Corporation *
* Oracle Applications Support Worldwide Customer Support *
* 5955 T. G. Lee Blvd *
* Fax: (407) 888-1539 Suite 400 *
* Email: jgodfrey@us.oracle.com Orlando, FL 32822 *
*******************************************************************
Journal Batch reversed instead of Journal
Date: Tue, 17 Aug 1999 16:05:42 +0400
From: Srinivas Sreepada satncr@emirates.net.ae
To: OraApps-L@cpa.qc.ca
Subject: Journal Reversals
Hi,
We are on Rel 11 GL. We are importing Journals from a non Oracle System on a
daily basis. These Imported journals are batched based on the Journal
category and each day a batch could contain anything between 50 -400
Journals.
One day on finding an erroneous Journal the user attempted to reverse a
journal but while reversing he selected the option to reverse the batch ,
this reversed all the journals in a batch totalling 350 Journals and created
each journal as a separate batch.
Thus instead of reversing one journal he has reversed 350 journals in as
many batches.To correct this situation we have to reverse all the remaining
349 Journals this will be a herculean task as each batch will have to
reversed individually.
We cannot restore the backup as the problem was reported almost one week
later
Can anybody suggest a better and faster way of reversing these journals
Thanks
Srinivas
Date: Tue, 17 Aug 1999 09:04:32 -0400
From: "Mark W. Farnham" mwf@rsiz.com
Subject: RE: Journal Reversals
If you still have the original data you loaded into the interface table you
could reverse the signs on the amount fields and tack something on to the
journal name to make it clear it is intended as a reversal of the
reversals.
Then use journal import again.
Or perhaps you can reverse the whole batch again and then finally reverse
the one journal that was intended to be reversed. That used to work, except
for some problems with very long journal names.
Mark
Date: Wed, 18 Aug 1999 09:01:13 +0400
From: Srinivas Sreepada satncr@emirates.net.ae
To: oraapps-l@cpa.qc.ca
Subject: RE: Journal Reversals
Mark,
Thanks for the suggestions while I can explore the possibility of using the
first option , the second option the problem in that when reversals are
created each journal is in a different batch,i.e they are all now single
journal batches so i will have to reverse then one by and there are 350 of
them.
Unfortunately there is no set up option which would make GL batch the
reversal also as one batch, in which case it would be simple to re- reverse
it.