Purchasing transaction data load error at DTP level.

Hi All,
we are doing daily load for the MM Purchasing Transaction data.
Today it failed while it is loading from2LIS_02_SCL( PSA) to DSO.
The error message is like this.
An error occurred while executing a transformation rule:
The exact error message is:
Overflow converting from '1052332762320000.00'
The error was triggered at the following point in the program:
GP46PDVI7I2JSVXEJSYCMP7PAFB 1773
Request to help in Correcting this error.
Thanks,
Manu.

Hi,
The value exceeds the maximum value of any integer ABAP type, and is the source of error.
Try to identify the record in the source system and fix it there, repeat load. Else look it up on the PSA and fix.
Regards,
Arek

Similar Messages

Transaction data loading error

I have one info-cube: C1, characterstic: Time(0calday), material number(IO_MAT), company code (0comp_code)
key figure: price of material (IO_PRC)
I create one datasource for transaction data
Material Comp code Price
110001 7770 23
when I create transformation, it says error 1::
Rule 2 (target field: IO_PRC): Field PRICE must be assigned to an InfoObject
Message no. RSTRAN526
Diagnosis
No InfoObject is assigned to field PRICE. This is mandatory if you want to use the corresponding rule type.
System Response
The rule is invalid.
Procedure
Assign an InfoObject to the field
error 2:
Key rule 3 (target field: 0CALDAY): Initial update set
Message no. RSTRAN508
do I need another column in my upload file for date? should I put "16/11/2011" or "11.16.2011" for example?
if I don't provide date, is it ok to run DTP? thanks

hi,
I already have key figure IO_PRC( price) defined and in my datasource, I have also a field called " price" as well as in the upload file. and I already create a mapping by link "price" (upload file field) and IO_PRC (key figure)
The issue is:
No InfoObject is assigned to field PRICE.
and second issue is:
Rule (target field: IO_PRC): No source unit assigned
Message no. RSTRAN517
My key figure IO_PRC is defined as:
Data type: CURR, fixed currency: USD Unit/currency: empty, Data element: /BIC/OIIO_PRC
anything missing?

Flat file transactional data load error

I am trying to load a flat into a BPC model. I am using a DM " Import transational data load from flat file" to load the data. The transformation file and data file are validated correctly.
However,when i am running the DM package, i am hitting the below message.
Task Name : Load
Cannot perform Read.
Model : Package Status : Error.
We have two secure dimension in the model. I have tried different combinations even with PRimary admin role and i am still getting the same error message.
Is this a secirity related error ? The model has been transported from DEV . In DEV, i am not facing any errors.
Any advise/ help?

Hi King,
I think in the back end you need check the option real time load behavior, Is it in planning mode or loading mode. If possible share your error message screen.
Goto RSA1 ---> select your cube--> Right click---> change real time load behavior--> Change it in to planning mode
Regards,
Saida Reddy Gogireddy

How to rectify the errors in master data loads & transactional data loads?

hy,
please any one tell me
How to rectify the errors in master data loads & transactional data loads?
thnQ
Ravi

Hi,
Please post specific questions in the forum.
Please explain the error you are getting.
-Vikram

Master Data/transactional Data Loading Sequence

I am having trouble understanding the need to load master data prior to transactional data. If you load transactional data and there is no supporting master data, when you subsequently load the master data, are the SIDs established at that time, or will then not sync up?
I feel in order to do a complete reload of new master data, I need to delete the data from the cubes, reload master data, then reload transactional data. However, I can't explain why I think this.
Thanks, Keith

Different approach is required for different scenario of data target. Below are just two scenarios out of many possibilities.
Scenario A:
Data target is a DataStore Object, with the indicator 'SIDs Generation upon Activation' is set in the DSO maintenance
Using DTP for data loading.
The following applies depending on the indicator 'No Update without Master Data' in DTP:
- If the indicator is set, the system terminates activation if master data is missing and produces an error message.
- If the indicator is not set, the system generates any missing SID values during activation.
Scenario B:
Data target has characteristic that is determined using transformation rules/update rules by reading master data attributes.
If the attribute is not available during the data load to data target, the system writes initial value to the characteristic.
When you reload the master data with attributes later, you need to delete the previous transaction data load and reload it, so that the transformation can re-determine the attributes values that writes to the characteristics in data target.
Hope this help you understand.

Sap bw 7.3 master data load error

sap bw 7.3 master data load error
erroe: Exception in Substep Rules

Hi Jayram,
I am assuming that you are getting this error when you are loading data from PSA to IO. If so, the error might be because of
1. Duplicate records
PSA might have duplicate records. But you will be able to load only one record to Master data IO. In DTP Update tab, there is an option for "Handle Duplicate Record Keys" . Just enable this & try to load again.
2. Erroneous records.
Some special reocrds are allowed in PSA where as thye might not be allowed in Master Data/Data Targets like Lower case letters/ some speacial characters etc. If error is because of this, then you might need to correct the data at PSA level & reload the data to Master data. Else get it corrected in source system itself & fetch the data to BW. Or write some code to take care of these special characters.
Hope it helps!
Regards,
Pavan

Common data load errors in BI 7

Hi , i would appreciate if any one can provide me a list with most common Data load errors effecting both master and transactional data in SAP BI 7 or BW 3.5..

Hi AAL,
There're lots of loading error posts in this forum. This one I guess is good for you:
production support errors
production support issues
Or you can search yourself using key word common load error etc.
Hope above helps.
Regards,
Frank

Data Load Error due to Master data deletion

Hi,
While doing the transactional data load I am getting following error.
+Master data/text of characteristic ZFOCUSGRP already deleted Message no RSDMD138 +
ZFOCUSGRP is an InfoObject (with Text). Last week we changed the source system from CRM to R/3 during that time we deleted all the Texts in ZFOCUSGRP manually from the table.
This error is not happening always some time it load properly. I executed the RSRV for InfoObject ZFOCUSGRP and InfoCube still this error happening.
Is there any way to fix this error?
Thanks in advance.
Thanks
Vinod

check this:
Re: Error while running InfoPackage
Master data/text of characteristic 0MATERIAL already deleted
Master data/text of characteristic ZXVY already deleted
Hope it helps..

Transactional data loads PIR, IM stock, Open PO's documentation

I have to make a documentation of the process of transactional data loads.
transactional data loads pirchase info rec, IM stock, Open PO's
the transactional data is live in both sap and legacy, so they have to be even in both systems in all stages of this process.
how do i maintain that is the question.
send me any details regarding this.
thank you
sridhar

Check these three thigns
/n/sapapo/CCR
/n/sapapo/CQ
Check what type of stock has active IM, and what type of stock went in after you created the GR.
Still if you have any problem let us know.
My

Most common BW data load errors in production and how to solve them ..

Hi All,
Most common BW data load errors in production and how to solve them ..
Any doc on it ,if so plz send it across to this id [email protected]
Thanks in advance.
Rgrds
shoba

hi
1) RFC connection lost.
2) Invalid characters while loading.
3) ALEREMOTE user is locked.
4) Lower case letters not allowed.
5) While loading the data i am getting messeage that 'Record
the field mentioned in the errror message is not mapped to any infoboject in the transfer rule.
6) object locked.
7) "Non-updated Idocs found in Source System".
8) While loading master data, one of the datapackage has a red light error message:
Master data/text of characteristic 'so and so' already deleted .
9) extraction job aborted in r3
10) request couldnt be activated because theres another request in the psa with a smaller sid
11) repeat of last delta not possible
12) datasource not replicated
13) datasource/transfer structure not active ´
14) Idoc Or Trfc Error
15. ODS Activation Error

What are the frequent data load errors in production support?

what are the frequent data load errors in production support?

It is a long list. Here is some of them.
1. Idoc not arriving from source system.
2. previous processes failed.
3. change run unsucessful or did not run properly and data in master data is messed up.
4. invalid characteristics in the data.
5. Duplicate records found.
and on and on.
Ravi Thotahdri

Data Loading Error : ToomanyError records.

Hi All,
I got Data Loading error when I am loading from Flat File.
Following is the error message :
Too many error records - update terminated
Error 18 in the update
No SID Found for value '00111805' of Characterstic ZUNIQUEID (Message No 70)
can anybody help in resolving the issue.
Regards,
Chakravarthy

hi
Check the format of your charecteristics and key figures .
Check you put data separators in you flat files approriately
In the particular charecteristics ZUNIQUEID ,ensure data is consistent...check the related tables
Assign points if useful
Regards
N Ganesh

Aggregating data loaded into different hierarchy levels

I have some problems when i try to aggregate a variable called PRUEBA2_IMPORTE dimensinated by time dimension (parent-child type).
I read the help in DML Reference of the OLAP Worksheet and it said the follow:
When data is loaded into dimension values that are at different levels of a hierarchy, then you need to be careful in how you set status in the PRECOMPUTE clause in a RELATION statement in your aggregation specification. Suppose that a time dimension has a hierarchy with three levels: months aggregate into quarters, and quarters aggregate into years. Some data is loaded into month dimension values, while other data is loaded into quarter dimension values. For example, Q1 is the parent of January, February, and March. Data for March is loaded into the March dimension value. But the sum of data for January and February is loaded directly into the Q1 dimension value. In fact, the January and February dimension values contain NA values instead of data. Your goal is to add the data in March to the data in Q1. When you attempt to aggregate January, February, and March into Q1, the data in March will simply replace the data in Q1. When this happens, Q1 will only contain the March data instead of the sum of January, February, and March. To aggregate data that is loaded into different levels of a hierarchy, create a valueset for only those dimension values that contain data. DEFINE all_but_q4 VALUESET time
LIMIT all_but_q4 TO ALL
LIMIT all_but_q4 REMOVE 'Q4'
Within the aggregation specification, use that valueset to specify that the detail-level data should be added to the data that already exists in its parent, Q1, as shown in the following statement. RELATION time.r PRECOMPUTE (all_but_q4)
How to do it this for more than one dimension?
Above i wrote my case of study:
DEFINE T_TIME DIMENSION TEXT
T_TIME
200401
200402
200403
200404
200405
200406
200407
200408
200409
200410
200411
2004
200412
200501
200502
200503
200504
200505
200506
200507
200508
200509
200510
200511
2005
200512
DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
-----------T_TIME_HIERLIST-------------
T_TIME H_TIME
200401 2004
200402 2004
200403 2004
200404 2004
200405 2004
200406 2004
200407 2004
200408 2004
200409 2004
200410 2004
200411 2004
2004 NA
200412 2004
200501 2005
200502 2005
200503 2005
200504 2005
200505 2005
200506 2005
200507 2005
200508 2005
200509 2005
200510 2005
200511 2005
2005 NA
200512 2005
DEFINE PRUEBA2_IMPORTE FORMULA DECIMAL <T_TIME>
EQ -
aggregate(this_aw!PRUEBA2_IMPORTE_STORED using this_aw!OBJ262568349 -
COUNTVAR this_aw!PRUEBA2_IMPORTE_COUNTVAR)
T_TIME PRUEBA2_IMPORTE
200401 NA
200402 NA
200403 2,00
200404 2,00
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
2004 4,00 ---> here its right!! but...
200412 NA
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
2005 10,00 ---> here must be 30,00 not 10,00
200512 NA
DEFINE PRUEBA2_IMPORTE_STORED VARIABLE DECIMAL <T_TIME>
T_TIME PRUEBA2_IMPORTE_STORED
200401 NA
200402 NA
200403 NA
200404 NA
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
2004 NA
200412 NA
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
2005 10,00
200512 NA
DEFINE OBJ262568349 AGGMAP
AGGMAP
RELATION this_aw!T_TIME_PARENTREL(this_aw!T_TIME_AGGRHIER_VSET1) PRECOMPUTE(this_aw!T_TIME_AGGRDIM_VSET1) OPERATOR SUM -
args DIVIDEBYZERO YES DECIMALOVERFLOW YES NASKIP YES
AGGINDEX NO
CACHE NONE
END
DEFINE T_TIME_AGGRHIER_VSET1 VALUESET T_TIME_HIERLIST
T_TIME_AGGRHIER_VSET1 = (H_TIME)
DEFINE T_TIME_AGGRDIM_VSET1 VALUESET T_TIME
T_TIME_AGGRDIM_VSET1 = (2005)
Regards,
Mel.

Mel,
There are several different types of "data loaded into different hierarchy levels" and the aproach to solving the issue is different depending on the needs of the application.
1. Data is loaded symmetrically at uniform mixed levels. Example would include loading data at "quarter" in historical years, but at "month" in the current year, it does /not/ include data loaded at both quarter and month within the same calendar period.
= solved by the setting of status, or in 10.2 or later with the load_status clause of the aggmap.
2. Data is loaded at both a detail level and it's ancestor, as in your example case.
= the aggregate command overwrites aggregate values based on the values of the children, this is the only repeatable thing that it can do. The recomended way to solve this problem is to create 'self' nodes in the hierarchy representing the data loaded at the aggregate level, which is then added as one of the children of the aggregate node. This enables repeatable calculation as well as auditability of the resultant value.
Also note the difference in behavior between the aggregate command and the aggregate function. In your example the aggregate function looks at '2005', finds a value and returns it for a result of 10, the aggregate command would recalculate based on january and february for a result of 20.
To solve your usage case I would suggest a hierarchy that looks more like this:
DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
-----------T_TIME_HIERLIST-------------
T_TIME H_TIME
200401 2004
200402 2004
200403 2004
200404 2004
200405 2004
200406 2004
200407 2004
200408 2004
200409 2004
200410 2004
200411 2004
200412 2004
2004_SELF 2004
2004 NA
200501 2005
200502 2005
200503 2005
200504 2005
200505 2005
200506 2005
200507 2005
200508 2005
200509 2005
200510 2005
200511 2005
200512 2005
2005_SELF 2005
2005 NA
Resulting in the following cube:
T_TIME PRUEBA2_IMPORTE
200401 NA
200402 NA
200403 2,00
200404 2,00
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
200412 NA
2004_SELF NA
2004 4,00
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
200512 NA
2005_SELF 10,00
2005 30,00
3. Data is loaded at a level based upon another dimension; for example product being loaded at 'UPC' in EMEA, but at 'BRAND' in APAC.
= this can currently only be solved by issuing multiple aggregate commands to aggregate the different regions with different input status, which unfortunately means that it is not compatable with compressed composites. We will likely add better support for this case in future releases.
4. Data is loaded at both an aggregate level and a detail level, but the calculation is more complicated than a simple SUM operator.
= often requires the use of ALLOCATE in order to push the data to the leaves in order to correctly calculate the aggregate values during aggregation.

Data Load error Please respond ASAP

Hi ,
When i am trying to load data for year 07 using rule files its showing an error and aborting the data load
Error Msg " Data Value [2007] Encountered before all dimensions Selected,[5] Records Completed"
Any help greatly appreciated.
Thanks

Key here is that 5 records were loaded before failing on the 6th, indicating it's not a header issue on the load rule.
Check the first 5 records and see how the column containing 2007 differs between them and the failing 6th record. Perhaps the 6th record has a null (as indicated eariler) or prehaps 2007 is not the name of the member in the outline.
I have had both issues give similar error results.
J

Data load error regarding timestamp

Hi All,
I am getting data load error related to time.
I am using 2lis_02_SCN for CNFTM(time stamp) filed
with value "08:00:" need to convert to 08:00:00...for some records and rest of the records are coming with normal 6 digit time.
please send your suggestion as early as possible.
Thanks
Rupa

Hi Rupa,
Try out following sample code inthe transfer rule for the same info object and it should work
lv_len = strlen( str ).
if lv_len = 4.
concatenate str '00' into str.
endif
Regards
Kapadia

Purchasing transaction data load error at DTP level.

Similar Messages

Maybe you are looking for