Chart report Condition fields and Data fields

Hi all,
i have tried chart report by adding two condion fields and one data field, the report is more meaning full in this scenario. the first condition field is taken as x-axis, the 2nd condition fields is taken as legend.
while adding more condition fields and data fields, i feel its not showing meaningfull data.
can anyone explain how the condition fields and data fileds are manipulated by crystal report.
i am using CR XI R2 Server.
Thanks
Padmanaban V

i am using Crystal Report XI R2 RAS Embedded in my server.
as we can add any number condition fields programatically using the method
ConditionField.Add(FieldObj), i would like to know how these fields are manipulated internally by the RAS server.
that means, what is the significance of condition fieldobject 1, condition fieldobject 2,condition fieldobject 3 etc...
if i add more than two condition fields , RAS Chart Report always returns 0 as legend value for all legends.
Thanks in advance
Regards,
Padmanaban V
Edited by: Padmanaban Viswanathan on Dec 22, 2008 9:53 AM

Similar Messages

Key fields and data fields in a DSO ??

i have a question regarding key fields and data fields in a Standard DSO...
i am using 2 datasources to build a open sales report 2LIS_11_VASTH and 2LIS_11_VASTI i am pulling in data from these 2 data sources to a DSO and i am wondering what infoobjects should be in the key fields and data fields .....does this reflect back to table VBUK and VBUP tables and does the key field in the DSO have to be the key fields in VBUK and VBUP tables ???? or what really should be included as key fields and data fields ????
please help....

If you look at the various SD tables, VBELN and POSNR are commonly used as the document number and document line item.
For VBAP and VBUP, it's referring to the Sales Order Line Item with the columns VBELN and POSNR as the key for both tables. However, if you look at the LIPS table, which is the Delivery Line Item table, it too has VBELN and POSNR as the key. Likewise, the VTTP table, which is the Shipment Line Item table, also has VBELN and POSNR as the key.
While using RSOSFIELDMAP as a map is a fairly good "rule of thumb", it still needs to be used with a level of skepticism.

DSO - What key fields and data fields in dso

Hi experts,
I need to create a dso in between the cube and 2 data sources(2lis_11_vaitm, 2lis_12_vcscl) to stage the data. My question is: what key fields and data fields to choose for the dso? is there a standard dso to copy? please explain in detail the model to set up, whether to connect both the ds's to dso and then to cube or one ds to dso and the other to the cube. more details will help.

Check this for standard DSO:
http://help.sap.com/saphelp_nw04/helpdata/en/43/fcdc387f34384f94c3227baf3837a8/content.htm
Thanks...
Shambhu

Prerequsites for deciding Key fields and data fields

Hi
I would like to know the criteria to decide upon KEY fields and Data fields for an infoprovider.

Hi,
What is a Key field in a Database and How should I choose one?
Keys are crucial to a table structure for many reasons, some of which are identified below:
They ensure that each record in a table is precisely identified.
They help establish and enforce various types of integrity.
They serve to establish table relationships.
Datafields may be Charecteristics and it may be keyfigures
Regards,
Marasa.

Identify key fields and data fields

Hi
i have datasource 0co_om_cca_9 .
i want build 1 DSO, how can i identify what are key fields and data fields to build DSO based on that datasource.

Hi sunnel,
The DSO are like 2-D database tables.
We use the technical keys here in counterpart to the business keys in Infocubes.
The key fields are the one based on which the records are identified uniquely in the database table.
And the data fields are the ones which are aggrgated or summarised or overwritten based on the value in key filed.
For example:
The ID no.s of the employees will be unique and it can be used as a key field.
The feilds like the Salary taken by the employee every month :"SALARY"
and the no. of leaves they taken: " NO. OF LEAVES" can be used as data fields.
So that the salary or the leaves taken by a particular employee can be aggregated based on her/his ID no.
The key fields in DSO doesnty mean Key figures.The key field means any unique key or a key based on which the records are sorted in the DSO
And key figures are the data fields.Some of the Characteristics can also be data fields in DSO.
Please give points if u r satisfied wit the information
Also let me know if u hav any doubt and if any thing is wrong.
Regards,
Kalpana M

Defining Key -field and data fields

Hi all
i have to define Key-Fields and data-Fields for a DSO(say DSO3).
DSO1 is a combination of DSO2 and DSO3..
DSO1 and DSO2 are SAP defined DSOs.
DSO3 is a User defined DSO.
my assumption:
   DSO3 has 30 fields
   DSO2 has 16 fields.
   can i create the DSO3 with remaining 14 fields which is there in DSO1?
   or i have to create the DSO3 with 30 fields(all DSO1 fields).
can any body explain....
Thanks & Regards
krishna

The problem is not how many fields you create where, the issue is where is the data is going to come from.
Since you data is going from DSO3 to DSO1and if the field is already getting populated in DSO1 from DSO2, then you don't have to worry about populating those fields again, unless and otherwise you want to overwrite them.
Remember any fields exist in both DSO3 and DSO2 which overlapping will be overwritten by the latest update.
Again, going back to your question, you should consider does your datasource has missing fields (14 of them).
thanks.
Wond

Key Fields and Data Fields in ODS

Hi Guru's ,
Can u Explain what are Key Field's and Data Field's in ODS,and How they work.
Thanx in Advance.

Hi Pradeep,
An ODS key fields forms a unique combination of chars according to which data in the ODS will be summed up. Data fields are additional fields, chars or key figures.
For example, you have the following key fields:
Doc No, Doc line item (item no in the doc) and you load the following data:
Doc# Item# Amount CALDAY
1234 1        100       26.09.2005
1234 1        150       27.09.2005
1234   2        300      27.09.2005
1235   1        400      27.09.2005
The first two rows with the same key fields (1234-1) will be aggregated and into ODS will go amount of 250.
What I said is true if for Amount key figure the Add option is set.
But if you set an Overwrite option, then the second record will overwrite the first one and only amount of 150 will go to ODS!
But if CALDAY is also a key field, then into ODS will go all records without any aggregation, because key fields combination is different for all records.
So, ODS key fields choice and KFs settings are very important for data aggregation in the ODS.
Best regards,
Eugene

Key fields and data fields re-arranged

Hello SDN,
Which design contains more records due to it showing more granularity? :
1. ODS with more infoobjects assigned as Keys.
2. ODS with less infoobjects assigned as Keys.
assuming the total number of infoobjects remain the same.
Where data fields can contain characteristics that can be used as keys or non-keys, depending on choice of design.
My understanding is with more keys, less details available due to aggregation. Could you kindly help to confirm this is correct?
I need to ask this because I am trying to change the re-arrange the keys by putting data fields as keys but not sure how this will turn out / behave.
Thanks,
Suzie

Hi,
BUT! I cannot say that it will increase. That means, I think the record number remains the same!
I do not think that this is Right?
for ex:
1)
Key fields:
Billing document
Data Fields
Sales Office
Customer
Net sales
So in the update rules , you can see the Overwrite for all Data fields. If the sales office is chaged for a record , the the OLD value will be over written by new value. So Before and after change to the records, the no of records are equal to 1.
2)
Key fields:
Billing document
Sales Office
Data Fields
Customer
Net sales
So in the update rules , you can see the Overwrite for all Data fields(now not for 'Sales Office'). If the sales office is chaged for a record , the the OLD value will not be over written by new value. It creates 2 records in Active table with respect to one change in new table. So Before the change , the no of records was 1.now after change, the records' number becomes 3.
With rgds,
Anil Kumar Sharma .P

DSO - Key Fields and Data Fields

Hi
Do we need at least one data fields (assigned at least one object to data field at DSO)?? or to create update rule to load data to DSO??
Because I am trying to load data with out any objects at data fields or unable to create update rule - all because, at least I should have one object in data fields - right?? pls clarify this.
Thanks.

Hi Raju,
Yes you are right in understanding this.
-Vikram

ODS Key Fields and Data Fields

Hi Gurus,
While creating an ODS how do we decide whether a characteristic has to be defined as a key field or a data field.
Thanks,
KR

Hi KG,
Key fields in the DSO are the primary keys in the active data table, depending on the keyfields the data in the aggregates will be overwrited.
It depends on the requirement we will decide what are the keyfields has to be taken. To utilise the overwrite functionality of the DSO depending on the data which is coming into bw we take keyfields. If u are using DSO as a staging then u have to lookinto the corresponding tables of the DSO, what are the primary keys in those tables..
Khaja

Infoset Join condition on Key feilds and data fields

Hi Guys,
I have a requirement to biuld the Info set with join conditon on two DSO's the info objects which i am using in the JOin condition are defined as data fieds in one DSO and defined as key fields in another DSO, is it possible to define join condition on key fields and data fields.
The two info objects are
                       0AC_DOC_NO
                       0ITEM_NUM
These two info objects are defined as data fields in DSO :   0LIV_DS1   Invocie verificaion
                                                        key fields in DSO:    0FIAP_0o3 FI AP Line Item
Please suggest me is it possible to define join the condtion on the data fields and key feilds.
Thanks
Best regards
SG

Hi
yes you can create join, you will get any issue in reporting level.
example: Say i want to create Info Set on 0MATERIAL and Sales DSO.
In 0MATERIAL Info Object it is key filed, but in my DSO 0MATERIAL is data field.Still we can create
Creation of join is dependent on fields common in your source objects.
check out the below document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7?QuickLink=index&overridelayout=true
Regards,
Venkatesh
Edited by: Venkateswarlu Nandimandalam on Sep 27, 2011 2:26 AM

How to process reports with two different date fields

Morning all,
This question is somewhat similar to what I asked few days back. I created two different reports for two different departments (Credit Control and Free of Charge Control).
These two reports pull data from two different date fields and has different status check ups.
Few days back my director requested me if he can have both reports in one report. That is when I asked question from all of you regarding two reports.
Anyhow, that was created by implementing two sub reports however, the director asked me to combine the two different reports into one in such a way that the output records should be added up with each other hence one single report with all combined data of Credit Control and Free of Charges (not two sub reports in one report).
The problem here which I am getting is that, both reports uses two different date fields. I can live with two different statuses as that can be easily done within formula/RT however how to create a report with Report Selection Formula condition which looks in both date fields and produces results accordingly?
I have tried this by not putting any condition in report selection formula and ran the report, it produced total results from past 6 years.
Any ideas how to produce combined report which has two different date fields?
Many thanks in advance
Regards
Jehanzeb
What I

Charliy,
No the both dates are from two different databases, tables and fields. The Credit date field is from KLAB database under max table where as the FOC date field is from SAE database under maxmast table. Klab date is under credit2 table where as foc date is under order header table.
So its more like this:
Klab->Max-Credit2--->Credit_date
Sae->Maxmast->Order_header---Date entered.
two dates totally different tables, dbs
however, I will try your idea too and see if that works.
Regards
Jehanzeb

How to transfer SRM PO Condition Type and Custom fields to ECC?

Hi All,
I have a scenario to transfer SRM Line item condition types and few custom fields to ECC.
I have found the following things but structure 'CI_EKPODB' does not exists in ECC.
I am using 'SRM 5.00' and 'SAP ECC 6.0'.
NOTE: I have to transfer condition records when PO is getting created / modified.
1) Earlier I was planning to use BADI 'BBP_CREATE_BE_PO_NEW' in SRM and this will transfer the data to ECC in case of PO
    Creation.
               It contains the Condition fields to be passed to ECC.
But i am unable to implement the same, whenever i create implementation when i click 'Activate' its getting activate then after few seconds its getting deactivate, i think this is because this BADI is not allowed for multiple use and SAP has already made one implementation on the same.
2) I need to implement BADI 'BBP_ECS_PO_OUT_BADI' in SRM and 'BBP_PO_INBOUND_BADI' in ECC.
SRM BADI will pass verified field details to ECC as a custom fields
       It does not contains the Condition fields to be passed to ECC, so i was planning to pass the same as custom field(s).
ECC BADI 'BBP_PO_INBOUND_BADI' will be used to map the fields to correct place and this should work.
i need to modify the structures and pass all the custom fields (z-fields) - (CI_EKPODB but does not exists kindly suggest) as data.
Other required details:
      Transfer of PO does not supported by SAP for service PO's, any suggestion on the same?
Expecting quick reply from your end.
Thanks in advance.
Regards,
Hemant

Naresh,
Thanks for quick response.
My concern is this BADI 'BBP_CREATE_BE_PO_NEW' will trigger only in case of creation, not when PO is changes.
I have to transfer condition types and custom fields to ECC in both the case (create / change)
If i have to do this only in case of creation then i can pass Condition types / custom fields then i can use parameter 'CS_PO1_DOCUMENT' from method 'FILL_PO_INTERFACE1'.
this parameter contains 'IT_POCOND', 'IT_POCONDX' and 'IT_EXTENSIONIN' as parameter so my problem will be solved.
But i dont think this will trigger in both the cases and 2nd thing i cann't implement the BADI since its not marked for multiple use so i am unable to implement the same.
Kindly correct me if i am wrong.
Once again thanks for your reply.
Please suggest on the same.
Regards,
Hemant

Stablish conditions between a data field in a query

Hello all,
Firstly, I´ve got an infoCube "A" where every record has a field called "Init date" (date field) and another field called "finish date"
In a query (that retrieves data for the infoCube A) there is a pop up with a date that user must enter (interval). This query must show every record for which different conditions regarding interval date are carried out by init date and finish date.
For example:
User enter: 03.02.2007 -- 17.04.2007
Query must show every record where init date is minor than 03.02.2007 and finish date is greater or equal than 03.03.2007 and greater than 17.04.2007.
I think this must be done in BW exit but I don´t know abap code I must enter.
Anybody can help me?
Thanks a lot.
Carmen

If you want to restrict data for sertain period, and these values are entered in variable entry screen. Query will display only that data which satisfies the entered conditions.
What exactly you want ? Is,t this your requirement ?
Regards
SS

Data fields and key fields

Hi,
Data fields and key fields are same as Characteristcs and key figures? Or they are diffrerent?
Thanks,
Radha

HI
Key Fields = Acts as Primary Key for The ODS like Primary of Tables in R3.
Data fields = Apart from Key fields We consider rest as data fields.
Ususally we use Characteristic info Objects and Dates in Key Fields and Key figures in Data fields.
It's decisive factor for overwriting property of ODS or DOS.
Hope this helps.
Regards,
Rangzz
Edited by: Ranganath Kodiugane on Feb 7, 2009 12:14 PM

Chart report Condition fields and Data fields

Similar Messages

Maybe you are looking for