Senior SAP ABAP Developer (SD / Payments / Integration)

Senior SAP ABAP Developer (SD / Payments / Integration)

Location: USA(Los angles,LA)

Travel: 7 days in month – to USA [candidate should have required Travel visa]

Job Type: Contract [6+ Months] – Corp 2 Corp

About the role:

We are integrating SAP ECC with Stripe so that customer-service users can take card payments against sales orders without any cardholder data entering SAP. The solution adds a button to the sales order (VA01/VA02) that launches a Fiori pop-up hosting Stripe's embedded checkout; Stripe returns a token that is written to the standard SD Payment Cards tab, and SAP's payment card engine then authorizes at order save and captures at settlement through custom clearing-house function modules that call Stripe via MuleSoft REST APIs.

You will be the lead ABAP developer for the SAP side of this build: the sales order enhancement, the SD payment card plug-ins, the OData service on SAP Gateway, and the outbound REST integration. The design, reference code and a step-by-step implementation guide already exist; your job is to make it real in the customer's landscape, validate the release-specific parts in a sandbox, and carry it through testing and go-live with a functional SD consultant, a UI5 developer and a MuleSoft developer.

What you will do:

• Implement the sales order header enhancement in SAPMV45A (customer subscreen 8310 "Additional data B", PBO/PAI modules, MV45AFZZ user exits) that launches the Fiori pop-up, shows payment status and applies the Stripe token to the payment card plan (FPLA/FPLTC).
• Build the SD payment card clearing-house plug-ins: card type check, authorization and settlement function modules (copies of CCARD_CHECK_*, CCARD_AUTH_SIMULATION, CCARD_SETTLEMENT_SIMULATION) that call Stripe through MuleSoft, including re-authorization, cancellation and partial capture.
• Work with the SD functional consultant on payment card customizing: card types and categories, checking groups, authorization horizon and validity, clearing house and merchant IDs, account determination, copy control to billing, settlement run (FCC1) and batch authorization (RSCCAUTH).
• Develop the outbound REST client (CL_HTTP_CLIENT / SM59 type G, OAuth 2.0 client credentials via OA2C_CONFIG, JSON with /UI2/CL_JSON), with idempotency keys, structured error handling, an API log table and no sensitive data in logs.
• Build and register the SAP Gateway OData service (SEGW, DPC_EXT) used by the Fiori pop-up and by MuleSoft webhooks, including CSRF handling, authorization objects and hub registration with trusted RFC.
• Design and create the custom tables, data elements, configuration views (SM30), message and exception classes, and authorization objects/roles for the solution.
• Run the sandbox spike that confirms release-specific behavior (payment card plan API, template function module interfaces, field lengths) and adjust the reference code accordingly.
• Support the UI5 developer with the Fiori app (semantic object, target mapping, Launchpad catalog/role, CSP for Stripe.js) and, if SAP GUI 8.x is in use, implement the embedded HTML-control variant with SAPEVENT callbacks.
• Own unit and integration testing on the SAP side against Stripe test mode (approvals, declines, re-authorization, partial capture, cancellation, webhook replay), and produce the technical documentation and transport plan.
• Apply secure-coding practices consistent with PCI DSS SAQ A scope: no PAN/CVV in SAP, no card data in traces, dumps or logs, least-privilege roles for technical users.

What you bring:

Must have:

• 10+ years of hands-on ABAP development on SAP ECC 6.0 (EHP 6–8, NetWeaver 7.40/7.50), including modern ABAP syntax (inline declarations, string templates, ABAP Objects, exception classes).
• Deep SD module knowledge from a developer's perspective: sales order processing (SAPMV45A user exits and BAdIs, screen enhancements, VBAK/VBAP/VBKD), deliveries, billing (RV60AFZ*), copy control, output determination and pricing.
• Solid understanding of SD payment concepts: payment card processing (payment card plan FPLA/FPLTC, card types, checking groups, authorization and settlement, clearing house function modules, FCC1), payment terms, down payments/billing plans, credit management basics and the FI postings that result from card settlement.
• Proven experience calling REST/JSON APIs from ABAP (CL_HTTP_CLIENT, SM59 HTTP destinations, STRUST/SSL, OAuth 2.0 or token-based auth, JSON serialization) and designing resilient outbound integrations (idempotency, retries, logging without sensitive data).
• SAP Gateway / OData development (SEGW, DPC/MPC extension classes, function imports, CSRF, hub/embedded deployment, service registration and authorizations).
• Experience with SAP GUI screen programming (Screen Painter, subscreens, PBO/PAI, GUI controls such as CL_GUI_HTML_VIEWER, CL_GUI_FRONTEND_SERVICES).
• Comfortable working from a design document and reference code, validating assumptions in a sandbox, and communicating trade-offs clearly to functional consultants and business stakeholders.

Nice to have:

• SAPUI5/Fiori development or close collaboration with UI5 developers: manifest and cross-app navigation, Launchpad configuration (target mappings, catalogs, roles), deployment via /UI5/UI5_REPOSITORY_LOAD.
• Prior work with a payment service provider (Stripe, Adyen, Cybersource, Paymetric, Delego or similar) or with SAP Digital Payments Add-on, and familiarity with PCI DSS concepts (tokenization, SAQ scope, MOTO).
• Exposure to MuleSoft or another API platform as the integration counterpart (RAML/OpenAPI contracts, webhook handling).
• S/4HANA experience and awareness of how ECC custom code migrates (custom code analysis, simplification items).