on 11-05-2009 6:01 AM
Hi,
We have gone line with SAP ECC for retail scenario recently. Our database is growing 3 GB per day which includes both data and index growth.
Modules configured:
SD (Retail), MM, HR and FI/CO.
COPA is configured for reporting purpose to find article wise sales details per day and COPA summarization has not been done.
Total sales order created per day on an average: 4000
Total line items of sales order on an average per day: 25000
Total purchase order created per day on an avearage: 1000
Please suggest whether database growth of 3 GB per day is normal for this our scenario or should we do something to restrict the database growth.
Fastest Growing tables are,
CE11000 Operating Concern fo
CE31000 Operating Concern fo
ACCTIT Compressed Data from FI/CO Document
BSIS Accounting: Secondary Index for G/L Accounts
GLPCA EC-PCA: Actual Line Items
FAGLFLEXA General Ledger: Actual Line Items
VBFA Sales Document Flow
RFBLG Cluster for accounting document
FAGL_SPLINFO Splittling Information of Open Items
S120 Sales as per receipts
MSEG Document Segment: Article
VBRP Billing Document: Item Data
ACCTCR Compressed Data from FI/CO Document - Currencies
CE41000_ACCT Operating Concern fo
S033 Statistics: Movements for Current Stock (Individual Records)
EDIDS Status Record (IDoc)
CKMI1 Index for Accounting Documents for Article
LIPS SD document: Delivery: Item data
VBOX SD Document: Billing Document: Rebate Index
VBPA Sales Document: Partner
BSAS Accounting: Secondary Index for G/L Accounts (Cleared Items)
BKPF Accounting Document Header
FAGL_SPLINFO_VAL Splitting Information of Open Item Values
VBAP Sales Document: Item Data
KOCLU Cluster for conditions in purchasing and sales
COEP CO Object: Line Items (by Period)
S003 SIS: SalesOrg/DistCh/Division/District/Customer/Product
S124 Customer / article
SRRELROLES Object Relationship Service: Roles
S001 SIS: Customer Statistics
Is there anyway we can reduce the datagrowth without affecting the functionalities configured?
Is COPA summarization configuration will help reducing the size of the FI/CO tables growth?
Regards,
Nalla.
Here are some things I do to stay ahead of the Retail Database growth problem.
1. Once a week I clean IDoc's out of the system by using txn WE11. I retain only 14 days of IDoc's. After all, once they are processed you shouldn't need them anymore. Tables affected - EDI40, EDIDC, EDIDS
2. Run RSCDOK99 weekly to get rid of change documents. Tables - CDHDR, CDPOS
3. Run RSRLDREL weekly to get rid of IDoc links. Tables - IDOCREL, SRRELROLES
4. Run txn SLG2 weekly to get rid of logs found in table BALHDR.
5. Run RVVBSKDL weekly to clear SD table entries. Tables - VBSK, VBSS, VBFS
6. Run RPTEXTPT quarterly to migrate payroll data from temp tables to the permenant tables. Tables - PTEX2000, PTEX2010.
7. You can avoid data in table BSIS. See note 178487. Get with your finance department and convince them of the need. You can also directly delete data.
8. The GLPCA table will grow explosively. Our Finance likes to keep 13 months of active data in the system. I archive the rest using archive object EC_PCA_ITM.
9. Also check SD archiving. It is there you remove delivery and billing documents.
Using these strategies I have kept our Retail data base growth manageable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
We are using ECC6 Unicode with Windows Server 2003 SP1 and SQL 2005 SP2 on Itanium Server.
We had live on 1st August 2007 with all core modules including COPA
We have same volume of Sales Order, Purchase Orderand Line items, but our DB are gorwing 10GB per month.
You can refer to blow BSIS Table which show the table size history of year which raised 5GB in 1 year.
Per day 0 0
BSIS 11.11.2009 13,462,793 12,430,120
BSIS 10.11.2009 13,462,793 12,430,120
BSIS 09.11.2009 13,462,793 12,430,120
BSIS 08.11.2009 13,462,793 12,430,120
BSIS 07.11.2009 13,462,793 12,430,120
BSIS 06.11.2009 12,979,203 11,858,336
BSIS 05.11.2009 12,979,203 11,858,336
Per week 0 0
BSIS 08.11.2009 13,462,793 12,430,120
BSIS 01.11.2009 12,979,203 11,858,336
BSIS 25.10.2009 12,979,203 11,858,336
BSIS 18.10.2009 12,979,203 11,858,336
BSIS 11.10.2009 12,979,203 11,858,336
Per month 0 0
BSIS 01.11.2009 12,979,203 11,858,336
BSIS 01.10.2009 12,979,203 11,858,336
BSIS 01.09.2009 12,423,476 11,195,200
BSIS 01.08.2009 12,423,476 11,195,200
BSIS 01.07.2009 11,810,650 10,510,304
BSIS 01.06.2009 11,109,973 9,754,264
BSIS 01.05.2009 11,109,973 9,754,264
BSIS 01.04.2009 10,454,887 9,046,648
BSIS 01.03.2009 9,809,423 8,380,984
BSIS 01.02.2009 9,809,423 8,380,984
BSIS 01.01.2009 9,017,450 7,802,072
BSIS 01.12.2008 9,017,450 7,802,072
BSIS 01.11.2008 8,406,762 7,280,784
Regards
SAP NetWeaver
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> We have gone line with SAP ECC for retail scenario recently. Our database is growing 3 GB per day which includes both data and index growth.
Those numbers are not uncommon.
We run ERP 6.0 without Retail and have much less orders and line items but also growing 2 -4 GB/day. We use all the major modules in the system.
Do you use SQL Server 2008? You can use row or page compression which reduces the amount of storage needed.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.