| Author | Message | ||
Maverick Legend Username: Maverick Post Number: 67049 Registered: 01-2008 Posted From: 107.77.97.50 Rating: N/A |
Finally oppincha..2 versions, will delete later from q after validation  There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Vjawarrior Legend Username: Vjawarrior Post Number: 33508 Registered: 02-2014 Posted From: 68.53.21.199 Rating: N/A |
sesani mothukunnaa kooda mav oppukovatkledu.... so 2 different programs tappateldu... no one does that unless its a completely different req... anthagaa kavalante...debug lo manipulate cheskovali Q lo thru the same code if possible by changing some variables using edit in debug... | ||
Junior_no1 Megastar Username: Junior_no1 Post Number: 24042 Registered: 09-2014 Posted From: 27.59.217.22 Rating: N/A |
testing kosam rendu complex abap programs antey vammo VRUDDHA NAARI PATHIVRATHA | ||
Vjawarrior Legend Username: Vjawarrior Post Number: 33504 Registered: 02-2014 Posted From: 68.53.21.199 Rating: N/A |
 | ||
Junior_no1 Megastar Username: Junior_no1 Post Number: 24035 Registered: 09-2014 Posted From: 27.59.217.22 Rating: N/A |
 VRUDDHA NAARI PATHIVRATHA | ||
Aaples Junior Artist Username: Aaples Post Number: 374 Registered: 07-2016 Posted From: 193.70.63.13 Rating: N/A |
existing version is slightly modified to new version with this additional selection of keys from C table also. They want to keep both versions. | ||
Vjawarrior Legend Username: Vjawarrior Post Number: 33501 Registered: 02-2014 Posted From: 68.53.21.199 Rating: N/A |
both are separate report programs....not diferent versions as per your case... bigbochh is trying to prove himself an OAF...he doesnt know he already is one... | ||
Aaples Junior Artist Username: Aaples Post Number: 373 Registered: 07-2016 Posted From: 193.70.63.13 Rating: N/A |
your requirement can be done very easily. also can keep two versions in single environment with simple steps. once i seen a report program extracting 180 fields from 15 different tables. one version joins primary keys from a & b tables while other version joins primary keys from a, b & c tables. in the starting screen, user was selecting which version he needs output from. | ||
Vjawarrior Legend Username: Vjawarrior Post Number: 33474 Registered: 02-2014 Posted From: 68.53.21.199 Rating: N/A |
mav...report program aa idi? if so, create a copy of the same program V0 as V1 and transport as independent object to Q. (this shud be an independent program and shudnt be an enahncement like a badi or sth) so u have 2 report programs in q now...and test as u wish... version ane wording vaadamaaku as that will create confusion... a new version implies that its an update to the existing code. but okati gurtunchuko...a new program means...it requires separate FS,TS,approvals, justification, change management vaallu saava denkutaar... but if u r the boss...ivanni lite... | ||
Gsn1 Side Hero Username: Gsn1 Post Number: 5210 Registered: 03-2008 Posted From: 100.36.157.96 Rating: N/A |
Mav --------- open cheyyakarledu poni..D lo ne rename(copy chesi) chesi to _old, original program ni modify chesi..rendu promote cheyyachu ga q ki, and when move to prod, just ingore _old in q and move only changes to prod.. ----------- The idea is to have a clean QA system. The _old, _1, _2 etc. are just in D where there will be log of junk and test programs. Only those that are meant to go to production usually moves to Q. If you want, you can have ZPROGRAM_1 and copy it to ZPROGRAM_2 and modify it for the newer version logic and move both of them to Q and test them out. Depending on what you want to keep, delete the other one in D and have that delete action transported to Q there by deleting the unwanted version. Just a thought. Sesani ----------- Bhayya.. entha friend aina do u really think they will open up the system for code changes? Config ante sare talli bidda nyaayam... code changes ante sontha pella aina accept cheyyadu emo... ------------ Who knows, Mav might be a BIG SHOT in his company and he can call shots -  . When you have power, you can do anything. | ||
Sesani Legend Username: Sesani Post Number: 57250 Registered: 08-2014 Posted From: 108.171.131.170 Rating: N/A |
it gets complicated.. and thats why u need to understand what is a t-code (transaction code)... Custom program may have a t-codes (assuming its a report for now)... users will not have access to run the program directly so they are given t-codes to make their life easy and for security purposes... ur old program has a t-code assigned and new program will also need one.. in order for u to make it work - create a program A.1 with current/old program and totally new t-code (optional if u have access to run programs in QA) - new program name should be same name as old/current program with old/current t-code assigned to it - move changes to QA and test - delete the A.1 program and then move everything to Prod.. lekapothe lots of garbage in prod. if at all Idi antha mee manager approve cheste, foto ettu.. linked in la add chesi ammalakka dobbuta for approving this... | ||
Maverick Legend Username: Maverick Post Number: 67038 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
open cheyyakarledu poni..D lo ne rename(copy chesi) chesi to _old, original program ni modify chesi..rendu promote cheyyachu ga q ki, and when move to prod, just ingore _old in q and move only changes to prod.. sarle..its not in my control anyway on how they do it There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Maverick Legend Username: Maverick Post Number: 67037 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
nuvvu t code anaku..i am not sap..edo yes no alright sap lo.. what iam saying issss..nuvvu cheppinanni mnoves deletes levu d has new version already. before moving to q, i want the version in q to be backed/renamed to _old, move new version to q, test both..leave _old in q, move new to prod.. There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Sesani Legend Username: Sesani Post Number: 57249 Registered: 08-2014 Posted From: 108.171.131.170 Rating: N/A |
Bhayya.. entha friend aina do u really think they will open up the system for code changes? Config ante sare talli bidda nyaayam... code changes ante sontha pella aina accept cheyyadu emo... | ||
Sesani Legend Username: Sesani Post Number: 57248 Registered: 08-2014 Posted From: 108.171.131.170 Rating: N/A |
missed this.... it is not possible in SAP... Program name cannot remain same for A.1... it has to be a new name all together... testing comes after all this... naa point is nee testing convenience kosam nuvvu intha mandiki problem create chestunnav antunna (approvals etc)...
Lets say the old program name is Z_MAV_EFFECTIVE_TESTING. This has a t-code Z_MAV. Now u create a new program Z_MAV_EFFECTIVE_TESTING_1 and add a new t-code Z_MAV_1 - nuvvu first Z_MAV_EFFECTIVE_TESTING_1 in QA ki move chesi test chesi - then overwite Z_MAV_EFFECTIVE_TESTING with Z_MAV_EFFECTIVE_TESTING_1 chesi - delete Z_MAV_EFFECTIVE_TESTING_1 chesi - QA ki changes move chesi, malla testing chesi appudu prod ki move cheyyale... ur testing twice right there... nen 2nd time test cheyyanu ante nai chalega... Maa SAP world atla undadu Mav... nuvvu mari comedy chestunnav babbai | ||
Maverick Legend Username: Maverick Post Number: 67036 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
anni program levu le..unna kooda..all 50 changeed anuko..creating 50 new versions and doing a diff of 2 ouput takes less time, than manually testing those all those 50 ouputs, comparing against table blah blah idi manual..laborious process..and u test this for every field..its insane amount of time.. why can i keep 2 versions in Q,just promote the final version to prod. There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Gsn1 Side Hero Username: Gsn1 Post Number: 5209 Registered: 03-2008 Posted From: 100.36.157.96 Rating: N/A |
Mav -------------- i just need a old version to test in q..if testing passes u move the modified version to prod..dantlo vinta emundi abuse emundi..nuvvu ela test chstav -------------- This cann't be done unless you have a friend/buddy in Basis team who can open the Q client for changes, then you can bring the old version back up and activate it and test it. Once you are done with the testing, you can overwrite this version with the D version and close the Q client again. | ||
Sesani Legend Username: Sesani Post Number: 57247 Registered: 08-2014 Posted From: 108.171.131.170 Rating: N/A |
anduke kada Mav testing chesedi... U test to make sure the existing co. cds are not messed up... u can compare the report output with table level data to make sure its extracting the data correctly... new code ki kuda same table level check cheyyocchu... I have never heard abt having 2 programs doing the same or similar thing in SAP... at least for testing purposes.... out side SAP nen be be... ok.. even if it changes, check the delta and see what changed for existing co. cds.. i really doubt there will be more than 5% change in data... this is way easier than getting 2 programs approved... Imagine this.. my current client has 50+ custom programs... every change ki i ask my manager for A.1... | ||
Maverick Legend Username: Maverick Post Number: 67035 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
ehe ivvani untai..where is testing in this all? code review cheste testing chesinatta? i just need a old version to test in q..if testing passes u move the modified version to prod..dantlo vinta emundi abuse emundi..nuvvu ela test chstav There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Gsn1 Side Hero Username: Gsn1 Post Number: 5208 Registered: 03-2008 Posted From: 100.36.157.96 Rating: N/A |
Mav, As long as you don't move D version to Q, you can execute latest version (A.1 in your terminology) in D and since it is not moved to Q yet, you can execute original version in Q (Version A in Q system). | ||
Sesani Legend Username: Sesani Post Number: 57246 Registered: 08-2014 Posted From: 108.171.131.170 Rating: N/A |
Mav babbai i dnt know which client ur working for... but nen pani chesina konni clients la if u have to change a piece of code it requires multiple approvals (from functional, technical, PMO, business owners), code review (common practice), performance review (depends). etc etc etc... documentation pakkaga undaale... u cant just add some BS bullet points and move the code... Atlaantidi nuvvu oka existing program ki A.1 version maintain chesi, testing chesi, i will revert it after testing ante physical abuse ki digutaaru emo | ||
Maverick Legend Username: Maverick Post Number: 67034 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
say, the extract populates based on a if else logic kotta condition add chesaru anuko, how do u prove it some offshote developer has not messed it up? i think all u sap folks have the same mind..outside sap world,its a very easy thing to switch versions...simple diff file a file b ane testing kante emi better untundi.. it can change..when the entire system is being tested..they may modify open orders in january as part of testing..controlled data set undadu as the time between these 2 programs execution increases There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Sesani Legend Username: Sesani Post Number: 57245 Registered: 08-2014 Posted From: 108.171.131.170 Rating: N/A |
honestly in my sap experience... i dnt think any PMO or manager would agree and approve for this... at least they wont buy the argument of effective testing... when ABAPer writes the code, thats when they specifically say these changes are applicable to this company codes only... adi code la restrict chestaru kada.. u maintain those co. cds in a set or a table or a tvarvc variable wat ever is the client specific process... testing difficult ayithadi ani 2 versions maintain chestaa anedi i would personally not buy it... when u think ur changes are only for specific co. cd u dnt have to test the rest of 9 co. cds... u test 1 more as regression to make sure the rest didnt get affected...antha kaani mottam 9 in and out test chese avasraam ledu, waste of time..
Why dont u run the old report with a date stamp.. like the data for month of Jan or so... when u move ur new version (which overwrites the old) run for exact same date stamp... old co. cd should still have same data because i dnt think anybody will post data in past periods... I am not saying u cannot have A and A.1 in QA (two program parallelly) but thats a very inefficent way of doing it anta... ide cheste every program ki 2 versions pettale inka... | ||
Maverick Legend Username: Maverick Post Number: 67033 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
the other way to test is run program a first, move transport and run program a1. this transport move say if it takes 3-4 days(process over head), and the underlying data changes, it will produce changes which will be hard to explain..ee sodi anta deniki why not keep 2 versions, run both of them one after the other, just do a diff, find changes..oka roju lo test cheyyachu There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Maverick Legend Username: Maverick Post Number: 67032 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
effective testing.. say u have 10 dvisions in teh company, they use different company codes and they have built processes that rely on the extract produced by this program..say the extract is producing 50 fields today and now a new division in the company is requesting a change to this program..how do you ensure that the changes caused by this new request for a new division are not impacting the rest of the divisions?..say the change requested will add new fields, and modify the existing fields with company code specific logic the simple and effective way i would do is, run old version of program A, run this for a specific date range in qa..run the new version for the same date range in same qa immediately, take the outputs and do a diff..its a thorough and effective test...ideally nothing should change for old divisions, except new fields(which are ignored by them)..for any changes, u should be able to eaily explain...mottam anni dvisions ippudu testing cheyyalante kudaradu kada.. There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Sesani Legend Username: Sesani Post Number: 57244 Registered: 08-2014 Posted From: 108.171.131.170 Rating: N/A |
Why do u want 2 versions babbai? Whats the requirement to have 2 versions? process wise kuda adi justifiable kaadu... u should never have 2 versions of the same program beyond Dev system.. Just for comparison purpose ante why dont u re-create the issue/scenario in dev or in sandbox with 2 programs and play around to see the comparsion? Then move to QA... QA daaka enduku move cheyyale code ni? Data issues in Dev?? If u still wanna do it... Original Version A, new version A.1 Create A.1 as a separate program all together and move to QA... after u finish testing decide on which version u want and delete the other one in Dev and move to QA then to Prod.. | ||
Boeing747 Side Hero Username: Boeing747 Post Number: 2507 Registered: 04-2016 Posted From: 70.162.116.98 Rating: N/A |
eesari kotha transport request ki ila cheyyi- Open a new transport req. then Using SE38 -> utilities->Versions->Generate version | ||
Boeing747 Side Hero Username: Boeing747 Post Number: 2506 Registered: 04-2016 Posted From: 70.162.116.98 Rating: N/A |
theres already a version management inbuilt for Abap | ||
Maverick Legend Username: Maverick Post Number: 67031 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
they say we have to revert back all changes in dev, build a copy with new changes and then move to qa..prod nunchi A ni A.1 or B kinda tecchukolema? There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Biggboss Side Hero Username: Biggboss Post Number: 3163 Registered: 08-2017 Posted From: 45.62.177.6 Rating: N/A |
why not use versioning system like git to manage this code? | ||
Maverick Legend Username: Maverick Post Number: 67030 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
ask is simple..how do u effectively and quickly test. say program is A BEFORE STATE A(DEV) A(QA) A(PROD) AFTER STATE A, lets call it A.1 (program name remains the same, just a new code) (New version) (DEV) A(QA) A(PROD) To test A in QA, Can i easily have A.1 AND A IN QA? I dont care if u call it A.1 vs A or B vs A ee transports gola ardham kaadu naku..sap side anta easy ga versions pettalemu..ilaa aite when we move this transprt to prod, both a.1 and a untai..thats a bad practice antaru There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs | ||
Boeing747 Side Hero Username: Boeing747 Post Number: 2505 Registered: 04-2016 Posted From: 70.162.116.98 Rating: N/A |
i mean for your QA testing if you "dont" want to duplicate the code into two programs | ||
Boeing747 Side Hero Username: Boeing747 Post Number: 2504 Registered: 04-2016 Posted From: 70.162.116.98 Rating: N/A |
Generally when u modify the existing program for new changes, you comment out the old code (i mean the old logic/lines) with a date/version number. and whatever new logic/code you are adding/modifying you will comment a line with the change request or ticket number. for your testing in QA if you want to duplicate the code into two programs then execute the program with old code and then comment it out and execute with the new changes to compare | ||
Tweety Side Hero Username: Tweety Post Number: 2706 Registered: 04-2008 Posted From: 173.225.160.178 Rating: N/A |
Maava as far as I know I would create two programs a with one version,b with second version and move those trasnports seprate. once tested completely remove one program or transport from queue other option is for testing purpose retrieve old version if QAS allows | ||
Maverick Legend Username: Maverick Post Number: 67027 Registered: 01-2008 Posted From: 165.225.50.165 Rating: N/A |
Custom ABAP programs versions maintain cheyyatam is it a big deal in SAP? Say you have 3 sap instances for dev qa and prod. all have a abap extract program that fetches data and creates a file say with 50 fields. now for a new development you modify that program in dev..how hard it is to keep the new version and the old version in qa to compare the outputs..how does this work with a sap transports? There's a cacophony in the truth, A melody in lies and it accompanies one on every journey, From the lows to the highs |