Transport request problem

[Former Member]

hi,

When ever i transport any customizing request from development server to production server the releasing,import happens properly, but the changes is not updated.

regards,

Prabhu

points assured.

[Satyabrata_Basu]

Hi Prabhu,

Do you import them to correct Client of Production system ? The customizing transports are client specific, so, if they are imported into a different client than you are looking, you will not find them.

Cheers !!

Satya.

PS: Points always encourage me to reply....

[Former Member]

hi satya,

That is all perfect,no problem while transporting to production, my ABAP objects are perfect.only with Customizing requests.

regards,

Prabhu

[Satyabrata_Basu]

Hi Prabhu,

Yes...but do you mention te client number in Production ? If you development client number is different than the production client, target client number has to be properly mentioned when you import.

ABAP objects are client independent, and so visible from all clients.

Can you let me know your development client number (where transport request was created and released), Production client number (where transport request is to be imported), your one Import log in detail (paste it) and how you are checking to see the customizing requests have not been updated (by logging on to which client do you check in production) ?

Cheers !!

Satya.

[Former Member]

Hi satya,

thanx for ur reply

I my dev server client no is 005 and the Production server client 900,i am not importing between clients, i am doing it in different server.

The transportation happens fine not an issue at all.

ex log:

Display restricted to target system PRD

Log overview for requests from import queue PRD

DEVK914383 New vendor A/c grp LTSB Lighting Switches Baddi 07-08-07

PRD System PRD

Selection for Import 07.08.2007 12:12:41 (0) Successfully Completed

Import 07.08.2007 18:13:57 (0) Successfully Completed

Check Versions 07.08.2007 18:14:02 (0) Successfully Completed

Import steps not specific to transport request

Feedback after export or import 07.08.2007 18:14:56 (0) Successfully Completed

Activate inactive runtime objects 07.08.2007 18:15:22 (0) Successfully Completed

Feedback after export or import 07.08.2007 18:16:14 (0) Successfully Completed

regards,

Prabhu

[Satyabrata_Basu]

Hi Prabhu,

When you transport between two systems and don;t exclusively specify the Target client, it imports in the same client number from where it was released. So, if you have a client called PRD-005, you should be able to see your customizing transports there.

Check the detailed import log (DEVI914383.PRD) for example for to see which client in PRD it actually imported ...

Cheers !!

Satya.

[Former Member]

hi satya,

I am clear on transporting, there is no problem with different client since we have only one client in production server and i am transporting to the correct client, that is not at all problem.

regards,

Prabhu

[Satyabrata_Basu]

Hi Prabhu,

Could you please paste one detailed import log of such request....The logname should be something like:

DEVI914383.PRD (when TR number: DEVK914383)...

Cheers !!

Satya.

[Former Member]

this is OS log

MMUSER1 W PRD 3 0 0 0 2 0 0 0 0 2 620 . 0 0 0 0 0 005

#A

#/1/ A G D U R C _ M Z RELE EX. _ _ _ _ _ CLI

DEV f 0000 20070807121232 DEVSERVER APServiceDEV

DEV e 0000 20070807121235 DEVSERVER APServiceDEV

PRD < 0000 20070807121241 DEVSERVER APServiceDEV

DEV E 0000 20070807121241 DEVSERVER APServiceDEV

PRD I 0000 20070807181357 PRDSERVER APServicePRD

PRD V 0000 20070807181402 PRDSERVER APServicePRD

and i have already posted the R3 import log.

regards,

Prabhu

[Satyabrata_Basu]

Hi Prabhu,

thanks for the log. You see the target is 005 and not 900.

MMUSER1 W PRD 3 0 0 0 2 0 0 0 0 2 620 . 0 0 0 0 0 <b>005</b>

#A

#/1/ A G D U R C _ M Z RELE EX. _ _ _ _ _ CLI

DEV f 0000 20070807121232 DEVSERVER APServiceDEV

DEV e 0000 20070807121235 DEVSERVER APServiceDEV

PRD < 0000 20070807121241 DEVSERVER APServiceDEV

DEV E 0000 20070807121241 DEVSERVER APServiceDEV

PRD I 0000 20070807181357 PRDSERVER APServicePRD

PRD V 0000 20070807181402 PRDSERVER APServicePRD

How do you perform the import ? Via STMS or via OS command (tp import) ?

also, could you check the tp import command line exact from the ULOG<xx>_<n> file (under /usr/sap/trans/log) ?

Cheers !!

Satya.

[Former Member]

Hi satya,

I have released in 005 client in development server, imported in 900 client in production server.

-> there is only one client 900 in production apart from the default client( 000,001and 066).

-> I do only with STMS, OS level transport is not recommended.

-> I examined the previos log which has been sucessfully transported and affected that also shows the same 005.

regards,

Prabhu

[Satyabrata_Basu]

Hi Prabhu,

This is really strange. Does it happen for all Customizing client or only for few ones ?

Could you try one request via OS level to see what's going on ?

tp import <TR no> <SID> Client900 pf=<profile> -D Transdir = <transdir>

Cheers !!

Satya.

[Former Member]

Hi Prabhu,

It might be that your PRD is expecting a QA step to have been performed in your QAS?

Another possibility is that you are not authorized to display vendors in PRD?

Cheers,

Julius

[Former Member]

Hi satya,

Thank u very much my problem solved, that was because of order of importing the request.

regards,

Prabhu

[Satyabrata_Basu]

Hi Prabhu,

Thx for the feedback. Glad that the problem is solved now

Cheers !!

Satya.