Error while transporting a data type

Hello all SAP PI Experts,
I'm trying to transport a data type but I'm getting the below mentioned error.
This is happening even when I gave the proper name of SWCV that contains this data type.
Please suggest how this problem can be solved.
Thanks,
Ajeya G V

Hi Ajeya,
An easy trick is to open the DataType on your Enterprise Service Builder, and once it is opened, (not edit, just open) go to Tools --Export Design Object
The correct SC will be filled as default.

Similar Messages

Activation error while changing the data type of a field of a table

hi friends,
i am facing one problem while changing a data type of a field of a table.
i just created one table(Yqm32) .i have assigned charcter data type to one field(ztotal_count) .now i want to change this charcter data type to numeric data type.
while changing to NUMC data type activation error is comming as below.
Table is not yet classified
Field ZTOTAL_COUNT: Type change
ALTER TABLE is not possible
Structure change at field level (convert table YQM32)
Check on table YQM32 resulted in errors
Table YQM32 could not be activated
(E- Structure change at field level (convert table YQM32)
plz suggest.i need to change the data type from char to numc.
Thanks & Regards

Hi Pabitra......
From the SE11 change the table as u wanted and then from menubar select
UTILITIES--> DATABASE UTILITY
It will open database utility
there u select the Activate and adjust database button.
then the database table will get adjusted.
just try it once.........
Suresh......

DYNPRO_SENT_IN_BACKGROUND Error while transporting XI data source

Hi Experts,
We are having an issue in in transporting XI data source in BI from Dev to Test. The error is geenrated during post handling of the transport, possibly while the data source is bing activated. Teh ST22 dump gives the DYNPRO_SEND_IN_BACKGROUND error. Following informaiton is available in the User Information section of ST22 dump.
Call Program........."CL_RSDS_WEBSERVICE============CP"
Function Module..... "RSDS_WS_WEBS_GENERATE"
Information on where terminated
    Termination occurred in the ABAP program "SAPLSTRD" - in "SYSTEM-EXIT".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 0
    of the (Include) program " ".
Please give us your advice on how to nail down this issue.

Hi,
Check if your data source extract structure is having all 40 fields.
Save and generate the data source again, replicate and then transport.
I hope it will help.
Thanks,
S

Error While Transporting export Data Source

Hi Experts,
We have a requirement to transport a data source from development to quality system through acceptance box.
We need to transport an export data source which contains 40 fields. But when I captured the data source in development system and transported the same to acceptance box it's displaying only 38 fields. 2 Fields are missing from the data source which are present in development system and also source system of export data source.
Please suggest how to get these 2 fields in acceptance box.
Thanks,
Sachin Motgi

Hi,
Check if your data source extract structure is having all 40 fields.
Save and generate the data source again, replicate and then transport.
I hope it will help.
Thanks,
S

Error while returning complex data type in a J2EE web service

Hello,
I am implementing J2EE web service which returns array of custom class object.
I have implemented serializable interface to custom class, and also to session bean.
But it gives the following error:
Serializing object [Lcom.ltitl.j2ee.ejb.classes.ProjectDetails;@2a2289 fails. Nested message: XML Serialization Error. Object of Class [com.ltitl.j2ee.ejb.classes.ProjectDetails] does not have property [ObjId] of type [java.lang.Integer]. Check if the right object is passed to the serialization routine..
As error stated about some property ObjId..I tried including such property in my class. But now it gave exception while deploying stating that ObjId already defined.
Also I want to return multiple arrays of complex custom classes. i tried using vectors but didnt work. What is the method to return arrays of complex custom classes.
Please help..
Abhijeet

Trying to create a web service that returns a Collection doesn't seem to be possible in Netweaver. The reason for this is that languages other than Java have difficulty in mapping Collections, amongst others, to their own native equivalents.
There is a discussion on the subject here you may find useful:
http://forum.capescience.com/showthreaded.php?Cat=&Board=webservices&Number=147&page=0&view=collapsed&sb=5&o=&vc=1
The short answer is to use object Arrays instead, or a custom class that contains an array of each type of object you would expect to find in your Vector
Hope this helps
Steve

Error while saving default data type

When I try to save system wide Default Data Format of any of the columns, an error pops out. Seems like an XML error:
The current xml is invalid with the following errors:
Bad xml instance!
<?xml version="1.0"?> <sawsavedformat:metadata xmlns:sawsavedformat="com.siebel.analytics.web/savedformat/v1.1"><sawsavedformat:columnSavedFormats><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Division Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Group Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Dept Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Class Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Subclass Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Chain Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Area Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Region Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."District Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Store Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Business Calendar"."Fiscal Week""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="left" vAlign="top"><saw:dataFormat xsi:type="saw:text" textFormat="plain"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Unit Inventory"."U BOP""><saw:displayFormat><saw:formatSpec suppress="repeat" wrapText="true" visibility="visible" hAlign="right" vAlign="top" imagePlacement="right"><saw:dataFormat xsi:type="saw:number" whistlerFormat="#,##0" commas="true" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat></sawsavedformat:columnSavedFormats></sawsavedformat:metadata>
Line:2, Col:8982, Attribute 'whistlerFormat' is not declared for element 'dataFormat'
Any suggestions?
Thanks

HI,
Its known bug in obiee11.1.1.5. version try to apply obiee11.1.5.5.BP bug fixes version.
fyi,
bug 13370386 - 'THE CURRENT XML IS INVALID WITH THE FOLLOWING ERRORS: BAD XMLINSTANCE!' OCCURS
bug 13249783 - OBIEE 11G THROWS BAD XML INSTANCE
Thanks
Deva

Error while appending clob data type ....

Hi,
I'm trying to append a clob variable as below -
declare
temp_log clob;
begin
temp_log:=temp_log||'validated;errors in Legal Units: '||to_char(n1)||'/'||to_char(n2)||'Start '||to_char(beginrun,'HH:MI:SS')||'ended'||to_char(endrun,'HH:MI:SS')||chr(10);
exception
when others then
dbms_output.put_line(sqlerrm);
end;
=>
and got the error msg -
ORA-06502: PL/SQL: numeric or value error
ORA-00001: uni
After that I try as below :-
declare
temp_log clob;
begin
dbms_lob.writeappend(temp_log,length(temp_log||'validated;errors in Legal Units: '||to_char(n1)||'/'||to_char(n2)||'Start '||to_char(beginrun,'HH:MI:SS')||'ended'||to_char(endrun,'HH:MI:SS')),temp_log||'validated;errors in Legal Units: '||to_char(n1)||'/'||to_char(n2)||'Start '||to_char(beginrun,'HH:MI:SS')||'ended'||to_char(endrun,'HH:MI:SS'));
exception
when others then
dbms_output.put_line(sqlerrm);
end;
And got below error -
ORA-06502: PL/SQL: numeric or value error: invalid LOB locator specified:
ORA-22275
ORA-06512: at "SYS.DBMS_LOB", line 833
ORA-06512: at "EGR.TRANS_BVD_NEW", line 1290
ORA-06502: PL/SQL: numeric or value error: invalid LOB locator specified:
ORA-22275
ORA-06512: at "SYS.DBMS_LOB", line 833
pls help me....
Subir

it is a single line... but it is changing here due to less space....
It is some thing like -
temp_log:=temp_log||'treatments validated;errors in Legal Units: '||to_char(n1)||'/'||to_char(n2)||'Start '||to_char(beginrun,'HH:MI:SS')||'ended'||to_char(endrun,'HH:MI:SS')||chr(10);
Subir

Error while transporting custom datasource

Hi All,
Below is the scenario that was carried out in my project.
1. Created OHD to load data from a CUBE to Data base Table /BIC/ABC.
2. Created a custom Datasource ZABC_TEST with the above table.
3. Activated the DataSource and loaded the data. (Data load successfull. It works fine).
4. Tried transporting the above. But trows error while transporting the data source.
Error -- InfoSource ZABC_TEST is not available in source system BITST.
Let me know what can be done to solve the above error. Please suggest if i have missed out something.
Thanks in advance.
Maddy

HI,
The problem seems to be occuring since you are transporting both OHD and DS in the same TR request.
Transport first the DS in a request, then in another request transport the OHD.
This should resolve the issue.
hope this helps.
thanks,
rahul

Error while transporting 0MAT_PLANT

Hi Experts
I am getting error while transporting 0MAT-PLANT to Prod System.It going fine to QA system.
it is giving the follwoing error with return code 8
Characteristic 0MAT_PLANT: Master data has to be activated before conversion
Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Delete Mode)
Errors occurred during post-handling RS_AFTER_IMPORT for DTPA L
RS_AFTER_IMPORT belongs to package RS
The errors affect the following components:
BW-WHM (Warehouse Management)
I have deleted one Info-object (Key figure) and added one info-object(Key figure) to 0MAT_PLANT ,transported still it is giving errors it is going fine to QA.
1.Is it because we have large no of records in Prod system ..??
2.Do we need to delete the data in Prod for 0MAT_PLANT and transport....????
3.Is it related to any database error in adjusting P table in Prod...?
Please let me know anybody faced this kind of problem.
Regards
Prasad

Hi Prasad,
Just to summarise the discussion. If you need to send the transport successfully you need to the following steps:
1. MD (complete) needs to be deleted from IOBJ. Please note, unless you delete the TD data involving the IOBJ, you will not be able to delete MD completely.
The reason being, the SID's for the MD are being used in the various IC/DSOs. So you need to go by deleting related TD and then MD.
2. Secondly, if you forcibly delete for 'P' and 'S' table using the SE14-> Table Name -> Delete Data & adjust Db. This will cause lot of inconsistencies on Drill Down in reports and even on execution as SID values are missing!
Moreover, as you said there are around 10/12 InfoProviders involved here, then this forcefull deletion can cause a real imapct to your Prod system and make many reports unsusable! So pls be careful!
Please decide accordingly as there is a trade off here!
-VA
Edited by: Vishwa Anand on Sep 27, 2010 12:15 PM

Error while transporting - Source RSDS 8ZRF_O01 LOGDBQ151 does not exist

Hi,
I am getting following error while transporting export DataSource to quality system.
Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)
No rule exists
Source RSDS 8ZRF_O01 LOGDBQ151 does not exist
Start of the after-import method RS_DTPA_AFTER_IMPORT for object type(s) DTPA (Activation Mode)
Transformation does not exist (see long text)
Although, the request is failing, I can see the DataSource 8ZRF_O01 present in the QA system. Only the transformation is set inactive.
Regards,
Pranav.
Edited by: P D on Sep 20, 2010 9:02 AM

Hi
might be your data source not collected into transport request.
If you are moving data source from once system to other system, this may missed.
RSA1->Transport connection>all objects>Datasource --> Select your data source as only neecessary to move
When ever we are moving objects from one system to other follow below are order to avoid failures
1).New Infoobjects.
2). Data source/Infosource
3). Info Providers ( Cube/DSo)
4). Update rules/Transformation
5).Impacted objects and other
Mahesh.

Error while transporting Transformation: Syntax error in Start Routine

Hi Everyone,
I'm facing a strange problem during transporting one of the Business Content cubes from Dev. to Quality.
I'd activated the DSO 'Purchase Order Items (0PUR_O01)' and its entire data flow from the 4 datasources 2LIS_02_CGR, 2LIS_02_SCN, 2LIS_02_SGR, and 2LIS_02_ITM from BC. Then I migrated the Transfer/Update rules to transformations and the DataSources to BI7 DataSource. So far so good. The migration was successful and all the objects were activated.
Now when I transport the same to Quality, the import fails with return code 8 and the error message says:
'Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)'
'Start Routine: Syntax error in routine'
I verified that the transformation where the error orrured was the one from InfoSource Z2LIS_02_ITM to DSO 0PUR_O01. I went and checked the start routine and it did indeed have a syntax error:
'In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter SOURCE_PACKAGE" is incompatible with the formal parameter DATA_PACKAGE". '
But when I check in the Dev. system, there is no syntax error for the same routine. Later, I tried to transport only the said transformation by re-activating it in Dev, and again I got the same error.
I have no idea why I'm getting a syntax error in the start routine when there are non in the Dev. system. Also none of the coding is customised, it was only the BC code, migrated to a transformation.
Any suggestions on the steps I could take to transport the transformation to my quality system?
Thanks,
Ram

Hi Ajay, Shanthi, svu and Ray
I do indeed have a start routine in my transformation and it was migrated from a 3.x update rule to a BI 7 transformation routine.
The migration was successful and the Start Routine has NO syntax errors in the start routine in the Dev. system. I only encounter the error while transporting it to the Quality system. I cannot modify the code in the Quality system because it is non-changelable and there is no point in trying to change the code in Dev. because there are no errors over there.
I've also made sure that I've transported all the necessary objects required by the transformations to quality. The routine does not perform a lookup, it simply deletes some records from the data package based on the processkey value (which is itself present in the data package).

Error while transporting Infocube

Hello all,
i am getting following error while transporting infocube to testing system.
Please see the bellow error message details.
Error/warning in dict. activator, detailed log > Detail
Structure change at field level (convert table /BIC/DZMD_Y_MR2)
Structure change at field level (convert table /BIC/FZMD_Y_MR)
Table /BIC/DZMD_Y_MR2 could not be activated
Table /BIC/FZMD_Y_MR could not be activated
Return code..............: 8
Following tables must be converted
ZMD_Y_MR InfoCube could not be activated
Thanks in advance.
BR,
YVReddy

Dear Venkat,
Looks like you have changed the fields on the infocube.Just wanted to make sure that did u delete the 'data' from the cube 'ZMD_Y_MR' in the testing system before u make the traansport?
for any changes in the cube fields (except addition of new char) u may need to delete the cube data..
regards,
Srini

Error while Transporting Update Rules.

hi xperts,
   I am getting Error while Transporting the Update rules,i already transported the INFOCUBE,INFOPACKAGE EVERYTHING.
    Start of the after-import method for object type R3TR ROUT (Delete Mode)
Errors occurred during post-handling RS_AFTER_IMPORT for ROUT L
The errors affect the following components:
    BW-WHM (Warehouse Management)
Is the error,I didn't change any thing in the Cube or changes to Update rules.
Can anybody Help me?.
   thanking you,
                               with regards,
                               Narendra.

Hi,
Are you still facuing the issue ?
No need to worry about the routines, once you save the update rules if there is any routines in it it will be saved in the same request. If you want to check the routines you can check in the transport connections. Transfer the update rule to the right hand side of the screen and you can see all the routines that belong to the UR.
If you know the technical names of the routines you can check in the TADIR table.
Have you transported the info-sources for this update rules ? why not you again capture the info-source and the update rule in a single request and transport again.
Hope it helps.
Thanks,
Soumya

Error while transporting Queries

Hi,
I am getting this error while transporting queries!!
Object '!ZTIC_UKA' (ELEM) of type 'Query' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name '!ZTIC_UKA' (in transport request ELEM) of type 'Query' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System Response
The object was not taken into account in the next stage of processing
Thanks

Hi Murali,
YOu are trying to transport the element ZTIC_UKA' of the query,may be an variable which is not colelcted in the request.
Try to transport the query through RSA1> Transport connection->Query-->give you query name -->Drag and Drop to Right hand side and Click on collect all dependent objects and check whetehr they have collected in the same request.Make sure ur variables are collected.
Tranport it now and Check.
Rgds
SVU123
Edited by: svu123 on Mar 4, 2010 7:41 AM

Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /

Guyz,
Firstly despite the plant+storage location + warehouse no. assignments are done , my replenishment delivery (delivery for stock transport order between plants under same company code) is not picking up storage location and warehouse no and thus stopping me from doing picking and PGI (post goods issue).
However in VL02N when i'm trying to change storage location for line item, i'm getting following weird error
*Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /*
I found a SAP Note(133223) regarding this error and VL02 transaction but that note was specific to older versions. I'm on ECC 6.0
Any suggestions please ?
Thanks

Warehouse managment has its own movement types, most identical to inventory management movement types.
These WM movement types are determined via reference movement types.
the error you have just looks like your customizing is not complete.
IMG > LE > WM > Interfaces > IM > define movement types.

Error while transporting a data type

Similar Messages

Maybe you are looking for