Graziela,
I have been going back and forth with Bryan Droney at SAP via incident 177925 trying to gain a clear understanding as to how I am to accomplish the same results with the new sync tool as with the traditional SAP TUB transports. Below is what he sent to me and what I replied with most recently. Can you answer the questions that I have?
| 03/03/2015 - 14:21:52 EST - Reply by SAP | | |
Hi Michael,
The assumptions of
the steps include:
"c. You have Clients 000, 090 & 300 in SAP System
and are all
having TUB NNN Data."
The steps include:
1. Use sync
tool to update 000 in productive mode.
2. Save cross-client data in workbench
transport "A"
3. Save client-specific tables in customizing transport
"B"
4. Logon to client 090 and compare client-specific data between 000
and 090 for the
client-specific tables and create customizing request
"C" on client
090 with the changes
available in 000 client.
5. Copy the
customizing transport "C" of Client 090 to Client 300 and
originally created
work
bench transport "A" of client 000 to client 300.
6. Update regulatory
bulletin TUB NNN+1 to 300 dataset of TF10
database schema.
These steps all take place on the same system, before moving Workbench
transport "A"
and
Customizing transport "C" to other QA/PROD/etc systems.
Please try
these steps with the clients appropriate to your system,
and let me know if
this
resolves this issue for you.
Regards,
Bryan Droney 03/03/2015 – 20:26 EST - Reply by
SAP
Hi Bryan,
I have taken what you sent and inserted the system names and
client
numbers of our landscape and included several questions that I
need
answered. I attached a word document that is easier to read.
Please
review this and let me know if I have misstated anything.
“The
assumptions of the sync tool steps include:”
"You have Clients 000, 045 &
020 in SAP DV2 System and all are having
TUB 046 Data applied."
The steps
include:
1. Use sync tool to update client 000 in productive mode for both
the
cross-client and the client-specific data.
2. Save cross-client data
in workbench transport "A" to be used for
client 000 of the QA2 and PRD
systems.
3. Save client-specific tables in customizing transport "B" (What
is
the purpose of this transport?)
4. Logon to client 045 and compare client-specific data between client
000
and client 045 for the
client-specific tables and create customizing
request "C" on client
045
with the changes available in 000 client.
5. Copy the customizing transport
"C" of Client 045 to Client 020 and
originally created workbench transport "A" of client 000 to client 020.
(Since the workbench transport contains only
the cross-client tables,
what is the purpose of attempting to transport them
to the same system?)6. Update regulatory bulletin TUB 046 to client 020 dataset
of TF10
database schema.
(This must be the first step in the process
before executing the sync
tool since the BSI TF10 tables are input to the
tool right?)
All steps are to take place on the same system, before moving
Workbench
transport "A" and
Customizing transport "C" to other QA2/PRD/etc
systems.
Regards,
Michael Nunnally |