Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

USOBT_C table is not identical in F and Q system

0 Kudos

Hi All,

We can see USOBT_C tables entries are not identical in F and Q system.some transactions are modified but not updates in F system.

we tried to refresh both the systems,but it didn't worked.

Can you please help me in resolving this issue.

Awaiting for your reply.

Thanks,

Darshan

1 ACCEPTED SOLUTION

sdipanjan
Active Contributor
0 Kudos

You can go for:

Download the contents of USOBT_C and USOBX_C (in excel format say) from both the systems and then compare them.

For the discrepancies, please check the Modification browser to identify the Transport request numbers which are yet to go Live in the downstream systems. Transport them.

Else, after identifying the discrepancy, please use the download - upload properties (as mentioned in the attached link provided by Alex) and replace the existing entries by the changed one of the upstream system.

Regards,

Dipanjan

4 REPLIES 4

Former Member
0 Kudos

It sounds like changes were made but not transported, alternatively they could be different releases.

Have a look at this thread for ideas on synchronising them:

morten_nielsen
Active Contributor
0 Kudos

Hello Darshan

There are several reasons why you have these differences. But basically this table is your "own" customizing table, you fill it initally in SU25 and have the option to maintain it as part of your daily "Security Maintenance", the entries here is therefore base on:

1. Manual Correction made in SU24

2. Transport - The entries in USOBT_C from your Development system might not imported in your F and Q system, or not in the correct order, or only partially etc.

3. Maintenance in SU25, in here you do the initial Fill of USOBT_C and upgrade it etc.

Even Though not all of your USOBT_C is required throughout your landscape, my recommendation here is that you maintain this data on your development system and make sure to transport it through your landscape.

If needed you can Transport the table from SU25 "3. Transport of Customer Tables".

Regards

Morten Nielsen

sdipanjan
Active Contributor
0 Kudos

You can go for:

Download the contents of USOBT_C and USOBX_C (in excel format say) from both the systems and then compare them.

For the discrepancies, please check the Modification browser to identify the Transport request numbers which are yet to go Live in the downstream systems. Transport them.

Else, after identifying the discrepancy, please use the download - upload properties (as mentioned in the attached link provided by Alex) and replace the existing entries by the changed one of the upstream system.

Regards,

Dipanjan

0 Kudos

To avoid this kind of issues in future you need to check for the below....

1) Transport route is in order.

2) Update access to these tables are given in a controlled way in each system.