BFC - Transport - Granularity

[deepesh_kumar]

Hi All,

IN BFC / FC transport,

Is it possible to transport one dimension member from a list of total 10 members?

In this case the |SCOPE dimension has 10 dimension members and I need to move only one memeber to quality and then to production.

Regards

[Former Member · Accepted solution]

Hello,

The transfer of some reference value members is not possible via tasks. The ‘reference table members’ object in  Send tasks transfers all members.

You can  use the copy/paste from excel to copy one or more references members from one database to another (more details in user guide).

I hope this helps you.

Best regards,

Emna.

[deepesh_kumar · Accepted solution]

Hi Emna & Siwar

Thanks for the reply.

In my case I need to move the Scope dimension member. When I try to copy the member from Dimension builder to excel sheet it is not getting copied. But I am able to copy the other dimension members from RU, AC etc. For SCOPE, I am not able to download to excel.

1. Is the above behaviour expected ?

2. Is it possibile to transport the scope dimension?

3. Even if I transport the Scope dimension, will I be able to create multiple versions of the same in the Production directly instead of doing the transport every time there is a change in the Scope.

Thanks

[siwar_taleb · Accepted solution]

HI,

you can transfer scopes via a send object task, you have to  select the ccope builder object in the definition tab of the task.

Siwar

[siwar_taleb · Accepted solution]

See the picture bellow:

[Former Member · Accepted solution]

Hi Deepesh,

1 - Yes, it is an expected behavior that SCOPE dimension members can not be coppied and pasted like Account or RU dimension.

2-Yes you can transport it via send task as Siwar shows in the screenshot.

3-You can create versions of scope at production site, even if you transport the dimension member from development site. But, if you transport the SCOPE itself (instead of dimension member), then you won't be able to change it at production and need to make the changes at the development site and transport it each time a scope change occurs.

You can not transport members one by one but all reference table of a dimension. Before that, you should decide on the approach you want to follow; are you going to manage a new scope (i.e. if a new scope emerges) in the development site or in the production site. 

By the way, I wouldn't recommend transport by excel for any of the dimension members. It may end up with several issues regarding consistency between development and production. Always transport members with send object task.

[siwar_taleb]

Hi Kumar,

The Send Objects task enables you to prepare the objects to be sent and select the correspondents  who will receive them.

First, you define the objects you want to send and where you want to send them.

In your case, you have to selectopn Scope builder object.

The program then prepares the data packets to be transferred and sends them to each  correspondent.

Regards,

Siwar