App Implementation: Create Sales Orders

System Landscape Requirements

Before you can start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori and that this system landscape already includes the front-end components and back-end components for your app:

SAP Fiori System Landscape Options	Setup of SAP Fiori System Landscape with ABAP Environment Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS
Configuration of Front-End Server	Configuration of SAP Fiori Infrastructure
Back-End Components Delivered with (Product Version Stack)	SAP enhancement package 7 for SAP ERP 6.0 SPS 8 or higher Note If you have not implemented the latest SPS level in your back-end system, you have to ensure that all SAP notes for your selected apps have been implemented there. You can find an overview of the available SAP notes in the release information note 1737650. End of the note.
Front-End Components Delivered with (Product Version Stack)	SAP Fiori 1.0 for SAP ERP SPS 6 or higher Note If you have not implemented the latest SPS level on your front-end server, you have to ensure that the respective SAP notes for your selected apps have been implemented there. You can find an overview of the available SAP notes in the release information note 1914499. End of the note.

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP:

Back-End/Front-End Server	Back-End/Front-End Component	Technical Name of Software Component	Support Package Level
Front-end server	Front-end component	UIX01EAP 100	8
Back-end server	Back-end component	SRA017 600	8

Required SAP Notes

For the Create Sales Orders app, the following SAP Note must be implemented:

Back-End/Front-End Server	SAP Note Number	Description
Back-End and Front-End Server	1942941	Release Note for the ERP SD FIORI application - Create Sales Orders

Implementation Tasks

The following sections list tasks that have to be performed to implement the Create Sales Orders 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=F0018.

Front-End Server: Activate OData Services

Component	Technical Name
OData Service (Version Number)	SRA017_SALESORDER_CREATE_SRV

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application

Component	Technical Name
SAP UI5 Application	SD_SO_CRE

For more information about how to activate the ICF service, see Front-End Server: Activate ICF Services of SAPUI5 Application (for transactional apps) or Activate ICF Service of BSP Application (fact sheets).

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.

Component	Technical Name
Semantic Object	SalesOrder
Business Role	SAP_SD_BCR_FIELDSALESREP_X1
Business Catalog	SAP_SD_BC_FIELDSALESREP_X1
Business Catalog Group	SAP_SD_BCG_FIELDSALESREP_X1
Technical Role	SAP_SD_TCR_T_X1
Technical Catalog	SAP_SD_TC_T_X1
LPD_CUST Role	UIX01SD
LPD_CUST Instance	TRANSACTIONAL

Front-End and Back-End Server: Assign Role with OData Service Authorization to Users

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

Caution Caution

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.

End of the caution.

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. For more information, see Back-End Server: Assign OData Service Authorization to Users.
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. For more information, see Add Start Authorizations for OData Services to Role on Front-End and Front-End Server: Assign Roles to Users.

OData Service (Version Number)	Back-End Server: Delivered Authorization Role (PFCG Role)	Front-End Server: Authorization Role
SRA017_SALESORDER_CREATE_SRV	SAP_SD_SO_CRE_APP Note In addition, this role contains authorizations to display the related business data. End of the note.	SAP_SD_BCR_FIELDSALESREP_X1

Prerequisites for Implementation

Before you implement the Create Sales Orders app, ensure to 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.

End of the note.

Configuration Tasks

To enable Create Sales Orders, perform these configuration tasks:

Call transaction SIMGH and open the Create 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)
  This defines which partner role in the customer master is used for the forwarding agent. The suggested value is SP.
Implement the following BAdIs:
- Customer Association to Employee (BADI_SRA017_USER_TO_CUSTOMER)
  You can use this BAdI to fetch a list of customers associated with a specific employee.
- Retrieve Product Image (BADI_SRA017_PROD_IMG_RETRIEVER)
  You can use this BAdI to retrieve the image of a product. It does not have a default implementation.

More Information

For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.