Transport Release Strategy

[Former Member]

Hi everyone,

I have a problem in transporting release strategies (entries in table T16FS). Although I get the request from the source system, when I transport it to the target system, I see that the strategy was not transported.

I have observed the oss note 86900. I follow the same way which is told in note.But it does not work?

Anyone who has an idea?

Waiting for your help..

Best and Kindest Regards,

Tolga

[Former Member · Accepted solution]

Hi ,

Especially when you change something frequently Thera may be many problems about release strategy .

When I implemented it , I had many same problems and I cleared all thing and did it almost again .

I know it is not logical but I solved this problem so . You must do it one times true

p.s. Data entered in classification screen didn't transfer with request transport . You must enter them in production . It is not logical too , isn't it

[Former Member]

Hello. Besides doing the transport you need to ALE the classification. This is done with several steps:

In the source client: We use transaction ZV03 (distribute classification via ALE). I don't know what you would use in your system, since this starts with 'Z' I expect it was something we developed. I specify the class type '032' and the class name (for the release strategy) After that I use BD88 to process the outbound IDOCS. Message type is CLFMAS.

In the receiving client: I use transaction BD87 to process the inbound IDOCS. Same message type as with BD88.

You may also need to execute transaction CL24 - which allocates objects to the class.

If you can figure out the ZV03 process/step this should get the complete strategy transported.

Karen.