segunda-feira, 21 de janeiro de 2019

SAP S/4HANA Landscape Scoping Webcast Recap

This was another session hosted by SAP Support

Source: SAP
Landscaping guidance related to S/4HANA

Source: SAP
Learning objectives are shown above

Source: SAP
Agenda is above; tutorial will be available later this year

Source: SAP
Landscape before and after

Source: SAP
Discovery phase
Which train (on-premise or cloud)
Key elements of discovery phase shown above

Source: SAP
Why move to S/4HANA?  Drivers are shown above

Source: SAP
Assess business/IT current situation.  Where is the ask for more innovation?  Cloud readiness?
Starting an exercise by function the better

Source: SAP
Landscape complexity; where are you in this grid?  Simplify the landscape, consolidate, harmonize

Source: SAP
Sample consolidation template
What is the business value? That should be the driver
Is it doable?

Source: SAP
May not be able to consolidate / harmonize in one “go”.
Single instance may not be target architecture; may have regional instances

Source: SAP
Next step is to document current system, the characteristics

Source: SAP
“Typical” transformation steps
Cloud solutions; can stay on current on-premise solutions
Look at it by business function

Source: SAP
Differentiate how your run your supply chain; may want to extend solution.  Buy vs build, consider SAP Cloud Platform

Source: SAP
R&D is connected to core
Above is a sample
More functions in the core allow for tighter, real time integration
Integration scenarios often slow down the innovation pace

Source: SAP
Integration complexity is shown above
S/4HANA allows more back in the “core” – transportation management, etc.
Look at the digital core architecture
“Best of breed” may be more inflexible
Data warehouse does not take away the need for other integration solutions
Data warehouse helps with IoT solutions, help recognize real time patterns



Source: SAP
SAP classical finance, GL, material valuation, have successors in S/4HANA
CIC is deprecated; use cloud solution
Classic WM can be run in compatibility mode
Use MDG to clean data
Embedded analytics using CDS is the go-forward solution from HANA Live
Check with your vendor for 3rd party add-ons
Industry solutions are generally embedded in S/4HANA

Source: SAP
Key takeaways are shown above
Source: SAP

Source: SAP
Output from transformation landscoping session
Listen to the other MTEs https://support.sap.com/esacademy and enter the search tag “SAP S/4HANA Discovery”.
This was a lot to digest.  What do you think?

Updates from SAP:


#1  Please note that for customers, to access the SAP Learning Hub, edition for SAP Enterprise Support, a one-time registration is required. A detailed step-by step guidance can be found here. The MTE links below  will not work if the customer has not registered.
#2 Please note that only Enterprise Support customers are eligible to listen MTE recorded sessions

MTE (Meet-The-Expert) live sessions open for registration
SAP S/4HANA The Essentials Thus, Sep 20, 10:00 AM Eastern Time/New York
MTE (Meet-The-Expert) existing recorded sessions
SAP S/4HANA Discovery – Greenfield vs. Conversion Overview  delivered on Aug 21st
SAP S/4HANA Discovery – Transition Paths and Best Practices   delivered on Aug 23rd
SAP S/4HANA Discovery – Landscape Scoping  delivered on Aug 31st
SAP S/4HANA Project and Ongoing Effort   delivered on Aug 28th
SAP Readiness Check for SAP S/4HANA  delivered on July 24th
Build Your Product Roadmap – SAP Transformation Navigator delivered on Aug 8th
Build high-level benefits case with SAP Quick Value Assessment  delivered on Aug 9th
Source: SAP


Source: https://blogs.sap.com/2018/08/31/sap-s4hana-landscape-scoping-webcast-recap/
Postado por às Nenhum comentário:

quinta-feira, 17 de janeiro de 2019

Extension Ledgers in S/4 HANA

Hello All,
Will try to explain the concept of Extension ledger in comparision to standard ledger with my recent experiences of projects.
Extension ledgers are one of the powerful options that can be used for Management reporting. These ledgers staple the data on top of Standard ledgers,hence no data duplications as number of extension ledgers can point to 1 Standard ledger.There are 2 types of ledgers in SAP S/4 HANA:
  1. Standard Ledgers
  2. Extension Ledgers

Comparision of Standard Ledger and Extension Ledger:
                  Standard Ledger                 Extension Ledger
This is an independent ledger and standard ledger is an underlying ledger.The underlying ledger is a standard ledger.
Postings made to standard ledgers will only be reflected in standard ledger.Postings made to standard ledger will form part of reports of extension ledgers linked to standard ledger.
Total Balance = Balance in Standard LedgerTotal Balance = Balance in Standard Ledger +
Balance in Extension Ledger
Postings can be specifically made in standard ledgerPostings can be specifically made in extension ledger
If you are on Classic GL and migrate to S/4 HANA, you cannot activate standard ledgers on day 1 (Subsequent activation of standard ledger is possible though)Extension Ledgers can be activated in S/4 HANA even if you were on classic GL in ECC.
Many Standard ledgers can be created to reportingMany Extension ledgers can be added on top of Standard ledger. (N:1 is possible)

When Extension ledgers can be activated?
  1. This can be activated in S/4 HANA.
  2. Unlike standard ledgers, Extension ledgers can be activated in S/4 HANA even if you were not on New-GL and not used Ledgers in ECC.
  3. Extension ledgers are non-disruptive, hence can be actived at any period of time.
Where is the data of Extension ledger stored?
  • It is stored in ACDOCA table only.
  • Postings made to standard ledger are not stored in extenstion ledger specifically.(below example will help you in better understanding)
Example: You have your standard ledger as 0L and Extension ledger as ZX .
  1. If you post a document to 0L. ACDOCA will be updated with ledger posting to 0L only, However when you try to extract reports like FAGLL03  for ledger ZX, all the postings of 0L+ZX will be calculated for balances.
  2. If you post a document to ZX. ACDOCA will be updated with ledger posting to ZX only,hence influencing the balances of ledger ZX.
Config: The setup of extension ledger is very simple.




I will try to update this blog with use cases for extension ledger. Happy to get some suggestions and use cases in comments.

Thanks
Praful Jain.


Source: https://blogs.sap.com/2019/01/15/extension-ledgers-in-s4-hana/
Postado por às Nenhum comentário:

Six Steps to Deploy SAP S/4HANA Cloud with SAP Activate

Happy New Year to all of our customers, partners and colleagues.
In this post I want to share an update about the recently recorded demo videos providing overview of the key capabilities in SAP Activate powered by SAP Cloud ALM application of Implementation Portal. It shows how the combination of prescriptive guidance, rich business process content and powerful tools work together to guide customers in deployment of SAP S/4HANA Cloud.
Few notes before we dive into the details:
  • The demo is showing example on one scope item (J60 – Finance: Account Payable) for simplicity. In real deployment project customer project team would execute these steps on number of scope items and backlog items that reflect the scope of their project.
  • Demo refers to different personas like Project Lead, Configurator, etc. to distinguish between the different roles participating in the project.
  • The videos are shortened to provide an overview of the key capabilities, they are not intended to be full click-though and show of all the tool capabilities.
The demo script follows closely the phases of SAP Activate and focuses on key steps in the deployment of SAP S/4HANA Cloud. The overview videoprovides introduction into the demo that then follows the six steps shown in the image below.
Now let’s briefly discuss the key activities that are shown in each of the six steps:
(Step 1) Setup and Enablement – this demo shows the steps project lead takes to setup the project, define key milestones, set the initial project scope and invite the team members into the project using Implementation Portal for SAP S/4HANA Cloud (that is part of SAP Cloud ALM).
(Step 2) Fit-to-Standard Analysis – in this video you will see how the configuration expert (or alternatively business process expert) sets the detailed scope for specific business area and company by selecting scope items to be in/out of scope for the deployment project. The demo then continues with the explanation of capabilities for reviewing the rich business process content, including displaying the business process models and documentation of the pre-delivered business processes. At the end of the demo, the team captures a requirement into the backlog using the “notes” functionality in the Implementation Portal.
While the demo shows this process in a straight sequence, in reality the project teams will iterate on various scope items and will refine the scope based on the results of the fit-to-standard workshop. Proper execution of fit-to-standard workshops is critical for projects to finalize the business scope, define the configuration values, define the scope of integrations, define output management and analytics needs and more. I do recommend you to take a look at the fit-to-standard guide accelerator we provide in SAP Activate that guides you through all the steps in detail.
(Step 3) System Provisioning – in this step, the team takes the results of the fit-to-standard workshops to set the scope for provisioning, maintain key values like chart of accounts and then trigged the Q-system provisioning process. The Q-system is provisioned with customer specific scope activated and the team can start configuration activities.
(Step 4) Configuration – in this step the project team takes the backlog and uses iterative agile approach to configure the solution. The demo shows how the backlog item gets implemented into a configuration in the system. It shows the configuration expert navigating to the Manage Your SolutionApp and then using Self-Service Configuration UIs to record the desired configuration values in the Q-system.
(Step 5) Testing – in this step the configuration expert runs the pre-delivered test script with appropriate values to confirm that the configuration in the system works as desired. The pre-delivered test scripts are useful not only during the initial configuration, but also and more importantly play critical role during the regression testing after each release upgrade. SAP S/4HANA Cloud comes pre-delivered with test scripts covering the scope of the solution, which is a significant saving of effort and cost.
(Step 6) Data Migration – the last demo shows the activities project team executes to load data into the new system. The data load tool simulates the load into the system, user can check the results, make adjustments if needed, and then complete the load activities. This process is tested in Q-system and then repeated in the production environment prior to the production cutover.
I hope that this blog provides you with better understanding of the available capabilities in SAP Activate and show you how SAP Cloud ALM supports the project team in execution of the project following the SAP Activate guidance.
If you have questions or want to engage with the SAP Activate team, please post your comment either directly on this blog post or join us in the SAP Activate Jam Group where you can find more information about SAP Activate.
Reference links
To save you time, in case you wanted to keep list of these videos, below are direct links to each step of the demo:


Source: https://blogs.sap.com/2019/01/10/six-steps-to-deploy-sap-s4hana-cloud-with-sap-activate/
Postado por às Nenhum comentário:

quarta-feira, 16 de janeiro de 2019

S/4HANA Embedded PP/DS: Shift Maintenance in Monitor Capacity Fiori App.

SAP S/4HANA offers the new Embedded PP/DS, which brings the SAP APO capabilities into the SAP ERP core. Embedded PP/DS brings many advantages, such as the simplified master data maintenance, simplified integration and planning PP/DS materials in MRP Live. The major innovation, however, is related to the user interface. Two new fiori apps were introduced in S/4HANA, one for capacity monitoring and another for capacity leveling.
The new fiori app Monitor Capacity Utilization provides an overview of the capacity load in the resources assigned to the area of responsibility and also a detailed capacity overview of a selected resource, including charts and additional details of the capacity load. As of SAP S/4HANA 1709, this Fiori App also includes the possibility of shift maintenance, in order to resolve capacity bottlenecks.
I have recently recorded two demos explaining the basic usage of this Fiori App and how can it be used to maintain shifts and change the orders allocating capacity to the resource.
The first video shows the Fiori App initial screen, explaining how to navigate, use filters, add columns and other basic features.


The second video shows the details of a specific resource, the different options of charts, how to maintain a shift and how to change an order using this Fiori App, in order to avoid a capacity overload.


This Fiori app is available with the profile SAP_BR_PRODN_PLNR (Monitor Capacity Utilization, Production Scheduling Board). The activation of Advanced Planning in customizing is a pre-requisite and only resourced marked for Advanced Planning can be selected.
In addition, only production resources are supported and shift maintenance is supported only for capacities of type external capacity.

The following SAP notes provide technical information about the S/4HANA Embedded PP/DS apps:
  • 2489383 – Release Information Note: Monitor Capacity Utilization app, Production Scheduling Board app on SAP Fiori for SAP S/4HANA 1709
  • 2353836 – Release Information Note: Monitor Capacity Utilization app, Production Scheduling Board app on SAP FIORI FOR SAP S/4HANA 1610, R
  • 2674523 – Release Information Note: Monitor Capacity Utilization app, Production Scheduling Board app on SAP Fiori for SAP S/4HANA 1809

More details about this Fiori App can also be found in the fiori Library, in the link below:
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps(‘F1523’)/S12OP
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps(‘F2900’)/S12OP


Source: https://blogs.sap.com/2019/01/15/s4hana-embedded-ppds-shift-maintenance-in-monitor-capacity-fiori-app./
Postado por às Nenhum comentário:

Fiori Lighthouse Scenarios in SAP S/4HANA Cloud and SAP S/4HANA

Latest Update 16th January 2018: The Fiori Lighthouse Scenarios deck has now been updated for S/4HANA 1809 and S/4HANA Cloud 1811.  You can use these to highlight the latest user experiences available to your business stakeholders including CoPilot and Machine Learning.
You can also look at our UX for S/4HANA Bootcamp Fiori Lighthouse Scenarios video (10 minutes) that shows how you can use this on your S/4HANA project.
Latest Update 31st October 2018: We are currently working on updates for 1809 and 1811. You can also find the Fiori Lighthouse scenarios deck on the home page of the Fiori Apps Library.  Stay tuned. 
Latest Update: We have added a few Industry Retail scenarios to the deck. Enjoy!
In the S/4HANA Regional Implementation Group we are privileged to work with many customers on the leading edge of SAP S/4HANA implementations. Some of the questions we hear again and again from SAP S/4HANA Cloud and SAP S/4HANA customers are:
  • Which SAP Fiori apps do you recommend we use to help drive our digital business transformation forward?
  • Which SAP Fiori apps are the quick wins to help us introduce digital transformation to our business people?
  • What are the best SAP Fiori apps for our business role(s)? That will help us drive innovation and bring immediate value to our people.
  • How can we use SAP Fiori apps to drive meaningful change?
Because when you are a leading-edge company, being the best means making a difference. And using only classic applications, such as SAPGUI, the same as you did a decade ago just cannot bring the change you need.
So with the generous collaboration of our S/4HANA business role owners and product owners, UX product management and with many recommendations from all of the SAP S/4HANA Regional Implementation Groups based on our experiences with leading edge SAP S/4HANA and sAP S/4HANA Cloud customers around the world, we created a document to highlight selected SAP Fiori scenarios to get you started on your journey into SAP Fiori for SAP S/4HANA or SAP S/4HANA Cloud.

Introducing recommended lighthouse SAP Fiori scenarios

Fiori lighthouse scenarios lighthouse icon
You will find in the document a collection of lighthouse SAP Fiori scenarios per business role complete with screenshots and major benefits. The sort of presentation you can use to win over your project sponsor and business stakeholders.
What are lighthouse SAP Fiori scenarios? These are scenarios enabled by SAP Fiori apps that we recommend as great starting points for customers implementing SAP S/4HANA Cloud and SAP S/4HANA.  Each scenario offers immediate business benefits to S/4HANA business users over and above related older SAPGUI transactions in SAP Business Suite.  And naturally you will also find several innovation scenarios that simply were not available in SAP Business Suite.
You will find in the collection:
  • SAP Fiori apps that offer a delightful user experience
    • Apps that bring business users immediate business value, supporting and encouraging them as they adapt to new digital transformation priorities
  • SAP Fiori apps that support tasks and processes that were not supported before (in SAP Business Suite)
  • SAP Fiori apps that simplify work and increase the efficiency of tasks and processes
You should look at this as expanding on the more generic advice given so far in blogs such as Leading SAP S/4HANA UX Selecting SAP Fiori apps , where you find suggestions on how to align your app selection to your digital transformation goals, and an explanation of why the business role is the best default granularity for selecting apps.
You can use this collection alongside the SAP Fiori apps reference Library Recommendations report. The recommendations report gives you a quick first cut of business roles and apps that are likely to be relevant to your business based on your usage of your existing SAP Business Suite (assuming you have one). While the lighthouse SAP Fiori scenarios will give you some additional suggestions for first innovation targets for those same business roles.

Using the Fiori Lighthouse Scenarios on your S/4HANA Project

You can also find a 10 minute Fiori Lighthouse Scenarios video that shows how you can use this on your SAP S/4HANA Project.
This is part of our UX for S/4HANA Virtual Bootcamp series.

What’s included and why

Many of the business roles and SAP Fiori apps chosen are an integral part of new innovations in business processes such as:
Now with 140 business roles available in SAP S/4HANA 1709 alone, don’t worry! You won’t have to read through every business role.  Instead you will find the collection is focused on common business roles that are core to many businesses, including yours.
You will find most of the business roles you expect, such as Cash Manager, General Ledger Accountant, Internal Sales Representative, Strategic Buyer, Master Data Steward, Budget Specialist, Production Planner, Maintenance Technician, Shipping Specialist, Warehouse Operative, Industrial Hygienist, and Project Steering Committee Member.
You will even find some industry roles such as Billing Specialist (Utilities) and Transportation Scheduler (Industrial Oil and Gas).
And a few business roles you might not expect. Including 2 of the 3 business roles we always recommend for every SAP S/4HANA customer – Administrator, Business Process Specialist, and Analytics Specialist. Why these 3 roles? They contain the apps that help you adapt other SAP Fiori apps to your specific business needs, such as:
  • Manage Workflows app – flexibly adjust when workflows start, what tasks are involved, and who they are sent to
  • Custom Fields and Logic app – rapidly add extra fields and logic specific to your business need
  • KPI Workspace app – configure thresholds, targets, and timelines of KPI tiles and drill down analytics
Similarly with already over 840 SAP Fiori apps in SAP S/4HANA Cloud and over 960 SAP Fiori apps in SAP S/4HANA you will find a condensed and careful selection of just the best of the best starting points.
There are many quick win out-of-the-box apps you will have heard of in previous use case series such as:
Screenshot of Project Profitability Overview Page app
Tip: Why do we particularly highlight so many embedded analytics including so many Overview Pages? If you are moving to SAP S/4HANA from an existing SAP Business Suite, often you will have some business users with deep expertise in their SAPGUI transactions.  It can be difficult to convince these business users to change to simpler app versions.  For these same business users often the burden of running traditional reports is a significant pain point. So the immediate value add of SAP S/4HANA for these experts users is not in transactional apps, but instead in embedded analytics apps that bring better, clearer, and importantly real-time insights. Knowing what to focus on today – as soon as you login to your Home Page – that’s an advantage! 
And you might find some apps are new to you such as:
Screenshot of Pick by Cart app
Every app recommended includes a link directly to the full details of the app in the SAP Fiori apps reference Library. Just look for the pointing hand icon.
Pointing hand icon
We are using these lighthouse scenarios now in our discussions with SAP S/4HANA customers, and you can also download the SAP Fiori Lighthouse apps collection for yourself.
Our intention is to update this list from time to time.  We would value your feedback in the blog comments on how we can make this even more relevant to you.  And if you have any apps that you are using with your SAP S/4HANA solution that you would recommend adding to the lists, we would love to hear about those too.

Where to from here

We aren’t stopping here. We are working on more S/4HANA Experience Transformation videos that show old (SAP Business Suite) vs. new (SAP S/4HANA Cloud & SAP S/4HANA) ways of working, such as Experience Transformation – S/4HANA Sales Order Fulfillment
You’ll also notice we have quietly been working on more content in the Fiori Apps reference library to explain how each app forms part of the holistic solution capability, and even to show you a brief demo of the app in action. Just look for the App demo links in the Product Features tab
Screenshot of Budget Overview app in the Fiori Apps reference library showing App demo links on the Product Features tab

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on our SAP Fiori for SAP S/4HANA wiki
Brought to you by the S/4HANA RIG


Source: https://blogs.sap.com/2018/01/21/fiori-lighthouse-scenarios-in-sap-s4hana-cloud-and-sap-s4hana/
Postado por às Nenhum comentário:

terça-feira, 15 de janeiro de 2019

Add Machine Learning capabilities in SAP Fiori App with Google ML Kit Custom Model

We are going to build an Android Fiori App with SAP Web IDE to identify objects in images using Google ML Kit Custom Model. With the custom model, you can train your own ML model to recognize the objects according to your needs.

Pre-requisities

Follow my earlier blog to setup the local HAT with SAP Web IDE Full Stack and install the required cordova plugins:
  • cordova-plugin-mlhttps://bitbucket.org/bhivedevs/cordova-plugin-ml-text.git
  • cordova -plugin-firebasehttps://www.npmjs.com/package/cordova-plugin-firebase
  • cordova-plugin-camera-previewhttps://www.npmjs.com/package/cordova-plugin-camera-preview
We will modify the cordova-plugin-ml and add some Java codes later on.
Don’t forget to setup the Firebase console project, download the google-services.json file and add into C:\Users\<user>\SAPHybrid\Scanner\hybrid\platforms\android\
In this tutorial, we will just use the existing ML model from Google codelabs.

Modify build.gradle 

Open build.gradle and add aaptOptions and the required dependencies:
dependencies {
    implementation fileTree(dir: 'libs', include: '*.jar')
    // SUB-PROJECT DEPENDENCIES START
    implementation(project(path: "CordovaLib"))
    compile "com.google.android.gms:play-services-tagmanager:+"
    compile "com.google.firebase:firebase-core:+"
    compile "com.google.firebase:firebase-messaging:+"
    compile "com.google.firebase:firebase-config:+"
    compile "com.google.firebase:firebase-perf:+"
    compile "com.google.firebase:firebase-ml-vision:18.0.2"
    compile "com.android.support:exifinterface:$ANDROID_SUPPORT_LIBRARY_VERSION"
    implementation 'com.google.firebase:firebase-ml-model-interpreter:16.2.4'
    // SUB-PROJECT DEPENDENCIES END
}

And sync the project.

Adding TensorFlow Lite Model to Project Asset Folder

We are going to use the existing model from TensorFlow. We can build our own custom model, you may refer to this tutorial how to do it.
We we will use the local version of the model for offline scenario.
Download the TF Lite model from here and extract.
Get the mobilenet_v1_1.0_224_quant.tflite.

For label, we need to get the label.txt from here.
Extract the code and get the label.txt from \mlkit-android-master\final\app\src\main\assets\

Now we have two files: mobilenet_v1_1.0_224_quant.tflite and label.txt.
Upload these files to the asset folder Android project.

Modify cordova-plugin-ml

Open MLtext.java from this location:

Update the code with Mltext.java.

Call the Plugin

How to call this plugin? it is very easy, just call takePicture() JavaScript method from SAPUI5 XML view and get the result from recognizedText.blocktext.
takePicture: function() {
    CameraPreview.takePicture({
        quality: 100
    }, function(imgData) {

      mltext.getText(onSuccessText, onFailText, {
            imgType: 4,
            imgSrc: imgData
        });

        function onSuccessText(recognizedText) {
            console.log(recognizedText);
            alert("Text: " + recognizedText.blocktext);
        }

        function onFailText(message) {
            alert('Failed because: ' + message);
        }
    });
},
Now everything is setup, you can build the project and install the .APK onto you Android phone.
A complete source code can be found on my Git.
Thanks for reading and let me know if there is any question.


Source: https://blogs.sap.com/2019/01/11/add-machine-learning-capabilities-in-sap-fiori-app-with-google-ml-kit-custom-model/?source=social-Global-SAP+Developers-LINKEDIN_COMPANY-AudienceEngagement-Developers-Fiori&campaigncode=CRM-XB19-MKT-DGEALL
Postado por às Nenhum comentário:

Data Masking for the SAP HANA Service – by the SAP HANA Academy

Introduction

Data masking provides an additional layer of object-level access control, for example to complement SELECT privileges. Regular object-level access control privileges return either a result set or an error: insufficient privileges. With data masking, a result set is always returned. However, unless the user has the UNMASKED object-level privilege, the data will be hidden as defined by the mask.
Different implementations are possible. Below a simple example.
For an introduction of the data masking feature, see the blogs from Aleks Aleksic:


Tutorial Video

In the video tutorial below, we demonstrate how to implement data masking.

Data Masking for the SAP Cloud Platform, SAP HANA Service works the same as for a regular on-premise SAP HANA versions, like the platform and express edition.
Data masking was introduced with SAP HANA 2.0 SPS 01 (April, 2017) and is not available for the SAP HANA Service in the Neo environment, currently on version SAP HANA 1.0 SPS 12.

Code Sample

For the full code sample, see the repository on the SAP HANA Academy GitHub site. Below the most essential parts. This is a sample implementation. Other approaches are possible.
Here we create a function which will perform the actual masking when called.
CONNECT mask_owner PASSWORD ******
CREATE FUNCTION credit_mask(INPUT VARCHAR(19))
RETURNS OUTPUT VARCHAR(19) LANGUAGE SQLSCRIPT AS
temp VARCHAR(19);
BEGIN
SELECT LEFT(INPUT,4) || '-XXXX-XXXX-' || RIGHT(INPUT,4) 
  INTO temp
  FROM SYS.DUMMY;
OUTPUT := temp;
END;

GRANT EXECUTE ON credit_mask TO data_owner;
Next, as the object owner of the table with sensitive data, we create a view which calls the mask.
CONNECT data_owner PASSWORD ******
CREATE VIEW credit_view AS 
  SELECT * FROM credit_tab
  WITH MASK 
    (CREDIT_CARD USING mask_owner.credit_mask(credit_card));

GRANT SELECT ON credit_view TO end_user;
Finally, as end_user we query the view and get a result set with masked data for the credit card column.

Granting the UNMASKED object privilege to the user returns an unmasked view on the data.
CONNECT data_owner PASSWORD ****
GRANT UNMASKED ON credit_view TO end_user;

YouTube Playlist(s)

The tutorials has been posted to the following playlists:

References

For the GitHub code repository, see
For the documentation, see

Thank you for watching

The SAP HANA Academy provides free online video tutorials for the developers, consultants, partners and customers of SAP HANA.
Topics range from practical how-to instructions on administration, data loading and modeling, and integration with other SAP solutions, to more conceptual projects to help build out new solutions using mobile applications or predictive analysis.
For the full library, see SAP HANA Academy Library – by the SAP HANA Academy.
For the full list of blogs, see Blog Posts – by the SAP HANA Academy.
Source: https://blogs.sap.com/2019/01/14/data-masking-for-the-sap-hana-service-by-the-sap-hana-academy/
Postado por às Nenhum comentário:

sexta-feira, 11 de janeiro de 2019

ACR Brazil Option (TDF): Relacionamento entre registros do Bloco B do EFD ICMS IPI

Olá pessoal,
Hoje vamos falar sobre o relacionamento entre os novos registros do Bloco B do relatório EFD ICMS IPI, entregues a partir das SAP Notes 2713794 and 2724367.
Essa mudança traz informações referente a apuração do Imposto Sobre Serviço de Qualquer Natureza (ISS), com base no Leiaute 13 do EFD ICMS IPI.
  • Registros B001 e B990:
Os registros B001 e B990, que são a abertura e o fechamento do Bloco B, atuam normalmente como qualquer outro registro de abertura e fechamento de bloco.
  • Registros B020 e B025:
O registro B020 reporta as notas fiscais de modelos 01, 03, 3B, 04, 08, 55 e 65 referentes ao ISS e alimenta demais registros totalizadores desse bloco. O registro B025 é responsável pelo detalhamento dos valores das notas fiscais do B020 por alíquota e item.
  • Registros B030, B035 e B350:
Os registros B030 e B035 são responsáveis pelas notas fiscais de serviço simplificadas e seu detalhamento por alíquota e item. O preenchimento desses dois registros é feito através da tabela Shadow /TMF/D_NFS_SIMPL.
O registro B350 reporta serviços prestados por instituições financeiras cujo preenchimento é feito através da tabela Shadow /TMF/D_NFS_FIN.
  • Registros B420 e B440:
O registro B420 totaliza os valores dos serviços prestados a partir do consumo de dados dos registros B025, B035 e B350 que são reportados no período de apuração (conforme a imagem abaixo):
B420:
O registro B440 totaliza os valores retidos referentes à prestação de serviço a partir do consumo de dados dos registros B020 reportados no período de apuração.
  • Registros B460, B500 e B510:
O registro B460 reporta as deduções do ISS cujo preenchimento é feito através da tabela Shadow /TMF/D_NFS_DEDU.
O registro B500 reporta a apuração do ISS Sociedade Uniprofissional e é preenchido através da tabela Shadow /TMF/D_NFS_UNIP. Já o B510 reporta os empregados e sócios dessa sociedade, e é preenchido através da tabela Shadow /TMF/D_NFS_UFUNC.
  • Registro B470:
O registro B470 totaliza os valores de ISS referente às prestações de serviço a partir do consumo de dados e do cálculo dos campos de valor dos seguintes registros: B020, B420, B440, B460 e B500 (conforme imagem abaixo):
B470:
Para inserir o valor do material próprio utilizado na prestação do serviço (campo VL_MAT_PROP), você precisa preencher a tabela Shadow /TMF/D_MAT_PROP.
Vale lembrar que o preenchimento das tabelas Shadow é de responsabilidade do cliente ou parceiro.
Gostaríamos muito de saber o seu feedback. Deixe seu comentário abaixo caso tenha alguma dúvida ou sugestão para um próximo post. E não esqueça de seguir a tag SAP Tax Declaration Framework for Brazil aqui na SAP Community para ficar ligado nas últimas notícias sobre o ACR Brazil Option.

Ailane Kuhn
Time de desenvolvimento do TDF



Source: https://blogs.sap.com/2019/01/10/acr-brazil-option-tdf-relacionamento-entre-registros-do-bloco-b-do-efd-icms-ipi/
Postado por às Nenhum comentário:

quinta-feira, 10 de janeiro de 2019

Sales Document Screen Sequence Control

Overview

SAP SD provides very dynamic approach to determine the sales document screen sequence. The user interface picks up different sub-screens to work with different business processes. The various user interface components are controlled by the function codes which are defined in the screen sequence group.
Let’s go to system to explore how screen sequence control works.

Sales Document Type

First of all, the screen sequence group as well as overview screen function code are defined in the sales document type:

In this example, the screen sequence group “LL” is defined for sales document type “LZ”, and the overview screen function code is defined as “UER2”.
How are those settings functioning in controlling user interface can be found several tables which are defined in transaction code “VFBS”.

Screen Sequence Control

The transaction code “VFBS” is used to control the screen determination for sales document.

Here we need to find out what program ID should be used on this transaction. This can be done by checking technical detail of any SD transaction (e.g.T-code VA01). It is not so difficult to find screen number of VA01 and the relevant program name:

In program logic, the program ID of sequence control is routed to “SAPMV45B” when transaction triggers to the main page of sales document.

So the program ID “SAPMV45B” will be used to control screen sequence determination:

Now let’s see how function code controls screen sequence in detail.

T185F

What kind of function is triggered in the screen will be defined in the table T185F. For example, generally we will press button ENTER to navigate from initial screen of sales document to the main screen. So the ENTER will be registered as a function code in table T185F:

In the same table, the second column defines transaction types. There are following transaction types available:

In our example, the default overview screen function code “UER2” was defined in the sales document type. The relevant entry can be found in the table “T185F”:

Settings in table T185F will be used to control what information is required in table T185.

T185

This table is used to define the paths between current location and next location. For example, from the initial screen of sales document, the current screen group is “A0”, and the function code is “UER2”.
So in the table T185, the next screen of initial screen is defined below:


The screen sequence group “LL” which was specified in the sales document type is defined here. Double click the item to check the detail:


Settings in the detail view represents that the current function and screen group are “USR2” and “A0”. The next location is defined as:
  • Subsequent screen group: U0 (TAXI_TABSTRIP_OVERVIEW)
  • Subsequent panel: ERFI – this will be used in the next step
  • Function code: ENT1

T185V

This table is used to define the technical detail, such as screen number.


By using the program ID, screen group “U0”, and panel “ERFI” which were determined in the previous step to locate the entry in this table:


Here field “Panel” was defined in table T185 according to previous step, and main screen number “4001” is defined here.
Double click the item to go to detail:


In the detail view, it is very clear that main screen “4001” has two sub-screens in tab control. To be precise, the sub-screen “4021” represents overview header:


And sub-screen “4419” represents item overview tab which was set by default on screen group “USR2”:


TAXITABS

This table is used to define tabs in the table control of sales document. Based on unknown reason, the program ID for table control definition is “SAPMV45A”:


In the table, there are many function codes defined to represent different tabs in the table control:


The screen group defines tab control. For example, “U0” represents overview table control.
There are following tabs (function codes) with their sequence defined in this table:


The column number defines sequence of overview tab. The function code “UER1” and “UER2” which were assigned in the sales document type will put the default active tab. For example, the first tab “Sales” is set as default tab if creating sales order (document type “OR”) and the tab “Item overview” is set as default tab when creating scheduling agreement (document type “LZ”).

Technical Detail

Screen Number Determination

PBO

In the PBO of initial screen the default values are prepared:


In step 1 the transaction VA01, system will prepare some default value based on transaction code. For example, the table T180 is used to store the screen sequence default value by transaction code.
The screen groups are hard coded in the form “TAXI_SCREEN_GROUPS_INIT”


The screen group will be used to determine the table control tabs and their function codes:


PAI

The screen sequence control information is determined in the PAI module of screen 101, which is the initial screen for sales document creation.


The screen number of main screen will be determined via screen sequence control in following module:


In above modules, following function modules are called:
  • FUNCTION_EXECUTE
  • SCREEN_SEQUENCE_CONTROL


Tab Control Determination

The tabs of the tab control are determined in the PBO of main screen of sales document. For example, assume the main screen of sales document is 4001. In its PBO there are following steps:


Step 1

Initialize the main screen and deactivate all unnecessary function codes.


The first form is used to determine the text (e.g. title) based on transaction group (e.g. order, inquiry, agreement, etc.)
The second one will filter out those unnecessary function codes.

Step 2

Following function modules are triggered to build up table control on the main screen by default:
  • TAXI_CREATE_CAPTIONS: determine the captions on each tab
  • TAXI_INITIALIZE_CARRIERSCREEN: hide unmarked tabs
  • GET_HANDLE_SD_TAB_CUST_H: handle the custom tab settings for sales document header
  • GET_HANDLE_SD_TAB_CUST_I: handle the custom tab settings for sales document item
  • TAXI_ACTIVATE_TAB: it is used to determine the default active tab by function code

Step 3 and Step 4

Call header sub-screen and call body sub-screen.

More investigation will be shared later.


Source: https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/

Postado por às Nenhum comentário:
Assinar: Postagens (Atom)