sábado, 21 de março de 2020

New videos showcasing SAP Fiori 3 for SAP S/4HANA

If you’re looking for examples of how SAP Fiori actually helps users get their work done more easily: we have created a series of two minute videos with some concrete examples, including for the first time some examples showing the Situations approach for surfacing machine intelligence, and an example showing the seamless integration of SAP S/4HANA Cloud and SAP Analytics Cloud.
The SAP Fiori 3 target design aims to enhance SAP Fiori to support consistency, intelligence and integration. Many SAP products now already provide first steps towards consistency by supporting the SAP Fiori 3 theme “Quartz Light” and the shell header bar; below you can see first examples for intelligence and integration.
The series starts with two introductory videos, which some of you may have already seen:
The subsequent three videos each give an example of how a user can quickly and easily perform a given task using SAP S/4HANA with SAP Fiori, and are updated versions of the three videos I published a year ago, with additional content:
Two of the next three videos show how the Situations approach introduced by SAP Fiori helps SAP S/4HANA users deal with important but not-so-common business situations, and one shows the seamless integration between SAP S/4HANA Cloud and SAP Analytics Cloud:
If you are not familiar with the Situations approach, let me summarize it briefly: it is a powerful approach for helping users deal with not-so frequent but important business situations. The system
  • recognizes when a business situation occurs;
  • notifies the responsible user;
  • provides the user with an explanation of the situation, and
  • provides guidance and recommendations on how to deal with it.
Identifying a business situation and determining appropriate recommended actions can be done using machine learning or rule-based. The power of the approach comes from the way it helps users: the notification means they are informed in a timely manner, and the explanation and recommended actions mean that users can save a lot of time by having all the relevant information presented to them in one place, rather than having to search for it themselves throughout the system.
The Situations approach is under continuous further development, and is one of the key elements of the SAP Fiori 3 target design, so stay tuned to learn about further improvements going forward.
For more insights into the currently supported design concepts behind the situations approach, have a look at the Situation Handling section in the SAP Fiori design guidelines.
Postado por às Nenhum comentário:

How and why to upgrade SAP Fiori for your SAP S/4HANA solution

As part of the SAP S/4HANA Regional Implementation Group, I have the privilege of working with a lot of customers who are implementing SAP S/4HANA locally, regionally, and internationally.
Now that SAP S/4HANA has been available for over 3 years, we are more often finding customers who are upgrading their version, sometimes as part of their initial project, sometimes as a next phase.
Are you already live or doing a project with SAP S/4HANA and SAP Fiori apps in your company? Maybe you wonder how to implement this on your system?
In September 2019, SAP released SAP Fiori 3 for SAP S/4HANA, providing UX harmonization across SAP Solutions and brought also on SAP S/4HANA a new Quartz theme and some new features.  SAP S/4HANA 1909 comes with SAP Fiori 3 by default but you can also upgrade other SAP S/4HANA releases to get it.
Next to technical improvements like the new Quartz theme, new launchpad functionalities, improved performance, every SAP S/4HANA release (1610, 1709, 1809, 1909, .. ) comes with many new apps, while existing apps are updated and get new functionalities (eg. more export to spreadsheet opportunities).
Upgrading SAP Fiori on your SAP S/4HANA system will bring your end-users:
  • New features and apps
  • The latest SAP Fiori 3 design improvements
  • Improve performance and bugs fixes
  • Move to the latest long-term SAPUI5 maintenance release, in case you are looking at the end of maintenance dates for your current SAP Fiori frontend server (FES) or SAPUI5 release
In this blog post you can find out how to approach upgrading your SAP Fiori in an SAP S/4HANA context.
NOTE: All recommendations below are applicable for both embedded and hub deployment options. The embedded deployment option is the recommended deployment option. For an overview and comparison of the different deployment options and recommendations, please refer to the document SAP Fiori Deployment Options and Recommendations.  If you are running a hub (aka standalone) deployment now, consider moving to embedded.  See blog and step-by-step guide Transition from Standalone to Embedded Deployment. This will provided you a lower total cost of operation (TCO) since there is no additional server needed and enable SAP Fiori Rapid Activation, lowering the effort to activate additional SAP Fiori apps.

Upgrade Scenarios

We can identify 3 different ways/options to upgrade:
  • Upgrade your SAP S/4HANA release – this is the preferred option!
  • Upgrade SAP Fiori Frontend Server (FES) – Reasonable alternative
  • SAPUI5 patching – bug fixing with minimal functional impact
Keep reading to find out the differences!

Upgrade Scenario 1: Upgrade your SAP S/4HANA release – this is the preferred option!

e.g. you are on SAP S/4HANA 1610 and upgrade to SAP S/4HANA 1909 FPS1.
With this upgrade you will update the following components in your SAP S/4HANA landscape:
  • SAP S/4HANA (e.g. S4CORE, NW ABAP release)
  • The corresponding SAP Fiori for SAP S/4HANA
  • The SAP Fiori Frontend Server (FES)
NOTE: FES upgrade is in most of the cases mandatory when upgrading your SAP S/4HANA system and FES 6.0 is currently recommended to be used for all releases.  All supported combinations are described in SAP Note 2217489 – Maintenance and Update Strategy for SAP UI (SAPUI5) in SAP Fiori Front-End Server.  Latest release is FES 6.0 SP1 and available for most S/4HANA releases (not for 1511), see SAP Fiori Front-end Server 6.0 – Extended maintenance and upgrade recommendations blog.  Some more info also in the later on in this blog.
Pros:
  • With this you will get new apps, and latest SAP Fiori Frontend Server (FES) with new features, new tools.
  • Greater opportunities, e.g. new simplifications, changes in business processes, new intelligent options to consider.
Cons:
  • The downside is you have to do lots of regression testing.
  • You also have greater business expectations and more choices to work through beyond simply new apps.
Who’s doing this?  An Australian automotive customer recently upgraded from SAP S/4HANA 1610 to SAP S/4HANA 1909.  Recent upgrades for SAP S/4HANA include USA customers moving from 1610 to 1809 – in the manufacturing/retail, and insurance.
How can you do this? In the following blog the steps to upgrade from S/4HANA 1610FPS1 to 1809FPS0 are described.
You can find in the SAP Fiori apps reference library which apps are available in every release.   For example: Filter by Product Version using your SAP Fiori for SAP S/4HANA version and FPS release:
Currently as at March 2020 you will find the below numbers showing there is an increasing apps for every S/4HANA release:
  • SAP S/4HANA 1909 > 1647 SAP Fiori apps
  • SAP S/4HANA 1809 > 1327 SAP Fiori apps
  • SAP S/4HANA 1709 > 948 SAP Fiori apps
  • SAP S/4HANA 1610 > 540 SAP Fiori apps
In the Finding the Delta of New Apps between SAP S/4HANA Versions blog we describe how to find the delta between versions.
In the SAP S/4HANA What’s New Viewer you can also find an overview of the new, changed and deleted features and functions in the most recent SAP S/4HANA releases:
IMPORTANT:  What is the difference between FPS and SPS in the context of SAP Fiori on SAP S/4HANA?
For the product SAP S/4HANA on-premise edition, SAP is shipping 1 new key release per year e.g. SAP S/4HANA 1809 FPS0 released in 2018, and 2 successive Feature Pack Stacks (FPS), e.g. FPS1 (01/2019), FPS2 (05/2019).
Then comes the next key release (eg. SAP S/4HANA 1909), followed again Feature Pack Stacks, etc.  On the previous key release there are in parallel SPS released eg. SAP S/4HANA 1809 SPS3 (10/2019). 
Feature Packages and Feature Package Stacks (FPS) – deliver nondisruptive innovation for generally available product versions as well as bundling software corrections and legal changes.  Support Package Stacks (SPS) – sets of support packages and patches for the respective software release that must be used in the given combination.
So, an FPS upgrade, e.g. SAP S/4HANA 1909 FPS0 to FPS1, can include new or enhanced functionality and patches/bug fixes.  For SAP Fiori we also see some apps get new functionality and also bugs are solved.
A SPS upgrade e.g. SAP S/4HANA 1809 FPS2 to SPS3, issues with some SAP Fiori apps are solved, no new functionality is introduced

Upgrade Scenario 2: Upgrade SAP Fiori Frontend Server (FES) – Reasonable alternative

e.g. you are on SAP S/4HANA 1709 and upgrade your FES from 4.0 to 6.0.
Upgrading FES will update components SAP_UI and UIBAS.
NOTE: FES stands for SAP Fiori Frontend Server, however this does not mean you need a separate server.  Actually, the FES components are recommended to be deployed embedded on the SAP S/4HANA system.  More info in the SAP Fiori Deployment Options and Recommendations blog
Pros
You get a new looking SAP Fiori launchpad (FLP) including:
  • SAP Fiori 3 (even on “older” releases like SAP S/4HANA 1610)
  • A few (frontend only) FLP new features, e.g. new personalization options
  • Some improvements to apps in UIBAS – i.e. My Inbox and general functions for Key User apps, e.g. Custom Fields and Logic.
  • Fewer business and org change management impacts – No changes in business processes, simplifications or intelligent options
Cons:
  • No new apps
  • Some regression testing is needed of the launchpad and a sample set of existing apps
IMPORTANT:
  • You will *not* get any new or updated SAP Fiori apps until you upgrade SAP S/4HANA itself.
  • Similarly, upgrading your SAP_UI or SAP FES may *not* bring new launchpad features or launchpad support/admin tools where these depend on backend capability e.g. no new business objects for Enterprise Search
  • Review differences between SAP Fiori launchpad guides
SAP FES 6.0 is the long-term maintenance version and the recommended go-to-version for SAP Fiori front-end server upgrades for SAP Business Suite and SAP S/4HANA customers both for embedded and hub deployments.   When upgrading to FES 6.0 SP1 your SAPUI5 release is on long-term maintenance (until 2025) version 1.71.  More details in the  SAP Fiori Front-end Server 6.0 – Extended maintenance and upgrade recommendations blog
Who’s doing this? Some current projects implementing 1809 FPS2 are now upgrading to FES 6.0 SP1, i.e. SAPUI5 1.71.
How to do such an upgrade?  In the SAP Maintenance Planner tool, select “Install or Maintain an Add-On”, choose SAP FIORI FRONT-END SERVER 6.0 – SP01.
Example of the installed product versions in a SAP S/4HANA 1809 system upgraded to FES 6.0 SP01 :
IMPORTANT:  SAP S/4HANA 1511 is not supported for SAP Fiori Front-end server 3.0, 4.0, 5.0 and 6.0. (SAP S/4HANA 1511 continues to run on version 2.0) See SAP Note 2775163 – SAP-Fiori-Frontend-Server 6.0 – General Information
– therefore customer on 1511 should look into the first upgrade scenario (Upgrade SAP S/4HANA Release)
IMPORTANT: For any deployed SAP Fiori apps that are not part of SAP S/4HANA you must also do due diligence check that these apps are still supported, see SAP Note 2825540 – Release of Fiori Product Versions for SAP Fiori front-end server 6.0
You can check the following note for the release schedule for FES :

Upgrade Scenario 3: SAPUI5 patching – bug fixing with minimal functional impact

We recommend patching your SAPUI5 to the latest patch level. Patching applies any already known and resolved bug fixes of that SAPUI5 version.  Patching SAPUI5 can be done regularly to keep your version up-to-date or to solve a known issue.
IMPORTANT: SAPUI5 releases a more patches than SAP_UI releases support packages, therefore this patching should also be done after upgrade scenarios #1 and #2 described above. Why is this important?  We have seen several customers apply the SAP_UI component changes and end up experiencing issues because their minor patch level was so very low.  It is better to directly upgrade the SAPUI5 directly as well.
NOTE : SAPUI5 uses a 3-digit version identifier, for example 1.60.2, the third digit specifies the patch number and is solving known issues,  see also Versioning of SAPUI5
You can find the available SAPUI5 versions here in the SAPUI5 Versions Maintenance Overviews Status page.  Differences between SAPUI5 version capabilities can be derived from the What’s New section of the SAPUI5 SDK for each version.  You will need to go through each version’s What’s New & Changelog to get a full picture.
NOTE: You can easily find the SAPUI5 version and patchlevel you are currently running via the About icon in the FLP, as described in the Finding the technical name of an app blog.
Who’s doing this? This is something every customer should be doing! It’s particularly important to make sure you have patched SAPUI5 prior to User Acceptance Testing to minimize issues.
How to do this patching is described in the following notes:

Involved ABAP software components

On an SAP S/4HANA system the following ABAP components are involved:
  • SAP FIORI FOR SAP S/4HANA
  • SAP_UI
  • UIBAS
  • SAP_GWFND
We share some more details on these components further below.
SAP FIORI FOR SAP S/4HANA : this component contains the actual SAP Fiori apps and there is a strict (1:1) dependency with the SAP S/4HANA release.
For example:
  • SAP S/4HANA 1909 FPS1 <> SAP FIORI FOR SAP S/4HANA 1909 SP1 (02/2020)
  • SAP S/4HANA 1909 FPS0 <> SAP FIORI FOR SAP S/4HANA 1909 SP0 initial shipment pack
  • SAP S/4HANA 1809 FPS3 <> SAP FIORI FOR SAP S/4HANA 1809 SP3 (10/2019)
  • SAP S/4HANA 1809 FPS2 <> SAP FIORI FOR SAP S/4HANA 1809 SP2 (05/2019)
  • SAP S/4HANA 1809 FPS1 <> SAP FIORI FOR SAP S/4HANA 1809 SP1 (01/2019)
Release notes of this software component:
  • 2805572– SAP FIORI FOR SAP S/4HANA 1909: Release Information Note
  • 2667191– SAP FIORI FOR SAP S/4HANA 1809: Release Information Note
  • 2482461– SAP FIORI FOR SAP S/4HANA 1709: Release Information Note
  • 2200415– Release of Fiori Product Versions for SAP UI Addon 2.0 / SAP_UI 7.50
  • 2310351– Release of Fiori Product Versions for SAP Fiori Frontendserver 3.0
SAP_UI:  this ABAP software component contains the SAPUI5 libraries.  New SAPUI5 versions bring new functionalities, bug fixes, performance improvements (in apps and in the FLP).
You can check the release schedule for SAP_UI component here:
NOTE: while it is technically also possible to only upgrade the SAP_UI component SAP recommends to always include the other FES components SAPBAS (upgrade scenario #2).  These are supported combinations that also other customers are using.   And you might face unexpected bugs, for which you will need to raise SAP Incidents.
Upgrading to the current latest SAP_UI version 7.54 SP2 will currently bring you the SAPUI5 1.71, a long maintenance release version (currently supported until Q4/2025).
Upgrading SAP_UI (and the included SAPUI5) will also bring you general improvements of SAP Fiori launchpad.  Please check the What’s New section of the SAP Fiori launchpad guide for your SAP S/4HANA version.   See  SAP Help – SAP Fiori Launchpad , select the SAP Fiori launchpad guide for your SAP_UI and ABAP platform version.
SAP S/4HANA 1909

SAP S/4HANA 1809SAP Fiori launchpad with SAP_UI 753
SAP S/4HANA 1709SAP Fiori Launchpad with SAP_UI 752 
SAP S/4HANA 1610SAP Fiori Launchpad with SAP_UI 751 

UIBAS:  contains basis UI libraries like MyInbox and general functions for key users.  Closely linked to the SAP_UI component. These are shipped together in the SAP Fioiri Frontend Server product version, e.g FES 6.0 SP1.
SAP_GWFND :
This software component replaced IW_PGW (frontend), IW_BEP (backend) and GW_CORE components since the ABAP NW 7.40 release.
SAP_GWFND was part of the FES release until NW 7.52 (SAP S/4HANA 1709).  As from NW 7.53 (SAP S/4HANA 1809) it is part of the core ABAP NW Platform.  See SAP Note 2634691 – Task Gateway – Software components
SAP_GWFND offers development and generation tools to create OData services to a variety of client development tools.
Related SAP Documentation and SAP Notes to check
Before making your decision go through all relevant SAP Notes and information regarding the relevant versions of the SAP FIORI for SAP S/4HANA, FES, and SAP_UI for your current and target versions.  While we try to keep also this blog updated, SAP Help and Notes are the official documentation and up-to-date information from SAP.
Usual SAP Notes and links of the latest releases:

 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

Postado por às Nenhum comentário:

Asset Legacy Data Migration in New Assets Accounting (S/4 HANA 1909) – Current year Acquisition Scenario Techno-Functional Solution

Introduction:

In FICO Asset Legacy Data Migration in New Asset Accounting, the procedure is explained below for current year acquisition scenario. Both the Functional and Technical Solutions along with the sample report for BAPI are explained in detail .

Main Problem:

In ECC system the Transaction code AS91 is used to create asset master and also post asset values in asset accounting through ‘Takeover values’. Now, Taking over of values is not possible in S/4 HANA system in AS91. In ECC, transaction data was getting posted separately in Assets Accounting through ‘AS91-Takeover values’ and General Ledger Accounting through OASV/FB01.
For the Asset Migration in S4 Hana, the System Procedure differs and needs some configurations before asset creation and acquisition in different scenarios. Also a combination of both LSMW and BAPI is required to complete the upload .

Solution:

Asset Cut over – Current Year Acquisitions :
In S/4 HANA, to post an asset with current year Acquisition we have to use three transactions:
Transaction code AS91 for Asset Master Data
Transaction code AB01 to transfer the acquisition transaction of legacy asset posted in current year.
Simulate and post . Further carry out Transaction code ABLDT to takeover ordinary depreciation posted in current year by entering amount in field ‘Ordinary dep.posted’ (NAFAG). & Post.
Now for Transaction Code AB01 during mass upload we cannot create a LSMW recording . This can be achieved by using a BAPI for mass upload.
BAPI : BAPI_ASSET_ACQUISITION_POST.
Using this BAPI all the Acquisition Data can be Posted , This BAPI should be followed by BAPI_TRANSACTION_COMMIT.

The IMPORT PARAMETERS of the BAPI :
In each of  the importing tables values for various fields required for acquiring the asset can be passed.
For Example :
In the Export parameters success message will be returned.
A z-report can be created for the BAPI upload program , which converts the data maintained in excel into internal table which can further be passed into the import parameters of the BAPI.

Sample of the Z-report created :
For converting data from Excel into Internal table.
For passing the values into import parameters of the BAPI .

Conclusion :

So, in this blog post we have seen how to carryout asset legacy data migration for SAP S/4 HANA for current year Acquisition . Please feel free to share if you have followed any other methods to do the same and share if you have any comments.
Postado por às Nenhum comentário:

Migration of House Banks from ECC to SAP S/4HANA

Prima facie Migration of House Banks to SAP S/4HANA seems to be simple. Sometimes,  it creates challenging and interesting issues as we go through the Migration process.
I tried to provide a brief information, relating to House Bank Migration:
  1. What is New in SAP S/4HANA 1909 (from Migration Cockpit perspective)
  2. High level SAP S/4HANA Data Model changes relating to House Banks
  3. Pre-requisites for House Bank Migration
  4. House Bank Migration
  5. How to Access House Bank Accounts after migration.
  6. References/SAP Notes
What is New:
To simplify the migration process, as of SAP S/4HANA 1909, following manual steps are included in Central Migration Cockpit (Start and Monitor Data Migration)
  • Activities “Fill in Due Dates in FI Document and Display Status of Filling Due Dates into FI Documents are now executed automatically in the Enrich Transactional Data (ENR) step of the Start and Monitor Data Migration activity.

  • Migrate House Bank Accounts now executed automatically in the Migrate House Bank Account (T012K) to Bank Account (CM1) step of the Start and Monitor Data Migration Activity

  • Migrate General Ledger Allocations activity now executed automatically in the Migration of the GL Allocations (GL)AL_MIG) step of the Start and Monitor Data Migration activity.

High -level SAP S/4HANA Data Model Changes relating to House Banks:
House Banks in SAP S/4HANA:
  1. House bank accounts merged into bank account master data. As a part of migration,  house bank accounts originally stored in database table T012K moves to table FCLM_BAM_ACLINK2.
  2. After Migration, we can create the House banks using transaction code FI12_HBANK. This transaction code is only for creating the House bank but not Bank Accounts for House Banks.
  3. Activation of Business Function FIN_FSCM_CLM is not mandatory for Migration of House Banks. (Not full scope of CLM used)
  4. Some House Bank Related table names
Table Name
Description
FCLM_BAM_AC_LINK
Linkages Between House Bank Accounts and Bank Accounts
FCLM_BAM_AC_TYPE
Bank Account Type
FCLM_BAM_AC_TYPT
Bank Account Type Text
FCLM_BAM_ACLINK2
Linkages Between Bank Account and House Bank Accounts
FCLM_BAM_AMD
Bank Account Master Data
FCLM_BAM_AMD_T
Bank Account Master Data: Text table of Account Descriptio
FCLM_BAM_BKBPHIS
History for Bank and BP Linkage
FCLM_BAM_BNKABP2
Relationship between Bank and Business Partner
FCLM_BAM_CONFIG
Configuration for Bank Account Management
FCLM_BAM_HIER
Bank Account Hierarchy
FCLM_BAM_HIERBGN
Bank – bank group name mapping
FCLM_BAM_REQ
Change request for bank account master data
FCLM_BAM_REQACNT
Change Request:Bank Accounts

Pre-requisites for House Bank Migration
Following flow charts indicates the  pre-requisites before starting the Migration/Conversion.

The Bank Account Master Data Processing with Full Cash Management versions including Direct Revision Activate, Dual Control Revision Activate and Workflow Revision Activate, require an additional license for SAP Cash Management powered by SAP HANA.
House bank Migration
House Bank Migration is a part of Migration Cockpit. (IMG>Conversion of Accounting to SAP S/4HANA>Data Migration>Start and Monitor Data Migration.
All the pre-conversion requisites to be completed.
All pre-requisites for executing the Migration Cockpit is completed.
As a part of Migration Cockpit execution, House Bank also gets migrated.
If the errors are relating to pre-delivered content, we can also accept the errors, if we are convinced about the nature of those errors. If it is relating to the Business bank data information, further analysis and fix is required.
Based on the errors during Migration Cockpit execution, we can fix the errors whatever is possible, reset and reexecute the step in Migration Cockpit.
If any errors found during the migration cockpit run, we can also execute the house bank migration manually using Tcode: FCLM_BAM_MIGRATION. This tcode gives an opportunity to see the status traffic light. We can re-execute for the red ones to know any further errors.
After executing the migration, we can also see log in tcode: SLG1 to see the details of the error.
Most of the errors during House bank migration are self explanatory.
SAP Notes, given under references section gives a good idea about House Banks related topics.
Please note, we need to document the process steps followed for resolution of the House bank migration issues and thorough testing is done subsequent to migration. This helps to have a clarity  during the next/subsequent cycle runs before the Production run of migration.
How to Access House bank Accounts, after Migration.
House Bank Accounts can be accessed either by Fiori Apps or through NWBC.
We can find the fiori apps in the fiori apps library https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/home
During the initial phase of Conversion/Migration cycles – fiori set up may not be ready, possibly!
This is required only to see the house bank after migration or to set up new house bank accounts for testing.
Technical Team can help us on this set up.
  1. Set up NWBC
  2. Activate the following Webdynpro using Tcode: SICF
    1. WDA_FCLM_BAM_HIERARCHY
    2. WDA_FCLM_BAM_ACC_MASTER
    3. WDA_FCLM_UPLOAD_DOWNLOAD
  3. Assign PFCG role for example: SAP_FI_BL_BANK_MASTER_DATA to  required users.
  4. From SAP GUI, use tcode: NWBC



Please refer the below notes and references mentioned within the notes, this helps to understand any issues during migration/conversion to SAP S/4HANA.
References/SAP Notes:
  1. 2162297 – Check Configuration Before Migrating House Bank Accounts
  2. 2270400 – S4TWL – Cash Management – General
  3. 2175053 – Trouble-Shooting Note for House Bank Account Migration
  4. 2873947 – House Bank Account Migration: Prepare account type ’01’ for house bank account migration activity CM1
  5. 2874558 – House Bank Account Migration: Avoid Internal Database Error of CM1
  6. 2763559 – FCLM_BAM_MIGRATION error BF00211: “Bank & & does not exist”
  7. 2463516 – Error FCLM_BAM_MAINT057 – Cannot find configuration for Bank Account Management
  8. 2824605 – House Bank Account Migration: Number Range Object FC_ACCID Missing
  9. https://help.sap.com/doc/saphelp_sfin300/3.5/en-US/88/b30755e654eb14e10000000a4450e5/frameset.htm
  10. Fiori Apps: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/home
Postado por às Nenhum comentário:
Assinar: Postagens (Atom)