GL_periods and GL_balances

Can anyone explain how to retrieve the previous months amounts based on tables gl_period_statuses and gl_balances..For eg.aquiring the actual values for last 10 months, what is the process?

Hello.
Is there any reason for not using FSG to retrieve that information? It is the perfect tool to do it.
Octavio

Similar Messages

GL Balances - SQL Query Help

Hello All,
I am trying to build a query which will give a monthly bucket for GL Balance which are due.I have built the below query which has the basic information but i am trying to rollup GL Periods which i am not able to find any link also. Could any one please help me in deriving the monthly bucket using GL Periods or is there any other way for this.
SELECT gb.code_combination_id,
       gb.currency_code,
       SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0))) - SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0))"CLOSE BAL",
       gcck.concatenated_segments ,
       flvt.description    account_type,
       gcck.segment2 department
FROM apps.gl_balances gb,
     apps.gl_code_combinations_kfv gcck,
     apps.fnd_flex_values_tl flvt
WHERE gb.currency_code = 'INR'
AND    gb.code_combination_id = gcck.code_combination_id
AND    gcck.segment3           = flvt.flex_value_meaning
AND   ((nvl(gcck.segment3,'') >= '5000' AND nvl(gcck.segment3,'') <= '7000'))
GROUP BY gb.code_combination_id,
        gb.currency_code,
        gcck.concatenated_segments,
        flvt.description,
        gcck.segment2
My output should look like this
Department      Account Type   Concatinated Segment    Closing Bal            JAN    FEB   MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
Please help me on this ....Need to get this done ASAP.

Hi,
check if this can be useful
select period_name,segment2,Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov,Dec
from
(select gp.period_name,gcck.segment2 ,lag(SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)))
over (partition by gp.period_name order by gp.period_name) Jan,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)) Feb,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0))Mar,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)) Apr,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)) May,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)) Jun,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0))Jul,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0))Aug,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)) Sep,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)) Oct,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0)) Nov,
SUM(( NVL(gb.period_net_dr,0) + NVL(gb.begin_balance_dr,0)))
- SUM(NVL(gb.period_net_cr,0)+NVL(gb.begin_balance_cr,0))DEc
from gl_periods gp,gl_balances gb,gl_code_combinations_kfv gcck
where gp.period_name = gb.period_name
and gb.code_combination_id = gcck.code_combination_id
and gp.period_set_name = 'Accounting'
and gp.period_year = '2010'
and gp.period_type = 'Month'
group by gp.period_name,gcck.segment2 )
order by period_name
thanks & regards
raghu

Move data from one table to another table

Hi all,
I had a custom table called sales_data in that table there are columns like JAn,FEB,upto DEC including other columns so in each month there is some data total data is 23000 count but each month has has specific data like JAn-2500,FEB-2000 like that it has total 23000 records
My Requirement is i have to move data from one table to another table that too if i will pass jan only jan data should move like that feb,march,.....
in my table there is no month column i had get it from another table called gl_periods and by using cursor and case function i have written the code
well while when i am inserting data am passing year,month as parameters but 23000 data is moving it should get like that.
Please suggest me.its urgent
Thank You

Hi hamid,
               Please go through the below procedure.
CREATE OR REPLACE PROCEDURE APPS.copy_sales_to_forecast(p_fiscal_year varchar2,p_month number)
IS
CURSOR C1 IS select period_year,period_num,start_date,end_date from apps.gl_periods
             where period_set_name='Accounting'
             and   period_year=p_fiscal_year
             and   period_num<=p_month;
type type1 is table of xxc_forecast_data%rowtype;
t1 type1;
BEGIN
FOR CREC IN C1 LOOP
BEGIN
DELETE FROM xxc_forecast2
where fiscal_year = crec.period_year
and attribute1='Copied From Sales to Forecast Table of Month '||crec.period_num;
END;
SELECT
product_category           ,
product_sub_category       ,
product_line               ,
product_style              ,
item_number                ,
item_description           ,
customer_name              ,
customer_number            ,
sales_channel              ,
null      ,
CASE
    WHEN crec.period_num=1 THEN sales_amount_month1
    ELSE 0
END Transaction_quantity_period1,
CASE
    WHEN crec.period_num=1 THEN sales_cost_month1
    ELSE 0
END item_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_mtl_cost_month1
    ELSE 0
END item_material_cogs_period1 ,
CASE
    WHEN crec.period_num=1 THEN sales_mtl_ovhd_cost_month1
    ELSE 0
END item_mtl_ovhd_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_res_cost_month1
    ELSE 0
END item_resource_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_op_cost_month1
    ELSE 0
END item_op_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_ovhd_month1
    ELSE 0
END item_ovhd_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_units_month1
    ELSE 0
END extended_amount_us_period1,
CASE
    WHEN crec.period_num=2 THEN sales_amount_month2
    ELSE 0
END Transaction_quantity_period2,
CASE
    WHEN crec.period_num=2 THEN sales_mtl_cost_month2
    ELSE 0
END item_material_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_mtl_ovhd_cost_month2
    ELSE 0
END item_mtl_ovhd_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_res_cost_month2
    ELSE 0
END item_resource_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_op_cost_month2
    ELSE 0
END item_op_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_ovhd_month2
    ELSE 0
END item_ovhd_cogs_period2,
   CASE
    WHEN crec.period_num=2 THEN sales_units_month2
    ELSE 0
END extended_amount_us_period2,
CASE
    WHEN crec.period_num=3 THEN sales_amount_month3
    ELSE 0
END Transaction_quantity_period3,
CASE
    WHEN crec.period_num=3 THEN sales_mtl_cost_month3
    ELSE 0
END item_material_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_mtl_ovhd_cost_month3
    ELSE 0
END item_mtl_ovhd_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_res_cost_month3
    ELSE 0
END item_resource_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_op_cost_month3
    ELSE 0
END item_op_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_ovhd_month3
    ELSE 0
END item_ovhd_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_units_month3
    ELSE 0
END extended_amount_us_period3,
CASE
    WHEN crec.period_num=4 THEN sales_amount_month4
    ELSE 0
END Transaction_quantity_period4,
CASE
    WHEN crec.period_num=4 THEN sales_mtl_cost_month4
    ELSE 0
END item_material_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_mtl_ovhd_cost_month4
    ELSE 0
END item_mtl_ovhd_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_res_cost_month4
    ELSE 0
END item_resource_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_op_cost_month4
    ELSE 0
END item_op_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_ovhd_month4
    ELSE 0
END item_ovhd_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_units_month4
    ELSE 0
END extended_amount_us_period4,
CASE
    WHEN crec.period_num=5 THEN sales_amount_month5
    ELSE 0
END Transaction_quantity_period5,
CASE
    WHEN crec.period_num=5 THEN sales_mtl_cost_month5
    ELSE 0
END item_material_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_mtl_ovhd_cost_month5
    ELSE 0
END item_mtl_ovhd_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_res_cost_month5
    ELSE 0
END item_resource_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_op_cost_month5
    ELSE 0
END item_op_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_ovhd_month5
    ELSE 0
END item_ovhd_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_units_month5
    ELSE 0
END extended_amount_us_period5,
CASE
    WHEN crec.period_num=6 THEN sales_amount_month6
    ELSE 0
END Transaction_quantity_period6,
CASE
    WHEN crec.period_num=6 THEN sales_mtl_cost_month6
    ELSE 0
END item_material_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_mtl_ovhd_cost_month6
    ELSE 0
END item_mtl_ovhd_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_res_cost_month6
    ELSE 0
END item_resource_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_op_cost_month6
    ELSE 0
END item_op_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_ovhd_month6
    ELSE 0
END item_ovhd_cogs_period6,
   CASE
    WHEN crec.period_num=6 THEN sales_units_month6
    ELSE 0
END extended_amount_us_period6,
CASE
    WHEN crec.period_num=7 THEN sales_amount_month7
    ELSE 0
END Transaction_quantity_period7,
CASE
    WHEN crec.period_num=7 THEN sales_mtl_cost_month7
    ELSE 0
END item_material_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_mtl_ovhd_cost_month7
    ELSE 0
END item_mtl_ovhd_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_res_cost_month7
    ELSE 0
END item_resource_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_op_cost_month7
    ELSE 0
END item_op_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_ovhd_month7
    ELSE 0
END item_ovhd_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_units_month7
    ELSE 0
END extended_amount_us_period7,
CASE
    WHEN crec.period_num=8 THEN sales_amount_month8
    ELSE 0
END Transaction_quantity_period8,
CASE
    WHEN crec.period_num=8 THEN sales_mtl_cost_month8
    ELSE 0
END item_material_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_mtl_ovhd_cost_month8
    ELSE 0
END item_mtl_ovhd_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_res_cost_month8
    ELSE 0
END item_resource_cogs_period7,
CASE
    WHEN crec.period_num=8 THEN sales_op_cost_month8
    ELSE 0
END item_op_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_ovhd_month8
    ELSE 0
END item_ovhd_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_units_month8
    ELSE 0
END extended_amount_us_period8,
CASE
    WHEN crec.period_num=9 THEN sales_amount_month9
    ELSE 0
END Transaction_quantity_period9,
CASE
    WHEN crec.period_num=9 THEN sales_mtl_cost_month9
    ELSE 0
END item_material_cogs_period9,
CASE
    WHEN crec.period_num=9 THEN sales_mtl_ovhd_cost_month9
    ELSE 0
END item_mtl_ovhd_cogs_period9,
CASE
    WHEN crec.period_num=9 THEN sales_res_cost_month9
    ELSE 0
END item_resource_cogs_period7,
CASE
    WHEN crec.period_num=9 THEN sales_op_cost_month9
    ELSE 0
END item_op_cogs_period9,
CASE
    WHEN crec.period_num=9 THEN sales_ovhd_month9
    ELSE 0
END item_ovhd_cogs_period9,
   CASE
    WHEN crec.period_num=9 THEN sales_units_month9
    ELSE 0
END extended_amount_us_period9,
CASE
    WHEN crec.period_num=10 THEN sales_amount_month10
    ELSE 0
END Transaction_quantity_period10,
CASE
    WHEN crec.period_num=10 THEN sales_mtl_cost_month10
    ELSE 0
END item_material_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_mtl_ovhd_cost_month10
    ELSE 0
END item_mtl_ovhd_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_res_cost_month10
    ELSE 0
END item_resource_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_op_cost_month10
    ELSE 0
END item_op_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_ovhd_month10
    ELSE 0
END item_ovhd_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_units_month10
    ELSE 0
END extended_amount_us_period10,
CASE
    WHEN crec.period_num=11 THEN sales_amount_month11
    ELSE 0
END Transaction_quantity_period11,
CASE
    WHEN crec.period_num=11 THEN sales_mtl_cost_month11
    ELSE 0
END item_material_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_mtl_ovhd_cost_month11
    ELSE 0
END item_mtl_ovhd_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_res_cost_month11
    ELSE 0
END item_resource_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_op_cost_month11
    ELSE 0
END item_op_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_ovhd_month11
    ELSE 0
END item_ovhd_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_units_month11
    ELSE 0
END extended_amount_us_period11,
CASE
    WHEN crec.period_num=12 THEN sales_amount_month12
    ELSE 0
END Transaction_quantity_period12,
CASE
    WHEN crec.period_num=12 THEN sales_mtl_cost_month12
    ELSE 0
END item_material_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_mtl_ovhd_cost_month12
    ELSE 0
END item_mtl_ovhd_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_res_cost_month12
    ELSE 0
END item_resource_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_op_cost_month12
    ELSE 0
END item_op_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_ovhd_month12
    ELSE 0
END item_ovhd_cogs_period12,
    CASE
    WHEN crec.period_num=12 THEN sales_units_month12
    ELSE 0
END extended_amount_us_period12,
CASE
    WHEN crec.period_num=2 THEN sales_cost_month2
    ELSE 0
END item_cogs_period2,
   CASE
    WHEN crec.period_num=3 THEN sales_cost_month3
    ELSE 0
END item_cogs_period3,
   CASE
    WHEN crec.period_num=4 THEN sales_cost_month4
    ELSE 0
END item_cogs_period4,
   CASE
    WHEN crec.period_num=5 THEN sales_cost_month5
    ELSE 0
END item_cogs_period5,
CASE
    WHEN crec.period_num=6 THEN sales_cost_month6
    ELSE 0
END item_cogs_period6,
CASE
    WHEN crec.period_num=7 THEN sales_cost_month7
    ELSE 0
END item_cogs_period7,
   CASE
    WHEN crec.period_num=8 THEN sales_cost_month8
    ELSE 0
END item_cogs_period8,
CASE
    WHEN crec.period_num=9 THEN sales_cost_month9
    ELSE 0
END item_cogs_period9,
   CASE
    WHEN crec.period_num=10 THEN sales_cost_month10
    ELSE 0
END item_cogs_period10,
   CASE
    WHEN crec.period_num=11 THEN sales_cost_month11
    ELSE 0
END item_cogs_period11,
CASE
    WHEN crec.period_num=12 THEN sales_cost_month12
    ELSE 0
END item_cogs_period12,
a.fiscal_year   ,
a.budget_entity ,
a.organization_code,
a.customer_id ,
a.inventory_item_id ,
NULL,
NULL,
a.created_by ,
a.last_updated_by ,
a.creation_date ,
a.last_update_date ,
'Copied From Sales to Forecast Table of Month '||crec.period_num,
a.attribute2,
a.attribute3 ,
a.attribute4 ,
a.attribute5 ,
a.attribute6 ,
a.attribute7 ,
a.attribute8 ,
a.attribute9 ,
a.attribute10,
a.attribute11,
a.attribute12,
a.attribute13,
a.attribute14,
a.attribute15
bulk collect into t1
FROM xxc_sales_data a
where a.fiscal_year          = crec.period_year
having CASE
             WHEN crec.period_num=1 THEN sum(sales_amount_month1)
             WHEN crec.period_num=2 THEN sum(sales_amount_month2)
             WHEN crec.period_num=3 THEN sum(sales_amount_month3)
             WHEN crec.period_num=4 THEN sum(sales_amount_month4)
             WHEN crec.period_num=5 THEN sum(sales_amount_month5)
             WHEN crec.period_num=6 THEN sum(sales_amount_month6)
             WHEN crec.period_num=7 THEN sum(sales_amount_month7)
             WHEN crec.period_num=8 THEN sum(sales_amount_month8)
             WHEN crec.period_num=9 THEN sum(sales_amount_month9)
             WHEN crec.period_num=10 THEN sum(sales_amount_month10)
             WHEN crec.period_num=11 THEN sum(sales_amount_month11)
             WHEN crec.period_num=12 THEN sum(sales_amount_month12)
            END !=0;
FORALL i IN t1.first .. t1.last
INSERT INTO xxc_forecast2 VALUES t1(i);
--commit;
END LOOP;
END;
Thank You

Wat is wrong in this formula column pls help me..

wat is wrong in this formula column pls help me..
function CF_BEGIN_BALFormula return Number is
cr number;
dr number;
begin
     select begin_balance_cr,begin_balance_dr into cr,dr from gl_balances
     where gl_balances.period_name=:from_period
and gl_balances.code_combination_id= :ccid;
if ( abs(CR) > abs (DR) ) then
return nvl((CR - DR ) , 0) ;
else return nvl((DR - CR ) , 0) ;
end if;
end;

Without any error message, it's guess work, but one thing - where do you expect those bind variables will come from?
FUNCTION cf_begin_balformula
   RETURN NUMBER
IS
   cr   NUMBER;
   dr   NUMBER;
BEGIN
   SELECT begin_balance_cr, begin_balance_dr
     INTO cr, dr
     FROM gl_balances
    WHERE gl_balances.period_name = :from_period
      AND gl_balances.code_combination_id = :ccid;
   IF (ABS (cr) > ABS (dr)) THEN
      RETURN NVL ((cr - dr), 0);
   ELSE
      RETURN NVL ((dr - cr), 0);
   END IF;
END cf_begin_balformula;

How to time dimension

How do you link a time dimension to the fact table?
If the time dimension has a sequence as the PK then
the following columns:
year
month
quarter
day
time
etc..
How is the fact table connected to the time dimension if the fact table has the
primary key as a FK in the fact table?
-Jim

Hi Ragnar
Because a date is in fact stored as a number you don't need a surrogate key for your time dimension. You can make the primary key the date itself. Then you just join from the fact to the time dimension on the date.
Oh yes, you would need to populate the time dimension before loading the fact table. But then this is true of all star schemas. You must populate the dimensions before you populate the facts.
However, in the case of time, because it never changes over time (pardon the pun) you could load years of dates way out into the future. Then you would never have to worry about it for a while.
I have customers who are using E-Business Suite where the time dimension is fed from GL_PERIODS and BOM_CALENDAR_DATES. Because the periods are entered once per year in most cases then they only need to run the load once per year. Matrialized vieww of time work well too.
Hope this helps
Regards
Michael

Updating one Segment Value in GL Code Combinations

Dear Members,
We are using Oracle GL in our Organization from past couple of years.
Our COA consists of 6 Segments (i.e, Company--Organization--Area--Activity--Account--Product)
Now users are requesting us to change few account combinations for instance
11-00-00-00-123456-0000 to 11-00-00-00-123456-1000 ie. We have to update all the Posted and Unposted Journals having code combination of 11-00-00-00-123456-0000 to 11-00-00-00-123456-1000.
Please let me know whether this is a common practice? Are we allowed to do such updates without any adverse effects?
If we are allowed to update is there any API available?
Many thanks in advance.
Best Regards.

Hi
If you do this from the backend (i.e. update GL_JE_LINES and GL_BALANCES) it is completely unsupported (for obvious reasons).
If you want to do it via the frontend the General Ledger Mass Maintenance function will do it (Setup > Other > Mass Maintenance), i.e. it will move the balances from one combination to another. It does not create journals to do so though so it depends on the business requirement as to whether an audit trail is required for the change.
It's a pretty common practice - finance often want new cost centres, change their minds about cost centres and move balances around. I usually don't use Mass Maintenance as the auditors usually prefer journals but if a mistake was made in the cost centre setup or something then yes, Mass Maintenance works. Give it a shot in your test environment, show finance what results and check that they are happy with that.
Regards
Jo

Measures in different levels

I am having problems with measures based on different levels of a dimension.
The situation is: I have a product dimension with 2 levels (category and detail) and a client dimension. I want a measure with the number of distinct clients wich buys each product (it works fine with count distinct). But I also want a measure with the number of distinct clients wich buys the category of products, wich it's not working.
I have tried level based measures, but it didn't show the right result. I have changed the aggregate rule for this measure to count distinct, but it shows the same result as the SUM.
Can I define a custom rule for aggregation based on attributes of another tables?
Does anyone know a solution for this?

The output of the reports needs to be as below which shows details of a single customer.
customer_name---ca_number-----obl_number--------gl_balance--------limit_available-----state
Krio motors---------222222222-----763764754---------37000.00--------1834297.00--------CA
Krio motors---------222222222-----326635675---------34820.00--------1834297.00--------CA
Krio motors---------111111111-----326684759---------670000.00------3456789.00--------CA
Krio motors---------111111111-----326611111---------32400.00--------3456789.00--------CA
Krio motors---------111111111-----326622222---------8700.00----------3456789.00--------CA
Krio motors---------111111111-----326633333---------632450.00------3456789.00--------CA
here for each record in dimension D6 (for each Ca_number) there are many records in dimension D1 (obl_number records)
The limit_available is at ca_number level (higher level) and gl_balance is in obl_number detail level.
Thank you.

Setup "conflict domain" for posting

Hi
I would like to configure a "conflict domain" for the Oracle Financials Posting concurrent program.
We've setup Posting to run concurrently for each batch of SET_OF_BOOKS_ID/USER_JE_SOURCE rows inserted into the GL_INTERFACE table.
The two concurrent programs are GLPPOS and GLPAUTOP. The conflict resolution is defined as "global" between the two.
Mostly it runs fine, but occasionally a long-running GLPPOS holds up several GLPAUTOP requests as they are labelled as "Standby" when waiting.
There is however no reason for such a wait to occur since the data is different in each case.
I've read up on conflict domains using the following documentation.
http://download-uk.oracle.com/docs/cd/B25516_14/current/acrobat/115sacg.zip
and realise that a "conflict domain" can be defined, which will enable changing the conflict resolution from "global" to "domain".
The question I have is how to go I about configuring a "Conflict domain" based on SOB ID and JE Source Name ?
Also, to which of the two concurrent programs should I associate the new "Conflict Domain", i.e. GLPPOS or GLPAUTOP?
Finally, is there a PL/SQL api available for configuring and associating "conflict domains"?
I'm also aware that the GL_DAILY_BALANCES/GL_JE_LINES and GL_BALANCES tables require partitioning, which would siginicantly improve the performance of GLPPOS, but would like to firstly focus on the conflict issue and then consider partitioning.
db = 10.2.04
ebs = 11.5.10.2
Much appreciate any help or ideas that could be offered.

Yes, I have looked at the document. I have gone into the Concurrent Conflict Domain form, but am unsure as to what to enter under "Domain", "Short Name" and "Description.
Say for example a posting against a Set of Books/JE Source is running (2,238), then another Posting (2,200) should be able to run concurrently.
What do I enter under the "Domain" and "Short Name" ?
I'm new to Oracle Apps, so all these terms and forms are a bit confusing at this stage!

How can i subtract budget and actuals amount from gl_balances in discoverer

I have a problem with a discoverer report.
The table is GL_BALANCES (Financials), and i tried to subtract data of current year and last year, same month, or data from actuals and budgets amounts.
Data from actuals have the "A" code in the ACTUAL_FLAG field, and budgets amounts have a "B" code. I construct a cross-tab report with ACTUAL_FLAG field in the "X" axis and the accounts segments in the "Y" axis (From GL_CODE_COMBINATIONS). The problem is: How can i substract budget and actuals amounts? Is the same field but differents columns in report.
I cannot use analytics function because the version of database does not support that .
Somebody told me: "...You need to construct a custom folder to handle this..."
I don't want to finish the reports in Excel...
Thanks.

Hi Miguel
You can either create a database view or custom folder to do this using aliases for the two joins to the same table.
For example, you need something like this in the body of the SQL:
select
act.code_combination_id,
nvl(act.period_net_dr,0) actual_net,
nvl(bgt.period_net_dt,0) budget_net,
nvl(bgt.period_net_dt,0) - nvl(act.period_net_dr,0) diff,
act.period_name
from
gl_balances act,
gl_balances bgt
where
act.set_of_books_id = bgt.set_of_books_id and
act.code_combination_id = bgt.code_combination_id and
act.period_name = bgt.period_name
Of course you will still need to add your own joins to get the code combinations but I trust you get the gist.
Hope this helps
Regards
Michael

Query on GL_BALANCES Table is very slow

Dear Members,
I have prepared a query on GL_BALANCES Table which is as follows:
SQL>
select (nvl(sum(gb.period_net_dr), 0) - nvl(sum(gb.period_net_cr), 0))
INTO V_AMT
from gl_balances gb,
gl_code_combinations gcc,
fnd_flex_value_hierarchies ffvh
where gb.set_of_books_id = 7
and gb.actual_flag = 'B'
and gb.period_year = P_YEAR --'2010'
and gb.budget_version_id = P_BUD_VER_ID--1234
and gb.code_combination_id = gcc.code_combination_id
and gcc.segment3 >= ffvh.child_flex_value_low
and gcc.segment3 <= ffvh.child_flex_value_high
and ffvh.flex_value_set_id = 1012576
and ffvh.parent_flex_value = P_FLEX_VAL;
The above query is taking long time to complete.
Plan of my query is as follows
SELECT STATEMENT, GOAL = CHOOSE     Cost=49885     Cardinality=1     Bytes=64
SORT AGGREGATE                                    Cardinality=1     Bytes=64
MERGE JOIN               Cost=49885     Cardinality=12     Bytes=768
SORT JOIN               Cost=49859     Cardinality=2192     Bytes=74528
HASH JOIN               Cost=49822     Cardinality=2192     Bytes=74528
TABLE ACCESS FULL     Object owner=GL     Object name=GL_BALANCES     Cost=47955     Cardinality=2192     Bytes=50416
TABLE ACCESS FULL     Object owner=GL     Object name=GL_CODE_COMBINATIONS     Cost=1854     Cardinality=526850     Bytes=5795350
FILTER
SORT JOIN
INDEX RANGE SCAN     Object owner=APPLSYS     Object name=FND_FLEX_VALUE_HIERARCHIES_N1     Cost=2     Cardinality=2     Bytes=60
Can any one please help me in tuning this query.
Thanks in advance.
Best Regards.

As per the other replies, you've not really given enough information to go on - what are you trying to achieve, versions, etc.
On my old apps 11.5.8 system, the explain plan for your query uses GL_CODE_COMBINATIONS_U1 rather than a full scan of gl_code_combinations.
Check your stats are up to date (select table_name, num_rows, last_analyzed from dba_tables where ...)
See if you can also use period_name and/or period_set_name (or period_num) from GL_Periods rather than period_year (i.e. use P_YEAR to lookup the period_name/period_set_name/period_num from gl_periods). It might be faster to do per period and then consolidate for the whole year, as there are indexes on gl_balances for columns period_name, period_set_name, period_num.
regards, Ivan

SQL Tuning- slow query on GL_BALANCES- Explain plan provided

Hi- I really need some help here.
The following SQL statement has been identified to perform poorly.
It currently takes from 2-3 minutes to execute. I see it is because GL_BALANCES has so many rows.
Is there any way around this? Explain and info below. Thanks gurus!
This is the SQL statement:
SELECT DISTINCT GLB.CODE_COMBINATION_ID CCID
FROM gl_balances GLB, gl_code_combinations GCC
WHERE GLB.ACTUAL_FLAG = 'A'
AND GLB.Last_Update_Date > to_date('11-JAN-2010','DD-MON-YYYY')
AND GLB.code_combination_id = GCC.code_combination_id
AND EXISTS (
              SELECT 1
              FROM fnd_flex_value_sets A, fnd_flex_values B
              WHERE A.flex_value_set_name = 'XXX_XXX'
              AND UPPER(B.ATTRIBUTE3) = 'APPORTIONMENT'
              AND A.flex_value_set_id = b.flex_value_set_id
              AND GCC.segment11 = b.flex_value
           );The version of the database is 11.1.0.7.
These are the parameters relevant to the optimizer:
NAME TYPE VALUE
optimizerautostats_job boolean FALSE
optimizerextended_cursor_sharing_r string NONE
el
optimizer_capture_sql_plan_baselines boolean FALSE
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 11.1.0.7
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
optimizer_secure_view_merging boolean FALSE
optimizer_use_invisible_indexes boolean FALSE
NAME TYPE VALUE
optimizer_use_pending_statistics boolean FALSE
optimizer_use_sql_plan_baselines boolean TRUE
SQL> show parameter db_file_multi
NAME TYPE VALUE
db_file_multiblock_read_count integer 128
SQL> show parameter db_block_size
NAME TYPE VALUE
db_block_size integer 8192
SQL> show parameter cursor_sharing
NAME TYPE VALUE
optimizerextended_cursor_sharing_r string NONE
el
cursor_sharing string EXACT
select
2 sname
3 , pname
4 , pval1
5 , pval2
6 from
7 sys.aux_stats$;
SNAME PNAME PVAL1
PVAL2
SYSSTATS_INFO STATUS
COMPLETED
SYSSTATS_INFO DSTART
09-02-2006 14:35
SYSSTATS_INFO DSTOP
09-02-2006 14:35
SNAME PNAME PVAL1
PVAL2
SYSSTATS_INFO FLAGS 1
SYSSTATS_MAIN CPUSPEEDNW 451.262136
SYSSTATS_MAIN IOSEEKTIM 10
SNAME PNAME PVAL1
PVAL2
SYSSTATS_MAIN IOTFRSPEED 4096
SYSSTATS_MAIN SREADTIM
SYSSTATS_MAIN MREADTIM
SNAME PNAME PVAL1
PVAL2
SYSSTATS_MAIN CPUSPEED
SYSSTATS_MAIN MBRC
SYSSTATS_MAIN MAXTHR
SNAME PNAME PVAL1
PVAL2
SYSSTATS_MAIN SLAVETHR
13 rows selected.
SQL> explain plan for
2 SELECT DISTINCT GLB.CODE_COMBINATION_ID CCID
3 FROM gl_balances GLB, gl_code_combinations GCC
4 WHERE GLB.code_combination_id = GCC.code_combination_id
5 AND GLB.ACTUAL_FLAG = 'A'
6 AND GLB.Last_Update_Date > '11-JAN-2010'
7 AND EXISTS (SELECT 1
8 FROM fnd_flex_value_sets A, fnd_flex_values B
9 WHERE A.flex_value_set_id = b.flex_value_set_id
10 AND A.flex_value_set_name = 'XXX_XXX'
11 AND UPPER(B.ATTRIBUTE3) = 'APPORTIONMENT'
12 AND GCC.segment11 = b.flex_value);
Explained.
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 1839014065
| Id | Operation | Name | Rows | By
tes | Cost (%CPU)| Time |
PLAN_TABLE_OUTPUT
| 0 | SELECT STATEMENT | | 4102 |
296K| 955K (3)| 03:11:03 |
| 1 | HASH UNIQUE | | 4102 |
296K| 955K (3)| 03:11:03 |
|* 2 | HASH JOIN | | 4102 |
296K| 955K (3)| 03:11:03 |
| 3 | NESTED LOOPS | | |
| | |
PLAN_TABLE_OUTPUT
| 4 | NESTED LOOPS | | 23907 | 1
354K| 2598 (1)| 00:00:32 |
| 5 | NESTED LOOPS | | 1 |
45 | 5 (0)| 00:00:01 |
| 6 | TABLE ACCESS BY INDEX ROWID| FND_FLEX_VALUE_SETS | 1 |
28 | 2 (0)| 00:00:01 |
|* 7 | INDEX UNIQUE SCAN | FND_FLEX_VALUE_SETS_U2 | 1 |
PLAN_TABLE_OUTPUT
| 1 (0)| 00:00:01 |
|* 8 | TABLE ACCESS BY INDEX ROWID| FND_FLEX_VALUES | 1 |
17 | 3 (0)| 00:00:01 |
|* 9 | INDEX RANGE SCAN | FND_FLEX_VALUES_N2 | 53 |
| 1 (0)| 00:00:01 |
|* 10 | INDEX RANGE SCAN | GL_CODE_COMBINATIONS_N11 | 25427 |
| 106 (1)| 00:00:02 |
PLAN_TABLE_OUTPUT
| 11 | TABLE ACCESS BY INDEX ROWID | GL_CODE_COMBINATIONS | 18664 |
236K| 2593 (1)| 00:00:32 |
|* 12 | TABLE ACCESS FULL | GL_BALANCES | 1022K|
15M| 952K (3)| 03:10:32 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
2 - access("GLB"."CODE_COMBINATION_ID"="GCC"."CODE_COMBINATION_ID")
7 - access("A"."FLEX_VALUE_SET_NAME"='SSA_SGL')
8 - filter(UPPER("B"."ATTRIBUTE3")='APPORTIONMENT')
9 - access("A"."FLEX_VALUE_SET_ID"="B"."FLEX_VALUE_SET_ID")
10 - access("GCC"."SEGMENT11"="B"."FLEX_VALUE")
12 - filter("GLB"."LAST_UPDATE_DATE">TO_DATE(' 2010-01-11 00:00:00', 'syyyy-mm
-dd hh24:mi:ss') AND
"GLB"."ACTUAL_FLAG"='A')
30 rows selected.

As per the other replies, you've not really given enough information to go on - what are you trying to achieve, versions, etc.
On my old apps 11.5.8 system, the explain plan for your query uses GL_CODE_COMBINATIONS_U1 rather than a full scan of gl_code_combinations.
Check your stats are up to date (select table_name, num_rows, last_analyzed from dba_tables where ...)
See if you can also use period_name and/or period_set_name (or period_num) from GL_Periods rather than period_year (i.e. use P_YEAR to lookup the period_name/period_set_name/period_num from gl_periods). It might be faster to do per period and then consolidate for the whole year, as there are indexes on gl_balances for columns period_name, period_set_name, period_num.
regards, Ivan

GL Tables Partitioning with daily and monthly periods

This implementation(bank) has a requirement for 'daily periods' (01-Jan-2010 ...31-Dec-2010 ) and 'monthly periods' (Jan-2010 ...Dec-2010)
They are also using multiple sets of books, multi-org.
Please advise how to best partition GL tables to best serve those requirements.
Secondly,
Has anybody tried using an on-update trigger on GL_PERIOD_STATUSES to automatically create partition?
if CLOSING_STATUS changes to 'F' or 'O'
and period_name not in dba_tab_partitions
create partition
We plan to use GL_PERIOD_STATUSES because GL_PERIODS.period_name
still changes until the period_name becomes used.
Is there a much better way of doing this?

Thanks for the reply Sandeep.
Banks in our location are regulated by central bank and subject to daily report requirements, therefore the daily periods.
gl_balances and gl_je_lines are the two tables we are looking to partition.
estimated records for daily is around 500K to 1M.

Account Query is taking longtime and not giving desired results

Hi,
I'm trying to run the following query to get code combination id for last six months with 1)no activity in gl_je_lines
2) Sum of begin balance and PTD is zero
Her's query :
select
cc.segment3 SEGMENT
from apps.gl_code_combinations cc,
apps.gl_balances bal,
apps.fnd_flex_values_vl ffvl,
apps.fnd_flex_value_sets ffvs,
(select period_name
from apps.gl_periods
where period_set_name ='abc Calendar'
and to_date(period_name,'Mon-YY') between add_months(sysdate,(6*-1)-1) and sysdate) p
where cc.CODE_COMBINATION_ID = bal.CODE_COMBINATION_ID
and ffvl.FLEX_VALUE = cc.segment3
and ffvl.FLEX_VALUE_SET_ID = ffvs.flex_value_set_id
and ffvs.flex_value_set_id = 2222222
and bal.SET_OF_BOOKS_ID =555
and cc.CHART_OF_ACCOUNTS_ID = 11111
and bal.period_name = p.period_name
and ffvl.ENABLED_FLAG = 'Y'
and ffvl.END_DATE_ACTIVE is null
and bal.TEMPLATE_ID IS NULL
and bal.actual_flag='A'
and bal.currency_code 'STAT'
and ffvl.creation_date <= add_months(sysdate,(6*-1)-1)
and cc.SEGMENT3 not in (
select
distinct gcc.SEGMENT3
from apps.gl_je_lines l
, apps.gl_code_Combinations gcc,
(select period_name
from apps.gl_periods
where period_set_name ='abc Calendar'
and end_date > add_months(last_day(sysdate),-1) and end_date <= last_day(sysdate)) lp
where l.code_combination_id = gcc.code_combination_id
and gcc.CHART_OF_ACCOUNTS_ID = 11111
and l.period_name=lp.period_name
and l.set_of_books_id = 555
and l.status='P')
group by cc.SEGMENT3
HAVING sum(abs(nvl(bal.BEGIN_BALANCE_DR,0))-abs(nvl(bal.BEGIN_BALANCE_CR,0))+abs(nvl(bal.PERIOD_NET_DR,0))-abs(nvl(bal.PERIOD_NET_CR,0))) = 0--------------------------------------------------------------------------------
Here's Explain Plan
Operation Node Cost IO Cost CPU Cost Cardinality Object Name Options Object Type Optimizer
SELECT STATEMENT 5155 5094 554583434 1 ALL_ROWS
FILTER
HASH (GROUP BY) 5155 5094 554583434 1 GROUP BY
FILTER
TABLE ACCESS (BY INDEX ROWID) 4 4 31301 1 GL_BALANCES BY INDEX ROWID TABLE ANALYZED
NESTED LOOPS 18 18 427467 1
MERGE JOIN (CARTESIAN) 14 14 396166 1 CARTESIAN
TABLE ACCESS (BY INDEX ROWID) 4 4 49409 1 GL_CODE_COMBINATIONS BY INDEX ROWID TABLE ANALYZED
NESTED LOOPS 8 8 82677 1
NESTED LOOPS 4 4 33268 1
NESTED LOOPS 4 4 31368 1
INDEX (UNIQUE SCAN) 1 1 8171 1 FND_FLEX_VALUE_SETS_U1 UNIQUE SCAN INDEX (UNIQUE) ANALYZED
TABLE ACCESS (BY INDEX ROWID) 3 3 23196 1 FND_FLEX_VALUES BY INDEX ROWID TABLE ANALYZED
INDEX (RANGE SCAN) 2 2 15293 1 FND_FLEX_VALUES_N3 RANGE SCAN INDEX ANALYZED
INDEX (UNIQUE SCAN) 0 0 1900 1 FND_FLEX_VALUES_TL_U1 UNIQUE SCAN INDEX (UNIQUE) ANALYZED
INDEX (RANGE SCAN) 2 2 33113 4 GL_CODE_COMBINATIONS_N3 RANGE SCAN INDEX ANALYZED
FILTER
TABLE ACCESS (BY INDEX ROWID) 20 20 163416 1 GL_JE_LINES BY INDEX ROWID TABLE ANALYZED
NESTED LOOPS 5136 5076 545022343 1
MERGE JOIN (CARTESIAN) 5103 5043 544739760 4 CARTESIAN
TABLE ACCESS (BY INDEX ROWID) 5 5 37587 1 GL_PERIODS BY INDEX ROWID TABLE ANALYZED
INDEX (RANGE SCAN) 2 2 15043 4 GL_PERIODS_N2 RANGE SCAN INDEX ANALYZED
BUFFER (SORT) 5098 5038 544702173 7 SORT
TABLE ACCESS (FULL) 5098 5038 544702173 7 GL_CODE_COMBINATIONS FULL TABLE ANALYZED
INDEX (RANGE SCAN) 3 3 29414 36 GL_JE_LINES_N1 RANGE SCAN INDEX ANALYZED
BUFFER (SORT) 10 10 346757 1 SORT
INDEX (FULL SCAN) 6 6 313489 1 GL_PERIODS_U1 FULL SCAN INDEX (UNIQUE) ANALYZED
INDEX (RANGE SCAN) 2 2 15493 1 GL_BALANCES_N1 RANGE SCAN INDEX ANALYZEDThis query is taking two hrs to get results :
How to tune this query to get results faster

Hi,
170 posts and still do not know how to use {noformat}{noformat} tags?
Please read <a href="https://forums.oracle.com/forums/thread.jspa?threadID=2174552#9360002">How do I ask a question on the forums?</a>
If you have a performance issue have a look at <a href="https://forums.oracle.com/forums/thread.jspa?threadID=2174552#9360003">How to improve the performance of my query? / My query is running slow. </a>
Additionally when you put some code please enclose it between two lines starting with {noformat}{noformat}
i.e.:
{noformat}{noformat}
SELECT ...
{noformat}{noformat}
Also consider closing some of your questions when someone is answering. Looking at your profile:
Handle:      user518071
Status Level:      Newbie
Registered:      Jun 30, 2006
Total Posts:      170
Total Questions:      92 (58 unresolved) it still looks that you have 58 unresolved questions. Are they really all unresolved?
Regards.
Al

JOURNAL AND BALANCES PURGE 방법

제품 : FIN_GL
작성날짜 : 2003-05-14
JOURNAL AND BALANCES PURGE 방법
=============================
PURPOSE
GL_IMPORT_REFERENCES 테이블의 퍼지를 위해 이 작업이 강력히 권장됩니다
Explanation
goal: How to Archive and Purge Balances and Journal Detail
fact: Oracle General Ledger
fact: GLXSTPRG - Archive and Purge
The period status must be permanently closed to archive and purge account
balances, and journal batches, headers, and lines.
주의사항: 퍼지 앤 아카이브를 위해서는 피리어드가 영구 close되어야합니다.
Budgets can be archived and purged regardless of the period status.
단, 버짓은 그렇지 않습니다.
To Archive the balances
1. Navigate to the Archive and Purge form
The Navigation Path is: Setup>System>Purge
패스는 이렇습니다.
2. Select Balances, Journals, or Translated Balances to be archived.
세 탭 중에서 해당사항을 고릅니다.
3. Check the 'Archive Balances' box
체크를 해야 아카이브가 됩니다.
4. Select the Balance Type to be Actual, Budget, or Encumbrance
For Budgets, choose which Budget to archive.
리스트박스에서 고르고 버짓인 경우 어느 버짓인지 명시합니다.
5. Enter the periods to archive.
기간을 넣습니다.
6. Press the Archive/Purge button
The Archive/Purge process copies account balances from the GL_BALANCES Table to
the GL_ARCHIVE_BALANCES table. For journals, the Archive/Purge process copies
journal details from GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES to
GL_ARCHIVE_BATCHES, GL_ARCHIVE_HEADERS, and GL_ARCHIVE_LINES. Any inported
references on the GL_IMPORT_REFERENCES will be copied to GL_ARCHIVE_REFEENCES.
카피될 테이블 이름들입니다.
7. Review the Archive and Purge Audit report to verify the data was
successfully archived.
확인하시면 됩니다.
8. Export the archive tables, and copy the export files to tape.
테이프나 다른 걸로 백업하실경우입니다.
9. Purge the data.
이후 퍼지방법에 대해 설명합니다. 먼저 아카이브를 했으니 이제 퍼지를
할수 있습니다.
To Purge the balances
1. Navigate to the Archive and Purge form
The Navigation path is Setup>System>Purge
2. Select Balances, Journals, or Translated Balances to be purged.
3. Check the 'Purge Balances' box
요령은 동일합니다.
4. Select the Balance Type to be Actual, Budget, or Encumbrance
For Budgets, choose which Budget to purge
5. Enter the periods to purge.
자동적으로 가장 오래된 이전의 퍼지기록을 보여줍니다.
오래된 순서대로 수행하셔야 합니다.
6. Press the Archive/Purge button
7. Review the Archive and Purge Audit report to verify the data was
successfully purged.
8. Export, drop, and reimport the new tables (GL_BALANCES, BATCHES, HEADERS,
and LINES)to shrink the size of the tables and reclaim lost disk space.
줄어들었는지 확인하시면 됩니다.
Example
Reference Documents
-------------------

unsolved

Opening balance and closing balance on Receivables Customer Statement repor

I need an opening balance and closing balance of the customer statement in one report. Currently I developed a custom Customer statement report in report builder 6i. I developed a custom procedure to retrieve the previous statement balance. I’m able to successfully retrieve ending balance statement with sysdate but if I go back to previous date or previous statement date then I’m not getting the right ending balance of the report.
Even the seeded api arp_customer_aging provides the ending balance for sysdate but not for previous dates because this api always looks back to amount due remaining column(ar_payment_schedules_all).
Did any one ever develop a custom logic to get previous balance and ending balance on one single customer statement?

Hi,
I am working on the same logic. My program loads opening and closing balance and a list of items everyday. The GL_balances table gives you current balance but if you want the previous balance, you have to use : "gl_daily_balances" table and provide accounting_date for which you want the balance.
Hope this Helps!
Yogini

GL_periods and GL_balances

Similar Messages

Maybe you are looking for