![]() ![]() Second SOAP Receiver channel is required to perform Product Master Data post call. Login SOAP receiver channel and dummy interface. The Login SOAP receiver channel should be linked with a receiver agreement to make a call to SFDC system. Operation mapping test can be performed to see how the SOAP envelope is added:įor the SOAP Look up, one SOAP Receiver Login Channel is required.Here set the target url as that of login request url and set the SOAP Action as login. Import the java mapping as Imported ArchiveĬreate Operation Mapping – Use JAVA mapping subsequent to the IDoc to Product message mapping as shown below: Login request Call using SOAP Look Up featureīuild SOAP Envelope around target message with the session id Import Product Master WSDL provided by Salesforce as External DefinitionĬreate Message Mapping with IDoc and Product Master external definition PI as middleware to send login request to SFDC, receive session ID and the preform required data update/insert call to SFDC system. Otherwise, there can be other response messages depending upon the error encountered like false or INVALID_SESSION_ID. If the data is posted successfully to SFDC CRM, the response received is true. Response received from SFDC contains, server URL and session ID, which is required to embed in SOAP envelope while making the product master data call to SFDC.ģ.Product Master Call: create a project in SOAP UI, call the Product Master Upsert request,set the Session ID, check target URL and execute.Ĥ. First Create a project in SOAP UI, Call the login request, Set Login Credentials, Check target URL and execute it.Ģ. ![]() WSDL files can either be downloaded from SFDC site with valid credentials or client should provide you. Here we will see Product Master Data post. Let us first see how this entire process works using SOAP UI :įirst step is to have 2 wsdl files, login wsdl and other data wsdl. In this blog, the focus is on SFDC outbound integration. SFDC Outbound integration: In case of data is to be posted to SFDC from ECC, the integration is based on two way communication using Java Mapping, soap look up. SFDC Inbound integration: In case of data needs to send from SFDC to ECC, the integration is similar to any other SOAP to ECC interface. Multiple data integration was implemented:Product Master, Invoices, Vendor Master, Customer Master, Vendor Contract etc. SAP PI is used as a Middleware to perform the ECC and SFDC integration. In our project requirement client has decided to use SFDC CRM solution. Integration of ECC and SFDC CRM required because it offers high reliability, high performance, SFDC CRM is preferred as it is less expensive, supports easy upgrades, better Service Delivery and it is easier to customize. Cloud computing, is used to describe a variety of different types of computing concepts that involve a large number of computers connected through Internet. SFDC is an on-demand CRM tool, based on Cloud Computing Concept. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |