Job Description
Full details about the role and requirements
Yukerja Summary
The SAP ISU CRM Technical role at PradeepIT Consulting Services Pvt Ltd is curated from Himalayas (category Teknologi & IT). This role is marked as remote — check timezone and location requirements on the official listing. Yukerja.com is not the employer — applications are handled on the official source site.
Job Title: ISU CRM Technical
?Experience: 10+ Yrs ( relevant 7 to 9 yrs in SAP ISU CRM is required)?
Work Timings: 1p.m to 10 pm
Work Type: WFH
Job Description:
- SAP CRM ABAP with Function modules, Reports, Data dictionary, Object-oriented ABAP programming, BADI- s, BAPI- s, ADOBE forms ,
- SAP CRM WEB UI with BOL Programming , GENIL , UI configurations, Transaction launcher, AET,
- Interfaces with RFC, ODATA, SPROXY, web services,
- ISU CRM with SAP CRM One Order framework, ISU data model(added advantage), S4HANA Service management(added advantage).
1x SAP IS-Utilities CRM/ISU Technical
- (7-9) years of hands on SAP CRM/ISU Abap programmer with at least one SAP IS-U project full implementation.
- They must be very competent with Object Orientated code (OO) breaking the code up into small methods and putting the minimum code in the program.
- They should be able to pick up a task, work on it themselves, thoroughly test it and hand it back.
- They should be use to putting in plenty of documentation in their code, before a logic block (*) and after most lines (").
- Must have knowledge and experience in the following development components:
1) ?General Abap + OO code.
2) ?ISU and CRM experience.
3) FI
- Good to have knowledge and experience in the following development components:
1) BADI
2) ?BDocs
3) Workflow
4) ?Adobe form
5) ?Alv/salv
6) ?WebUI
7) ?SRM
8) IDocs
9) ?FIORI
- Strong communication skills required: written, verbal, strong interpersonal skills and able to participate actively in project requirement discussions and business process analysis.
- Ability to work collaboratively across the different SAP work streams (functional and technical teams) and with the different stakeholders.
Originally posted on Himalayas