SAP Integration with Concur Solutions Best Practices: Integration via SAP Process Orchestration PUBLICTABLE OF CONTENTS PRELIMINARY REMARKS oc 3 STEP-BY-STEP CONFIGURATION wwsssrsmnsnnnnnmninnnnnnnnnnninnnnnnnnnnnnnseiensnsnnse A Option 1: Configuration via NWDS. Sender Channel. Receiver Channel for Calling the Token Service. Receiver Channel for Exchanging Business Data, Receiver Channel for the Ping Check. Integration Flow. Determine Integration Flow End Point URL. Option 2: Configuration via Integration Builder Sender Channel. Receiver Channel for Calling the Token Service Receiver Channel for Exchanging Business Data. Receiver Channel for the Ping Check. Integrated Configuration Object Determine Integration Flow End Point URL. Configuration enhancements for Credit Card Detokenization scenario. CONCUR INTEGRATION SETUP AND MONITORING TRANSACTIONS. Employee Master Data Expott..... Cost Center Export.. Importing Concur Documents (Fi Posting)..‘The communication between Concur and SAP ERP or SAP S/4HANA is a simple communication running in ‘sort of Point-to-Point (P2P) mode. All communications are triggered by the SAP system, so there are only ‘outgoing calls from SAP to Concur. Since there is no mapping nor content based routing required, the scenario can run in a direct mode without the need of any middleware. However, this integration can also run ina mediated mode in case client's internal policy requires the usage of a middleware. Currently, SAP Cloud Platform Integration is the only middleware being supported out-of-the-box. The usage of any other middleware is basically possible but the customer is responsible to build up the content required to mediate the integration between Concur and SAP system, This document provides best practices showing how to setup and run the integration between SAP ERP with Concur Solutions using SAP Process Orchestration / SAP Process Integration as middleware Note: This is not part of SAP's product shipment. SAP takes no liabilty for this best practices template, PRELIMINARY REMARKS. The current document shows how to setup mediated integration between SAP system and Concur Solutions using SAP Process Orchestration as middleware. SAP Process Orchestration is used as pass-through whereas the following requirements need to be met + The request from SAP Financial has to be passed as is to Coneur, + The response from Concur has to be retumed to SAP Financial as is. + The following HTTP methods need to be supported: GET, POST, PUT, DELETE. +The pass-through Integration Flow needs to be document type agnostic, e., it needs to support the ‘exchange of any document type including the token service call, + The communication is synchronous. + The Integration Flow needs to accept all HTTP header fields that are sent by SAP System which are as follows: = targetURL targetAuthorization = content-type = X-ConsumerKey + The Concur target URL needs to be set dynamically based on the HTTP header attribute targetURL. + The HTTP header attribute targetAuthorization needs to be mapped to the HTTP header attribute Authorization, + The rest of the HTTP header attributes as listed above need to be passed through, + SAP Process Integration or SAP Process Orchestration, release 7.31 SP17 /7.4 SP13/ 7.5 SPO and above + Apply SAP note 2408216 - Corrupted request message when the XML is Unicode BOM (byte order mark)‘STEP-BY-STEP CONFIGURATION In order to configure the routing rules on SAP Process Orchestration / SAP Process Integration, you do have two options: either using the SAP Process Integration Designer perspective in the NetWeaver Developer Studio (NWDS) or using the Integration Builder (Java WebStart Ul). On SAP Process Orchestration, the recommendation is to use the NWDS, on a SAP Process Integration dual-stack / dual-usage type system. however, only the Integration Bullder is supported. Besides this, the choice of tool depends on your preferences. At the end, the same runtime artifacts are created. In the following, we will show you both options. Option 1: Configuration via NWDS. ‘Open the NWDS, and switch to the SAP Process Integration Designer perspective by selecting Window + Perspective + Open Perspective ¢ Other from the main menu of the NWDS, un | Window Help =f New Window Se ator > Appescance > ShowView > [Parnpectve >) OpenPerpectve 9) A Debug Novigation > -—=—CustomizePerspectve. 9. Develorment nrastructure Preferences Save Perspectives. SP Process Modeling Reset Penpectve. Visual Composer Close Perspective HL Web Dynpro Close All Perspectives © open Perspective o x ‘Remote System Explorer BResource BBriako SBiato on EMF Rules Composer ]SAP Management Console SAP Process Integration Adminstration ‘2ESAP Process Integration Designer FESAP Process Integration Runtime © service Composer EP Team Symehronng In the SAP Process Integration Designer perspective, select the connect icon to logon to the Integration Directory of the SAP Process Orchestration / SAP Process Integration system.ABZ (tp N12 (tp// mR aR (BV (p/m) Choose ether conection. In the upcoming logon screen, enter your user credentials, and click on OK. (Connect to Process tegration Integration Directory -ZH4 [tp UserName: [deme Paseword— [» [Z)Use common credential for directory and repository OK Cancel Sender Channel We assume that you have created the sender and receiver communication component already. First, we will create a new sender channel of type REST. Navigate to the sender communication component, and select, New Channel from the context menu. 23 Pielorer £2 [BS Entepraese =O @oBAG - : » @ Systems RP = 4 ae Ep New Sender Agreement Export @ Version History Show Cache StatusIn the upcoming dialog, enter a channel name, and click on Finish. {New Crane a x Create a channel | Enter name and elect» ystem fr the new channel Communication Component [ERP Browse. ar Destin (On the General tab, select adapter type REST, and direction Sender. PassTIvough. REST. Sendor a mtone Pan ST ts ‘Switch to tab General below tab Adapter-Specific. Communication is always synchronous, so select Quality of Service Best Effort. We do use the very same channel to exchange any data format, Right now, the REST adapter supports the data formats JSON and XML. Since we just pass through the message without the need to transform nor access the payload, it usually wouldn't matter which data format we maintained in the channel. However, for XML as data format the REST adapter obviously parses the XML payload, so if the actual payload is in JSON format, the message exchange will fail. This is not the case when choosing JSON as data format, here both will work, .¢., payload in JSON or XML format. So, select JSON as data format for both the input message format (request) and the output message format (response).General Adopter Spectic | Module) Mente General Channa election |REST Resources REST Opecation| Operation Dtumination| Resut HTTP Header Enor Handing Input Mezage Format Data Foxma 1s0N z Character Set HITP Content-type header 5 Clcenver to xm nly OF Serie Quality OF Serie: Beaton ¥ put Mesage Format Dats Format ISON Cistrip Operation rom Mesage outer lement) Character Set Request Message Character Sat 7 Convert XML Palond To SON ‘Switch to tab Channel Selection. Select check box Specify Endpoint, and maintain endpoint as /concurfpassthrough’allobjects. General |Adater-Spectie| Modules| dentin General | Chanel Section] REST Resources] REST Opeaton| Operation Determination] Rest HTTP Header| Emr Honing ‘Channel Selection Aspect Endpoint Endpoine™ [concsn/pntoughalobjeds Clow public acces ine authorization required) (tit to SON Element im te xP ath lement Clim to HTTP Operation ‘Switch to tab REST Resources. Select Custom Pattern as URL Pattern, and set the same as In order to store the HTTP header elements of the incoming callin the XI message header, define the following dynamic attributes. For keeping the target URL, select from the drop down the pro-defined REST ‘Service (service) entry. For the rest of the attributes, select Custom Attribute as Dynamic Attribute, maintain the Custom Attribute Name as listed in the table below, select HTTP Header Variable as Value Source, and maintain the HTTP Header Element as listed in table below. Furthermore, itis important that all attributes are defined as optional, because depending on whether the Concur tokan service is called or actual business data is exchanged, not all HTTP header elements are passed to SAP Process Orchestration, So, for each dynamic attribute select the Optional check box. Note: for the target URL we need to use a pre-defined dynamic attribute since the attribute is later used in @ routing condition, this is not supported out of the box for custom attributes.Type Dynamic attribute name HTTP header element Pre-defined REST Service (service) targatURL Custom atir_targetAuthorization targatAuthorization Custom atir_contentType content-ype Custom atir_consumerkey X-ConsumerKey i Specie Modules | enters {General | Chanel Selection FEST Resources| REST Operation | Operation Determination] Result HTTP Header Err Hanling| URL Pate URL Pate (Gistom Pater y M1 Dynamic Abate Dynamic Atibute REST Seni rence) Ei Value Source: (HTTP Hende vaio Bi ITP Header Element Target options Dynamic Aibute Dynamic Atibute = Gumtom Abu == B Custom Atte Name wi ingethatoaton Value Source: [HTTP Header Variable zy HTTP Header Element” tage@huthoriston Boptiont XaDymamic Abte Dynamic Atibute Custom atribute zi custom stnbte Nome sar contentvpe Value Source: [HTTP Header variable z ITP Header Element content pe option! 1 Dynamic Atrbute Dynamic Atibute Gusto Ate = El Custom Atte Nome aircenaimerey Nalue Source: FaTTP HendeVaabe y ITP Header Element Consumer optionalWe like to store the HTTP Operation of the incoming callin the XI message header. Switch to tab REST ‘Operation, and select HTTP Operation as Value Source, This will store the HTTP Operation in the predefined attribute named operation. General | Adopter Spec | Modes] eis General Channa Selection REST Resources REST Opeation| Operation Deteminatin|Resut HTTP Header Enor Handling ‘Operation atrbte Source opetion) Volue Source HTTP Opention 5) We like to pass through the content type of the response. Switch to tab Result HTTP Header. Create a new HTTP Result Header element. Select Message Attribute as Value Source, and maintain Content-Type for both the Message Attribute and the Header Name. General |Adapter-Spectic| Moduls| enti General | Channel Selection REST Resources| REST Operation Operation Determination Result HTTP Hesder| Error Handling HITP Result Header Value Source: Message Attribute zi Message atnbute” Content-Type Defout ue Header Neme* Content-Type ‘Save the channel, and select Activate from the context menu G3 PlEporer eo @e8Ag > SyoternZH4 ‘ype iterter GB Enya concur receiver a Enyacerp sender vB ep © PessThrough REST Sender TBOCAICP| Se copy Sc nein ( FileServer Sei Rat: Gunn TB INT2e2 EX Check Consistency TS INT2@2_EX (D_Vercon Hitory 3 INTe62. x CG irate sc DeleteReceiver Channel for Calling the Token Service Next, we will create a new receiver channel of type REST. Navigate to the receiver communication ‘component, and select New Channel from the context menu, 8S Pleplorer 12 |BB Enema. = SoAS > SystemZH¢ Concur & Integration Flows ¥ B Sytems G Concur ca x Delete Bee co Authorizations Be Ga Cea Sl New Receiver Agitement [Sco EP NewSender Agreement Ba Ba [3 Co @ Version History Export Show Cache Status In the upcoming dialog, enter a channel name, here TokenService_REST_Receiver, and click on Finish. New Channa o x Create a channel Enter mame and sect» system forthe ne channel Chana Name” [tener RESTReccned id Communion Componer| Concur = Paty [ Description Gamal On the General tab, select adapter type REST, and direction Receiver.Stns te | ckisnmsineereale ba ord ‘Sa anagtetedn pe . LSS rete pani (Se BTS Bowe Switch to tab General below tab Adapter-Specific. You may have to maintain a proxy depending on your network policies General REST UR REST Operation | Dats Format] Option Rules] Response Daterminaton| HTTP Headers Evor Handing] Pry use Pry Prony Hose Boy Prony Pr co Prony Uremame Prony Paewort soneen Cent CericateAutentetion ony act when using HTTPS) Tue cient conetes ‘Switch to tab REST URL. We need to maintain the target URL pointing to the Concur service and the HTTP. header for the actual call. For this, we need to define a set of placeholders, here called pattern elements, based on the dynamic attributes that we have set in the REST sender channel. For calling the token service, the target URL, the authorization, and the consumer key needs to be set. The content type however is empty, and hence must not be set here. For each of the dynamic attributes, create a new pattern element. For the target URL, select Adapter Specific Attribute as Value Source, maintain the Pattern Element Name as listed in the table below, and select the pre-defined Attribute REST Service (service). For the rest of the pattem elements, select Adapter Specific Attribute as Value Source, maintain the Pattern Element Name as listed in the table below, select Custom Attribute as Adapter Specific Attribute, and maintain the Attribute Name as listed in the table below. Pattern element name Dynamic attribute type Dynamic attribute name var_targetURL Pre-delivered var_targetAuthorization Custom ‘var_consumerKey ‘Custom REST Service (service) attr_largetAuthorization attr_consumerkeyDefine the URL Paltem as {var_targetURL}. During runtime, the placeholder will be replaced by the actual value, General Adopter Speci Modules| deters ‘General| REST URL | REST Operation] Data Format| Operation Rules Rezponse Determination] HTTP Header Enor Henaing Warning: Pacameeriing HTTP Host Pot is a sect ik ee SAP Note 2174651) URL Patter" ‘Rar targetUR) Follow Server Redirects on HTTP GET calls Pater Vrable Replacement Value Source Adopter pectic Atibute ¥ Pate Element Name sarge AdeperSpecticAtibute” FEST Service (erie) 7 Pattem Voiable Replacement Value Source ‘Adapter Specific tribute ¥ Patten Element Name var targethuthortion Adapter Specie tute Custom attibute Z setribute Name" ae fargethutorzaton Pate Variable Replacement Value Source Adopter Specie Atibite ¥ Pate Element Name var consmerkey Adapter Specie Atbute™ Custom Attibute a stout Name ar consmeney ‘Switch to REST Operation. We need to set the operation of the Concur service call. As Value Source select, Adapter Specific Attribute, and REST Operation (operation) as attribute. Since we simply pass through the operation, we define an identical mapping between the operation attribute and the HTTP operationGener Adapter Speic| Modules identifiers Genel REST URL REST Operation| Data Format] Operon Res] Response Detemination| HTTP Headers ror Handing] HTTP Operation Source Vale Source: Adapter Speci tibte =| Adapter Spctic tibute” FEST Operation (partion) a GET Opetion pression Go: = POST Opeation Espresso Got > PUT Oper Epresion Go: our presion 60 arte ‘Aston Operation Mapping ‘Switch to tab Data Format. Select JSON for both the request format and the response format, General Adapter-Speciic| Medles| dete General REST URL [REST Operation [Ost Format | Opestion Rules] Response Ostemination| HTTP Header | or Handling] Request Format (Disp Operation frm Message outer element (Character Set Name” ues (Coceonve Mt Payload To SON Response Format for Synchronous Messages) DateFormat Ison z irre Hanae z comet ‘Switch to tab HTTP Headers, and define the HTTP header elements using the placeholders defined before as listed in table below. HTTP header element name Value pattern “Authorization ‘(var_targetAuthorization} X-ConsumerKey {var_consumerkey}General| Adapter-Specific| Modules| Identifiers) Genera [REST URL | REST Operation | Data Format | Operation Rules | Response Determination HTTP Headers jor Hendiing| Additional HTTP Headers Header Nome Volue Pattem Authorization {var targetAutherization) X-ConsumerKey {var_consumesKey) ‘Save the channel, and select Activate from the context menu iP Pleplocer Systeme ype iter tot GB checkConeltionBeM » & Concur BHP Receiver © Tokensenvice REST Receiver Z]Concu ¥ Delete 8 Cone pe GB Concu 8 Copy 5 conc [AES uN (3 conal Reve 7 Conc Check Consistency CS concy @ Version History = Genet Open Channel Monitoring [Cond Show Cache StatusReceiver Channel for Exchanging Business Data Next, we will create a new receiver channel of type REST for exchanging the messages containing the actual business data. You can either copy the beforehand created channel, and make slight modifications or create the new channel from scratch. In the following, we create the channel from scratch. Navigate to the receiver ‘communication component, and select New Channel from the context menu, 1S PlEpiorer SptemzH ‘ype ier tex CheckConelationBM © Cane (BCH Delete Be Be Mthorzatons 7 =a OC New Rébeiver Agreement gece SC New Sender Agreement Se eon Be Sc @ Version History TSC Show Cache Status SS In the upcoming dialog, enter a channel name, here PassThrough_REST_Raceiver, and click on Finish. New Chane ao x Create a channel mera name and select 2 system forthe new channel ‘Channel Name* [PassTiwough REST Recewer i ‘Communication Component” | Concur Browse. Pay. Desciption: er Fish Cenceh ‘On the General tab, select adapter type REST, and direction Receiver.(Bom a PassThough REST Recower om . ances Remap [armas —) CES] ‘Switch to tab General below tab Adapter-Specific. You may have to maintain a proxy depending on your network policies. General Adapter Speci) Module iene Genera REST UL REST Operation | Data Format| Option Rule| Response Dterminaton| HTTP Headers Eror Ha Pry se Pray Provy Por” oo Provy Uremame Prony Passwort ra Cent CereteAutentstion ony active when using HTTPS) (Due cere Cemeter ‘Switch to tab REST URL. We need to maintain the target URL pointing to the Concur service and the HTTP. header for the actual call. For this, we need to define a set of placeholders, here called pattern elements, based on the dynamic attributes that we have set in the REST sender channel. For exchanging business data, the target URL, the authorization, and the content type needs to be set, The consumer key however is empty, and hence must not be set here. For each of the dynamic attributes, create a new pattem element. For the target URL, select Adapter Specific Attribute as Value Source, maintain the Pattern Element Name as listed in the table below, and select the pre-defined Attribute REST Service (service). For the rest of the pattern elements, select Adapter Specific Attribute as Value Source, maintain the Pattern Element Name as listed in the table below, select Custom Attribute as Adapter Specific Attribute, and maintain the Attribute Name as listed in the table below. Pattern element name Dynamic attribute type Dynamic attribute name var_targetURL Pre-delivered REST Service (service) var_targetAuthorization Custom attr_largetAuthorization ‘var_contentType ‘Custom attr_contentTypeDefine the URL Paltem as {var_targetURL}. During runtime, the placeholder will be replaced by the actual value, {General Adapter Specifc| Modules| Identifies General REST URL | REST Operation| Data Formet| Operation Rules] Response Determinstion| HTTP Headers| Error Handling Warning: Parameterisng HTTP Host or Portis security ik (see SAP Note: 2174651) URL Patter var targetU RL) EZ Folin Server Redirects on HTTP GET calls Patter Vanable Replacement Value Source: Adapter Speci Atibute z Pattern Element Name* var tagetURL Adapter SpecticAtibute* EST Service (service) z Pater Vale Replacement Value Source: Adapter Specific Atribute y Pater Element Narne* var togetiuthorztion Adapter Specific Attribute” Custom Attribute z Atuibute Name* att targetauthorzation Pater Vale Replacement Value Source: Adapter SpecticAtibute z Pattern Element Narne* var contentType Adapter Specie Atibute* Custom Attribute Ez Attribute Name* att contentype ‘Switch to REST Operation. We need to set the operation of the Concur service call. As Value Source select, ‘Adapter Specific Attribute, and REST Operation (operation) as attribute. Since we simply pass through the ‘operation, we define an identical mapping between the operation attribute and the HTTP operation,General apter Specti| Modules| enti ‘General REST URL REST Operation] Data Frmat| Operation ules Response Dtermination| HTTP Heades|Eor Handling HTTP Operation Source veSeion “Ape Spec tte 4 Ape Spc Rte [EST Open (operon) ¥ GET Opersion Expresion (Gob (or OST Operation Epresion (lb: [Post PUT Operation Espen (lb (pur DELETE Operation Expresion (lb (bare Switch to tab Data Format. Select JSON for both the request format and the response format. ene] Adapter Speci] Medes lentes ‘General | REST URL REST Operation | Data Fermat| Operation Rules Response Detemination| HTTP Headers | Er Handing Request Format Data Format 150N 7 [Dsrip Operation rom Message outer element) Choracter Set Name urs conve 2 Payoad To SON Response Format for Synchronous Mestages) Data Fumat Isow ¥ Character Se TTP Header 2 convert xia ‘Switch to tab HTTP Headers, and define the HTTP header elements using the placeholders defined before as listed in table below. HTTP header element name Value pattern ‘Authorization ‘(var_targetAuthorization} Content-Type {var_contentType}General [Adopter Specic [Modes Mente Generel REST URL REST Operation [Dots Format Operation Rules [Response Determination HTTP Headers] Err Handing Adsiional ITP Headers Header Name Volue Patern| Authorization (var_targethuthorization) Content-Type (var_contentType) ‘Save the channel, and select Activate from the context menu. SptemzHe type iter tet [ CheckconelationBPM 5 > & Concur STP Receiver © hassThvough REST Receiver SSS 5 Copy & Conc 3 Concu [3 conc 7 Reve CS concay Check Consistency [3 Concur (3) Version History 3 Concut CB Cones Pete [3 Concue & Concur ConcurReceiver Channel for the Ping Check When checking the connection in SAP ERP, a ping towards the Concur system is carried out. For the ping, only the target URL is filled, the rest of the http header attributes are empty. So, we will create a dedicated receiver channel for the ping. You can either copy the beforehand created channel, and make slight modifications or create the new channel from scratch. Create a new receiver channel Ping_REST_Receiver of adapter type REST. The settings of the channel are the same like before except for the REST URL and HTTP Headers settings. ‘On tab REST URL, define the URL Pattern as (var_targetURL). For the target URL, select Adapter Specific Atribule as Value Source, maintain the Pattern Eloment Name 28 var_targetURL, and select the pre-defined Attribute REST Service (service) ‘GS ConcurtipensentegratonWithFinancils |} Ping REST Receiver £3 Ping_REST_Receiver General |Adopter-Specific| Module) Identifiers General [REST URL | REST Operation | Data Format | Operation Rules| Response Determination| HTTP Headers | Error Handling Warning: Paremeterzing HTTP Host or Portis a secu ik (ee SAP Note: 2174651) Unt Pate” ‘ecerget) Follow Server Redirects on HTTP GET calls Pattern Variable Replacement Vet Souce ‘Adapter pectic Atibte z Patter Element Name verge Adapter Specific itt” EST Senice eve) yl ‘Switch to tab HTTP Headers. Ensure that no hitp headers are maintained, REST Receiver WE ConcurExpenseintegrationWithFinancials Pin: Ping_REST_Receiver General Adopter-Spectfic| Modules identifies General REST URL |REST Operation | Oata Format | Operation Rules [Response Determination HTTP Heades| Err Hendling Adltional HTTP Headers Header Name Value Pattern Save the channel, and select Activate from the context menu,Integration Flow Create a new point-to-point integration Flow with REST adapter channels on both sender and receiver side. As sender and receiver interfaces, simply maintain dummy interfaces. To group your configuration objects, you can use folders. Assuming that you have created a folder already, select the same, and select New Integration Flow from the context menu. 22 Pl Explorer 12 [BS Enterprise... = Ol @EBRG > SystemZHe ‘ype filter text ¥ @ Integration Flows a & AIM © CloualntegrationScenario @ Concur XC © Concur Prep & Concur SOL © ConcurPassThrouah © CPOrde Authorizations © Gatewa & intaez, Corr @ INT262, 2 Rename & INT26, Delete INT, Move. & InT266, @ MFT ale @ Nagel Deploy © Orders1 @ prowy €2 Check Deployment © Success'C$ New Folder (@ UNI EXt S In the upcoming dislog, select the Point-to-Point Channel pattern, maintain an integration flow name, and click on Finish,New integaton Flow a x Create an intogration low ick Mesto configu the endpins now Folder Patt [Cone enTiough Categories Select a pate to createanintegation lw Enter IetegetionPafterns = ser Defined Tempter, Point-to-Point Channel "= Pain to-Peine Channel ensures that messages ae sent to cnereceher oy. ecient List ‘Areiient st lo: youto spe one or more recipients This mesage outer amines Suggested Use Xpath /BuyerParty/BuyeriD = "AA Create Xpath containing whitespaces Cobo oK CancelDefine the condition for the other interfaces accordingly. The condition for the token service should be es follows: ContextObject.service = "https://wmyw.concursolutions.com/net2/oauth2/accesstoken.ashx” ‘The condition for exchanging the business data (interface allobjects) should be as follows: ContextObject service l= “https://www concursolutions.com/net2/oauth2/accesstoken.ashx" AND ContextObject.service != “https://www-concursolutions.com") Note, for lattor we use the Not Equal To and AND operators, Note: The conditions shown here were defined based on the URLs for the US data center. Depending on which data center your Concur account is assigned to, the URLs may differ, and you need to adapt the conditions accordingly. ‘Optionally, you can maintain condition names which will then also be displayed in the Integration Flow model. When done, the integration flow should look as follows, mem 5 Sin bine pate eas iy ‘Save the integration flow, and select Activate from the context menu in the navigation pane.3S PlEsplorer Enterprise Sevice Browser = 0 CEES # Systemznt type ier tet Integration Flows eam © ClovcintegrationScenaio © Concur exc © Concur Prep © Concur SOL © ConcusPassThvough 29 ConcurfspensentearationWithFinancials © CPordersTo! —Acsign Alert Rules © Gateway Authorizations & Ine Exc @ INT2E2 SOL FE Deploy @ INT265 SOL View Deployment Log © INTROS = Check Deployment (© Inrz6e, sou Mr Check Consistency © Nagel BPM. <2 Revert © OrdersToinv © PROInevar proms | Yesion Histon (Once activated, select Deploy from the context menu. WPlbolowe 2 BS EmeriseSevice Bowser =O eoeAas Sytem type iter tet GB Integration Flows eam & CloualntegrationScenario (@ Concur EXC © Concur Prep © Concur sol ¥ © ConcurPassThrough [22 ConcurBspencentearationithFinancias B CPordersTolnvoice Assign Alert Rules © Gotewey Authorizations @ wreeexc & INTE. SOL @ INTR65 SOL View Deployilen Log wires Bc Check Deployment @& INT266 SOL said ‘The deployment of the integration flow will be triggered. Once done, in the deployment log the integration flow should have the status Finished.TBPaeeee | osemen Ayden sues Potions © comle 5 Sener Poses} Hany (Probes a Tebaai Ieee AOE RT]Determine Integration Flow End Point URL ‘When we run the Concur Integration setup in SAP ERP, we need to maintain the end point URL. Switch to the SAP Process Integration Runtime perspective. Select the Integration Flow from the navigation pane, and select Show Runtime Properties from the context menu, TE PiRuntime por 12 affeueMapping = Et Cone PSS Sytem ‘ypefitertot v Bat a a) © Clousintegrtionscenaio & Concur 6X & Concur Prep © Coneu sot & © ConcuPutTicigh ~ $5 Concepcion Gram Past Open Mage Montong creer ene © Gateray Enza pec Open Channel Monitoring INES assign Alert es emp ee © nee so — eur El Check Deployment (© NogeL 6PM In the upcoming dialog, the HTTP as well as the HTTPS end points are displayed. Based on our channel ‘configuration, the end point should be defined as follows: httpu/chost>:/RESTAdapter/concur/passthrough/allobjects! https:l/:/RESTAdapter/concur/passthrough/allobjects! Runtime Properties aq x Funtime Properties untie properties for integration Mow ConcurbpensentegaionWithFinancial Runtime Properties Propery Message Menitring ‘Channel Mentoring pees nnora/esoures/an.com/tc=lm=isam=uieman Channel Monitoring a n= tam=yinmain Channel Mentoring t/a oc eee eet Endpoint REST t/a pND/RESTAdepter/concui/pestvoughllobject/ Endpoint AEST tp: lpn HN RESTAdapter/concut/psethvough/lbjects/ ® Ee GesOption 2: Configuration via Integration Builder ‘Open the Process Integration tools page, and select the link Integration Builder below Integration Directory. «>calo eins OP int Gn fo oe fom Di a eens a g see In the upcoming logon screen, enter your user credentials and click on Log on. This opens the Integration Builder client. o Sender Chane! In the Integration Builder, navigate to your sender system, select the node Communication Channel below the same, and select New from the context menu.[Gi configustion: Integration Bur » Object Navigation Tools Environment Help Oeielm IIe) e ‘Ml leleta)ey CondttonaistartReeewer ConditonalStatSender c Enya_concut receiver Enya_erp_sender ERP » Xa) Exct_JcP EXCA_Bystem In the upcoming dialog, enter a communication channel name, and click on Create. ooo Seon 7 Pan Samana ‘Communcaton Component” (ERP + cotaboratin Agresenat ‘Communcston Channel” [PassTivouyh REST Sede] SB Sender agrerert Deserpton EBpreconersareement ae Scena gates Conuratin ita Fier ~ coniguraion onets Serecoher Rue Value appa cour > smastation contain certo Aynenrwe aratcer & Change st [ema] Cenar Below tab Parameters, select adapter type REST, and select the Sender radio button, ‘On tab General, select Quality of Service Best Effort. Select JSON as data format for both the input message format (request) and the output message format (response).at Commaniston chan tue InProcees ipo Language (Engin (ODT) ‘Communcssencranne! _PateTWOuR REST. Sener Paty [ Cermmunisson compunert (ERB Descraton i MEER versie, nose aap Type est me sapconnsysem swreiss750 lo © Sencer_O Recehar TTaneperroecol” TTP 2 essageProeal? “REST a aapercraa Cervaladopier Engine 5 put essoe farmat ‘ta Fomat aH ‘cnaract et [HTP Conte TypeHeaser Dicoments x0. out o sorace ‘cut rsortee jaestenen utr essgo Format 5 & ‘ta Format ew Dime operaten tom meas icone it Pa si message Chars st ‘Switch to tab Channel Selection. Select check box Specify Endpoint, and maintain endpoint as Jeoncurfpassthroughvallobjects. ‘Channa Selection A speety Endpoint Endpot* Jeonourpassivoughaenees Cintow pute access eo autnoreation equ) [Bitumtt s50n etement Blunts xeats cement Blum tT? operaton ‘Switch to tab REST Resources. Select Custom Pattern as URL Pattern, and set the same as /. In order to store the HTTP header elements of the incoming callin the XI message header, define the following dynamic attributes. For keeping the target URL, select from the drop down the pre-defined REST Service (service) entry. For the rest ofthe attributes, select Custom Attribute as Dynamic Atribute, maintain the Custom Attribute Name as listed in the table below, solect HTTP Header Variable as Value Source, and maintain the HTTP Header Element as listed in table below. Furthermore, it s important that all attributes are {defined as optional, because depending on whether the Concur token service is called or actual businessdata is exchanged, not ell HTTP header elements are passed to SAP Process Orchestration. So, for each dynamic attribute select the Optional check box. Note: for the target URL we need to use a pre-defined dynamic attribute since the attribute is later used in @ routing condition, this is not supported out of the box for custom attributes. Type Dynamic attribute name HTTP header element Pre-defined REST Service (service) targatURL Custom attr_targetAuthorization targetAuthorization Custom atir_contentType content-ype Custom attr_consumerkey X-ConsumerKey URL Pattern URLPattern [Custom Patiem Pattom* — [7 X1 Dynamic Attribute Dynamic Atibute REST Seniee (eenice) Value Source HTTP Header Variable HTTP HeaderElement® targelURL Optional X1 Dynamic attbute Dynamic tribute Custom atrioute — ‘Custom Attribute Name * stt_targetauthorzation Value Source HTTP Header Variable HTTP Header Element* —targetAuthorzation © Optional X1 Dynamic tribute Dynamic Atribute Custom Attioute — ‘Custom Attibute Name [st_contentType value Source HTTP Header Variable HTTP Header Element contentype A optional 21 Dynamic attribute Dynamic Attribute Custom atvioute ‘Custom Attribute Name * stt_consumerkey Value Source HTTP Header Variable HTTP HeaderElement” xConsumerkey © OptionalWe like to store the HTTP Operation of the incoming callin the XI message header. Switch to tab REST Operation, and select HTTP Operation as Value Source. This will store the HTTP Operation in the predefined attribute named operation. Operation Attribute Source (operation) Value Source HTTP Operation ‘We like to pass through the content type of the response. Switch to tab Result HTTP Header. Create a new HTTP Result Header element. Select Message Attribute as Value Source, and maintain Content-Type for both the Message Attribute and the Header Nam HTTP Result Header Value Source (Message Atrbute Message tribute’ Content-Type DefautValue Heagername* (Content-Type HTTP Rosuit Header ‘Value Source = Unused, ‘Save the channel, and select Activate from the context menu in the navigation pane. ~ ERP "Ye Communication Channel ‘open mo ‘Gopy object. camanie Dette. cup {assign Contiguraton Scenarios. ove to Folder Winere-Used UistReceiver Channel for Calling the Token Service Navigale to your receiver system, select the nade Communication Channel below the same, and select New from the context menu. > @ Business Component AB. Resetver ABLSender ABC PSI Ageney 110 Agency 221 BPM_Demno CheekCarrlatonAEX CheekCorlatonBPM Concur > Communion Channa » cone 2 AER > Coneur_EXC_Clout » Concur EXC’ Contenténricher In the upcoming dialog, enter a communication channel name, here TokenService_REST_Receiver, and click on Create, create Object x a a @ Business Component el cao ‘Communication Component* (Concur coerce eee] ‘Communicaton Channel” _{TokenSenice_REST_Recelver 8) Sender Agreement Desenption| Ei ecener Agreement ‘Adio Scenario 3 Integrated Coniguaton ‘ais Folder ~ Coniguration Objects ‘Ba Recener Rule ‘el Value Wapping Group ~ ministration I Comgurstion Scena By Alert Rule Grotser change List crenahy [caret Below tab Parameters, select adapter type REST, and select the Receiver radio button, ‘On tab General, you may have to maintain a proxy depending on your network policies.Ean Communteation Channel staus ave Displayes Language Erg CCommuniaton Channel TokenSenice_REST_Recier any Descrston | Adapter Tipe? REST mp sap corabarystem [ssp easis7.50 O sender @ Recsher TansperProwco!’ (HTTP IuessagePrtocal est Acagter Engine * (Cena Aasster Engine Prov 7 Use Proxy ProsHest™ pro PronPot* 080 Proxy User Name ‘hen Certieate Auhenication (On Active When Using HTTPS) use cient cones (1 Use Basic Athenteston ‘Switch to tab REST URL. We need to maintain the target URL pointing to the Concur service and the HTTP. header for the actual call, For this, we need to define a set of placeholders, here called pattern elements, based on the dynamic attributes that we have set in the REST sender channel. For calling the token service, the target URL, the authorization, and the consumer key needs to be set. The content type however is empty, and hence must not be set here. For each of the dynamic attributes, create @ rnew pattern element. For the target URL, select Adapter Specific Attribute as Value Source, maintain the Pattern Element Name as listed in the table below, and select the pre-defined Attribute REST Service (ervice). For the rest of the pattem elements, select Adapter Specific Attribute as Value Source, maintain the Pattern Element Name as listed in the table below, select Custom Attribute as Adapter Specitic Attribute, ‘and maintain the Altribute Name as listed in the table below. Pattern element name Dynamic attribute type Dynamic attribute name var targetURL Pre-delvered REST Service (service) var_targetAuthorization Custom attr_targetAuthorization var_consumerKey ‘Custom attr_consumerkeyJRL Warning: Parameterizing HTTP Host or Portis a security risk (see S URL Pattem* {fvar_targetURL) Follow Server Redirects on HTTP GET calls Pattern Variable Replacement Value Source ‘Adapter-Specifc attribute Pattern ElementName* —var_targetURL Adapter-Speciic Atribute * REST Service (service) Pattern Variable Replacement Value Source ‘Adapter-Specific Attribute Pattern ElementName* var_targetAuthorization Adapler-Specific Attibute* Custom attribute ‘Atibute Name" ‘at_targetAuthorization Pattern Variable Replacement Value Source ‘Adapter-Specife attribute Pattern ElementName* —_var_consumerKey Adapter-Speciic Atribute * Custom attribute Attribute Name * ‘att_consumerkey Pattern Variable Replacement Value Source — Unused — ‘Switch to REST Operation. We need to set the operation of the Concur service call. As Value Source select Adapter Specific Attribute, and REST Operation (operation) as attribute, Since we simply pass through the ‘operation, we define an identical mapping between the operation attribute and the HTTP operation.HITP operation Source Value Source [adaptor Speci Atibute Adapter Spectic Atnbute* REST Operation (operation) ET Operation Expression Olob) [GET POST Operation Expression (Glob) [POST PUT Operation Expression Glob) [PUT DELETE Operation Expression (Glob) [DELETE ‘Switch to tab Data Format. Select JSON for both the request format and the response format. Request Format Data Format Jason 1 8irip Operation from Message (Cuter Element) Character SetNName* [UTF-8 Ci Convertx9¢L Payload to JSON Response Format flor Synchronous Messages) ata Format Gson Character Set HTTP Header Di convert to 0, ‘Switch to tab HTTP Headers, and define the HTTP header elements using the placeholders defined before as listed in table below. HTTP header element name Value pattern “Authorization ‘(var_targetAuthorization} X-ConsumerKey {var_consumerKey}‘Adnional HITP Headers + 58 communicaton Component¥vthout ary > B) Business System > @ Business Component ~ Yq Communication Channel a come A tow ConcurzExcly 20Py Object c Cores ci Concut_SOL_A Assign Configuration Scenarios. Concur_SOL_C Concut_soLF Move to Folder. ‘Concur_SOL_€_Whe oe ConditinnalstarReceiver Channel for Exchanging Business Data Navigale to your receiver system, select the nade Communication Channel below the same, and select New from the context menu. > @ Business Component AB. Resetver ABLSender ABC PSI Agency_110 Agency.221 BPM_Demno CheekCarrlatonAEX CheekCorlatonBPM Concur > Communion Channa » cone 2 AER > Coneur_EXC_Clout » Concur EXC’ Contenténricher In the upcoming dialog, enter @ communication channel name, and click on Create. eat Oct x - Ce: Ya Communication Channel Rrew arty Communcaton Component® Con Pe eweven soreret Ccommuncaton Chamel* PassTiough REST Recetas CE) Sener agree Descrpion 7 En Recon arement aa Scere Inert Cotasaton da Foor ~ conuration jects Ba Recor Ruse afl Value mapping Group = Aceinistration [Bcontguraton Scenario ‘4 Aer Rule Fotoer % Change List Below tab Parameters, select adapter type REST, and select the Receiver radio button ‘On tab General, you may have to maintain a proxy depending on your network policies.Et Communication Charmol ts, nose5s Dipled Language [Engioh 8) Communication Chane! PabeThough REST Recah? any CCommurieaon Component (Const Deserpton aap Te esr te asan.commisem sess 750 a © sensor @ Recover NeseageProvea” REST ape Engin (Conant Eine 5 use Poy ProyHest" [pony ProyPed —_sueo Proy ter Name hon certs Auer ton Ont Ave Wan Using HTS) (D)use crt ceteates ane atbore ston (Clues Basic aanerteaton ‘Switch to tab REST URL. We need to maintain the target URL pointing to the Concur service and the HTTP. header for the actual call, For this, we need to define a set of placeholders, here called pattern elements, based on the dynamic attributes that we have set in the REST sender channel. For exchanging business data, the target URL the authorization, and the content type needs to be set. The consumer key however is emply, and hence must not be set here. For each ofthe dynamic attributes, create ‘a new pattem element, For the target URL, select Adapter Specific Attribute as Value Source, maintain the Patter Element Name as listed in the table below, and select the pre-defined Attribute REST Service (cervice). For the rest of the pattem elements, select Adapter Specific Attribute as Value Source, maintain the Pattern Element Name as listed in the tabie below, select Custom Attribute as Adapter Specitic Attribute, ‘and maintain the Atribute Name as listed in the table below. Pattern element name Dynamic attribute type Dynamic attribute name var targatURL Pre-delvered REST Service (sanvice) var_targetAuthorization Custom attr_targetAuthorization var_contentType Custom atte_contentType Define the URL Patter as {var_targetURL}. During runtime, the placeholder will be replaced by the actual value,Warning: Parameterizing HTTP Host or Portis a security risk (set URL Pattem* [jvar_targetURL) Follow Server Redirects on HTTP GET calls Pattern Variable Replacement Value Source [Adapter-Specifc Attribute Patten ElementName* —ar_targetURL Adapter-Specific Atribule* REST Service (service) Pattern Variable Replacement Value Source [Adapter-Specifc Attribute Pattern Element Name* —ar_targetAuthorization Adapter-Specific Atribute* (Custom attribute Atribute Name * ‘att_targetAuthorization Pattern Variable Replacement Value Source [Adapter Specific Attribute Patten ElementName* —jvar_contentType Adapter-Specific Atribute* Custom Afribute Attribute Name * ‘at_contentType Pattern Variable Replacement Value Source Unused ‘Switch to REST Operation. We need to set the operation of the Concur service call. As Value Source select Adapter Specific Attribute, and REST Operation (operation) as attribute. Since we simply pass through the ‘operation, we define an identical mapping between the operation attribute and the HTTP operation.HITP operation Source Value Source [adaptor Speci Atibute Adapter Spectic Atnbute* REST Operation (operation) ET Operation Expression Olob) [GET POST Operation Expression (Glob) [POST PUT Operation Expression Glob) [PUT DELETE Operation Expression (Glob) [DELETE ‘Switch to tab Data Format. Select JSON for both the request format and the response format. Request Format Data Format Jason 1 8irip Operation from Message (Cuter Element) Character SetNName* [UTF-8 Ci Convertx9¢L Payload to JSON Response Format flor Synchronous Messages) ata Format Gson Character Set HTTP Header Di convert to 0, ‘Switch to tab HTTP Headers, and define the HTTP header elements using the placeholders defined before as listed in table below. HTTP header element name Value pattern “Authorization ‘(var_targetAuthorization} Content-Type {var_contentType}‘Acidtional HTTP Header aa Hoar Name Value Paton ‘Authorization {ar_targetauthorzation) Content-Tpe ‘var_contentType} ‘Save the channel, and select Activate from the context menu in the navigation pane. Sy ere llal ey | > GO Party + communist Component vamnoutPary > i Business System -y @ Business Component © concur ~~ Yq, Communication Channel _ 2 Passtinoini REST Rabat REST-R New Taker] oven COU EES, copy object. Concur exCWC! Delete ‘Concur_EXC_Fi Assign Configuration Scenarios. eT ‘Move to Folder. Concur SOL_Ag Coneur_SOL_ci Where-Used List Concur SOL g¢ Beieet ChangsReceiver Channel for the Ping Check When checking the connection in SAP ERP, a ping towards the Concur system is carried out. For the ping, only the target URL is filled, the rest of the http header attributes are empty. So, we will create a dedicated receiver channel for the ping. You can either copy the beforehand created channel, and make slight modifications or create the new channel from scratch. Create a new receiver channel Ping_REST_Receiver of adapter type REST. The settings of the channel are the same like before except for the REST URL and HTTP Headers settings. ‘On tab REST URL, define the URL Pattern as (var_targetURL). For the target URL, select Adapter Specific Attribute as Value Source, maint a8 var_targetURL, and select the pre-defined Attribute REST Service (service). the Pattern Element Name Eat Communication Chama caw CommuneatonChomePiag_REST ROG ary Communeten componen SRE ee es Acer Type * nest tipssap commanasyatem O sender @ Receiver TransportProtocel (HTTP Message Protocol (REST canter Engine CeriralAdapier Engine ‘Warning: Parameterizing HITP Host of Port isa secur isk (208 SAP Mate: 2178651) URL Pate var_targetURL) llow Server Radiects on HTTP GET calls Pattern Variable Replacement value source [Raapter Specie ibe Patter ElementName* —var_targetURL Adapt SpectcAtibule* REST Serie ernce) ‘Switch to tab HTTP Headers. Ensure that no hitp headers are maintained. ‘addtional HITP Headers ‘Save the channel, and select Activate from the context menu.Integrated Configuration Object In the navigation pane, select the Integrated Configuration node, and select New from the context menu, > 9G Party > §® Communication Component Without Party > Ze Receiver Rule » 3 Sender Agresment > Gh Receiver Agreement » 5 Integrated Confauration » cto > @B Value Map Grouping! > & integration Frow" » AyAedule Maintain your sender system, and the sender interface and namespace, the click on Create. Create Objet x {> ntorated Contiguration @ Business Component %, commmunicaton Channel ~ CattaborationAgreernent ‘s8} Sender Agreement Pc ~ connguraton Objects ‘Ba Recever rule €8} Value Mapping Group ndmeistration i Coniguraton Seenaro Ayalon Fue aFoiser % change ust (i [ca] ‘On the Inbound Processing tab, maintain the sender communication channel. Select the beforehand created REST sender channel Ccommuniaton Paty CCommunicaton Component” [ERP ‘mtraco* aonjects Namespace * inp tence sap com sender Uses vitatRecener Deserption ado Seenato ror er‘tans [inProcess | Dieplayed Language [Engish O17) ‘Communication Party Communication Component ERP z| Irwrace ‘atobjedts Namespace [nepatconoursap com —S Racetver Communication Party ‘Communication Component Desiioton Cconiguraton fr itrtaceaobjects ‘Communicaton Channel ~ ‘Asap Type ‘Asapler Engine Sonware Corspanent Version of Senderiteace To Virus Stan (Use Global Coniguration 3) ‘Sehema Vaiation @ No Validation © Valsaton by adaster ‘Switch to tab Receiver, and maintain your receiver system, Laltow arbirary receiver (outbound processing by eceher agreements) ‘ype ofRecenar Determination @ standars O Esdended ‘Switch to tab Receiver Interfaces, and maintain your dummy interface name and namespace, here allobjects with namespace hitp://concur-sap.com.‘Add two further dummy interfaces, one for the token service, here tokenService with namespace http://concur.sap.com, and another for the ping, here ping with namespace http:/Iconcur.sap.com, ver oe [Communication Party ‘Commur Receiver interiaces (Sw) Li} 0 naan one atria Siar ae RE peraion Mapping Name = Namespace i Dr attobjects Cl- ntp:iconcursap.com irtoxensenice (Gir tptconcur sap.com Bir ping (Gietpstconcursap.com Furthermore, maintain routing rules. For the token service interface, maintain condition as follows: service = hitps:/}www. concursolutions.com/net2/oauth2/accesstoken.ashx Condition tor Previews senace = ins uw concursolubons commetZioaumdfaccesstoken ashi ze For the ping, maintain condition as follows: service = hitps:/iwww.concursolutions.com For the allobjects interface, maintain condition as follows: service # https:/iwmw.concursolutions.com/net2/oauth2/accesstoken.ashx AND service # https:www.concursolutions.comD Condition Editor x tS Lon Oparand ‘Op. RiphtOparana fence ‘tose concusalutons com Preview senice # htps sw concursolitons.comnetlvautnaaccesstoken ash AND sen hits awww concusclutons com Note: The conditions shown here were defined based on the URLs for the US data center. Depending on Which data center your Concur account is assigned to, the URLs may differ, and you need to adapt the conditions accordingly. ‘Once done, the Receiver Interfaces should look as follows. [=I] Cwsnancnertnine portage nee Seconds + sonora cm peewee rte cee). Spee Orhan ‘Switch to tab Outbound Processing, and maintain the receiver communication channels. Select the beforehand created REST receiver channels. For the token service interface, select the channel TokenService_REST_Receiver.Assoned Recon mteaces over cover narace Communion Paty Communion Comoonert Name amespace Concur snes mene sop com ‘con og Iapaconsep.com ‘Conigaion or terface tokenSence [icon sp com ‘Communication Channel” Toten REST Resear aster Te6 ame Era onal Engne Sore ConponertVrson ot Recher interace viv Sean Use iba Confusion Stora Vakdton @ tio Vakson © Valtaton by Al For the ping interface, select the channel Ping_REST_Recsiver. acer ioianornnace Commanaon Paty [conminaionamgonet Nae “Names corer stones ‘prorat ss0com ‘coneut tohenserice np aconcus38.com Conrguration or itertace pig | pstcancusap.com ‘communiaten Channel” (ing_REST Roce ‘cote Type ‘Adaoer Engine ‘otware Commponert Version orReceveeriace vue sean (Use Gioval Configuration ‘nema vaeston © Nova inti ap commana For the other interface, select the channel PassThrough_REST_Receiver.» GO Pary Gl » ® Communication Component Without Party a » SaReceierRule » 3) Sender Agreement » GhReceiver Agreement ‘y > integrated Configuration 717 LAccessTokenuery_Sync_Outoound | | *|* | ExpenseReporiGuery_Async_Outbound | | I Coneur_SOL_Setup | EmenseRepontGetit1_sync_( I Concur_SOL_Setup | ErenseReportauery_Sync_Ou| | Conditional6tartSender | ConditionalstartServieePO_(| New F) Open cuts ‘Copy Object. ctvesnine Delete cu. assign Configuration Scenarios. Display WSDL. Publish in SR, Move to Folder where-Used List UINTOR? Rot” RPA Ienenisoncunn Re uel ‘Concur rensewe ito eon 4p com ‘concur ‘png Iie eoncusap com Conrguration for terface abjets | tpiconcusep.com ‘Communtation Channel PPaseThrough REST Recever step Rest imp oapcompisyster ‘AsaterEngine Cea AaasterEngne Stare Component Version of Receiver intetace ‘nus S80 (Use Global aniguaton ehera Vaidaton @ NoValiation © Vaktaton by Adare ‘Save the Integrated Configuration object, and select Activate from the context menu in the navigation pane.Determine Integration Flow End Point URL ‘When we run the Concur Integration setup in SAP ERP, we need to maintain the end point URL. For a REST sender channel, the following rule apply: http(s):i/:/RESTAdapter// ‘The static part corresponds to the endpoint path that we maintained on tab Channel Selection, whereas the dynamic part is the pattem that we maintained on the REST Resources tab. Hence, based on our channel configuration, the end point should be defined as follows: httpu/:/RESTAdapter/concur/passthroughallobjects! https:l/chost>:/RESTAdapter/concur/passthrough/allobjects!Configuration enhancements for Credit Card Detokenization scer io ‘The credit card detokenization scenario behaves in some extend different compared to the rest of the ‘scenarios. For both, the token service call to request for a bearer token as well as the actual exchange of the credit card number, the path for exchanging business data can be used. So, there is no need to change the xpath conditions, however we need to enhance the receiver channel for exchanging business data. In the following the enhancements are shown for the integration flow only, the configuration using the Integration Directory is pretty much the same. ‘When checking the connection in transaction code CTE_SETUP, a dummy credit card number XXX is used ‘and hence the actual call results into a bad request with http status code 400. The response may look like below: {'timestamp":"2018-05-1 1111:07:42.046+0000","httpStatus’:"400 - Bad Request","errorMessage":"Bad Tequest [creditCardGUID] received." "errorld”:"BAD_REQUEST”, "path’:"idetokenizeriv/company/a83afcbd- 4d68-406a-a052-513bfb9cO8edicreditcard/XXX"} ‘The Concur add-on in the SAP ERP system can handle the http 400, however the REST adapter results into ‘a message processing error. So, we need to fetch the error to be able to pass the response to the SAP ERP. ‘system, This can be done via the error handling feature of the REST adapter. In the SAP Process Integration Designer perspective of the NWDS, open the channel PassThrough_REST_Receiver, and switch to tab Error Handling. Add a new result handler as follows: + As source choose JSON Expression + AS JSON Element maintain errorld + As Expression maintain BAD_REQUEST + Asaction choose Custom Result + As message content maintain {hitp_result}. The parameter http_result contains the response of the service call Geom] REST URL REST Operation eta omat Option Rates| Ronse Deter TTP Heads ror ding sous ISON reson . pen th AD ROU This will set the delivery state to successful (http 200), and returns the service call response, For the actual call to gather the credit card number, encoding of the url leads to an http 500 error. By default, the REST adapter encodes the whole url. So, we need fo switch off the encoding of the url. See SAP Note 2215187 - Options for URL encoding of query strings with PI REST adapter. In the PassThrough_REST_Receiver adapter witch to the Modules tab, and add a new parameter to the RESTAdapterBean as follows: + Parameter name: EncodeURL + Parameter value: falseCONCUR INTEGRATION SETUP AND MONITORING In the following we will sotup the integration between SAP System and Concur via the previously configured Integration Flow on SAP Process Orchestration. For detailed information about the Concur integration setup in SAP ERP, refer to the Concur Setup Guide at the SAP Service Marketplace, accessible from httpv//servies.sap.com + Products + Installation & Upgrade Guides + Cloud Solutions from SAP + SAP. Integration with Concur Solutions. Create Connection ‘Open the SAP ERP system, and start the Concur integration setup via transaction code CTE_SETUP. In the Concur integration setup, select Create Connection from the System menu. © sep Ede Goto Enyfonment system Heb °o )«S1@G@ SHHiDNCHOIAB OB ‘Greek connection ‘Star Concur System ‘ormuncaton Hontor Delete Connecton In the upcoming dialog, select Continue. A(On the next screen, select the radio button Middleware, and maintain an RFC destination name and description. The Concur Host wwww.concursolutions.com is preset. Maintain the SAP Process Orchestration host and port, and the path prefix of the REST service end point created before. To authenticate to the SAP Process Orchestration system, maintain user and password. Depending on your network policy you may hhave to maintain proxy settings. Then click on Continue. wn concurs. com <== Imes tAcapereonexnssvouh Tacs [sose0 | ‘On the next screen, maintain Consumer Key, Secret, and Concur Company ID of your Concur system. Then click on Continue.Sem & ee ‘On the next screen, maintain User and Password to authenticate to your Concur system. Then click on. Continue,GG conte) Se ceet ‘On the final screen, all settings are displayed. Click on Complete. This will create a new destination of type G (HTTP Connection to External Server). Furthermore, the overall configuration is used to gather an access token from the Concur token service,‘Now you're all set for the connection wth the following data Middleware RFC Destination: PL_ZH4 P Description: PLZHA : Concur Host: www.concursolutions.com 5 Middleware Host Sam tmp omy Pat Prefsc IRESTAdaptericoncur/passthroughiallobjects : Port 50300 E Proxy Host 3 Proxy Service . RFC User: demo : ‘SSL Client entity: $SL Client (Standard) . Defauit Language: English E (Concur Company 1D: Concur User [email protected] ‘Open the message monitor of SAP Process Orchestration, and switch to tab PI Messages, For demo purposes | have switched on logging of the synchronous communication. Furthermore, | have defined a user defined message search fitar based on the operation attribute (not shown above). So, two new entries should be displayed, the request and the response of the Concur token service call. The operation is GET. ‘Message Monitor: Monitor Messages a ——— = —ax = yaar IBYIn the message details of the request, the dynamic attributes are displayed. You can see that the Concur token service is called. To authenticate to the token service, user credentials for basic authentication and your consumer key are provided. The content type is not required and hence empty. In the message details of the response, the payload contains the access token as well as the refresh token, ‘Message kaltor: Versions peers | tren Pm oe at‘Check Connection In the Concur integration setup, select Check Connection from the System menu. © Setup Edt Goto Enyonment System Heb ° ~)«S1@ee 55 es Setting Up the Integration with Concur [Floccumentaton Integration Actwties [)Downiaad Gude [System ___][Eroioyee [cost Center__]ntemal oder __[francal posing [vendor] ‘eate connecton (Employee | Cost Center tema Ord, |FeancalPo,. Vendor ge Comnecten a 8 a a a a | at a a a a aw ‘Stare Cone Sytem ey ‘Sormmunicaton Montor Delete Connection ‘A.couple of checks such as ping and actual transactions were carried out. The result of the checks are displayed in the upcoming logs. Display logs @ @ Serecncatinfomaton veo a + [i200 0k >>> Speer avabityn aneactn SUSE + W200 OK >>> Pg + 1B 200 0K >>> Unt /apfva.0fcammon/sttens) : ‘OK >>> URE /apstsvompanies/219831/stategories/Q16%20Cos%200bjecU/sa (OK >>> URE /apii /corpanes/219631/transactontypes/expense/transacons (OK >>> URE /apf¥/eompanes/219831/trasactontypesexpense/transaccons/acknow (OK >>> URE /ap/fi/coroanes/219631/trasactontypes/emense/tansacons/postng (Ok >>> URE /apexDense/s/v.0) (OK >>> URE /apfuse/v.0/Fomelés ‘Ok >>> URE /aiexpense/expensereprtv1./report/Forms/PHT_VENDOR, ‘Open the message monitor of SAP Process Orchestration, and switch to tab PI Messages, In the message monitor you should see 9 new messages, ie., for each message a request and a response, so 18 entries in total. So, during the checks actual messages are exchangad between SAP System and Concur via SAP Process Orchestration.TRANSACTIONS. In the following we will show: + The export of master data from SAP ERP to Concur via SAP Process Orchestration. For demo, Purposes, we will just show the Employee Export (XML format) and Cost Center export (JSON format) + The import of Concur documents from Concur to SAP Fl system (FI Posting) Employee Master Data Export In the Concur integration wizard, set up the export of the Employee data, For detailed information about the setup of the export, refer to the Concur Setup Guide. Once you have run through the configuration wizard, you can trigger the export. For demo purposes we have chosen a manual export. To export employee data, ‘select Manual Export from the Employee menu. © setup Edt Goto Environment System Heb o v« eee Setting Up the Integration with Concur Hlpocumentation integration Activities [Download Guide (Sinem Jeroen eter ier ee renona eso) Sy. RFCDest change Export Employee | Cost Center intemal Ord,|Fnancel Po... Vendor 2 RQA3_St Specify Field Mapping s a 3 AA Test a s a a a Sem | Refine Defaut Locales 5 tvorvg |_BAdl Implementations Remove Export ‘On the next screen, maintain the selection criteria, and then select the Execute button.© progam Edt Goto system Help Qo *)«<8ie@es Export Employees to Concur GS & GX oowseucue © search eb Selection Critera Person 1D Personnel Number {susmfo Employment Status commany code Personnel rea Employee group The log indicates thet the export was successful © Log Edt Goto System Hep o vJ« eee Anioe Display logs & @ SK Technical information [Hep ‘Overview Nu > Gi Empbyee: export finshed with 1 successful objects. 2 + B® 49025774 1 ‘Open the message monitor of SAP Process Orchestration, and switch to tab PI Messages, In the message monitor, you should see a new message. The operation is POST.In the message details of the request, the dynamic attributes are displayed. You can see that the Concur user service is called. To authenticate to the Concur service, OAuth is used. The content type is application/xml. The consumer key is not required and hence empty. ——<—| In the message details of the response, you can see that the content type is set based on the response from Concur, :., equals application/xmMessage Editor: Versions seen | tere I to When switching to the Payload tab, you can see that the payload is XML. Here, the content type is given as applicationyjson. This is due to the JSON format setting of the REST adapter channel. However, the content type will be actually overwritten by the correct value application/xml of the dynamic attribute, Message Header | Mesoge Aiden cht - (Gserel (Ua) at mente spetenpen:chave-UTEt See 288 Chee “eran et rn hp encore oman ume hy 20 Val Scans tangs acre ‘Setecarcheewar urease ncotsse bccn ee -UssDean» ann Enea HST cca “Feces cetacean SceSS atsene”stsO uber SC mee Cost Center Export In the Concur integration wizard, set up the export of Cost Center data. For detailed information about the selup ofthe export, refer to the Concur Setup Guide. Once you have run through the configuration wizard, you can trigger the export, For demo purposes we have chosen a manual export. To export cost center data, Select Manual Export from the Cost Center menu.G Setup Edt Goto Enyronment System Heb ° ~)«81@aee 5n\ee Setting Up the Integration with Concur Documentation Integration Actwties [%)Download Guide: Geien —Jescine [eek |main|) '9r..|R5C Destination Grange Export, Center Intemal Ord, Financial Po epee ctirokmensters | @ @ 2 ATE = B a a + ee Seo (On the next screen, maintain the selection criteria, and then select the Execute button [ progam Est Goto System Heb °o *)«Beeeis A608 Export Cost Centers to Concur R tS selecoon Controtng area Comeany Code Bushes Aves cose Center [Peneonso2eic system Recenng System e) pLawe zm} Test Mode — sis ais The log indicates that the export was succesful© Log Edt Goto System Hep o *}<«81@G@lsHK! HoiAnios ‘Open the message monitor of SAP Process Orchestration, and switch to tab PI Messages. In the message ‘monitor, you should see a new message. The operation is PUT. In the message details of the request, the dynamic attributes are displayed. You can see that OAuth is used. ‘The content type is application/json. The consumer key is not required and hence empty.cs = a In the message details of the response, you can see that the content type is JSON. oi oo [eeImporting Concur Documents (FI Posting) Now that we have exported employee and cost center, we are able to perform Fi posting. In Concur, we create and submit an expense report. Once approved, the expense report is ready to be imported from Concur into SAP FI system. For the import to work, the customizing of Fl posting should be set up. For detailed information about the import/posting of Concur documents, refer to the Concur Setup Guide, ‘Open Concur travel and expense, and create a new Expense Report, Now let's submit the report and get it approved. Trip to Pl-Land Fics Faire’) omoowem ones nampa rete 2 om a ‘cme ese Bete peseounoee Fi cower f= S] [eave a race conn [e= g Let’s remember the report id (EDDADDCBAFSE4028BAFB) of our report accessible from the report header. Report header for: Trip to Pl-Land a Petey Resor Nae Report 2) Pretoria ESOADDAFSELCOON enor Key apart Ota Ledger cs ever? a z per Cure repro Sis Comment fro Not Sues ages sya omoary Code os obeet Tipe FJiconcuvrase concurrien|~] J roontoosine cusce |v] fi ccicon: corer z ost Ont 0 og unes org unt [Jrerrocncat tr potorane] =] Once the report has been submitted and approved, we jump back to SAP Fl system and import the expense report using our integration wizard. Inthe Concur Integration Setup, select Concur Documents from the Financial Posing menuSetting Up the Integration with Concur [HDocumentation Integration Activties [@)Download Guide [system __.J[Emoiyee [cost center__ intemal order_.[[FnancalPostng _.|\Vendor_ 4) Sy... RFC Destination 1D. Employee | Cost — change Import 2 RQA3_Standard_Test a 8 TE syboke account 3 AA Test a 8 @ ten So ‘Tax Jursdiction Codes Seal ew BAdI Implementations BBAdI Implementations Invoice 8 pLtest_enyaz a oie El Remove Import 10 PLNZS ev In Concur Documents, select Feedback Loop + Step-By-Step + Import Documents from Queue, Concur Documents ‘T)Documentaton system Key © | paws (mLzH9) Document Type View Docursnts i ¥]—Bocument 1D (@___star seeccon__} a Sib ‘Bloeanee | =a Rey. Doc Name 1D Document St Send Confirmation ee Besend » Select the Single Document radio button, and enter the Concur report ID.= Imp System Key | Pr_zxa (Pr_znay Document Type Expense Report . ‘AI Documents @)sngle Document Document 1D JEODADDCBAFSEAO286ARB | 4x) ‘Once done, you get a message that the report has been successfully imported Display logs X_ © Earechnicatinformaion [F] Help [Overview ¥ I Expense Report: import completed with 1 successful objects. Moss ‘Checking the message monitor in SAP Process Orchestration, we see that there are two new successfully processed messages, the request and the response. When selecting the request message, we see in the message log that the operation is GET. Furthermore, you can see that the target URL contains the Concur report ID,(im a fata ae se = = Now let's take a closer look at the response message. In the payload you find the reference to the Concur report ID (E0DADDCBAFSE4028BAFB) of the expense report that we imported via the integration wizard, oePoot, Maseite, 0%, ete | Seti 8 (sat es [| (Saran ea) pi lela aac soe Forat (TEE —— re. (SFR [e terms (0 nt cote open nan 6 ann Seca Se pep ae a eine mya pr ns aa oe ae ee ee eae. Downloading the payload, will show you the whole JSON file saccarenet 1 \temptajes\ts(\eplopests\"s\ "4908885", NeployeePizetiane\\ "Bids \serployeetasetane\*s\haschs\", \remployeei\ "el, eng Code\*\"ERCLT3SO\", se\",\tenpoyentep ner {Soe\"s\ "Eta", Pempoyestepinse Cosa sne 2, \replogeeoegseiValae\"s\*oncar sncegetion\" \employesdepieie2Vaoe\": Tenplace DE(t,\PenployedegtricSVaue\*:\ "Cort Cencee\",\eployeeteyiaic2code\*2\ "DEO, \werptoyecustentSCoce\ nit, Peployeetunton6ode\ "inst, \Pnpiopeecestnt7Cede\"s\"9054868\7, \serptoyeecaszenziVatue\":\" \rreporta\ \rcocatagprovesiaune\*:123.009000 \szeportey\ "983, eployeetarcencyigtacede\"s\P0R\",\twersinta\*=\*6\,\taneCeantrCode\*2\"2E \szeporsCurcnaSCoce\\*08\",\"eepartantont Cote anuhl,\*eeprvInerDetineaate*2\"2017-0in29200:00:09.0000\", \szeporsRaenaterocessingtate\"2\*201701-29T08:0:4).7572\,\eporeCuatoncode\"ensl,\tepertCurtadcade\*et, \reevionntes\"e\\y (snp bmacaoe\"s\*257-00-24708 9040, 0072. \aeporeCurnt Wades \MS8HEE3 \sseporscuronss?atse\stat,\eeperscmeoniSVaiee\ "ECC Gro DE\",\"reporecuat anise ini, \szeporscursns Tents \sna1,\enporscvconieVae\ ins), \"eepracuat oni alae nul, \eporssurtoniVasca\ "eR, \weeporcorgieisicece\" goats 25\",\reportOrgnstZtede\*s\"RoN\",\*eporsorghase3coae\ "VCO" \wzeportorgiescAcece\"\Pat-FI00\,\epeetOrgdrscoae\" a, \reperrOrgnse#ceee\ "oul, "eporcOrgoestaVabee\" \sceecer sncepratien\,\zepercorgcaczVauue\"s\"ogrcey Tenpace TE, \"reparcoepinstsvaie\*s\ "Cor: Oaster\, \szeportorgescavalue\\*xingnten vt center fer DEDI\,\*eeporvorgotarSValue\ "rai, \*eporsorgDai alee \werpensetacry\": 1 sertage? 1 ml, 1), \enzzyvenderCoge\ oni, \enezyCuntenValue\ "eal, \enteqoustenzValue\ "eR, \tncsyCunrcesalue\ "Rahwww.sap.com/eontactsap ‘Stone paveton may tryed ants oem am nse er mtn EPS or nS aN me aii : tue da cae pun sae cnn ese