0EC_CS_1--Datasource A.H.P & vishvesh Plz confirm
i am trying to use this infosource and the associated infocube which i am able to find in the Business content but to my surprise i am not able to find any transfer rules r datasource in the R/3,
even when i have tried to install this infocube with before and after i didn't get the transfer rules
i will be happy if somebody can focus on this to solve it please
thanks and regards
Message was edited by: Neel Kamal
check oss 381626
It is not clear which DataSources are available in which Releases and which should be used.
Additional key words
0EC_CS_1, 0EC_CS_1A, 3EC_CS_1, 3EC_CS_1A
Cause and prerequisites
In 4.0B and 4.5B, SAP delivers DataSources 0EC_CS_1 and 0EC_CS_1A.
As of Release 4.6B, SAP does not deliverDataSources for EC-CS transaction data any more, the customer must generate them in the BW IMG of the source system (settings for application-specific DataSources -> Enterprise Controlling -> create Customizing for extractors in the consolidation). these generated DataSources are called 3EC_CS_1 and 3EC_CS_1A.
The generation is required because as of 4.6B you have the option to create customer-defined subassignments. As a result, the DataSource definition may differ from customer to customer.
What is the difference between 0EC_CS_1 and 0EC_CS_1A or 3EC_CS_1 and 3EC_CS_1A?
In PlugIn 2000.1, an new extractor FCIW_BIW_GET_DATA_NT was delivered, the extraction logic of this new extractor was significantly advanced compared to the previous extractor FCIW_BIW_GET_DATA_A.
This new extractor is assigned to DataSources 0EC_CS_1A and 3EC_CS_1A. Refer to the onLine documentation for the Business Content and to the extractors for EC-CS for more detailed information on the new extractor.
The following overview illustrates which DataSources are available in which Release and with which extractor they are connected:
Release | 45B | 0EC_CS_1 | 0EC_CS_1A |
SAP recommends using DataSources 0EC_CS_1A and 3EC_CS_1A. However, you have to delete the InfoCube contents before you change from the old to the new extraction logic. Subsequently you have to load the data completely with the new extractor.
Source code corrections