1 2 3 13 Previous Next

SAP Business One Application

189 Posts

Dear SAP Business One Consultants/Partners/Customers/Co-ordinator


To start off this discussion (not a serious one )

I want to know the journey of  the people (of their respective SAP Business One Career)who are active in our area of SAP Business One particularly. So it could be helpful for people looking into an SAP Career via SAP B1


To start off, i will tell my journey since i have started it.(no need of mentioning company names)


Well  i started my career as a sales employee(BDE) selling IT Products after doing B.E(C.S)(even though i didn't have a clue about it )

But the reason being i wanted to learn both technical and management so i  completed my M.B.A (Sys&Mktg).


I wanted to make use of both my Technical & Management knowledge to be productive in my career. I had heard of SAP during my M.B.A period but when i joined for an institute(unauthorized -only came to know later) to learn the course there was no mention of SAP Business One any where.

If you want to enter SAP career, you can only do by doing the following course SAP FICO/SD/MM/CRM(All R/3) cause R/3 consultants make huge bucks of money . So happily i completed my SD course in an institute (but later came to know only doing course is not enough have to do certification .Thought of completing that also but there is no Guarantee of getting job after paying huge amount  as END TO END implementation experience is required.(this i have heard n number of times whenever i tried applying for an SAP R/3 Job)


Somehow joined a Startup company which gave an opportunity to work as SAP Business one consultant provided you get some business to them (expected startup company have to compromise).But the good thing was that i got introduced into SAP Business one which a product specifically designed by SAP for SME'S .In that duration i got chance to go to SAP company got  training on B1 technical by Yatsea Li   and  some how journey continued. Got to know that B1 consist of all modules in one single software so worth of doing degrees was somehow accomplished   .


Later on i wanted more knowledge in SAP B1 hence joined the course specifically on SAP B1 in an Authorized institute(this time with proper information) . Later got chance to work in a Customer company and became active member in this awesome community of SCN. Both through my exposure to issues in the company and issues posted in SCN forum  helped me a lot in completing my certification in B1.



So though this blog people looking for  an SAP Career keep you eyes and years open, there is not only R/3 required to enter into SAP but there are many other modules like B1 which doesn't ask for any END- End implementation experience, provided you have thorough subject knowledge .


the SAP Business one DEMO videos posted by Richard Duffy is really helpful for people looking to get a good SAP B1 subject knowledge and SQL queries for SAP Business book by Gordon Du is helpful to get a proper SQL skillset .I also got guidance from Prasanna s in my sap b1 journey .I would like to thank everyone for all their direct and indirect help..


I kindly request people to share their SAP B1 Journey so it would be worth full for the  community and people looking specifically in our B1  community.



Darshan Desai

SAP Business One 9.0, version for SAP HANA PL13 has been released, available as base installation and upgrade patch.


SAP Business One, version for SAP HANA 9.0 PL13 is synchronized to:

  • SAP Business One 9.0 PL13
  • SAP HANA Platform Edition 1.0 SPS 07 Rev 74.3 (Since HANA Rev 70, you can install any HANA Rev directly without a base revision installation, hereby you can install HANA Rev 74.3 directly without Rev 70 installation.)
  • SAP Business One 1.1 analytics powered by SAP HANA PL05


  • Migration between SAP Business One 9.0 PL13 and SAP Business One 9.0 PL13, version for SAP HANA is not supported.
  • If you are running SAP Business One 8.82 PL02, version for SAP HANA  and lower, you can upgrade it to SAP Business One 9.0 PL13, version for SAP HANA directly.
  • If you are running SAP Business One on the Microsoft SQL Server, upgrade the database to SAP Business One 9.0 PL12, and then migrate from the Microsoft SQL Server database to the SAP HANA database. Then you can upgrade it to SAP Business One 9.0 PL13, version for SAP HANA.


As of PL11, SAP Business One 9.0, version for SAP HANA supports both SuSE Linux Enterprise Server 11 SP2 and SP3 If you use SAP Business One 9.0 version for SAP HANA and want to upgrade the operating system to SPS3, you must first upgrade SAP Business One to PL11 and then upgrade the OS.

Please check the corresponding PL13 central note for more details : 2046092 - Overview Note for SAP Business One 9.0 PL13, version for SAP HANA

Important Notes

SAP Business One 9.1 PL01, version for SAP HANA is currently synchronized to and contains all bug fixes of the following base versions: 

  • SAP Business One 9.0 PL12, version for SAP HANA
  • SAP HANA Platform Edition 1.0 SPS 07 Rev 74.3

Note: SAP Business One 9.1 PL01, version  for SAP HANA contains the integration framework (B1iF) version 1.20.0 and SAP Business One analytics 1.1 PL05 powered by SAP HANA.


Please check the Overview Note for more details:

2046045 - Overview Note for SAP Business One 9.1 PL01, version for  SAP HANA (S-user required)


Upgrade Path

  • Migration between SAP Business one 9.1 PL01 and SAP Business one 9.1 PL01,  version for SAP HANA is not supported.
  • If you are running SAP Business One 8.82 PL02, version for SAP HANA and  lower, upgrade it to SAP Business One 9.1 PL00, version for HANA, then you can  ugrade it to this patch level.
  • If you are running SAP Business One 9.0 PL12, version for SAP HANA and  lower, upgrade it to SAP Business One 9.1 PL01, version for HANA directly.
  • If you are running SAP Business One 9.0 PL11 and lower on Microsoft SQL  Server, upgrade the database to SAP Business One 9.0 PL12, then migrate from the  Microsoft SQL Server database to the SAP HANA database. Then you can upgrade it  to SAP Business One 9.1 PL01, version for SAP HANA.


Important Notes


SAP Business One analytics 1.1 PL5 powered by SAP HANA is synchronized with:

  • SAP Business One 8.82 patch level 7 and higher
    SAP Business One 9.0 patch level 3 and higher
    SAP Business One 9.1
  • SAP HANA Platform Edition 1.0 SPS 07 Rev 74.3


Please check the corresponding central note for more details:

2036585 - Overview Note for SAP Business One analytics 1.1 PL5 powered by SAP HANA (S-user required)


Other interesting notes are:

1914461 - SAP Business One Analytics Portal (S-user required)

2036802 - You Can Now Use Semantic Layers Provided by SAP Business One analytics powered by SAP HANA (S-user required)

Dear All,


My client's industry required BOM and Production Order must be Multiple Inputs to Multiple Outputs. We propose to create customization program to work on it but client do not want any customizations. Any suggestions?


Thank you very much in advance.


Best Regards,


One of the key strengths of SAP Business One is the ability to tailor the solution to the needs of customers using add-ons developed by our Software Solution Partners (SSPs) and our Value Added Resellers (VARs). So you’ll be pleased to know that SAP Business One Cloud still has add-ons, the scope of them has just changed slightly so they get a new name, SAP Business One Cloud Extensions.

In this post I’ll cover what SAP Business One Cloud Extensions are and what you need to consider when deploying them as part of your SAP Business One Cloud Strategy. In part two we’ll look at how you deploy extensions in the cloud.

So why the name change? The reason is simple, we wanted to differentiate between cloud add-ons and on-premise add-ons as there are multiple extension types in SAP Business One Cloud:

  • Compatible add-ons - These are add-ons that do not have fully automated lifecycle management within the SAP Business One Cloud environment. This means that they may need manual configuration outside of the SAP Business One Cloud Control Center. Typically these add-ons will be on-premise add-ons that have been made compatible with any changes in the API to support the cloud but not fully migrated to take full advantage.
  • Add-ons enabled for Lightweight Deployment - These add-ons have been designed to take advantage of the ability to fully automate lifecycle management with the SAP Business One Cloud Control Center. Depending on just how extensive the integration has been it may be possible to configure a large amount of the add-on from within the SAP Business One Cloud Control Center, removing the need to configure the add-on in the SAP Business One client thereby speeding up deployment and reducing complexity. These add-ons can also be certified by SAP for use with SAP Business One Cloud.
  • SAP Business One Script - This is a lightweight, javascript based  extension system that allows you to develop small solutions that address last mile extensibility requirements for customers. This provides users with very flexible, sandboxed and simple to use extension functionality.



More information about SAP Business One Cloud Extensions, such as the certification process, a list of certified extensions etc. can be found in the SAP Business One Cloud section of the PartnerEdge.com

When developing the SAP Business One Cloud architecture SAP did a lot of work to ensure that it was possible to run multiple extensions from multiple providers (and even multiple versions of the same extension - key when it comes to supportability) within the same service unit in a SAP Business One Cloud landscape. Even so this doesn’t mean we should deploy them to our tenants without careful attention.

One of the key reasons being that each extension is different and we should consider how an extension uses the infrastructure we provide it. Let’s put this into a pricing context, should we charge the same price for the infrastructure required for a an extension that consumes 300MB of RAM versus one that consumes 1GB? The knowledge of the resources consumed by an extension is not just important for deciding pricing, we also need to know so that we can accurately size the resources in our landscape.

How you price for the infrastructure required to run extensions is entirely up to you but let’s look at some possible strategies. We could decide to tailor the price for each extension individually but this could make the pricing to our customers more complex, and when it comes to cloud we are trying to make the complex simple for our customers!

One thought is to categorise extensions into different pricing levels, e.g. 1-3 with 1 being the least costly and 3 being the most costly. For instance an extension that consumes an additional 150MB of RAM over the core SAP Business One client process is categorised in Level 1 whereas an add-on that consumes an additional 1GB of RAM is categorised in Level 3.

Doing this gives the ability to calculate the total cost for each user easily based on the extensions used and provides a predictable and transparent structure to our customers. Some partners even include the first Level 1 extension in the base infrastructure cost as customers typically use at least one extension.

As well as the obvious infrastructure cost there are hidden costs too.  With each upgrade of SAP Business One we perform in the cloud (see my previous post here) will need to consider the impact on the extensions our tenants are using. This impact ranges from the small, e.g. no changes needed at all, to large when extensions follow a major upgrade path of their own. In running a multi-tenant environment where the tenants in a service unit are running the same version of SAP Business One (preferably the most current to ensure they are getting the most benefit from the application) how do we handle an extension that a tenant is running that has not yet been upgraded but it’s author? What about the testing process of an extension running against a new release of SAP Business One?

When we start to consider all of potential impacts you may decide that you are going to need to introduce some level of governance to control which extensions you deploy in your SAP Business One Cloud landscape. There is no right or wrong answer in how strict or otherwise you want to be in deciding the level of control, the trade off is between flexibility and cost/efficiency in running a SAP Business One Cloud. Ultimately it is for each partner to decide what is the best policy for their cloud however in order to try to create some guidelines you may want to consider the following aspects for your policy:

  • Decide what type of extensions you are willing to consider deploying in your landscape, e.g. only SAP Business One Cloud certified add-ons, add-ons for lightweight deployment  or compatible add-ons(I make no mention here of SBO Script add-ons as these designed specifically to avoid many of the deployment pitfalls we face in the lifecycle management and resource consumption of an extension)
  • Define the categories you want for extensions and decide on the pricing of each band, e.g.:
    • Level 1 extensions - Up to 150MB RAM consumption per user
    • Level 2 extensions - From 150MB - 500MB consumption per user
    • Level 3 extensions - More than 500MB consumption per user
  • Decide how a customer, consultant, sales person etc. can request the deployment of a new extension to the SAP Business One Cloud landscape.
  • Collect information from the provider regarding compatibility with cloud, cloud commercial agreements (e.g. subscription pricing) etc.
  • Ensure that your are satisfied with the development approach taken for extension updates, compatibility with new releases of SAP Business One etc.
  • Define your own testing procedure for each new extension, to include:
    • Deployment
    • Operation
    • Resource consumption
    • Compliance with your cloud infrastructure (interaction with the resources in your cloud landscape - especially important if an extension has not been adapted for the cloud fully and doesn’t conform to the SAP Business One Cloud guidelines for extensions.)
  • Based on the outcome of your testing use the metrics to classify your extension into levels you have decided on.
  • Publish the pricing to your sales team so that they can quote effectively for new customers.


I’m sure that you will think of many other things and that your approach and policies will evolve and change over time, as your experience of running customers in the cloud grows. This post isn’t meant to be an “must do” list of working with SAP Business One Extensions, it is instead meant to provide some food for thought when you start working with them.


We are work with partners all the time to share best practice for different aspects of SAP Business One Cloud landscapes, so if you have any thoughts on the above or any related topic please let us know.


In part two of this post I’ll look at how you manage the lifecycle of extensions in the SAP Business One Cloud Control Center.


About me:


I've been working at SAP with SAP Business One for the last 9 years in a variety of roles. Currently I look after SAP Business One Cloud and spend much of my time working with partners to help them take advantage of the new and exciting opportunities that have emerged since it's release. You can follow me on Twitter @joelaharris if you want to hear more!

This was originally posted at ASUGNews.com.

When Murriel Calaycay of Mars Air Systems attended the 2013 ASUG SAP Business One Summit in Anaheim, it was her second year at the event. And while that was a short trip from her Gardena, Calif. office, the uniqueness of the Business One Summit’s focus on small and medium enterprise has her making the 2,000 plus mile trek to attend this year’s summit in Schaumburg, Ill.


“One of the big draws to this summit, compared to some of the others, where there is so much content that is fun to know but is not really going to provide business value—is having it specifically focused on Business One,” says Calaycay. “That is the biggest value for me.”


The SAP Business One Summit, being held September 15-17, is like other ASUG events throughout the year in that it brings together customers, partners and experts for education, networking and influence. But no event serves those purposes for small and medium business better than the Summit—and this year, attendees can expect an even greater emphasis on customers.


The SAP Business One Summit will also give customers unparalleled access to members of the SAP Business One team. Calaycay recalls SAP’s workshops as being some of the most valuable sessions she attended—from those that would go into a “little bit of detail” on certain products to others that would preview the latest enhancements. Calaycay also says the Summit connected her with many partners that helped her build the crucial add-ons used at Mars Air.


Customers will also get the chance to hear from other customers – in dozens of user-led sessions based on feedback from previous years’ content and trends. Highlights also include a customer panel session following the SAP keynote on Sept. 16 of the Summit and customer award presentations on Sept. 17.


“SAP’s Business One customers make up one of the fastest growing communities in the SAP ecosystem,” says Margo Jadzak, ASUG’s Senior Vice President of Business Development. “ASUG is committed to providing all of the advantages of connection and community that membership brings to large businesses to Business One users as well.”


Access to that independent ASUG community is important to Calaycay, who devotes time to volunteer in the ASUG SAP Business One Special Interest Group (SIG). She says there are people she has met at the summit who she stays in touch with through the SIG to continue to gain insight and advice all year long.


“There are some people I meet that I keep in touch with to be able to bounce questions off of,” says Calaycay. “We share war stories, implementation successes and challenges. It’s always nice to hear about how things went.”


For more information of the SAP Business One Summit, check out the digital brochure and visit the ASUG event page.

SAP Business One 9.0, version for SAP HANA PL12 has been released, take advantage of the latest new features.


SAP Business One, version for SAP HANA 9.0 PL12 is synchronized to:

  • SAP Business One 9.0 PL12
  • SAP HANA Platform Edition 1.0 SPS 07 Rev 74
  • SAP Business One 1.1 analytics powered by SAP HANA PL04


  • Migration between SAP Business one 9.0 PL12 and SAP Business one 9.0,
    version for SAP HANA PL12 is not supported. 
  • If you are running SAP Business One 8.82, version for SAP HANA PL02 and
    lower, upgrade it to SAP Business One 9.0, version for HANA PL11 first. Then you
    can upgrade it to this patch level. 
  • If you are running SAP Business One on Microsoft SQL Server, upgrade the
    database to SAP Business One 9.0 PL11, then migrate from the Microsoft SQL
    Server database to the SAP HANA database. Then you can upgrade it to SAP
    Business One 9.0, version for SAP HANA PL12.


As of PL11, SAP Business One 9.0, version for SAP HANA supports both SuSE Linux Enterprise Server 11 SP2 and SP3 If you use SAP Business One 9.0 version for SAP HANA and want to upgrade the operating system to SPS3, you must first upgrade SAP Business One to PL11 and then upgrade the OS.


Please check the corresponding PL12 central note for more details : 2025674 - Overview Note for SAP Business One 9.0, version for SAP HANA PL12 (S-user required)


Main new features

Check the PL12 overview note for details about the new features and fixes included offered by SAP Business one 9.0 PL12, version for SAP HANA:
2025674 - Overview Note for SAP Business One 9.0, version for SAP HANA PL12 http://service.sap.com/sap/support/notes/1997092(S-user required)


Important Notes

June 23, SAP Business One helps small businesses to grow quickly and profitably, while fully integrating their business operations with a single application. SAP has now started to ramp-up the new SAP Business One 9.1 and SAP Business One 9.1, version for HANA. The new release speeds time to value, facilitates business adaptability, focuses on functional improvements and simplifications of implementation, operations and usage of SAP Business One.


More information can be found on the SAP Partner Edge Portal (Partners only).

Since SAP Business One is one of the most popular mid-sized ERP Application in Pakistan, and many of those who are using it are pretty much satisfied with their selection, where there are many who always compare this with local market trends and give excuses for not adopting it because of their budgeting constraints.

But the comparison is always there, either they belongs to a construction, retail, trading or any industry, Most of the people (even from the IT Industry) in Pakistan usually don’t know the difference between SAP and SAP Products, for them SAP products are all SAAAP (something really big), they neither don’t go into details nor investigate or if I rephrase it: they don’t know anything about ERP Products. Similarly, like users on Oracle application, one of my friends is a very literate and bio-medical engineer, even from him I have heard saying that he is working on Oracle…. As I have a very large interest in Software Application development I asked him when did you learned programming, and when he replied; I found out that he is just the user of some Oracle – based application and doing some KPO kind of work, that means again they don’t know the difference between Oracle and Oracle based products. And this is my first point; the basic understanding or general concept. No matter you are an IT professional or not, it is just like what is gastroenterologist in medical sciences, and every person should know.

Concept and understanding

People don’t know the differences in terminology.


Need to develop the understanding first; Not only for the differences between the databases and applications, but also between the brand/company and their products. The understanding won’t take time, all one need is internet; it can be found easily through Google, or by asking any relevant person, or just visiting or browsing the relevant web resource or even Wikipedia.

IT People of your organization need to give some presentations on Technology which they are planning to adopt – or invite the staff of your organization in Demo Presentations of Software – Which channel partners are presenting. And ofcourse have some interactive questions and answers sort of session with them to get better understanding.

Skilled Workforce.

People don’t adopt changes easily.


There are some organizations which really doesn't have any IT literates, or they have the mid-sized  IT setups, but they are working on Microsoft Office for recording their daily basis transactions and billing, where in some they have the skilled people and the setups as well, but using obsolete technologies, and they are in majority in Pakistan, the mid level business now have trends to adopt customized solution locally available, and this is a good sign, but again; there are few using Oracle based system, or some cloud based applications which are marked as good large enterprises and not in the list of mid-sized company, which i am talking about.

The IT industry fashion is now changing in Pakistan, now you can find POS application on every store, locally developed by software teams and big named software firms and brands, now here comes the second part of this document, Workforce i.e. people who are working on those systems. One don’t need to be IT literate, (when we use the word IT literate in Pakistan, usually it means the person who knows how to operate computer, and internet.) for working in such mid-sized business Software application.

I have seen many people, who are trained for the Key Punching Only, and when the application halts or gives system messages, they starts screaming and leave the terminal or asking for help. A freelance developer was sharing his experience on a blog and was stating that a guy was complaining that the system is giving error and not allowing him to post the transaction, and when support team checked the error, it was a system message asking him to input some mandatory fields. It is something just not he doesn't know how to read, but it is because he don’t own or he don’t care, and in most of the cases, where people were working on a fox-pro based legacy system and migrated to the new GUI interfaced system, they don’t adopt the changes easily, or they don’t want themselves to get upgrade, and then, there is the problem.

Most of the people in mid-sized organizations don’t want to work on new systems, there are few, which in my knowledge which were working on locally made ERP solution and when they get to know that their management is deciding to move on SAP, then, they were found saying; SAP is big investment, SAP is not the solution, even in ABC, XYZ (some big organization name in Pakistan) company they are implementing it since 2 years and it’s not working for them, and all words of different mouths from the planet to prove that the management decision is a foul.

Having said that, again there are few mid-sized organizations in which people are willing to work in new technologies and it is easy for any channel partner to work with them easily as the interest level is there for adaptation.

Need to ask Auditors or IT People of your organization to do some gap-analysis, and give some presentations on Technology; planning to adopt – difference between the legacy and SAP Business One, and how it can be beneficial for the organization, the new processes and procedures, and also ask them to sit in the demo presentation.

This will really helps the staff to understand the importance of organization up-gradation process and their updation as well. This is the very important part; an employee who is working on SAP products gets his profile also updated, as the SAP business one is globally recognized system.

Information Sharing

People don’t share their desk information.


Information sharing in any organization has a very significance importance, to float the correct and authenticate information is a part of efficient reporting, organization which have people with such behavior always grow by taking quick decision on their smart reported information, Now, there are some black and some white sheeps always there in an organization, despite of the internal politics, which is again the integral part of organization, there are people who wants their organization to get dependent on them, and there comes my third point, information sharing.


When one migrated from legacy to new SAP Business One system, the old closing balances either from financials or inventory figures comes into play, and there is the hurdle, the employees of such behavior mentioned above, will delay the implementation process, and even if the float the information the audit  or IT team will take large number of days to authenticate or audit those figures reverting back to them again and again.


If we have started the process of implementation from Understanding the basic concepts and skilled workforce, it would get easier than, to work like a team, on closing balances and relevant figures. The process time varies from organization to organization depending upon the sizes and numbers of the transactions,


Need the provisional date of closing from the starting, so when the requirement specification or a blue print is started by the Channel partner, then the management or concerns should announce the provisional cut-off date to calculate the closing Balances. Which will helps the organization to save the time when it comes to the closing balances import.

Reporting and Informative Queries

People don’t know what and how to report.


Reporting is the most important part of any ERP Solution; I have heard people saying this report is not in the System, when asked. Despite of general formats of marketing or traditional documents, there are other information as well, which management or departments do requires for their daily working or decision making, Since, SAP Business One integrated to SAP Crystal Reports, now provides you an option to make as many report as you want, moreover, a query manager is there to give proper information to the users when required.

The problem is, the departments don’t have interest when it comes to reporting part. They either forward the IT Department or channel partners their legacy formats or just ask verbally about the processes and doesn't think for the MIS level or beyond it.

For example, a store manager should have the aging report for the inventory that can be made easily on SAP Business one, the requirement is there but the demand is not ON.  The Other Example; A manager asked a query from his department on phone, and the guy was replying back to him sir I don’t have such report in my system. The information is there, all he needs to do is share the queries with the channel partners or their IT Department, so they can give them access of query manager with such information which is not required on hard evidence but usually asked for information only for some other purpose.

The IT Department or concerns should conduct some reporting session with the inter department personals, asking them what they are reporting, what queries are general, what are on daily basis, and what would they think they will be requiring for any summarized patterns etc.

Training and Hands-On.

People don’t take training seriously.


And yes, they really don’t. when IT Department or channel partners starts training of the staff, they always pretend that they know the process already, and sometimes yes they do, but the new interface, may have some different ways for doing the daily transactions, but not necessary.

The management should ask the staff to reserve some time to do some parallel working, the general problems which usually seen, they complaint they don’t have time to do the parallel working. Because they don’t know the importance they don’t care.

Need to conduct more sessions, after the primary training as well. Addressing individual user, and ask them on daily basis, the problem what they are facing, and how they are doing, Feedbacks will not only helps the concern to define the authorization in the system, but also will helps to develop the controls, and the reporting.


That concludes my post, I didn't mention intentionally the infrastructure, this is just the experience sharing post and many of you may have different opinions regarding the subject.

Thank you for reading.



Some of you might already know this but in case you don't have...


Hereby explained : How to post inventory Opening Balance by using FMS.


It will ease your work and make work efficient and time saving.



Step 1:


Create one User Defined Table (UDT) with the columns ItemCode, WareHouse, Quantity and Price.


Most of the client prepare excel sheet. So you can import data from excel sheet to UDT.



Step 2:


Now make two FMS.

               FMS 1:    For Quantity,


                                   SELECT Quantity FROM InventoryOB WHERE ItemCode=RTRIM(LTRIM($[$9.1.0]))



               FMS 2:    For Price,


                                  SELECT Price FROM InventoryOB WHERE ItemCode=RTRIM(LTRIM($[$9.1.0]))



              InventoryOB is the UDT.


Step 3:


Now set this FMS into Inventory Opening Balance Screen in Quantity and Price Columns.



We have to select    'When Field Changes'  option in Auto Refresh and assign any one field for refresh.







Thats all. It will take time for getting value. It depends upon  the number of items.



I hope this will help to our friends.




Thanks & Regards,


Just recently I’ve had a number of queries from partners regarding how to go about upgrading SAP Business One within a Cloud environment. In this context when I talk about Cloud I am specifically talking about the SAP Business One Cloud multi-tenant landscape, not a single SAP Business One system hosted on a cloud platform; in the latter case normal SAP Business One upgrade procedures would apply.


Before we go into the process of upgrading SAP Business One tenants (think of a tenant as a company database) it is worth providing some background on the SAP Business One Cloud landscape. The SAP Business One Cloud landscape contains a number of different server components to make it work, many of these play a “supporting” role, i.e. they are not running SAP Business One processes themselves rather providing the infrastructure to make the SAP Business One Cloud work. The main processing happens within Service Units, each service unit contains everything that is required and dedicated to a specific version (down to patch level) of SAP Business One:


  • Database Instance
  • Presentation Server(s)
  • SAP Business One Integration Framework (optional)
  • SAP Business One Mailer (optional)
  • Extensions (optional)

Each service unit is responsible for providing SAP Business One to multiple customers (the number will vary according to hardware, number of users and a number of other factors).


This configuration requires us to take a different approach to upgrading tenants within the SAP Business One Cloud landscape compared to company databases in an on-premise installation. The key difference in the approach is that we do not perform an upgrade directly on a database server that holds our SAP Business One tenants as we would do in on-premise SAP Business One. This approach would prove problematic in a cloud installation for a number of reasons:


  • From the moment we began an upgrade within a service unit the entire service unit would be offline (e.g. once we upgrade the SBO-COMMON database we can no longer login to a tenant that has not been upgraded to the higher version). In a service unit that houses, say, 100 tenants this could cause significant downtime for customers.
  • Upgrading a tenant can be a resource intensive process, in a multi-tenant environment where infrastructure is shared this has the potential to negatively impact customer experience.
  • If we did upgrade a whole service unit and there were 100 tenants in a service unit what would happen if we got to tenant 100 and it failed to upgrade when all the others were successful?


For these reasons and others the process of upgrading in SAP Business One Cloud involves two (or possibly three but more on that later) service units. The principle is this:


  • Service Unit 1 has 100 tenants running SAP Business One 9.0 PL10
  • Service Unit 2 is created for SAP Business One 9.0 PL11
  • Tenants (either individually or in batch) from Service Unit 1 are taken offline, backed up, restored to Service Unit 2 and upgraded to SAP Business One 9.0 PL11 where they are again available to the end user.


Of course this is a simplistic approach to upgrades as most partners go through a process of testing a new release before simply “pulling the trigger” on a live upgrade. SAP Business One Cloud provides functionality to assist with this as well as the upgrade process itself:


  • Pre-upgrade testing - All SAP Business One upgrades must pass pre-upgrade testing, this process can be carried out separately within the SAP Business One Cloud Cloud Control Center in preparation for the upgrade process itself.
  • Duplicate tenant - Similar to the upgrade process (if duplicating to a service unit that is tied to a higher SAP Business One version) with one key exception - the duplicate tenant is for testing, the original tenant in the source service unit remains live for users to carry on with live transactions. The duplicate tenant can then be tested for extension compatibility, key processes, data etc. before the live upgrade occurs.
  • Staging Service Units - I mentioned earlier that upgrading tenants can be a resource intensive process, by default this processing will occur in the destination service unit. If we are concerned about the effect on any tenants already in that destination service unit we can introduce a staging service unit. This temporary service unit receives the tenant to be upgraded, upgrades it (ensuring the resources required for processing are not provided by live service units) and then sends it to the destination service unit.
  • Service Unit Duplication - This process enables you to create a new service unit but automates some of the steps such as deploying the required extensions and moving presentation servers.


As you can see there is a lot of scope within these processes to define your own strategy for the lifecycle management of your SAP Business One Cloud customers. You do not have to follow a strategy of upgrading all of the tenants in one service unit in one go and instead could choose to stage the upgrade into smaller batches of tenants. And if you need to upgrade one tenant urgently for reasons related to a patch you can handle them individually rather than being forced into an unscheduled upgrade for your entire service unit.


So with the concept and functionality explained what is it that you should do in order to upgrade from one patch level of SAP Business One to another?


  1. Check note 1756002, to ensure that the version of SAP Business One that you are upgrading to is supported by the version of SAP Business One Cloud you are running.
  2. Before you begin the process of any upgrades within the SAP Business One Cloud landscape SAP recommends that you create snapshots so that you can roll back in case of any errors during the upgrade process.
  3. Register the version of SAP Business One you are upgrading to in the SAP Business One Cloud Software Repository.
  4. Upgrade the SAP Business One License Server to the latest version, this can be done within the SAP Business One Cloud Control Center (not every release of SAP Business One will require an upgrade to the license server but you will receive a message if that is the case)
  5. Create a new service unit
    • Database Instance - Another database instance needs to be configured and the SBO-COMMON database deployed via the SAP Business One Cloud Control Center.
    • Presentation Servers need to be assigned to the new service unit, the SAP Business One client is automatically deployed to them. ( Note: these can be unregistered and moved from the source service unit as the resource required in it begins to drop, e.g. in the case of staged upgrade process)
    • Deploy the required extensions in the new service unit (both SAP and third-party extensions in use)
    • If you are following our recommendation of using Security Groups to manage access by users to presentation servers you will need to separately configure them to allow the correct user access.
    • If using the SAP Business One Integration Framework and Mailer these will need to be manually deployed into the new service unit (it is also possible to unregister the existing ones in the source service unit, upgrade them manually and register them to the destination service unit however this would rely on the upgrade for all tenants taking place at one time.)
  6. Perform pre-upgrade tests on the tenants in the source service unit
  7. (Optionally) Perform test upgrades for tenants
  8. Upgrade the tenant to the new service unit, during the time of the upgrade the tenant will not be available to end users.


Once you have completed this process for all tenants all your users will now be logging in to the new service unit and you can power down the old one, reduce it’s resources, use it for testing the next release etc.


To help explain some of the concepts above and demonstrate the process I’ve also recorded the following video:


More information on the upgrade process and other administration steps can be found in the SAP Business One Cloud Administrators Guide, which can be found with the SAP Business One Cloud installations files.



About me:


I've been working at SAP with SAP Business One for the last 9 years in a variety of roles. Currently I look after SAP Business One Cloud and spend much of my time working with partners to help them take advantage of the new and exciting opportunities that have emerged since it's release. You can follow me on Twitter @joelaharris if you want to hear more!

The Preview Program offers SAP partners an opportunity to download a preview version of SAP Business One 9.1 (both on MS SQL and on SAP HANA) prior to the official Ramp-Up start. This new program is vital to the successful Ramp-Up of SAP Business One 9.1. Participating partners will have the opportunity to participate in the quality assurance process and provide SAP with feedback prior to Ramp-Up. This will give SAP time to address any software issues prior to final release.


See further information as well as the download links here:

SAP PartnerEdge (s-user required)

So you have your SAP Business One Cloud landscape set up and running smoothly, you're creating tenants quite happily and users are merrily going about their business. Then one day one of your users emails to ask, "How do I change my SAP Business One Cloud password?"


By default the SAP Business One Cloud portal doesn't have a change password option, thankfully though because it is based on the MS Remote Desktop Web application we can fix this fairly easily.


The following example assumes Windows Server 2008 R2 is being used, and is provided as-is and without any warranty of any kind. You should ensure you have a working backup of your configuration before attempting the below.


Step 1:


The reason the SAP Business One Cloud portal doesn't have a change password option by default is because neither does MS Remote Desktop Web, so the first thing we need to do is fix that. KB Article 2648402 contains the patch that we need to apply (can be found under the link "Hotfix Download Available" near the top of the page.


On the server that is running MS Remote Desktop Web and your SAP Business One Cloud User portal download the file, apply it and reboot the server. Once the server has restarted you need to enable the password change option in IIS, using Application Settings:




Step 2:


Now that we have a default page that will allow a user to change their password from the portal (you can check in %Windows%\Web\RDWeb\Pages\en-US for the newly created password.aspx file) we can link it into our SAP Business One Cloud User Portal. We will need to make a change to main.html, this is can be found in the SAP Business One Cloud Portal directory:

main html folder location.png


Open main.html and make the following changes to the file:


main html code.png


Here we are calling the newly added password page from the main window using a new button. This button is located with the welcome message for a user so will only be displayed to users that have been successfully logged on. Where you see the address https://dewdfwtec2546.b1cloud-wdf.corp.sap you need to replace this with the address of your own RDWeb directory. The result will be:




Now when you click the Change My Password link it will open the following page:




Step 3:

Now we have a working solution although the page that is opened doesn't fit with the look and feel of the SAP Business One Cloud User Portal. We can make some changes to make it look a little better. I'm sure that some of you will be able to take this one step further and make it look like a seamless part of the portal! Feel free to share with the community if you do!


I've attached the customised password.aspx page to this post so I won't go through all of the changes that I made to get the look and feel. The more important change is that we have got the application to pre-populate the User Name to include the full domain name in a read only field. RDWeb requires this full user name and don't forget that our users do not normally enter it for SAP Business One Cloud so it has the potential to confuse if not implemented this way.

The first snippet creates a variable that stores the current domain and user name:


The second changes the value of the string so that if the variable set above was DOMAIN\MYUSER it will now be DOMAIN\\MYUSER. The second '\' is required as when we access this in JavaScript the '\' is treated as an escape character on it's own:


This script gets the variable we have stored and manipulated on the server and adds it to the textbox that is collecting the Domain/User Name combination, in this case it is called 'DomainUserName'


To ensure the script above works we call it when the page loads, add it to the body tag as below:



And that's it, just a few simple steps to add functionality to change passwords through the SAP Business One Cloud User Portal.


Over the coming weeks and months I will be posting more content around SAP Business One Cloud, if you have anything that you would like me to cover please let me know!


About me:


I've been working at SAP with SAP Business One for the last 9 years in a variety of roles. Currently I look after SAP Business One Cloud and spend much of my time working with partners to help them take advantage of the new and exciting opportunities that have emerged since it's release. You can follow me on Twitter @joelaharris to make sure you hear the latest news!

1 Mind Map


Innovation Summit in Bratislava took place from the 26th of May - 28th of May 2014 and in the following I share my Mind Map as sort of summary of the event.


2 Details

2.1 SAP

Most important were the Demos of the new 9.1 release which really impressed me. Apart from that, SAPs Business One Mini Cloud / MCaaS approach seems to be worth looking at.

2.2 Implementation

The Summary of which of the different Reporting Tools to use in which scenario got my attention apart from fast Implementation Approaches (done by some VARs), HANA-related XApps and River as well as the known Sizing Tool from PartnerEdge. The session about KPI Designer were also interesting (Feature already included since 9.0 PL 9 but still evolving).

2.3 Maintenance

The RSP can be a great tool for VARs and is now available for B1H. In regard of the B1 Cloud, the Cloud Control Center is the comprehensive tool for Administration.

2.4 Cloud

During the Sessions on B1 Cloud Sizing and Configuration of Cloud Control Center were discussed as well as the so-called "Support User".

2.5 New Features (9.1)

In the Cockpit Area there are many new Features which you should definitively check out (especially for Demo-Cases). Apart from that Business-related new Features like working with multiple branches within one Company, Resources in Production or Optimization of the Sales Order Tabs were shown. Furthermore, Basic Functionality has evolved with Authorization Groups, the configurable UI (move fields etc.) and a powerful Excel Import and Export in the Grids. Technical Sessions discussed e. g. the new Service Layer and High Availability for HANA in context of B1H.

3 Miscellaneous

Thanks a lot to all the People who made this a great event!


Filter Blog

By author:
By date:
By tag: