Integrating SAP Ariba with SAP S4HANA (Mohana Singh Divya Srivastava) (z-library.sk, 1lib.sk, z-lib.sk)

【One-Line Pitch】 A hands-on configuration companion for SAP integration specialists who need to connect SAP Ariba and SAP Business Network with SAP S/4HANA or SAP ERP through the SAP Ariba Cloud Integration Gateway. It is written for practitioners who already know their way around SPRO and want a step-by-step path from add-on installation to live transactional and master data flows. 【Book Arc】 - **Opening (~0%–10%)**: Frames the integration landscape—master data and transactional data flows between SAP ERP/SAP S/4HANA, SAP Business Network, and SAP Ariba solutions—and establishes the required service pack levels before installation. - **Early (~10%–30%)**: Moves into the Cloud Integration Gateway setup itself: interface configuration for IDoc and web service connections, partner profiles, sender/receiver definitions, and the general settings that govern document status updates and supply chain collaboration. - **Early–Middle (~30%–47%)**: Applies those foundations to SAP Business Network transactional data, walking through PO collaboration, subcontracting, service sheets, and the parameters that control each document type. - **Middle (~47%–57%)**: Shifts to master data integration, covering user profile and role mapping, native integration programs, and the background jobs that export master data to Ariba. - **Late (~57%–onward)**: Extends into strategic sourcing transactional integration—quote messages and awards converting into POs or contracts—and supplier lifecycle topics, including custom mapping and BAdI-based enhancements. 【Key Takeaways】 - **The Cloud Integration Gateway is the spine of the whole book** (Opening): every integration path—Ariba Network, sourcing, master data—runs through this gateway, so understanding its interface setup is the prerequisite for everything else. - **Interface configuration splits cleanly into IDoc and web service tracks** (Early): outbound and inbound messages are configured separately, and the Execute button provisions proxy and IDoc connections in one pass, with logs checkable via SLG1. - **Document status updates are a deliberate design choice, not automatic** (Early): because some integrations use IDocs whose status is not pushed immediately, you must decide when and which statuses to send, then schedule the relevant background programs. - **Master data integration depends on role and realm mapping** (Middle): user profiles must be maintained per solution, and FPC-enabled realms require the realm name to map roles correctly. - **Native master data integration is job-driven** (Middle): a long list of ARBCIG_MDNI_* programs (company code, cost center, GL account, material group, plant, purchasing org, and more) are scheduled as background jobs via SM36. - **Sourcing awards flow back as quote messages** (Middle): an award from SAP Ariba Sourcing becomes a quote message that converts into a PO or contract, with enumerations (F for purchase order, K for contract) deciding the outcome. - **Custom mapping and BAdIs are the escape hatch** (Late): when standard mapping does not fit, BAdI implementations such as supplier confirmation mapping let you inject custom logic. - **External format and time zone settings matter in real landscapes** (Early): parameters control whether numbers are sent with or without preceding zeros, and plant-specific time zone conversion keeps dates aligned when ERP and the Ariba data center differ. 【Reading Tips】 - **Deep-read the general settings chapters first.** The interface setup, partner profile, and sender/receiver definitions are referenced repeatedly later; skimming them will make the transactional chapters confusing. - **Treat the transactional chapters as reference, not narrative.** PO collaboration, subcontracting, service sheets, and supply chain collaboration each follow a similar configure-and-map pattern—read one closely, then skim the rest for parameters unique to each document type. - **Keep SPRO open alongside the book.** The excerpts are heavily menu-path driven; following the paths in a sandbox or test client will cement the sequence far better than reading alone. - **Note the background job programs.** The ARBCIG_* program names and SM36 scheduling steps are easy to overlook but are what make the integration run in production. - **Pay attention to the BAdI and custom mapping sections if your landscape is non-standard.** These are where the book moves from configuration into extension. 【Coverage Limits】 The excerpts cover the integration architecture, Cloud Integration Gateway setup, SAP Business Network transactional configuration, master data integration, and the start of strategic sourcing and supplier lifecycle topics. Later chapters on supplier lifecycle and performance, and the full depth of custom mapping and BAdI implementation, are only partially represented in the available excerpts.