Skip to Content

Category Archives: Uncategorized

Brazil Winners


The SAP Innomarathon JR 2018 occurred in the weekend of June 9th and 10th. The event was organized by the SAP Labs Latin America CSR team and hosted by the SAP Next-Gen. It is a spin off event of the SAP Innomarathon, and it´s called Junior because is targeted to high school students.

The event was held in four different locations at the same time: Brazil, Chile, Mexico and Peru. In each location, high school students teamed up to compete in Hackathons. The main question that all the groups had to answer was: how can you tackle the UN Global Goals using SAP technology?

Mexico Winners


In the first phase, all locations had to compete locally to find their SAP Innomarathon JR champion, where the appointed judges had to give points based on five different criteria: Engagement, Social Impact, UN Global Goals, SAP Technology and Project Viability. After the location champions were announced, they received feedback to improve their projects for the grand finale.

Chile Winners


The four location champions presented their ideas for the regional jury. Brazil with an intelligent biodigestor idea wanted to improve the use of a clean and sustainable energy. Chile presented a thermodesalination to mainly combat UN global goal numbers 6 (clean water and sanitation) and 7 (affordable and clean energy). Mexico team brought the recycling in the cities issue, and wanted to implement a system that would automatically separate trash to better redistribute for recycling purposes. Peru created a project for underground drip irrigation which is a better way to irrigate agriculture systems in arid zones.

Peru Winners


The SAP Innomarathon JR 2018 final happened with all the four locations connected remotely on the second day of the event. After the presentations from Labs Latin America CSR team, José Caceres, Director of Corporate Social Responsibility in Latin America and Maria Cecilia Calzada de Neumann, SAP Next-Gen Regional Manager for LAC, Spain and Portugal, evaluated and decided the winner. Since it was a tie between Brazil and Peru, the final prize was doubled and both teams got the award. The students earned each 250 EUR and a 3D printer for their school (Instituto Federal do Rio Grande do Sul Campus Osório in Brazil and Nuestra Señora de La Reconciliación in Peru).

April was Autism Awareness month and our SAP Labs Latin America prepared some special activities for our employees to engage with the cause. The activities aimed at raising awareness on the autism spectrum to break stigmas and increase knowledge on the topic, encouraging everyone to build a more diverse workforce.

The month kicked off on April 3rd with a special decoration in our Labs. Several hummingbirds, symbol of our Autism@Work program, also, stickers were distributed to all employees and a decorated frame was available for colleagues to take pictures.

A Leadership Talk with professor Vivian Missaglia, from Institute Autism and Life, gathered our colleagues in the auditorium for a special session that helped them to understand more about the autism condition.

Following the activities, our CSR group organized two sessions with Pandorga’s children and adults, where Labs employees could spend a special afternoon of fun and integration with autistic people.

Closing the month, two auctions with the arts made by the children from the Autism@Work local partner Pandorga, an institution that supports people with severe autism and their families.  Around 1000 reais were collected and donated to the institution.

We also had engagement from colleagues in external activities, 20 Labs employees joined the Caminhada Azul, a walk that occurred in Porto Alegre on April 8th, the walk was organized by Instituto Autismo e Vida with the objective to raise awareness on the subject.


In this year’s conference our Labs LA was featured like never before, with some examples shared from Hasso Plattner and Mala Anand. 900 customers from Latin America participated in the event, the highest participation from Latinos. The attendees had the chance to listen to references & success cases created with our Labs touch.

Our Chairman’s keynote, showed to the more than 30 thousand people the Leonardo Centers, including Labs Latin America.  Four SAP Leonardo success cases were shared. 2 out of 4 from LAC customers – Vale & Boticário Group, developed by our Lab´s colleagues.

The Data Management Suite / Data Hub was heavily discussed, being the center piece of the intelligent enterprise. Our location is instrumental in driving this success. We cannot forget to mention that our close friends from Stara joined the stage again this year. This time with Nicole Trennepohl, Marketing VP, presenting to a huge audience their co-innovation case with SAP.

Michael Kleinemeier, one of our board members, mentioned in his press release “Automatic Translation”, an idea born in our Labs and implemented in collaboration with GS, PS, SAP Translation Hub, SAP Language Services and Customer Success Hub.

Hasso Plattner, SAP’s co-founder delivered a keynote where he mentioned and used as an example one project that was developed by our colleagues from Labs Latin America. The project was L2A, Law to Action, which Hasso said that the project has a very interesting name. He presented L2A affirming that SAP Globalization Services team that delivers over 1000 regulatory changes every year, and the application pro-actively scans and analyze thousands of decrees in the world, determining the relevance of them and making recommendations upon it. He closed his comments with a very positive feedback, saying that this project show that “SAP in a very early stage know what is coming and how we have to react”.

Our Labs was also in the words from Mala Anand, SAP Leonardo data & insights president. She delivered a keynote together with Nicolas Simone, CIO of Boticário Group, where they discussed how to bring an Intelligent Enterprise to Life with SAP Leonardo. The keynote session also positioned how the world’s largest cosmetics franchise is transforming their business using the innovative technologies and industry excellence found in SAP Leonardo, which started with our Labs Smart Shelf Solution. Nicolas expressed his gratitude to SAP Labs Latin America on stage, highlighting our contribution in driving and enabling customers’ digital transformation, with special mention to Innoweeks. Innoweeks is globally known now!

Mala Anand & other Executives from LAC confirmed their visit to Labs for the Leonardo Live event in August and several customers showed interest and are already scheduling visits to our Labs, such as Comfama from Colombia, Xcaret and Liverpool from Mexico.

It is clear how well established we are in Latin America, now it’s time to spread our wings to be “the Innovation Hub for Americas”.

When you implement SAP B1 and wants to migrate transactions data also for batter analysis or its statutory requirement to have data of specified time period in your accounting software. Here i will discuss methodology and challenges during migration

Tool used for migration is Data Transfer Workbench (DTW) offered by SAP free of cost within installation package and same licenses and users can be used as used to use SAP B1 for detailed guide please visit

Templates with sample data applicable with DTW can be found on following path on same machine where DTW is installed C:\Program Files (x86)\sap\Data Transfer Workbench\Templates

The Methodology used during migration is EFI (Export, Filtration, Import) i will discuss it step by step and assume your legacy system’s database is also in SQL Server and for example you want to import Open Purchase Orders

1- Export (E): First you export Open Purchase Orders from your legacy system to excel while exporting develop your query according to Data Transfer Work Bench (DTW) templates  i.e 1 query for header and one query for rows with reference of header record number and line number for each row.

Fields which should be mandatory in your header templates are Document Number, Vendor Code,  Posting Date, Due Date, Document Date, Document Discount, Document Total and Vendor reference Number or any remarks any other fields according to your business process.

Further regarding required fields you can post some transactions in your test company with you consultant to know which fields you need to import 

Fields mandatory for rows are  Document Number, Line number, Item Code, Item Description, ,Quantity (Open Only), Warehouse, Unit of Measure, Unit Price, Discount , Line total and Line remarks if any or any other fields according to your business process


2- Filtration (F): Now you have your data in excel you need to do filtration and some updates according to SAP B1 like if there is change in item codes, vendor codes or UOM Codes, Whs Code,Update codes and descriptions according to new system, adjust charterer size of remarks fields as may be SAP B1 have short field lengths as compare to legacy system in this case you need to revise remarks or add UDF in SAP B1 according to character size of legacy system.

In Header File add additional column of Old document number From legacy system in your template and duplicate document number as its in legacy system.

Deploy a UDF for Old Ref number so in future user can easily track documents between legacy and new system.


3- Import (1): Now you have your data ready to import you just need to link column with relevant fields while importing i.e CardCode with vendor code and Cardname with vendor Name and so on



1- If you did not put discount there is some difference between multiplication of unit price and quantity system will automatically consider it as discount same for header total and total of all rows

2- If you did not put reference number from legacy system in separate filed user will never be able to track your documents

3- Reference between header and rows should be 100% correct otherwise header from one document will be imported with rows from other documents

4- Use Base Entry from SAP B1 if there are base documents like if you are importing Goods Receipts POs. To have accurate results use base entry of Po number from SAP B1.


Always perform such activity in test environment first after successful reconciliations go for live environment


This blog will discuss some important keywords that are relevant for a better understanding of CPE. Moreover, these terms will be used frequently and hence having a firsthand understanding of them would be beneficial.

Derivative Contract Specification (DCS)

As the name suggests, it is a contract specification in a way trading is done at exchanges. Every exchange provides a specification for a commodity to be traded at that exchange.

Consider an example of soybean to be traded at an exchange.

The above image shows that if a Soybean Futures Contract has to be created when the following specification have to be met.

Contract Unit signifies that the quantity should be in multiples of 5000 bushels. Price quotations for soybean to be traded at this exchange would be in cents per bushel. The specification even provides the minimum price fluctuation(tick size)  that is possible for the quotations of soybean being traded at this exchange.

SAP provides DCS similar to this.

As seen in the image above, the first tab ‘Basic Data’ shows the Physical Commodity i.e. Soybean. It also shows the unit of measure to be used for that commodity while trading i.e. BU. Product Symbol here is DCS is same as Product code in the contract specification.

Maturity Code Determination is the way to identify futures for a contract. But what are futures?

Well, whenever a commodity is being traded then the buyer and seller decide upon a specified future date as a reference and agrees to buy or sell that commodity at that date in future at a future price. These futures can be specific months, weeks or even days depending upon the commodity being traded. Each maturity code has a specific code and maturity code determination is used for the same.

Example: SMYY (as seen in the image)

  • S – Product Code
  • M – Month Code
  • YY – Year

So if the product code is for CME Globex and the mont is January 2018 then the Maturity code would be ZSF18. ‘Determination Methods’ is a way to determine the Maturity. It can be Manual or something like SMYY as shown in the image.

The second tab ‘Derivative Details’ gives some more information about the market.

Quantity/UoM refers to the lot size whereas the tick size is same as seen in the contract specification.
NOTE: Tick size can be different for a different MIC.

Other fields refer to the quotation that will be used for this contract specification. It is sometimes possible that CPE Unit of Measure can be different that Quotation UoM. This is typically in case of metals where individual components have different UoM.

The third tab ‘Periods’ gives details of all maturity periods possible for a commodity.

As seen in the image, the maturity here is for the month of July with a Contract Maturity Code ZSN16. There are different types of periods that can be defined and each refers to a specific activity. So in the image above trading can be done from 15.03.2014 to 15.07.2016 and quotations would also be for the same period. Whereas the final contract can be made in the period 01.07.2016 to 15.07.2016 and its settlement can be done only on 15.07.2016

These period are generally resemblance of how business is done for a specific commodity.

A DCS can be created/viewed using the transaction FDCS01 or from SPRO -> Materials Management -> Purchasing -> Commodity Pricing -> Commodity Pricing Engine -> Definition of CPE Quotations -> Market Data Based on Derivative Contract Specification -> Derivative Contract Specifications -> Specify Derivative Contract Specifications

A similar path can be identified for Sales and Distribution side.

Market Identifier Code (MIC)

MIC is a four character key that identifies a stock exchange or a trading platform. It is assigned to a DCS and each DCS needs to have at least one MIC assigned to it. An operational MIC always starts with ‘X’ followed by 3 more characters. The MIC seen in the DCS above is not the operational MIC but rather a MIC of the operational MIC.

XCBT is the operational MIC for Chicago Board of Trade but it has a market in different cities so if the trading is done in Chicago then the MIC used is CBOT whereas if the trading is done in Kansas City then the MIC used is KCBT.

There can be a case when more than one MIC is assigned to a DCS. This happens if the contract specification is similar for both the exchange or trading platforms. For example: If soybean is traded at both FCBT and KCBT and the contract specification is same, then both MIC can be added to a single DCS.

Moreover, a MIC can be assigned to multiple DCS as a MIC only identifies the market but not the commodity being traded

MIC can be created/displayed/changed via SPRO -> Materials Management -> Purchasing -> Commodity Pricing -> Commodity Pricing Engine -> Definition of CPE Quotations -> Market Data Based on Derivative Contract Specification -> Specify Market Identifier Codes

A similar path can be identified for Sales and Distribution side.



Both DCS and MIC together form a market reference that is frequently used in CPE.

More in the upcoming blogs.

There are different types of master data class and HANA views delivered in S/4HANA embedded BW.

S/4HANA 1610


InfoObject Hierarchy Class Hierarchy Data Source

Master Data

InfoObject Master Data Class Master Data HANA View

I’ll keep updating the blog for 1709 and future S/4HANA versions.

1.Go to Administration>>System Initialization>>Implementation Center>>Implementation Tasks


2) Select Copy data between Companies:

select Copy to file.

save the file where we want to export data with extension .qdf then press OK.

3)It will shows which type of data we want to copy data .its will select relevent fields also.

E.g.if we take Item master then system autmatically select item groups,UOM,warehouse master etc (relelevent info).

then click on export button . now this data store in selected qdf file. it will show data dependecies.

4)Now Import this file >>select Copy from file

Copy Method use: 4.1)

Adds new records and updates records with matching keys


Does not update records with matching keys but adds new records


Updates records with matching keys without adding new records


Erases all existing records in the target database and adds new records

5) COPY Options:

  • Use Accounts in Source – If the source accounts also exist in the target, then the application copies the account assignments from the object in the source to the object in the target. However, if the source accounts do not exist in the target, then the application encounters an error during the copy process.

  • Use Default Accounts in Target – The application assigns the default accounts in the target to the object, and does not copy the source assignments.

Respective data fields seleted then Import 

now all item master data copy from source comapny to target company.

The product is constantly changing, so if you find anything different than the real product, don’t be surprised and please do comment and let us know.

SAP Analytics Cloud Planning model has the capability of currency conversion( in this blog, we’ll user CC for short ). The rate information is maintained in rate table

Below is a how a rate table looks like.

Currency and Currency Conversion setting

Currency Conversion off

The Currency setting will be a bit different when you switch on and off Currency Conversion.

For a Model that has CC switched on, you should choose either a Default Currency or a Currency Dimension for the model.

CC off with Default Currency

In the case of CC off, the Default Currency is both the default reporting and input currency.

You can also choose to use a Currency Dimension. Noticed that unlike BPC the ID of the Currency dimension is the currency key, in SAC, you need to specify a currency property.

  • For Organization type dimension, the property is Local Currency
  • For Generic type dimension, the property is Currency

In any of the case above, the Story will not automatically detect the currency type and the number will be displayed as normal key figure without any currency sign.

Use Local Currency from Organization dimension as the Currency Dimension

Currency Conversion On

You can also switch on the Currency Conversion feature for a model. And once the CC is created, you’ll need to setup both Default Currency and a Currency Dimension. Similar to above, the Currency Dimension can be either Organization or Generic type.

Also you need to choose the rate table you want to attach to this model.

Currency Conversion on

How CC is performed

CC in SAC is performed at runtime. Different than BPC, the converted results are not persisted. When CC is on, SAC only stores the local currency data. For planning case, user can input both local currency and converted currency.

In SAC, unlike BPC where you can drag/drop CURRENCY on row/column as it’s a dimension, to display the Currency property, you’ll need to create a Currency Conversion typed Cross Calculation.

By default, there are 2 types of Cross Calculation members. One is Default Currency and the other is Local Currency. When you create a story, by default only the Default Currency is displayed.

Default Currency and Local Currency

*If you use Org type, it’s Local Currency, if you use Generic type, it’s Currency.

Below is a report with CC on. Story will automatically attach the currency sign to the number.

Currency Conversion on and Org type dimension as Currency Dimension

Besides the 2 types, you can create more “currency measures” by adding a new CC type calculation.

Create CNY type Currency Conversion

After creating the CC, it’ll become a member in CrossCalculation. You can choose to display it on the story like any other dimension members.

CNY displayed on the report

*You need to make sure the rate values are maintained beforehand, otherwise the story won’t show correctly.

Meaning of Default Currency is different when switching on/off Conversion

  • When CC is off, Default Currency is both reporting currency and input currency
  • When CC is on, Default Currency is Reporting currency. The end user is inputting data on Local Currency, Default Currency is automatically converted. If user input data on Default currency or Converted Currency, before publishing, the other type of currency data will become temporarily unavailable. After publishing, SAC will calculate all types of data.


Type in Default Currency, before publish

After publish


About Import from S/4HANA

S/4HAHA has 3 default types of currencies:

  • Global Currency
  • Transaction Currency
  • Company Code Currency

The relationship of currency between S4 and SAC is below:

Global Currency Default Currency(model setting)
Transaction Currency Currency dimension(Generic type Currency Dimension)
Company Code Currency Local Currency( The Currency property in Organization dimension )

So based on above mapping relationship, we can create below table as recommendation of Import

CC on Import Company Code Currency to Local Currency
CC off w.o Currency Dimension Import Global Currency to Default Currency
CC off w. Currency Dimension Import Transcaction Currency to the Currency Dimension

Export to S/4HANA Mapping Recommendation

SAC Export is flexible. But without proper configuration it’s easy to make mistakes.

Below is the recommendation for export:

CC on CC off
w. Default Currency w. Default Currency w.o. Default Currency
Org Currency Dimension LC->ComCode Curr NA (new case)
LC->ComCode Curr
Generic Currency Dimension (new case)Generic Curr -> Tranx Curr NA(used to support) (new case)
Generic Curr -> Tranx Curr
w.o. Currency Dimension NA Def Curr -> Glbl Curr NA



Import/Export with BPC Recommendation

This is still being discussed as the behavior could be very complex when introducing the new Currency as dimension concept.

At last

As I have also emphasized at the beginning of this blog, this is an evolving product and the feature is kept enhanced. Do not feel surprised my blog becomes completely wrong in a few months. If you find do, do leave comments and let us know. Thanks in advance!

After a long wait or more than a decade(personally), we finally have the most awaited feature in document management capability in SAP Solution Manager 7.2 version in SPS 06 onwards.

Yes, it is now possible to have the mass upload of documents in SAP Solution Manager including their attribute maintenance.

We recently upgraded couple of customer on Solution Manager 7.2 SPS06 or SPS07 and finally seen this new functionality working out of box. Ofcourse, it was earlier working in Build Add-on etc. but it was with few customers only.

Above is now available to all and it is really a much awaited features boosting the usage of documentation in Solution Documentation scenario of Solution Manager.

However, if you have upgraded your solution manager from 7.1 version to latest Solution Manager 7.2 SPS06 or SPS07 then it will be hidden be default in SOLDOC.

You should perform below simple step to enable it.

Step 1 – Goto solution documentation tile from fiori launchpad or enter soldoc transaction code.

Choose the ribbon or global menu and select SHOW DROP AREA.

Step 2 : We should be able to see the button or area in the lower portion of screen DROP DOCUMENTS HERE as below.

Hence, we can now drag and drop several documents which can be of type pdf/document/excel files etc. from our local desktop/laptop to specific location in solution documentation.

In addition, I would like to also share that I have seen sometime a below error i.e. SERVICE CANNOT BE REACHED.

It is a bit difficult to troubleshoot as it didn’t provide much information here but basically we need to activate one SICF service.

Kindly visit SICF transaction and activate below service i.e. SMUD_DROP_DOCS.

Once it is activated you will be able to see the button for mass upload as below.

Really an exciting feature and will share some information regarding the same latter. It is really saving huge efforts for maintaining or uploading several documents at the same time.

Feel free to share your opinion about the same.



Dear SAP EA Explorer users,

Almost 5 years ago, two colleagues and I had the idea of providing an information platform for customers, using a semantic network to relate technical concepts with SAP products.

When we launched this project, semantic approaches of this kind were relatively new, so it made a lot of sense to start with a specific, individual tool that we later called SAP Enterprise Architecture Explorer.

Now, five years later, the SAP world has moved on (in a positive sense), with much stronger focus on simplification, and new initiatives to relate valuable content for our customers.

I really like this development, although it also spells the end of the Explorer.

SAP Enterprise Architecture Explorer to be discontinued by end of July.

It’s been a great journey but– unfortunately – it has to end here. After many years of successful collaboration with the German SAP User Group (DSAG) and with individual customers throughout the world, this is a sad moment. The fact is however that there are simply too many SAP information platforms at present, meaning that some inevitably have to disappear for the greater good.

Why so sudden?

Why do we need to shut down so suddenly and quickly though? The plan was to carry on until the end of September. Unfortunately, with some global changes in the SAP environment, we now have a pretty serious bug in the Explorer that limits our capabilities to make changes to its content.

Considering that the Explorer is going to be shut down anyway, it makes no business sense for us to invest in further bug fixing.

We have therefore decided to bring forward the discontinuation to the end of July.

Will the content be distributed to other places?

A lot of content has already been transferred to other places. If you have been following the history of, you might recognize that these pages contain a lot more detailed information than back in 2013, when we started with the Explorer. Also, the SAP Help Portal has evolved over time to more of a knowledge portal. Finally, there are tools like the SAP Transformation Navigator.

While most of the various content types can be found at these places, some types might be lost for now. We are obviously trying to avoid this, especially for particularly popular content. In the case of the “Enterprise UX Strategy” and “Enterprise IoT Strategy” topics for example, I plan to create two blogs containing all the information previously stored in the Explorer.

Every end is a new beginning

As the blog’s title points out: “Every end is a new beginning”. And so, this story too will turn into something new, something bigger and something with even more value for all of us.

Some of you might wonder what will happen to me, as most of the external communication for SAP EA Explorer went through me. Besides being the guy on Twitter, LinkedIn, SAP Community and TechEd, I was also the project lead, major architect, and the content owner for numerous topics.

Since April 2018, I’ve been working in Christian Klein’s new board area. Katja Mehl leads a team here that focusses on customer experience at SAP across all digital interactions between customer and SAP. Working as a solution architect for this team, I’m going to steer individual customer requirements into something that we currently call “MyHome”, a central location that connects customers with the various locations and content types within SAP.

You can therefore still count on me to bring together the different strands within SAP that are of most value to your daily business. For me this is an even greater chance to support our customers. I’ll tell you more about this project once it gets well and truly off the ground.

Thank you to all our users and contributors

By way of closing this blog, I would like to say a big thank you to all of you who supported this project, either with content or with feedback. And I also want to thank all of our users for their amazing support and interest throughout the course of the project. I would be delighted if you would continue to follow me as I embark on my new adventure with “MyHome”.

All the best,