Field in DSO 0BBP_QUO from Datasource 0BBP_TD_QUOT_1

Hi,
Please let me know if someone has any idea about transformation that needs to be done to get value for field 0SR_NOREJCT(Number of Rejections) from the various fields of datasource 0BBP_TD_QUOT_1 (bids) or any other datasources which may get the data for 0SR_NOREJCT.
Regards,
Joy
[email protected]

Create a new calculated key figure and in the properties tab click on enhance and set exception aggregation to count all values and then select an object giving you the status of the bid.
Then a delimited index with this and status = rejected (or whatever tells you that a specific item is a reject) will hold the count of rejects

Similar Messages

Update multiple rows of DSO from Datasource

Hi,
We have a custom DSO with 4 key characteristics. It is initially populated by a custom datasource correctly.
We now need to update some of the data fields using a standard datasource, but it only has two of the key fields available.
In the transformation from the datasource to this DSO, I have generated an internal table in the start routine to collect the additional two key fileds from the DSO table.
I was wondering if there is a way to loop through when loading to update all the rows for the other two keys?
e.g.
DSO - load from custom datasource:
K1 K2 K3 K4 D1 D2
a    b     c    d     1   2
a    b     e    f      3   4
standard datasource
K1 K2   D2
a   b      8
We would like to use the data from the standard datasource to update both rows in the DSO to populate data column D2 with the value 8.
Thanks!
Darryl

Darryl,
In case you dont want to create a new DSO, you can try this option.
Add the infosource between the standrad data source and DSO and this infosource should have the structure same
as the DSO.
The transfermations between DS and Infosource should be 1 to 1, But in the start routine of the transfermations between infosource and DSO , write the following logic.
- Declare an 2 internal tables same as the source_package.
- Read the DSO active table with key1 and key2 from source_package into the internal table1 declared above.
- Copy source_package contents to internal table2.
- delete the contents of source package.
- Loop at internal table 1 and populate key3 and key4 by reading internal table2.
- Modify source_package from internal table1.
Thanks,
Ravi.

Error while loading data from DataSource to InfoCube/DSO through DTP

Hi Friends,
I am trying to load data from DataSource to InfoCube/DSO through DTP and getting the following error:
Exception in substep: Extraction completed
Processing terminated
Data package 1 / 30.04.2009 22:38:30 / Status 'Processed with Errors'
When i see the detail message it says:
Syntax error in routine "convert_to_applstru", line 25 of generated program"
I checked all my transformation and looks ok. I was able to load data earlier and i getting this error all of sudden. Does some one know what is this routine "convert_to_applstru" ?
Thanks,
Amit

Hi Arun,
Where do i see this generated program in RSRV. I dont see this in RSRV. Please guide me.
Thanks,
Amit

No key field found for creation of DataSource - Classification Datasource

Hello,
While trying to create a clasiffication datasource based on 0PLANT_ATTR, when i assign a characteristic and push the DataSource button, i get the following message:
No key field found for creation of DataSource
Diagnosis
During generation of a classification or configuration DataSource, only those key fields for the object table (field "Obj.Tabelle") that are already present in the basis DataSource transferred to the extract structure. This is the case when none of the key fields of the object table were found in the structure of the basis DataSource.
System response
A DataSource cannot be created without key fields. The action was cancelled.
Procedure
Check whether you have selected the correct basis DataSource and object table. For more information, please see SAP Note 569849.
Do you know what can be the problem?
Thank you and regards

Hi Alberto,
plants are a special case. The key which is used for the classification
of plants (object type BETR) is not the same as the key which is used in
datasource 0PLANT_ATTR.
BETR has key LOCNR (Site). That's a customer related to a plant. The
customer number will be extracted in field LOCNR.
0PLANT_ATTR extracts the plant in its key field WERKS.
Transaction CTBW and the generic extraction program for classifications
don't know the relationship between LOCNR and WERKS. So they cannot map
them.
I do recommend a solution which would add the mapping between
LOCNR and WERKS:
1. Create please the classification datasource as intended, but use
datasource 0RT_LOC_MGR_ATTR as basis datasource. It's the only
datasource of the content where LOCNR is a key field. So
0RT_LOC_MGR_ATTR is used as a dummy here, to allow transaction CTBW to
create the classification datasource. It's not necessary to extract
data with datasource 0RT_LOC_MGR_ATTR.
2. Extend please the extract structure of the created classification
datasource. Add please field WERKS using component type WERKS_D. Make
this field visible.
3. Fill field WERKS in the extractor user exit EXIT_SAPLRSAP_002. WERKS
can be read from table KNA1 by using the customer number extracted to
LOCNR to select on field KNA1-KUNNR.
4. Transaction CTBW_META on the BW system isn't able to append the
characteristics from the classification datasource to infosource
0PLANT, because the keys are different. So create please a new info
source with CTBW_META. This allows CTBW_META to create the info objects
for the characteristics used in the classification datasource.
5. Add please the characteristics used in the classification datasource
to infosource 0PLANT manually. You will find the info object names of
the characteristics by looking up the characteristic datasources which
are assigned to the classification datasource in transaction CTBW. From
these names you can derive the info object names:
1CL_A... -> C_A...
6. Disconnect the infosource which has been created with CTBW_META from
the classification datasource.
7. Connect please the classification datasource to infosource 0PLANT
Use following info object:
info object   field
0PLANT       WERKS
The info object names for the characteristics are explained in step 5.
8. Add an infopackage to infosource 0PLANT for the classification
datasource.
Now the extraction of classifications of sites should work.
Best regards,
Rolf
P.S. I saw the system messed it up and doesn't display any new and empty lines. Sorry, I hope you still can read it.
Edited by: Rolf Doersam on Mar 26, 2010 6:56 PM

Data Fields & Key Fields IN DSO

Hi Guys,
Can any one tel me what exactly key field holds & Data field hold in DSO.
Thanks,
Venkatesh

Hi,
A DSO serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level. This data can be evaluated using a BEx query.
A DSO contains
Key fields (such as document number, document item) and data fields that, in addition to key figures, can also contain character fields (such as order status, customer). The data from a DataStore object can be updated with a delta update into InfoCubes (standard) and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.
Key fields : It will contains both Chars and KeyFigures.
Data Fields : Based on this i.e. the charecterisctics which you will keep in this Data Fields, the DSO will over write the Data in DSO.
Overwriting functionality will works based on Data Fileds.
http://help.sap.com/saphelp_nw2004s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm
Thanks
Reddy

Adding fields into DSO in the Key Fields

Hello Experts,
I am using a Cube which loads data from DSO. Now, for some requirement I have to add one field into DSO in the key fields Part. But DSO already has 16 fields which I cannot remove.
So how can I add one more field into DSO in this case?
The cube I am using is 0FIGL_C10 and the DSO is 0FIGL_O10.
Regards,
Nirav Shah

You can create an Infoobject - acts as a custom key to concatenate multiple fields into one and make it a keyfield.
15 fields + custom key ( concatenate 2 fields ) = 16 Keyfields
Procedure - > Example
16th Key - > RVERS-Version-CHAR-3-0VERSION
17th Key - > RMVCT-TransactnType- CHAR-3-0MOVE_TYPE
1. Create one infoobject - ZKEY - Length = 6 ( add lenghts of the two objects)
2. Make ZKEY as a keyfield for the DSO.
3. Make 16th Key and 17th Key datafields.
Create a routine for ZKEY in the transformation or transfer rules to concatenate values coming from source into one.
TRFN Routine
Concatenate SOURCE_FIELDS-RVERS SOURCE_FIELDS-RMVCT into RESULT.
Or
Transfer Rules Routine
Concatenate COMM_STRUCTURE-RVERS COMM_STRUCTURE-RMVCT into RESULT.
This way nodata will be lost/overwritten due to less number of keyfields in the DSO.
We have as many as 21 Keyfields for GL Totals DSO.

Addition of fields in ODS/Cube till Datasource

Hi All
Assuming, I hv a Datasource/copa Datasource replicated and connected till Cube/ODS with data in it,,and Now I am in a need to add extra fields in this pipeline, So plz guide me, on to add these extra fields starting from Datasources,Infosources,Info objects, Transformations(BI 7.0),TransferRules/Update Rules(BW 3.5) if any,,,and then finally Data targets.(ODS & CUBE)??
THANKS

Please search in SDN u will get lot of threads which are already discussed about the same....
Khaja

Key fields of DSO

Hi Experts,
I have a issue with DSO.We extracted data from R/3 in to BI and send it in to DSO.We are getting data from R/3 to PSA with right records with init load.But from PSA to DSO,we are getting duplicate records for 2 invoices.We have 2 invoices say xxxx01 and xxxx02 have problems in DSO.
XXXX01 has 3 items(10,20,30) created on April2008 with billing Doc type A
XXXX02 has 2 Items(10,11) created on April2008 with billing Doc type B
But in DSO we are getting extra Item record for each of document
i.e XXXX 01 has 4items(10,20,30,10).3 items(10,20,30) created on April 2008 with billing Doc type A.One Item(10) created on June 2008 with billing Doc Type C(this is not in R/3 so This extra one).
XXXX02 has 3 items(10,11,10) .First 2Items(10,20) are original ones created on April 2008 with Billing type B.One extra Item(10) created on June 2008 with Billing Doc Type C(this Item is not in R/3).
We have key fields in DSO is Sales Document,Material,Billing Item,Fiscal variant.I din't add Document Type,Document Category,Calender day in Key Fields but they are in Data Fields.
I am not sure how can I overcome this issue either adding Document type ,Calender day,Document Category in DSO or Put some fields in Semantic group.
Please advise me and tell me some possible solutions.
We ran setup tables with init and ran infoPackage and ran delta Infopackage too in Testing box.If I change the design in Dev box and Transport in to the test box,Hope I need to fill the Setup tables again right.Please advise me.
Thanks,
Ran.

Hi,
Use this key fields and sure it will solve.
Doc no.,Doc Item. for Orders
Bill Item and Bill no. for Invoices
Delivery No. and Delivery item no. for deliveries.
Moreover check ur transformations once.
Cheers,
shana

You do not have authorization to extract from DataSource ZZ_TD_EBAN COMPONE

Hi,
Iam facing the problem As
You do not have authorization to extract from DataSource ZZ_TD_EBAN COMPONENT.
ERROR IN SUBSTEP
ERROR IN SUBSTEP
Error reading the data of InfoProvider ZDP_VIRT..
I had created a Virtual Infoprovider. and taking the Dat source ZZ_TD_EBAN.
done the Trasf and DTP. for data source to cube. which was bulit in BI7..
i can see the flow AS Source system- datasource- virtual provider.
for virtual provider at run time it picks the data from source.
But when i rum the query on this VP iam getting error as
You do not have authorization to extract from DataSource ZZ_TD_EBAN COMPONE
even if i chek data at virtual provider level byclicking display Data..
after selecting the fields once i execute . there aso iam facing the same error. as
You do not have authorization to extract from DataSource ZZ_TD_EBAN COMPONENT.
Once i get in tthe error.. i can see the below msg.. but even though not able to solve .. i need your assistence.
You are not authorized to extract from DataSource ZZ_TD_EBAN in application component: MM .
System Response
The authorization check was performed with the following field values:
DataSource: ZZ_TD_EBAN
Application component: MM
Subobject: DATA
Activity: 03
Procedure
To be able to extract from the DataSource, you need authorization for authorization object S_RO_OSOA (authorizations SAPI-DataSource) with the field values specified above.
Procedure for System Administration
There is a role template S_RO_OSOA_TMPL (DataSource (OSOA) Display/Maintain/Extract) available that contains the authorizations to display, change and extract all DataSources.
Pls help mewith your valuable answer.

Hi ,
As given in your error message that S_RO_OSOA authorization object is missing . You need to include this auth object in the ID from which you are extracting the data using the TCODE : PFCG . You can ask the basis person to do so for you .
When you run any report on a virtual infoprovider , you need to give the authorization of the DTP & the transformations apart from your cube and datasource in PFCG so that it can display the output in the report . This setting is only necessary for virtual cubes.
You can always check the missing authorizations in tcode : SU53 .
Hope the above reply was helpful.
Kind Regards,
Ashutosh Singh

New deltas are not posted to BI from datasource:2LIS_12_VCITM

Hi All,
recently we integrated new sales organisation to our datasource: 2LIS_12_VCITM,but the data is not coming from this datasource:2LIS_12_VCITM
to BI system.this data is not coming to BI system,but data is available in r/3 tables: likp and lips tables. daily we are loading deltas to our bi system.Could you please provide us the table at r/3 side where i can check the settings of this datasource:2LIS_12_VCITM.
Thanks,
Vikarm.

Hi Vikram,
Below are tables where you can check for datasources:
In the Source System:
Table                         Description
ROOSOURCE            Header table for DataSources in the source system
ROOSFIELD              Specific fields for a DataSource in the source system
ROOSGEN                Generated objects for spcific DataSource in the source system
In the Business Warehouse system:
Table                                       Description
RSOLTPSOURCE                    Replicate Table for OLTP Sources in BW. For 3.X DataSources.
RSOLTPSOURCEFIE OLTP      Source Fields. For 3.X DataSources. I
RSDS                                      For 7.X DataSources.
RSDST                                    DataSource - Texts
Regards,
Ashvin

Add fiscalyear./period field in one of the datasource

I need your quick suggestion, how to create Function module and Write the code for a datasource. I want to add fiscalyear./period field in one of the datasource. please tell the logic which field and what table i will pick that. can you tell me the steps if i can create the function module and make alll enhancements in that FM for that datasource. Please write me quick step by step starting from se37 to create FM.
also if you have any abap code to add fiscalyear./period in datasource.
Will appreciate your help.
thanks
sincerely
Soniya

No need - just add fiscal year period to your cube and assign it cal day/posting date - whatever you want to calculate the fiscal period
Then the automatic time conversion will take care of the rest
You will need the fiscal year variant - if you don't have this - get it from the Company Code table in R3 (T001 or similar)

Units field WAERS for field NAVALUE is hidden for DataSource ..

Hi,
I am trying to change the DataSource but getting the error "Units field WAERS for field NAVALUE is hidden for DataSource ..".
It is not allowing me to get the field list to change after that.
Can anyone throw somelight on this issue please..
Thanks,
Hans

I solved this problem myself by writing ABAP program.
REPORT ZTEST.
TABLES ROOSFIELD.
DATA: ITAB LIKE ROOSFIELD OCCURS 0 WITH HEADER LINE.
SELECT * FROM ROOSFIELD INTO TABLE ITAB
WHERE OLTPSOURCE = 'DATASOURCE_NAME'
AND FIELD = 'WAERS'.
*update ROOSFIELD set SELECTION = 'X'.
*ENDSELECT.
Create a report program and update the value of field "SELECTION" as above.
Then try to make changes in RSO2 as it needed.
Let me know if you need my help..
Thanks,
Hanuma

Data fields in dso

Hi
If I need to calculate amount based on source and destination,and if these two source and destination fields char are there in data fields of dso and keyfigure amount is also in data fields of DSO can we get exact value if make report on this.
thx
rubane

Actually i need to build report where in rows there will be some char
like source plant and destination plant and in rows on the basis of source and destination the cummulated value of amount base on some other few restriction
now my question is :-
acc to my need I need to make genric extractor but one is already there which contains all my fields. now can i use the same extractor,but the worry is ;these all feilds are first going in dso and all are there in data fields coloumn
What I'm thinking is; it will suppress or accumulte records on the basis of key field's(as usual).
so can you pls let me know what to do in this scenario?
how to build a new report using existing extractor ;can i use existing one?
rubane

Reg Data fields in DSO

Hello SAP Guru's!!!!
I have some doubt on maximum number of data fields in DSO. I gone through so many threads on SCN, but could not clarify my doubt.
The max no of key fields in DSO is -- 16
Max no of data fields in DSO is --749.
But i read in some of the scn documents a table can have maximum 256 columns .
DSO is also like a two dimensional table which can also have the same properties of a two dimensional table.
if the above statement of mine is correct.. the number of columns in a DSO is 256 columns = 16(primary key)+240 (data fields--non key fields)
but how come 749 data fields (max) will be there ? if it is so ... the max no of fields will be 749+16 = 765.
I need some clarification on this ....
Awaiting for your responses!!!!
regards,
vamshi

Hi Rajavamshi,
For DSO:
1. See for Standard DSO we have Key fields & Data Fields will be there
2. Key Fields will store only Characterisitc Info Objects, maximum no.of characteristic info object we can add here was 16
3. But in Data fields we can add both Characterstics & Keyfigure infoobjects, Max of 749 data fields we can add here.
4. Atleast one field should be there in either Key fields & Data fields.
For InfoCube :
1. Info cube structure will be having the 16 Dimensions and the Key Fields.
2. In that 16 Dimensions 13 User defined and the 3 pre defined dimensions.
3. One user defined Dimension will maximum can hold 248 Characteristics Info Object, not the Keyfigure Info Object here.
4. But the Key Fields here will store maximum will hold 233 Key Figure Info Object.
Thanks..!!
Regards,
Harish. K

Miximum no of fields in DSO

Hi All,
Can you please provide me info:
How many maximum KeyFields a DSO can have?
How many maximum datafileds a DSO Can have?
basically is there any restrictions on no of fields for DSO like Infocube?
Your information is greatly appreciated.
Regards,
Ravi

Hello,
Yes its there..
you can have maximum 16 keys for an oracle table therefore you can have only 16 keys for the DSO.
Also depending upon the maximum size of the data blocks the maximum number of data fields is 749.
check this thread.
http://help.sap.com/saphelp_nw04/helpdata/en/4a/e71f39488fee0ce10000000a114084/content.htm
Not sure if this has chnaged recently but should hold true.
Thanks
Ajeet

Field in DSO 0BBP_QUO from Datasource 0BBP_TD_QUOT_1

Similar Messages

Maybe you are looking for