Urgent requirement: SAC (Sap Analitic Cloud) SAP Business Technology Platform

Apply : Click here 

SAP  Business Technology Platform (BTP) Specialist – Custom Application Development & IntegrationWe are seeking an experienced SAP Business Technology Platform (BTP) Specialist with proven expertise in designing, developing, and deploying custom applications that seamlessly integrate with the broader SAP Business Data Cloud ecosystem, including SAP Analytics Cloud (SAC), SAP Datasphere, and other SAP solutions.The consultant will play a key role in enabling digital innovation and extending SAP’s cloud capabilities by building tailored, scalable applications that support complex business scenarios and data-driven decision-making.Key Responsibilities:Design, develop, and implement custom applications on the SAP Business Technology Platform (BTP).Integrate BTP applications with SAP Datasphere, SAP Analytics Cloud, SAP S/4HANA, and other SAP and non-SAP systems.Utilize BTP services such as SAP CAP (Cloud Application Programming Model), SAP Fiori, SAP UI5, and SAP Integration Suite to deliver robust, end-to-end solutions.Collaborate with functional teams to translate business requirements into scalable technical architectures.Ensure security, performance, and reliability of cloud-based applications and services.Implement best practices for DevOps, CI/CD, and application lifecycle management within the SAP cloud environment.Provide technical advisory and hands-on development to enable innovation and rapid deployment of SAP extensions.

Core Competencies:Strong experience with SAP Business Technology Platform (BTP) and its core services.Proficiency in SAP CAP, Node.js, Java, or Python for back-end development.Solid knowledge of SAP UI5, Fiori Elements, and front-end development on BTP.Experience integrating with SAP Datasphere, SAP Analytics Cloud (SAC), and SAP S/4HANA.Understanding of OData, REST APIs, and event-driven architectures.Familiarity with authentication, authorization, and identity management in SAP BTP.Excellent analytical skills and ability to work independently or within cross-functional project teams.
Preferred Qualifications:SAP Certification in BTP, Extension Suite, or Integration Suite.Experience with SAP Datasphere modeling, data federation, or data integration.Knowledge of Cloud Foundry, Kubernetes, or container-based deployments.Exposure to SAP Build Apps, SAP Mobile Services, or Low-code/No-code development tools.Summary (for LinkedIn “About” section):Experienced SAP Business Technology Platform (BTP) Consultant specializing in the design and implementation of custom, cloud-based applications integrated with SAP Datasphere, SAC, and S/4HANA. Skilled in leveraging BTP services such as CAP, UI5/Fiori, and Integration Suite to deliver scalable, innovative business solutions. Passionate about driving digital transformation through agile development and intelligent data integration.

Apply : Click here 

Urgent requirement: Python Developer : remote location

Job Title: Python Developer

Location: Remote Experience: 3–7 years

Employment Type: Full-time

Apply: Click here 

Job Summary:We are looking for an experienced Python Developer with strong expertise in FastAPI to design, build, and maintain high-performance APIs and backend systems. The ideal candidate will have hands-on experience with modern Python frameworks, RESTful API design, and cloud-based deployments.

Apply: Click here 

Urgent requirement: Blackline Consultant : USA onsite

Description

Rate: $70/hr on W2 Client -IBM/Financial Domain

Apply: click here 

Job details :

Finance Professional with 10+ years of RTR, General Accounting, Controllership, Transitions, Automations, Process Transformations & Standardization and BlackLine Financial Close implementation certified.

Experience with various finance tools, BlackLine implementation, SAP, etc.

Assist in customizing and configuring BlackLine modules (Account Reconciliation, Transaction Matching, Journal Entry, Variance Analysis, Task Management) to meet clients' financial close needs.

Provide hands-on support in integrating BlackLine with existing ERP and financial systems, ensuring smooth data flow.

Help clients align their internal controls and business processes with BlackLine modules, ensuring they are designed to optimize financial close workflows.

Provide training and ongoing support to key users and system administrators, helping them fully leverage BlackLine's features.

Prepare and validate cut-off procedures and hyper-care plans, ensuring a smooth transition into live operation.

Offer continuous support post-implementation to troubleshoot any BlackLine-related issues, provide system updates, and assist in performance optimization for clients.

Apply: click here 

Use case in SAP CPI

 Why Groovy is Powerful in Integration (especially SAP CPI)

SAP CPI provides many standard tools like Message Mapping, Content Modifier, etc. But real-world integrations often need custom logic, such as:

 Complex data parsing (e.g., splitting a CSV file, filtering records) 

 Custom message transformation (e.g., dynamic XML or JSON generation) 

 Header/property manipulation (e.g., set Authorization header based on token) 

 Dynamic behavior (e.g., choose endpoint URL based on some condition) 

Standard flow steps are not enough for these, so SAP provides Script Step where Groovy is used.

Example Use Cases in SAP CPI

Use Case	Groovy Script Role
Transform CSV to XML	Parse CSV line by line and generate XML format
Set CSRF Token in Header	Extract and set token for HTTP request
Filter out invalid records	Loop through records and skip based on conditions
Generate Atom XML	Build deep insert XML payload for OData
Format DateTime	Convert date formats as required by receiver

Groovy in SAP CPI gives flexibility and control when standard flow steps fall short. It enhances your ability to customize, transform, and control data and integration logic to meet complex business needs.

In Short, Groovy = "Custom logic engine" inside SAP CPI

It gives developers the power to go beyond the limitations of graphical tools. It’s ideal for: 

 Complex data manipulation 

 Dynamic behavior 

 Fine-grained control over message processing 

Prints the Message

 def messageLog = messageLogFactory.getMessageLog(message);

messageLog.addAttachmentAsString("Payload", message.getBody(String), "text/plain");

 message.getBody Logs the message body for debugging or monitoring purposes. 

 addAttachmentAsString("Payload" Attaches the payload as a string with a label (e.g., "Payload") in plain text format. 

 Helps trace message flow without modifying the actual message content.

Complete example – Fetch and Modify Data

import com.sap.gateway.ip.core.customdev.util.Message;

def Message processData(Message message) { 

    // Get Header and Property

    def sourceSystem = message.getHeader("SourceSystem")

    def docType = message.getProperty("DocumentType")

    // Get Body

    def body = message.getBody(String) 

    // Add new header

    message.setHeader("ProcessedBy", "GroovyScript")

     // Modify Body (append a note) 

    def newBody = body + "\n<!--Process by CPI-->"

    message.setBody(newBody)

     return message;

return message; }

Fetch Property & Set Property

 def myProperty = message.getProperty("MyProperty")

 It retrieves a custom property (often set earlier in a flow or message processing pipeline) with the name "MyProperty" from the message object. 

 It accesses a property attached to the message. 

 Properties can be metadata like headers, variables, or values set during previous steps in a flow.
 These are not part of the body (i.e., the payload or content) of the message.

message.setProperty("NewProperty", "PropertyValue")

 Stores flow-level variables used during message processing. 

 Helps with internal logic like decision-making or transformations. 

 Does not affect headers or body, keeping the payload and metadata clean. 

Fetch Body & Set Body

 def body = message.getBody(String)

 is used to fetch the body (payload) of a message and cast or convert it to a specific type — in this case, a String. 

 message.getBody() — fetches the body (the main content of the message). 

 message.getBody(String) — fetches the body and tries to convert it to a String, if it's not already.

message.setProperty("NewProperty", "PropertyValue")

 Flow-Specific Data: Stores data used only within the current flow or context. 

 Temporary Storage: Holds intermediate values (e.g., flags, counters) without affecting headers or body.  Internal Logic Use: Useful for conditions, expressions, or scripting during processing.