Key fields and non-key field of condition table

Hello Gurus,
what is key fields and non-key field of condition table?
thanks very much!

Key field
Each condition table contains keys that can be used for creating dependent condition records.
for example let take condition type PR00.
PR00 uses access sequence PR02 .
Access sequence PR02 has following tables associated with it namely 304, 305 & 306
When you create a conditon record for PR00 with transaction VK11 or VK31, you have a button 'key combination' which is nothing but fields associated with tables 304, 305 & 306.
In brief, Condition records are always created using specific keys. Condition tables are used to define the structure of the keys of a condition record.
Non key field
For example take condition table 144 - sales deal basic data.
Table 144 is associated with access sequence PBUD.
If you check the fields associated with this table (click technical view button), there are three fields at bottom which do not have 'key' check mark -KDATU, PLTYP, KSTAF
So, when you create a condition record for PBUD, system does not propose these 3 fields in 'key combination' and hence are non key fields.
Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme.

Similar Messages

Difference between Key figure and a Key field?

Difference between Key figure and a Key field?
Thanks,
Pramod

Hi,
Key fileds as just like your primary key of R/3 Tables.
Key figure are type of info object which is used to hold amout,value for your info providers..
check this link for key figures and there types...
http://help.sap.com/saphelp_bw31/helpdata/en/80/1a63b3e07211d2acb80000e829fbfe/frameset.htm
under "Tab Page: Aggregation". you can be able to find three aggregation options:
Minimum
Maximum
Sum
Types of non-cumulative keyfigures
Regards,
Viren.

Any Orjinal SAP Reports which has currency field and currency key

Hi Friends,
I am looking for a report which has currency field and currency key at selection screen. I want to learn how SAP do selection with currency. Can you say a transaction deal with my desire?
Thanks.

try report RFSSLD00
A.

Cumulative key figure and non cumulative key figure

Hi BW Expertz
Could any one give me the clarification about cumulative and non cumulative key figures .Why we go for cumulative key figure and non cumulative key figure.If any docs could u just mail to the following [email protected]
Thanx In advance
Best regards
sankar prasad

Cumulative values are those key figures (KF) that are cumulated using all characteristics, thus also using time.
Ex: Sales revenue, Quantity....
Non-cumulative values are those key figures that are measured in relation to a period in time; they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so called exception aggregation.
Ex: Number of employees, Inventory, Stock prices, Account balance,.....
AGGREGATION TAB
Non cumulatives are evaluated by non-cummulative values. Non-cummulative values are special key figures that are different from other key figures (cummulative values) in data transfers and saving as well as in aggregational behaviour. These are measured in relation to a period in time; that is to say, they cannot be meaningfully cumulated over time. Non-cumulative value are summaraized over-time using exception aggregation.
Non-cumulative values such as 'number of employess' are cumulated using characteristics such as 'cost center'. It does not make any sense, however, to cumulate the number of employees using different periods. The result at the end of any particular period would be the sum total of number of employees for each posting during the period. This would of course be wrong.
Instead, the aggregation of the KF can be defined as exception aggregation wherein an additional references characteristics is utilized to tell BW which value to use during the period, in this case, 0CALMONTH is used, in the above example, to indicate that only the last value of 0HEADCOUNT, updated by costcenter, is to be taken for any calender year and month.
Cummulative vs Non-Cumulatives
The purpose of non-cumulatives is to optimize the data transfer in BW, the data retention and the database access. The data transfer from OLTP to BW is minimized and only the meaningful data is saved and processed.
It is recommended that you use non-cumulative values for areas that dont change frequently such as warehouse stock or number of employees.
Non-cumulatives are modeled in BW using a non-cumulative value with the fields belonging to it for storing the non-cumulative or for inflows or outflows.
Non-cumulative values are stored with special KF that differ in terms of data transfers and aggregational behaviour.
Features of NON-Cumulative Values Transfering and Saving Data:
- NC values are mapped uisng one KF for NC changes or two KF for inflows and outflows.
-NC are transferred in an initialization run and the change runs that follow (initialization can also be omitted here)
- A non-cumulative value always has a time-related exception aggegation.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm
with Example
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
****Assign Points If Useful*********

How use non cumulative key figure and noncumulative key figure screenshot

how use non cumulative key figure and noncumulative key figure screenshot

Hello,
Please see this docs for Non-Cumulative and Snapshot scenario,
[How to Handle Inventory Management Scenarios in BW (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
[Non-Cumulative Values / Stock Handling|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366]
Thanks
Chandran

Qualifier and non qualifier fields

Hi,
What is the diff b/w Qualifier and non qualifier fields
Regards,
Ganga

Hi,
You can get a lot of information on Qualifier & Non- Qualifiers.
Please follow the link below for info:
http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
Go to->Repository Maintenence->Designing an MDM Repository-> Qualified Tables.
How to Consolidate Data in Qualified Tables (NW7.0) :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30380d0e-2f23-2a10-8f9d-da55511adbd8
SAP Network Blog: Taming the animal - Qualified Tables:
Taming the animal - Qualified Tables
Here is a link to the thread where you can understand the concept to Qualified tables:
Qualified table concept
After basic understanding, you can follow the links below for importing the data into Qualified Tables:
Importing Qualified Tables in MDM:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
Importing Qualified Tables and Main Table Data in a Single Step:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e
Hope this info helps.
Thanks and Regards
Nitin jain

A cmr-field and a cmp-field on the bean are using the same name. The names

Hi:
I am using weblogic 8.1 and MyEclipse 5.1.1. I am deploying my ear application through MyEclipse 5.1.1 as an ear file.
When I ran the following EJB QL:
SELECT OBJECT(p) FROM Product p.category = ?1
I get the following error:
n relation Category-Product, a cmr-field and a cmp-field on the bean are using the same name. The names of cmr and cmp fields must be unique.
It is basically complaining that I have a field
<cmr-field>
                         <cmr-field-name>category</cmr-field-name>
                    </cmr-field>
in my ejb-jar.xml and also the same category in the
<cmp-field><field-name>category</field-name></cmp-field>
field. The problem is that if I changed the value of the cmr-field, I have to add a get and set in my productLocal.java and when you do that you have to do the same in the ejb-jar.xml.
Here is my ejb-jar.xml:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>CategoryEJB</ejb-name>
<local-home>com.CategoryHomeLocal</local-home>
<local>com.CategoryLocal</local>
<ejb-class>com.CategoryBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>Category</abstract-schema-name>
     <cmp-field><field-name>categoryId</field-name></cmp-field>
<cmp-field><field-name>categoryName</field-name></cmp-field>
<cmp-field><field-name>picture</field-name></cmp-field>
<cmp-field><field-name>pictureWidth</field-name></cmp-field>
<cmp-field><field-name>pictureHeight</field-name></cmp-field>
<cmp-field><field-name>labelOn</field-name></cmp-field>
     <cmp-field><field-name>labelOff</field-name></cmp-field>
     <cmp-field><field-name>button</field-name></cmp-field>
<primkey-field>categoryId</primkey-field>
<security-identity><use-caller-identity/></security-identity>
          <query>
               <query-method>
                    <method-name>findCategory</method-name>
                    <method-params></method-params>
               </query-method>
               <ejb-ql>
                    SELECT OBJECT(c) FROM Category c
               </ejb-ql>
          </query>
     </entity>
     <entity>
<ejb-name>ProductEJB</ejb-name>
<local-home>com.ProductHomeLocal</local-home>
<local>com.ProductLocal</local>
<ejb-class>com.ProductBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>Product</abstract-schema-name>
     <cmp-field><field-name>productId</field-name></cmp-field>
<cmp-field><field-name>brandName</field-name></cmp-field>
<cmp-field><field-name>productDescription</field-name></cmp-field>
<cmp-field><field-name>purchasePrice</field-name></cmp-field>
<cmp-field><field-name>category</field-name></cmp-field>
<primkey-field>productId</primkey-field>
<security-identity><use-caller-identity/></security-identity>
          <query>
               <query-method>
                    <method-name>findProduct</method-name>
                    <method-params>
                    <method-param>com.CategoryLocal</method-param>
                    </method-params>
               </query-method>
               <ejb-ql>
                    SELECT OBJECT(p) FROM Product p.category = ?1
               </ejb-ql>
          </query>
     </entity>
</enterprise-beans>
<relationships>
               <ejb-relation>
               <ejb-relation-name>Category-Product</ejb-relation-name>
               <ejb-relationship-role>
                    <ejb-relationship-role-name>
                         Category-has-many-Product-numbers
                    </ejb-relationship-role-name>
                    <multiplicity>one</multiplicity>
                    <relationship-role-source>
                         <ejb-name>CategoryEJB</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>productNumbers</cmr-field-name>
                         <cmr-field-type>java.util.Collection</cmr-field-type>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <ejb-relationship-role-name>
                         Product-belongs-to-Category
                    </ejb-relationship-role-name>
                    <multiplicity>many</multiplicity>
                    <cascade-delete/>
                    <relationship-role-source>
                         <ejb-name>ProductEJB</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>category</cmr-field-name>
                    </cmr-field>
               </ejb-relationship-role>
          </ejb-relation>
</relationships>
<assembly-descriptor>
<security-role>
<role-name>Employees</role-name>
</security-role>
<method-permission>
<role-name>Employees</role-name>
<method>
<ejb-name>CategoryEJB</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>CategoryEJB</ejb-name>
<method-name>*</method-name>
</method>
<method>
<ejb-name>ProductEJB</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Here is my weblogic-cmp-rdbms-jar.xml:
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-rdbms20-persistence-810.dtd'>
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
     <ejb-name>CategoryEJB</ejb-name>
<data-source-name>ShoeStore</data-source-name>
     <table-map>
          <table-name>category</table-name>
          <field-map>
          <cmp-field>categoryId</cmp-field>
          <dbms-column>categoryID</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>categoryName</cmp-field>
          <dbms-column>categoryName</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>picture</cmp-field>
          <dbms-column>Picture</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>pictureWidth</cmp-field>
          <dbms-column>PictureWidth</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>pictureHeight</cmp-field>
          <dbms-column>PictureHeight</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>labelOn</cmp-field>
          <dbms-column>LabelOn</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>labelOff</cmp-field>
          <dbms-column>LabelOff</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>button</cmp-field>
          <dbms-column>Button</dbms-column>
          </field-map>
</table-map>
<automatic-key-generation>
<generator-type>SQL_SERVER</generator-type>
</automatic-key-generation>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
     <ejb-name>ProductEJB</ejb-name>
<data-source-name>ShoeStore</data-source-name>
     <table-map>
          <table-name>PRODUCT</table-name>
          <field-map>
          <cmp-field>productId</cmp-field>
          <dbms-column>productId</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>brandName</cmp-field>
          <dbms-column>brandName</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>productDescription</cmp-field>
          <dbms-column>productDescription</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>purchasePrice</cmp-field>
          <dbms-column>purchasePrice</dbms-column>
          </field-map>
          <field-map>
          <cmp-field>category</cmp-field>
          <dbms-column>categoryId</dbms-column>
          </field-map>
</table-map>
     
<automatic-key-generation>
<generator-type>SQL_SERVER</generator-type>
</automatic-key-generation>
</weblogic-rdbms-bean>
<weblogic-rdbms-relation>
     <relation-name>Category-Product</relation-name>
<weblogic-relationship-role>
<relationship-role-name>Product-belongs-to-Category</relationship-role-name>
          <relationship-role-map>
<column-map>
<foreign-key-column>categoryId</foreign-key-column>
<key-column>categoryID</key-column>
</column-map>
          </relationship-role-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
</weblogic-rdbms-jar>
Here is my productLocal.java:
package com;
import javax.ejb.CreateException;
import javax.naming.NamingException;
import java.util.Date;
import java.util.Vector;
import java.util.Collection;
public interface ProductLocal extends javax.ejb.EJBLocalObject
     public Integer getProductId();
     public void setProductId(Integer productId);
     public String getBrandName();
     public void setBrandName(String brandName);
     public String getProductDescription();
     public void setProductDescription(String productDescription);
     public Double getPurchasePrice();
     public void setPurchasePrice(Double purchasePrice);
public CategoryLocal getCategory();
     public void setCategory(CategoryLocal category);
Here is my ProductBean.java:
package com;
import javax.naming.InitialContext;
import javax.ejb.EntityContext;
import javax.ejb.CreateException;
import javax.naming.NamingException;
import java.util.Date;
import java.util.Collection;
import java.util.Iterator;
import java.util.Vector;
import java.lang.Integer;
public abstract class ProductBean implements javax.ejb.EntityBean
     public Integer ejbCreate(Integer id)
          this.setProductId(id);
          return null;
     public void ejbPostCreate(Integer id)
     //public abstract Integer getCategoryId();
//     public abstract void setCategoryId(Integer categoryId);
     public abstract CategoryLocal getCategory();
     public abstract void setCategory(CategoryLocal category);
     public abstract Integer getProductId();
     public abstract void setProductId(Integer productId);
     public abstract String getBrandName();
     public abstract void setBrandName(String brandName);
     public abstract String getProductDescription();
     public abstract void setProductDescription(String productDescription);
     public abstract Double getPurchasePrice();
     public abstract void setPurchasePrice(Double purchasePrice);
     public void setEntityContext(EntityContext ec)
          System.out.println("ProductBean setEntityContext");
     public void unsetEntityContext()
          System.out.println("ProductBean unsetEntityContext");
     public void ejbLoad()
          System.out.println("ProductBean ejbLoad");
     public void ejbStore()
          System.out.println("ProductBean ejbStore");
     public void ejbActivate()
          System.out.println("ProductBean ejbActivate");
     public void ejbPassivate()
          System.out.println("ProductBean ejbPassivate");
     public void ejbRemove()
          System.out.println("ProductBean ejbRemove");
What do I needed to do to fix this problem.
Any hint or help would be greatly appreciated!!!
Yours,
Frustrated

cmr field which is "category" in ur mapping , u can't use as cmp field in abstract schema mapping. just remove category from cmp field . and every thing is fine

Unique Field as Non-Qualifier in Qualified Flat Table

Hi experts,
I have the requirement to store the customer data regarding company code in the qualified flat:
customer have different data related on company code. It's important that this company code have to be unique in this qualified flat. (e. g. one customer have data with company code 3850, 3860 and 3870, its not allowed to store further data with the same company code 3850).
In the console I set the company code as unique and non-qualifierer field. But afterwards I was able to put two records with the same company code in this lookup qualified flat table.
What did I wrong? ( I use MDM 5.5 SP 6 Patch 3).
Best regards,
Nico

Hello,
the behaviour depend of the settings for qualified upadate.
(Set Qualified Update sub-menu when define mapping in import manager)
Settings can be:
- Append
- Replace
- Update
In your, case looks to be "Update". be sure the Set Matching Qualifier is righly set for the qualifier which indentify the relation to the flat data. (sometimes have to clean this point)
Check New links are : Create and Existing Links are : Update (All Mapped Qualifiers)
Hope helps you
best regards
Vincent

User Exit for validating overall limit field and expected limit field-ME2xN

Dear Gurus,
Can you please suggest me any user exit or BAdi to validate the overall limit field and expected limit field in transaction ME2xN.
Or any other way to to achieve this functionality in ME2xN.
Our Requirement is while raising a service PO in the Limits tab the 'Overall limit' should be same as 'Expected Value', at present the user can enter overall limit greater than 'Expected Value'.
Regards,
Priyank Joshi

this will not work. you cannot add another structure (AUFK) on top of CEBAN. all characteristics have to be of one structure and since you want to release a PR it has to be CEBAN. before attempting to program something around that why do you not go to tx. OLME -> PR -> Release Strategy -> With Classfication -> Release Strategie and run it in a simulation mode. you will then see how it reacts.
there's a white-paper on service.sap.com explaning in detail release-strategies. it's a good one and a good read too!

Field catalog not appearing in the condition table for output determination

Hello,
I wanted to include WBSTK as a condition table entry in the output determination for outbound deliveries, WBSTK is available as field catalog , but not available during condition table creation.
Can you pls help me out?
Regards
Vaidee

Check OSS Notes
379619 - Preference process in SD order: Prefrnc ID missing
595984 - Preference indicator in SD order
379269 - Preference in SD doc: User exit: Set pref. indicator PREFE
Regards

Profit center field and internal order field in sales order

Hello all,
I am unable to find the settings for profit center field and internal order field in sales order account assignment tab screen. kindly let me know the path and configuration settings.
Thanks in advance
Regards
srinivas

Hi Srinivas
If you want to assign the profit center then make sure that the Profit center is assigned in MMR->Sales orgn 1 view .
But to assign the Profit center in MMR also you need to configure the Profit center first for your Material in your company code with the help of FI/CO consultants and then assign then the profit center will flow from MMR to sales order item data->account assignment tab
Regards
Srinath

Key fields are not visible in output condition table

Hi,
     I have created few conndition tables using V/61. But i can not see Key field. It is not displaying. But when I check thru VK11 i can see that all fields are marked as key fields. example of table B018.
My problem is that , i want to make few filed non key fields rest of fileds as key fields so that there should not be any duplicate ntry based on key fields. also I do not want to maintain these two fields for each record.
Is there any exit to modify and view thesefields? or it is a security issue...bold
Your earliest response is highly appreciated.\
Thanks,
AKS

Hi Raga,
Please check the documentation under the customizing path:
IMG -> Sales and Distribution -> System Modifications ->
Create New Fields (Using Condition Technique) ->
New Fields For Pricing
Then click on the paper icon
Here is explained how to setup additional fields for pricing,
not present in the standard.
Notice the following rules:
1. the new fields must have name beginning with 'ZZ' or 'YY' in order
   to avoid problem after upgrade
2. add the new field in the table T681F for the application 'V' and the
   usage 'A'
3. these new fields must be appened to the structures KOMKAZ or KOMPAZ
   (depending they are header or item fields)
4. you should provide these fields by implementing the userexits
   USEREXIT_PRICING_PREPARE_TKOMK (header fields)
   USEREXIT_PRICING_PREPARE_TKOMP (item fields)
   in program MV45AFZZ for sales order, RV60AFZZ for invoice.
In that documentation there are some examples too.
Please check it.
Regards,
Alex

Purchase Order Field and Cost Center Field Non Editable In F-48

Hi Friends,
I have a cretain requirmnet to make the PO and cost centre field non editable.I tried through shd0 bt it says i can only cretae Transcation variats for Dialiog tran.Please help
Regards,

Hi,
You can speak to your functional people. I think through SPRO "Maintain Field Status Variant' under Financial Accounting ->........
we can control this.

Mandatory and non-mandatory fields

Hi all,
Is it possible to have certain fields in VD01 mandatory for one user and the same fields are non mandatory for another user.If so, can anyone please explain it.
Thanks in advance
Sandeep

Hi,
In the customizing you can set up mandatory based on the account groups..But not for each user..Instead you can do it through user exit..
Check this user exit EXIT_SAPMF02D_001.
Thanks,
Naren

COPA Derivation based with target field as non-copa field

Hello experts,
There is a requirement to derive the Characteristic maintained in Classification view(AUSP table) in Material master based on material number.The target field into which the characteristic value needs to be populated is not in COPA(it is a non-copa field).
I tried to use table look up with AUSP table, but it is asking for values of certain key fields like
ATZHL(Characteristic value counter) MAFID(Indicator: Object/Class) and
KLART(Class Type), which are not there in COPA.
With the Enhancement in KEDR transaction, EXIT_SAPlKEDRCOPA_001 and Include ZXKKEU11, I created an enhancement step by giving the material as the key in the source fields.With that material number I can do a select on the AUSP table inside the include ZXKKEU11 and get the characteristic value. The problem i am facing is that the target field which stores the internal characteristic value is not there in COPA?And while creating a derivation rule, I can only select the COPA fields as target fields.
It's urgent....any suggestions please? Points will be rewarded for any useful answer.
Thanks,
Anky

Hi,
As far as I know the derivation functionality in COPA is meant for derivation of characteristic values to store them in a characteristic field.
If you splitt up the derivation in two steps it might be possible to use the USERTEMP fields, to store the information needed and to pass it on to an other lookup step as a key-reference.
Regards,
Roy

Key fields and non-key field of condition table

Similar Messages

Maybe you are looking for