Changes after transport are not reflecting in QA and Production

[Former Member]

Hi All,

We changed two table settings in developemnt system table names are ALMBCADM & ALMBCDATA.

We modified the table technical settings as "buffering allowed but de-activated". After we transported the change requested in QA Prod enviornment ,the changes are not getting reflected in the systems. Technical settings in both the systems are still showing as "Buffering is switched off". What could could be the reason behind this???????

Regards,

Prashant

[Former Member · Accepted solution]

Hi,

what options you have selected while transporting the reuest.

Thanks & Regards,

Vidyadhar K

[Former Member · Accepted solution]

Hi All,

Transported ended with return code 0 in both QA and prod systems.

I am not sure about the transport options we have taken while doing the import.

most likely we have done the normal transport .Please let us know if we need to select some option for doing the import for these dictionary tables.

thanks in advance.

Regards,

Prashant

[Former Member · Accepted solution]

Hi Prashant,

The transport request generated automatically at the time of modification or you included the object after modification to the transport request created manually?

Regards

Ashok Dalai

[Former Member · Accepted solution]

Hi Ashok,

We included the object in the already created transport request provided to us.

Pls suggest.

Regards,

Prashant

[Former Member · Accepted solution]

Hi Prashant,

You include the object with below way

Program Object Type Object Name

LIMU TABT ALMBCADM

Regards

Ashok Dalai

[Former Member · Accepted solution]

Hi Ashok,

That means we will now have to create a new change request for the same.

Also please let me know why we need to follow the process suggested by you??

Why import has not happend earlier?

Regards,

Prashant

[Former Member · Accepted solution]

Hi Prashant,

You can create a new request and include the object again.In the previous run you may have included the wrong data type.

This will decide what datatype you will include in the TR

the data type LIMU TABT will transport the Technical Attributes of a Table and here that is your requirement.

For example if you will take R3TR TABU then it will transport the table content.

Regards

Ashok Dalai

[Former Member · Accepted solution]

Hi Ashok,

I have checked the CR from SE01 from objects tab , and found these entries-:

Program ID Object Type Object Name

LIMU TABT ALMBCADM

LIMU TABT ALMBCDATA

Which I suppose is correct.

Please advise.

Regards,

Prashant

[Former Member · Accepted solution]

Hi Prashant,

Yes ,you have the correct setting.

Can you repeat the transport once more and check.

Regards

Ashok Dalai

[Former Member · Accepted solution]

Hi All,

We resolved the issue by creating a new transport request and importing it in quality and production systems.

Regards,

Prashant

[Former Member]

Hi Prashant,

What do the transport logs show? Any errors/warnings?

Regards.

Ruchit