Error occurred in the data uploading from Flat File in BPC NW

Hi,
I am doing Migration project from BPC MS to NW.
In this i am loading data from flat file to BPC NW. One error occured in this process that is Record Duplication.
Total 17000 records in that 7000 recards rejected by the reason of duplication.
The Information about Package Log
/CPMB/MODIFY completed in 0 seconds
/CPMB/CONVERT completed in 2 seconds
/CPMB/LOAD completed in 7 seconds
/CPMB/CLEAR completed in 0 seconds
[Selection]
FILE= DATAMANAGER\DATAFILES\Aprilmayjun_2011_Budget_V1.CSV
TRANSFORMATION= DATAMANAGER\TRANSFORMATIONFILES\ZAPRMAYJUN_2011BUDGET.xls
CLEARDATA= No
RUNLOGIC= Yes
CHECKLCK= No
[Messages]
Task name CONVERT:
No 1 Round:
Record count: 17064
Accept count: 17064
Reject count: 0
Skip count: 0
Task name LOAD:
Reject count: 7230
Submit count: 9834
Application: CorpBudget Package status: WARNING
Could you help me in this at the earliest.
Thanks and Regards
Krishna

Hi,
You cannot send the duplicated with the standard import package. You need to create or add a new package and link to /CPMB/APPEND process chain and do the import. This would consider the duplicate entries also. It looks like you need somehow load all the records including the duplicate ones.
So on excel go to Manage Data -> Maintain Data management -> organize package list and add a new package and link to the standard BPC process chain /CPMB/APPEND.
Thanks,
Sreeni

Similar Messages

Va31 shedule line agreement data upload from flat file

Hi abapers
I have to upload some data (va31) from flat file to my database (shedule line agreement data) I am using user exit for it...Cant get which user exit will solve the purpose and where to check it from..I tried using SDTRM001 , meeta001 and and the va45A series but its not working. I used break point on these user exits but its not stoping at break point.
Can any one help me where to find which user exit will work in this case?
Thanks in Advance
Annu

Hi Prash,
Check these posts:
Re: Increasing the length of Infoobject from 60 to 240 characters
Re: InfoObject > 60
Bye
Dinesh

Procurement Card data upload from flat file to database

Hi All,
I need to upload Procurement Card data from a flat file to the database in the table BBP_PCMAS.
I found a BAPI BAPI_PCARD_CREATEMULTIPLE which uploads the data perfectly, however the structure PCMASTER that it takes as input does not contain the field for Blocking reason PCBLOCK - Reason for blocking procurement card. I need to upload this file as well from the flat file.
Any suggestions?
Thanks

Hi,
You are correct the function module BAPI_PCARD_CREATEMULTIPLE does not contain the PCBLOCK field.
Alternatively what you can do is read the PC data after it is created and modify it with the PCBLOCK appropiately. The necessary function modules are given below.
BBP_PCMAS_READ_PCMAS - Read Data
BBP_PCMAS_MODIFY_PCMAS - Modify Data
Note: BBP_PCMAS_MODIFY_PCMAS is a Update Task FM. Hence it shoild be called as given below, ( refer form write_data of the FM BAPI_PCARD_CREATEMULTIPLE)
call function 'BBP_PCMAS_MODIFY_PCMAS' in update task
       exporting
            i_pcmas     = i_pcmas
*         I_PCMAS_OLD =
*         I_DELETE    =
      tables
           t_pcacc     = i_pcacc
*         T_PCACC_OLD =
      exceptions
           not_found   = 1
           others      = 2.
Regards
Kathirvel

Error occured in the data selection while extract data from Source system

Hello Friends
i am facing Problem while extracting data to Biw System from SAP R/3 system
The error mesage is 'Error occured in the data selection '
i.e. Monitoring - Details tab - Extraction - With error

Hi
The delta wil take the Last init selection for loading data in to the BW...
Did u check the IP at the Update tab is it the correct delta only.. or its a full..
better to go to the RSA3 and check the extractor in the Delta mode .. if u give ur delta mode it automatically takes the selction options.. so please try in RSA3..
regards
CK
PS: CHECK THE INIT SELECTIONS TOO or do an init with outdatatransfer and perform the delta...
Message was edited by:
BW Star

Error occurred in the data selection,If i do Repeat, then it is working fin

Hi Freinds,
Here is the error message,
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Details Tab:
Extraction (messages): Errors occurred
Error occurred in the data selection ....
If i do Repeat Delta, then it is working fine.
As it is a daily load, manually repeating the load from the past 10 days.
Have tried using program RS_TRANSTRU_ACTIVATE_ALL.
Any inputs pls.....

Hi Friends,
Thanks for your valuable inputs, Problem is solved.
The Reason is that, there is a time difference in the r/3 system and bi system.
The tolerable time differene shud be only 60 seconds.
Basis guys took down time at the OS level and hav made the timers sync.....
The problem is on the source system GNP time differences
persists, which can cause the problem with delta upload .
Universal Time Coordinated UTC....: 1291187626
Date and time of database.........: 01.12.2010 12:46:59
Date and Time of R/3-Kernel.......: 01.12.2010 12:43:46
Date and Time of ABAP-Processor...: 01.12.2010 12:46:58
ABAP Time zone Setup ..............: 19800
Date and Time / local time ........: 01.12.2010 12:43:46
This leads to an exception of the delta processing, because this
tolerates a deviation of 60 seconds only (When the repeat is processed,
the "local time" in the ABAP is higher than the qrfc counter at the time when the delta was processed -> So a repeat works fine).
Please synchronize the timers like described in attached note 101726 and 741734 to eliminate the time difference .
With Regards
Badri Thiriveedhi.

Error in data loads-Error occured in the data seletion

Hi,
We have to do an init load for Period 10 from data source 0EC_PCA_3.
When the period changes we usually copy the previous infopack and change the fiscal yesr period and do an init load.
This time we have to change the fiscal period to 010, we created a new info pack but the fiscal year period we forgot to change and was 009 and scheduled a init load.
The load failed with error mesg IN EXTRACTION PART:
1) syntax error in RSCDELTA
2) Error occured in the data selection -RSM 340
REQUEST part in monitor screen is green.
TRANSFER part in monitor screen is green
EXTRACTION shows:
Data request received ---green
Data selection scheduled -
green
Error occurred in the data selection -
RED
Processing (data packet): No data ---RED
We deleted the red request in the ods , deleted the init load in scheduled -init for source system --- chnaged the fiscal yesr period to 010 and triggered a new load but again it gives the same error mesg.
How to rectify this and do loads to the target successfully.
Please suggest

Please check the job log in the source system. It will give you the exact reason why extraction is failing. You need to act accordingly.
Thanks..
Shambhu

Error message :"Error occurred in the data selection"

Hi All ,
When I am exracting a Delta from source I am getting this error mesage Error occurred in the data selection" can any one let me know how to slove this,
Thanks in Advance.
rao

Praveen,
In SM 37
In JobName i have given - *REQU_4683BBF4HXG4XW4ASQOSP6PJG
where REQU_4683BBF4HXG4XW4ASQOSP6PJG is Request no
User Name is -- *
then I had check all these
sched, Released, ready, active, Finished, cancelled
then executed
then i received the message no jobs are matches the selection criteria
thanks
prasanna

"Error occurred in the data selection" on init delta load ODS- InfoCube

Hi, gurus and experts!
I'm trying to do Init delta load from 0FIAR_O03 ODS into 0FIAR_C03 InfoCube in PRD env. by InfoPackage "Initialize with delta transfer (with data transfer)". Immediately after the load was started I got error
"Error occurred in the data selection"
with details
"Job terminated in source system --> Request set to red".
Where are no any short dumps. There are 1 activated init load in ODS - nearly 6 500 000 records.
Any ideas about error? And the way I can load data?

Hi Gediminas Berzanskis,
I faced the similar error when I tried to load data from an ODS which contained huge amount of data to a Cube. Even in your case the volume of data is more (around 6.5 million records). The error could be due to the table space issue, please contact your Basis team to check if enough table space exist for both the data targets.
Meanwhile you may also check the RFC connection of the Myself source system.
You can replicate the DSO datasource once and then reactivate the transfer rules using the program RS_TRANSTRU_ACTIVATE_ALL.
Try load with a small amount of data with a Full load option and then with a delta option..
Hope this Helps,
Prajeevan (XLNC)

How to solve "error occurred in the data manipulation engine"? 64bit Windows 7

Hi all
I'm having quite a testing time here trying to use the new SAP PA 2.0. After installation the software launches, the Automated Analytics seems to work fine but not the Expert Analytics.
Steps as follows:
Launch PA
Choose and launch Expert Analytics
Choose Try with Samples
Open the Dairy Wholesaler file
Error: An error occurred in the data manipulation engine. Check the manipulation parameters. (HDB 01001)
I also get this same error when I try to create my own New Dataset.
I’m on 64bit Windows 7 Pro
Is there anyone who knows how to solve this problem. I've searched the SCN and online and have tried the following:
1. Uninstall and re-install. Doesn't help
2. Uninstall and delete old lumira related folders on the C drive e.g. the SAPPA and SAPVI folders on the C drive, then re-install.
Much appreciated if anyone could shed some light on this. I've previously had Lumira working with no issues. I've since uninstalled Lumira, Predictive Analytics, and Infinite Insights (as PA 2.0 is all of this combined)
Regards
Ria

In case anyone has the same problem, I found the the following helpful (taken from Error after upgrading to 1.18 ). The solution is for Lumira however its the same steps for PA2
1. You might want to try a ‘clean’ uninstall / reinstall . After uninstalling, try deleting these folders:
C:\Users\Public\sapvi
C:\Users\<user>\AppData\Local\SAP\Lumira
C:\Users\<user>\AppData\Local\Temp\sapvi
In this step I searched for every SAP related file in AppData in the Public, User, and my own username folder under \Users\
2. Next, to launch the application, explicitly click "Run as Administrator" on the install file

Process chains-Error occurred in the data selection-DBIF_RSQL_TABLE_UNKNOWN

Hi All,
The problem occurred in PC which was running smooth until now
Now I am getting message:
in BI : Error occurred in the data selection
When I went in R/3 it shows DBIF_RSQL_TABLE_UNKNOWN
Probably the only way to eliminate the error is to correct the program.
Please check the entries in the system log (Transaction SM21).
Internal call code.........: "[RSQL/READ/PA0009 ]"
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
DBIF_RSQL_TABLE_UNKN
SAPLXRSA" or "ZXRSAU
EXIT_SAPLRSAP_002"
Can anyone explain..

Hi ,
Check note 950317.
also check the blow forum having same kind of discussion :
Runtime Errors DBIF_RSQL_TABLE_UNKNOWN
Short dump error DBIF_RSQL_TABLE_UNKNOWN
DBIF_RSQL_TABLE_UNKNOWN
thanks,
Deepak

Steps to load the data by using flat file for hierarchies in BI 7.0

Hi Gurus,
steps to load the data by using flat file for hierarchies in BI 7.0

hi ,
u will get the steps int he following blog by Prakash Bagali
Hierarchy Upload from Flat files
regards,
Rathy

Data loading from flat file to cube using bw3.5

Hi Experts,
                   Kindly give me the detailed steps with screens about Data loading from flat file to cube using bw3.5
       ...............Please

Hi ,
Procedure
You are in the Data Warehousing Workbench in the DataSource tree.
       1.      Select the application components in which you want to create the DataSource and choose Create DataSource.
       2.      On the next screen, enter a technical name for the DataSource, select the type of DataSource and choose Copy.
The DataSource maintenance screen appears.
       3.      Go to the General tab page.
                            a.      Enter descriptions for the DataSource (short, medium, long).
                            b.      As required, specify whether the DataSource builds an initial non-cumulative and can return duplicate data records within a request.
                            c.      Specify whether you want to generate the PSA for the DataSource in the character format. If the PSA is not typed it is not generated in a typed structure but is generated with character-like fields of type CHAR only.
Use this option if conversion during loading causes problems, for example, because there is no appropriate conversion routine, or if the source cannot guarantee that data is loaded with the correct data type.
In this case, after you have activated the DataSource you can load data into the PSA and correct it there.
       4.      Go to the Extraction tab page.
                            a.      Define the delta process for the DataSource.
                            b.      Specify whether you want the DataSource to support direct access to data.
                            c.      Real-time data acquisition is not supported for data transfer from files.
                            d.      Select the adapter for the data transfer. You can load text files or binary files from your local work station or from the application server.
Text-type files only contain characters that can be displayed and read as text. CSV and ASCII files are examples of text files. For CSV files you have to specify a character that separates the individual field values. In BI, you have to specify this separator character and an escape character which specifies this character as a component of the value if required. After specifying these characters, you have to use them in the file. ASCII files contain data in a specified length. The defined field length in the file must be the same as the assigned field in BI.
Binary files contain data in the form of Bytes. A file of this type can contain any type of Byte value, including Bytes that cannot be displayed or read as text. In this case, the field values in the file have to be the same as the internal format of the assigned field in BI.
Choose Properties if you want to display the general adapter properties.
                            e.      Select the path to the file that you want to load or enter the name of the file directly, for example C:/Daten/US/Kosten97.csv.
You can also create a routine that determines the name of your file. If you do not create a routine to determine the name of the file, the system reads the file name directly from the File Name field.
                              f.      Depending on the adapter and the file to be loaded, make further settings.
■       For binary files:
Specify the character record settings for the data that you want to transfer.
■       Text-type files:
Specify how many rows in your file are header rows and can therefore be ignored when the data is transferred.
Specify the character record settings for the data that you want to transfer.
For ASCII files:
If you are loading data from an ASCII file, the data is requested with a fixed data record length.
For CSV files:
If you are loading data from an Excel CSV file, specify the data separator and the escape character.
Specify the separator that your file uses to divide the fields in the Data Separator field.
If the data separator character is a part of the value, the file indicates this by enclosing the value in particular start and end characters. Enter these start and end characters in the Escape Charactersfield.
You chose the; character as the data separator. However, your file contains the value 12;45 for a field. If you set u201C as the escape character, the value in the file must be u201C12;45u201D so that 12;45 is loaded into BI. The complete value that you want to transfer has to be enclosed by the escape characters.
If the escape characters do not enclose the value but are used within the value, the system interprets the escape characters as a normal part of the value. If you have specified u201C as the escape character, the value 12u201D45 is transferred as 12u201D45 and 12u201D45u201D is transferred as 12u201D45u201D.
In a text editor (for example, Notepad) check the data separator and the escape character currently being used in the file. These depend on the country version of the file you used.
Note that if you do not specify an escape character, the space character is interpreted as the escape character. We recommend that you use a different character as the escape character.
If you select the Hex indicator, you can specify the data separator and the escape character in hexadecimal format. When you enter a character for the data separator and the escape character, these are displayed as hexadecimal code after the entries have been checked. A two character entry for a data separator or an escape sign is always interpreted as a hexadecimal entry.
                            g.      Make the settings for the number format (thousand separator and character used to represent a decimal point), as required.
                            h.      Make the settings for currency conversion, as required.
                              i.      Make any further settings that are dependent on your selection, as required.
       5.      Go to the Proposal tab page.
This tab page is only relevant for CSV files. For files in different formats, define the field list on the Fields tab page.
Here you create a proposal for the field list of the DataSource based on the sample data from your CSV file.
                            a.      Specify the number of data records that you want to load and choose Upload Sample Data.
The data is displayed in the upper area of the tab page in the format of your file.
The system displays the proposal for the field list in the lower area of the tab page.
                            b.      In the table of proposed fields, use Copy to Field List to select the fields you want to copy to the field list of the DataSource. All fields are selected by default.
       6.      Go to the Fields tab page.
Here you edit the fields that you transferred to the field list of the DataSource from the Proposal tab page. If you did not transfer the field list from a proposal, you can define the fields of the DataSource here.
                            a.      To define a field, choose Insert Row and specify a field name.
                            b.      Under Transfer, specify the decision-relevant DataSource fields that you want to be available for extraction and transferred to BI.
                            c.      Instead of generating a proposal for the field list, you can enter InfoObjects to define the fields of the DataSource. Under Template InfoObject, specify InfoObjects for the fields in BI. This allows you to transfer the technical properties of the InfoObjects into the DataSource field.
Entering InfoObjects here does not equate to assigning them to DataSource fields. Assignments are made in the transformation. When you define the transformation, the system proposes the InfoObjects you entered here as InfoObjects that you might want to assign to a field.
                            d.      Change the data type of the field if required.
                            e.      Specify the key fields of the DataSource.
These fields are generated as a secondary index in the PSA. This is important in ensuring good performance for data transfer process selections, in particular with semantic grouping.
                              f.      Specify whether lowercase is supported.
                            g.      Specify whether the source provides the data in the internal or external format.
                            h.      If you choose the external format, ensure that the output length of the field (external length) is correct. Change the entries, as required.
                              i.      If required, specify a conversion routine that converts data from an external format into an internal format.
                              j.      Select the fields that you want to be able to set selection criteria for when scheduling a data request using an InfoPackage. Data for this type of field is transferred in accordance with the selection criteria specified in the InfoPackage.
                            k.      Choose the selection options (such as EQ, BT) that you want to be available for selection in the InfoPackage.
                              l.      Under Field Type, specify whether the data to be selected is language-dependent or time-dependent, as required.
       7.      Check, save and activate the DataSource.
       8.      Go to the Preview tab page.
If you select Read Preview Data, the number of data records you specified in your field selection is displayed in a preview.
This function allows you to check whether the data formats and data are correct.
For More Info: http://help.sap.com/saphelp_nw70/helpdata/EN/43/01ed2fe3811a77e10000000a422035/content.htm

Help Required regding: Validation on Data Loading from Flat File

Hi Experts,
I need u r help in the following issue.
I need to validated the transactional data loading to the GL Cube from Flat file,
1) The transactional data to the Cube to be loaded only if master data record exists for the 0GL_ACCOUNT info object.
2) If the master data record does not exits then the record need to be skipped from the loading and after the loading the system should throw a message saying that these many records have been skipped (if there are any skipped records.).
I would really appriciate u r help and suggestions on solving this issue.
Regds
Hari

Hi, write a start routine in transfer rules like this.
DATA: l_s_datapak_line type TRANSFER_STRUCTURE,
 l_s_errorlog TYPE rssm_s_errorlog_int,
 l_s_glaccount type /BI0/PGLACCOUNT,
 new_datapak type tab_transtru.
 refresh new_datapak.
 loop at datapak into l_s_datapak_line.
 select single * from /BI0/PGLACCOUNT into l_s_glaccount
 where CHRT_ACCTS eq l_s_datapak_line-field name in transfer structure/datsource for CHRT_ACCTS
and GL_ACCOUNT eq l_s_datapak_line-field name in transfer structure/datsource for GL_ACCOUNT
and OBJVERS eq 'A'.
 if sy-subrc eq 0.
 append l_s_datapak_line to new_datapak.
 endif.
 endloop.
 datapak = new_datapak.
 if datapak[] is initial.
abort <> 0 means skip whole data package !!!
 ABORT = 4.
 else.
 ABORT = 0.
 endif.
i have already some modifications but U can slightly change it to suit your need.
regards
Emil

Upload hierarchy from flat file to BPC

Hello SAP Guru,
I have download customer / material hierarchy in flat flie from BI/BW and now I want to upload hierarchy from flat file to BPC
Please can any one give me step by step method to load hierarchy from Flat file to SAP - BPC.
Thanks in advance.
With regards,
Anand Kumar

Hi Saida Reddy,
why you resurrect a 5 years old thread? Surely he solved in the meanwhile his issue, see please dr Frankenstein.
Regards
Roberto

Data updation from flat file to I.C. via ODS

Hi,
I have to load transaction data from 4 tables into 4 ods and these 4 ods data will be loaded to 1 info cube.so please tell me the best method whether to use 4 info sources for 4 ods or can i define all the info objects in one info source and use the same info source for all ods objects.
Thank you

Hello GanGa,
How r u ?
1st could u tell, the loads are from Flat File or Tables ?
coz ur Subject and the Message is getting clashed.
If u use Flat Files, then better go for 4 IS and 1 ODS is enough. Then update the cube.
If u r going to extract from Tables, then you have to create the Data Source using "Extraction from Views", for this u should have common key fields in all the 4 tables. In BW DataSource to InfoSource mapping should be 1 to 1.
Best Regards....
Sankar Kumar
+91 98403 47141

Error occurred in the data uploading from Flat File in BPC NW

Similar Messages

Maybe you are looking for