This will happen almost 65% of the time especially u join those  consulting sap companies (there are few where I not going to name any).

Pretty much, even as senior, don't take things for granted. It will come back and bite  back. For those juniors, it will going to be hard lesson. I went thru that scenario b4 in a foreign consulting company with local management. They don't like u, they will make u suffered both at project site and in office until they force u to resign or give them a reason to fire u.

all the best loh u better go 'kilat' the senior's shoe nice nice.. coz when u enter sap, it's like eating a piece of their pie liao.. they got no reason to teach u abt sap at all..but will instead 'throw u into the deep sea' and hope u will give up and leave sap. So, must make them like u first, then only they accept u as "brother" and teach u stuff.

I did this before 2 years back. Barcodes are read using an app created with Java. Setup JCO connections and RFCs and you're ready to go.

Transport Management System (tcode STMS) -> System Overview. this is to check how many systems are connected in one transport domain (meaning in one landscape).

not sure about your question about differentiating login in e.g. DEV and PRD systems. i just know that the user tables (USR*) consolidates users PER SYSTEM PER CLIENT. can you please elaborate your question?

SM51 only displays the instances within ONE SAP SYSTEM.

now i get the second question. if ever some SAP systems are within the same server, yes they will have the same ip address. but two items differentiate them - SAP systemID (like mentioned above), and the system number (two digit number).

How long u been in sap? 6,7 Months?

Crazy 2,3 months can do what?
SD/MM,FI simple reports display in alv, some conversion programs, and sapscript layout changes can la!
Some functional folks sometimes so stupid to think abaper just do coding in abap.

There are lot of stuffs la in abap, function modules, conversion programs using badi or bdc, sapscripts, smartforms, adobe form,
BSP, webdynpro, screen programing, badi, function module exit, data dictonary objects; tables,
data elements, structures, lsmw, workflow, idocs, and alot more la.
And the hardest i think is doing coding in object oriented because the design is the most important!
If ur design fail, everything will fail especially for complex requirements or to follow specific design
patterns eg: MVC. For simple program is sup sup sui.

And i havent talk bout performance tuning, sometimes this part is the most difficult one. Even to improve
1 sql statement also can takes a lot of time, need to try a lot of ways, views, inner join, subqueries, buffer, and ect..
And if everything fails the no choice; data archiving.

And do coding in abap also u need to code in the most efficient way, u need to know when to use local structures,
when to use field symbol, when to use CHECK statement, when to use IF Statement, when to use binary search, before use
binary search what u should do first, before use FOR ALL ENTRIES statement what u should do first to avoid the sql select all records
in the table, when u should use HASHED table and what are the do's n donts when coding abap and ect..
U think all these can cover in months meh?

And sometimes, being abaper u need to know some BW basic stuffs oso, because sometimes BW people needs abaper to do complex coding
for them. Eg: u need to know Start routine, end routine, routines in the transformation, need to learn to create
cubes, infoobjects, ods, load the cube, ods, master data, schedule them in process chain, do codings in ADP, do some variable
exit in CMOD to be used in query desginer, sometimes need to code in javascript for WAD,
and blablablablabla... Zzz..Zz....

Btw, u hardly can find good abapers in sap consulting firm la, because consulting firm dont really need a good abaper
escpecially the small sap consulting firm. They just need 2,3 seniors and the rest juniors and teach them the basics
like sapscript, do reports in alv, smartforms, conversion program, some stuffs in data dictionary, and
some badi or function module exit.
Thats all. And repeat again and again for different projects.
Some functionals(not all) are so stupid to think being abaper is so easy. Try to be one la before talk so much.
Thats why some abaper can easily tapau functional folks salary if they really good in what they doing.
Ceh.

is ur compnay using SAP All-in -One?

hello sifus,
I just want to know what are the important things that new SAP basis needs to know. What is the 'essence' of basis??

@antaeusguy,

I was a fan of sapfans.com until when there were some irresponsible posters who posted their specs. and asking for people to help them. I stopped frequenting the site eventhough, I do from time to time, participate in the discussion.

I hardly go to sap's sdn .. too many junks, cut & paste suggestions in there.  What they're interested is to get as many points as they can w/o really reading the problem and giving the probable solution to the original problem. The best is still Uncle Google .. I could search and most of the time, it went to either sapfans or sdn anyway

So what do I suggest? Register to both, sdn and sapfans .. and don't expect to be spoon-fed