Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
You can create a transport and export from Dev - Production. It is not really required to have a sync between the systems since while exporting you will have option to select only those tax codes which you require. Consideration should be given with the entries in OB40 acct keys which needs to be in sync It is a Audit issue if we create directly in production however always its a exception to bypass this. On Sat, Jul 24, 2010 at 5:40 AM, LindaSue via sap-acct < sap-acct@groups.ittoolbox.com> wrote: > Posted by LindaSue(SAP Coordinator) > on Jul 23 at 7:46 PM In > my experience, we maintain in DEV and transport to our other systems but... > the "valid from" date in each tax code is overwritten and replaced by the > date on which the transport was imported. I have had to reset this date > manually in each system. This was back in 4.7 so the problem may be resolved > by now. > > ---------------Original Message--------------- > From: Sindhu_Chugh > Sent: Tuesday, July 20, 2010 10:20 AM > Subject: FTXP transporting tax change or tax code > > > In the last 6-7 years we have been making any tax rate changes or > creating new tax codes directly in the SAP environment (not transporting). > Our basis team will like us to transport any tax related changes in future. > In your organization do you transport or directly make the tax related > changes/setups in the SAP environment? Secondly, can you think of any risks > if we start transporting tax changes after setting them up directly in a > client for so many years? Thank you. | __.____._ Copyright © 2010 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | Related Content White Papers In the Spotlight _.____.__ |