Skip to content

Commit 57ec14d

Browse files
updates
1 parent a439b0d commit 57ec14d

1 file changed

Lines changed: 49 additions & 1 deletion

File tree

_interviews/2026-03-05-real-sap-abap-interview-questions-otc-pricing-odata-btp.md

Lines changed: 49 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -279,7 +279,7 @@ The ABAP driver program collects business data and passes it to the Adobe form i
279279

280280
---
281281

282-
# 16. Did you work on OTC process in PepsiCo?
282+
# 16. Did you work on OTC process in your projects?
283283

284284
Yes.
285285

@@ -396,6 +396,54 @@ Binding allows applications to access credentials and connection configurations.
396396

397397
---
398398

399+
# 25. When integrating SAP with a third-party SaaS system that performs calculations, where should the calculation logic reside?
400+
401+
In enterprise architectures the calculation logic should remain in the **third-party SaaS system** because that system owns the business rules for the calculation.
402+
403+
SAP acts as the transactional system that:
404+
405+
sends required input data
406+
receives calculated values
407+
applies results to SAP business documents
408+
409+
This design keeps systems loosely coupled and avoids frequent SAP code changes when SaaS algorithms change.
410+
411+
---
412+
413+
# 26. Where should mapping logic between SAP and third-party SaaS payload be implemented?
414+
415+
Mapping logic is usually implemented in the **integration layer** such as:
416+
417+
SAP CPI (Integration Suite)
418+
SAP PI/PO
419+
SAP BTP integration flows
420+
421+
Middleware handles:
422+
423+
payload transformation
424+
protocol conversion
425+
field mapping between SAP and external systems
426+
427+
In small integrations mapping can be done directly in **ABAP programs**, but enterprise systems typically manage mappings in middleware.
428+
429+
---
430+
431+
# 27. How do you map calculated values returned from the SaaS system back into SAP?
432+
433+
When SAP receives the response payload (usually JSON or XML), the ABAP program parses the response and extracts the calculated values.
434+
435+
These values are then populated into appropriate SAP structures depending on the business process.
436+
437+
For example:
438+
439+
pricing conditions in sales order
440+
document fields during transaction processing
441+
custom fields in SAP tables
442+
443+
The values are updated before the transaction is saved so that SAP documents reflect the calculated results from the external system.
444+
445+
---
446+
399447
# Final Thoughts
400448

401449
These questions represent **real enterprise interview discussions** for senior SAP ABAP developers working in production environments.

0 commit comments

Comments
 (0)