BEx query transport getting Failed

[Former Member]

Hi Experts,

I imported newly developed BEx query from Development to Quality,But getting following error,

Post-import method RS_AFTER_IMPORT started for ELEM L, date and time: 20140129092437

Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Activation Mode)
Error when activating element DGV210RU1OIP7MA8JPJ1T55FV

Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Delete Mode)

Summary of invalid objects from request GBDK919386
Errors occurred during post-handling RS_AFTER_IMPORT for ELEM L
The errors affect the following components:
   BW-WHM (Warehouse Management)
Post-import methods of change/transport request GBDK919386 completed
     Start of subsequent processing ... 20140129092437
     End of subsequent processing... 20140129092437

I checked table RSZELTDIR in Quality, 'M' version of query is Available.

I thought of try reimporting after deleting existing 'M' version of query using T-code but I dont found option to delete 'M' version of query to delete.

So again I captured all query elements and query in new request and imported it again,but getting same error.

Recently we upgraded the Support Pack from 10 to 13 ,I suspect the issue might be because of that.

existing SAP release is BW 7.1

Kindly give some input.

Regards,

J.Sakthikumar

[RamanKorrapati · Accepted solution]

Hi,

Have you tried to reimport again.

if you query was saved properly then recollect into new transport and release it.You need to collect all elements of your query. at RSA1---> transport connection, using grouping option only necessary objects.

coming SP13 - its problematic one. check to degrade your sp level or go for higher than 13 if available.

Thanks

[Former Member · Accepted solution]

Hi Ram,

I tried Reimport,then again collected all the objects in new TR and imported it.

Getting same error.

Regards,

J.Sakthikumar

[former_member185177 · Accepted solution]

Hi Sakthikumar,

Re-collect your BEx query in another transport.  Import it with the below mentioned options in STMS

1) Leave transport request in queue for later import

2) Overwrite originals

3) Overwrite originals in unconfirmed repairs

Hope it resolves your problem.

Regards,

Krishna Chaitanya.

[Former Member · Accepted solution]

Hi Krishna,

Actually BEx query which i transported is new development,

I used to select Leave transport request in queue for later import and Overwrite originals, everytime i import.

Regards,

J.sakthikumar

[RamanKorrapati · Accepted solution]

Assuming as your bex query connected target moved to prod/quality.

Please can you share the error screen shot.

go to SE09 enter your transport request number and find it what is this DGV210RU1OIP7MA8JPJ1T55FV.

That might be may not be saved properly. go to your bex designer open your query change mode, do some changes and  save it.

Again collect into transport, release again.

Thanks

[Former Member · Accepted solution]

Hi Ram,

Below given is the error Screen shot,

DGV210RU1OIP7MA8JPJ1T55FV is UID of Query,I already checked it.

Regards,

J.Sakthi

[RamanKorrapati · Accepted solution]

Against to red error messages there is + symbol. expand them each and read it. what it says.

Have you moved all info objects ,data flow, your target to target systems?

[Former Member · Accepted solution]

Hi Ram,

Already all the objects were moved to quality and done UAT with Cube data,

This query is build on already existing Cube in Dev and quality.

Regards,

J.Sakthikumar

[RamanKorrapati · Accepted solution]

Please refer this note 1593665 .

Are you sure, your collecting all ckf,rkf and variables along your bex query.

Can you check your transport content which you have collected.

[Former Member · Accepted solution]

Hi Ram,

Thanks for your Input,My issue got fixed.

But it shown 1 element as missing obj,but which is not relevant to my Query.

Whether this issue is because of SP 13 upgrade ?

Regards,

J.Sakthikumar

[RamanKorrapati · Accepted solution]

Not sure. But seems like SP13 is bit kind problematic level.

Any way its resolved. nice to hear.

[Former Member · Accepted solution]

Hi Ram,

Thanks for your support,

Regards,

J.Sakthikumar

[KodandaPani_KV · Accepted solution]

Hi sakthi,

please check the object DGV210RU1OIP7MA8JPJ1T55FV. these have getting the issue.

collect the one more time all objects including all query elements.

after collecting the objects check the SE09

and STMS while importing select these options.

Hope it will help.

Thanks,

Phani.

[KodandaPani_KV]

Hi jayaram,

please collect the one more time all queries.

select the transport connection -> select only necessary object and collect manually then do transport.

Thanks,

Phani.