segunda-feira, 30 de setembro de 2019

It’s Trial Time for ABAP in SAP Cloud Platform


You have asked. We have listened.
Since SAP TechEd 2019 in Las Vegas the long awaited trial version of the SAP Cloud Platform, ABAP Environment is now available. Everybody can now get their hands dirty and can try out, for example the new ABAP RESTful Programming Model.

Where do I find ABAP trial ?
The ABAP trial is part of the Cloud Foundry trial and can be accessed via the SAP Cloud Platform trial access https://cockpit.hanatrial.ondemand.com.
For a detailed step-by-step description check out our Onboarding Tutorial.
A short description of the onboarding process can also be found in the SAP Online Help.

What do you need as prerequisites ?

What are the Rules of the Game ?
This trial is a Shared Offering. Opposed to other trial offerings in SAP Cloud Platform this is a shared trial offering. Trial users share an instance of the same backend system. As in an on premise ABAP development system the content is not separated which means you are able to see and change all objects that other developers have created. And they can to see and change the objects that you have developed. As a result we ask you to be careful when editing objects. So you should always be sure to replace the placeholders XXX provided in our tutorials with an unused 3-digit number or 3-character combination.
"Replace 'XXX' by an unused 3-digit number or 3-character combination
CLASS zcl_generate_travel_data_XXX DEFINITION
It’s for educational purposes only. The system may only be used to educate yourself. You must not use it for any other purposes.
It has a limited lifetime. The total lifetime of a shared trial system is 4 months. The first month is used for onboarding the users. After the onboarding period each user can use the system up to 3 months.

What is in that box and how can I import code?
For your convenience we have preinstalled the Flight Reference Scenario for the ABAP RESTful Programming Model. So no need for you to install it again. The Flight Reference Scenario provides sample data and services as well as legacy business logic to get familiar with the ABAP RESTful Programming Model. You can check out the end-to-end scenarios or build your own app based on the reference scenario and sample data.
As described in Use abapGit to Transform ABAP Source Code to the Cloud you can also import your own code into the trial system. This is possible using the abapGit client that comes with the ABAP Development Tools. But remember, this is a shared trial, so you must not upload anything beside your own demo code.

What should I do if I have a question or an issue ?
If you have a question or are stuck with something you can post it here: Ask a question using the tag SAP Cloud Platform, ABAP Environment .

Known limitations
Due to the shared trial approach, the following Steampunk features are limited:
  • Limited access to the Fiori UIs of the Admin Fiori Launchpad
  • No Identity Management Apps
  • No Communication Management Apps
  • No Software Component Life-cycle Apps
  • No support for custom Identity Provider
Most important limitations that result from the technical limitations above:
  • No usage of Destination Service
  • No usage of On Premise Connectivity
  • Business Roles can’t be created nor assigned
  • Custom Authorization Objects & Fields can’t be used

Related blogs

Where do I find further information ?
SAP Help Portal – ABAP RESTful Programming Model
Product Information – SAP Cloud Platform, ABAP environment
Tutorials
Learning Journey – SAP Cloud Platform ABAP Environment –> Choose Your Role –> Navigate to “Become competent” –> There you will find (in a few days) a section “ABAP Trial” that contains all tutorials that can be performed in the trial version.
Postado por às 3 comentários:

sexta-feira, 27 de setembro de 2019

Custom code analysis for SAP S/4HANA with SAP Fiori App Custom Code Migration

Maybe you already know, that ABAP Test Cockpit offers the option of executing the checks remotely on any ABAP system (SAP_BASIS >= 7.00). Using remote ABAP Test Cockpit infrastructure SAP customers and partners can analyze custom code in older systems using the latest ABAP Test Cockpit checks and only one central system for ABAP Test Cockpit (see blog series about Remote Code Analysis in ATC).
With SAP S/4HANA 1809, we offer the SAP Fiori Custom Code Migration App based on this remote ABAP Test Cockpit infrastructure. The App should be used for custom code analysis for SAP S/4HANA in the context of  SAP S/4HANA conversion (see also  SAP S/4HANA System Conversion – Custom code adaptation process).
NEW: Starting with the SAP Cloud Platform ABAP Environment 1908 you can use SAP Fiori App Custom Code Migration in the Cloud to analyze custom code in your on-premise SAP system for SAP S/4HANA readiness. See also the blog ABAP custom code analysis using SAP Cloud Platform.
The App performs SAP S/4HANA checks on your custom code, which needs to be migrated from your SAP Business Suite System to SAP S/4HANA and provides the analytical presentation of the ABAP Test Cockpit check results with comprehensive filtering and navigation capabilities. Beyond this the App identifies the unused custom code based on your collected usage data, and this enables you to remove it automatically during a system conversion to SAP S/4HANA.

Technical Setup

There are two options to setup the custom code analysis with SAP Fiori App Custom Code Migration:
1) Use SAP Fiori App Custom Code Migration in SAP Cloud Platform
For technical setup instructions for using the SAP Fiori App Custom Code Migration in SAP Cloud Platform please refer to the blog ABAP custom code analysis using SAP Cloud Platform.
The SAP Fiori App Custom Code Migration will run in SAP Cloud Platform ABAP Environment and will check custom code in your on-premise SAP system using the remote ATC infrastructure with RFC through SAP Cloud Connector:
2) Use SAP Fiori App Custom Code Migration in SAP Cloud Platform
You need an SAP S/4HANA >=1809 system set up as a central ATC check system. Our recommendation is to use your SAP S/4HANA sandbox system. See also Remote Code Analysis in ATC – Technical Setup step by step for setup guidance.
You need also to setup and configure the SAP Fiori App Custom Code Migration on this SAP S/4HANA 1809 system. Use SAP documentation on SAP Help Portal for specific implementation and configuration information on SAP Fiori App Custom Code Migration. The SAP Note 2436688 provides all required SAP Notes for the SAP Fiori App Custom Code Migration.
The SAP Fiori App Custom Code Migration will check custom code in your SAP backend system using the remote ATC infrastructure:

Create your Custom Code Migration Project

Start Custom Code Migration App on your SAP Fiori Launchpad. You can maintain multiple custom code migration projects in the App:
  => 
Create your Custom Code Migration Project by pressing “+” (Create Object) button and entering your project data: Project Description, Target Release for your SAP S/4HANA System and RFC Destination to your SAP ERP system:

Add usage data to your Custom Code Migration Project

Now you can add usage data collected either by the ABAP Call Monitor (SCMON) and aggregated by the SUSG transaction or add usage data collected in your SAP Solution Manager system (SAP Solution Manager 7.2 SP8 is the prerequisite).
NOTE: You should collect usage data of your business processes at least for one year in order to get really reliable results for not productively used code.
For information about how to collect usage data and aggregate it in your ERP production system see the blogs: ABAP Call Monitor (SCMON) – Analyze usage of your code and Aggregate usage data in your production system with SUSG transaction.
If you collected usage data in your ERP production system, use there the SUSG transaction to create a snapshot of usage data. The App will access it via RFC:
You can add usage data to your Custom Code Migration Project by pressing “+” (Add) button and using F4 Help in the Usage Description field. Save your project by pressing the “Save” button.
NOTE: If you collected usage data in the SAP Solution Manager, then the App detects whether it is a SAP Solution Manager system behind the RFC destination for the usage data. Then the existing SAP Solution Manager usage data records are displayed in the selection dialog.

Define the scope of your Custom Code Migration Project

Now you can define (based on usage data) which ABAP custom code needs to be taken over to your SAP S/4HANA system. The App will create a deletion transport in order to enable deletion of unused ABAP custom code during the system conversion to SAP S/4HANA.
Navigate to the Scope overview. You will see the graphical presentation of the detailed scope information. When you add usage data to your custom code migration project, a default scope is calculated. The default scope includes all used objects, all objects which are statically referenced by the used objects, and objects for which no usage data is available such as database tables or data elements.
If you included usage data into your Custom Code Migration Project, you can click on the Scope Request Entry Points. There you will get (based on the usage data) a list of the executed request entry points (such as a specific transaction, RFC call, URL request, or ABAP report) along with all ABAP procedures that have been executed under these entry points, and you can decide, which objects you want to remove (Remove from scope) (for example based on the last usage date).
In case you want to adjust the scope manually, the App offers the possibility to add/remove packages or single objects to/from the scope (click “Scope Packages” button). This can be useful to include new developments that are not yet productively used or exclude some developments that you will not need in your new SAP S/4HANA system.
After you defined the scope of your Custom Code Migration Project, you can create a transport request in your ERP system, which contains all information about your unused custom code (all objects that are not in scope). To do so go to the Project tab and click Save Scope as Transport Request):
The transport request gets created and appears under Request/Task of your Custom Code Migration Project:
This transport request can be added to the Software Update Manager (SUM) for the SAP S/4HANA conversion, the unused objects (not in scope) will be deleted by SUM.
NOTE: In case you want to keep a backup of the deleted objects we recommend to use abapGit in order to store the objects of the transport request in a Git Repository. For assistance how to do it see also the Steps 1-3 in the tutorial Use abapGit to Transform ABAP Source Code to the Cloud on sap.com.

Analyze your custom code with SAP S/4HANA checks

As soon as you create your Custom Code Migration Project the SAP S/4HANA custom code checks are executed automatically by ATC, and the App offers you the analytical presentation of SAP S/4HANA custom code check findings.
Go to the Analysis tab and click on the “Analyze Findings” button:
Using the visual filters above you can group your ATC findings to get information on for example:
  • What are the most important (urgent) findings (-> filter Findings by Priority)
  • How many findings relate to the custom code objects you take over to SAP S/4HANA (-> filter Findings by Scope Information)
  • How many findings relate to your custom package XYZ (-> filter Findings by Package)
  • In which simplification areas do you get the most findings (->filter Findings by SAP Note Number)
  • For which findings there are Quick Fixes available and which findings you need to fix manually (->filter Findings by Quick Fix Availability, currently available with SAP S/4HANA 1809 SP02)

Further information


Postado por às 3 comentários:

ABAP custom code analysis using SAP Cloud Platform

As you probably already know, you can analyze your ABAP custom code for the SAP Cloud Platform ABAP Environment using the Remote ABAP Test Cockpit with the ATC central check system on the SAP_BASIS 7.52 and Cloud readiness checks.
You can also analyze your ABAP custom code for SAP S/4HANA readiness using the SAP Fiori Custom Code Migration App in an SAP S/4HANA 1809 system based on the same remote ABAP Test Cockpit infrastructure.
Often SAP customers experience the problem, that they have neither SAP_BASIS 7.52 nor SAP S/4HANA 1809 system in their landscapes, and therefore the custom code analysis was not even possible.
Therefore, starting with the SAP Cloud Platform ABAP Environment 1908 we offer an option in the Cloud to execute custom code analysis for your on-premise SAP systems. You can now use the SAP Fiori App Custom Code Migration in the Cloud to analyze your ABAP custom code for both use cases: SAP S/4HANA conversion and Cloud readiness.
The advantages of the Cloud-based offering for custom code analysis are apparent. You don’t need to install and maintain an additional SAP system in your landscape. Beyond this you can immediately consume the newest innovations of the ABAP stack and the newest custom code checks because of quarterly shipment schedule, and delegate all infrastructure, lifecycle management and operational tasks to cloud operation.
The SAP Fiori App Custom Code Migration runs in the SAP Cloud Platform ABAP Environment and performs remotely, depending on your use case, SAP S/4HANA or Cloud readiness checks for the custom code in your on-premise SAP system. The App provides the analytical presentation of the ABAP Test Cockpit check results with comprehensive filtering and navigation capabilities. During custom code analysis the App identifies, which custom code can be adapted in a semi-automated way using the Quick Fixes in ABAP Development Tools (ADT).

Technical Setup

After the setup the SAP Fiori App Custom Code Migration will run in SAP Cloud Platform ABAP Environment and will check custom code in your on-premise SAP system using the remote ATC infrastructure with RFC through SAP Cloud Connector:
The procedure for setting up the SAP Fiori App Custom Code Migration in the Cloud is as following:
  1. First you need to purchase the entitlement to SAP Cloud Platform ABAP Environment. For more details see SAP Cloud Platform, ABAP environment on SAP Cloud Platform web site or SAP Cloud Platform, ABAP environment in the SAP Store.
  2. After that you have to set up your SAP Cloud Platform ABAP Environment as described in Getting Started with a Customer Account: Workflow in the ABAP Environment
  3. Then you need to get a user in the SAP Cloud Platform ABAP Environment Connect to the ABAP System.
  4. Afterwards you must enable the SAP Fiori App Custom Code Migration in the Cloud to check your SAP on-premise system. Use SAP documentation on SAP Help Portal Enable Usage of the Custom Code Migration App.
  5. Finally for your on-premise SAP system you need to apply the SAP Notes mentioned in SAP Note 2364916 for the Checked System (Recommended SAP Notes for using ATC to perform remote analysis)and apply the SAP Note 2599695 (Custom Code Migration Fiori App: Remote Stubs for the Checked System).
  6. Now you can start the SAP Fiori App Custom Code Migration on your SAP Fiori Launchpad in the Cloud and create your first Custom Code Migration Project.

ABAP custom code analysis for SAP S/4HANA

For detailed step-by-step guidance on how to use the SAP Fiori App Custom Code Migration to analyze your custom code for SAP S/4HANA readiness please refer to the blog Custom code analysis for SAP S/4HANA with SAP Fiori App Custom Code Migration.

ABAP custom code analysis for Cloud

For detailed step-by-step guidance on how to analyze your custom code for Cloud readiness with SAP Fiori App Custom Code Migration please refer to the blog How to check your ABAP code for SAP Cloud Platform ABAP Environment.
Postado por às Nenhum comentário:

quinta-feira, 26 de setembro de 2019

Business Partner SAP S/4 HANA insights

Business Partner Approach in SAP S/4 HANA
The following blog post provides an insight into the SAP S/4 HANA system and how business partner setup must be done for migration.
I would like to share a glimpse of my current experience with SAP S/4 HANA migration.
Many of us always struggle where to start, how to start and finally ends with why to start 😊
Let us discuss, how to start/maintain a system with clean data and migrate to SAP S/4 HANA.
For a successful implementation of the data migration, it is vital that the system is populated with a complete and accurate set of data from legacy systems that meets the technical requirements of target systems and the business requirements of its users.
In any project, appropriate understanding and analysis of the data of the source system and the ‘to be’ system allows a program of data management actions to be defined and implemented to produce a data set:
  • That maximizes the value of legacy data used in the new system
  • That makes data available to accelerate business benefit delivery
  • That meets the data demands of business processes
  • That meets the technical data demands.
  • Takes care of pain areas of the current data quality
With current project experience, I have divided into below categories
  1. Analysis – of the system (source and target) and source data
  2. Enrichment – the source data
  3. Cleansing – the data
  4. Consolidation – final output which is going to be migrated
SAP S/4 HANA offers you many new possibilities for managing your business partner data. But many SAP customers realize: a smooth transition is impossible with the data as it is – the quality is just too poor.
Companies found data migration is more difficult than expected, let us go through how (with my knowledge)
  • Today, customer and supplier data might be distributed everywhere. Tomorrow, you want it consolidated in one database (the “SAP Business Partner”)
    • Eg: company ABCD may be having their businesses in different countries and maintaining their transactional data in various databases and they have decided to consolidate their customer data and supplier’s data at one point.
    • And here is a solution what are we talking about.
Issues generally what we face:
  • Countless duplicates make it very hard to identify the truly active business partners
  • Closer to go-live, companies discover that data is incorrect and incomplete, automatic transactions do not go through; deliveries might end up at the wrong address
  • As the go-live date looms, the time has run out to organize a manual data cleanup
In SAP S/4 HANA, Business Partner is the leading object and single-entry point to maintain Business Partner, Customer, and Supplier (formerly known as Vendor) master data. This is to ensure ease of maintenance of the above master data and to achieve harmonization between them. Compared to classical ERP transactions, maintenance of Customer and Supplier master data via Business Partner has multiple advantages. Some of them are as follows:
  • Business Partner allows maintenance of multiple addresses with corresponding address usages.
  • In classical transactions, one customer can only be associated with one account group. But in Business Partner, multiple roles can be associated with the same Business Partner.
  • Maximal data sharing and reuse of data which lead to easier data consolidation.
  • General Data available for all different Business Partner roles, specific data is stored for each role.
  • Maintenance of multiple relationships to the same Business Partner.
  • Maintenance of Time Dependency at different sub-entities roles, address, relationship, bank data, etc.
Description:
There are redundant object models in the traditional ERP system. Here the vendor master and customer master are used. The (mandatory) target approach in SAP S/4 HANA is the Business Partner approach.
Business Partner is now capable of centrally managing master data for business partners, customers, and vendors. With current development, BP is the single point of entry to create, edit, and display master data for business partners, customers, and vendors.
Using RFC functions, we can target to load/migrate the data to SAP S/4 HANA.
There are standard RDP (Rapid Data Mart) functionalities were offered by SAP, it is the best to part of creating business partners.
Like using CVI functions, we can create, edit and delete*(this is a huge topic could be discussed, here deleting could be considered as limited to the individual roles).
In native application, it is not possible to migrate customer and vendor/supplier together to the target system, the question arises here is: can we achieve this through a business partner approach in SAP S/4 HANA?
The answer is: YES, we can.
The solution is: Maintaining with different roles in a business partner for supplier and customer.
Ideally, for a customer- it will be FLCUXX(FLCU00/FLCU01)
As below:
FLCU00 will be accounting and FLCU01 will be sales
In details:
How to navigate to Business partner?
Answer is:
Go to SAP screen and Tcode – BP
Then you can find the next screen with business partners:
You can easily identify with roles, what are you dealing with:
The base role should be a business partner- 000000- In general, you need to do nothing here, it will automatically be created with other roles by default.
Let us see other roles here for customer and vendor integration:
  1. Business Partner -000000
  2. Customer- FLCUXX
    1. Customer Account
    2. Customer sales
  3. Vendor -FLVNXX
    1. Vendor accounting
    2. Vendor purchasing
You can easily identify in below screen:
The subcategory roles will be replaced XX with 00/01/02 follows (customization part).
In a nutshell, we can send these roles along with additional details which were required like general data along with address, identification details, sales organizations, company details, vendor general data, vendor purchasing information and maintaining relationships(another tricky part and important for BPs)
The above-mentioned additional details will itself another big topic like, how to set up sales orgs, purchase information, company details, etc, could be probably discussed in the next blogs.

Learning credits: @arunkumar yadav
You can find more details here in the following link, how to configure too.
In the next blog posts, we can discuss more on the processings.
That’s all about this blog post.
Happy Learning!!!
Postado por às 3 comentários:
Assinar: Postagens (Atom)