SAP EDI -Contract to Hire.
Detroit, MI
6 months contract to hire
Immediate Start
ESSENTIAL DUTIES AND RESPONSIBILITIES:
Must have experience with the ABAP programming language, Dialog programming, User-exits, BADI's, BAPI’s, Smart Forms, IDOCS, ALV, RFCs and other SAP development objects.
• Experience with and knowledge of Workflow applications.
• Good understanding of programming requirements in the MM, PP, SD, FI, and CO Modules and have a strong understanding of EDI concepts.
• Must have experience and understanding of data flow and integration across modules.
• Strong problem solving and analytical skills. Must be able to work individually or with multi-disciplinary team.
• Must understand the software development life cycle and be able to perform systems analysis and design activities in accordance with development methodology.
QUALIFICATION REQUIREMENTS:
Minimum Qualifications:
Bachelor’s degree in Computer Science, Information Technology or related field or equivalent experience
Extensive experience in SAP project life cycle deployments and/or sustain operations
- 5 plus years’ experience in ABAP development activities associated with an SAP system
- Experience working in a multi-instance global organization
- Automotive Supplier industry experience preferred
Reach me at james.smith@netmatrixsolutions.com
Comments pYou can get an overall estimate by looking in SM04 and switching on thebr MB size beside the users so so you will see how much memory the currentbr transactions are using Take into consideration that there is a bigbr difference between dialog transactions with several steps and massbr processing or lists The latter two consume usually a lot more memorybr br 190 MB is not much our usercontextes can become as big as 2 GB per userbr which is the limit on 32bit platforms several times a day This isbr not uncommon on systems that have a lot of data in them however itsbr impossible to give a general advise here since this is VERY different onbr what appications you are running how many systems are connected BWbr CRM APO etc and so onbr br br Start with note 88416 there is explained in depth what it is and how itbr worksbr br For Windows you also should look in note 129813 which will describe thebr rebasing process since M has the start addresses of their DLLs loadedbr into the PXA This is one reason why we switched to a non M operatingbr system because after each IE patch in fact after each patch you needbr to check if the new DLLs will fragment your PXAshared memorybr br Note 546361 can also be helpfull If you have hangs in the system readbr note 530871 which will describe the problem and finally recommendbr upgrading to Windows 2003br br If you have further questions get back to mep