Datasource error- while activating it- warnings occured

Question

Hi experts,
I'm using the standard BC datasource 3FI_SL_7R to load the data into the cubes 0rtl_c01 & 0rtl_c03.
while activating the data source in the R/3 the system displayed the below warnings:
"Generating DataSource 3FI_SL_7R"
"Delta process ABR for DataSource 3FI_SL_7Rrequires a cancellation field"
by ignoring them i configured the whole data flow, but while i scheduled the data for extraction it showed the following errors in the monitor error message:
"The extraction program does not support object"
I again activated the function module, extractor and the datasource(again with warnings), and done the whole thing once again but i came across the same error in the monitor.
Does any one have a solution for this PLZ HELP ME.
UR HELP WILL BE HIGHLY APPRECIATED.
thanks & regards

Answer 1

Hi
Here is the following note:
Symptom
You want to use the delta mode for the BW extraction of total record data from FI-SL or EC-PCA.
Other terms
0EC_PCA_1, 3FI_SL_
Reason and Prerequisites
Note the following prerequisites and restrictions:
This note only applies to totals record DataSources.
The R3 Release must be 4.0B or higher.
The delta method is currently only available for actual data.
The delta method uses the same transfer structure as the full upload, that is, only totals record fields are transferred.
The BALANCE field of the transfer structure is not filled. To get the non-cumulative for balance sheet accounts, you can either create a non-cumulative value in the BW System, which is updated via values DEBIT/CREDIT, or accumulate the transactions of period 0 to n in the query definition.
You must use the online through-posting for balance sheet accounts. You can create a separate InfoPackage that works in the full upload for balance sheet accounts that are transferred periodically.
The line item update must be active for currency conversions in the FI System.
Deleting transactions are not connected to the delta method:
a) Periodic CO data transfer (transaction 0KE0) (use transaction 1KEA instead because this transaction cancels the data instead of deleting it).
b) Rollup
c) Delete transaction data (transaction 0KE1)
d) Modification of SAPFGVTR balance carryforward program (transaction GVTR):
After you implement the modification from note 182201, the ZZVTR001 delete program used there is not connected for the carryforward balances (TSLVT, HSLVT, KSLVT fields and so on).
              This means:
              Do not use these transactions if a delta method is initialized for the same selections because the deletion is not updated for the BW system.
               If you absolutely have to use one of the transactions or you have used one of them by mistake, you must delete the initial requests and delta requests from the InfoCubes in the BW system and you must restart the delta method with an initial upload.
Posting is not allowed during the initial upload. You must take organizational measures to make sure that no posting takes place at that time because there is no corresponding system check at present.
If the delta method was initialized for a source system, you must regularly schedule a delta upload so that the delta queue does not overflow. If you want to stop the delta method you should also delete the initialization. You can display the delta queue in the source system via transaction RSA7.
Enter the selection for the actual data in the information package (0VTYPE = 010). Planning data can be transferred with another InfoPackage in the full upload.
Solution
The solution is contained in the standard version as of Release 4.7A. The solution may be implemented in advance for lower releases:
To activate the delta method for DataSource 0EC_PCA_1 and for 3FI_SL_* generated totals record DataSources, you must perform the following steps in the OLTP:
Caution:
Steps 1 and 2 are delivered in Support Packages with note 485264 and no longer have to be executed with the corresponding Support Package status.
1. Create the following function modules in accordance with the correction instructions:
a) OPEN_FI_PERFORM_00005030_P in function group BFFM2 (4.0B - 4.5B)
                           or in function group BFFM3 according to note 450079 (4.6B - 4.6C)
b) OPEN_FI_PERFORM_00005040_P in function group BFFM2 (4.0B - 4.5B)
                           or in function group BFFM3 according to note 450079 (4.6B - 4.6C)
c) SAMPLE_PROCESS_00005030 in function group BFFMSMPL2 (4.0B - 4.5B)
                                                 in function group BFFMSMPL3 (4.6B - 4.6C)
d) SAMPLE_PROCESS_00005040 in function group BFFMSMPL2 (4.0B - 4.5B)
                                                 in function group BFFMSMPL3 (4.6B - 4.6C)
and create the following data elements using transaction SE11:
e) PR00005030
              Text: Open FI process 00005030
              Domain: XFELD
f) PR00005040
              Text: Open FI process 00005030
              Domain: XFELD
2. Add the following entries to table TPS01:
PROCS INTERFACE Text1
00005030 SAMPLE_PROCESS_00005030 BW delta extractor PCA FI-SL
00005040 SAMPLE_PROCESS_00005040 BW delta extractor PCA FI-SL
3. Implement the remaining corrections in accordance with the correction instructions in reports:
a) FGIDBF24
b) FGVTRF20 (up to and including Release 4.6B)
c) RGUGVTR0 (up to and including Release 4.6B)
d) and in function module G_BIW_GET_TRANSACTION_DATA (except for Release 4.0B)
4. Regenerate the update modules
a) Execute report SAPFGIDB using transaction SE38 with process type 1
b) Execute report RGUGVTR0 using transaction SE38 (up to and including Release 4.6B)
5. Implement the corrections from note 325824 (only Release 4.6C)
6. Execute report GBIWDGEN by using transaction SE38 (you must implement note 407091 beforehand up to and including P2001.1)
7. Change the data record in table ROOSOURCE for OLTPSOURCE = 0EC_PCA_1 and OBJVERS = A in field DELTA to 'ABR'. This may be done using report ZPCA_DELTA_FOR_0EC_PCA_1. Follow the same procedure for an FI-SL totals record DataSource.
As of PI 2003.1, the delta mode 'ADDD' is used instead of 'ABR'; an indicator is also set in the T881IS_PI control table. If you have installed Plug-In Release 2003.1 or higher, use the attached ZGBIWPI_DELTA report instead of the ZPCA_DELTA_FOR_0EC_PCA_1 report.
8. Replicate the DataSource in the BW System and activate it.
Import the changes into the production system via transports and then perform steps 4, 6, 7 and 8 again.
You will have to repeat step 6 again if you encounter problems after the Plug-In upgrade.
When you upgrade the source system to Release 4.7, discard the modification of reports FGIDBF24, FGVTRF20 and RGUGVTR0 during the data comparison and use the delivered version of these programs. If you use this note for FI-SL DataSources, call transaction BW03 once and accept the conversion of the DataSources in the dialog box that appears. If you do so, an initialized delta method will continue to run successfully even after you upgrade the source system.