Up1 Scrp30 Bpd en Xx

Test ScriptSAP Screen Personas 3.0June 2015English

CUSTOMER

Sales Order Processing with SAP Screen PersonasUP1

Table of Contents

1 Test Description 4

2 Prerequisites 52.1 Association to Sales Order Processing: Sell from Stock (109) 52.2 System Access and Roles 52.3 Master Data, Organizational Data, and Other Data 62.4 Business Conditions 7

3 Overview Table 9

4 Test Procedures 104.1 Test Generic Example Flavors 10

4.1.1 Start Sales Order Processing Landing Page 104.1.2 Create Sales Order with Generic Example Flavor 114.1.3 Create Delivery with Generic Example Flavor 124.1.4 Check Batches with Generic Example Flavor 134.1.5 Assign Serial Numbers with Generic Example Flavor 154.1.6 Post Goods Issue with Generic Example Flavor 164.1.7 Create Billing with Generic Example Flavor 17

4.2 Test Fiori Flavors 184.2.1 Start Sales Order Processing Launchpad194.2.2 Create Sales Order with Fiori Flavor 204.2.3 Create Delivery with Fiori Flavor214.2.4 Check Batches and Assign Serial Numbers with Fiori Flavor 224.2.5 Assign Serial Numbers with Fiori Flavor 234.2.6 Post Goods Issue with Fiori Flavor 25

4.2.7 Create Billing with Fiori Flavor 26

5 Appendix 285.1 Process Integration 28

5.1.1 Preceding Processes 28

Sales Order Processing with SAP Screen Personas

Typographic Conventions

CUSTOMER

© 2015 SAP SE OR AN SAP AFFILIATE COMPANY. ALL RIGHTS RESERVED. 2

Document History

Revision Change Date Description

0 June 8, 2015 Published version

Note for the customer project team: Instructions for the customer project team are highlighted in yellow and should be removed before hand -over to project testers. The appendix is included for internal reference, in particular to support A2O, and should also be deleted before hand-over to the customer, unless deemed helpful to explain the larger context.

If there are any special requirements that do not fit into the template, add instructions to the appendix.


Appendix

CUSTOMER


1 Test Description

This scope item provides example SAP Screen Personas flavors for transactions to process a standard sales order for a customer. The example flavors are provided in two different design versions:

Generic Example Flavors

Fiori Flavors

This document provides a detailed procedure for testing the scope item Sales Order Processing with SAP Screen Personas after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be added.


Appendix

CUSTOMER


2 Prerequisites

This section summarizes all prerequisites to conducting the test in terms of systems, users, master data, organizational data, and other test data and business conditions.

2.1 Association to Sales Order Processing: Sell from Stock (109)

Scope item Sales Order Processing with SAP Screen Personas (UP1) reflects the mandatory process steps of the business process included in Sales Order Processing: Sell from stock (109) configured using SAP Screen Personas 3.0. Therefore in order to fully utilize the process steps in this scope item, it is recommended that you are familiar with the scope item Sales Order Processing: Sell from stock (109) and follow the prerequisites for that scenario.

2.2 System Access and Roles

The test is conducted in the following systems:

System Details

SAP ERP <Provide details on how to access system, e.g. system client or URL>

Use the following standard test users or assign roles to testers, respectively:

Business Role Business Role Description Business Role ID Log On

Employee (Professional User) Assignment of this role is necessary for basic functionality.

SAP_NBPR_EMPLOYEE_S Test user: <userid>

Password: <password>

SAP Screen Personas standard user

Assignment of this role is necessary to use SAP Screen Personas to execute the transactions in the business process

/PERSONAS/CONSUMER_ROLE Test user: <userid>


Sales Administrator SAP_NBPR_SALESPERSON_S Test user: <salesperson_userid>


Warehouse Clerk SAP_NBPR_WAREHOUSECLERK_S Test user: <warehouse_clerk_userid>


Billing Administrator SAP_NBPR_BILLING_S Test user: <billing_userid>


Appendix

CUSTOMER


Business Role Business Role Description Business Role ID Log On


2.3 Master Data, Organizational Data, and Other Data

The organizational structure and master data of your company has been created in your system during activation. The organizational structure reflects the structure of your company. The master data represents materials, customers, and vendors, for example, depending on the operational focus of your company.

Use your own master data to go through the test procedure. If you have installed an SAP Best Practices baseline package, you can use the following baseline package sample data:

Note

The master data used is the same as for the scenario Sales Order Processing: Sell from stock (109).

If you are using these master data, ensure that you carry out the activities listed in Preliminary Steps in the document Sales Order Processing: Sell from stock (109).

Data Sample Value Details Comments

Material H11 Trading Good for Reg. Trading (MRP planning)

no Serial no.; no batch

Material H12 Trading Good for Reg. Trading (reorder point planning)

no Serial no.; no batch


with serial numbers, no batch

You must have activated Serial Number Management.

Example

You have activated the building block Serial Number Management (126).


no Serial no.; batch controlled (Exp. Date)

You must have activated Batch Management.

Example

You have activated the building block


Appendix

CUSTOMER


Data Sample Value Details Comments

Batch Management (117).


no Serial no.; batch controlled (FIFO strategy)


Example

You have activated the building block Batch Management (117).

Material F29 Finished Good MTS for Process Industry (PD planning)

no Serial no.; with batch (Exp. Date)


Example

You have activated the building block Batch Management (117).

Material F126 Finished Good MTS for Discrete Industry (PD planning)

with Serial no.; with / w/o batch (FIFO strategy)

You must have activated Serial Number Management.

Example

You have activated the building block Serial Number Management (126).

Sold-to party 493000 Customer Company 02 You can test the scope item using another customer.

Ship-to party 493000 Customer Company 02

Payer 493000 Customer Company 02

Plant 1000 (1100)

Shipping Point 1000 (1100)

Sales organization 1000

Distribution channel 10

Division 10

2.4 Business Conditions

Before this scope item can be tested, the following business conditions must be met.


Appendix

CUSTOMER


Business Condition Comment

1 Relevant SAP Screen Personas flavors have been created for all transactions in the business process.

Note

The scenario Sales Order Processing: Sell from stock (109) contains several business conditions that are prerequisites for that scenario. These steps are not provided with example SAP Screen Personas flavors, nor do they form part of the solution for SAP Screen Personas.


Appendix

CUSTOMER


3 Overview Table

The scope item Sales Order Processing with SAP Screen Personas consists of several process steps, provided in the table below.

Process Step Business Role Transaction Expected Results

Start Sales Order Processing Landing Page

Employee (Professional User)

SMEN -

Create Sales Order with Generic Example Flavor

Sales Administrator VA01 Sales Order is created.

Create Delivery with Generic Example Flavor

Warehouse Clerk VL10, VL01N Delivery is created. The Warehouse Transfer Order is created.

Check Batches and Assign Serial Numbers with Generic Example Flavor

Warehouse Clerk VL02N -

Post Goods Issue with Generic Example Flavor

Warehouse Clerk VL06O The goods issue is posted.

Create Billing with Generic Example Flavor

Billing Administrator VF04, VF01 Billing is carried out.

Start Sales Order Processing Launchpad Employee (Professional User)

SMEN -

Create Sales Order with Fiori Flavor Sales Administrator VA01 Sales Order is created.

Create Delivery with Fiori Flavor Warehouse Clerk VL10, VL01N Delivery is created. The Warehouse Transfer Order is created.

Check Batches and Assign Serial Numbers with Fiori Flavor

Warehouse Clerk VL02N -

Post Goods Issue with Fiori Flavor Warehouse Clerk VL06O The goods issue is posted.

Create Billing with Fiori Flavor Billing Administrator VF04, VF01 Billing is carried out.


Appendix

CUSTOMER


4 Test Procedures

This section describes test procedures for each process step that belongs to this scope item.

The test should take around 60 minutes.

4.1 Test Generic Example Flavors

This process exclusively uses the generic example flavors for Sales Order Processing.


4.1.1 Start Sales Order Processing Landing Page

Test Administration

Customer project: Fill in the project-specific parts (highlighted).

Test Case ID <X.XX> Tester Name Testing Date Click here to enter a date.

Business Roles Employee (Professional User)

Responsibility <State Service Provider, Customer, or Joint Service Provider and Customer> Duration 5 minutes

Purpose

In this process step you access the Sales Order Processing Landing Page in the Web browser. This is the starting point to access each of the transactions in the process.

Note

Each business role uses the landing page to access the transactions for which they are responsible.


Appendix

CUSTOMER


Procedure

Test Step #

Test Step Name Instruction Expected Result Pass / Fail / Comment

1. Log on using Web browser You log on to the system using a Web browser with the correct URL address

You have logged on to the system and the initial transaction is displayed in the Web browser session.

2. Navigate to landing page Navigate to the transaction for the landing page.

The landing page for Sales Order Processing is displayed

4.1.2 Create Sales Order with Generic Example Flavor

Test Administration



Business Roles Sales Administrator

Responsibility <State Service Provider, Customer, or Joint Service Provider and Customer> Duration 5 Minutes

Purpose

In this process step you enter a sales order.

Procedure

Test Step #


1. Start Create Sales Order In the landing page for Sales Order Processing, choose You are directed to the overview screen


Appendix

CUSTOMER


Test Step #


transaction Enter button below the text Create Sales Order. for the transaction Create Sales Order.

2. Enter customer In the Sold-To-Party field, enter the customer number <Sold-To-Party>.

The customer number is displayed in Sold-To-Party

3. Enter purchase order number

Enter a customer purchase order number as a reference The Customer purchase order number is displayed.

4. Enter payment terms In the Payment terms field, enter the payment terms.

Example

0003 14 days 3%, 20/2%, 30 net

The Terms of Payment Key and the Description of terms of payment are displayed.

5. Enter material and order quantity

Enter <Material> in Material, and <Quantity>.

Example

Enter H11 or H20 (for serial number assignment) or F29 (for batch assignment) in Material;

Enter 5 in Order Quantity.

The material id, order quantity, and unit are displayed in the order item

6. Save order Choose Save. You have saved the sales order.

Note

Make a note of the sales order number:

_______________.

4.1.3 Create Delivery with Generic Example Flavor

Test Administration



Business Roles Warehouse Clerk


Appendix

CUSTOMER



Purpose

In this process step you create the delivery.

Prerequisites

Sufficient quantities of the materials are available for delivery. You can maintain this in Goods Receipt Other (transaction MIGO).

Note

For further information on this process, refer to section Preliminary Steps in Sales Order Processing: Sale from Stock (109).

Procedure

Test Step #


1. Start Create Delivery transaction

In the landing page for Sales Order Processing, choose the Enter button below the text Create Delivery.

You are directed to the initial screen for the transaction Create Delivery.

2. Create delivery In the Sales Document field, enter the <Sales Order Number> and choose Execute.

You are directed to the overview screen of the order.

3. Choose Activities Due for Shipping

Select the sales order document in the list Activities Due for Shipping: Sales Order and choose Execute in Dialog.

You have selected the sales order to create a delivery.

4. Enter Delivery Quantity If necessary, in the Create Outbound Delivery screen, in the Deliv. Qty column, enter the delivery quantity for each item in the outbound delivery.

5. Save Delivery Choose Save. You have saved the delivery document.

Note

Make a note of the delivery


Appendix

CUSTOMER


Test Step #


number:

_______________.

4.1.4 Check Batches with Generic Example Flavor

Test Administration





Purpose

In this process step you check batches for the materials in the delivery document.

Prerequisites

Use this step if batch management is activated.

You can only execute this step for a material with batches.

Example

Material F29.


Appendix

CUSTOMER


Procedure

Test Step #


1. Start Check Batches/Assign Serial Numbers transaction

In the landing page for Sales Order Processing, choose the Enter button below the text Check Batches Assign Serial Numbers.

You are directed to the initial screen to check batches and assign serial numbers.

2. Enter Outbound Delivery Number

In the Outbound Delivery field, enter the <Outbound Delivery Number> and choose Enter.

You are directed to the overview screen of the delivery.

3. Select an Item with a Batch Split

Select an item for which a batch split exists.

Note

The batch split indicator is represented by an icon in the Batch Split Indicator column.

You have selected an item with a batch split.

4. Display Batch Split Choose Batch Split. You are directed to the overview screen of the batch split.

5. Check Batch Number Assignment

In Batch split items, check the batch number assignment in the Batch field.

You have checked the batch assignment.

6. Save Batch Number Assignment

Choose Save. You have saved the batch assignment.

4.1.5 Assign Serial Numbers with Generic Example Flavor

Test Administration






Appendix

CUSTOMER


Purpose

In this process step you carry out serial number assignment for the materials in the delivery document.

Prerequisites

You can only execute this step for a material with serial number assignment.

Example

Material H20.

Procedure

Test Step #


1. Start Check Batches/Assign Serial Numbers transaction

In the landing page for Sales Order Processing, choose Enter in the button below the text Check Batches Assign Serial Numbers.





3. Select an Item with Serial Numbers

Select an item for which a serial number is maintained.

Example

Material H20.

You have selected an item with serial numbers.

4. Choose Serial Numbers Choose Serial Numbers. The Maintain Serial Numbers dialog box is displayed.

5. Create Serial Numbers Automatically

Choose Cre… (Create serial number automatically – Create serial numbers automatically)

You have created serial numbers for the selected item of the delivery order.

6. Assign Numbers and Save

Choose Continue and Save The serial numbers are assigned to the item. Save the delivery order to persist your changes.


Appendix

CUSTOMER


4.1.6 Post Goods Issue with Generic Example Flavor

Test Administration





Purpose

In this process step you post the goods issue.

Prerequisites

In order to render the ABAP List Viewer (ALV) screen in an SAP Screen Personas flavor, the list type must be set to Grid Control.

Procedure

Test Step #


1. Start Post Goods Issue transaction

In the landing page for Sales Order Processing, choose the Enter button below the text Post Goods Issue.

You are directed to the initial screen for posting goods issue.

2. Enter Shipping Point In Shipping Point/Receiving Point, enter the value for <Shipping Point> and choose Execute.

Example

Enter 1000 for Shipping Point/Receiving Point.

The list of outbound deliveries to be posted is displayed.

Caution

The list is displayed in ALV format.

3. Select Order for Goods Issue

Select the delivery order and choose Post Goods Issue.


Appendix

CUSTOMER


Test Step #


4. Specify Actual Goods Issue Date

Choose today’s date in the dialog box and choose Continue.

You have posted the goods issue for the outbound delivery.

4.1.7 Create Billing with Generic Example Flavor

Test Administration



Business Roles Billing Administrator


Purpose

In this process step you handle the billing for the order.

Procedure

Test Step #


1. Start Create Billing transaction

In the landing page for Sales Order Processing, choose the Enter button below the text Create Billing.

You are directed to the initial screen for billing.

2. Search for Billing Documents

Enter the relevant search criteria and choose Display Bill List.

Example

Enter dates in Billing Date From and to in order

The Maintain Billing Due List is displayed.


Appendix

CUSTOMER


Test Step #


to search for documents according to date.

3. Create Individual Billing Document

Select the respective billing document and choose Individual Billing.

The Create Invoice screen is displayed.

4. Create Invoice In Create Invoice: Overview of Billing Items, choose Save.


Note

The status of the document is displayed as OK (icon with green tick).

5. Leave Billing Choose Back twice to return to the landing page. You have created an invoice for the order.

4.2 Test Fiori Flavors

This process exclusively uses the Fiori flavors for Sales Order Processing.


4.2.1 Start Sales Order Processing Launchpad

Test Administration



Business Roles Employee (Professional User)

Responsibility <State Service Provider, Customer, or Joint Service Provider and Customer> Duration 5 minutes


Appendix

CUSTOMER


Purpose

In this process step you access the Sales Order Processing Launchpad in the Web browser. This is the starting point to access each of the transactions in the process.

Note

Each business role uses the Launchpad to access the transactions for which they are responsible.

Procedure

Test Step #


1. Log on using Web browser You log on to the system using a Web browser with the correct URL address

You have logged on to the system and the initial transaction is displayed in the Web browser session.

2. Navigate to Launchpad Navigate to the transaction for the Launchpad.

The Launchpad for Sales Order Processing is displayed

4.2.2 Create Sales Order with Fiori Flavor

Test Administration



Business Roles Sales Administrator


Purpose

In this process step you enter a sales order.


Appendix

CUSTOMER


Procedure

Test Step #


1. Start Create Sales Order transaction

In the Sales Order Processing Launchpad, choose the tile Create Sales Order.

You are directed to the initial screen for the transaction Create Sales Order.

2. Enter customer In the field Sold-To-Party, enter the customer number <Sold-To-Party>.

The customer number is displayed in Sold-To-Party

3. Enter purchase order number

Enter a customer purchase order number as a reference The Customer purchase order number is displayed.

4. Enter payment terms In the Payment terms field, enter the payment terms.

Example

0003 14 days 3%, 20/2%, 30 net

The Terms of Payment Key and the Description of terms of payment are displayed.

5. Enter material and order quantity

Enter <Material> in Material, and <Quantity>.

Example

Enter H11 or H20 (for serial number assignment) or F29 (for batch assignment) in Material;

Enter 5 in Order Quantity.

The material id, order quantity, and unit are displayed in the order item

6. Save order Choose Save. You have saved the sales order.

Note

Make a note of the sales order number:

_______________.

4.2.3 Create Delivery with Fiori Flavor

Test Administration



Appendix

CUSTOMER





Purpose

In this process step you create the delivery.

Procedure

Test Step #


1. Start Create Delivery transaction

In the Sales Order Processing Launchpad, choose the tile Create Delivery.

You are directed to the initial screen for the transaction Create Delivery.

2. Create delivery In the Sales Document field, enter the <Sales Order Number> and choose Execute.

You are directed to the overview screen of the order.

3. Choose Activities Due for Shipping

Select the sales order document in the list Activities Due for Shipping: Sales Order, Fast Display and choose Execute in Dialog.

You have selected the sales order to create a delivery.

4. Enter Delivery Quantity If necessary, in the Create Outbound Delivery screen, in the Deliv. Qty column, enter the delivery quantity for each item in the outbound delivery.

5. Save Delivery In the Create Outbound Delivery screen, choose Save. You have saved the delivery document.

Note

Make a note of the delivery number:

_______________.


Appendix

CUSTOMER


4.2.4 Check Batches with Fiori Flavor

Test Administration





Purpose

In this process step you check batches for the materials in the delivery document.

Prerequisites

Use this step if batch management is activated.

You can only execute this step for a material with batches.

Example

Material F29.

Procedure

Test Step #


1. Start Assign Serial Numbers transaction

In the Sales Order Processing Launchpad, choose the tile Check Batches Assign Serial Numbers.






Appendix

CUSTOMER


Test Step #



Select an item for which a batch split exists.

Note

The batch split indicator is represented by an icon in the Batch Split Indicator column.



5. Check Batch Number Assignment

In Batch split items, check the batch number assignment in the Batch field.

You have checked the batch assignment.

6. Save Batch Number Assignment

Choose Save. You have saved the batch assignment.

4.2.5 Assign Serial Numbers with Fiori Flavor

Test Administration





Purpose

In this process step you carry out serial number assignment for the materials in the delivery document.

Prerequisites

You can only execute this step for a material with serial number assignment.Sales Order Processing with SAP Screen Personas

Appendix

CUSTOMER


Example

Material H20.

Procedure

Test Step #


1. Start Check Batches Assign Serial Numbers transaction

In the Sales Order Processing Launchpad, choose the tile Check Batches Assign Serial Numbers.






Select an item for which a serial number is maintained.

Example

Material H20.



5. Select Item for Batch Assignment

In Batch Structure for Item <item number>, choose the item for the batch assignment.

Note

The item with the batch number has batch number displayed in Batch column.

You have selected the batch for serial assignment.

6. Create Serial Assignments

Choose Create Serial Assignments. You have created serial assignments for the delivery order.


Appendix

CUSTOMER


4.2.6 Post Goods Issue with Fiori Flavor

Test Administration





Purpose

In this process step you post the goods issue.

Prerequisites

In order to render the ABAP List Viewer (ALV) screen in an SAP Screen Personas flavor, the list type must be set to Grid Control.

Procedure

Test Step #


1. Start Post Goods Issue transaction

In the Sales Order Processing Launchpad, choose the tile Post Goods Issue.

You are directed to the initial screen for posting goods issue.

2. Enter Shipping Point In Shipping Point/Receiving Point, enter the value for <Shipping Point> and choose Execute.

Example

Enter 1000 for Shipping Point/Receiving Point.

The list of outbound deliveries to be posted is displayed.

Caution

The list is displayed in ALV format.

3. Select Order for Goods Issue

Select the delivery order and choose Post Goods Issue.


Appendix

CUSTOMER


Test Step #


4. Specify Actual Goods Issue Date

Choose today’s date in the dialog box and choose Continue.

You have posted the goods issue for the outbound delivery.

4.2.7 Create Billing with Fiori Flavor

Test Administration



Business Roles Billing Administrator


Purpose

In this process step you handle the billing for the order.

Procedure

Test Step #


1. Start Create Billing transaction

In the Sales Order Processing Launchpad, choose the tile Create Billing.

You are directed to the initial screen for billing.

2. Search for Billing Documents

Enter the relevant search criteria and choose Display billing list.

Example

Enter dates in Billing Date From and to in order



Appendix

CUSTOMER


Test Step #


to search for documents according to date.

3. Create Individual Billing Document

Select the respective billing document and choose Individual billing.

The Create Invoice screen is displayed.

4. Create Invoice In Create Invoice: Overview of Billing Items, choose Save.


Note

The status of the document is displayed as OK (icon with green tick).

5. Leave Billing Choose Back twice to return to the landing page. You have created an invoice for the order.


Appendix

CUSTOMER


5 Appendix

5.1 Process Integration

The process to be tested in this test script is part of a chain of integrated processes.

5.1.1 Preceding Processes

You may first have completed the following processes and conditions before you start with the test steps:

Process Business Condition

Best Practices for SAP Screen Personas Development (UP0)

Development of SAP Screen Personas flavors.


Appendix

CUSTOMER



Appendix

CUSTOMER


Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade, and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .


Appendix

CUSTOMER


www.sap.com/contactsap

© 2015 SAP SE or an SAP affiliate company. All rights

reserved.

No part of this publication may be reproduced or transmitted

in any form or for any purpose without the express

permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of SAP SE (or an SAP affiliate company) in

Germany and other countries. Please see

http://global.sap.com/corporate-en/legal/copyright/index.epx

#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its

distributors contain proprietary software components of other

software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate

company for informational purposes only, without

representation or warranty of any kind, and SAP SE or its

affiliated companies shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP SE

or SAP affiliate company products and

services are those that are set forth in the express warranty

statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an

additional warranty.

In particular, SAP SE or its affiliated companies have no

obligation to pursue any course of business outlined in this

document or any related presentation, or to develop or

release any functionality mentioned therein. This document,

or any related presentation, and SAP SE’s or its affiliated

companies’ strategy and possible future developments,

products, and/or platform directions and functionality are all

subject to change and may be changed by SAP SE or its

affiliated companies at any time for any reason without

notice. The information in this document is not a

commitment, promise, or legal obligation to deliver any

material, code, or functionality. All forward-looking

statements are subject to various risks and uncertainties that

could cause actual results to differ materially from

expectations. Readers are cautioned not to place undue

reliance on these forward-looking statements, which speak

only as of their dates, and they should not be relied upon in

making purchasing decisions.

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark