Modeling an advanced Hierarchy with Directory in SAP Datasphere

In our previous blog, we covered the basics of creating a Hierarchy with Directory. Now, we're taking a step further in this blog by enhancing our model with an extra node type, language-dependent texts, and time-dependency, both for the hierarchies and node assignments. These advanced features are often seen in SAP S/4HANA or SAP BW hierarchies but are also applicable to non-SAP hierarchies. We continue to use a simplified data model with local data for clarity, making it easier to grasp these concepts before applying them to more complex, real-world data sources. The additions to the data model are pointed out in Figure 1, with the numbering corresponding to the section numbers in this blog post. The figure shows all views, and each view has a table with data underneath.

Modeling a basic Hierarchy with Directory in SAP Datasphere

In the previous blog, we provided an overview of the new features introduced with the Hierarchy with Directory. In this blog, we'll guide you through creating a basic Hierarchy with Directory, starting from scratch and progressing to the data preview in an Analytic Model. Our focus is on simplicity, ensuring you grasp the fundamental concepts with minimal complexity. To keep it simple, we use data from local tables, before moving on to data from SAP S/4HANA or SAP BW in future posts. However, the model is complete and comes with a few lines of transaction and master data. In our upcoming blog, we'll enhance the model by introducing advanced elements such as language-dependent texts, additional node types, and time-dependency features.

Field inventory management (FIM) in the Medical Device Industry – Create capitalized assets and fulfill demo requests orders from sales representatives

Introduction:

This blog outlines the leading medical device industry business process steps to fulfill a customer request for demo of a capitalized equipment.

A customer may request a particular product from your company to be demonstrated and evaluated before making a purchase decision. If the product is of high value, the company may treat the product as an asset when it is used for demo purposes. The below document will explain tracking, logistics support, and accountability of these products when they go out to the field from the company’s premises.

Converting Simple Date format to JSON date format with User Defined Functions (UDF)

As an SAP Integration Developer working with SAP S/4 HANA API’s with JSON Schema format, I encountered the necessity to adeptly convert simple date formats received from both SAP and non-SAP systems to JSON date format prior posting the payload to SAP S/4 HANA for required operations.

In this case, if payload posted to S/4 HANA consists of simple date format (DD/MM/YYYY), it reverts with date-related errors that arise due to unrecognized formats by the system.

To address this issue, I couldn’t find an existing guide, prompting me to share my approach with fellow Integration Consultants.

SAP S/4HANA Business Partner – Address Management at Contact Persons

Introduction

With introduction of Business Partner at SAP S/4HANA and CVI (Customer-Vendor-Integration) an additional object level in addition to old/known Customer and Contact Person concept has been implemented.

Customer Master and Contact Person is using BAS (Business Address Service) for many years by using central address tables. Business Partner is using BAS as well with own address data sets. This makes whole address management complex.

An Introduction to Hierarchy with Directory in SAP Datasphere

SAP Datasphere has rolled out a much-anticipated feature set with the Hierarchy with Directory. This feature set extends beyond directory capabilities, which we will explore in detail, to a host of other functionalities engineered to integrate smoothly with SAP S/4HANA and SAP BW hierarchies. The outcome is a more efficient experience in modeling these hierarchies within SAP Datasphere, with a richer end-user experience.

This blog post kicks off a series dedicated to unpacking the Hierarchy with Directory bit by bit. We begin with an overview of the new features. Following that, we’ll detail the functionality across two posts, starting with constructing a simple data model to represent a product, and then expanding the hierarchy with additional capabilities. This approach ensures you gain a thorough grasp of the hierarchy features, setting the stage for in-depth guides on integrating specific S/4HANA hierarchies such as GL Account, Cost Center, and Profit Center. A screenshot of the end-result of a GL Account Hierarchy is illustrated in Figure 1.

Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA

Introduction:

This blog outlines the leading industry business process steps to deliver critical medical instruments and consumables for surgery at the hospital promptly providing tracking and visibility to all stakeholders.

When the Sales Rep is notified of surgery, a list of assets like medical Instrumentation Loaner Kits and implants/disposables needed for a particular surgery event is determined. This material then must be tracked, and delivered to the hospital or location where the surgery event takes place. After the Surgery event, the Instrumentation loaner kit is returned to the plant where the inspection is carried out. The consumed items are billed to the Customer through the invoicing process.

Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline

For AMEX acquirer the requirement is to update the assignment field of the accounting document with the unique payment id (Merch ID) that will be sent through in the note to payee of the EBS while processing the FEBAN. This will update the SB document type assignment field with the unique payment id.

Blackline is also expected to update the SA document type assignment field for matching transaction. This will help in auto clearing of such open items.

Following are examples of note to payee wherein the highlighted information is the “Unique” payment id received from the acquirer

HANA Prod tables access in Dev for CV nodes data preview

SAP HANA XS Advanced application developments are done using Web IDE for HANA and it is installed in Dev instance and not in QA/prod instance. It is because we don’t want any changes directly deployed in Prod. In that case, we can’t troubleshoot the CV nodes data preview in Prod.

So we can configure the process below to access Dev and Prod tables interchangeably when required.

Azure Monitor for SAP solutions One-stop-shop for SAP technical monitoring

Are you an SAP Customer/Partner/ISV seeking a seamless monitoring solution? In this blog, I introduce Microsoft’s latest Monitoring solution—Azure Monitor for SAP Solutions—a user-friendly and plug-and-play tool.

1. What is Azure Monitor for SAP Solutions?
2. What is the architecture?
3. What can you monitor?
4. What are the other key capabilities of AMS?
5. What are pricing and regions available?

S/4Hana 2023 – Key User Extensibility – Custom Logic App – Keep the Core Clean

With S/4hana 2023 SAP introduce another fiori application which can help key users to implement BADI’s that have been released by SAP. We can start implementing from the Custom Logic app or from the UI adaptation in an application that can be extended.

BADI’s Extension can be created by using the application and we will also have the flexibilities to view the latest documents, Develop extension where we can also refer sample code, Test the code and compare the code as well. This app can play a major role to keep the core clean.