Test Script

SAP S/4HANA Cloud - 27-12-22

Intercompany Financial Posting (1GP_US)

PUBLIC

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
2.5 Preliminary Steps
2.5.1 Post a General Journal Entry Between Two Company Codes
2.5.1.1 Configure Clearing Account for Intercompany Posting (General Ledger)
2.5.1.2 Configure Responsible Team
2.5.1.3 Configure Workflow Definition for Intercompany
2.5.1.4 Submit Journal Entry to Be Verified (Intercompany)
2.5.1.5 Approve Journal Entry by Different User (Intercompany)
2.5.1.6 Check the Journal Entry Status (Intercompany)

3 Overview Table

4 Test Procedures
4.1 Display Journal Entries Cross-Company Code
4.2 Change Journal Entries Cross-Company Code
4.3 Reverse Journal Entries Cross-Company Code
Intercompany Financial Posting (1GP_US)
Purpose PUBLIC 2
1 Purpose

In an intercompany posting across company codes, the system posts a separate document with its own document number in each of the company codes. Individual documents are linked by a com-
mon cross-company code number. The system generates line items to balance the debits and credits in each document.
The company codes involved must be part of a single legal entity for tax purposes if one of the following is true:
· The receivables or payables are posted in a different company code from the one in which the revenue or expenses (costs) are posted
· The business transaction is relevant to taxes
In addition, the customer can assign a paying company code to each company code. You can have one company code process payment transactions centrally for several company codes. however,
these company codes must be in the same country/region and have the same local currency and parallel currencies. They must have the same settings for enhanced withholding tax functions (active
or inactive).
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.

Note Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a different notation, enter values as appropri-
ate.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 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
Create business roles using the following business role templates delivered by SAP and assign them to your individual test users.
Alternatively, if available, you can use the following spaces delivered by SAP. You create a space with pages containing predefined essential apps and assign it to the business role. You then assign
this business role to your individual users.
For more information, refer to How to Create a Business Role for the Administrator in the product assistance for SAP S/4HANA Cloud.

Name (Role Template) ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log On

General Ledger Accountant SAP_BR_GL_ACCOUNTANT General Ledger Accountant SAP_BR_GL_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 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 or the following sample data to go through the test procedure.

Master Data Sample Value Details Comments

Company Code 1710

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 4
 Master Data Sample Value Details Comments

Chart of Accounts YCOA

Controlling Area A000

You can find general information on how to create master data objects in the following Master Data Scripts (MDS):

MDS Description

BND Create Customer Master

BNM Create Cost Center and Cost Center Group

BNG Create G/L Account and Cost Element

2.4 Business Conditions

The following business conditions must be met before this scope item can be tested,

Scope Item ID Business Condition

J58 - Accounting and Financial Close Post General Journal Entry

2.5 Preliminary Steps

2.5.1 Post a General Journal Entry Between Two Company Codes

2.5.1.1 Configure Clearing Account for Intercompany Posting (General Ledger)

Purpose

In this activity, you configure the clearing account to be used for intercompany posting.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 5
Procedure

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
1. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
2. Open Manage Your Solution (F1241).
3. If necessary, change the country or region by choosing Set Local Version.
4. Choose Configure Your Solution.
5. Make the following entries:
Application Area: Finance
Sub Application Area: General Ledger
6. For the row with Item Name of Chart of Accounts, choose Details (>).
7. For the Automatic Account Determination row, choose Configure.
8. Continue with the procedure in the table below.
SAP Central Business Configuration:
1. Log on to the project experience in SAP Central Business Configuration.
2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab.
3. Search for the Automatic Account Determination activity and choose Go to Activity to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configura-
tion Expert - Business Process Configuration.
4. Continue with the procedure in the following table.

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Area Make the following entries and choose Step 2:

Area: Financial Accounting
Subarea: General Ledger Accounting
Process: Prepare Intercompany Transactions

2 Parameters Make the following entries and choose Step 3: The Account Assignments pane displays the details of the assignments.
Transaction Key: BUV (Clearing between com-
pany codes)
Postings Between: <first company code>
And: <second company code>

3 Add Account Assign- Choose Add. The Add dialog box is displayed.
ment

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 6
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

4 Verify Company Codes Verify the two company codes and choose OK. The Automatic Account Determination view is displayed.

5 Enter Accounts For the first company code, make the following entries:
Posting Key - Debit: 40
Account - Debit: 12122000
Posting Key - Credit: 50
Account - Credit: 21720000
Make the same entries for the second company code.

6 Account Assignments Choose Review. The view displays the details of the selections you made.

7 Save Choose Save. To confirm the dialog box, choose Save. The system displays a message that the changes were submitted successfully, then returns to the
Step 1 view.

2.5.1.2 Configure Responsible Team

Purpose

In this activity, you configure the team responsible for the journal entry workflow.

Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

1 Log On Log on to the SAP Fiori launchpad as a General Ledger Accountant.

2 Access SAP Fiori App Open Manage Teams and Responsibilities For Journal Entry Verification - In General Ensure that FGJEV G/L Journal Entry Verification is chosen
Ledger (F3932). in the Category field.

3 Create Team Choose Create. The New Team screen displays.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 7
 Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

4 Enter Team Details Make the following entries:

General Information section:
Name: RESPONSIBLE <first company code>
Description: RESPONSIBLE <first company code>
Type: FGLVG
Responsibility Definitions section:
Company Code: <first company code>
Cost center: <leave blank>
GL account Group: <leave blank>
Team Owners section:

Note The fields in this section are automatically populated with the details for the
General Ledger Accountant.

5 Enter Team Members In the Team Members section, choose Create. The Select: Business Partner dialog box is displayed.

6 Enter Team Members Search for the user for the General Ledger Accountant for the other country/region,
then choose OK.

7 Enter Team Members Make the following entries:

Function: FGJEV_L1 (Group 1 for Verifying G/L Journal Entries)

8 Save Choose Save. The Team screen displays.

9 Edit Choose Edit.

10 Team Information Choose the Team Information tab.

11 Change Status Make the following entries and choose Save:

Status: Ready to Use

12 Create Team for Another Com- Repeat steps 3-12 for the following information:
pany Code Name: RESPONSIBLE <second company code>
Type: FGLVG
Company Code: <second company code>
User: GL_ACCOUNTANT role for second company code's

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 8
 Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

country/region

2.5.1.3 Configure Workflow Definition for Intercompany

Purpose

In this activity, you configure the workflow for the intercompany process.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log onto the SAP Fiori launchpad as a General Ledger Accountant.

2 Access SAP Fiori App Open Manage Workflows for Journal Entry Verification - In General Ledger (F2720).

3 Create Team Choose Add. The New Workflow screen displays.

4 Enter Detail Make the following entries:

Workflow Name: Intercompany GJE Verification
Step Properties section:
Description: Intercompany GJE Verification
Start Conditions section:
Only start the workflow if all of the following preconditions are met: (None)

5 Step Sequence In the Step Sequence section, choose Add.

6 Enter Details Make the following entries and choose Add: The system returns to the prior screen.
Step Name: Intercompany

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 9
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

Step Type: Verify Intercompany General Journal Entry

Recipients section:
Assignment By: Role
Role: Group 1 for Verifying G/L Journal Entries
Step to be completed by: All of the recipients
Exception Handling section:
● For Reject:
• Required Action: Redo General Journal Entry
• Action Result: Restart Workflow
● For Processing obsolete:
• Required Action: Do nothing
• Action Result: Cancel Workflow

7 Step Sequence Repeat steps 5 and 6 with the following data: The system returns to the prior screen.
Name: Post
Type: Post General Journal Entry

Note Do not make any other entries on this screen.

8 Save Choose Save.

9 Activate Choose Activate. The workflow is activated.

2.5.1.4 Submit Journal Entry to Be Verified (Intercompany)

Purpose

In this activity, you submit the journal entry for intercompany verification.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 10
Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Com-
ment

1 Log On Log on to the SAP Fiori launchpad as a General Ledger

Accountant.

2 Access SAP Fiori Open Verify General Journal Entries - For Requester
App (F2547).

3 Add Journal Entry In the Journal Entries section, choose Create.

4 Enter Details Make the following entries in the header:

Journal Entry Date: <date of journal entry>
Posting Date: <posting date>
Journal Entry Type: <journal entry type>
Company Code: 1710
Transaction Currency: USD
Make the following entries for Line Item 1:
Company Code: <first company code>
G/L Account: 11001010
Debit: 100.00
Value Date: <today's date>
Make the following entries for Line Item 2:
Company Code: <second company code>
G/L Account: 11001010
Credit: 100.00
Value Date: <today's date>

5 Submit Choose Submit. The system displays a message that the journal entry was submitted for verification in the company code
Make a note of the journal entry number. from the first line item.
The document is parked.

6 Back Choose Back.

7 Review In the Journal Entries section, locate your journal entry The status is Submitted.
number.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 11
2.5.1.5 Approve Journal Entry by Different User (Intercompany)

Purpose

In this activity, the approvers in each company code approve the journal entry per the workflow setup.

Procedure - First Company Code

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log onto the SAP Fiori launchpad as a General Ledger Accountant for the country/region of the first company
code.

2 Access SAP Fiori Open Verify Journal Entries in General Ledger - For Processor (Inbox) (F2728). The Verify General Journal Entry view dis-
App plays.

3 Select Journal Entry In the left pane, choose the journal entry to process.

4 Approve Choose Approve. The workflow is approved.

Procedure – Second Company Code

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log onto the SAP Fiori launchpad as a General Ledger Accountant for the country/region of the second com-
pany code.

2 Access SAP Fiori Open Verify Journal Entries in General Ledger - For Processor (Inbox) (F2728). The Verify General Journal Entry view dis-
App plays.

3 Select Journal Entry In the left pane, choose the journal entry to process.

4 Approve Choose Approve. The workflow is approved.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 12
2.5.1.6 Check the Journal Entry Status (Intercompany)

Purpose

In this activity, you verify the status of the journal entry.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log onto the SAP Fiori launchpad as a General Ledger Accountant.

2 Access SAP Fiori App Open Verify General Journal Entries - For Requester (F2547). The Verify General Journal Entries view displays.

3 Select Journal Entry In the Journal Entries pane, find the journal entry from the prior steps. The Status field for the journal entry is Posted.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 13
3 Overview Table

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

Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the typical tasks of a business
role.
You can find all other (searchable) apps not included on the homepage using the search bar (2434549).
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.

Process Step Business Role App/Transaction Expected Results

Display Journal Entries Cross-Company Code [page ] 15 General Ledger Accountant Display Journal Entries - Cross-Company Code The financial documents with the cross-company postings are displayed.
(FBU3)

Change Journal Entries Cross-Company Code [page ] 16 General Ledger Accountant Change Journal Entries - Cross-Company Code The cross-company document is changed.
(FBU2)

Reverse Journal Entries Cross-Company Code [page ] General Ledger Accountant Reverse Journal Entries - Cross-Company Code The cross-company document is reversed.
17 (FBU8)

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 14
4 Test Procedures

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

4.1 Display Journal Entries Cross-Company Code

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>

Purpose

In this step, you display the journal entries for cross company codes (the journal entry you posted in the first step should be displayed).

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log on to the SAP Fiori launchpad as a General Ledger Accountant.

2 Access the SAP Fiori App Open Display Journal Entries - Cross-Company Code (FBU3). The Display Journal Entries Cross-Company Code screen dis-
plays.

3 Display CC Document List Choose Document List. The List of Cross-Company Code Transactions screen displays.

4 Execute Document List Choose Execute. The List of Cross-Company Code Transactions screen is dis-
played.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 15
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

Press Enter.

5 Select Document From the list, select the checkbox next to the document to display, and choose The Display Transaction Overview screen displays.
Choose .

4.2 Change Journal Entries Cross-Company Code

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>

Purpose

In this activity, you change the journal entries for cross-company codes (the document you posted in the first step should be changed).

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log on to the SAP Fiori launchpad as a General Ledger Accountant.

2 Access the SAP Fiori App Open Change Journal Entries - Cross-Company Code (FBU2). The Change Transaction: Initial screen displays.

3 Select Document from List Choose Document List. The List of Cross-Company Code Transactions screen dis-
plays.

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 16
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

4 Enter Selection Criteria Make the following entries and choose Execute:
Company code: 1710
Fiscal Year: <current year>

5 Select Document Select a document to change and choose Choose. The Change Transaction: Overview screen displays.

6 Select Document Header Select a line in the document header area and choose Select Individual Object. The Document Header: XXXX Company code screen dis-
plays.

7 Change Journal Entry Change the text in the Doc. Header Text and Reference fields, then choose Continue/
Confirm.

8 Save Changes Choose Save. The document is changed and saved.

4.3 Reverse Journal Entries Cross-Company Code

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>

Purpose

In this step, you reverse the journal entry for cross-company codes (the document you posted in the first step should be reversed).

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 17
Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log on to the SAP Fiori launchpad as a General Ledger Accoun-

tant.

2 Access the SAP Fiori App Open Reverse Journal Entries - Cross-Company Code (FBU8). The Reverse Cross-Company Code Transaction: Header Data screen dis-
plays.

3 Enter CC Document Number Make the following entries and choose Post: The cross-company journal entry is reversed.
Cross-co. code no: current posted CC document num-
ber
Reversal Reason: 01

Intercompany Financial Posting (1GP_US)

Purpose PUBLIC 18
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 parame-
ters, 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.

<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, F 2 or E N T E R .

© 2023 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 affili-
ate company. The information contained herein may be changed without
prior notice.
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 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.
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. All other product
and service names mentioned are the trademarks of their respective compa-
nies.

See www.sap.com/copyright for additional trademark informa-

Intercompany Financial Posting (1GP_US) tion and notices.
Purpose PUBLIC 19