Day: January 24, 2018

President Donald Trump signed into law a two-year delay on the 40 percent excise tax on high-value health care plans—the so-called Cadillac tax—as part of the measure to restore funding to the federal government. Both political parties supported the provision to postpone the Cadillac tax from taking effect until 2022, instead of in 2020—as did the Society for Human Resource Management. President Donald Trump signed into law a two-year delay on the 40 percent excise tax on high-value health care plans—the so-called Cadillac tax—as part of the measure to restore funding to the federal government. Employer advocates praised the move but also called on Congress to permanently repeal the levy. https://goo.gl/M29D4r #GlobalHR #HRTech

Earlier this week I wrote SAP Inside Tracks by Country.  Little did I know it is far more interesting to look at it by city.  I also missed an Inside Track in my previous post: Berlin – apologies to Oliver Kohl – he also streamed Inside Track Berlin, parts of which I watched online live.

First, from the previous post, I used the “interoperability” from Discovery to Designer and learned this:

So I couldn’t execute locally in Designer, something I am so used to.

So I uploaded to the BI Platform

Because I wanted to see it on SAP BusinessObjects Mobile, I assign a mobile category on the BI Platform

Above shows how it looks like on the “Fiori-fied” BI Platform

Here is how Europe looked

On Mobile iOS:

I really like the crisp views of Lumira Designer 2.1 on the SAP BusinessObjects Mobile software; thanks to Vivek Das and team.

Inside Track by City – Lumira Desktop 1.31.9

Now I struggled to find Bogota, Colombia with Lumira but fortunately it suggested Bogota, DC

Above shows Lumira Inside Track by City (including Berlin) using 1.31.9

Lumira Discovery 2.1

What I liked about Lumira Discovery is the marker feature on the maps.  You can see that SAP Inside Tracks in Eastern Australia are covered well.

Customized Maps Lumira 2.1

A nice new feature is using customized baseline maps in Lumira Discovery 2.1

Setting:

Once you create a geographic hierarchy on cities Lumira also looks at regions/sub regions.  Above is using a Stamen baseline map.  You can see that New South Wales had 3 SAP Inside Tracks last year (in Sydney)

It’s a geography lesson for me, learning that Hannover is in Lower Saxony

Because Lumira couldn’t find Ballerup on the map, I changed it to the closest city, Copenhagen.

How does it compare to previous years?

See this video by year:

In 2016 Australia had 3, in 2017 they had 6

Here’s the raw data

Country
2015
2016
2017

Brazil
3
6
5

Australia
2
3
6

Germany
4
3
6

India
2
3
2

Mexico
1
2
1

Turkey

2
2

United States
2
2
2

Belgium

1
1

Canada

1
1

Jamaica
1
1

Japan
1
1
2

Netherlands
1
1
1

Peru

1

Poland
1
1
1

Switzerland

1
1

United Kingdom
1
1

Denmark

2

Argentina

1

Colombia

1

France

1

Spain

1

Italy
1

Malaysia
1

View by Country by year:

I don’t like this line graph; I find it hard to read

Reading Stephanie Evergreen’s visualization book, she is not a fan of area charts, but I think it depicts the data better than the line chart.

I resorted to Excel as I wanted to show the years on the X-axis:

You can see trends for Europe and APJ on the upswing.  North America in 2017 didn’t have as many SAP Inside Tracks in Mexico or the Caribbean.  I still maintain that North America will be lower due to the active 38 ASUG Chapters spanning the United States and Canada.

Raw data by region:

Region
2015
2016
2017

Europe
8
8
14

APJ
6
9
12

South America
3
7
7

North America
4
6
4

In working on this I reflected how in 2015 I helped John Astill with SAP Inside Track Washington DC, in 2016 I presented at SAP Inside Track Mississauga thanks to William Laverde and 2017 I presented virtually at SAP Inside Track Bangalore.

 

Reference

SAP Inside Track Wiki

You can learn more here:

BI2018

BI+Analytics Conference

Upcoming ASUG BI Webcasts http://bit.ly/2nceM8G #SAP #SAPCloud #AI

Overview:

* A business scenario in which IDoc is to be sent from SAP-ECC to Non-SAP System via SAP-PO (SAP Process Orchestration 7.5 Single Stack).
* Here, in this blog, we focus on how IDoc is been transferred from SAP-ECC to SAP-PO.
* In SAP-PO, IDoc-xml is to be transformed to a specific message format of Non-SAP System using Graphical Map and transformed message will be sent to Non-SAP System using SOAP Receiver Adapter communication channel, thus technically it can be called as a “Outbound IDoc-to-Soap Asynchronous Interface”.

Communication Channel Configuration:

IDoc is been transferred from SAP-ECC to SAP-PO using IDOC_AAE Sender Adapter, which can be configured in following manner:

1. RFC Server Parameters: Default(Recommended)

2. RFC Server Parameters: Manual

3. RFC Server Parameters: From NWA

Common errors during IDoc processing:

Normally in SAP-ECC’s t-code SM58, we see following common errors during outbound IDoc processing:

[1] Bean IDOC_INBOUND_ASYNCHRONOUS not found

[2] Error when opening an RFC connection (CPIC-CALL:

[3] Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad

Resolution of above common errors:

* 3rd Error can be resolved by correcting/verifying following points:

* Check IDoc_AAE Sender channels started or not
* Also verify SAP-ECC’s t-code WE20 partner profile outbound parameter details

* 1st and 2nd errors can be resolved by correcting NWA Configirations for ‘Default’ settings as given below…..

NWA Configuration Steps for ‘Default’:

 [1]         In SAP-PO create a RFC Destination connecting to SAP-ECC

Create one RFC Destination named as  ‘XI_IDOC_DEFAULT_DESTINATION’

NWA url:       http://sappoHost:port/nwa

Path:             NWA -> Configuration -> Infrastructure -> Destinations -> Destinations

Enter SAP-ECC details like:

* Target Host                    eccHost
* System Number             eccSysNum
* System ID                      eccSystemID
* SAP Gateway Host        eccHost

* SAP Gateway Service   sapgwXX

* where XX is SAP-ECC’instance Number (generally value is 00)

[2]          In SAP-PO create a Program-ID for Sap-Ecc

Path: NWA -> Configuration -> Infrastructure -> JCO RFC Provider -> Create

Here again, we need to enter all following parameters related to SAP-ECC, for example:

* Program ID                     PgmID_Ecc_PO
* Gateway Host                 eccHost
* Gateway Service            sapgw00
* Server Count                  5
* Application Server Host  eccHost
* System Number              eccSysNum
* Client                               eccClient
* User                                 eccUserId 
* Password                         *****
* Language                        EN
*

[3]          In SAP-PO, Resource Adapter ‘inboundRA’ configuration

Path: NWA -> Configuration -> Infrastructure -> Application Resources -> filter ‘inboundRA’ -> select ‘inboundRA’ ‘Resource Adapter’ -> Tab ‘Properties’

In ‘Properties’ tab, maintain following settings:

* ProgramID                          PgmID_Ecc_PO
* MaxReaderThreadCount    5
* DestinationName                XI_IDOC_DEFAULT_DESTINATION
* GatewayServer                   eccHost
* GatewayService                  sapgw00
* Local                                   false
* BindingKey                          PI_AAE_IDOC

[4]          In SAP-PO, starting Java Applications for Resource Adapter ‘inboundRA’

Path: NWA -> Operations -> Systems -> Start & Stop -> Java Applications -> filter ‘inboundRA’ -> select ‘com.sap.aii.adapter.idoc.sapjra.inboundRA’ -> start

Once Java-Application ‘com.sap.aii.adapter.idoc.sapjra.inboundRA’ gets started, its status turns to green, and respective ‘inboundRA’ status also turns to green

[5]          In SAP-ECC, check Registered Program

Once Java-Application ‘com.sap.aii.adapter.idoc.sapjra.inboundRA’ gets started, at this event, program-id ‘PgmID_Ecc_PO’ gets registered in SAP-ECC

Registered programs in SAP-ECC can been seen via following steps:

* in t-code ‘SMGW’
* -> Menu item ‘Goto’ -> ‘Logged on Clients’
*
* Once window opens, check TP Name= program-id ‘PgmID_Ecc_PO’
* Here total 5 entries of TPName ‘PgmID_Ecc_PO’ can be seen, as maxThreadCount in ‘inboundRA’ is given as 5.
*

 [6]         In SAP-ECC, create a tRFC RFC Destination

Create one tRFC RFC Destination (t-code SM59) with following parameters:

* Registered Server Program        enabled
* Same program-id                        PgmID_Ecc_PO
* GatewayHost                              eccHost
* GatewayService                         sapgw00
* Unicode                                      enabled

Testing:

Once above configuration gets completed, to trigger IDoc from SAP-ECC to SAP-PO, we need to do following tasks:

* ALE-Configurations for outbound IDoc

* In SAP-ECC,

* t-code BD54:  maintain Logical Systems for SAP-ECC, SAP-PO
* t-code WE21: maintain tRfc PORT having tRFC destaination
* t-code WE20: maintain Partner profile for outbound IDoc
* t-code BD64:  maintain distribution model

* In SAP-PO,

* use import/use meta structure of IDoc in Enterprise Repository
* Configure scenario having IDoc_AAE Sender Channel with ‘Deafult(Recommended) settings’

* Trigger IDoc

  http://bit.ly/2E4S8qy #SAP #SAPCloud #AI