Ah, the joys of enterprise software integrations. I bet the developer who came up with these options has a stellar sense of humor. 'ENVIRONMENT_RISK' - is that like the 'Danger Zone' from Top Gun?
Option D with the externalized parameters? That's thinking outside the box! I like the creativity, but I'm not sure it's the most efficient solution for this particular task.
Option C is interesting, but it feels a bit convoluted. Exporting the WSDL from S/4HANA and then importing it into the Sales and Service Cloud communication arrangement? Seems like a lot of moving parts.
D) Create an 'ENVIRONMENT RISK' variable in externalized parameters in SAP Cloud Integration. Update the externalized parameters with the variable for the 'ENVIRONMENT RISK' field. Save and activate the updated externalized parameters.
C) Export the WSDL from SAP S/4HANA. Import the WSDL into the communication arrangement in SAP Sales and Service Cloud. Update the mapping with the new WSDL from SAP Sales and Service Cloud.
B) Download the extended WSDL from SAP Sales and Service Cloud. Import the WSDL into SAP Cloud Integration. Map the 'ENVIRONMENT RISK' target field with source field 'EnvironmentRelevanceIndicator' in the message mapping.
A) Add the 'ENVIRONMENT RISK' field to the target message WSDL in SAP Cloud Integration. Map the 'ENVIRONMENT RISK' target field with source field 'EnvironmentRelevanceIndicator' in the message mapping. Activate the new mapping.
I like the approach in Option B. Downloading the extended WSDL from Sales and Service Cloud and importing it into Cloud Integration sounds like the way to go. Keeps everything in sync.
Terry
10 months agoCasandra
9 months agoRose
9 months agoAleta
9 months agoBulah
10 months agoErnie
10 months agoRosio
9 months agoGenevieve
9 months agoChery
10 months agoLoreta
10 months agoPamela
11 months agoLeslee
10 months agoJean
10 months agoHayley
10 months agoBuck
11 months agoLawanda
11 months agoLou
11 months agoTheola
11 months agoLavelle
11 months agoLayla
11 months agoBurma
12 months ago