Tables and Indices

Hello,
I check the current sizes of tablespaces in DB02.
If I analyze the tablespace for whole ODS area
(storage management: tablespaces) there
are different types of database objects for example
"TABLE", "INDEX", "TABLE PART" and "INDEX PART".
My question is what are the database objects "Table Part"
and "Index Part"? These objects allocate a lot of DB-memory. But they are not listed when I check the size of a single ODS object (detailed analysis, the size of a single ODS only results from the database objects "TABLE" and "INDEX").
Best regards
Mauricio

Hi,
Indexes are build on the Tables,Indices reduces the database accessing every time.By defualt one index(known as Primary Index)built on the table.Seconday index can be maintained by the user.In Primary index with Primary key by default index can be accessed.
To see the DBperformance Tcode used is DB02.
Thanks,
Praveena.

Similar Messages

/BIC/4 tables and indices after repartitioning

I am testing repartitioning infocubes and noticed that the temporary tables used in the process are not deleted. Is there a delivered SAP program to delete the /BIC/4 tables and indices? If not is it safe to ask our DBA to drop all /BIC/4* tables?

If you are sure you can delete the tables, you can ask the DBA to use Tcode SE14 to adjust/delete.
If you have to delete data in the tables, you can use function module RSDU_TABLE_TRUNCATE in SE37.

From which table and field can I get batch split indicator?

Dear friends,
There is batch split indicator at VL02N screen. From which table and field can I get this indicator?
Thanks regards..

Hi,
I dont think there is anythign called batch split indicator.
You can find that there is a batch split in a delivery if LIPS-UECHA field is updated for a particular delivery. If UECHA is filled, then the number means that for the item number mentioned in UECHA, those records are the split records.
i.e. For example say for a line item 10, there are 2 split items in a delivery. In this case, there will be two line items with LIPS-POSNR = 90001 and 90002. These line items will have LIPS-UECHA = 10. This means that the items 90001 and 90002 are the child batch items for the parent line item 10 as mentioned in UECHA field.
btw....u can check LIPS-CHSPL if this is what you are looking for.
I hope this answers your question. If you have any doubt, pls lemme know

Interactively changing values to table problem: indicator and control table, and why it does not work after a while...?

I have been producing a VI that loads a set of data and displays it in a table: A table control is initialised with an empty variable, the loaded data takes the place of the variable and fills the table, while some headers are added. That table feeds an intensity graph to give a pictorial impression of the data.
With this scheme, a user can change any value of the table, and the changes are interactively reflected on the graph.
Problem: after few saving of the VI, the access to the table doesn't work anymore. It is the same with all my numerical controls in the VI where it should be possible to enter a value.
If anybody has an idea on the potential
causes of these problem, I would be really grateful as it is very useful...when it works !
Regards,
Elie Allouis

I can not image what is causing the error. Would you be willing to post some code to see if we can reproduce the problem?
Jeremy7

What are the tables and fields in fico & sd module

what are the tables and fields in fico & sd module

Hi,
 Sales and Distribution:
Customers KNA1 General Data
KNB1 Customer Master Co. Code Data (payment method, reconciliation acct)
KNB4 Customer Payment History
KNB5 Customer Master Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data (credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Partner Function key
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link
Sales Documents VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document Header Data
VBKD Sales Document Business Data
VBUP Item Status VBAP Sales Document Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records
SD Delivery DocumeLIPS Delivery Document item data, includes referencing PO
LIKP Delivery Document Header data
Billing Document VBRK Billing Document Header
VBRP Billing Document Item
SD Shipping Unit VEKP Shipping Unit Item (Content)
VEPO Shipping Unit Header
Financial Accounting
FBAS Financial Accounting Basis
BKPF Accounting Document Header BUKRS / BELNR / GJAHR
BSEG Accounting Document Segment BUKRS / BELNR / GJAHR / BUZEI
BSIP Index for Vendor Validation of Double BUKRS / LIFNR / WAERS / BLDAT /
 Documents XBLNR / WRBTR / BELNR / GJAHR / BUZEI
BVOR Inter Company Posting Procedure BVORG / BUKRS / GJAHR / BELNR
EBKPF Accounting Document Header (docs from GLSBK / BELNR / GJHAR / GLEBK
 External Systems)
FRUN Run Date of a Program PRGID
KLPA Customer / Vendor Linking NKULI / NBUKR / NKOAR / PNTYP
 / VKULI / VBUKR / VKOAR
KNB4 Customer Payment History KUNNR / BUKRS
KNB5 Customer Master Dunning Data KUNNR / BUKRS / MABER
KNBK Customer Master Bank Details KUNNR / BANKS / BANKL / BANKN
KNC1 Customer Master Transaction Figures KUNNR / BUKRS / GJHAR
KNC3 Customer Master Special GL Transactions KUNNR / BUKRS / GJAHR / SHBKZ
 Figures
LFB5 Vendor Master Dunning Data LIFNR / BUKRS / MABER
LFBK Vendor Master Bank Details LIFNR / BANKS / BANKL / BANKN
LFC1 Vendor Master Transaction Figures LIFNR / BUKRS / GJHAR
LFC3 Vendor Master Special GL Transactions LIFNR / BUKRS / GJHAR / SHBKZ
 Figures
VBKPF Document Header for Document Parking AUSBK / BUKRS / BELNR / GJHAR
FBASCORE Financial Accounting General Services Basis
KNB1 Customer Master (Company Code) KUNNR / BUKRS
LFA1 Vendor Master (General Section) LIFNR
LFB1 Vendor Master (company Code Section) LIFNR / BUKRS
SKA1 G/L Account Master (Chart of Accounts) KTOPL / SAKNR
SKAT G/L Account Master (Chart of Accounts SPRAS / KTOPL / SAKNR
 Description)
MAHNS Accounts Blocked by Dunning Selection KOART / BUKRS / KONKO / MABER
MHNK Dunning Data (Account Entries) LAUFD / LAUFI / KOART / BUKRS /
 KUNNR / LIFNR / CPDKY / SKNRZE /
 SMABER / SMAHSK / BUSAB
FI-GL-GL (FBS) General Ledger Accounting: Basic Functions- G/L Accounts
SKAS G/L Account Master (Chart of Accounts SPRAS / KTOPL / SAKNR / SCHLW
 Key Word list)
SKB1 G/L Account Master (Company Code) BUKRS / SAKNR
FI-GL-GL (FBSC) General Ledger Accounting: Basic
 Functions - R/3 Customizing for G/L Accounts
FIGLREP Settings for G/L Posting Reports MANDT
TSAKR Create G/L account with reference BUKRS / SAKNR
FI-GL-GL (FFE) General Ledger Accounting: Basic
 Functions - Fast Data Entry
KOMU Account Assignment Templates for G/L KMNAM / KMZEI
 Account items
FI-AR-AR (FBD) Accounts Receivable: Basic Functions - Customers
KNKA Customer Master Credit Management : KUNNR
 Central Data
KNKK Customer Master Credit Management : KUNNR / KKBER
 Control Area Data
KNKKF1 Credit Management : FI Status data LOGSYS / KUNNR / KKBER / REGUL
RFRR Accounting Data A/R and A/P RELID / SRTFD / SRTF2
 Information System
FI-BL-PT Bank Accounting: Payment (BFIBL_CHECK_D) Transactions General Sections
PAYR Payment Medium File ZBUKR / HBKID / HKTID / RZAWE /
 CHECT
PCEC Pre-numbered Check ZBUKR / HBKID / HKTID / STAPL
FI-BL-PT-AP(FMZA)Bank Accounting: Payment Transactions Automatic Payments
F111G Global Settings for Payment Program for MANDT
 Payment Requests
FDZA Cash Management Line Items in Payment KEYNO
 Requests
PAYRQ Payment Requests KEYNO
Hope this solves your concern...
Regards,
Habeeb
Assign points if helpful

Can you programmatically change the width of columns in a table control\indicator

Is it possible to programmatically change the width of columns in a table control\indicator ie to fit to width of the data or in my case the header information.

Create a property node (or reference) and use the 'Active Cell' property to select which column you want to change and then use the 'Cell size'--> 'Width' property to change the size.
"There is a God shaped vacuum in the heart of every man which cannot be filled by any created thing, but only by God, the Creator, made known through Jesus." - Blaise Pascal
Attachments:
table.vi ‏33 KB

Check table and value table -Example

Hi Experts
Please give me the step by step procedure to create the check table and value table, and how to work on it.
Thanks in advance.
Regards
Rajaram

Hi
Check Table is for Field level Validation whereas Value table is for Domain Level Validations.
Value Table proposes table for check table.
I think you are clear with this.
more elaborate.
Check Table
The Check Table is the table used by system to check if a data exist or not exist.
While creating a table if you want to be sure that a field can have some values
and these are in a certain table, you can give IT this table as CHECK TABLE.
Value Table
This is maintained at Domain Level.
When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator.
Here only allowed values is H or S.
When ever you use this Domain, the system will forces you to enter only these values.
This is a sort of master check . .
To be maintained as a customization object.
This mean that if you want to enter values to this table you have to create a development request & transport the same.
Differences:
1)check table will carry out the check for input values for the table field being entered in any application
and value table will provide values on F4 help for that table field.
2)The check table defines the foreign keys and is part of the table definition.
The value table is part of the domain definition.
check table is validation at field level.
value table is at domain level.
Value table is defined at the domain level and is used to provide F4 help for all the fields which refer to that domain.
Check table is defined against a field in SE11 if you want the values in that field to be checked against a list of valid values. For e.g. if you are using the field matnr in a table you could define MARA as the check table.
Also while defining a check table SAP proposes the value table as check table by default. Referring to the previous example if you tried to define a check table for the matnr field SAP would propose MARA as the check table.
1. what is the purpose / use ?
-- so that the user can select values
from some master table , for that field !!!!
2. This is done by
CHECK TABLE (foreign key concept)
(and not value table)
3. When we create a check table for a field,
then
some DEFAULT table is PROPOSED
4. that DEFAULT table is nothing
but PICKED up from the domain of that field,
and shown from the value of VALUE TABLE.
CHECK TABLE -it is a parent table.
for example..
i have two tables ZTAB1 and ZTAB2.
I have one common field in both the tables,i can make any ztable to be the check table .If i make Ztab1 to be the check table then when i have to make an entry in ztab2 i will check whether ztab1 is having that value or not..
its also field level checking..
Valuetable-It is nothing but default check table.
one parent can have n number of child tables.For example
For ztable we have zchild1 and zchild2 tables r there.
Its domain level checking..When zchild2 uses the same domain as used by zchild1 then the system automatically generates a popup saying a check table already exists would u want to maintain it.
go to domain and then press the value tab u can see the valuetable at the end...
Please refer the links below,
d/r b/n check and value table?
wjhat is the exct difference between check table and value table
what is the check table and value table
check table and value table
Re: wjhat is the exct difference between check table and value table
http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm

Transaction DB02 = Missing Tables and Indexes shows under Secondary indexes from package $tmp

Hi SAP Gurus,
I noticed on our SAP business warehouse (BW) system (NetWeaver 7.0 based on AIX/Oracle 11g) in transaction DB02 => Diagnostics => Missing Tables and Indexes under Secondary indexes, 26 indexes, in package $tmp:
The indexes are defined, but they don't have been created on the database.
When I try to create them via the database tool, I am getting the warning:
Does the warning raise up, because they where defined in the $tmp package?
I was looking in SAP notes for a solution for this "warning" concerning the /BIC/F-Indexes but I didn't found yet anything helpful ...
Thanks for your help and ideas ...
Best regards
Carlos

Hi Carlos,
These are secondary indexes created during process chains in BI to improvise performance.
You may refer below SCN blogs on creation of these indices in BI.
Secondary Index - Improving DSO insert/read performance
How to Create Secondary Index on DSO in SAP BW
Hope this helps.
Regards,
Deepak Kori

Cannot INSERT records into Partitioned Spatial Table and Index

I am trying to tune our Spatial Storage by creating partitioning our spatial_entity table and index. I used the World Geographic Reference System (GEOREF) creating a partition for each 15 x 15 degree grid square assigning a partition key of decimal longitude, decimal_latitude. The build went OK, however when trying to insert a data record I receive an ORA-14400: Inserted partition key does not map to any partition.
I validated the CREATE(s), and all appears correct, but obviously something is not correct, which is prompting for expert help in this forum.
I would be very grateful for your help.
Below are the code snippets for the table and index, and an insert statement.
CREATE TABLE spatial_entity
     geoloc_type VARCHAR2 (60 BYTE) NOT NULL
,entity_id NUMBER NOT NULL
,metadata_xml_uuid VARCHAR2 (40 BYTE) NOT NULL
,geoloc MDSYS.sdo_geometry NOT NULL
,nee_method CHAR (1 BYTE) NOT NULL
,nee_status CHAR (1 BYTE) NOT NULL
,decimal_latitude NUMBER (15, 6) NOT NULL
,decimal_longitude NUMBER (15, 6) NOT NULL
PARTITION BY RANGE (decimal_longitude, decimal_latitude)
     PARTITION p_lt_0_90s
          VALUES LESS THAN (1, -90)
     ,PARTITION p_lt_0_75s
          VALUES LESS THAN (1, -75)
     ,PARTITION p_lt_0_60s
          VALUES LESS THAN (1, -60)
     ,PARTITION p_lt_0_45s
          VALUES LESS THAN (1, -45)
     ,PARTITION p_lt_0_30s
          VALUES LESS THAN (1, -30)
     ,PARTITION p_lt_0_15s
          VALUES LESS THAN (1, -15)
     ,PARTITION p_lt_0_0
          VALUES LESS THAN (1, 0)
     ,PARTITION p_lt_0_15n
          VALUES LESS THAN (1, 15)
     ,PARTITION p_lt_0_30n
          VALUES LESS THAN (1, 30)
     ,PARTITION p_lt_0_45n
          VALUES LESS THAN (1, 45)
     ,PARTITION p_lt_0_60n
          VALUES LESS THAN (1, 60)
     ,PARTITION p_lt_0_75n
          VALUES LESS THAN (1, 75)
     ,PARTITION p_lt_0_90n
          VALUES LESS THAN (1, maxvalue)
CREATE INDEX geo_spatial_ind ON spatial_entity (geoloc)
INDEXTYPE IS mdsys.spatial_index
PARAMETERS ('layer_gtype=MULTIPOINT TABLESPACE=GEO_SPATIAL_IND') LOCAL
(PARTITION p_lt_0_90s,
PARTITION p_lt_0_75s,
PARTITION p_lt_0_60s,
PARTITION p_lt_0_45s,
PARTITION p_lt_0_30s,
PARTITION p_lt_0_15s,
PARTITION p_lt_0_0,
PARTITION p_lt_0_15n,
PARTITION p_lt_0_30n,
PARTITION p_lt_0_45n,
PARTITION p_lt_0_60n,
PARTITION p_lt_0_75n,
PARTITION p_lt_0_90n,
INSERT INTO spatial_entity
     geoloc_type
     ,entity_id
     ,metadata_xml_uuid
     ,geoloc
     ,nee_method
     ,nee_status
     ,decimal_latitude
     ,decimal_longitude
VALUES
               'BATCH'
               ,0
               ,'6EC25B76-8482-4F95-E0440003BAD57EDF'
               ,"MDSYS"."SDO_GEOMETRY"
                    2001
                    ,8307
                    ,"MDSYS"."SDO_POINT_TYPE" (32.915286, 44.337902, NULL)
                    ,NULL
                    ,NULL
               ,'M'
               ,'U'
               ,32.915286
               ,44.337902
Thank you for you help.
Dave

Thank you for your quick reply. I did not post the entire CREATE script as it is quite long. The portion of the script that is applicable to the INSERT is:
,PARTITION p_lt_45e_90s
          VALUES LESS THAN (23, -90)
     ,PARTITION p_lt_45e_75s
          VALUES LESS THAN (23, -75)
     ,PARTITION p_lt_45e_60s
          VALUES LESS THAN (23, -60)
     ,PARTITION p_lt_45e_45s
          VALUES LESS THAN (23, -45)
     ,PARTITION p_lt_45e_30s
          VALUES LESS THAN (23, -30)
     ,PARTITION p_lt_45e_15s
          VALUES LESS THAN (23, -15)
     ,PARTITION p_lt_45e_0
          VALUES LESS THAN (23, 0)
     ,PARTITION p_lt_45e_15n
          VALUES LESS THAN (23, 15)
     ,PARTITION p_lt_45e_30n
          VALUES LESS THAN (23, 30)
     ,PARTITION p_lt_45e_45n
          VALUES LESS THAN (23, 45)
     ,PARTITION p_lt_45e_60n
          VALUES LESS THAN (23, 60)
     ,PARTITION p_lt_45e_75n
          VALUES LESS THAN (23, 75)
     ,PARTITION p_lt_45e_90n
          VALUES LESS THAN (23, maxvalue)
Or, I do not fully understand. Are you indicating that I must explcitly state the longitude in each clause,
e.g ,PARTITION p_lt_45e_45n
          VALUES LESS THAN (45, 45)
,PARTITION p_lt_45w_45n
          VALUES LESS THAN (-45, 45)
If so, that answers the question of why it cannot find a partition, however an Oracle White Paper "Oracle Spatial Partitioning Best Practices" Sept 2004, discusses multi column partitioning such as represented by this problem, and gives an INSERT statement example of :
CREATE TABLE multi_partn_table (in_date DATE,
geom SDO_GEOMETRY, x_value NUMBER, y_value NUMBER)
PARTITION BY RANGE (X_VALUE,Y_VALUE)
PARTITION P_LT_90W_45S VALUES LESS THAN (1,-45),
PARTITION P_LT_90W_0 VALUES LESS THAN (1,0),
PARTITION P_LT_90W_45N VALUES LESS THAN (1,45),
PARTITION P_LT_90W_90N VALUES LESS THAN (1,MAXVALUE
and as I am writing this I am seeing that I failed to include the longitude and latitude in the SDO_GEOMETRY clause, so it does appear tht I need to explicitly state the longitude valuues.
What is your judgement sir?
Dave

Pooled table and clustred table

pooled table and clustred table

Hi
Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just
clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.
For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as
program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.
Table Pools
From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were assigned to this table pool.
Field Type Description
TABNAME CHAR(10) Table name
VARKEY CHAR(n) Maximum key length n =< 110
DATALN INT2(5) Length of the VARDATA record returned
VARDATA RAW(m) Maximum length of the data varies according to DBMS
Table Clusters
Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several logical rows from different cluster tables are brought together in a single physical record. The records
from the cluster tables assigned to a cluster are thus stored in a single common table in the database.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the
data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.
Field Type Description
CLKEY1 CHAR(*) First key fields
CLKEY2 CHAR(*) Second key field
CLKEYN CHAR(*) nth key field
PAGENO INT2(5) Number of the next page
TIMESTMP CHAR(14) Time stamp
PAGELG INT2(5) Length of the VARDATA record returned
VARDATA RAW(*) Maximum length of the data section; varies according to database system
Working with Tables
The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name
input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key, or, alternatively,
select Dictionary object Display from the menu.
In this screen, you can see table information such as
¨ Table type, shown next to the name of the object. In the example, it is a transparent table.
¨ Short text description.
¨ Name of the user who made the last change, and the date of the change.
¨ Master language.
¨ Table status. On the screen, you can see this table is saved and active.
¨ Development class. For information on development classes, refer to Chap. 6.
Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨
Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.
¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:
¨ Field name.
¨ Key indicator. When set, this field is the primary key, or part of it.
¨ Data element.
¨ Basic data type.
¨ Length.
¨ Check table.
¨ Short text, describing the field.
Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings
Standard table:
The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
You should usually access a standard table with index operations.
Sorted table:
The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
Hash table:
The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
Index table:
The table can be a standard table or a sorted table.
Index access is allowed to such an index table. Index tables can be used to define the type of generic parameters of a FORM (subroutine) or a function module.
Just have a look at these links:
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/74/83015785d811d295a800a0c929b3c3/frameset.htm
For creating cluster tables first u have to create table pool ...
create a table and specify the fields and other tecnical settings and
then Goto EXTRAS --> Change Table Category and selct the Pooled table and activate it...
Then Create another table And specify the required fileds and also the settings and then
Goto EXTRAS --> Change Table Category and selct the Cluaster table and in Delivery and
Maintainence Properties mention the Pooled table that u created and activate it...
Regards
Sreeni

QM Tables and T codes

can anybody tell hw many QM Tables and T codes are ther in total approx.
and if possible which r imp. one?atleast tables.
thnx

Dear Sandip,
Important QM Tables
Area Table Description
Master Data QMAT Inspection type - material parameters
Master Data QMHU QM Link Between Inspection Lot and Handling Unit Item
Master Data QMTB Inspection method master record
Master Data QMTT Inspection Method Texts
Master Data QPAC Inspection catalog codes for selected sets
Master Data QPAM Inspection catalog selected sets
Master Data QPMK Inspection characteristic master
Master Data QPMT Master Inspection Characteristics Texts
Master Data QPMZ Assignment table - insp. methods/master insp. characteristic
Master Data TQ01D Authorization groups for QM master data
Master Data TQ01E Text authorization groups for QM master data
Master Data TQ21 Assignment of screens to screen groups
Master Data TQ25 QM:screen sequence for master and inspection characteristics
QM Master Data
Catalog QPCD Inspection catalog codes
Catalog QPCT Code texts
Catalog QPGR Inspection catalog code groups
Catalog QPGT Code group texts
Catalog TQ07 Follow-Up Action for Usage Decision of Inspection Lot
Catalog TQ07A QM: Function Modules for Follow-Up Action
Catalog TQ07T Language-dependent texts for Table TQ07
Catalog TQ15 Inspection catalog type index
Catalog TQ15T Language-dependent texts for table TQ15
Catalog TQ17 Defect classes
Catalog TQ17T Language-dependent texts for table TQ17
Catalog
Sample Determination QDEB Allwd. Relationships: Sampling Procedures/Dynamic Mod. Rules
Sample Determination QDEBT Allowed combinations of procedures/dynamic mod. rules: texts
Sample Determination QDPA Sampling scheme-instructions
Sample Determination QDPK Sampling scheme header
Sample Determination QDPKT Sampling scheme: texts
Sample Determination QDPP Sampling scheme item
Sample Determination QDQL Quality level
Sample Determination
Inspection Char TQ17A Weighting of Char
Inspection Char TQ11 Inspection Qualification
Inspection Char TQ29 Tolerance Keys
Inspection Char T006 Unit of measurement
Inspection Char
Dynamic Modification QDBM Valuation mode
Dynamic Modification QDBMT Valuation Mode: Texts
Dynamic Modification QDDR Dynamic modification rule (header)
Dynamic Modification QDDRT Dynamic modification rule: texts
Dynamic Modification QDEP Allowed inspection severities
Dynamic Modification QDEPT Allowed Inspection Severities: Texts
Dynamic Modification QDFB Function modules for the individual procedure categories
Dynamic Modification QDFBT Function Modules for Procedure: Texts
Dynamic Modification QDFM Function modules for valuation mode
Dynamic Modification QDFMT Function Modules for Valuation Mode: Texts
Dynamic Modification QDPS Inspection stages for a dynamic modification rule
Dynamic Modification QDPST Inspection Stages: Texts
Dynamic Modification QDSA Sampling type
Dynamic Modification QDSAT Sampling Type: Texts
Dynamic Modification QDSV Sampling procedure
Dynamic Modification QDSVT Sampling Procedure: Texts
Dynamic Modification TQ39B QM : Activates reference for dyn. modification level
Dynamic Modification
Graphics & SPC QASH Quality control chart
Graphics & SPC QAST Control chart track
Graphics & SPC QPSH Control chart types
Graphics & SPC QPSHT Texts for control chart types
Graphics & SPC QPSP SPC criterion
Graphics & SPC QPSPT Texts for SPC criteria
Graphics & SPC QPST Control chart track
Graphics & SPC QPSTT Texts for control chart tracks
Graphics & SPC
Specifications QMSP QM: material specification
Specifications
Inspection Plan PLKO Inspection plan Header
Inspection Plan MAPL Material Assignement
Inspection Plan PLPO Operation Details
Inspection Plan PLMK Inspection plan characteristics
Inspection Plan PLMW MAPL-Dependent Charac. Specifications (Inspection Plan)
Inspection Plan TQ03 QSS: Control for Screen Texts/TABLE NOT USED (Rel. 4.6)
Inspection Plan TQ29A Dependency tolerance key - nominal measurement
Inspection Plan TQ72 Type of share calculation
Inspection Plan TQ72T Texts for type of share calculation
Inspection Plan TQ75 QM formula parameters
Inspection Plan TQ75F Field names for QM formulas
Inspection Plan TQ75K Short text for Table TQ75F
Inspection Plan TQ75T Description of formula parameters
Inspection Plan
Qm in procurement QINF QM-info record for material and vendor
Qm in procurement TQ02 QM system definition
Qm in procurement TQ02A QM system assignment and QM system requirements
Qm in procurement TQ02B QM system
Qm in procurement TQ02T QM system description
Qm in procurement TQ02U Description QM system
Qm in procurement TQ04A Functions that can be blocked
Qm in procurement TQ04S QM block functions : texts
Qm in procurement TQ05 QM certificate categories for procurement
Qm in procurement TQ05T QM: text table for certificate types
Qm in procurement TQ08 Control of QM in procurement
Qm in procurement TQ08T QM: text for QM procurement keys
Qm in procurement TQ09 QM: agreement of QM document types
Qm in procurement TQ09T QM: agreement of QM document types
Qm in procurement TQ32A Inspection type to status assignment from status profile
Qm in procurement
QM in SD QVDM QM Info Record - QM Control in SD
QM in SD TQ32B Find insp.type for quality insp. for delivery note
QM in SD
Inspectio lot QALS Inspection lot record
Inspectio lot QALT Partial lot
Inspectio lot T156Q Movement Type: Material-Independent Control
Inspectio lot TQ30 Inspection types
Inspectio lot TQ30T Texts for inspection types
Inspectio lot TQ32 Assignment of inspection type to origin
Inspectio lot TQ32C Lot creation allowed values for the origin
Inspectio lot TQ32C _T Texts for lot creation indicator
Inspectio lot TQ33 Relevant fields for origin
Inspectio lot TQ34 Default values for inspection type
Inspectio lot
Inspection point QAPP Inspection point
Inspection point TQ79 Table with inspection point/user field combinations
Inspection point TQ79T Key words for inspeciton point user fields
Inspection point
Results Recording QAES Sample unit table
Results Recording QAKL Results table for value classes
Results Recording QAMR Characteristic results during inspection processing
Results Recording QAMV Characteristic specifications for inspection processing
Results Recording QASE Results table for the sample unit
Results Recording QASR Sample results for inspection characteristics
Results Recording QASV Sample specifications for inspection processing
Results Recording TQ12 Ind. external numbering for test units in results recording
Results Recording TQ12T Texts for the ind. for ext. numbering of units to be insp.
Results Recording TQ70 Control table for results recording
Results Recording TQ70C Function codes for navigation from the char.overview screen
Results Recording TQ70E Screen-based processing tables
Results Recording TQ70F Navigation during results recording
Results Recording TQ70S Characteristic overview screen for results recording
Results Recording TQ73 Origin of results data
Results Recording TQ73T Texts for origin of results data
Results Recording TQ74 Recording configuration
Results Recording TQ74T Recording configuration
Results Recording TQ76 Processing status of inspection characteristics
Results Recording TQ76T Texts for the processing status of insp. characteristics
Results Recording TQ77 Attributes for the Inspection Characteristic
Results Recording TQ77T Text Tables for Attributes
Results Recording TQ78 Status-dependent processing table for insp. characteristics
Results Recording TQ78T Texts for the status-specific proc. table for insp. char.
Results Recording
Defects recording TQ84 Confirmation profile
Defects recording TQ84T Text table for confirmation profile
Defects recording TQ86 Report category for defects recording
Defects recording TQ86A Assignment report category for work center
Defects recording TQ86T Text table for report category
Defects recording V_T35 2B_F Generated table for view V_T352B_F
Defects recording
Usage decision QAMB QM: Link Between Inspection Lot and Material Document
Usage decision QAVE Inspection processing: Usage decision
Usage decision TQ06 Procedure for Calculating the Quality Score
Usage decision TQ06T Language-specific texts for Table TQ06
Usage decision TQ07M QM: Inventory postings with usage decision
Usage decision
Sample Mgmt QPRN Sample drawing of phys. samples
Sample Mgmt QPRS Master record for phys. samples
Sample Mgmt QPRVK Sample-drawing procedure
Sample Mgmt QPRVK T Header for sample drawing procedure texts
Sample Mgmt QPRVP Sample-drawing items
Sample Mgmt QPRVP T Items for sample drawing procedure texts
Sample Mgmt TQ40 Definition of sample types
Sample Mgmt TQ40T Text table for sample type
Sample Mgmt TQ41 Storage locations for physical samples
Sample Mgmt TQ41T Texts for storage locations
Sample Mgmt TQ42 Physical sample containers
Sample Mgmt TQ42T Texts for phys. sample containers
Sample Mgmt
QMIS S068 Vendor statistics
QMIS S069 Material statistics
QMIS S097 QM notifications: Matl anal.
QMIS S098 QM notification: Vendor anal.
QMIS S099 QM notifications: Cust. anal.
QMIS S100 Problems: Material analysis
QMIS S102 Problems: Vendor analysis
QMIS S103 Problems: Customer analysis
QMIS S104 Customer statistics
QMIS S161 Inspection results: General
QMIS S162 Quantitative insp. results
QMIS S163 Quant. Insp. Result: Vendor
QMIS S164 Quant. Insp. Result: Vendor
QMIS S165 Inspection result: gen. custs
QMIS S166 Insp. Results: Quant. Customer
QMIS TQ55 Assign inspection lot origin for update group
QMIS TQ56 Definition of quality score classes
QMIS TQ56T Text table for the definition of quality score classes
QMIS TQ57 Assignment of quality score key to info structure
QMIS
Quality Certificates QCPR QM quality certificates in procurement
Quality Certificates I000 Conditions for certificate profile
Quality Certificates KONDI Conditions: Data part for certificates
Quality Certificates QCVK Certificate profile header
Quality Certificates QCVM Certificate profile characteristic level
Quality Certificates QCVMT Certificate profile characteristic level: texts
Quality Certificates QCVV Certificate Profile: List of Preliminary Products
Quality Certificates TQ61 Result value origin for certificates
Quality Certificates TQ61T Origin of result values for certificates: texts
Quality Certificates TQ62 Output strategy for skip characteristics
Quality Certificates TQ62T Output strategy for skip characteristics: texts
Quality Certificates TQ63 Origin of insp. specs for certificates (function modules)
Quality Certificates TQ63T Origin of inspection specifications for certificates: texts
Quality Certificates TQ64 Origin of characteristic short text for certificates
Quality Certificates TQ64T Origin of characteristic short text for certificates: texts
Quality Certificates TQ65 Certificates: Combinations allowed for origins, specs/values
Quality Certificates TQ67 Certificate-Relevant Output Types
Quality Certificates
Quality Notification QMEL Notification header
Quality Notification QMFE Item
Quality Notification QMSM Task
Quality Notification QMMA Activities
Quality Notification T352C Catalog types for each catalog profile
Quality Notification TQ81 Notification Scenario
Quality Notification TQ81V Usage of parts
Quality Notification TQ81V_T Texts for usage of parts
Quality Notification TQ81_T Texts for Notification Scenarios
Quality Notification TQ82 Change of Notification Type
Quality Notification TQ83 Partner Functions for Codes
Quality Notification TQ85 Function table for follow-up functions
Quality Notification TQ85R Rules for Follow-Up Functions
Quality Notification TQ85_T Action box text table
Quality Notification TQ8CO Assignment of reference orders to notification type
Quality Notification
Other Objects MARA Material Number
Other Objects T001W Plant
Other Objects LFA1 Vendor
Other Objects KNA1 Customer
Other Objects AUFK Order Number
Other Objects SAFK Run Schedule Header Number
Other Objects MCH1 Batch Number
Other Objects MCHA Batch Record
Other Objects EKKO Purchasing Document Header
Other Objects EKPO Purchasing document Item
Other Objects EKET Delivery Schedule
Other Objects VBUK Delivery Header
Other Objects VBUP Delivery Item
Other Objects CSKS Cost Center
Other Objects EQUI Equipment Number
Transaction List:
Q000 Quality management
QA00 Quality inspection
QA01 Create Inspection Lot
QA01A Create Inspection Lot
QA02 Change Inspection Lot
QA02A Change Inspection Lot
QA03 Display inspection lot
QA05 Job planning: Periodic inspection
QA06 Job overview: Periodic inspection
QA07 Trigger for recurring inspection
QA07L Deadline Monitoring Log
QA08 Collective Processing of Insp. Setup
QA09 No. range maintenance for insp.lots
QA10 Trigger automatic usage decision
QA10L Log for Automatic Usage Decision
QA11 Record usage decision
QA12 Change usage decision with history
QA13 Display usage decision
QA14 Change UD without history
QA16 Collective UD for accepted lots
QA17 Job planning for auto usage decision
QA18 Job overview for auto usage decision
QA19 Automatic usage decision
QA22 Change inspection point quantities
QA23 Display insp.point quantities
QA32 Change data for inspection lot
QA32WP QA32 -Call from Workplace/MiniApp
QA33 Display data for inspection lot
QA40 Auto. Usage Decision for Production
QA40L Log for Automatic Usage Decision
QA41 Scheduling UD for Production Lots
QA42 Job planning: UD prod. insp.lots
QA51 Scheduling Source Inspections
QA52 Source inspections: Job overview
QAC1 Change insp. lot actual quantity
QAC2 Transfer stock to insp. lot
QAC3 Reset sample
QAER Display archive objects
QAS1 Download Insp. Specs. (Obsolete)
QAS2 Download Basic Data (Obsolete)
QAS3 Upload Results (Obsolete)
QAS4 Upload UD (Obsolete)
QC01 Create certificate profile
QC02 Change certificate profile
QC03 Display certificate profile
QC06 Immediate delete of cert. profiles
QC11 Create cert. profile assignment
QC12 Change cert. profile assignment
QC13 Display cert. profile assignment
QC14 Create cert.prof.assign.w/copy model
QC15 Create cert. profile assignment
QC16 Change cert. profile assignment
QC17 Display cert. profile assignment
QC18 Create cert.prof.assign.w/copy model
QC20 Certificates for Deliveries
QC21 Quality certificate for the insp.lot
QC22 Quality Certificate for Batch
QC31 Archive display: Delivery item
QC32 Archive display: Inspection lot
QC40 Internet Certificate for Delivery
QC40A Internet Certificate for Delivery
QC42 Batch certificate on WWW
QC51 Create certificate in procurement
QC52 Change certificate in procurement
QC53 Display certificate in procurement
QC55 Worklist: Certificates - Procurement
QCC0 QM: Direct Access to IMG
QCC1 Direct Access to IMG: Notification
QCC2 IMG Direct Access: QM Q-Notification
QCC3 IMG Direct Access: QM Q-Inspection
QCC4 IMG Direct Access: QM Q-Planning
QCC5 IMG Direct Selection: QM Bus. Add-In
QCC_STABI Copy Stability Study Customizing
QCC_STABI_NK Copy Stability Study Number Ranges
QCCC QM standard settings complete
QCCF QM standard forms
QCCK QM standard settings: Catalogs
QCCM QM std. settings: Qual. notifs.
QCCN QM standard number ranges
QCCP QM std. settings: Quality planning
QCCS QM sampling schemes
QCCT QM standard texts
QCCU QM standard settings: Environment
QCCW QM std. settings: Quality inspection
QCCY Transport QM tolerance key
QCCZ QM std. settings: Qual. certificates
QCE2 Edit Communication Support
QCE3 Display Communication Support
QCYF QM standard forms (general)
QCYT QM standard texts (general)
QD21 Mark completed notifications
QD22 Archiving Notifications: Archive
QD24 Archiving Notifications: Delete
QD25 Archiving Notifications: Admin.
QD33 Delete quality level
QD34 Delete quality level planning
QD35 Delete job overview for Q-levels
QDA1 Edit sampling type
QDA3 Display sampling type
QDB1 Maintain allowed relationships
QDB3 Display allowed relationships
QDH1 Q-level evaluation: Change data
QDH2 Q-level evaluation: Display data
QDL1 Create quality level
QDL2 Change quality level
QDL3 Display quality level
QDM1 Edit valuation mode
QDM3 Display valuation mode
QDP1 Create sampling scheme
QDP2 Change sampling scheme
QDP3 Display sampling scheme
QDR1 Create dynamic modification rule
QDR2 Change dynamic modification rule
QDR3 Display dynamic modification rule
QDR6 Disp. where-used list-dyn. mod. rule
QDR7 Replace dynamic mod. rule used
QDV1 Create sampling procedure
QDV2 Change sampling procedure
QDV3 Display sampling procedure
QDV6 Uses: Sampling procedures
QDV7 Replace sampling procedure used
QE00 Quality Planning
QE01 Record characteristic results
QE02 Change characteristic results
QE03 Display characteristic results
QE04 Record sample results
QE05 Change sample results
QE06 Display sample results
QE09 Indiv.display of charac.result
QE09WP Call QE09 from Workplace
QE11 Record results for inspection point
QE12 Change results for inspection point
QE13 Display results for inspection point
QE14 Record results for delivery note
QE15 Change results for delivery note
QE16 Display results for delivery note
QE17 Record results for equipment
QE18 Change results for equipment
QE19 Display results for equipment
QE20 Record results for funct. location
QE21 Change results for funct. location
QE22 Display results for funct. location
QE23 Record results for phys. sample
QE24 Change results for phys. sample
QE25 Display results for phys. sample
QE29 No. Range Maint.: Conf. No. for Char
QE51 Results recording worklist
QE51N Results Recording Worklist
QE52 Worklist: Results for phys. sample
QE53 Worklist: Record results for equip.
QE54 Worklist: Results for funct. loctns
QE71 Tabular res. recording for insp. pts
QE72 Tabular Results Rec. for Insp. Lots
QE73 Tabular res. recording for characs.
QEH1 Worklist for Mobile Results Rec.
QEI1 Displaying QM Interfaces Appl. Log
QEI2 Deleting QM Interfaces Appl. Log
QEW01 Results Recording on Web
QEW01V Variant Maint.: Recording on Web
QF01 Record defect data
QF02 Change defect data
QF03 Display defect data
QF11 Record defects for inspection lot
QF21 Record defects for operation
QF31 Record defects for characteristic
QG09 Maint. num. range Q control charts
QGA1 Display quality score time line
QGA2 Display inspection results
QGA3 Print inspection results
QGC1 Qual. control charts for insp. lots
QGC2 Control charts for task list charac.
QGC3 Control charts for master insp. char
QGD1 Test Equipment Usage List
QGD2 Test Equipment Tracking
QGP1 Results history for task list charac
QGP2 Results History for Task List Charac
QI01 Create quality info. - purchasing
QI02 Change qual.information - purchasing
QI03 Display quality info. - purchasing
QI04 Job planning for QM procurement keys
QI05 Mass maintenance QM procurement keys
QI06 QM Releases: Mass maintenance
QI07 Incoming insp. and open pur. orders
QI08 Job overview of QM procurement keys
QISR Internal Service Request
QISR1 Internal Service Request - Forms
QISR_PCR60 vc_scenario for Message type 60(PCR)
QISR_SM29 ISR Customizing: Table Transfer
QISR_SR12_START Suggestion System
QISRSCENARIO Customizing Szenario
QISRTRANSPORT ISR Customizing Transport
QISRW Internal Service Request on the Web
QK01 Assign QM order to material
QK02 Display assigned QM orders
QK03 Maintain specs. for order type
QK04 Create QM order
QK05 Confirmed activities for insp. lot
QL11 Mat: Distribute Inspection Setup-ALE
QL21 Master Inspection Characs (ALE)
QL31 Distribute Inspection Methods (ALE)
QL41 Distribute Code Groups (ALE)
QM00 Quality Notifications
QM01 Create quality notification
QM02 Change quality notification
QM03 Display quality notification
QM10 Change list of quality notifications
QM10WP QM10 - Call from Workplace/MiniApp
QM11 Display List of Qual. Notifications
QM12 Change list of tasks
QM13 Display list of tasks
QM13WP QM13 - Call from Workplace/MiniApp
QM14 Change list of items
QM15 Display list of items
QM16 Change activity list
QM17 Display activity list
QM19 List of Q Notifications, Multi-Level
QM50 Time line display Q notifications
QMW1 Create quality notification (WWW)
QP01 Create
QP02 Change
QP03 Display
QP05 Print inspection plan
QP06 List: Missing/unusable insp. plans
QP07 List: Missing/Unusable GR InspPlans
QP08 Print task lists for material
QP11 Create reference operation set
QP12 Change reference operation set
QP13 Display reference operation set
QP48 Number Ranges for Physical Samples
QP49 Number range for phys. samp. drawing
QP60 Time-related development of plans
QP61 Display change documents insp.plan
QP62 Change documents ref.operation sets
QPIQS8 QM MiniApp Selection Variant
QPIQS9 QM MiniApp Selection Variant
QPNQ Number ranges for inspection plans
QPQA32 QM MiniApp Selection Variant
QPQGC1 QM MiniApp Selection Variant
QPQM10 QM MiniApp Selection Variant
QPQM13 QM MiniApp Selection Variant
QPR1 Create physical sample
QPR2 Change physical sample
QPR3 Display physical sample
QPR4 Confirm physical sample drawing
QPR5 Manual inspection lots for physSamps
QPR6 Create new phys.-samp. drawing w.ref
QPR7 Storage Data Maintenance
QPV2 Maintain sample drawing procedure
QPV3 Display sample drawing procedure
QS21 Create master insp. characteristic
QS22 Create master insp. charac. version
QS23 Change master insp. charac. version
QS24 Display master insp. charac. version
QS25 Delete master insp. charac. version
QS26 Display characteristic use
QS27 Replace master insp. characteristic
QS28 Display insp. charac. list
QS29 Maintain characteristic number range
QS31 Create inspection method
QS32 Create inspection method version
QS33 Change inspection method version
QS34 Display inspection method version
QS35 Delete inspection method version
QS36 Display inspection method use
QS37 Central replacement of methods
QS38 Display inspection method list
QS39 Maintain method number range
QS41 Maintain catalog
QS42 Display catalog
QS43 Maintain catalog
QS44 Maintain catalog
QS45 Display catalog
QS46 Display code group use
QS47 Central replacement of code groups
QS48 Usage indicator - code groups
QS49 Display code groups and codes
QS4A Display catalog
QS51 Edit Selected Sets
QS52 Display selected set index
QS53 Maintain individual selected set
QS54 Maintain selected set
QS55 Display selected set
QS58 Usage indicator - selected sets
QS59 Display selected sets
QS61 Maintain material specification
QS62 Display material specification
QS63 Maintain material spec: Planning
QS64 Display material spec: For key date
QS65 Activate material specification
QS66 Plan activation of material spec.
QS67 Job overview: Activate mat. spec.
QSR5 Archive inspection plans
QSR6 Delete routings
QST01 Create Stability Study
QST03 Display Stability History
QST04 Display Inspection Plans
QST05 Graphical Scheduling Overview
QST06 Scheduling Overview (StabilityStudy)
QST07 Change Testing Schedule Items
QST08 Display Testing Schedule Items
QSUB Define subsystems
QT00 Test Equipment Management
QT01 Test equipment management
QTSA Product Allocations: Send Quantities
QTSP Product Allocations:Send Customizing
QUERY_BP_FSBPBILDER BP: Screen Customizing for Query
QV01 Create quality assurance agreement
QV02 Change quality assurance agreement
QV03 Display quality assurance agreement
QV04 Find Quality Assurance Agreement
QV11 Create technical delivery terms
QV12 Change technical delivery terms
QV13 Display technical delivery terms
QV14 Search technical terms of delivery
QV21 Create QA agreement (DocType Q03)
QV22 Change Q-agreement (doc. type Q03)
QV23 Display Q-agreement (doc. type Q03)
QV24 Find Q-agreement (doc. type Q03)
QV31 Create Q-spec. (doc.type Q04)
QV32 Change Q-specification (docType Q04)
QV33 Displ. Q-specification (docType Q04)
QV34 Find Q-specification (doc. type Q04)
QV51 Create control for QM in SD
QV52 Change control for QM in SD
QV53 Display control for QM in SD
QVM1 Inspection lots without completion
QVM2 Inspection lots with open quantities
QVM3 Lots without usage decision
QZ00 Quality Certificates
Hope this will help.
Regards,
Naveen.

Separate table and figure numbering sequences

I need some pointers and guideance on how to setup autonumbering for tables and figures separately. As it is, the number sequence advances upon usage by a table or a figure. For example, Table 1, Figure 2, Figure 3, Table 4. What I need in that case is Table 1, Figure 1, Figure 2, Table 2.

Steve,
The easisest way is to use what's called a series indicator for you autonumber sequence. This consists of a single letter at the star of the autonumber. Typically, one could use F:<n+> for figures and T:<n+> for tables. FM will then number these streams differently. You can make things more complex in your setup (and much easier for the authors) using a numbering matrix where parent heading tags reset the lower level counters (which is what Peter was alluding to).
See:
http://www.freeframers.org/archive/99/msg00281.html
http://help.adobe.com/en_US/FrameMaker/9.0/Using/WSF176D8C8-8133-4860-88E3-AF69262623F0.ht ml
http://www.techcomplus.com/reference/autonumbering.pdf
http://www.microtype.com/resources/articles/AUTONUM_DE.PDF
http://www.infocon.com/files/autonum.pdf

Link information from tables and show the "best " box.

Hello! I'm totally new to this great software and the truth is I'm lost D:
I try to explain in more detail what I have to do, I hope you can help me please it's urgent T_T
I must make 3 tables should be linked to each other , ie a table where the name of a user will be manually enter, another where you manually enter the last name of a user and the third which will automatically enter the power of each user (for the automatic entry i will use a random data ) . Each table will have a box number , for example :
Table 1, Box 1: Paul
Table 2, Box 1: Gate
Table 3, Box 1: 3.74
Table 1, Box 2: Miguel
Table 2, Box 2: Ramos
Table 3, Box 2: 4.99
Table 1, Box 3: Maelle
Table 2, Box 3: Branco
Table 3, Box 3 : 4.98
I mean, I link the box to a table with the other three . And given that the program must compare the data in Table 3 (power ) and display data from the best user ( who has the highest power). In this example, the program should display :
BEST USER :
NAME: MIGUEL RAMOS
POWER: 4.99
(Is not nessesary save the information when i will close the program)
I do not know if I 'm asking a lot , I have a very clear idea in my head of what I have to do , but being a new software for my not know how to implement it .
Thank you in advance for your help and quick and ilustrative response! xD
Solved!
Go to Solution.

Hi Miguel_Exe
-Please check the snippet it does exactly what you said.
-The Box 1,2,3 you mentioned are array indices.For example if you use table_1 and index it with 0(Yes, arrays index starts from 0), you will get first element which is Miguel-Vi used is Index Array.
-For linking you can use string concatenation. Get each element from array using proper index and use Concatenate Strings.
-I am getting the last Numerical Table and passing it to Array Max and Min to get where maximum value is and using same index (Box value) am getting full name.
Thanks
uday,
Please Mark the solution as accepted if your problem is solved and help author by clicking on kudoes
Certified LabVIEW Associate Developer (CLAD) Using LV13
Attachments:
Nearest_name.png ‏30 KB

How can I customize the Column Headers of the TABLE control/indicator in LabVIEW ?

I need to customize the TABLE control/indicator in the LabVIEW as the same shape of the table in the LabWindows CVI or the DBgrid of the Borland Delphi. Where can I modify the color and shape of the Column Headers and the Row Headers.
Thanks,
Cleber

Salutations,
You asked this question about 3 months ago, and no one answered it.. How rude of them, well....
You can customize any control/indicator by right mouse clicking on it, going to advanced, then customize. If you want to color it, you can always right mouse click with the shift key down, and pull up the painting tool stuff. Or use the tab key if you want to scroll through tools. I believe it's the tab key. Alright, i bet you've long since figured it out, but i couldn't resist.
Sincerely,
ElSmitho

PC_UI Switch in T77S0 Table and T582G

Hello All,
I know there are many threads on this topic, but the answer I am looking for was not in any of the threads. This is a very specific question:
We see that with this Grouping Value issue, we get an error on the iView something like "Grouping expected to be '10' whereas found....".
So is the solution to this issue, that you activate PC_UI switch in T77S0 table and run the RPUFIXDS report for existing master data? The gouping reasons are picked from the T582G table, so does this mean that activating the switch is good enough without having to run the RPUFIXDS report? The switch will take care of new records, but will it also take care of existing records?
We have not implemented CE, so do we really need this Grouping? The issue mainly is we have lots of employees with 2 PERNRS and we dont want our Master Data to get deleted because of running the RPUFIXDS report. Can we get around to have the ESS working without having to run this report? Will activating the switch but taking off the groupings in T582G solve this?
The bottomline is we want the ESS to work without the Grouping Value error, while at the same time not running the RPUFIXDS report (since we have lot of employees with more than 1 PERNRs linked via CP, which will get deleted because of this report)
Please let me know if I need to make myself more clear, and please help me understand this issue?
Thanks and Regards
Nakul

Hi Nakul,
For this issue, two notes are relevant: [783499|https://service.sap.com/sap/support/notes/783499] y [845592|https://service.sap.com/sap/support/notes/845592].
A set of actions are proposed to solve it, but that depends on your system config. So, i advise you read both notes carefully.
E.g. the CCURE PC_UI indicator is required for Concurrent Employment environments, but not for non-CE environments. Instead of that, check the reports mentioned in note 783499 (RPUFACECPRFN, RPUFACEVIEKN and RPUFIXDS), plus IVWID feature.
Also, in Master data side, for non-CE the UGR and MOL parameters should match with the country assignment of personnel area of the user.
Best regards

Tables and Indices

Similar Messages

Maybe you are looking for