If you’ve been involved in a Business ByDesign implementation or pre-sales process, in any way, then you have seen this:

 

Project Dimensions.jpg

 

It’s easy to gloss over this slide. After all, this is just one of 50+ in a ByD presentation, and you’ve only got an hour to get a huge amount of information across to your customer.

 

But when you get here, you need to pause. This is the most important slide in your presentation, and your customer needs and deserves to absorb this information. I will explain why in reverse order of importance of these three dimensions.

 

3. System Readiness

 

Why is this the least important of the three? Because the majority of responsibility for System Readiness falls on SAP and the project Service Advisors. These folks should have no problem configuring a customer’s system to match their processes, and enabling customer testing of these processes. If they can’t, you are working with the wrong partner.

 

2. Data Readiness

 

Your legacy systems (probably Quickbooks, Excel, and maybe Salesforce) contain a lot of data. You need this data in ByD for business continuity. Some of this data, however, may be of bad quality, inaccurate, or simply irrelevant. Because of these reasons, Data Readiness should be a high priority.

 

You need to start preparing your data for migration to ByD starting on the first day of the project. Do not underestimate the effort required to do this.

 

Assign someone to this task and have them work on it as soon as possible. SAP provides data migration templates that make the ByD side a breeze. But you must populate those templates with clean, valuable, and relevant data. If you don’t do this, your ByD system that will be a garbage pile which will require many, many hours of manual labor to pick through and clean.

 

In short, Data Readiness Is not a trivial part of the project, requires a lot effort to complete, and will lay the foundation for success in your ByD system from day 1.

 

1. People Readiness

 

Who runs your business? Androids? Mystical forces?  Autonomous machines from the future? No.

 

People run your business.

 

And those people will be using ByDesign every day. Some of them will embrace the new system, appreciating and an integrated solution where they can view one source of the truth, instead of four to six versions of the semi-truth that must be consistently reconciled.

 

But make no mistake; some people hate change. You must spend time with these people, demonstrating the benefit ByDesign will bring to their specific role. Show them what they will gain personally.

 

If they don’t realize the benefit, they won’t embrace the solution.

 

Remember that we are living in an era where there are hundreds, maybe thousands of cloud point solutions that your dissatisfied customer can buy on their own to complete their piece of your business process.

 

I’ve seen this happen many times. I’ve seen users abandon ByD CRM and go back to their Excel spreadsheets. I’ve also seen customers delighted with the product.  And I can assure you that ByD CRM is a better solution than Microsoft Excel. So why does abandonment happen?

 

It’s an easy answer: People Readiness. End users must fully understand how to execute their role in ByDesign. There is a wealth of information in ByD and the Business Center demonstrating user roles. Before you go live, everyone needs to go through this learning process and you must follow-up with them to ensure that have done so. It may seem like you’re nagging them, but your nagging will be rewarded with a satisfied, referenceable customer.

 

I even recommend spending some one-on-one time with end users, demonstrating their role in the system youself. This shows that you care about the user being ready for the transition and that you’re not just dumping a new system on them.

 

In the end, your business is about people. Make sure they feel empowered with the right set of tools to get the job done. And most importantly, teach them how to use those tools.

 

Note: I was recently in a very serious accident that left my right arm paralyzed, so please excuse any left-handed typing mistakes.

I am currently helping out on a customer project where the ByDesign customer wants to send out purchase orders to a supplier.

In this blog post I want to share what I found out during this project of how you can directly connect ByDesign and a third-party application.

 

I am far away from being an expert in B2B connectivity, nor am I a developer. Therefore please bear with me in case the following information is not complete. I'm happy to hear any corrections or additional information.

I know that a Connectivity Guide is in the works and once finished I will add a link to it here later.

 

Overview

The connection between ByDesign and a third-party system such as a supplier or a customer is primarily defined in the so called Communication Arrangement.

Communication Arrangements can be defined in ByDesign in the Application and User Management work center.

To be able to do that though you need some basic prerequisites.

 

Prerequisites

Business Configuration/Scoping

In the Business Configuration of your system you need to select the business documents that you want to send or receive electronically to or form your business partners.

SNAG-1274.png

Screenshot 1: Scoping of electronic exchange of Purchase Order and Purchase Order Acknowledgment

 

Unique identification numbers of business partners

You need to define unique identifiers to the outside for your business partner and your own company, such as a DUNS number or a Global Location Number

For your customers or suppliers you can define them in the master data:

SNAG-1275.png

Screenshot 2: DUNS number or Global Location Number in supplier master

 

In addition you need to define your identification number at the business partner there:

SNAG-1282.png

Screenshot 3: Customer ID at Supplier in supplier master

 

For your own company you have to edit your organizational structure in the Organizational Management work center:

SNAG-1276.png

Screenshot 4: DUNS number and Global Location Number in org structure

 

Communication Arrangement

Depending on the xml-format you want to share with your business partners there are different ways of how you can set up communication arrangements.

SAP ESD format

To use the SAP ESD xml format create a new communication arrangement from the Communication Arrangements view in the Application and User Management work center.

Select Purchase Order Integration (B2B).

On step two select the business partner (and your own company) that you want to connect to.

SNAG-1277.png

Screenshot 5: Business partner selection in communication arrangement

 

 

On step three of the guided activity define the host name you want to connect to or click Edit Advanced Settings to be able to even change things like the port number (default is 443). By default the authentification method is a client certificate but you can also change that to a username and password.

SNAG-1279.png

Screenshot 6: Technical data of communication arrangement for SAP ESD format

 

SOAP/Idoc format

In case you want to send your purchase order in an idoc format you can start your communication arrangement definition directly from a supplier master by clickint the Maintain XML Settings button in the Collaboration view. Make sure you select the right business document in the table before you click the button.

SNAG-1280.png

Screenshot 7: Where to maintain XML settings for Idoc xml files

 

Again maintain the technical data such as the host name in the communication arrangement

SNAG-1281.png

Screenshot 8: Technical data definition in communication arrangement

 

Output of business document

Once a communication arrangement has been defined you are finally able to see and select the XML entry as an Output Channel in the supplier master.

SNAG-1283.png

Screenshot 9: Output channel selection in supplier master

 

The next purchase order will automatically be sent via XML but you can always manually change the channel in each purchase order.

SNAG-1284.png

Screenshot 10: Success message about sent purchase order

 

Error Handling

In the Business Communication Monitoring view in the Application and User Management work center you can always have a look at the business communication messages you sent and received. In case something went wrong with a message you can see the error message and also have a look at the xml-file directly by clicking Show Payload.

SNAG-1286.png

Screenshot 10: Business Communication Monitoring view

 

Conclusion

Setting up a direct integration with a supplier or a customer is fairly easy in ByDesign. Even a non-developer like me can do that.

Nevertheless this can be a lot of work especialy if you have to communicate and coordinate with multiple business partners at once because nearly at each business partner a mapping between SAP ESD or Idoc and their own xml format needs to be done. This can take up to several weeks for each business partner. I therefore want to mention two more possibilities here:

  1. SAP also offers services for such an integration including the all new Information Interchange OnDemand solution. This solution already supports a mapping to a lot of business partner systems. You can find more information here: http://b2b.ondemand.com/
  2. SAP Business ByDesign partnered with Alligacom to offer our customers more choices to integrate via EDI. Alligacom is fully integrated with ByDesign and works out of the box. For more information check out the SAP Store here.

Filter Blog

By author:
By date:
By tag: