C_C4H450_21 Questions and Answers

The ID mapping is verified and adjusted

The single sign-on authentication is set up

The integration flows in SAP Cloud Integration are undeployed.

The integration scenario is technically connected and tested

The code list mapping is completed.

Terminate the SSL connection when an inbound request is received

Verify client certificates

Terminate the VPN connection when an inbound request is received

Communicate via SSL from the demilitarized zone of the customer's network

Analyze inbound traffic with a built-in malware detector

When using a user ID and password for the authentication

After configuring the communication arrangement for the first time

When using client certificates for the authentication

After adding an extension field using the adaptation tools

Use a condition filter in the middleware to ensure other integrations are NOT impacted and all filtering logic can be maintained in one central place

Use custom BAdis to ensure other integrations are NOT impacted by SAP Sales and Service Cloud integration

Use the standard filtering objects in the ALE distribution model. If this is NOT sufficient, use the IDOC_CREATION_CHECK BADI

Use the change pointers BADI, IDOC_DATA_MAPPER. If this is NOT sufficient, use the IDOC_CREATION_CHECK BADI

Service Request to Service Request

Sales Quote to Sales Quote

Opportunity to Opportunity

Ticket to Ticket

Web Service Message Monitoring

OData APl Monitor

EventNotifications

OData Service Explorer

SAP Cloud Integration: Connectivity Test

SAP Cloud Integration: Monitor Message Processing

SAP Cloud Integration: Manage Integration Content

SAP Cloud Integration: Access Policies

Marketing Attribute Definition is uni-directional

Marketing Attribute Values are uni-directional

Marketing Attribute Values are bi-directional

Marketing Attribute Definition is bi-directional

SAP Process Orchestration is configured to use the Java-only stack

SAP Process Orchestration is already in use and can be re-used for the integration project.

SAP Process Orchestration has at least release 7.10.

SAP Cloud Integration cannot be installed within the time frame required for the project.

Identify custom fields early in the project

Include functional, integration, basis, and networking experts on the project team

Set the expectation that prepaclra.ged integration requires configuration

Create extension fields across all systems from the BTP subaccount

Align business processes after setting up prepackaged integration

In the transaction STRUST

In the report RCOD_CREATE_CONNECTIVITY_SIMPL

In the VUSREXTID table view

In the transaction SOAMANAGER

Integration of Master Data

Integration with SAP Cloud Identity

Integration into Sales, Service, and Marketing Processes

Integration with SAP ERP

1. Replicate accounts and contacts from SAP S/4HANA to SAP Sales and Service Cloud.2. Update account details such as address and contact details in SAP Sales and Service Cloud. 3. Send updates back to SAP S/4HANA

1. Replicate products from SAP S/4HANA to SAP Sales and Service Cloud. 2. Update product details such as net weight and material group in SAP Sales and Service Cloud. 3. Send updates back to SAPS/4HANA

1. Replicate opportunities from SAPS/ 4HANA to SAP Sales and Service Cloud.2. Update opportunity details such as related products and status.3. Send updates back to SAP S/4HANA

1. Replicate employees from SAP S/4HANA to SAP SAP Sales and Service Cloud2. Update employee details such as e-mail and phone number in SAP Sales and Service Cloud. 3. Send updates back to SAP S/4HANA

Ports, service bindings, change pointer activation, and report variants for periodic batch jobs

RFC destinations, service bindings, partner profiles, ALE distribution model, and classes

Ports, RFC function modules, outbound/inbound 1Docs, and segment filters

RFC destinations, partner profiles, ALE distribution model, and report variants for periodic batch jobs

Only filtering by BAdl is secure and allows enforced consistency

Reduced load on the middleware (eg SAP Process Orchestration or SAP Cloud Integration)

Data protection, which ensures that sensitive data NOT intended for external systems never leaves SAP S/4HANA

Automatic update of WSDL structure in the target system

Secure communication from on-premise solutions

Secure communication to on-premise solutions

Secure communication between integration flows

Secure communication to other cloud solutions

In the basic authentication artifact

In the 0Auth2 authentication artifact

In the keystore artifact

In the PGP secret keyring artifact

Account Hierarchy

Employees

External Pricing

Customer Material Info

Define Data Replication Model

Define Communication Arrangement

Define Business System

Define Service Group

Define Logical System