Saturday, June 27, 2015

Understanding what SAP solutions are provided to help manage your Supply Chain

SAP provides a myriad of solutions covering all aspects of the supply chain. In addition they often provide more than one solution to the same requirement. This makes it quite a challenge to choose the right solution for your scenario. With that being said I'd prefer to have more options to choose from than no option at all...
In this blog I have collected the current suite of Supply Chain solution offerings from SAP and grouped them in to 3 categories:
  • Most commonly used solutions
  • Less commonly used solutions
  • Solutions that cover Supply Chain processes as well as the rest of your ERP needs
At Q Data USA we specialize on these types of solutions so feel free to reach out to us with any questions.

Friday, June 26, 2015

Social is for Closers! New eBook on Social Marketing with Microsoft Dynamics CRM

In order to keep up with today’s social and mobile world, businesses need to move at a faster pace, connect to customers on their terms, and share knowledge more broadly than ever before. Microsoft Dynamics CRM comes loaded with out-of-the-box social tools designed to empower your sales, service, and marketing teams to deliver better customer experiences and grow customer satisfaction.

Thursday, June 25, 2015

Application Identifier on Bar Codes in SAP Business ByDesign

It appears that there have been a number of questions raised on the ByDesign forums related to the use of the mobile devices with existing SAP Business ByDesign form templates, and errors due to a lack of an “Application Identifier” when trying to scan barcodes.
The reason for this is that not all standard form templates for ByDesign are built with mobile devices in mind. Luckily, the fix to this is very straightforward. By default, most of the forms do not include the “Application Identifier” for the related fields. The “Application Identifier” is a numeric code that represents what type of data is being scanned.
Take the use-case in which the product ID is expected to be scanned. The associated application identifier is “91”. Note that this is a ByDesign-specific application identifier (it is one of the “90 – 99” custom fields referenced in the GS1 specification). Therefore, the mobile device will expect that any barcode that represents a product ID will start with a “91”. However, the XML data that is used to generate the forms will not necessarily have information in this format – in general, it would come over with just the regular value.
With the example of a product ID “SKU1234”, the product ID on the form template would still be “SKU1234”. However, if this product ID needs to be scanned, then the application identifier would need to come first – the barcode would actually need to contain the value “91SKU1234” to scan correctly, with the “91” representing the application identifier. We can make this adjustment through the addition of a simple script in Adobe LiveCycle Designer.

Wednesday, June 24, 2015

What GTIN would you use under this co-marketing scenario?

I saw this conversation on Linked In and felt that it was worthy to repost here for preserving...
Here’s the scenario:
A large multi-national manufactures and packages pharmaceutical finished goods. One presentation of these finished goods are sold in the US through a Partner (co-marketing arrangement). The Artwork and GTIN (NDC) of the product is that of the Partner. However the manufacturing authorization holder (MAH) is the large multi-national brand owner. With Serialization according to the DSCSA, should the GTIN remain that of the Partner? Or, would it need to revert to the MAH?
My belief is that it would not change – remain that of the Partner. Curious if you have come across this and if so, what approach you would take. 

SAP Business ByDesign Customization: 4 Real-Life Examples

When it comes to ERP systems, a strong and diligent selection process can really help you meet your business needs without the requirement for any customization. While SAP Business ByDesign is able to fulfill the majority of common business requirements, there will always be industry-specific or customer-specific requirements. For these requirements, SAP provides a combination of tools: both front-end based adaptation and extensibility as well as the Cloud Applications Studio can be used to develop solutions to bridge any out-of-the-box gaps.
In the blog series below, we’ll explore four examples of customer-specific SAP Business ByDesign solutions built by FMT Consultants. While the level of effort behind each of these enhancements varies, the business impact for even the simple solutions has been substantial – improving efficiency, automation, visibility, and data integrity. The solutions are ordered from least complex to most complex. The first two solutions can be built without the use of the SAP Cloud Applications studio. The second two solutions do require a small customization to be built in the SAP Cloud Applications Studio.

4 SAP Business ByDesign Customization Examples - by FMT Consultants:

  1. Application Identifier on Bar Codes
  2. Detailed Material Description
  3. Actual Freight on Customer Invoice
  4. Material-Specific Lead Time

Actual Freight on Customer Invoice in SAP Business ByDesign

We’ve often come across the requirement to invoice customers for only the actual freight price or cost incurred related to the outbound delivery. In the example we explore here, the “Freight Price” is an extension field that has been added to the outbound delivery. The value in the field is actually being sent to SAP Business ByDesign from an external system, but this functionality could also work with a value entered manually on the outbound delivery itself.
Note that this customization was only built for a single-currency environment, but it would be very easy to adjust to a multicurrency environment by changing the “Freight Price” field to an “Amount”-type field instead of a “Text” type field. In this scenario, the external system did not send data in an “Amount” type structure.
The external system would send back the actual amount value to populate the “Freight Price” field once the outbound delivery had been processed.

Tuesday, June 23, 2015

How to Handle Three Common Outbound Logistics Deviation Scenarios inSAP Business ByDesign

As many of us have experienced, transactions flow pretty smoothly through an ERP system until a deviation from the norm occurs. Deviations from normal processes can cause incorrect transactions, workarounds, or lost productivity when users do not have sufficient instructions on how to handle these. This blog will cover how to handle three common scenarios within Outbound Logistics in SAP Business ByDesign where deviations from the regular processes might occur.

Thursday, June 18, 2015

10 Tips for Reports and Data Sources in SAP Business ByDesign

Author: Dan Edelman, Senior SAP Business ByDesign Consultant at FMT Consultants
This blog is intended to provide some tips and tricks for creating custom reports or data sources in SAP Business ByDesign. It’s aimed at users that don’t have a reporting background, so if you’re used to building SQL-based reports, just bear with me. This isn’t an end-to-end guide from data source to report, but serves as a reference to use if you’re just getting started, or have gotten stuck trying to figure out how to do something.

Wednesday, June 17, 2015

Video: 5 Brilliant Ways to Customize SAP Business ByDesign (by FMT Consultants)

Like snowflakes, no two businesses are alike, and at times it’s necessary to customize your ERP solution to ensure it works exactly the way your business does.
In this video we’ll demonstrate 5 brilliant examples of how you can customize SAP Business ByDesign to ensure it accommodates your most unique and critical business needs.
Specifically, the video covers:
  1. How Development Works in SAP Business ByDesign
  2. Basic User Assistance – Sales Order Duplicate Check
  3. More Advanced Validation – External Reference Required for Release
  4. Store Custom Data – Approved Supplier List
  5. Upload Custom Data – File Input
  6. Automate Processes – Freight on Customer Invoice

Sunday, June 14, 2015

Enhancement Framework – Introduction

The ABAP Enhancement Implementation concept allows you to easily enhance the standard SAP delivered functionality with your desired one. The ABAP Enhancement Implementation concepts have been in SAP for quite some time now.

What is an Enhancement

An enhancement is used when you need to enhance any standard SAP delivered functionality by introducing new code. There are certain ways to achieve the enhancement:
  • Core Modification – You obtain the access key by registering the object with SAP and make the necessary changes. This is more dangerous and thus least preferable among other techniques. What makes it more dangerous is when SAP provides any OSS note, or during an upgrade, there is a chance of losing your changed functionality if you don’t perform the proper SPAU activity.
  • User Exit – You find SAP delivered Subroutines (PERFORM) which begins with USEREXIT_ in the standard SAP programs. To implement the user exit, you would need to also register the object through OSS. They are little bit safer from an upgrade point of view as they are in a separate include.
  • Customer Exit – You find SAP provided function exits with CALL CUSTOMER FUNCTION ‘001’. This would be a FM with an include. This include would not be delivered by SAP. If you need your new functionality, you need to create the include and implement your code. You would need to create Customer Enhancement Project in CMOD using the Enhancement which houses the Exit function SMOD.
  • BADI (Business Add Ins) – are based on the Object Oriented Concept. Std SAP provides you with the BADI calls. You would need to Create the BADI implementation based on the BADI definition. Then you can add your code in the implementation which is essentially a method in the class. You can implement the same BADI multiple times, if the BADI is set for multiple implementations.