Quantcast
Channel: SCN: Message List - SAP S/4HANA
Viewing all 1361 articles
Browse latest View live

Re: New Installation of S/4HANA, confusion


ALE connection between S/4HANA Finance and ECC availability?

$
0
0

Hello, Guys:

 

I have one question about the availability of ALE connection between S/4HANA Finance (aka, Simple Finance) and remote ECC systems, is it still supported in new release will be delivered in May 2016? and for both directions? and how about the connection between S/4HANA and ECC?

 

Can you please help to clarify? Thank you in advance.

 

BR, Lawrence

Re: Error: Could not open app. Try again later - Configure your solution S4HANA

$
0
0

We have implemented SP01 for On Premise 1511.  Cleared all caches.  Installed language packs.

 

This is now working:

 

Capture.JPG

 

I can continue with my post install steps now.

Re: ALE connection between S/4HANA Finance and ECC availability?

Re: ALE connection between S/4HANA Finance and ECC availability?

$
0
0

Hi Lawrence,

 

please check the published Simplification Guides for S/4HANA.

In there you will find several explanations where ALE connections are technically possible and useful.

 

Please keep in mind that in some cases it does not make sense to setup ALE connections and exchange objects between S/4HANA and ECC due to the changes in application logic.

 

Regards Christina

Installing SAP Fiori for S/4 on Premise 1503 - Questions.

$
0
0

Hi guys

 

We are in the process of Installing Fiori Apps for S/4 On Premise 1503.

 

My main questions are:

 

Is there any difference on the deployment roadmap than a Standard ERP 6 EHP7 NW 7.4  on AnyDB?

Below there is an example of a current Fiori deploymen

 

 

SAP S/4 On Premise 1503 it does include all Fiori Backend Compoents within or should I proceed as similar as ERP 6 EHP7 / AnyDB System

 

Thanks!

 

 

 

 

Actual Fiori Deployment

 

 

Frontend system with the UI Packages

 

 

 

SAP_BASIS7400012SAPKB74012SAP Basis Component
SAP_ABA7400012SAPKA74012Cross-Application Component
SAP_GWFND7400012SAPK-74012INSAPGWFNDSAP Gateway Foundation 7.40
SAP_UI7400013SAPK-74013INSAPUIUser Interface Technology 7.40
PI_BASIS7400012SAPK-74012INPIBASISBasis Plug-In
ST-PI7400002SAPK-74002INSTPISAP Solution Tools Plug-In
SAP_BW7400012SAPKW74012SAP Business Warehouse
IW_PGW1000008SAPK-10008INIWPGWProcess Gateway
UIX01EAP1000003SAPK-10003INUIX01EAPUI for ERP Central Applications
UIX01HCM1000003SAPK-10003INUIX01HCMUI for HCM Application
UIX01TRV1000002SAPK-10002INUIX01TRVUI for Travel Application
UIX02EA41000000-UI component for ERP Applictaions 1.0
UIX02EAP1000001SAPK-10001INUIX02EAPUI for ERP Central Applications 1.0
UIX02RT41000000-UI for Retail Applications 1.0

 

 

And a actual ERP 6.0 EH7 / SQL Server with Fiori Components

 

GBAPP0026000006SAPK-60006INGBAPP002GBAPP002
GBHCM0026000012SAPK-60012INGBHCM002HCM Employee Requests (Leave)
GBHCM0036000010SAPK-60010INGBHCM003HCM Manager Approvals (Time, Training, Leave)
SRA0016000004SAPK-60004INSRA001Approve Purchasing Contracts OData Integration Component
SRA0026000005SAPK-60005INSRA002Time Recording OData Integration Component
SRA0036000001SAPK-60001INSRA003Create Travel Expenses OData Integration Component
SRA0046000004SAPK-60004INSRA004Create Travel Request OData Integration Component
SRA0066000005SAPK-60005INSRA006Remuneration Statements OData Integration Component
SRA0076000004SAPK-60004INSRA007My Benefits Enrollment OData Integration Component
SRA0086000005SAPK-60005INSRA008Approve Travel Expenses OData Integration Component
SRA0096000004SAPK-60004INSRA009Approve Travel Requests OData Integration Component
SRA0106000005SAPK-60005INSRA010Staffing List OData Integration Component
SRA0126000003SAPK-60003INSRA012My Department Spend
SRA0136000005SAPK-60005INSRA013Create Purchase Order from Released Purchase Req. OData Integration Component
SRA0166000005SAPK-60005INSRA016Price and Availability Check OData Integration Component
SRA0176000004SAPK-60004INSRA017Create Purchase Order OData Integration Component
SRA0186000004SAPK-60004INSRA018Purchase Order Status Tracking OData Integration Component
SRA0196000003SAPK-60003INSRA019Track Shipment OData Integration Component
SRA0206000005SAPK-60005INSRA020Purchase Order Status (In Process, Approved)
SRA0216000004SAPK-60004INSRA021Customer Invoices OData Integration Component

Re: Installing SAP Fiori for S/4 on Premise 1503 - Questions.

$
0
0

Hi Martin ,

 

As you are referring to 1503 , i believe you are setting up a system for S4 Finance  The implementation and architecture of fiori apps in S4Hana also remains same as in ERP 6 EHP 7 on any DB.(FactSheet apps , Analytical apps , Web Dynpro apps implementation are in addition to transactional apps)

 

The implementation process remains same for transactional apps (with/without) web dispatcher. The good thing is the reduction in installation of addons for simple finance apps.Majority of FIori SFin apps are bundled in UIAPF170 ,SAP_FIN  addons for Finance transactional apps.

 

If your front end system is based on Netweaver 7.4 + the below e add ons can be skipped.

SAP_GWFND7400012SAPK-74012INSAPGWFNDSAP Gateway Foundation 7.40
SAP_UI7400013SAPK-74013INSAPUIUser Interface Technology 7.40

 

The add ons mentioned below can be installed based on the requirement . Same applies to back end components also (Non Finance apps and logistics apps).

IW_PGW1000008SAPK-10008INIWPGWProcess Gateway (For Work Flow apps)
UIX01EAP1000003SAPK-10003INUIX01EAPUI for ERP Central Applications
UIX01HCM1000003SAPK-10003INUIX01HCMUI for HCM Application
UIX01TRV1000002SAPK-10002INUIX01TRVUI for Travel Application
UIX02EA41000000-UI component for ERP Applictaions 1.0
UIX02EAP1000001SAPK-10001INUIX02EAPUI for ERP Central Applications 1.0
UIX02RT41000000-UI for Retail Applications 1.0

 

Regards

Virinchy

Re: Installing SAP Fiori for S/4 on Premise 1503 - Questions.

$
0
0

Hi Virinchy

 

Thanks for your quick response!

 

Indeed, my frontend is running NW 7.4.

 

So I would need to Install SAPK-200AGINUIAPFI70 (UIAPFI70 200: Add-On Installation) on my frontend only since SAP_FIN 720 SP1 is already on my backend system



Re: Installing SAP Fiori for S/4 on Premise 1503 - Questions.

$
0
0

UIAPFI70 addon would work for majority of transactional apps for SFin 1503. I would suggest to cross check with Fiori apps library docs during each app implementation.


Hope you are aware that Fact Sheet , Analytical , Dynpro apps setup is additional to the above one.


Regards

Virinchy

Re: Installing SAP Fiori for S/4 on Premise 1503 - Questions.

Re: support forms to HANA S/4

$
0
0

Hi,

i cannot comment much on this as it was done by other teams.

 

Regards

Virinchy

Re: support forms to HANA S/4

$
0
0

Hi,

 

If possible please check with them and let me know.

 

 

Thanks,

Sai

Re: support forms to HANA S/4

$
0
0

Hello,

find attached the text rearding Output Management within SAP S/4HANA from the Simplification List (see SAP Help or here the direct link:  http://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdfa4322f56824ae221e10000000a4450e5/1511%20001/en-US/SIMPL_OP1511_F…

).

I hope that helps.

 

Kind Regards,

Frank

 

Output Management

Description

Over the years several output management tools have been established. Different applications are using different output management tools to determine what is to be communicated, how it is to be communicated and when it is to be communicated. Additionally if communication is determined to be done via printing different print form technologies have been established like SAPScript, Smart Forms and Adobe Form technology. E.g. form determination (along with other output parameters) is done via message determination (NAST) in SD and MM while other applications use different output management technologies e.g. FIN. E.g. the output management based on NAST support the following

  • Print Channels:   
    • Print output
    • Fax
    • Telex
    • External send
    • EDI
    • Simple Mail
    • Special function
    • Events (SAP Business Workflow)
    • Distribution (ALE)
    • Tasks (SAP Business Workflow) 
  • Print Technologies:
    • SAPScript
    • SmartForms
    • Adobe Forms

  There is a new and modern Output Management within SAP S/4HANA. The new output management by design includes cloud qualities like extensibility enablement, multi tenancy enablement and modification free configuration. Therefore the complete configuration differs from configuration that is used when output management is based on NAST. The configuration is based on BRF+ which is accessible for Customers on premise. Information about the configuration steps are available in the CSS note 2228611. In SAP S/4HANA the target architecture is based on Adobe Document Server and Adobe Forms only. For the form determination rules (along with other output parameters) BRF+ functionality is used (in this sense in combination with the message determination).  

  • Print Channel: The SAP S/4HANA Output Management supports the following Channels:
    • Email
    • Printout
    • XML
  • Print Technology: The SAP S/4HANA Output Management supports the following print technologies: 
    • SmartForms
    • Adobe Forms
    • Adobe Forms using Fragments 

  Regarding the forms especially footer and Logos for the new output management: 

  • The standard SAPScript Repository is used (Transactions: SO10 and SE78). A customer can maintain texts and logos centrally. The determination rules can be accessed via Customizing. The access is available for Customers on premise (and for Service Center in the cloud edition).

ABAP CDS Views: Associations & Joins - best practice advice

$
0
0

According to the ABAP Keyword Documentation it is desirable to use associations instead of joins when creating ABAP CDS views.

 

When you have a classical data vault model with Hubs and Satellites this approach is easy:

1.png

Just associate all satellites to the hub.

More often I face a situation like this:

2.png

The information of a logical entity requires several joins chained into each other, because the logical entity strechtes among several hubs (it is probably wrong to call them hubs now).

As I understand it, ABAP CDS views dont support chained associations. Thus there are two ways to model this using ABAP CDS:
1) Use one View: Join HUB1 and HUB2, then associate all satellites.
2) Use two Views: The first starts with HUB2 and associates Satellite2 and Satellite3. The second starts with HUB1 and associates the previous view as well as Satellite1.

Which one is the better way?

 

When thinking about link tables, the situation seems more obvious:

3.png

Create a consolodated view starting with the Link table and associating the two CDS views to it. Once again it gets more complicated when a chain of several Link tables is required.

 

Using this approach of nesting CDS views, one easily creates a stack of 5 to 10 CDS views on top of each other. Does this have a negative impact on the evulation of the views compared to just using joins?

Recommended browser for S/4 HANA fiori apps

$
0
0

Hi,

 

Is there a recommended web browser by SAP for the apps that come with S/4 HANA?

 

From a debugging/developer point of view which web browser is will suited for Fiori apps in general?

 

 

Regards,
Ramesh-


Re: Recommended browser for S/4 HANA fiori apps

$
0
0

The different browsers and mobile devices support for Fiori apps are listed here . From Developer point of view i would always go with Chrome as first and Firefox as second.

 

Chrome also wins from the apps performance . At times enterprises have restrictions with browser versions and availability , so please have a look at the added snote.

 

Regards

Virinchy

Re: Operational Reporting in S/4 HANA

Re: S/4 HANA 1511, Operational reporting

Re: support forms to HANA S/4

$
0
0

Hi,

 

Thanks for your information.

 

 

Regards,

Sai

Re: support forms to HANA S/4

$
0
0

Hi,

 

you meant to say it can support only smartforms and adobe forms not scripts.

 

is there any preconfigurations to generate froms?

 

 

Thanks,

Sai

Viewing all 1361 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>