Back end activities for Activation & Deactivation of Aggregates

Hi ,
Could any body help me to understand the back-end activites performed at the time of activation and deactivation of aggregates.
Is filling of Agreegate is same as Roll up?
What is the diffrence between de-activation and deletion of Aggregate?
Thanks.
Santanu

Hi Bose,
Activation:
In order to use an aggregate in the first place, it must be defined activated and filled.When you activate it, the required tables are created in the database from theaggregate definition. Technically speaking, an aggregate is actually a separate BasicCube with its own fact table and dimension tables. Dimension tables that agree with the InfoCube are used together. Upon creation, every aggregate is given a six-digit number that starts with the figure1. The table names that make up the logical object that is the aggregate are then derived in a similar manner, as are the table names of an InfoCube. For example, if the aggregate has the technical name 100001, the fact tables are called: /BIC/E100001 and /BIC/F100001. Its dimensions, which are not the same as those in the InfoCube,have the table names /BIC/D100001P, /BIC/D100001T and so on.
Rollup:
New data packets / requests that are loaded into the InfoCube cannot be used at first for reporting if there are aggregates that are already filled. The new packets must first be written to the aggregates by a so-called “roll-up”. In other words, data that has been recently loaded into an InfoCube is not visible for reporting, from the InfoCube or aggregates, until an aggregate roll-up takes place. During this process you can continue to report using the data that existed prior to the recent data load. The new data is only displayed by queries that are executed after a successful roll-up.
Go for the below link for more information.
http://sapbibw2010.blogspot.in/2010/10/aggregates.html
Naresh

Similar Messages

BI Front end & Back end Activities

Hi BW/BI gurus,
Can some one enlighten me what are the front end & back end activities to be highlighted for taking a BW/BI Consultants position/interview in the US.
Regards
Chandu

Hi,
I think you are asking about the Roles and responsibilities of a
BW consultant. It differs based on the project (support, implementation, upgrade, etc)
BW_ROLES_SKILLS
http://help.sap.com/bp_biv335/BI_EN/documentation/BW_ROLES_SKILLS.doc
Roles and Responsibilities of SAP BW Consultant
production support
https://forums.sdn.sap.com/click.jspa?searchID=10063267&messageID=3785914
Role of Developer in Implementation
BI Technical/functional
Hope this helps.
Thanks,
JituK

Define Logical Port and Back-End Destinations for ESOA use of this config

Hi,
Please let me know what is the use of this config I am not able to get a documentation.
Define Logical Port and Back-End Destinations for ESOA

Hi Autobots,
Even I am looking for the same information. Did u get some headstart into the matter?
Pl provide me with the inputs too.
Cheers
Nikhil

What r the month end activites for a consultant which enduser cannot do?

Hi all
what r the month end activites for a consultant which enduser cannot do?
thanks to all plz respond me

Hi,
NIL
All activities should be assigned to an enduser based on the organisation of the company.
regards

Help for activating & deactivating a window.

Here beelow, I have written the code.
Asper the code, I have created window1, that has a button "ok",clicking "ok", window2 appears.window2 has a "close" button.
So, the no. of times, I click the button "ok", the same no. of instances of window2 appears.But, I want after clicking the button "ok" in window1, window1 should be deactivated,and after clicking window2's "close" button, then window1 should be activated again.It means,only one instance of window2 should be visible,clicking the "ok" button.
If anybody has idea about this, please write me the updated version of the code given bellow.
Regards.
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class window1 extends JFrame
JButton b;
window1()
Container con=getContentPane();
addWindowListener(new WindowAdapter(){
public void windowClosing(WindowEvent e)
System.exit(0);
JPanel p1=new JPanel();
b=new JButton("ok");
b.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent e)
if(e.getSource()==b)
new window2();
p1.add(b);
con.add(p1,BorderLayout.SOUTH);
setSize(200,150);
setVisible(true);
public static void main(String arg[])
window1 obj=new window1();
class window2 extends JFrame
JButton b2;
window2()
Container con=getContentPane();
JPanel p2=new JPanel();
b2=new JButton("close");
b2.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent e){
if(e.getSource()==b2)
dispose();
p2.add(b2);
con.add(p2, BorderLayout.SOUTH);
setSize(200,150);
setVisible(true);

A.
Keep the instance of the Window1 as global to the class.
e.g.
private window1 myWindow;
B.
In the constructor assign to the instance.
public window1 () {
myWindow = this;
C.
On click of "ok" set
myWindow.setVisible(false);
or
myWindow.setEnabled(false);
D.
In your window2's close button call the myWindow.setVisible (true) or myWindow.setEnabled (true)
I assume you have both the windows declared in one file.
Chintan

Changing the ABAP Back-End System for the UME

Hi,
I went through many forums; sap notes (943498, 764417, 943602, 940893, 810434) and at help.sap.com
(http://help.sap.com/saphelp_nw70/helpdata/en/9e/fdcf3d4f902d10e10000000a114084/frameset.htm)
I am not able to resolve the issue.
Problem: We already have SSO configured between Portal (EP7) and backend R/3 system (ECC 6) which is working fine. Scenario is that we have dual maintenance system going on. Now we want to move our SSO configuration for Portal to point to new R/3 system, which is exactly same except different server name (same SID, system #, using same ports on different servers). Here is the catch service file for both R/3 system have same service name and port number defined.
R/3 current: sapmsXXX    3601/tcp
R/3 new sys: sapmsXXX     3601/tcp
Will this be causing hte problem or could be something else.
Thank in advance for your inputs!!
Error from the dev_server0 file:
[Thr 172] Fri Mar 28 14:10:19 2008
[Thr 172] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 172] Fri Mar 28 14:10:20 2008
[Thr 172] ***LOG Q0I=> NiPConnect2: connect (146: Connection refused) [nixxi.cpp 2770]
[Thr 172] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 46
(SI_ECONN_REFUSE/146; I4; ST; 156.44.162.55:3601) [nixxi.cpp    2770]
[Thr 172] *** ERROR => MsIAttachEx: NiBufConnect to server.name/sapmsXXX failed (rc=NIECONN_REFUSED) [msxxi_mt.c   652]
[Thr 172] *** ERROR => LgIAttach: MsAttach (rc=NIECONN_REFUSED) [lgxx_mt.c    3980]
[Thr 172] *** ERROR => LgIGroupX: LgIAttach(rc=-101) [lgxx_mt.c    4284]
[Thr 172] *** ERROR => JRFC> Error jrfc_lg LgGroup failed(-101) [jrfclg_mt.c 344]
[Thr 172] *** ERROR =>       mshost: server.name, msserv: sapmsXXX, r_group: BASIS [jrfclg_mt.c 345]
[Thr 14] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 14]
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes
for additional information and trouble shooting.
[Thr 14] SigISetIgnoreAction : SIG_IGN for signal 18
[Thr 14] JLaunchCloseProgram: good bye (exitcode = -11113)

Hi Patel,
It seems that the portal cannot attach backend system via load balancing.
1- Can you access to port# 3601 on 156.44.162.55 via telnet, from your portal system?
2- Did you checked your firewall settings on both systems?
Best regards,

Value for customized fields didn't get copied to back end system

Hi,
We are in SRM 4.0 and using extended classic scenario.
We have defined two customized fields in account assignment tab in shopping cart and SRM Po and also in back end PO.
SRM POs are having values for the field but while transferring the Po details to back end system, for some of the line items of the Po the entries are missing in back end system.
Problem is only with few line items of the PO.
Have tried with FM like BBP_PD_PO_TRANSFER_EXEC and BBP_PD_SC_RESUBMIT, but it is not transfering the values to back end.
Is there any other way to push the missing values to back end system.
Please advise.
Thanks.

Sk,
Table adjustment has to be done accordingly. Get in touch with your Basis team.
Thanks.

How to find out back end mapping program for Idoc ?

HI Experts,
Iam new to ALE IIDOCS .. i have a issue in existing idoc .
Some data maping problem is there in the existing idocs
I need to find out back end program for this perticular idoc no .
Exactly where they have written the maping code .
How to find out this ?
is there any preceedure to trace the back end program based on the idoc number .
Regards
RameshG

Hi Ramesh,
If you are looking at Inbound que then we generally double click on idoc go to control datat info and then take partner data info there
Goto we20 check teh system and there double click the message type and there in inbound option double clik the porcess code it gives you one FM where you can see logic written to process that IDOC
Regards,
Poornima

What are the year end and month end activities carried in FI?

Hi all,
I am new to FI, what is the steps or the activites/process to be carried out during the month end as well as the year end activities for FI.
Can anyone explain me about it and does sap provide any standard documentation on year end / month end activities.
Thanks
Pooja

Hi Pooja,
Please find the details below
Month end closing Activities
1. All the expenses including amortization, prepaid expenses, Preliminary expenses and accruals have been booked.
2. Complete Bank Reconciliation (T. Code: FF67)
3. Make sure that Sum of Inter Company balances is Zero
4. Suspense Accounts should be cleared regularly.
5. Ensure that all documents related to MM & SD have been entered in system. (T.Code:F-22 & F-43) 6. Ensure that all billing documents are released to accounting.
7. Calculate Overheads on all process Orders (CO43)
8. Technically complete all process orders which are fully processed (CORM).
9. Calculate Variance (KKS1)à (Relevant only if Standard cost is calculated).
10. Settle all process orders which are technically complete (CO88).
11. Close All settled Process Orders
12. Close MM period (Transaction Code: MMPV).
13. Carry out GR/IR clearing (F.13) transaction
14. Depreciation Run (AFAB) has been carried out for the month
15. Close FI Posting period after the month end closing activity is over (T.Code:OB52) Year end
Closing Activities:
1. Calculate production work in progress on process orders which are not technically complete. (CO88).
2. Carry out Assessment cycle for Cost Centers (T. Code: KSUB)
3. All month end closing Activities should be carried out.
4. Carry Forward Balances to next year With TC: F.16 we can carry forward the balance to next year. With TC: OBH2 copy the number ranges to next year Open next year periods by selecting the Posting Period Variant. then test by posting the transaction in F-02)
SAP FI Month End and Year End Activities
1 - Maintain Activity prices - KP26
2 - Release of Standard Cost Estimate - CK40N
3 - MM period close and open - MMPV
4 - FI period open
5 - Parked documents to be posted - FBV0, MIRO
6 - Reposting of Inter Office CC - KB61
7 - Bank Reconciliation
8 - Update Section Code where missing - J1INPP
9 - Maintain GRIR clearing - F.13
10 - Provision for current month - FB50
11 - Depreciation entry - FB50
12 - Exchange rate - To be Updated
13 - Revaluation of foreign currency open items - F.05
14 - Recognition of Inventory at Bonded warehouse - FB50
15 - Maintain Statistical Key Figures - KB31N/KP46
16 - Variance Calculation of Process Orders - KKS1
17 - Settlement of variances - CO88
18 - Assessment cycles - Aux/WH CC to Main CC - KSU5
19 - Assessment cycles - Functional CC to SBU CC - KSU5
20 - Assessment cycles - SBU CC to COPA - KEU5
21 - Profit Center Reposting - 9KE0
22 - Balance Sheet Adjustment calculation - F.5D
23 - Transfer Profit Center to AR & AP - 1KEK
24 - Transfer Inventory to PCA - 1KEH
25 - Assessment Cycle - Dummy PC to SBU PC - 3KE5
26 - Check for u201CDelivery made, not Invoicedu201D - VF03
27 - Match GL and PCA - KE5T
28 - Match PCA and PA
29 - Top Down Distribution in COPA - KE28
30 - Reclassification of GL balances
31 - Balance Carry forward (Year End Only) - F.16
32 - PCA Balance Carry forward (Year End Only) - 2KES
33 - Transfer to FI - 1KE8
Regards,
JA

Period end closing for production orders

Dear all,
what is period end closing???
Pl. enlist all period end activities for product costing by order scenario.
what inventory adjustments are necessory.
what FI entries required to post??

With respect to PP- Period end closing is the procedure to close all the production orders and see that cost is flowing from production order to material
During period end - we TECO all the orders and see that production is complete from PP angle. Then costing will calculate over head/variance and settle the difference to production material or price difference a/c depending on the production material price control.
Just see below the example of a production and costing entries. Thi8s may be helpful to understand the concept.
Planned price
Planned Material cost = 115.15USD
Planned Activity cost = 6 USD
Planned Over head = 25% of material cost+ 250% of activity cost = 28.79+15=43.79
Total cost = 164.94
Product cost as per S price = 1 USD (example)
After GR and confirmation
Actual Material cost = 7456.55 USD
Actual Activity cost = 2USD
Total cost = 7458.55
Actual O/H = 0
Production variance = 7293.61 USD
After o/h calculation
Actual Material cost = 7456.55 USD
Actual Activity cost = 2USD
Actual O/H = 25% of material cost+ 250% of activity cost = 1869.138
Total cost = 9327.69
Production variance = 9162.75
After settlement
Actual Material cost = 7456.55 USD
Actual Activity cost = 2USD
Actual O/H = 25% of material cost+ 250% of activity cost = 1869.138
Total cost = 9327.69
Production variance = 0
Variance will be settled to Price difference a/c.
When we do the GR the FI a/c will hit as below
Production order expense a/c -
stock a/c +
When we GI the following a/c will hit
Raw material a/c -
Production order expense a/c +
When we settle
Production order expense a/c + or -ve
variance a/c = + or -ve
I hope this will help you.

CO month end or year end activities

Hi All,
Kindly brief me for what are the CO month end and year end activites?
My mail id is:[email protected]
Thanks in advance.
Soma

Hi,
Please find the list of year ending activities for FI and CO as below:
CLOSING ACTIVITIES
1 Execute Report for Inter Company Activity & Journal Entries
2 Open posting period for next yr (T.Code: OB52)
3 Run Business Area's Assignment report. (T.Code: F.50)
4 Review list of recurring journal entries (T.Code: FBD3)
5 Execute Recurring Entries for A/R, A/P, G/L (T. Code: F.14)
6 Process Parked A/R, A/P, G/L accounting documents (T.Code: FBV0)
7 Final Cutoff for the Maintenance of Fixed Asset- Add Transfer and Retire (T.Code: ABUMN)
8 Run Depreciation in Test Run and post (T.Code: AFAB)
9 Verify Display Log for Depreciation Test Run (T.Code: AFBP)
10 Capitalize AUC Assets if needed (T.Code: AIAB, AIBU)
11 Enter Payroll Data to SAP (T.Code: CAT2)
12 Verify Depreciation Balances with GL balances (T.Code: ABST2)
13 Post Depreciation (T.Code: AFAB)
14 Execute Asset History Report, and retire assets if needed (T.Code: S_ALR_87011963, ABAVN)
15 Adjust specific depreciation areas if necessary (T.Code: ABCO)
16 Reconcile AM sub ledger with GL (T.Code: ABST2)
17 Check Bank Data (T.Code: S_P99_41000212)
18 Review AR Open Items (T.Code: FBL5N)
19 Review AP Open Items (FBL1N)
20 Execute Pending Invoices(T.Code: MRBP)
21 Clear Open Item for GRIR, freight (T.Code: F.13)
22 Reconciliation of Financial Documents and transactional figures (F.03)
23 Open new CO Posting Period: (T.Code: OKP1)
24 Compare current (cost estimates) with last current price (Moving Avg) (T.Code: OKBH)
25 Update current cost price to material master price field (T.Code: CK11N, CK24)
26 Process Freight charges, Match SD freight to actual (T.Code: V-31)
27 Review Internal Order Postings(T.Code: OKSA)
28 Settle All Orders (T.Code: KO88)
29 Verify All Post Goods Issue have been Invoiced (Billing Due List) (T.Code: VF04)
30 Review SD Billing Doc from prior month that have not yet been released to accounting (T.Code: F.2D)
31 Reconciliation of MM movements in Transit Intra-SAP to Non SAP
32 Reconcile PI Inventory with SAP (T.Code: MI07)
33 Perform Manual Adjustment if needed (T.Code: F-02, FB50)
34 Verify balance of the GR/IR account (T.Code: MB5S)
35 Post Accruals and Deferrals (T.Code: FBS1)
36 Clearing of Cancelled Documents (T.Code: F-03, F-32, F-44)
37 Check Profitability Segment Adjustment (T.Code: KISR)
38 Aging Report-Reconcile GL balances with sub ledger balances AP (T.code: FBL1N, FBL5N, FBL3N)
39 Check the check run numbers (T.Code: FCH1, FCHI)
40 Bank reconciliation Data (T.Code: FF67 & FEBA)
41 Enter Tax Journal Entry (T.Code: FB41)
42 Reconcile GL balances with sub ledger balances AR/MM/AP (T.Code: F.03)
43 Display Balance Sheet Adjustments (T.Code: F.5F)
44 Post Balance Sheet Adjustments (T.Code: F.5E)
45 Post Foreign Currency Valuation (foreign exchange) (T.Code: F.05)
46 Check generic cost centers for posting with wrong accounts
47 Correct wrong postings on generic cost centers
48 Check Validation dates for Cost Centers, Cost Elements, CO area (T.Code: GGB0)
49 Check COGI--for both month end and year end
50 Doubtful receivables (T.Code: F104)
51 Verify In-transit Inventory
52 Reconcile PA to G/L (T.Code: KE5U)
53 Post Cost Center Assessments and Distributions (T.Code: KSU5 & KSV5)
54 Run CO-FI Reconciliation to balance (T.Code: KALC)
55 Run BW reports P&L and Balance Sheet
56 Maintain CO yr variant (T.Code: KCRQ)
57 Fiscal Yr Balance carry forward AP/AR/AM (T.Code: F.07,
58 Fiscal Yr Balance carry forward CO (T.Code: CXS1)
59 Fiscal Yr balance carry forward FI (T.Code: F.16)
60 Fiscal Yr balance carry forward PCA (T.Code: 2KES)
61 Set Document number ranges - FI - new year (T.Code: OBH2, OBA7)
62 Set Document number ranges AP/AR - new year (OBA7)
63 Generate Financial statement Reports (T.Code:OB58) OR (T.Code: FSE2)
64 Change Fiscal Year For Assets (T.Code: AJRW)
65 Year end Closing-- Asset Accounting--final for year end (T.Code: AJAB)
66 Close CO Posting Period : (T.Code: OKP1)
67 Close Prior A/R Posting Period (T.Code: OB52)
68 Close Prior A/P Posting Period (T.Code: OB52)
69 Close Prior MM Posting Period (T.Code: OMSY)
70 Reverse accruals and deferrals for the new month (T.Code: F.81)
71 Reconciliation of Financial Documents from old fiscal year and new fiscal year (T.Code: FNSL)
72 Load Balances, Budget Data for Cost centers, sales
73 Update Retained Earning Account , balance carry fwd (T.Code: F.16)
Month end closing Activities
1. All the expenses including amortization, prepaid expenses, Preliminary expenses and accruals have been booked.
2. Complete Bank Reconciliation (T.Code: FF67)
3. Make sure that Sum of Inter company balances is Zero
4. Suspense Accounts should be cleared regularly.
5. Ensure that all documents related to MM & SD have been entered in system. (T.Code:F-22 & F-43)
6. Ensure that all billing documents are released to accounting.
7. Calculate Overheads on all process Orders (CO43)
8. Technically complete all process orders which are fully processed (CORM).
9. Calculate Variance (KKS1)à (Relevant only if Standard cost is calculated).
10. Settle all process orders which are technically complete (CO88).
11. Close All settled Process Orders
12. Close MM period (Transaction Code: MMPV).
13. Carry out GR/IR clearing (F.13) transaction
14. Depreciation Run (AFAB) has been carried out for the month
15. Close FI Posting period after the month end closing activity is over (T.Code:OB52)
Year end closing Activities:
1. Calculate production work in progress on process orders which are not technically complete. (CO88).
2. Carry out Assessment cycle for Cost Centers.(T.Code: KSUB)
3. All month end closing Activities should be carried out.
4. Carry Forward Balances to next year
(With TC: F.16 we can carry forward the balance to next year.
With TC: OBH2 copy the number ranges to next year
Open next year periods by selecting the Posting Period Variant.
then test by posting the transaction in F-02)
all the best

FI Year end activities - Step by step - Urgent

Hi Guru,
Please forward the year end closing activities.If possible give step by step details with t-code also.Thanks in Advance.
my email id is
[email protected]
pls send soon since it is very urgent
Points will be awarded

Please find the list of year ending activities for FI and CO as below:
CLOSING ACTIVITIES
1 Execute Report for Inter Company Activity & Journal Entries
2 Open posting period for next yr (T.Code: OB52)
3 Run Business Area's Assignment report. (T.Code: F.50)
4 Review list of recurring journal entries (T.Code: FBD3)
5 Execute Recurring Entries for A/R, A/P, G/L (T. Code: F.14)
6 Process Parked A/R, A/P, G/L accounting documents (T.Code: FBV0)
7 Final Cutoff for the Maintenance of Fixed Asset- Add Transfer and Retire (T.Code: ABUMN)
8 Run Depreciation in Test Run and post (T.Code: AFAB)
9 Verify Display Log for Depreciation Test Run (T.Code: AFBP)
10 Capitalize AUC Assets if needed (T.Code: AIAB, AIBU)
11 Enter Payroll Data to SAP (T.Code: CAT2)
12 Verify Depreciation Balances with GL balances (T.Code: ABST2)
13 Post Depreciation (T.Code: AFAB)
14 Execute Asset History Report, and retire assets if needed (T.Code: S_ALR_87011963, ABAVN)
15 Adjust specific depreciation areas if necessary (T.Code: ABCO)
16 Reconcile AM sub ledger with GL (T.Code: ABST2)
17 Check Bank Data (T.Code: S_P99_41000212)
18 Review AR Open Items (T.Code: FBL5N)
19 Review AP Open Items (FBL1N)
20 Execute Pending Invoices(T.Code: MRBP)
21 Clear Open Item for GRIR, freight (T.Code: F.13)
22 Reconciliation of Financial Documents and transactional figures (F.03)
23 Open new CO Posting Period: (T.Code: OKP1)
24 Compare current (cost estimates) with last current price (Moving Avg) (T.Code: OKBH)
25 Update current cost price to material master price field (T.Code: CK11N, CK24)
26 Process Freight charges, Match SD freight to actual (T.Code: V-31)
27 Review Internal Order Postings(T.Code: OKSA)
28 Settle All Orders (T.Code: KO88)
29 Verify All Post Goods Issue have been Invoiced (Billing Due List) (T.Code: VF04)
30 Review SD Billing Doc from prior month that have not yet been released to accounting (T.Code: F.2D)
31 Reconciliation of MM movements in Transit Intra-SAP to Non SAP
32 Reconcile PI Inventory with SAP (T.Code: MI07)
33 Perform Manual Adjustment if needed (T.Code: F-02, FB50)
34 Verify balance of the GR/IR account (T.Code: MB5S)
35 Post Accruals and Deferrals (T.Code: FBS1)
36 Clearing of Cancelled Documents (T.Code: F-03, F-32, F-44)
37 Check Profitability Segment Adjustment (T.Code: KISR)
38 Aging Report-Reconcile GL balances with sub ledger balances AP (T.code: FBL1N, FBL5N, FBL3N)
39 Check the check run numbers (T.Code: FCH1, FCHI)
40 Bank reconciliation Data (T.Code: FF67 & FEBA)
41 Enter Tax Journal Entry (T.Code: FB41)
42 Reconcile GL balances with sub ledger balances AR/MM/AP (T.Code: F.03)
43 Display Balance Sheet Adjustments (T.Code: F.5F)
44 Post Balance Sheet Adjustments (T.Code: F.5E)
45 Post Foreign Currency Valuation (foreign exchange) (T.Code: F.05)
46 Check generic cost centers for posting with wrong accounts
47 Correct wrong postings on generic cost centers
48 Check Validation dates for Cost Centers, Cost Elements, CO area (T.Code: GGB0)
49 Check COGI--for both month end and year end
50 Doubtful receivables (T.Code: F104)
51 Verify In-transit Inventory
52 Reconcile PA to G/L (T.Code: KE5U)
53 Post Cost Center Assessments and Distributions (T.Code: KSU5 & KSV5)
54 Run CO-FI Reconciliation to balance (T.Code: KALC)
55 Run BW reports P&L and Balance Sheet
56 Maintain CO yr variant (T.Code: KCRQ)
57 Fiscal Yr Balance carry forward AP/AR/AM (T.Code: F.07,
58 Fiscal Yr Balance carry forward CO (T.Code: CXS1)
59 Fiscal Yr balance carry forward FI (T.Code: F.16)
60 Fiscal Yr balance carry forward PCA (T.Code: 2KES)
61 Set Document number ranges - FI - new year (T.Code: OBH2, OBA7)
62 Set Document number ranges AP/AR - new year (OBA7)
63 Generate Financial statement Reports (T.Code:OB58) OR (T.Code: FSE2)
64 Change Fiscal Year For Assets (T.Code: AJRW)
65 Year end Closing-- Asset Accounting--final for year end (T.Code: AJAB)
66 Close CO Posting Period : (T.Code: OKP1)
67 Close Prior A/R Posting Period (T.Code: OB52)
68 Close Prior A/P Posting Period (T.Code: OB52)
69 Close Prior MM Posting Period (T.Code: OMSY)
70 Reverse accruals and deferrals for the new month (T.Code: F.81)
71 Reconciliation of Financial Documents from old fiscal year and new fiscal year (T.Code: FNSL)
72 Load Balances, Budget Data for Cost centers, sales
73 Update Retained Earning Account , balance carry fwd (T.Code: F.16)
thanks
sejal

Front-end/back-end cluster question

[att1.html]


Patrick Power wrote:
          > Thanx for your reply Prasad. I was surprised none of the Bea engineers
          > wished to touch this one. What do you suppose is up with that? Either
          > they are too busy, or possibly my question is too dumb.
          >
          I am from BEA so its not that we are not responding ;).
          >
          > Back to the issue: Yes, we will NES bridge/proxy into servlet front-end
          > cluster, potentially with Directors on the very front of the topology for
          > balancing. Your diagram as such:
          >
          > <Netscape/IIS/Apache/WLS FRONT END> ----- <CLUSTER OF WEBLOGIC SERVER
          > > SERVING SERVLETS> --- <CLUSTER OF WEBLOGIC SERVERS SERVING EJB>
          >
          > 1) Does <Netscape/IIS/Apache/WLS FRONT END> mean NES with proxy shared lib,
          > with a WLS service definition into cluster in obj.conf? I assume yes.
          Yes.
          >
          > 2) I would assume that <CLUSTER OF WEBLOGIC SERVERS SERVING SERVLETS> would
          > need the WLS HttpClusterServlet to the <CLUSTER OF WEBLOGIC SERVERS SERVING
          > EJB> all the way in the back.
          No. I was splitting presentation logic (namely servlets and jsp) and business
          logic (ejb) into two layers. Again you don't have to split it into two. You can
          colocate them both together. You could use NES or IIS or Apache or WLS. You
          don't need HttpClusterServlet.
          Lets get this straight.
          1. You need our proxy plugin for failover and to load balance the request that
          are going to presentation logic.
          2. From presentation logic layer, when you talk to backend business logic
          providers (like ejb cluster), if you use stateless session beans we provide
          failover and load balancing. In future we will support clustered stateful
          session beans as well. Therefore you don't need load balancer here.
          3. HttpClusterServlet should run only in front of presentation logic cluster and
          also it supports http only.
          Hope this helps.
          - Prasad
          > The NES proxy would only proxy into the f/e
          > cluster, right? You're not suggesting an external proxy of some type, are
          > you? The HttpClusterServlet is for WLS cluster-to-cluster proxies.
          > 3) A load balancer between the wls f/e and wls b/e clusters? That doesn't
          > seem applicable here. Once again, it should be HttpClusterServlet for WLS
          > cluster-to-cluster proxies.
          > 4) "use two or three proxy servers to avoid single point of failure."
          > Hmmm, once again - are we talking the WLS HttpClusterServlet proxy? Well,
          > that's the inital question: Can I have more than one HttpClusterServlet
          > proxy in the front-end cluster, proxying to the back-end cluster?
          > Otherwise, internally from this WLS architecture perspective, it is a single
          > point of failure.
          >
          > An example: 10 instances in f/e cluster. can more than one of these
          > instances have the WLS HttpClusterServlet proxy to the b/e cluster? Or, are
          > there instances of WLS HttpClusterServlet proxy in all 10 f/e cluster
          > instances?
          >
          > Cheers, Pat
          >
          > Prasad Peddada <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > >
          > > Patrick Power wrote:
          > >
          > > > I know that this topic was addressed to some degree here in an earlier
          > > > posting, but I still have a question regarding the architecture
          > > > design:
          > > >
          > > > If configuring a front-end cluster for servlets/sessions and a
          > > > back-end cluster for remote services -- you route requests to the
          > > > back-end using the WLS proxy servlet. ok, got that part.
          > >
          > > Not quite. The typical scenario is
          > >
          > > <Netscape/IIS/Apache/WLS FRONT END> ----- <CLUSTER OF WEBLOGIC SERVER
          > > SERVING SERVLETS> --- <CLUSTER OF WEBLOGIC SERVERS SERVING EJB>
          > >
          > > You don't proxy and serve servlets from the same server.
          > >
          > > >
          > > > The question: Is there a single instance of the wls proxy servlet in
          > > > the front-end cluster? Or, is it on every instance in the front-end
          > > > cluster? What is the failover mechanism, in the case of a single
          > > > instance of proxy servlet in the f-e cluster failing?
          > >
          > > To prevent that you need to use some kind of h/w or software load
          > > balancer and then use two or three proxy servers to avoid single point
          > > of failure.
          > >
          > > > Is it a single point of failure between the 2 clusters?
          > > >
          > > > Thanx in advance for your help.
          > > >
          > > > BTW, I think Wei, Kumar and the other Bea folks cruising this group
          > > > have been doing a bang-up job of providing badly-needed detail on this
          > > > subject area - material this largely absent from the documentation.
          > > > Good job.
          > > >
          > > >
          > >
          > > --
          > > Cheers
          > >
          > > - Prasad
          > >
          > >

For direct activation of hierarchy, Aggregates have to be deactivated

Hi,
There are 2 monthly master data hierarchies loaded.
We face some problem while loading the hierarchies.
Now the 2 hierarchies are seen as Modified version.
When I try to activate the hierarchies manually I receive the below message
"For direct activation of hierarchy, 0042 Aggregates have to be deactivated"
with 2 options as:
1 Prebook activation
2 Activate directly
What are these options?
Will affect on aggregates?

hi,
Activate directly wlll directly activate the hierarchy....
Prebook for activation will capture it and it will be activated later at the time of the chnage run.
Always prefer Prebook for activation...
hope this helps.
regards,
Mahesh
Edited by: Mony Maheshsingh on Jun 24, 2010 4:22 PM

Back up plan for Asset year end closing

Hi,
Do you have any back plan prepared for Asset year end closing especially t.code AJRW and AJAB (running this in Background).
what back up plan we should recommend if it fails for already happened activities.
Regards
Shanu

Hi Shanu,
there is a Test-run modus.
If it fails for some reasons, you will get a error message. Then you solve this error and repeat AJRW or AJAB.
regards Bernhard

Back end activities for Activation & Deactivation of Aggregates

Similar Messages

Maybe you are looking for