Skip to Content

Architecture

In my SAP Discovery System for enterprise SOA – Part 1 I gave a general overview of what is “SAP Discovery System for enterprise SOA” and provided high level overview of sample procurement scenario built in the system. In this article I would like to dive a little bit into the architecture and describe the role of different NetWeaver Components in the scenario, Web services that were developed and development tools that were used.

Business Task image image image image image image

Dev Tools

NW Dev Studio (Adobe perspective)

Visual Composer

Web Dynpro (Java)

Web Dynpro (Java)

Web Dynpro (Java)

NW Dev Studio (Adobe perspective)

Web Services

Sales Order Service

—–
  • Supplier Service
  • Quote Service
  • Suppliers Services
  • Purchase Order Service
  • SupplierS Services
  • Purchase Order Service
  • Goods Received Service

Components

  • SAP Portal (optional)
  • SAP NW Application Server
  • SAP XI
  • ECC 5.0
  • SAP Portal
  • BW
  • ECC 5.0
  • SAP Portal
  • SAP NW Application Server
  • SAP MDM
  • SAP XI
  • ECC 5.0
  • Non SAP system (SQL)
  • SAP Portal
  • SAP NW Application Server
  • SAP XI
  • ECC 5.0
  • SAP Portal
  • SAP NW Application Server
  • SAP XI
  • ECC 5.0
  • SAP Portal (optional)
  • SAP NW Application Server
  • SAP XI
  • ECC 5.0

Description

At this step , sales person creating a Sales Order. Sales Person fills a form, which when submitted, will update the SAP ECC system.

The form is an Adobe Form (PDF file), built into NWDS. This form passes its data through a Web Service to a service deployed on the SAP Web Application Server (WAS). This J2EE service communicates with SAP XI using a Web Service through a Web Service proxy. SAP XI submits the Sales Order to the SAP ECC system.

At this step user would like to analyse the existing stock .

The analytics screen was developed with Visual Composer, all the details in this screen retrieved from BW info cubes at the runtime. Additional operation should be executes in order to retrieve all the details from ERP system into BW, in our case this operation is done at the design time but you can also schedule this process to be executed every number of minutes in order to see updated details in your analytic application inside the portal.

This scenario gets a product quote and purchases a product.

The Web Dynpro application communicates via Web Service with J2EE applications that retrieve data from MDM, or calls other Web Services (Supplier WS and XI WS). So first of all , list of all the suppliers who can supply requested product retrieved from MDM , the when we want to get quotes from some suppliers in the list – it is done by retrieving external IDs of the suppliers from MDM sending request to BPM which splits the requests and sending it to the relevant suppliers. The lst step in this process is when quotes received in the portal (through BPM and SAP Web Application server)

In this step user would like to submit the Purchase Order/s after the quotes from different suppliers have been already reviewd.

By entering the quantity of product to order and pressing “Place order” button, the create PO sub-process starts. It will call the createPO service that will then call the XI WS. This createPO step has a Web Dynpro to display the PO numbers, a CreatePO service on the WAS and a WS proxy to a XI Web Service. Five Supplier Web Services are deployed on WAS to mimic a supplier service that gives an online quote.

Purxhase Orders confirmations should be received after placing the POs. We want to be sure that our suppliers got the Pos.

We get the PO number for each supplier displayed in the Web Dynpro UI. Once the create Purchase Order service is invoked, it returns the Purchase Order numbers PO number means a real confirmation numbers from the back end systems.

In the scenario, the user fills in a form to declare that he received the products that he has ordered.

The ECC system must be updated. The users (in the warehouse) filling “Goods Received ” Adobe form, by pressing the “Submit” button , the form passes its data by Web Service to the goodsReceived service on the WAS. This service passes the data to a service using XI, which then updates the ECC system.

You can find more information in the documentation that was published on SDN just before one week ago.

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

    1. Oleg Figlin Post author
      Hi

      The process was coded.

      BPM was also used to do some kind of decision workflow capability that were needed. Such is the case with the integration with the external suppliers.

      Best Regards.
      Oleg.

      (0) 
  1. sudeep adhikari
    Hi Oleg,

    Thanks for sharing the information.
    Now I am working as a consultant for a vendor in Japan and we are in a step to introduce SAP Discovery system to our prospective clients.

    I have collected as much information about the features and composition of Discovery system. But I couldnot find information about what will happen after the customer will agree to buy the Discovery system.
    Regarding the maintainence and liscencing, what will be the best way to follow?

    looking forward to hearing from you,

    Thanks in advance,

    sudeep

    (0) 
    1. Oleg Figlin Post author
      Hi

      Once the customers agrees to buy , he should order it through out HW Partners, it is supplied by HP or Fujitsu today.
      Once the server is delivered to the customer , they should refer to it as a complete SAP environment and general licensing applies to it.

      Regards.
      Oleg

      (0) 
  2. chandra shekar dasari
    Dear Oleg,
              Thanks for bringing such highly informative blogs.
    I am new to ESA,gone through the articles & blogs in sdn corner.

    I have once query based on first step”create sales order” from SAP XI point of view.

    “”This J2EE service communicates with SAP XI using a Web Service through a Web Service proxy. SAP XI submits the Sales Order to the SAP ECC system””

    I didnt get the point called “Web Service proxy”.

    Regards
    chandra

    (0) 

Leave a Reply