SAP Convergent Charging Architect

Unable to sponsor - ONLY Candidates that don't require any sponsorship are accepted

Job title: SAP Convergent Charging Architect

Work Location: Detroit, MI 48226 - Onsite

Minimum years of experience: 10+ years

Job Description:

Skill required SAP Convergent Charging

5- 8 years Experience in BRIM Convergent Mediation and Convergent Charging implementations. End-to-end know-how of BRIM process flow;

Exposure in client-facing roles;

Good exposure in SAP ABAP and Web service development.

Preferable Utility Energy experience.

Experience and Strong knowledge of J2EE (EJB, Servlet/JSP, XML)

Knowledge of BRIM architecture

Experience in HTML, CSS, JavaScript Strong knowledge of Oracle, SQL programming and tuning, stored procedures

Strong knowledge of Unix, Windows, JVM, Web servers, and Application servers

Experienced in security programming and concepts

Extensive hands-on experience with the SAP Convergent Charging Core tool, Admin tool, and Bart tool.

Worked on Chargeable Item Class, Pricing Macro, Charge Plan, Rating & Charging for One Time, Usage and Recurring Charges, Product Cross-Catalog Modelling.

Working experience on Mapping and rating tables.

Have good knowledge of the Provider Contract & Subscriber Account - Billable Item Mapping & Consumption Item Mapping Integration.

Experience in the Utility or Telecommunication Industry using the Convergent Mediation tool will be a great asset, with knowledge of the following tool functionalities

Data Acquisition (Batch & Real-time)

Data Validation

Enrichment & Analysis

Filtering, Error & Duplicate Checks Merging/Splitting and Correlation

Routing

Format Conversion

Working knowledge and expertise to support (create new/modify existing functionality of) mediation zone workflows responsible for communicating and loading data (usage) into SAP CC or CI directly

Experience of working with usage aggregation policies to build an end-to-end usage record/file, similarly reverse engineering to break down consolidated usage data into granular level based on requirements downstream (eg., for accounting or revenue allocations, etc.)

Adequate product knowledge to support E2E design discussions in an integrated BRIM implementation, running detailed design sessions, adapting to new business requirements, ensuring optimization of building blocks in CM to avoid performance tuning/gaps with high volume data needs