Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Mr_Aziziyah on Jul 16 at 1:33 AM Hi All, It's annoying when wage type parameters differ between clients for processing and testing purposes, you know the apples and apples comparison, but we are all to aware of these inconsistencies and then you have the transport sequence issue. What I do is use an external app that gives me control of the wage type landscape with the assigned processing specifications. I use a pasync tool I take a cut of all the WT specs and process a quick comparison. This also controls wage type changes over a period of time to obtain change control accountability. Regards
| | | ---------------Original Message--------------- From: sreedharkadiyala Sent: Tuesday, July 15, 2014 1:21 AM Subject: Existing Wage Types Got Deleted While a New Request is Transported With New Wage Types Our previous consultant has created a wage type 9110 in Quality directly and transported to Production which was working fine. Later I've created a new wage type 9111 in Development and transported it to quality and then to production. My problem here is since 9110 doesn't exist in development, when I moved the request for new wage type 9111 to quality, 9110 got deleted in quality. Is there any solution so that I can retrieve the wage type 9110 in quality and production? | | Reply to this email to post your response. __.____._ | _.____.__ |