SCA file

[Former Member]

Hi,

In our environment we have four steps from Development to Production:

Development, Consolidation (Quality Assurance), Preproduction (User Acceptance Test), Production

We have our DCs/Web Dynpros split between several tracks, each one of those has the same custom SC "PROJECTS".

Now when a change request/activity goes from Consolidation to Preproduction, a SCA file is made via Assembly.

I was wondering, since we have several tracks but only one SC, how the SCA file was made.

Let's say that I have tracks A, B and C and I have two activities on development A, two activities on consolidation B, and two activities on consolidation C.

1) If I make the assembly of the track B activities, what changes will the SCA contain?

Let's suppose that after the assembly of track B I make the assembly of track C.

2) Now if I send the track C SCA into production before of the track B SCA, which changes will I get in the production environment?

Thank you.

Pietro

[Former Member · Accepted solution]

There would be track connection made between these individual tracks. Please refer this particular previous post to get a better idea.

Regards,

Mahesh

[Former Member · Accepted solution]

Hi,

thanks for the links, they are very informative.

I've checked our Landscape Configurator: we do not have Track connections between tracks.

Given that, are you able to answer my questions?

Thank you,

Pietro

[Stefan-EA]

Hi,
> In our environment we have four steps from Development to Production:
> Development, Consolidation (Quality Assurance), Preproduction (User Acceptance Test), Production
> 
> We have our DCs/Web Dynpros split between several tracks, each one of those has the same custom SC "PROJECTS".
> Now when a change request/activity goes from Consolidation to Preproduction, a SCA file is made via Assembly.
> I was wondering, since we have several tracks but only one SC, how the SCA file was made.

Are the same portals used on tracks A, B and C?

> Let's say that I have tracks A, B and C and I have two activities on development A, two activities on consolidation B, and two activities on consolidation C.
> 1) If I make the assembly of the track B activities, what changes will the SCA contain?

Since consolidation is before assembly, the assembled "PROJECTS" SC of track B will not have the changes that are sitting in the Consolidation tab of track B. After assembly, the "PROJECTS" SC will then be ready to be imported into the Test tab (your pre-production system) in the Landscape Configurator.

> Let's suppose that after the assembly of track B I make the assembly of track C.
> 2) Now if I send the track C SCA into production before of the track B SCA, which changes will I get in the production environment?

If tracks A,B and C use the same portals and they all have the same SC called "PROJECTS", the "PROJECTS" SCA from track C will overwrite the "PROJECTS" SCA on the production portal.

There is one catch. The NWDI will not overwrite an SC on a portal if it is older than the one already deployed to the portal. Since the "PROJECTS" SC in track B was assembled before the "PROJECTS" SC in track C and the "PROJECTS" SC in track C was deployed first, you will not be able to deploy the "PROJECTS" SC in track B.

If you must deploy the "PROJECTS" SC from track B, you can undeploy it from the portal using the SDM deploy tool if you are on 7.0X NetWeaver portal or NWDS if you are on 7.1 or newer NetWeaver portal.

Another option is to delete the system state using the [CMS Support Tool|https://service.sap.com/sap/support/notes/973346].

[Former Member]

Hi Stefan,

thank you for your reply.

> Are the same portals used on tracks A, B and C? 

Every step (development, consolidation/QA, test/preproduction, production) has its own server. There is one server per step, so all the tracks have the same server/runtime environment in every step.

> Since consolidation is before assembly, the assembled "PROJECTS" SC of track B will not have the changes that are sitting in the Consolidation tab of track B. After assembly, the "PROJECTS" SC will then be ready to be imported into the Test tab (your pre-production system) in the Landscape Configurator.

I was expecting that the PROJECT SC of track B had the changes that are sitting in the Consolidation tab of track B. Was that a typo or you really meant that?

> If tracks A,B and C use the same portals and they all have the same SC called "PROJECTS",  the "PROJECTS" SCA from track C will overwrite the "PROJECTS" SCA on the production portal. 
> 
> There is one catch. The NWDI will not overwrite an SC on a portal if it is older than the one already deployed to the portal. Since the "PROJECTS" SC in track B was assembled before the "PROJECTS" SC in track C and the "PROJECTS" SC in track C was deployed first, you will not be able to deploy the "PROJECTS" SC in track B.

But track C's SCA file, being assembled after track B's SCA file, will have also the changes made on track B's DCs?

The problem is that in a setting like ours, I cannot figure out how this SCA file is made... I think that it should be a "merge" of all the projects residing over all the different tracks. Am I right?

Thanks again,

Pietro

[dao_ha]

Hi Pietro,

I believe Stefan meant that since the consolidation step is before the assembly step; therefore, when you assemble your SC, it only takes whatever is in the Assembly tab and not the ones that are sitting in the Consolidation tab (which are not imported yet).

Anyway, you can always take a look at the log files (Assembly tab --> select your SC --> Details --> View Log File) to see exactly which DCs were propagated and exported to your test RTS.

Same thing in the Approval tab, go to Details --> Content --> Propagation List of SCA to see which DCs were actually propagated to the production RTS.

[Stefan-EA]

> Let's say that I have tracks A, B and C and I have two activities on development A, two activities on consolidation B, and two activities on consolidation C.

>

> > Since consolidation is before assembly, the assembled "PROJECTS" SC of track B will not have the changes that are sitting in the Consolidation tab of track B. After assembly, the "PROJECTS" SC will then be ready to be imported into the Test tab (your pre-production system) in the Landscape Configurator.
> 

> I was expecting that the PROJECT SC of track B had the changes that are sitting in the Consolidation tab of track B. Was that a typo or you really meant that?
> 

If the activities are sitting in the Consolidation tab of track B, then they have not been imported into the the workspace yet. This is why I said that they will not be part of the Assembled SC. You will need to import them into Consolidation first if you want them to be part of the assembled SC.

> But track C's SCA file, being assembled after track B's SCA file, will have also the changes made on track B's DCs?

The only way to include changes from other tracks is if you have setup track connections.

> The problem is that in a setting like ours, I cannot figure out how this SCA file is made... I think that it should be a "merge" of all the projects residing over all the different tracks. Am I right?

With track connections, your code changes can propagate from different tracks automatically. Depending on your needs, you may want to setup repair connections from track A->B, A->C and B->C.

More info.

http://help.sap.com/saphelp_nw70/helpdata/en/13/602b27f6fb41b4a9eb4f72eabb9832/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/ba/2e61fda9764a29833ddc41feb4e113/content.htm

You can expand on the above to include many tracks.

[dao_ha]

Hi Pietro,

I'm not sure what you meant by your DCs 'split between several tracks'. Are your tracks on the same RTS? Are you doing parallel developments? Please provide more details about your environment setup and what exactly you're trying to achieve.

Each track has its own repository in the DTR so I believe each track rather has its own copies of your 'shared' DCs. The transport activities in the NWDI's Transport Studio only affect the concerned track; so,

1) if you assemble track B, it has nothing to do with the contents of track A.

2) if you have only 1 production env for all the tracks, then the production env will have the last deployed SC's contents (if you do have the same named DCs/SCs). In your example, the production env will get the contents of track C's SCA. What else do you expect?

Hope it helps.

Dao

[Former Member]

Hi Dao,

thank you for your reply.

> I'm not sure what you meant by your DCs 'split between several tracks'.  Are your tracks on the same RTS? Are you doing parallel developments? Please provide more details about your environment setup and what exactly you're trying to achieve.

Every step (from development to production) is linked to one run time system (i.e. : we have one development server, one quality assurance/consolidation server, one test/preproduction server and one production server).

We have several tracks: every track, excluding SAP standard SCs (dependencies), has only one custom SC named "PROJECTS" (the name is the same in every track). Every track, inside the PROJECTS SC, has a different subset of DCs.

For example: Track A has DC AccountingDc; Track B has DCs ClientManagementDc and so on... (of course we have multiple DCs per track but if a DC is in track A, for instance, then that DC is not in any of the other tracks)

In that way we can send in test and in production different DCs in separate times. I know that this may be not an optimal design, but I inherithed this situation and I cannot change it.

Hope that makes it clear now.

Pietro