Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 31

Test Script

SAP S/4HANA - 27-09-22

Internal Order - Actual (BEV_AE)

PUBLIC

Table of Contents

1 Purpose

2 Overview Table

3 Prerequisites
3.1 System Access
3.2 Roles
3.3 Master Data, Organizational Data, and Other Data
3.4 Business Conditions
3.5 Preliminary Steps
3.5.1 User Settings - Set Controlling Area
3.5.2 Maintain Investment Profile (Mandatory Step)

4 Test Procedures
4.1 Internal Order - Actual
4.1.1 Create Internal Order
4.1.2 Enter General Ledger Account Document
4.1.3 Consumable Purchasing (Only for R&D Order)
4.1.4 Consumable Purchase Receiving (Only for R&D Order)
4.1.5 Post Goods Issue to R&D Internal Order (Only for R&D Order)
4.1.6 Record Working Time
4.1.7 Create Settlement Rule
4.1.8 Execute Settlement Internal Order
4.2 Internal Order - Actual using Universal Parallel Accounting
4.2.1 Create Internal Order
4.2.2 Enter General Ledger Account Document
4.2.3 Execute Settlement (Step relevant only for Order Type Y600 Investment)
4.2.4 Create Settlement Rule
4.2.5 Execute Settlement Internal Order
4.3 Analytics
4.3.1 Internal Order Actuals

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 2
1 Purpose

Various internal initiatives consume resources and incur costs or expenses. This process enables the tracking of costs incurred for these initiatives to facilitate cost control and monitoring, ROI calcu -
lations, settlement to other cost objects, among others.
This process uses SAP’s internal order functionality to track costs and status. For every R&D initiative undertaken, an internal order is created using the R&D order type. Cost planning is performed
on this order. When the initiative is approved, the order is released. Costs incurred for the initiative are posted on the order. Periodically, the costs collected on the order are settled to the assigned
R&D cost center or to CO-PA. When the internal order initiative is complete and fully settled, the order is closed by setting the appropriate status.
For marketing initiatives, an internal order is created using the marketing order type. Marketing orders are created as statistical orders. Costs are posted to the assigned cost center and as statistical
costs to the internal order. The order does not need settlement since the real costs are assigned to the cost center.
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.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 3
2 Overview Table

The scope item consists of several process steps. Choose the appropriate entity provided in the tables 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 apps not included on the homepage using the search bar.
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.
Table 1: Internal Order – Actual
Process Step Business Role Transaction/App Expected Results

Create Internal Order [page ] 10 Cost Accountant - Over- Manage Internal Orders (F1604) Internal Order is created for R&D and other overhead costs.
head

Enter General Ledger Account Document [page ] 12 General Ledger Accoun- Post General Journal Entries (F0718) The General Ledger Accountant account document is entered and
tant posted.

Consumable Purchasing (Only for R&D Order) [page ] 14 Purchaser Create Purchase Order (ME21N) Consumables are purchased.

Consumable Purchase Receiving (Only for R&D Order) [page ] 15 Warehouse Clerk Post Goods Movement (MIGO) Consumable purchases receipts are acknowledged.

Post Goods Issue to R&D Internal Order (Only for R&D Order) Warehouse Clerk Post Goods Movement (MIGO) Goods issue to the R&D internal order are posted.
[page ] 17

Create Settlement Rule [page ] 19 Cost Accountant - Over- Manage Internal Orders (F1604). A settlement rule to settle an order to a R&D cost center is created.
head

Execute Settlement Internal Order [page ] 20 Cost Accountant - Over- Run Settlement - Orders - Actual (Collective) Settlement internal order is executed.
head (KO8GH)

Table 2: Internal Order – Actual using Universal Parallel Accounting


Process Step Business Role Transaction/App Expected Results

Create Internal Order [page ] 22 SAP GUI/KO01 Internal Order is created for R&D and other overhead costs.

Enter General Ledger Account Document [page ] 12 General Ledger Accoun- Post General Journal Entries The General Ledger Accountant account document is entered and
tant (F0718) posted.

Execute Settlement (Step relevant only for Order Type Y600 Investment) [page SAP GUI/KO88 Settlement internal order for order type Y600 is created.
] 25

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 4
Process Step Business Role Transaction/App Expected Results

Create Settlement Rule [page ] 27 SAP GUI/KO02 A settlement rule to settle an order to a R&D cost center is created.

Execute Settlement Internal Order [page ] 28 SAP GUI/KO88 Settlement internal order is executed.

Table 3: Analytics
Process Step Business Role Transaction/App Expected Results

Internal Order Actuals [page ] 29 Cost Accountant - Overhead Internal Orders - Actuals (F0941A)

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 5
3 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.

3.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.

3.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 for your own roles.

Business Role Business Role ID as Delivered by SAP Log On

Cost Accountant - Overhead SAP_BR_OVERHEAD_ACCOUNTANT

General Ledger Accountant SAP_BR_GL_ACCOUNTANT

Purchaser SAP_BR_PURCHASER

Warehouse Clerk SAP_BR_WAREHOUSE_CLERK

For more information about business roles, refer to Assigning business roles to a user in the Administration Guide to Implementation of SAP S/4HANA with SAP Best Practices.

3.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:

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 6
Data Sample Value Details Comments

OPERATING A000
CONCERN

CONTROLLING A000
AREA

COMPANY CODE 3310

G/L ACCOUNT 10010000 G/L account for


posting

COST CENTER 33101501 R&D cost center

COST CENTER 33101601 Marketing cost cen-


ter

INTERNAL OR- Business Conditions in SAP S/4HANA on-premise internal orders continue to be supported. For additional information on internal orders, please refer to
DERS https://launchpad.support.sap.com/#/notes/ 2865342.
Internal Order type Y100 (Research and Development)
Internal order type Y020 (overhead cost orders)
Internal order type Y400 (marketing internal orders

MATERIAL TG0011

MATERIAL TG0012

For more information on creating master data objects, see the following Master Data Scripts (MDS)
Table 4: Master Data Script Reference
Master Data ID Description

BNG Create G/L Account and Cost Element

BNM Create Cost Center and Cost Center Group

BNF Create Trading Good (“HAWA”)

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 7
3.4 Business Conditions
Internal orders continue to be supported. For additional information on internal orders, refer to note 2865342.

3.5 Preliminary Steps

3.5.1 User Settings - Set Controlling Area

Purpose

The controlling area must be set before you carry out the first steps in controlling.

Procedure

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

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Choose User Preferences Choose the user icon on the top right corner of the screen, and choose Settings. The Default Values dialog box displays.
Choose Default Values.

3 Enter Data On the CO Area field, Controlling area A000 is set for your user.
enter the following value: A000.
Choose Save.

3.5.2 Maintain Investment Profile (Mandatory Step)

Context

The standard investment profile is delivered without a specific asset class assigned and must be mapped.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 8
Procedure

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

1 Log On Log onto the SAP GUI. The SAP GUI displays.

2 Access the SAP GUI In the Command, field, enter transaction code OITA and press Enter. The Change View "Investment profile": Overview view is displayed.

3 Select Investment Profile Select investment profile 000001 and choose the Details button. The Change View "Investment profile": Details view is displayed.

4 Settlement Rule In Inv.meas. ast.class, enter 4001 and save the entry.

5 Investment Profile Repeat steps 3 and 4 for investment profile YS0001.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 9
4 Test Procedures

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

4.1 Internal Order - Actual

4.1.1 Create Internal Order

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>

Context

In this activity, you create an internal order for R&D for other overhead costs or a statistical order for marketing costs.

Prerequisite

The responsible cost center must be assigned to the internal order and the internal order is released. This step can be skipped if the internal order is already created for planning purposes.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 10
Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /


Step # Comment

1 Log on Log onto the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Manage Internal Orders (F1604). The Manage Internal Orders screen displays.
Fiori App

3 Create Internal Choose Create. The Internal Order: New screen displays.
Order

4 Enter Data Make the following entries: The Controller creates an internal order. Cost planning is performed on this
Controlling Area: A000 order. Also costs incurred for the project can then be posted on the order.

Order Type: Y100


Choose Continue.

5 Enter Data In the General Data section, make the following entries:
Order (second field): <for description example, R&D Internal Order>

Note If you plan to create a statistical internal order type Y090 in the Control section,
you must enter the actual posted cost center and ensure that the statistical box is selected.

Currency: AED
In the Assignment section, make the following entries:
Company Code. 3310
Object Class: Overhead Costs
Profit Center: YB110
Cost Center Responsible: for example, 33101501

Note If you are creating order type Y600 for AuC, also maintain Investment Profile:
000001 under the Investments section.

6 Change System In the Status section, choose Change System Status and a dialog box opens. Select from the
Status list:
Change System Status: BFRE, Release

Note If you are creating order type Y600 for AuC, create AuC via Extra-Asset Under
Construction.

Internal Order - Actual (BEV_AE)


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

7 Save Save your entries.

8 Make Note Note the order number for the subsequent transactions.

4.1.2 Enter General Ledger Account Document

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>

Context

When you carry out postings to G/L accounts, you enter document header data (usually document date, document type, company code, posting date, and currency) as well as a posting key, G/L ac-
count number, and the first line item. The posting key and the field status group for the G/L account determine which fields are displayed on the next screen.
The system carries out consistency checks before saving the data. When the debits equal the credits and the data is complete, post the document. If errors exist, the data is not saved, and the system
proposes adjustments.
The system updates the document file and the G/L account balances.

Procedure

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

1 Log on Log onto the SAP Fiori launchpad as a General Ledger Accountant. The SAP Fiori launchpad displays.

Internal Order - Actual (BEV_AE)


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

2 Access the SAP Fiori Open Post General Journal Entries (F0718).
App

3 Enter Header Data In the header area, make the following entries:
Journal Entry Date : <Enter Current Date>
Posting Date: <Enter Current Date>
Journal Entry Type: SA
Company Code: 3310
Transactions Currency: AED

4 Enter Data In Line Items (2), make the following entries:


Company Code: 3310
G/L Account: For example, 65002000
Debit: <enter an amount> for example, 5500
Choose Enter.

5 Enter Additional Detail In the expanded section, make the following entries:
Tax Code: <Input Tax Code>
Order: For example, order created in previous step
Choose Enter.

6 Close Expanded Detail Select left arrow of the first line item to collapse detail.

Note For the Amount in Document Currency field above, make the entry in
the debit or credit column as appropriate.

7 Enter Second Line In Line Items (2) second line, make the following entries :
Item Detail Company Code: 3310
G/L Account: For example, 11001000
Credit: <amount> for example, 5500
Choose Enter.

8 Enter Additional Detail In the expanded section, make additional entries:


Value date: <Enter Current Date>
House Bank: <House Bank> for example, AEBK1
House Bank Account: <House Bank> for example, AEAC1

Internal Order - Actual (BEV_AE)


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

Note The Value Date field is required for cash accounts.

9 Save Choose Post. The General Ledger Accountant account document is posted. The system has au-
tomatically added the Input tax amount.

10 Make Note Write down the document number for the subsequent transactions.

4.1.3 Consumable Purchasing (Only for R&D Order)

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>

Context

Once the order is created, you require external services. In this activity, you purchase consumable items.

Procedure

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

1 Log on Log on to the SAP Fiori launchpad as a Purchaser. The SAP Fiori launchpad displays.

2 Access the SAP Fiori Open Create Purchase Order (ME21N). The Create Purchase Order screen dis-

Internal Order - Actual (BEV_AE)


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

App plays.

3 Enter Supplier Make the following entries and press Enter:


Supplier: For example, 33300001

4 Enter Org. Data In the Header section, Org. Data tab, make the following entries:
Purch. Org.: 3310
Purch.Group: 001
Company Code: 3310

5 Enter Item Overiew Expand the Item Overview section, make the following entries and select Enter:
"A" Acct Ass. Cat.: For example, F (Order)
Material: For example, TG0012
PO Quantity: 1
Net Price: 300
Currency: AED
Plnt: 3310

6 Enter Item Detail Expand the Item Overview section,select the Account Assignment tab and make the following entries:
Order : For example, order created in the step Create Internal Order.

7 Assign Tax Code Choose the Invoice tab and make the following entries:
Tax Code: <Input Tax Code>

8 Save Choose Save.

Note If information messages appear after saving, acknowledge all messages by choosing Enter, then choose
Save again.

7 Document Number Write down the document number for subsequent transactions.

4.1.4 Consumable Purchase Receiving (Only for R&D Order)

Test Administration

Customer project: Fill in the project-specific parts.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 15
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>

Context

In this activity, you acknowledge receipt of the purchased consumable items.

Prerequisite

Creation of purchase order, step Consumable Purchasing is a prerequisite.

Procedure

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

1 Log on Log onto the SAP Fiori Launchpad as a Warehouse Clerk. The SAP Fiori Launchpad dis-
plays.

2 Access the SAP Fiori App Open Post Goods Movement (MIGO).

3 Enter Header Data In the header area, make the following entries and select Execute:
Select Goods Receipt in the drop down control
Select Purchase Order in the drop down control
Document Date: <Enter Current Date>
Posting Date: <Enter Current Date>
Purchasing Document Number: For example, <Enter the purchase order created in the pre-
vious step>.
GR good receipt: For example, 101

4 Enter Data At the bottom of the screen, make the following entries:
Item OK: Select

5 Save Choose Post.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 16
4.1.5 Post Goods Issue to R&D Internal Order (Only for R&D Order)

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>

Context

Material is required from inventory for your R&D internal order. To facilitate this, you post a goods issue to the R&D internal order.

Prerequisite

Stock must be available in inventory to perform this step. There are several ways stock can be created. Executing test script J45 (Procurement Processing) will create material TG0011 in stock.

Procedure

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

1 Log on Log onto the SAP Fiori launchpad as a Warehouse Clerk. The SAP Fiori launchpad
displays.

2 Access the SAP Fiori Open Post Goods Movement (MIGO).


App

3 Enter Header Data Make the following entries and choose Enter:
Choose Goods Issue from the dropdown list.
Choose Other in the dropdown list.
Document Date: <Current Date>

Internal Order - Actual (BEV_AE)


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

Posting Date: <Current Date>

4 Enter Detail Data On the Material tab, for


Material: enter <your material code> For example, TG0011

5 Enter Additional Make the following entries in the various tab sections and press Enter:
Data Choose the Quantity tab.
Quantity: 1

6 Enter Additional Choose the Where tab.


Data Movement Type: 961 Ensure there field to the right is blank. Plant: 3310
Storage Location: For example, 331A .
Press Enter

7 Choose the Account Assignment tab and make the following entry :
Order: For example, order created in step Create Internal Order

8 Save Choose Post.

Note If you receive a Deficit of SL unrestricted -use error, this means there is not enough inventory in stock. In-
ventory must be purchased and received using testscript J45.

4.1.6 Record Working Time

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>

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 18
Context

In this activity, you can perform time recording against the internal order.

Prerequisite

To execute this activity, run the process Time Recording(1Q4) scope item, using the Master Data account object internal order and activity type 8 – Consulting.

4.1.7 Create Settlement Rule

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>

Context

In this activity, a settlement rule to settle an order to a R&D cost center will be created for R&D orders.

Procedure

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

1 Log on Log onto the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Manage Internal Orders (F1604). The Manage Internal Orders screen
Fiori App displays.

Internal Order - Actual (BEV_AE)


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

3 Select Order In Internal Order No., select the internal order you created.

4 Edit Order In the Internal Order: XXXX view, choose Edit.

5 Enter Actual Data Note Skip this step when using order type Y600. AuC only requires entry of full settlement rule. Partial settlement is created
automatically for the AuC during AuC settlement.

Select Maintain Settlement Rule and in the Distribution Rules section, choose Insert and make the following entries:
Category: <Cost Center
Settlement Receiver: 33101501
%: 100
Settlement type: Periodic Settlement
Rule Sequence: 001

6 Enter Actual Data In the Distribution Rules section, choose Insert and make the following entries:
Category: <Either Cost Center or if using order type Y600 AuC, select Asset (FXA)>
Settlement Receiver: <Enter either Cost Center of if using order type Y600 AuC, enter the
already created asset>
%: 100
Settlement type: Full Settlement
Rule Sequence: 002

7 Mark as Done Choose Done.

8 Save Save your entries. Settlement rule is created.

4.1.8 Execute Settlement Internal Order

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 20
Tester Name: Duration:

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

Context

In this activity, you execute the settlement. The internal order is settled to the responsible cost center in the case of internal orders with order type: R&D and overhead costs. Please note settlement
for internal orders with order type: marketing costs is not allowed .

Procedure

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

1 Log On Log onto the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Fiori Open Run Settlement - Orders - Actual (Collective) (KO8GH). The Actual Settlement: Orders screen dis-
App plays.

3 Create Selection Variant Make the following entries:


Selection Method: Standard Selection for Internal Orders
Selection Variant: Enter the variant name, for example, YBLMF_RD and choose Create.
On the Edit Variants: Variant XXX screen, in the Order Type field, select the Multiple Selection icon on
the right.
In the Multiple Select for Order Types screen, enter order types, for example, Y100.
Choose Copy.
On the Edit Variants: Variant XXX screen, choose Attributes.
In the Variant Attributes screen, enter a description, for example, R&D Orders.

4 Save Choose Save.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 21
4.2 Internal Order - Actual using Universal Parallel Accounting

4.2.1 Create Internal Order

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>

Context

In this activity, you create an internal order for R&D for other overhead costs or a statistical order for marketing costs.

Prerequisite

The responsible cost center must be assigned to the internal order and the internal order is released. This step can be skipped if the internal order is already created for planning purposes.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /


Step # Comment

1 Log on Log onto the SAP GUI. The SAP GUI displays.

2 Access the SAP Fiori Enter transaction code KO01. The Manage Internal Orders screen displays.
App

3 Create Internal Order Choose Create. The Internal Order: New screen displays.

Internal Order - Actual (BEV_AE)


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

4 Enter Data Make the following entries: The Controller creates an internal order. Cost planning is performed on
Controlling Area: A000 this order. Also costs incurred for the project can then be posted on the or-
der.
Order Type: Y100
Choose Enter.

5 Enter Data In the General Data section, make the following entries:
Order (second field): <for description example, R&D Internal Order>

Note If you plan to create a statistical internal order type Y090 in the Control section,
you must enter the actual posted cost center and ensure that the statistical box is se-
lected.

In the Assignment section, make the following entries:


Company Code. 3310
Object Class: Overhead Costs or when using order type Y600 use
INVST Investment
Profit Center: YB110
Cost Center Responsible: for example, 33101501

6 Investments Tab for Or- Note Only applicable for Y600: INVST Investment
der type Y600 only
Investment Profile: 000001

7 Control tab In the Status section, choose Release and a dialog box opens. Select from the list:
Currency: AED

8 Save Save your entries.

9 Make Note Note the order number for the subsequent transactions.

4.2.2 Enter General Ledger Account Document

Test Administration

Customer project: Fill in the project-specific parts.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 23
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>

Context

When you carry out postings to G/L accounts, you enter document header data (usually document date, document type, company code, posting date, and currency) as well as a posting key, G/L ac-
count number, and the first line item. The posting key and the field status group for the G/L account determine which fields are displayed on the next screen.
The system carries out consistency checks before saving the data. When the debits equal the credits and the data is complete, post the document. If errors exist, the data is not saved, and the system
proposes adjustments.
The system updates the document file and the G/L account balances.

Procedure

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

1 Log on Log onto the SAP Fiori launchpad as a General Ledger Accountant. The SAP Fiori launchpad displays.

2 Access the SAP Fiori Open Post General Journal Entries (F0718).
App

3 Enter Header Data In the header area, make the following entries:
Journal Entry Date : <Enter Current Date>
Posting Date: <Enter Current Date>
Journal Entry Type: SA
Company Code: 3310
Transactions Currency: AED

4 Enter Data In Line Items (2), make the following entries:


Company Code: 3310
G/L Account: For example, 65002000
Debit: <enter an amount> for example, 5500
Choose Enter.

Internal Order - Actual (BEV_AE)


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

5 Enter Additional Detail In the expanded section, make the following entries:
Tax Code: <Input Tax Code>
Order: For example, order created in previous step
Choose Enter.

6 Close Expanded Detail Select left arrow of the first line item to collapse detail.

Note For the Amount in Document Currency field above, make the entry in
the debit or credit column as appropriate.

7 Enter Second Line In Line Items (2) second line, make the following entries :
Item Detail Company Code: 3310
G/L Account: For example, 11001000
Credit: <amount> for example, 5500
Choose Enter.

8 Enter Additional Detail In the expanded section, make additional entries:


Value date: <Enter Current Date>
House Bank: <House Bank> for example, AEBK1
House Bank Account: <House Bank> for example, AEAC1

Note The Value Date field is required for cash accounts.

9 Save Choose Post. The General Ledger Accountant account document is posted. The system has au-
tomatically added the Input tax amount.

10 Make Note Write down the document number for the subsequent transactions.

4.2.3 Execute Settlement (Step relevant only for Order Type Y600 Investment)

Test Administration

Customer project: Fill in the project-specific parts.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 25
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>

Context

In the case of AuC, the settlement rule is automatically created at the time of settlement.

Procedure

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

1 Log On Log onto the SAP GUI. The SAP GUI displays.

2 Access the SAP GUI Enter transaction code KO88. The Actual Settlement: Orders screen displays.

3 Run Settlement Make the following entries and choose Execute:


Order: the number of the Internal Order type Y600 created created pre-
viously
Settlement Period: <Current>
Fiscal Year: <Current>
Ledger: <for example, 0L>

Note Each ledger must be run separately.

Processing Type: <1 Automatic>


Test Run: Deselect

4 Save Choose Save.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 26
4.2.4 Create Settlement Rule

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>

Context

In this activity, a settlement rule to settle an order to a R&D cost center is created for R&D orders.

Procedure

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

1 Log On Log onto the SAP GUI. The SAP GUI displays.

2 Access the SAP Enter transaction code KO02. The Change Internal Orders: Initial
GUI Screen displays.

3 Select Order Select the internal order you created before.

4 Settlement Rule Choose the Settlement Rule button.

5 Periodic Settle- Note Skip this step when using order type Y600. AuC only requires entry of full settlement rule. Partial settlement is cre-
ment ated automatically for the AuC during AuC settlement.

Select Maintain Settlement Rule and in the Distribution Rules section, choose Insert and make the following entries:
Category: Cost Center
Settlement Receiver: 33101501
%: 100

Internal Order - Actual (BEV_AE)


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

Settlement type: Periodic Settlement


Rule Sequence: 001

6 Enter Actual In the Distribution Rules section, choose Insert and make the following entries:
Data Category: <Either either Cost Center or if using order type Y600 AuC, enter Asset (FXA)>
Settlement Receiver: <Enter either Cost Center of if using order type Y600 AuC, enter the
already created Final Fixed Asset>
%: 100
Settlement type: Full Settlement
Rule Sequence: 002

Note For order Y600, this is the final settlement with the actual Final Fixed Asset as receiver.

7 Mark as Done Choose Done.

8 Save Save your entries. Settlement rule is created.

4.2.5 Execute Settlement Internal Order

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>

Context

In this activity, you execute the settlement. The internal order is settled to the responsible cost center in the case of internal orders with order type: R&D and overhead costs. In the case of AuC, the
order is settled to the asset. Note that the settlement for internal orders with order type of marketing costs is not allowed.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 28
Procedure

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

1 Log On Log onto the SAP GUI. The SAP GUI displays.

2 Access the SAP GUI Enter transaction code KO88. The Actual Settlement: Orders screen displays.

3 Run Settlement Make the following entries and choose Execute:


Order: Order created previously
Settlement Period: <Current>
Fiscal Year: <Current>
Ledger: <for example, 0L>

Note Each ledger must be run separately.

Processing Type: <1 Automatic>


Test Run: Deselect

4 Save Choose Save.

4.3 Analytics

4.3.1 Internal Order Actuals

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>

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 29
Context

This allows for viewing internal orders.

Procedure

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

1 Log on Logon to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Fiori App Open Internal Orders - Actuals (F0941A).

3 Enter Selection Criteria Make the following entry :


Order: for example, the order you created in step one and enter a period.

4 Execute Choose Execute.

Internal Order - Actual (BEV_AE)


Purpose PUBLIC 30
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 .

© 2022 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-


Internal Order - Actual (BEV_AE) tion and notices.
Purpose PUBLIC 31

You might also like