Split tables for DMO

I am preparing to use DMO to upgrade/convert an Oracle/Unix based BW7.1 to Bw7.4 at Hana/SUSE.
Some tables are very big so that I plan to split them.
However, the DMO document does not show the step where the table-split can be configured.
Could you please share you experience on how to do this?
Thanks!!

Hi, Boris,
We have many large tables, all greater than 100GB, but DMO only choose 3 large and 9 small tables to split. this leads to we wait for large table running at the end phase.
Could you share us what the logic is for dmo to split table ?
3 ETQ399 Looking for tables to be split:
4 ETQ399 /BIC/AZI_BLS0100               size   358470/ 358470 MB split with segment size 0.500000
4 ETQ399 /BIC/B0004785000               size   349106/ 349106 MB split with segment size 0.500000
4 ETQ399 /BIC/AZFIGLO0200               size   300177/ 300177 MB split with segment size 0.500000
4 ETQ399 RSBATCHDATA                    size    50614/   25307 MB split with segment size 0.267057 (has 1 blobs)
4 ETQ399 RSZWOBJ                        size     9406/    4703 MB split with segment size 0.500000 (has 1 blobs)
4 ETQ399 ARFCSDATA                      size    25138/   25138 MB split with segment size 0.268852
4 ETQ399 RSBMREQ_DTP                    size    25147/   25147 MB split with segment size 0.268756
4 ETQ399 RSBMONMESS_DTP                 size    22417/   22417 MB split with segment size 0.301485
4 ETQ399 RSBMLOGPAR_DTP                 size    14525/   14525 MB split with segment size 0.465294
4 ETQ399 RSODSACTDATA                   size     7244/    3622 MB split with segment size 0.500000 (has 1 blobs)
4 ETQ399 RSSELDONE                      size     6798/    6798 MB split with segment size 0.500000
4 ETQ399 BDLDATCOL                      size     9882/    4941 MB split with segment size 0.500000 (has 1 blobs)
3 ETQ399 Identified 12 large tables out of 52282 entries.

Similar Messages

Tables for vendor invoice and payment

Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.

There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation

Logic to retrieve batch number in batch split scenario for a material

Hi All!
LIPS-CHARG gives the batch number for a material in normal scenario.But in batch split scenario for a material what should be the logic to retrieve the field batch number based on POSNR,VBELN and UECHA in LIPS.
UECHA corresponds to higher level item of a batch.
I had been given the following logic to do the same but it is not pulling any values inspite of a batch split available for the material.The logic is
Select lips-charg (batch number) where lips-posnr = lips-uecha ( higher level item batch)
Please advise
Regards
Praneeth

Hi Praneeth,
The way LIPS records are in a batch split scenario is that let us say you have a delivery with one line item 00010. Now if this splits into two batch split items, then you will find in LIPS 3 records, one with line item 00010, one with 90001 and another with 90002. Both 90001 and 90002 will have a UECHA of 00010, whereas for 00010, this field will be blank. So the logic is to create two internal tables one where UECHA is blank and another where it is not blank and use it.
SELECT * FROM LIPS
         INTO TABLE I_LIPS
        WHERE VBELN = P_VBLEN.
I_LIPS_TEMP[] = I_LIPS[].
DELETE I_LIPS_TEMP WHERE UECHA IS INITIAL.
*-- This table will not have only the batch split items not the main items.
LOOP AT I_LIPS WHERE UECHA IS INITIAL.
*-- loop at the main items.
IF I_LIPS-CHARG IS INITIAL.
*-- batch is not there on the main item, see if it is there on any batch split items.
    READ TABLE I_LIPS_TEMP WITH KEY UECHA = I_LIPS-POSNR.
     do whatever
ENDIF.
..... do whatever
ENDLOOP.

Slow split table export (R3load and WHERE clause)

For our split table exports, we used custom coded WHERE clauses. (Basically adding additional columns to the R3ta default column to take advantage of existing indexes).
The results have been good so far. Full tablescans have been eliminated and export times have gone down, in some cases, tables export times have improved by 50%.
However, our biggest table, CE1OC01 (120 GB), continues to be a bottleneck. Initially, after using the new WHERE clause, it looked like performance gains were dramatic, with export times for the first 5 packages dropping from 25-30 hours down to 1 1/2 hours.
However, after 2 hours, the remaining CE1OC01 split packages have shown no improvement. This is very odd because we are trying to determine why part of the table exports very fast, but other parts are running very slow.
Before the custom WHERE clauses, the export server had run into issues with SORTHEAP being exhausted, so we thought that might be the culprit. But that does not seem to be an issue now, since the improved WHERE clauses have reduced or eliminated excessive sorting.
I checked the access path of all the CE1OC01 packages, through EXPLAIN, and they all access the same index to return results. The execution time in EXPLAIN returns similar times for each of the packages:
CE1OC01-11: select * from CE1OC01 WHERE MANDT='212'
AND ("BELNR" > '0124727994') AND ("BELNR" <= '0131810250')
CE1OC01-19: select * from CE1OC01 WHERE MANDT='212'
AND ("BELNR" > '0181387534') AND ("BELNR" <= '0188469413')
 0 SELECT STATEMENT ( Estimated Costs = 8.448E+06 [timerons] )
|
--- 1 RETURN
 |
 --- 2 FETCH CE1OC01
 |
 ------ 3 IXSCAN CE1OC01~4 #key columns: 2
query execution time [millisec] | 333
uow elapsed time [microsec] | 429,907
total user CPU time [microsec] | 0
total system cpu time [microsec] | 0
Both queries utilize an index that has fields MANDT and BELNR. However, during R3load, CE1OC01-19 finishes in an hour and a half, whereas CE1OC01-11 can take 25-30 hours.
I am wondering if there is anything else to check on the DB2 access path side of things or if I need to start digging deeper into other aggregate load/infrastructure issues. Other tables don't seem to exhibit this behavior. There is some discrepancy between other tables' run times (for example, 2-4 hours), but those are not as dramatic as this particular table.
Another idea to test is to try and export only 5 parts of the table at a time, perhaps there is a throughput or logical limitation when all 20 of the exports are running at the same time. Or create a single column index on BELNR (default R3ta column) and see if that shows any improvement.
Anyone have any ideas on why some of the table moves fast but the rest of it moves slow?
We also notice that the "fast" parts of the table are at the very end of the table. We are wondering if perhaps the index is less fragmented in that range, a REORG or recreation of the index may do this table some good. We were hoping to squeeze as many improvements out of our export process as possible before running a full REORG on the database. This particular index (there are 5 indexes on this table) has a Cluster Ratio of 54%, so, perhaps for purposes of the export, it may make sense to REORG the table and cluster it around this particular index. By contrast, the primary key index has a Cluster Ratio of 86%.
Here is the output from our current run. The "slow" parts of the table have not completed, but they average a throughput of 0.18 MB/min, versus the "fast" parts, which average 5 MB/min, a pretty dramatic difference.
package time start date end date size MB MB/min
CE1OC01-16 10:20:37 2008-11-25 20:47 2008-11-26 07:08 417.62 0.67
CE1OC01-18 1:26:58 2008-11-25 20:47 2008-11-25 22:14 429.41 4.94
CE1OC01-17 1:26:04 2008-11-25 20:47 2008-11-25 22:13 416.38 4.84
CE1OC01-19 1:24:46 2008-11-25 20:47 2008-11-25 22:12 437.98 5.17
CE1OC01-20 1:20:51 2008-11-25 20:48 2008-11-25 22:09 435.87 5.39
CE1OC01-1 0:00:00 2008-11-25 20:48 0.00
CE1OC01-10 0:00:00 2008-11-25 20:48 152.25
CE1OC01-11 0:00:00 2008-11-25 20:48 143.55
CE1OC01-12 0:00:00 2008-11-25 20:48 145.11
CE1OC01-13 0:00:00 2008-11-25 20:48 146.92
CE1OC01-14 0:00:00 2008-11-25 20:48 140.00
CE1OC01-15 0:00:00 2008-11-25 20:48 145.52
CE1OC01-2 0:00:00 2008-11-25 20:48 184.33
CE1OC01-3 0:00:00 2008-11-25 20:48 183.34
CE1OC01-4 0:00:00 2008-11-25 20:48 158.62
CE1OC01-5 0:00:00 2008-11-25 20:48 157.09
CE1OC01-6 0:00:00 2008-11-25 20:48 150.41
CE1OC01-7 0:00:00 2008-11-25 20:48 175.29
CE1OC01-8 0:00:00 2008-11-25 20:48 150.55
CE1OC01-9 0:00:00 2008-11-25 20:48 154.84

Hi all, thanks for the quick and extremely helpful answers.
Beck,
Thanks for the health check. We are exporting the entire table in parallel, so all the exports begin at the same time. Regarding the SORTHEAP, we initially thought that might be our problem, because we were running out of SORTHEAP on the source database server. Looks like for this run, and the previous run, SORTHEAP has remained available and has not overrun. That's what was so confusing, because this looked like a buffer overrun.
Ralph,
The WHERE technique you provided worked perfectly. Our export times have improved dramatically by switching to the forced full tablescan. Being always trained to eliminate full tablescans, it seems counterintuitive at first, but, given the nature of the export query, combined with the unsorted export, it now makes total sense why the tablescan works so much better.
Looks like you were right, in this case, the index adds too much additional overhead, and especially since our Cluster Ratio was terrible (in the 50% range), so the index was definitely working against us, by bouncing all over the place to pull the data out.
We're going to look at some of our other long running tables and see if this technique improves runtimes on them as well.
Thanks so much, that helped us out tremendously. We will verify the data from source to target matches up 1 for 1 by running a consistency check.
Look at the throughput difference between the previous run and the current run:
package time start date end date size MB MB/min
CE1OC01-11 40:14:47 2008-11-20 19:43 2008-11-22 11:58 437.27 0.18
CE1OC01-14 39:59:51 2008-11-20 19:43 2008-11-22 11:43 427.60 0.18
CE1OC01-12 39:58:37 2008-11-20 19:43 2008-11-22 11:42 430.66 0.18
CE1OC01-13 39:51:27 2008-11-20 19:43 2008-11-22 11:35 421.09 0.18
CE1OC01-15 39:49:50 2008-11-20 19:43 2008-11-22 11:33 426.54 0.18
CE1OC01-10 39:33:57 2008-11-20 19:43 2008-11-22 11:17 429.44 0.18
CE1OC01-8 39:27:58 2008-11-20 19:43 2008-11-22 11:11 417.62 0.18
CE1OC01-6 39:02:18 2008-11-20 19:43 2008-11-22 10:45 416.35 0.18
CE1OC01-5 38:53:09 2008-11-20 19:43 2008-11-22 10:36 413.29 0.18
CE1OC01-4 38:52:34 2008-11-20 19:43 2008-11-22 10:36 424.06 0.18
CE1OC01-9 38:48:09 2008-11-20 19:43 2008-11-22 10:31 416.89 0.18
CE1OC01-3 38:21:51 2008-11-20 19:43 2008-11-22 10:05 428.16 0.19
CE1OC01-2 36:02:27 2008-11-20 19:43 2008-11-22 07:46 409.05 0.19
CE1OC01-7 33:35:42 2008-11-20 19:43 2008-11-22 05:19 414.24 0.21
CE1OC01-16 9:33:14 2008-11-20 19:43 2008-11-21 05:16 417.62 0.73
CE1OC01-17 1:20:01 2008-11-20 19:43 2008-11-20 21:03 416.38 5.20
CE1OC01-18 1:19:29 2008-11-20 19:43 2008-11-20 21:03 429.41 5.40
CE1OC01-19 1:16:13 2008-11-20 19:44 2008-11-20 21:00 437.98 5.75
CE1OC01-20 1:14:06 2008-11-20 19:49 2008-11-20 21:03 435.87 5.88
PLPO 0:52:14 2008-11-20 19:43 2008-11-20 20:35 92.70 1.77
BCST_SR 0:05:12 2008-11-20 19:43 2008-11-20 19:48 29.39 5.65
CE1OC01-1 0:00:00 2008-11-20 19:43 0.00
 558:13:06 2008-11-20 19:43 2008-11-22 11:58 8171.62
package time start date end date size MB MB/min
CE1OC01-9 9:11:58 2008-12-01 20:14 2008-12-02 05:26 1172.12 2.12
CE1OC01-5 9:11:48 2008-12-01 20:14 2008-12-02 05:25 1174.64 2.13
CE1OC01-4 9:11:32 2008-12-01 20:14 2008-12-02 05:25 1174.51 2.13
CE1OC01-8 9:09:24 2008-12-01 20:14 2008-12-02 05:23 1172.49 2.13
CE1OC01-1 9:05:55 2008-12-01 20:14 2008-12-02 05:20 1188.43 2.18
CE1OC01-2 9:00:47 2008-12-01 20:14 2008-12-02 05:14 1184.52 2.19
CE1OC01-7 8:54:06 2008-12-01 20:14 2008-12-02 05:08 1173.23 2.20
CE1OC01-3 8:52:22 2008-12-01 20:14 2008-12-02 05:06 1179.91 2.22
CE1OC01-10 8:45:09 2008-12-01 20:14 2008-12-02 04:59 1171.90 2.23
CE1OC01-6 8:28:10 2008-12-01 20:14 2008-12-02 04:42 1172.46 2.31
PLPO 0:25:16 2008-12-01 20:14 2008-12-01 20:39 92.70 3.67
 90:16:27 2008-12-01 20:14 2008-12-02 05:26 11856.91

Can WBS element be adopted as splitting characteristic for general GL

Hello :
In our PS module implementation, the client requires that WBS element be picked up in the line item of account payable (vendor) during logistic invoice verification. Currently, we managed to post below document:
   Dr:    GR/IR   - WBS1
            GR/IR -   WBS2
            VAT
      Cr: Account payable (vendor)
I am wondering whether WBS element can be selected as splitting characteristic for general GL? Therefore, WBS element can be posted for account payable.
As fas as I know, in IMG only three characteristics: Segment, profit center and business area are preferred as   splitting characteristic for general GL. WBS element is regarded as splitting characteristic for Controlling.
Does anybody has experience on using WBS element as splitting characteristic for general GL?
Cheers

Hello,
You can add PS_PSP_PNR to the ledger scenarios with the transaction FAGL_GINS which intends to be used for updating the open item and sum tables of the New GL. after that PS_PSP_PNR can be defined as splitting criteria for controlling, but can not be defined as splitting criteria for general ledger.
The reason for this is that it cannot be guaranteed that such fields as PS_PSP_PNR are supplied with values on the account receivables/payables by the standard FI and integration processes. The settings as
zero balance or mandatory field can lead to errors in the system. Therefore we do not recommend the usage of such fields as split criteria for the general ledger.
While PS_PSP_PNR can be defined as split criteria for controlling, so the relevant lines are splitted on the Profit & Loss accounts which are relevant for the CO account assignments.
With Best Regards,
Gladys

Problem with import of split tables.

We are creating copy of our production system. The
system copy has a change of Operating system from HP-UX to Windows
X86_64 and is also has unicode conversion. We followed the following
steps:
1) Performed post copy steps and pre-unicode conversion steps
2) Split big tables using OSS note 1043380 - Efficient Table Splitting
for Oracle Databases
3) Copied *.WHR files to export directory and performed export using SAPinst
4) Copied files export dump to new server.
5) Created whr.txt manually and copied it to the DATA directory of
export dump
6) Started import using SAPinst
Surprisingly the import does not consider the split tables but marks
them as complete in the TSK files. Also the rows imported is 0 for
those tables.
The only error is:
(RFF) ERROR: no entry for table "CDCLS" in "F:\export\ABAP\DATA\CDCLS-1.TOC"
(IMP) INFO: import of CDCLS completed (0 rows) #20110122022015
Why is SAPinst not importing the tables that are split. All table that were not split are importing successfully and R3load is patched.

Resolved.
this is a known issue which is due to the sql splitter tool which
generates space characters at the end of the 'where' clause within the
TSK-file.
At the import that leads to the fact that the entries are not
recognized and nothing is imported, so in the import log you get
no entry for table "BALDAT" in "F:\ccpexport\CCP\ABAP\DATA\BALDAT-1.TOC"
As a workarround I would like you to apply the following:
1. remove all blank characters at the end of the WHR clause in the TSK
-file, that is i.e.:
D BALDAT I ok
WHERE ("LOG_HANDLE" < '4iLKIlCIjLpX0000p5bqa0')__ <-- I have marked the
two blank characters at the end of the line by '_'
remove this characters, so that the thera are no blanks at the end of
the line
2. set the status in the corresponding TSK-file from 'ok' to 'err'
3. repeat the import of the corresponding packages
I would like to mention that as per note # 1043380 you should use
both for the export and import:
R3load 7.00 version built newer than June 18th, 2008
- where this issue should be fixed.

Unrecognized partition table for drive 80 error??

Currently running leopard on a macbook pro.
Formatted w bootcamp and running Windows Vista Ultimate.
Installation went fine reformated drive to ntfs 45gigs.
But when booting into windows I get this error message
"unrecognized partition table for drive 80"
Then the system boots into vista as normal but that error message is annoying.
Tells me to fix bootmgr using fdisk. How do I do that?
Thanks.

I previously had Vista installed under the beta with Tiger and there was no issues at all regarding boot times or error messages. (Boot times being quite nippy considering)
I did reformat the hard drive space partitioned in side Vista installation as NTFS. As I am only a switcher for a year or so I imagine there may be something I am missing but given the text when I try to boot into Vista, it looks to be the boot loader that is erroring and that looks the same as a GRUB loader failing.
I just do not get why a BETA product would work fine, then after a fresh installation of the new Mac OSX 10.5 with the final version of boot camp I would receive errors like this.
I have reclaimed the hard drive space and split the disk again but the same error persists. Previously I was showing off my Macbook to work mates showing how it handled Windows as well as the user friendly OSX. Now all I can show them is a 5 minute loading screen full of non booting Vista as they look at me like some kind of idiot. (Which depending on who you ask is possibly correct)

Table for taxes

Hi
Can any one please suggest me (a MM guy) a table equivalent to BSET (for taxes) which will contains fields accounting document number, fiscal year, company code, material number, cost center (split account assigned vendor invoice), tax amount, and base amount for the tax amount
BSET will have all the fields except the material number and cost center. I want to know, to which material, this tax amount has been paid
waiting for your quick reply
regards
srini

Hi Srini,
refer these tables:
T005S - Taxes- Region (Province) Key
T005U - Taxes- Region Key- Texts
T006 - Units of Measurement
A003 - Tax Indicator
A053 - Taxes via Jurisdiction Code
T007A - Tax Keys
T007B - Tax Processing in Accounting
T007S - Tax Code Names
T030K - Tax Accounts Determination
T030R - Rules for Determination of Standard Accounts
T050T - General texts
T681A - Conditions: Applications
T681B - Conditions: Applications:
Texts - T681V Conditions: Usages
T681W - Conditions: Usage: Texts
T681Z - Conditions: Dependent Data for Application/Usage
T682I - Conditions: Access Sequences (Generated Form)
T683S - Pricing Procedure: Data
T683T - Pricing Procedures: Texts
T685 - Conditions: Types
T685A - Conditions: Types: Additional Price Element Data
T685T - Conditions: Types: Texts
TTXD - Description of Tax Jurisdiction Code Structure
TTXJ - Check Table for Tax Jurisdiction
TTXJT - Text Table for Tax Jurisdiction
Thanks and regards

Tables for Fiels Fixed Value and Variable Value

Hi,
Can any one tell me where the actual fixed and variable costs are stored in which table and also the planned costs. I have checked it, but it is showing RKPLN as data structure. We are doing development report where in standard Cost Center Report we need to have break up of fixed and variable cost. Please guide me where exactly these fields are stored in which table. its very urgent.

Hi,
In regard to the tables for planned data please do a search of the forum as this question has already been asked a few times. E.g. here:
CO PLANNING TABLES
In regard to fixed / variable actual costs: these are not stored in separate tables. If a posting contains fixed and variable portions, for example postings resulting from splitting (KSS2), then the fixed portion is stored in the COEP- WKFBTR (line items) and COSS-WKF* fields (summary items). Please observe SAP note 192107 on this issue.
Regards
Karl

Split Table Procedure in Database Migration

Hello,
We are doing Database Migration from Informix to Oracle...
We have a Big Table PCL4 in our system which is around 100 GB..
I want to split the table and would like to know what is the procedure to do so...
What changes are to be done at database level , in STR Files , in TOC files and if any in .cmd files...
Thanks & Regards,
RaHuL...

RaHul,
In my last experience with Informix migration (HeSC), I didn't use split table, because the following caution:
CAUTION: This may not be possible on databases that need exclusive access on the table when creating an index (for example, Informix).
I used the following informix features:
1. We fragmented the BIG Table (In our case CDCLS) into four peices ( Four DBSPACES) and moved CDCLS~0 (Index) to others DBSPACE.
2. We increased CPU VPs and used the following Informix parameters:
PDQPRIORITY 100
PSORT_NPROCS 32
The results of the test was: ~ 5hs50min less during export
Cheers,
Jairo

Table for MRP results

Dear all,
Is there any table in which the results of MRP run are stored?
I want to pick up some of the data for a report.
Thank you,
Shrenik

Dear Shrenik,
check in these tables,
MDKP                           Header Data for MRP Document
MDTB                           MRP Table
MDVL                           Planning file entry for long-term planning
MDVM                           Entry in MRP File
PBVPV                          Material index for consumption of planning
PLAF                           Planned order
REUL                           Material stock transfer reservation index
SAFK                           Run Schedule Master Data
T024D                          MRP controllers
T436A                          Floats for scheduling
T437V                          Distribution key in MRP
T437W                          MRP distribution key (texts)
T438A                          MRP Type
T438S                          Text describing the range of coverage profile
T438T                          MRP description
T438X                          MRP group text
T439F                          Handling of planning flag at abnormal termination
T439L                          Warehouse costs for MRP lot size
T439T                          Texts for lot-sizing procedures
T440A                          Change fields for MRP
T440B                          Control table for creating MRP record
T440F                          Exception messages for the forecast
T440Z                          Allocate error -> error class in the forecast
T449A                          Period split
T449B                          Period split: language-dependent description
T450                           MRP transaction control
T457A                          Processing key for planning run
T457C                          Transaction calls control
T457S                          Block table for MRP and forecast run
T457T                          Description of MRP elements
T458B                          Description of exception messages
T460A                          Special procurement key
T460B                          Special Procurement Key Conversion
T460C                          Order/Purchase order types for planned order
T460D                          Order/Purchase order types for planned order
T460T                          Texts for special procurement keys
T461P                          Planning strategy group
T461S                          Planning strategies
T461T                          Planning strategy text
T461X                          Planning strategy group text
Regards
Mangalraj.S

How to extract data from monthly tables for annual balance chart?

Hello Again!
I am wanting to decide whether to enter all of my transactions into one table for the whole year or separate tables for each month. If I was to use one table for the whole year it would probably have in the region of 1000 entries, and as I understand it, Numbers doesn't work so well with such large tables. Also, as I will be mostly using Numbers on my iPad, where it runs slower, this may well slow things down considerably. Another reason for using Monthly Tables is that it would be easier to search.
Having said this, I am using the following method to construct balance charts for my accounts which seems to depend on having just one table for all transactions for the year. Here is a sample of the transactions table:
which updates the balance for each account after each new transaction is entered.
Then I use the following table for creating the balance charts:
It uses the following formula to return the balance at the end of each week for each account (this is the formula for Account 1) which then is displayed in the chart.
=LOOKUP(A2,$Week Number,All Transactions :: Account 1)
If I was to use the Monthly Tables method it is not obvious to me how I would create the Weekly Balance Table, given that I would need to draw data from 12 different tables, and that some of these Tables would contain the same Week Number (for weeks that overlap months).
I would be grateful for any advice on achieving the result I am looking for by the most efficient method.
Thanks
Nick
P.S. Hopefully this is the last question for a while!

I wasn't urging you to keep an annual table but to spit it on an easier to rule basis.
Split it in chuncks of exactly 35 days starting from the first one of the 'year' in operation
Doing that everything will be easier
the index of a day will be calculated by
=DATEDIF(B,D,"D")+1
The index of the 'custom_week' will be calculated by :
=1INT((DATEDIF(B,D,"D")1)/7)
So, it would be easy to gather datas from a given 'custom_week'.
Yvan KOENIG (VALLAURIS, France) jeudi 5 août 2010 10:22:25

Table for Customer and vendor open balance on a key date

Dear All,
Can anyone please let me know Table for Customer and vendor open balance on a key date. We are developing one customized report.
I have checked with the below table :
Customer-KNC1, KNC3,BSID, BSAD
Vendor-LFC1, LFC3, BSIK, BSAK.
But these are not working properly for all customers and vedors. Also, in open items, there are items with clearing documents.
Plesae let me know, how to go for it.
Please suggest.

Hi
Use BSID and BSIK for open items
And pass company code, year and from date and to date range in Posting date selection option
Reg
Vishnu

Creation of New Table for Delivery Output Type.

Hi Guys,
I need to replace an existing table by creating a new Table in the existing Access Sequence with the combination of "Ship to Party/Product Hierarchy".
Logistics>Shipping>basic Shipping functions>Output determination>Maintain Condition Tables-->maintain output condition table for deliveries.
I am choosing a new table by the name 902, but i am not getting the field " PRODH Product Hierarchy" on the right hand side to choose from.
I checked the field catelog also. Firstly the field catelog was also not having the field, and then i added the field in it by choosing new entries.
I guess i am missing some step in between, thats why the new field (PRODH) is not showing on the right hand side while creation of the condition table.
One more thing, when i am seeing the Field Catelog, i am able to see a very large number of fields, then why only a few are appearing during creation of a new table??????
Can you guys correct me and let me find a way.????
Thanks very much indeed.
Regards,
Vivek

Hi If u have already the field in FC u can add with new entries .
Try with ,enter t- code SE11, enter KOMB- it will ask for access key get from basis and add u r Field catalog
Field catalog for condition key: output determination
If at all u want a new field tao add to u r FC u Can try with userexit.
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields.
 The fields which are not in either of the two tables KOMK and KOMP
cannot be used in pricing .Sometimes a need arises when the pricing
is to be based on some other criteria which is not present in the form of fields in either of the two tables.
This problem can be solved by using USEREXITS which are provided for pricing in SD.
Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP
program SAPMV45A. The name of the userexits are same. i.e
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely
created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that
has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose
includes are provided in each of them .
To create the field in header data(KOMK) the include provided is KOMKAZ
and to create the field in item data(KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2)The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
Message was edited by:
 SHESAGIRI GEDILA

Document splitting: Items for clearing 0010/100062508/2010/001 not found

HI Gurus,
I hava issue with FC valuation. I have done configurtin for FC Valuation of GL A/c i.e, Long Term loan paybles which is created as Open Item management.
It is working fine post the entries at the end of May and reversed the same on 01.06.2010 in development system. i have moved saem request to Acceptance client and testing the same scenario. But i am getting the following error.
"Document splitting: Items for clearing 0010/100062508/2010/001 not found
Message no. GLT0002
Diagnosis
Document splitting cannot perform clearing because it was not possible to find complete splitting information on the items to be cleared (company code 0010, document number 100062508, fiscal year 2010, item 001).
System Response
Clearing cannot be performed and the document cannot be posted.
Procedure
Exclude the affected item from clearing.
It may be that this item was not posted with active document splitting. In this case, this item or document would have to be migrated."
I have checked the docuemnt splitting config . In two systems it was same and doc.splitting was configurated very long back.
Could any one help on the above error
Thanks in advance
PAVAN

Hi Pavan,
Please note the following, the error GLT0002 is normally caused by a change done in your customizing for splitting. Since you mentioned that this is happening for one company code, it seems to be that one change was made only for this company code in your SPRO settings.
For example if you have activated open item managment subsequently on account or another example would be that you posted document prior to activation of document splitting.
Please see section 5 of note 891144:
Items posted while open item management was still inactive in G/L account master data cannot be cleared after open item management has been activated subequently if New G/L document splitting is active.
Therefore, if document splitting is active, open item management should never be activated subsequently on accounts to which documents had already been posted with inactive open item management.
Review note 891144 in full. I believe that this will help you resolve the issue.
Best Regards,
Vanessa.

Split tables for DMO

Similar Messages

Maybe you are looking for