Show TOC

App Implementation: Change Shipping AddressLocate this document in the navigation structure

System Landscape Requirements

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. Depending on the database type serving as the basis in your system landscape, it has to be set up for SAP Fiori and has to meet the respective prerequisites:

The SAP product version in the back-end system serving as the the basis for the app must be the following:

Required Back-End Product (Product Version Stack)

  • EHP2 FOR SAP ERP 6.0 - SPS 05 (02/2009)
  • EHP3 FOR SAP ERP 6.0 - SPS 05 (08/2009)
  • EHP4 FOR SAP ERP 6.0 - SPS 05 (11/2009)
  • EHP4 FOR SAP ERP 6.0 / NW7.01 - SPS 05 (11/2009)
  • EHP5 FOR SAP ERP 6.0 - SPS 03 (12/2010)
  • EHP6 FOR SAP ERP 6.0 - SPS 01 (11/2011)
  • SAP ERP 6.0 - SPS 15 (02/2009)
  • EHP7 FOR SAP ERP 6.0 - SPS 01 (08/2013)
Each SAP Fiori app consists of front-end components and back-end components:
  • The front-end components of the app consist of the user interfaces and content required for launching the app on the SAP Fiori launchpad. These components have to be installed on your front-end server.

  • The back-end components of the app mainly consist of the OData services required for the app. These components have to be installed in your back-end system.

The front-end and back-end components of the app are delivered with the following SAP product versions as part of the listed software components. The required software components for the app are contained in the listed product instances:

App Component

Required SAP Product Version (Support Package Stack)

Available Instances Containing Software Component

Software Component Required for App (Support Package)

Front-End Components

SAP Fiori principal apps 1.0 for SAP ERP ( 06 (04/2015) )
  • Central App UI NW731
  • Central App UI NW740

UIX01EAP 100 (0006 )

Back-End Components

SAP Fiori principal apps 1.0 for SAP ERP (06 (04/2015))

  • Central App INT
  • Central App INT NW740

SRA018 600 (0007 )

For more information about the installation of front-end components, see http://help.sap.com/fiori_implementation.

The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your respective back-end system and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information about virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.

Required SAP Notes

On the back-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

1942983 Information published on SAP site

Release Note for the ERP SD Fiori application - Change Sales Order

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

1942983 Information published on SAP site

Release Note for the ERP SD Fiori application - Change Sales Order

Implementation Tasks

The following sections list tasks that have to be performed to implement the required components of the app. The tables contain the app-specific data required for these tasks.

You can find the data required to perform these tasks in the SAP Fiori apps reference library at:

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0019

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

SRA018_SO_TRACKING_SRV (001 )

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAP UI5 Application

Component

Technical Name

SAP UI5 Application

SD_SO_MAN

For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services.

Enable App for Access in SAP Fiori Launchpad

To define the access of single users to this app in the SAP Fiori launchpad, technical content is delivered, such as catalogs and example roles.

You can find an overview of the delivered technical content for this SAP Fiori app in the SAP Fiori apps reference library.

For more information about how to procede with this content, see Enable App for Access in SAP Fiori Launchpad.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

Note

Several authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server :
  • On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.

  • On the front-end server , you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.

OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server : Assignment to Authorization Role

SRA018_SO_TRACKING_SRV (001 )

In addition, this role contains authorizations to display the related business data.

  • SAP_SD_SO_MAN_APP

Note

In addition, this role contains authorizations to display the related business data.

OData service authorization must be assigned.

Prerequisites for Implementation

Before implementing the app, you must ensure the following:

You must create an employee master record as follows:

  • Implement SAP ERP HCM to maintain employees in the HCM personnel records with the infotype Communication (0105) and the subtype (0001) of System User Name SY-UNAME.

  • If you have not done this, implement the Sales and Distribution configuration with Use Sales Employees with HR (Tcode: PULT). This IMG setting copies the appropriate HCM tables from the 000 Client and allows the setup of the employee record with the above infotype and subtype.

    Note

    This associates the employee's user ID with a personnel number that is assigned as the sales employee partner function in the customer master.

Configuration Tasks

To be able to implement the app, you must perform the following configuration tasks in the back-end system:

  1. Call the transaction SIMGH and open the Change Shipping Address node. By default, the change order functionality is disabled and the value of this parameter is not entered. To enable this functionality, enter X as the value for the EDITENABLED parameter.

  2. Call the transaction SIMGH and open the Track Sales Orders node to configure user information parameters of the Customizing activity Define Configuration Parameters:

    • Document Type (DOCTYPE)

      By default, the app uses the standard order (TA/OR). Changing this to another document type may significantly impact the functionality of the application.

    • Order Period (ORDPERIOD)

      Defines how many days into the past sales orders are retrieved. The suggested value is 30 days.

    • Search Period (SEAPERIOD)

      Defines how many days into the past a search must look for sales orders that match the search criteria. The suggested value is 90.

    • Ship To Party (SHIP_TO/PARTNER_ROLE)

      Defines which partner role in the customer master is used for the ship-to party. The suggested value is WE.

    • Forwarding Agent (FORWARDING_AGENT/PARTNER_ROLE)

      Defines which partner role in the customer master is used for the forwarding agent. The suggested value is SP.

    Note

    Refer to the customizing activity documentation for more information.

  3. Implement the Customizing activity Define Additional Sales Order Document Types to define additional document types than the default standard order(TA).

  4. Implement the BAdI: Customer Association to Employee (BADI_SO_USR_TO_CUSTOMER) to associate employees with a specific customer.

More Information

For more information about app implementation, see http://help.sap.com/fiori_implementation Start of the navigation path App Implementation Information for SAP Fiori End of the navigation path.