cancel
Showing results for 
Search instead for 
Did you mean: 

Transport sequencing in ZMHF

Former Member
0 Kudos

Hi All,

Is it possible to sequence the TR based on the dependency while import to QAS system in a UC.

I wanted to know the possibilities of the TR sequencing especially after release. The release order will not be the same as the import sequence.

Kindly guide.

Thanks,

Subhashini.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Subhashini,

Normally the import sequence will be depond upon the TR release sequence in the development.

So not able to control the import order, it will take automatically the TR release sequence and import.

Rg,

Karthik


Former Member
0 Kudos

Hi Karthik,

Thanks for the reply.

Is there any note or any Standard SAP Document available for this.

I have to convey this to the client . they might ask for a confirmation.

It will be veryhelpful if you could share any.

Thanks and Regards,

subhashini.

prakhar_saxena
Active Contributor
0 Kudos

Hi Subhashini,

I know that client will never accept unless you show them proof.

Here is the proof.....goto solar_project_admin click on Change Management tab

now click on "No Variant For Task List Assigned" Tab

Here click F1 in the buffer column and below strategy from SAP will be detailed out

*************************************************************

Leave Transport Request in Buffer after Import, or Delete

Definition

Existing Import Strategy

The existing import strategy distinguishes between two types of import:

Normal and validated corrections are always imported together, i.e. all transport requests for a CTS project, in the import buffer, are imported into the system together, in the order of their release (project import). The transport requests are then removed from the import buffer.

Urgent corrections must get from the development into production as quickly as possible, so urgent corrections are always transported individually, i.e. only the transport requests for the urgent correction are imported. There is usually only one (there can only be one changeable transport request for an urgent correction; but you can create another after release, if required). After import, the transport requests of the urgent correction stay in the import buffer. They are imported with other CTS project transport requests in the order of their release, and are only then deleted from the buffer, during the project import, like the other transport requests.

You must ensure consistency between urgent corrections, manually , i.e. the user must ensure that the import sequence of urgent corrections matches the release sequence; in particular if there are technical or semantic dependencies between them.

As the project import imports validated and urgent corrections together, in their release sequence, inconsistencies caused by urgent corrections (different import sequence from release sequence) may be repaired.

SAP recommends this import strategy.


New Import Strategy

The new import strategy handles all imports like urgent corrections, but the transport requests are removed from the import buffer after import, so the import buffer is small.

If you do not import in the release sequence, inconsistencies can occur which you can no longer repair by importing the project, because the buffer entries no longer exist.

SAP does not recommend this import strategy.

There may still be reasons to use this import strategy, usually if you are only making small changes which are not interdependent. Only the developer can determine which transport requests are to be imported and which not, if there are interdependencies. In such a case import individually with the new import strategy, not in a project import.

If you use the new import strategy (because you only have urgent corrections, you do not want to import the project, a full import buffer is a risk , import buffer size, ...), you can no longer import the project in the generated task lists. You can only import individually. A project import in the task list is cancelled.

Most phases in the task lists have no meaning in this import strategy. The new import strategy has a simplified phase model comprising the phases 'Created', 'Maintenance' and 'Completed', and a new procedure type.

*******************************

I hope above will clarifies all doubts and satisfy your client as well with SAP Recommended import strategy

Regards

Prakhar

Answers (2)

Answers (2)

Former Member
0 Kudos

Thanks Prakhar and Jhansi  for your replies...

Thanks for the confirmation...

It gives me a confidence that I have told the right and can show this to the Client.

Thanks again...

Regards,

Subhashini.

Former Member
0 Kudos

Hi,

One of the finest thing with Charm is the Transport Sequence, its always in the order of get released in Dev system, it avoids risk and issues of forgotten transports , and transport sequence violation

which will go well with Transport of copies concept. Once ToC confirmed with successful then your orginal TR released, so the releasing order follows to Production Import.

So if you want to skip or avoid any TR moves to PRD, we can deal all with Toc.

Best understanding check here , Read the section Charm Driving Factors.

Thanks

Jansi