You are on page 1of 16

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC

Purpose Error: Reference source not found 1

Test Script PUBLIC


SAP S/4HANA Cloud - 11-07-19

Intercompany Processes - Project-Based Services


(16T_SG)

Table of Contents

1 Purpose

2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
2.4 Business Conditions

3 Overview Table

4 Test Procedures
4.1 Time and Expenses Intercompany Settlement
4.1.1 Check Intercompany Sales Order
4.1.2 Create Customer/Internal Project
4.1.3 Time Recording
4.1.4 Create Supplier Invoice for Travel Expenses of Intercompany Resource
4.1.5 Generate Intercompany Billing Request
4.2 Invoicing
4.2.1 Create Intercompany Invoice
Intercompany Processes - Project-Based Services (16T_SG) PUBLIC
Purpose Error: Reference source not found 2
1 Purpose

A company has an affiliate company. The affiliate company delivers a service to the ordering company in the course of a customer project. The affiliate company posts expenses and records time on
the project. These expenses are transformed into debit memo requests. An intercompany invoice with reference to the debit memo request is created by the delivering company. The intercompany in-
voice is posted automatically also to the accounts payables of the ordering company.
The intercompany process described here is sample data.
● The ordering company is DE.
● The delivering company is US.
The scenario is restricted to one direction: US delivers services for DE.
If you want to apply Inter Company for other countries, please adapt country-specific data. This scope item describes the entire process sequence for the intercompany process for professional ser-
vices.
Both country solutions for DE and US have to be activated to support the intercompany process. The intercompany process is only applicable for the two countries DE and US, not for any other
countries.
This document provides a detailed procedure for testing this scope item 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.

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 3
2 Prerequisites

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

2.1 System Access

System Details
System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.

2.2 Roles
Assign the following business roles to your individual test users.
Note The following roles are provided as example roles from SAP. You can use these as templates to create your own roles.

Business Role Business Role ID as Delivered by SAP Log On


Internal Sales Representative - Professional Services SAP_BR_INTERNAL_SALES_REP_PRSV

Billing Clerk SAP_BR_BILLING_CLERK

Project Manager - Commercial Services SAP_BR_PROJ_MANAGE_COMM

Employee SAP_BR_EMPLOYEE

Accounts Payable Accountant SAP_BR_AP_ACCOUNTANT

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 implementation. The organizational structure reflects the structure of your company. The mas -
ter 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 scenario data:
Intercompany Processes - Project-Based Services (16T_SG) PUBLIC
Purpose Error: Reference source not found 4
Data Sample Value Details Comments
Material P002 Project-based Service: Time & Expenses Material which is used in order to describe different services being provided to the customer

Material E001 Accommodation

Material E002 Airfare

Material E003 Ground Transportation

Allowed changes to the above listed service-related materials are limited to descriptions and some attributes, since they are provided with DIP-Profile, a technical object necessary for selling of
project-based services.

Data Sample Value Details Comments


Sold-to party 10401010 Customer in sending company, for example 1710 (US) representing the receiving company, This is sample data. You can apply other countries' data
for example 1010(DE) on your needs.

Supplier 10401710 Supplier in sending company, for example 1010 (DE) representing the receiving company, This is sample data. You can apply other countries' data
for example 1710(US) on your needs.

Sales organiza- 1710 Sales Org., for example, US This is sample data. You can apply other countries' data
tion on your needs.

Distribution 10 Direct Sales This is sample data. You can apply other countries' data
channel on your needs.

Division 00 Product Division 00 This is sample data. You can apply other countries' data
on your needs.

For more information on creating master data objects, see the following Master Data Scripts (MDS) :
Table 1: Master Data Script Reference
Master Data ID Description
31X Create Product Master of Type "Services"

BNE Create Supplier Master

BND Create Customer Master

2.4 Business Conditions


Before this scope item can be tested, the following business conditions must be met.
Intercompany Processes - Project-Based Services (16T_SG) PUBLIC
Purpose Error: Reference source not found 5
Both country solutions have been activated, for example, sending company is US and receiving company is DE.

Business Condition Comment


J11- Customer Project Management - Project-Based Services Must be run in receiving company, for example, DE before this test script.See details below.

J12 - Time Recording - Project-Based Services Must be run before this test script. See details below.

J13 - Service and Material Procurement - Project-Based Services Must be run before this test script. See details below.

Note Specific data that has to be used for the Intercompany process in test scripts J11, J12 and J13 is listed in the following chapters of this document.
Note Before you start the testing, please make sure the setup in the scope item specific customer facing document S4H_389 Intercompany Billing for Project-Based Services Setup (16T) has been
completed.
If you want to know how time recording process can trigger intercompany markups and how the expense is claimed, you may refer to https://sapinsider.wispubs.com/Assets/Blogs/2018/February/
SAP-S-4HANA-Real-Time-Intercompany-Postings-for-Project-Based-Services for more information.

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 6
3 Overview Table

This scope item consists of several process steps provided in the table below.

Process Step Business Role Transaction/App Expected Results


Time and Expenses Intercompany Settlement

Check Intercompany Sales Order [page ] 8 Internal Sales Representative - Pro- List Sales Orders - Intercompany Intercompany Sales Order is created in delivering
fessional Services (VA05_AUART) company code 1710 for selling company code 1010.

Create Customer/Internal Project [page ] 9 Project Manager - Commercial Ser- See Customer Project Management - Project- A customer project is created in company code 1010.
vices Based Services(J11) scope item

Time Recording [page ] 10 See Time Recording - Project-Based See Time Recording - Project-Based Time is recorded for employees (DE and US employ-
Services(J12) scope item Services(J12) scope item ees) staffed on the project.

Create Supplier Invoice for Travel Expenses Accounts Payable Accountant See Service and Material Procurement - Project- A supplier invoice for travel expenses of the intercom-
of Intercompany Resource [page ] 10 Based Services(J13) scope item pany resource is created in company code 1710.

Generate Intercompany Billing Request Internal Sales Representative - Pro- Generate Intercompany Billing Request A debit memo request is created.
[page ] 11 fessional Services (F1829)

Invoicing

Create Intercompany Invoice [page ] 13 Billing Clerk Execute Billing - Business Partner Intercompany Invoice is created.
(FKKBIX_S)

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 7
4 Test Procedures

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

4.1 Time and Expenses Intercompany Settlement

4.1.1 Check Intercompany Sales Order

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

This process step shows you how to check intercompany sales order.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /


Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative - The SAP Fiori launchpad displays.
Professional Services.

2 Access the App Open List Sales Orders - Intercompany (VA05_AUART). The List of Sales Orders screen displays.

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 8
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment
3 Check if Intercompany Make necessary filter to check if an intercompany sales order exists in One (and only one) intercompany sales order exists.
Sales Order is Existing sending company. Make a note of the sales order document number.
For example, sending company 1710 to customer 10401010, set as
sales organization: 1710, Sold-to-party: 10401010
Choose Execute at the right bottom to display list of sales order.

If the intercompany sales order does not exist, proceed with the following steps to create the order.

4 Access the App Open Create Sales Orders - Intercompany (VA01). The Create Intercompany Order: Overview screen displays.

5 Verify the Order Type The system defaults the Order Type. You can verify it by clicking on
the top left arrow, near the SAP logo and Home.
● Order Type: SO03 - Intercompany Order
Choose Continue.

6 Enter Order Detail In the Header section, make the following entries: This is sample data. You can apply other countries' data on
● Sold-To Party: for example, 10401010 your needs.

Dialogue box of possible Sales Area related to Sold-To Party displays. Order quantity is filled with "1" by system automatically.
Select the correct one of your scenario.
In the All Items section near bottom of the page, make the following
entries:
● Material: P002
● Amount: 1000

7 Save Intercompany Sales Save the sales order document. An intercompany sales order is created. Make a note of the
Order Note The currency of the sending company will be used in the sales or- sales order document number: _________________
der. For example, if the sending company is US, the currency: USD.

4.1.2 Create Customer/Internal Project


In this activity a customer/internal project is created with a work package for time and material in receiving company, for example company code 1010 (DE).
An internal employee and intercompany resource from sending company, for example company code 1710 are staffed to the project.
Proceed with the following test steps:

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 9
For Customer Project:

1. Create Customer Project: create a customer project as described in test script Customer Project Management - Project-Based Services (J11) for the receiving service org. company, for example
DE (Sales Area 1010 / 10 / 00). Customer: Inlandskunde DE 1.
2. Maintain work packages and Time-based planning. Create a work package for time and material as described in test script Customer Project Management - Project-Based Services (J11).
3. Maintain work package Staffing with intercompany resource. Maintain staffing of the work package as described in test script Customer Project Management - Project-Based Services(J11). Staff
an internal employee (own employee = tester) and an intercompany resource from sending company, for example company code 1710 (Consultant1_US).
4. Maintain Customer Project Billing. The project billing information is maintained as described in test script Customer Project Management - Project-Based Services (J11). Create a billing item for
time and expense.

For Internal Project:

1. Create Internal Project: create an internal project as described in test script Internal Project Management - Project-Based Services (1A8) for the receiving service org. company.
2. Maintain work packages and Time-based planning. Create a work package for time and material as described in Internal Project Management - Project-Based Services(1A8).
3. Maintain work package Staffing with intercompany resource. Maintain staffing of the work package as described in test script Internal Project Management - Project-Based Services (1A8). Staff
an internal employee (own employee = tester) and an intercompany resource from sending company, for example company code 1710 (Consultant1_US).

4.1.3 Time Recording


For both employees staffed on the project (internal employee and intercompany resource) time has to be recorded.
Please refer to test script Time Recording - Project-Based Services(J12) and proceed with the step “Perform time recording”. For internal employee with the employee user used above. For the inter -
company employee, for example, Consultant_1US.

4.1.4 Create Supplier Invoice for Travel Expenses of Intercompany Resource


A supplier invoice for travel expenses of the intercompany resource is created in sending company, for example company code 1710.
Please refer to test script Service and Material Procurement - Project-Based Services (J13), step Posting expenses for internal employees w/o PO relation. Use the following data for the supplier in-
voice:

Field Value
Document Type ER – Manual Expense Travel

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 10
Field Value
Account Accomodation (61003000)

Assign the expenses to the work package of the project created before in receiving company, for example, company code 1010. This type is triggering the reposting of the expenses to the target
company code, for example, company code 1010.

4.1.5 Generate Intercompany Billing Request

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Purpose

This process step shows you how to generate the intercompany billing request. This happens via scheduling of a background job (analog to DP94).
Result is a debit memo request for intercompany billing for the time recordings and expenses for the intercompany services.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /


Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative - Pro- The SAP Fiori launchpad displays.
fessional Services .

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 11
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment
2 Access the App Open Generate Intercompany Billing Request (F1829). The Application Jobs screen displays.

3 Schedule Job to Create In- Choose New. The New Jobscreen displays.
tercompany Billing Re-
quest

4 Enter Schedule Job Details Make the following entries: Note Click the icon of the Log column to the log de-
● Job Template: Resource Related Billing between Company tail. There you may find the DMR number in one line
Codes of the log content.
● Job Template: Resource Related Billing between Company The billing request is created.
Codes
● Job Description: Resource Related Billing Between Com-
pany Codes
● Scheduling: Start Immediately: X
● Intercompany Sales Document: Document number
● Current w/ Curr.Date: X
● Save Options: Save Sales Document
Choose Schedule.

5 Access the App Open Manage Debit Memo Requests. The Manage Debit Memo Requests screen displays.

6 Enter Document Number Enter the Document Number of the debit memo request you have created be- Debit memo request displays.
fore and choose Go.
● Debit Memo Request: Document number
Note The currency of the sending company will be used in the debit memo
request. For example, if the sending company is US, the currency: USD.

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 12
4.2 Invoicing

4.2.1 Create Intercompany Invoice

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Purpose

This process step shows you how to create an intercompany invoice for services which have been executed in the delivering company of the intercompany process. A journal entry is created in fi -
nance.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /


Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a The SAP Fiori launchpad displays.
Billing Clerk.

2 Access the App Open Create Billing Documents The Billing Due List screen displays.
(F0798) - Billing Due List Items.

3 Define Billing Choose Billing Settings on the bottom


Settings bar, you can make the following set-

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 13
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment
tings as below:
1. Set billing date and type before
billing - OFF
2. Automatically post billing docu-
ments- OFF

4 Select Document Make the filter to find out the certain


to be Invoiced item in the Billing Due List.
● SD Document category: Debit
Memo Request

5 Create Intercom- Select the document and choose Create. The screen Billing Document shows. Check if all billing information here is correct.
pany Invoice All the information is composed into an invoice document start with "S", like "S3000000xx". It is a
temporary document, will be replaced by the formal invoice(start with "9") in the future.

6 Check Taxes on Check that taxes on the intercompany Tax amount is zero.
Invoice invoice are zero.

7 Save the Inter- Select Save at the right bottom to trig- A formal invoice(Start with "9") is generated.
company Invoice ger the formal intercompany invoice. To check the details of the IDoc generated by the intercompany billing document, you can refer to the
section Message Monitoring of the customer facing document Intercompany Billing for Project-Based
Services Setup (16T) (SAP Customer).
Note The currency of the sending company will be used in the intercompany invoice. For example, if
the sending company is US, the currency: USD.

8 Preview Inter- On the Billing Document screen, A PDF printout of the billing document is displayed.
company Invoice choose the Preview button to generate
and print a PDF.

9 Post the Invoice Choose Post Billing Doc to create an The invoice is transferred to Accounting. The system displays the message Billing documents posted.
Accounting document.

Financial Posting

In all the scenarios related to a Sales Flow, whatever Billing Document is created (Customer Invoice, Debit Note, Credit Note, Intercompany Invoice, etc.) the Journal Entry type is determined ac -
cording to the following rule:
● If the Destination country is Italy, the FI document type is W1 IT Local Cust. Sales
Intercompany Processes - Project-Based Services (16T_SG) PUBLIC
Purpose Error: Reference source not found 14
● If the Destination country is within European Union, the FI document type is W2 IT EU Cust. Sales
● If the Destination country is outside European Union, the FI document type is W3 IT EXEU Cust. Sales

Result

Intercompany billing has been created. In the meantime, the FI posing for A/P (receiving company) will be automatically posted via IDoc.
Note The currency of the receiving company will be used in the A/P. For example, if the receiving company is DE, the currency: EUR.

Intercompany Processes - Project-Based Services (16T_SG) PUBLIC


Purpose Error: Reference source not found 15
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. www.sap.com/contactsap


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 IN-
CLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and param-
eters, 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 documenta-
tion.
<Exam- Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
ple> make entries in the system. 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 affili-
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . ate company.
The information contained herein may be changed without prior notice. Some
software products marketed by SAP SE and its distributors contain propri-
etary software components of other software vendors. National product speci-
fications may vary.
These materials are provided by SAP SE or an SAP affiliate company for in-
formational purposes only, without representation or warranty of any kind,
and SAP or its affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in the express war-
ranty 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’ strat-
egy and possible future developments, products, and/or platforms, 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 infor-
mation 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, and they should not be relied
upon in making purchasing decisions.
Intercompany Processes - Project-Based Services (16T_SG) SAP and other SAP products and services mentioned herein as well as their
PUBLIC
Purpose respective logos are trademarksError:
or registered trademarks
Reference offound
source not SAP SE (or an 16
SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective compa-
nies.

See www.sap.com/copyright for additional trademark information and


notices.

You might also like