Skip to main content

Building the Foundation of the PO System: Architecture and some terminologies

1. Loosely Coupled and Tightly Coupled Services:

  • Loosely Coupled Services: These services interact with each other with minimal dependencies. Changes in one service don't significantly impact others. Pros include flexibility, easier updates, and better scalability. A common example in PO is when a shipping service communicates with an inventory service. Changes in the inventory service won't necessarily disrupt shipping.

  • Tightly Coupled Services: These services are interdependent, so changes in one service can affect others. While they might provide faster communication, they can be less flexible and harder to maintain. For example, tightly coupling an order processing service with a payment service means any change in payment could ripple to order processing.



2. SOA - Service-Oriented Architecture:

SOA is an architectural approach where everything is treated as a service, encapsulating specific functionality.

  • Service Orchestration Example (Banking Transaction): Consider a banking transaction like transferring money from one account to another. Service orchestration involves coordinating multiple services to achieve this. The process might involve verifying account balances, updating transaction records, and sending notifications. Each of these steps is a service, and orchestrating them ensures the entire transaction occurs seamlessly.

  • Benefits: Flexibility, reusability, and agility. Services can be combined to create various processes without rebuilding everything from scratch.

  • Cons: Complexity can increase if not properly managed. Service versions, dependencies, and communication need careful attention.

3. ESB - Enterprise Service Bus:

An ESB is a central hub that connects and manages different services. In the context of PO, it's the backbone that enables integration.

  • Integration Principles:
    • Orchestration: ESB can coordinate service interactions to achieve complex business processes.
    • Transformation: It can translate data between different formats.
    • Transportation: ESB routes messages between services.
    • Security: It enforces security measures.
    • Governance: It manages service access and policies.
    • Business Process Management: ESB supports designing and executing business processes.

4. ESA - Enterprise Service Architecture:

ESA combines the principles of an enterprise's operations with SOA. It's about aligning IT architecture with business goals.

In summary, SAP Process Orchestration (PO) fits into these concepts:

  • Loose Coupling: PO encourages loose coupling of services, making it easier to maintain and adapt.
  • SOA: PO embraces the SOA approach, where functionalities are encapsulated as services, offering flexibility and reusability.
  • ESB: PO includes an ESB component, facilitating seamless integration and service communication.
  • ESA: PO aligns with ESA by incorporating service architecture to drive business processes effectively.

Remember, these concepts are the foundation of modern enterprise architecture, including SAP Process Orchestration, allowing businesses to achieve efficiency and agility in their operations.

Different Types of Message Flow Diagrams in PO:

  • Intranet Scenario - A2A (Application-to-Application) Integration: In an intranet environment, different applications within an organization communicate with each other.

    • Example: An HR system needs to update the payroll system whenever new employee data is added. The HR system triggers a message to the payroll system in real-time.
  • Internet Scenario - B2B (Business-to-Business) Integration: In a B2B scenario, businesses communicate with external partners over the internet.

    • Example: A retail company needs to send purchase orders to its suppliers. The retail company's order management system communicates with the supplier's order processing system via the internet.

Internet Firewall with Respect to PO: An internet firewall acts as a barrier between your internal network and the external internet. It monitors and controls incoming and outgoing network traffic.

  • Example: Imagine you have a PO system that communicates with external partners for order processing. The firewall ensures that only authorized messages are allowed to enter or leave your network, protecting your internal systems from unauthorized access.

Synchronous (Sync) and Asynchronous (Async) Communication:

  • Synchronous (Sync) Communication: Think of it like a phone call. When you make a phone call, you expect an immediate response from the other person. You wait on the line until you get an answer.

    • In PO: Synchronous communication is like sending a request to a service and waiting for the response before proceeding. For example, sending a request to calculate the sum of two numbers and waiting for the result.
  • Asynchronous (Async) Communication: Picture sending a text message. You send the message and go about your tasks. The response might not be immediate, but you don't have to wait for it actively.

    • In PO: Asynchronous communication involves sending a request and not waiting for an immediate response. You might check later for the response. For example, sending a message to a service to process an order and then moving on to other tasks.

Electronic Data Interchange (EDI) with SAP Process Orchestration:

Evolution of EDI: Electronic Data Interchange (EDI) has come a long way in revolutionizing business communication. Originally, it involved structured data exchange through proprietary formats, making it challenging for businesses to collaborate seamlessly. Over time, EDI has evolved to embrace standardized formats and protocols, making it a crucial part of modern supply chain and business integration.

Example: Order to Cash Process and EDI Evolution: Consider the "Order to Cash" process, where a customer places an order, and the business fulfills it. In the past, businesses exchanged paper documents, causing delays and errors. As technology advanced, businesses started using proprietary EDI formats to transmit data electronically. However, different formats hindered interoperability. Now, with standardized formats like ANSI X12 and EDIFACT, EDI has transformed into a streamlined process, allowing systems to seamlessly communicate across organizations.

Types of EDI:

  1. ANSI X12: Commonly used in North America, ANSI X12 defines standards for various industries such as retail, healthcare, and manufacturing.
  2. EDIFACT: Widely used internationally, EDIFACT is prevalent in Europe and other regions, and it's often used for global trade.

Benefits of EDI:

  • Efficiency: Automation reduces manual data entry and processing time.
  • Accuracy: Fewer errors due to manual data input.
  • Speed: Messages are transmitted in near real-time, enhancing business agility.
  • Cost Savings: Reduced paper-based processes and faster transactions.
  • Visibility: Better tracking of transactions and data exchange.
  • Compliance: Adhering to industry standards and regulations.

EDI to XML Format: EDI messages can be transformed into XML format for easier processing. XML is more flexible and readable, allowing for seamless integration with modern systems. SAP Process Orchestration can handle this conversion, enabling systems to communicate using both EDI and XML formats.

Electronic Data Interchange (EDI) has evolved from paper-based processes to streamlined, standardized electronic communication. With SAP Process Orchestration, businesses can integrate EDI seamlessly, ensuring efficient and accurate data exchange across different systems and partners.

Partner Interface Process (PIP) in SAP Process Orchestration:

Understanding PIP: Partner Interface Process (PIP) is a concept within SAP Process Orchestration that defines a standardized framework for exchanging business data between trading partners. It involves a set of standardized processes and document structures to ensure smooth communication between businesses.

Benefits of PIP vs. EDI: Global Standards:

  • Global Standards: PIP uses standardized processes and document structures, ensuring consistency in communication across global partners. This minimizes errors and improves interoperability, especially in complex supply chain scenarios.

RosettaNet and PIP:

  • RosettaNet Community: RosettaNet is a consortium of companies that collaborate to develop and implement e-business process standards. It aims to streamline business processes and data exchanges.
  • PIP Members and History: The RosettaNet community consists of members from various industries. They work together to create PIPs that define how specific business processes should be structured and executed.

PIP Structure:

  • PIP Represents: Each PIP represents a specific business process, such as Purchase Order (PIP3A4). PIPs are composed of messages, documents, and actions that define the process steps and data exchanges.
  • Process to PIP Combo: A process in SAP Process Orchestration is associated with a specific PIP. For instance, a "Purchase Order" process might use PIP3A4 to facilitate the exchange of purchase order data.

Understanding PIP Flow and Dependency:

  • Flow: A PIP flow represents the sequence of steps and interactions between trading partners during a specific business process.
  • Dependency: PIPs may have dependencies on other PIPs, especially when processes involve multiple steps or require data from different sources.

PIP Organization: Cluster, Sub-classification:

  • PIP Organization Cluster 0-7: PIPs are organized into clusters (0 to 7), each focusing on specific business processes and industries.
  • Sub-Classification: Within a cluster, PIPs are further classified into sub-classifications like Cluster, Segment, and Business Process.
Cluster NumberFocus
Cluster 0Internal Use Only
Cluster 1High-Tech Manufacturing and Distributing
Cluster 2Automotive and Aerospace Manufacturing
Cluster 3Computers, Peripherals, and Electronics
Cluster 4Telecommunications Equipment Manufacturing
Cluster 5Pharmaceutical and Chemical Manufacturing
Cluster 6Textiles and Apparel Manufacturing
Cluster 7General Manufacturing and Distributing

Example: E-Commerce Order Fulfillment Process:

Imagine you're running an e-commerce business, and you want to optimize your order fulfillment process using the concepts of Cluster, Segment, and Business Process.

1. Cluster:

  • A Cluster represents a broad category or area of business operations. It encompasses a range of related processes within a specific domain.
  • In our example, let's consider the Cluster "Order Fulfillment," which includes everything related to processing and shipping customer orders.

2. Segment:

  • Within a Cluster, a Segment narrows down the focus to a specific aspect or subset of the broader category.
  • In our example, the Segment could be "Shipping and Delivery," which deals specifically with the processes involved in getting products to customers after they've placed an order.

3. Business Process:

  • A Business Process further narrows down the focus to specific steps, activities, or tasks within a Segment.
  • For instance, within the "Shipping and Delivery" Segment, you could have the Business Process "Packaging and Labeling." This process involves preparing products for shipment, ensuring they are packaged securely and labeled accurately.

Putting It All Together:

  • Cluster: "Order Fulfillment"

    • Encompasses all activities related to processing customer orders, preparing products, and delivering them to customers.
  • Segment: "Shipping and Delivery"

    • Within the "Order Fulfillment" Cluster, this Segment focuses solely on the processes required to ship and deliver products to customers.
  • Business Process: "Packaging and Labeling"

    • Within the "Shipping and Delivery" Segment, this Business Process involves specific steps such as selecting appropriate packaging materials, packing products securely, and labeling packages with shipping information.

Why This Hierarchy Matters:

  • This hierarchical structure ensures clarity and organization in your business operations.
  • By breaking down processes into Clusters, Segments, and Business Processes, you can manage and optimize each aspect separately.
  • It also facilitates collaboration, as teams can focus on specific areas of expertise.

Benefits of Using Cluster, Segment, and Business Process:

  • Structured Approach: Hierarchical organization provides a structured way to manage complex business operations.
  • Focused Efforts: Teams can concentrate on specific aspects, leading to better specialization and efficiency.
  • Easy Navigation: The hierarchy helps employees quickly understand where specific processes fit within the larger context.
  • Effective Communication: It aids in communication by providing a common language to discuss and manage processes.

Example of PIP Sub-Classification:

  • Cluster PIP: Cluster PIP4A1 involves the "Planning & Forecasting" business area. It covers various processes related to demand planning, inventory optimization, etc.
  • Segment PIP: Segment PIP4A1.1 specifies a subset of the Cluster PIP, focusing on a specific aspect of demand planning.
  • Business Process PIP: Business Process PIP4A1.1.1 further narrows down the focus, dealing with specific steps and data in demand planning.

Benefits of RosettaNet and Similarities to EDI:

  • Similar to EDI, RosettaNet offers standardized communication, reducing errors and improving efficiency.
  • RosettaNet's focus on specific industries enables tailored solutions for their unique requirements.

RNIF Protocol:

  • RNIF: RosettaNet Implementation Framework (RNIF) is a protocol used to transmit RosettaNet messages securely and reliably between partners.
  • RNIF vs. SOAP: While SOAP is a protocol for general web services, RNIF is tailored to RosettaNet's specific requirements, ensuring proper message handling and authentication.

PIP vs. EDI: Similarities and Differences:

AspectPIPEDI
StandardizationStandardized processes and dataStandardized data formats
InteroperabilityEnhances partner collaborationEnhances partner collaboration
ComplexityCan be complex due to specificityCan be complex due to mapping
Industry FocusSpecific to RosettaNet communityIndustry-specific and generic
Process EfficiencyTailored to specific processesGeneralized process approach

Trading Partner, Trading Profile, PIP Version vs. RNIF Version:

  • Trading Partner: A business entity with which you exchange data and collaborate.
  • Trading Profile: A configuration that defines how you communicate with a specific trading partner.
  • PIP Version vs. RNIF Version: PIP version refers to the specific release of a PIP, while RNIF version indicates the RosettaNet Implementation Framework version used for message transmission.

Comments

  1. https://www.betterup.com/blog/visualization

    ReplyDelete
  2. Welcome to APTRON's Beginner's Guide to Azure! If you're new to cloud computing or Microsoft Azure, you're in the right place. Azure is one of the leading cloud platforms in the world, offering a wide range of services and solutions for businesses and individuals.

    ReplyDelete

Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set