Discover Top Posts Tagged with #saplo

SAP LO as a Strategic Driver for Modern Logistics Performance

SAP LO covers a wide range of logistics processes across planning, procurement, inventory and distribution, and the LO Info-Cube introduces this scope directly in its opening resources. The product connects supply chain operations with real-time analytics, financial transparency and efficient warehouse and transport processes to help organizations shape an agile and resilient logistics foundation. Its integration with SAP S/4HANA supports smarter forecasting, synchronized demand and supply and intuitive SAP Fiori access for operational teams. Leaders benefit from clearer insights into inventory, reduced cycle times and more accurate decision-making. The Info-Cube enhances this understanding through high-value tutorials, demos and industry knowledge from around the world. With the SAP LO Info-Cube, S4-Experts brings together the knowledge of the global SAP community and makes it accessible worldwide through translation.

https://s4-experts.com/sap-le-lo-logistikberatungen-consultants/

#sap #logistics #SAPLO #SAP logistics

Web APIs & Net::HTTP

Introduction

Net::HTTP is a Ruby library we can turn to in order to send and receive HTTP requests and responses. To begin with, let's take a look at the API documentation.

Net::HTTP provides a rich library which can be used to build HTTP user-agents.

Net::HTTP is designed to work closely with URI. URI::HTTP#host, URI::HTTP#port and URI::HTTP#request_uri are designed to work with Net::HTTP.

For our purposes, a user agent means a client application or service that runs on our behalf. We can use Net::HTTP in order to communicate with a web API if by some tragedy a wrapper is not available.

To begin with, we should take note of the fact that Net::HTTP is designed to work with the URI module. In a nutshell, the URI module provides us with a simple way of parsing a URI string.

For example, when fed a URI / URL string, an URI object will expose a number of methods which can, among others, return the host, port, domain and relative path.

Communicating with a Web API

For a practical application of Net::HTTP, we will be interacting with the Saplo API. When browsing the documentation on their page, 3 things become apparent :

The API uses the RPC model. This basically means that we will be communicating exclusively with POST requests which will contain a method call embedded in the body.

There is no Ruby API wrapper or interface

The company is based in Sweden. Not that there's anything wrong with that :)

Our goal will be to get an authentication token from the API using the "auth.accesstoken" method. Let's begin by gathering the necessary libraries.

<![CDATA[// <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // <![CDATA[ // ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]]]><![CDATA[><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]]]><![CDATA[><![CDATA[><![CDATA[> // ]]]]]]><![CDATA[><![CDATA[> // ]]]]><![CDATA[>]]>

Note that we have also included 'net/https'. The Saplo API makes use of both HTTP and HTTPS, and we will need the latter for the authentication process.

Line 4 : Here we have created our URI object

Line 5 : Set the port variable to the HTTPS standard of 443.

Line 6 : We have also created an instance of Net::HTTP - note that only the host and port are required at this stage.

Lines 7 through 10 : These are optional parameters that need to be set for HTTPS requests.

Line 11 : Instantiates a new Post request object, with a header indicating the content type, which in this case is JSON.

Now that our connection parameters are set, we can move ahead by formatting the body and send the request.

Line 2 : This is the call to the set_connection_parameters method which we looked at above

Line 3 : Here we set the request body. Note that the entire hash is converted to json. The instance variables @api_key and @secret_key refer to API keys which are declared elsewhere.

Line 4 : We are initiating the request using the "request" method of our Net::HTTP object

Line 5 : The response is parsed in order to retrieve the returned access token

Note that the response is returned as a string, which is subsequently parsed using the JSON module.

Et voilà, we have our authentication token in 8 "simple" steps!

There are shortcut methods available from Net::HTTP, and thankfully most common APIs already have well documented Ruby wrappers. However, I hope the above will be useful should you ever find yourself in the position to have to craft HTTP responses manually.

References & Resources :

Net::HTTP Cheat Sheet

Net::HTTPSession Class Documentation

#ruby #net::http #json #saplo #api wrapper #api

Is my privacy worth someone's death?

In the wake of the shooting in Tuscon, there has been much discussion regarding the shooter's various social media profiles. People are analyzing all the different things the shooter said and wrote through various mediums; YouTube and Facebook being the most quoted and analyzed. Without delving into what his dark and seemingly incoherent blogs/profiles/videos said, the question is being asked, "Could we have seen this coming?" and "Should we have seen this coming?".

This week, while in San Francisco, I spent some time with a great guy and new friend, Frederik. He is from Sweden and is co-founder of the company www.Saplo.com. Their product can scrape huge amounts of text, tag the important words in that text, and analyze the sentiment of the text. One commercial application of this product is brand sentiment analysis. For example, Coca Cola could pay Saplo money to analyze all the text on the entire world wide web and they would report back the overall sentiment of the world towards Coca Cola. By the way, they could do this in minutes.

It got me to thinking, could we use these types of enterprise tools to analyze user profiles' sentiments? Could we possibly monitor the content distributed by potential killers and mass murderers, and stop them before they commit a crime? Would it be possible to sort of let a computer use "pre-cognition" to determine criminal intent? Could the shooting in Tuscon have been avoided?

I think think the real question is should we do these things, not could we. Where would the line be drawn? Would everyone's online activity need to be monitored? How would we delineate between feelings and actual intent? How violating would a world like I am describing be? Think about that....

But, a much harder question: is my privacy worth someone else's death?

#Tuscon #shooting #pre-cognition #saplo #privacy