Table for PO components

HI All,
Plz let me know the table used for PO components.
Regards,

Hi,
Use the tables mentioned below in the sequence mentioned to get the components:
MAST -- Material to BOM Link
STKO -- BOM Header
STPO -- BOM item
Regards,
Chandra
Edited by: chandra piminty on Dec 9, 2009 1:09 PM

Similar Messages

  • Table for Subcontracting PO Components (not adopted from BOM)

    Hi All,
    In which table do the components of a subcontracting PO get stored? This is specifically for a situation involving subcontracting of a material without a standard BOM. I will be feeding the components manually during PO creation. I need to pull the component list in the Smartform. Any idea? In case there's a function module for the same, please help out.
    - Rahul

    Hi,
    Thanks for your reply. But these are all tables related to BOM for the item. My requirement is specifically for an item that does not have a BOM. That's why I am stuck up. Please let me know if there's any table where the component data flows (not from the BOM, from the PO). PO component data is available in the Structure MDPM. How to retrieve the data from Structure MDPM ? Any function module is there for that?
    - Rahul.

  • TABLE for components issued to the order

    Hello all,
    I have a requirement where I am asked to create a report which picks up all the open orders and and all the Actual quantities of components that have been issued to the order and the currency value for it. Would you know what tables I can use for this report? One table that I found useful is COSP (CO Object: Cost Totals for External Postings). It gives me the dollar value of components issued and quantity but we dont get the material number for those components.
    If you have any suggestion plz let me know.
    Regards

    For actual
    Check AUFM table
    selection criteria movement type 261  -(AUFM- BWART)
    posting date:( AUFM- BUDAT)
    you can find the actual posting quantity  (AUFM-ERFMG)  relevant to production order and value (AUFM-SHKZG)
    for plan
    use RESB table.

  • Tables for BOM Header and Components

    Dear Friends,
    Please let me know which tables provide a link between the header Material and corresponding Component Materials of a BOM?
    I have seen STKO and STPO but couldn't find such a link in them. STPO gives the component material but I couldn't get any link to Header material.
    Regards,
    Alok.

    Hello Alok,
    Table for BOM header             - STKO
    Table for BOM item                - STPO
    Table for material to BOM link - MAST
    Check if MARC table has a material in it and the same material is available in MAST also, it means that BOM has been created for that material..
    If Material is available in MARC and not available in MAST, it means BOM has not been created for that material.
    Reward Points, if useful.
    Regards,
    Nitin.

  • 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                  

  • Tables for subcontracting process

    Hi All,
    Pls tell the tables for components in subcontracting process.
    Regards
    Sunil

    Hi
    After creating a subcontacting po, it will update the following tables
    RESB , EKET , EKKO, EKPO
    Join the two tables RESB and EKET with RSNUM , PO NUmber, Line item as the linking field, if u pass the PO Number in the EKET Table then you can able to see all the components that you have mentioned in the PO for the Final Product. This component is not from the Material BOM , its from what you have maintained in the PO.
    Pls clarify in your query , completing means closing the PO with GR,IR or just PO creation.
    Regards
    Amuthan M.
    Edited by: Amuthan M on Nov 3, 2009 2:28 PM

  • Tables for Report

    I am trying to make an ABAP report where the standard price for a particular material (row) will be shown broken down into cost components (columns).
    Can you please advice from which tables should I pull the info for cost components. I have tried table KEKO and KEPH but didnu2019t find it in their. Can you please state the table and the name of the fields.
    Cost components include:
    Active, Raw, Pkg. Comp, Direct Labor, Additive Cost and Overhead

    @ Srikanth Munnaluri
    Currently the client dosen't use COPA. However it would be nice if you could explain in a bit of detail as to how COPA would solve that problem. Actually we need to make a case before the management as to how COPA would help us solve the issues we are currently facing to justify it's implementation.
    @ other experts on the forum.
    If you guys can exactly tell me what tables are needed to pick fields like Standards broken down into cost components, previous year standards and Budgeted production volume.
    Edited by: NIK83 on Feb 23, 2009 8:11 PM

  • Table for model characteristic usage in queries

    Hi does anyone know the name of the table(s) which I can establish the following:
    1.  I have a multicube with say 15 dimensions consisting of a total of 35 Dimension characteristics
    2. There are say 6 navigational attributes switched on for reporting
    3. There are say 10 key figures
    4. There are say 65 queries built off this info provider
    What I would like to establish is in the 65 queries which elements in 1, 2 and 3 have been used.  I am aware of the RSZ* tables but was not able to find what I am looking for.  Thanks in advance

    Hi Anand,
    I find this is relevant to your query and go through this...
            The names of the structural components are language dependent. When you define and save a query with the logon language as German, only the corresponding German texts are saved in the relevant tables (for example, RSZELTTXT). This is not the original key figure, but rather a structural component, a new object that linksto the original key figure but is not the original key figure.
    ·        If you then execute the query in a different logon language to the one that you used to define the query, the standard texts are displayed for all structural components that have no text.
    ·        Structures and structural components (selections, formulas) are completely independent objects that appear in the BEx Query Designer and that you can store in the relevant tables when you save them. Since texts are fundamentally language-dependent, the texts in the query definition appear in the logon language only when you save the query.
    regards,
    rudra.
    Assign points if helpful...

  • How to find tables for a particular business object.

    Dear Friends,
    I want to display, all the tables related to a particular business object.
    So I think there must be way of doing it using packages.
    example:-
    I will have list of all packages referencing to all business Components
    (ex.SALES) then i will get a list of all the tables related to SALES and then I would like to get all the METADATA regarding that TABLE.
    please give me some ideas How to achieve this.
    thanks,
    jeevan

    hai Naveen ,
    Thanks for the reply.
    I had gone through the Link.
    I want to know "How could I get the list of all the Tables of a particular Business Component"
    like suppose i entered Sales i sould get all the tables related to Sales ....if  MM then list of MM tables...
    in Se80 the package VA is for sales .....
    and there i can get all the tables for sales...
    but If u know any searching criteria by which i will be able to the list of tables.
    thx,
    jeevan

  • What is the table for query name

    Hi All,
    I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
    Thanks,
    Alex.

    hi Alex,
    try RSRREPDIR, RSZCOMPDIR.
    there is one oss note all the tables.
    Table containing Work Book and query relation
    Query Detailes
    oss 792779
    Symptom
    Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
    The program is recommended for BW system administrators.
    Other terms
    Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
    Reason and Prerequisites
    ATTENTION: the described version of the program is delivered with the following Support Packages:
    SP27 for release BW 3.0B
    SP21 for release BW 3.1C
    SP13 for release BW 3.5
    All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
    Check prerequisites
    Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
    Checks for query elements in 'D' version are possible only in the systems which are set as content.
    Checks description
    Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
    1. Table RSRREPDIR
    The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
    The following errors can be found:
    - queries with missing definition;
    - queries with missing GENUNIID;
    - queries with technical names different than in RSZCOMPDIR;
    - non-queries in the table.
    1.1 Queries with missing definition
    The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
    1.2 Queries with missing GENUNIID
    Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    1.3 Queries with technical names different than in RSZCOMPDIR
    The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
    1.4 Non-queries in the table
    The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
    2. Table RSZCOMPIC
    The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
    The following errors can be found:
    - local elements in RSZCOMPIC;
    - components with inconsistent definition;
    - components based on non-existing InfoProviders;
    - components based on non-active InfoProviders.
    2.1 Local elements in RZSCOMPIC
    The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
    2.2 Components with inconsistent definition
    The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    2.3 Components based on non-existing InfoProviders
    Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
    2.4 Components based on non-active InfoProviders
    Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
    The check is available only for the query elements in object version 'A' (active).
    3. Table RSZCOMPDIR
    The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
    The following errors can be found:
    - duplicated technical names (COMPID);
    - components with inconsistent definition;
    - components without InfoProvider assignment;
    - components with missing OWNER.
    3.1 Duplicated technical names (COMPID)
    The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
    The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
    different queries are available in BEX Analyzer and RSRT under the same name;
    wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
    replacement of variables does not work... etc.
    The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
    ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
    The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
    3.2 Components with inconsistent definition
    Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
    3.3 Components without InfoProvider assignment
    All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
    3.4 Components with empty ONWER field
    Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
    For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
    4. Table RSZELTXREF
    The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
    The following errors can be found:
    - missing elements (INCONSISTENCY dump);
    - not supported relations between query elements;
    - extended RSZELTXREF check.
    4.1 Missing elements
    Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
    The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
    The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
    ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
    4.2 Not supported relations between query elements
    Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
    4.3 Extended RSZELTXREF check
    The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
    - records with empty INFOCUBE field
    - records which are not used in any query or query component
    Records with empty INFOCUBE field
    The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
    When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
    Records which are not used in any query or query component
    The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
    The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
    ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
    Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
    records used in existing queries or query components with empty INFOCUBE field;
    records used in existing queries or query components with wrong INFOCUBE assignment;
    records with or without INFOCUBE assignment which are not used in any query or query component.
    For further check details read the OSS note 859086.
    5. Table RSZGLOBV
    The table RSZGLOBV contains the definitions and technical properties of the variables.
    The following errors can be found:
    - variables with inconsistent definition;
    - variables with missing or incorrect properties;
    5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
    The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
    In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
    As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
    ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
    ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
    5.2 Variables with missing or incorrect properties
    Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
    Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
    6. Table RSZELTDIR
    The table RSZELTDIR is the main directory table containing all query elements available in the system.
    ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
    The following errors can be found:
    - local elements not in use;
    - reusable elements not in RSZCOMPDIR table;
    - reusable elements not in RSZCOMPIC table;
    - structure (STR) without structure members;
    - selections or RKF without definition in RSZSELECT table;
    - formulas or CKF without definition in RSZCALC table;
    - variables (VAR) without definition in RSZGLOBV table;
    - queries (REP) without entries in RSRREPDIR table.
    6.1 Local elements not in use
    Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
    6.2 Reusable elements not in RSZCOMPDIR table
    Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
    6.3 Reusable elements not in RSZCOMPIC table
    Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
    6.4 Structures (STR) without structure members
    Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
    In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
    6.5 Local selection of RKFs without records in RSZSELECT table
    Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
    Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
    Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
    Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
    Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
    If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
    In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
    6.6 Local formulas of CKFs without records in RSZCALC table
    Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
    The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
    In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
    6.7 Variables without records in RSZGLOBV table
    Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
    The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
    6.8 Queries without records in RSRREPDIR table
    Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
    A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
    The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
    In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
    hope this helps.

  • Table for flag STLKZ in CS03 transaction

    Hi Guru,
    in the transaction CS03 for some materials I see in the column (ASM ASSEMBLY STLKZ field) who wants a flag to indicate that this material is related to a bom.
    In which table can I see the flag STLKZ?
    Thank for all !

    Hello Marco,
    This field is not a table field therefore it is not stored on any table that you can refer for a direct link. This field is filled in if an entry is found table MAST for that component. Table MAST is a table for material/Plant BOMs. The assembly indicator is set If the component was is found on the header material on a BOM. The system checks the table MAST to see if that material was ever assigned to a BOM number (STLNR). 
    In this case, materil A will be set assembly indicator in BOM B since it is a header material of a BOM. This indicator is set no matter what the usage the BOM has. You can find what BOM it is linked . You can then use MAST-STLNR to check tables STPO for components.
    There is also another field checked when setting this flag, There is a field in the table MARA for storing low-level code. This
    field is also considered for setting the flag.Low level flags are changed based on bom levels
    Hope this information helps.
    Thanks
    Amber

  • Default Subpackage Names for Business Components (11g); Bug?

    Does anyone know how to enable the ability to specify the default packages under Tools -> Default Project Properties ->Business Components -> Packages?
    Mine are all greyed out.
    Also, even when I have the bare minimum of an ADF model project, before even checking "Initialize Project for Business Components", the defalt packages are greyed out.
    Further, once I do check "Initialize Project for Business Components", the section for Default Subpackage Names is complete gone.
    I want to be able to specifiy the subpackages, so that when I regenerate entities etc. from tables the components go to the right packages.
    Thanks for any help.

    This seems like a bug to me. If you select Initialize Project for Business Components, everything is enabled. And stays that way even after you open a different application.
    But , You can set these values under Tools - Preferences - Business Components - Packages. This works nicely. Once you set these, create a new application and things will be fine. If you have existing application, it may require some xml file (.jpr) manipulation. That seems to be a nicer approach. I don't know what is the purpose of Default Project Properties, when you can set everything by Tools - Preferences.

  • Base table for 0CRM_SALES_CONTR_I(CRM Sales Contracts: Item)

    Hi experts,
    Im looking for the base tables for 0CRM_SALES_CONTR_I(CRM Sales Contracts: Item).if there is a base table for the datasource how do we find it.
    Thanks,
    sivarama landa

    Hello Siva,
    This is the way to find in the system:
    From RSA2>Extraction Tab-> Extract Structure-->Components Tab->Component Column( You will see .INCLUDE)  with its Corresponding Description in the column---> Short Description ( FOR EX : ORDERADM_H Data for BW DataSources), usually the CRM system table will be CRMD_******** or CRM_******.
    Here you will not find the lbwe( way to find tables in the ECC ).
    The Best and easiest way to find is as said by Martin.
    Regards,
    Adhvi

  • Table for Assembly indicator checkbox in BOM

    Please inform me about Table for Assembly indicator checkbox in BOM
    Field name--- STLKZ.
    If table is not there then how to find if this field is checked or Not checked  in development program

    Dear Mayuresh,
    There is no table where in you can get this information which has got an assembly of its won.
    Either you can use CS11,CS12 or CS13 for limited level explosion or else to identify for which
    components an assembly exists for itself.
    Or else at Functional module level.
    Regards
    Mangalraj.S

  • Tables for task list

    For task list header operation extract we use table plko,now my question is in which tables do we check the opeartions,the packages and the components for the task list.Is there a single table,or a separate table for each to extract the data?

    PLAS      Task List - Selection of Operations / Activities
    PLKO      Task List Header
    PLPO      Task List - Operation / Activity
    ABAP table link to

Maybe you are looking for