5KF - S4CLD2408 - BPD - EN - DE - Copie
5KF - S4CLD2408 - BPD - EN - DE - Copie
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 Validate Asset Accounting System Readiness
2.5.1.1 Confirm Takeover Date Information
2.5.1.2 Confirm Run of Balance Carry Forward for Current Fiscal Year
2.5.1.3 Create Asset Master Record for Legacy Asset
2.5.1.4 Transfer Open Items of AuC for Legacy Asset
2.5.1.5 Acquisition Assets
2.5.2 Activate Direct Posting to Asset
3 Overview Table
4 Test Procedures
4.1 Asset Acquisition for Constructed Assets (External Procurement)
4.1.1 Create Assets
4.1.2 Post Acquisition (Integrated AP) Without Purchase Order
4.1.3 Define Distribution Rules for Assets Under Construction (Periodic Processing)
4.1.4 Execute Settlement for Assets Under Construction (Periodic Processing)
5 Appendix
5.1 Create Supplier Invoice
Overview
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 appropriate.
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and busi-
ness conditions.
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 from a Template in the product assistance for SAP S/4HANA Cloud.
Name (Role Template) ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log On
Vendor * Domestic vendor If no vendor is available in your system yet, create a domestic vendor.
Cost Center 10101301 Manufacturing – 1 You can also use another Cost Center, but you must make sure that you use a consistent combination of Cost Cen-
ter and Profit Center (see table Overview of assignments below).
Profit Center YB110 Product A You can also use another Profit Center, but you must make sure that you use a consistent combination of Cost Cen-
ter and Profit Center (see table Overview of assignments below).
Functional Area YB20 Production You can also use another Functional Area, but you must make sure that you use a consistent combination of Cost
Center and Functional Area (see table Overview of assignments below).
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
BNI - Cre- During the execution of this scope item, asset master records will be created for assets under construction and the assets to which final settlement is performed.
ate Asset To create the assets, use the master data script Create Asset (BNI) using the data described in this test script.
Purpose
In this activity, you create a legacy data transfer segment to be allow for transfer of fixed assets on a specific transfer date. Apart from the transfer date, you
also define additional parameters for the legacy data transfer.
Note After you finalize the initial content activation, you must define a take-over date. This defines the current fiscal year and last closed fiscal year in As-
set Accounting. The takeover date is critical for system processing: It identifies the point in time that old asset values are loaded. This is usually the prior
year-end day. For AuC Asset Value Date, the value is automatically set to the first day of the new fiscal year (1/1/YYYY+1) instead of the transfer date
(12/31/YYYY).
Caution For example, if you're in fiscal year 2023, this implies the loading of old legacy assets is as of the year end 2021.
Caution If Legacy Data Transfer is defined in general ledger, the Legacy Data Transfer Date in Asset Accounting can’t be set as an earlier date.
Procedure
Note Company codes are automatically synchronized. If problems occur, you can manually start the synchronization by choosing Synchronize Com-
3. Enter your company code in the filter area and choose Go.
4. Select your company code. On the next view, choose Edit.
5. Check the status for your company. If it is not in For Testing status, set it to that status.
6. On the Legacy Data Transfer Settings tab, check or change the following entries (if necessary, to create a new legacy transfer segment, choose Create):
Transfer <last day of This is usually a year-end date for a prior year. If you’re instructed to use a midyear date, use a month-end date. The date should always
Date prior fiscal move forward (don’t change it backward).
year end>
The current and closed fiscal years are derived based on Transfer Date. To check the current and closed fiscal year, double-click the ledger on
the left side of the screen. The result is displayed on the right side of the screen on the Ledger Settings tab. If the Legacy Data Transfer Seg-
ment isn’t required, the current fiscal year can be manually entered and the closed fiscal year is derived. Without Legacy data Transfer Seg-
ment defined, no legacy asset master data can be created.
7. After the legacy data transfer is completed, set the Legacy Data Transfer Status to Completed.
8. Before you make postings in Asset Accounting in your P-system, repeat the preceding steps to confirm values for data the takeover date, the status, and
the document type for entering legacy assets already done in the Q-system.
2.5.1.2 Confirm Run of Balance Carry Forward for Current Fiscal Year
Purpose
In this activity, you confirm that Balance Carry Forward has been run for the current fiscal year.
Procedure
2 Access App Open Schedule General Ledger Jobs (F1927). The Application Jobs view is dis-
played.
6 Enter De- Make the following entries and choose Schedule: You scheduled the job run as a test
tails Ledger: <ledger>, for example, 0L run.
7 Review Re- To review the results of your test run, find your run in the Jobs pane and choose the arrow but-
sults ton to the right of its row.
8 Run Details Choose the Run Details tab. Review the log status.
9 Productive To perform a productive run, repeat this process, but deselect Test Run. You scheduled the job run as a pro-
Run ductive run.
Context
In this activity, you create legacy Assets Under Construction (AUC) assets with values. These assets may be used for various testing scenarios. You create
five legacy AUC assets in Asset Class 4000 with different descriptions.
You first create the asset master record for the legacy asset and then transfer the open items for the legacy asset.
Procedure
3 Create Fixed As- Choose Create > Create Legacy Asset Main Number . The Create Legacy Asset Main Number dia-
set log box is displayed.
Caution Ensure that the asset descriptions begin with the words Legacy AUC.
7 Enter Capitaliza- For the appropriate ledger, make the following entry and press Enter
tion Date Capitalized On: date, for example, 04/08/2016
Note : This is a prior year AUC asset, so this date must be in a past fiscal year.
Note You can enter the Cost Center and/or the WBS Element.
11 Confirm Values Confirm Dep. Key, UL in Years (or UL in Periods), and Dep. Start Date. The fields are verified.
Note You may need to choose Details (>) for the row to see some of these
fields.
12 Save the Record Choose Create. Make a note of the asset number:
_________________.
13 Home Choose the Home button to return to the SAP Fiori launchpad. The SAP Fiori launchpad displays.
Context
In this activity, you create legacy Assets Under Construction (AUC) assets with values. These assets may be used for various testing scenarios. You create
five legacy AUC assets in Asset Class 4000 or 4010 with different descriptions.
You first create the asset master record for the legacy asset and then transfer the open items for the legacy asset.
2 Access the SAP Fiori To transfer the open items for the legacy asset, open Transfer The Create General Header Data for Posting dialog box dis-
App Open Items of AuC - For Legacy Asset (ABLDT_OI). plays.
3 Enter the Company Enter a legacy asset to be updated with values (this is an AUC Note Transaction Type 900 lets you enter open items for a
and Legacy AUC Asset asset in Asset Class 4000 or 4010). legacy AUC asset in Asset Class 4000 or 4010.
Make the following entries and choose Continue:
Company Code: For example, 1010
Asset: <asset number>
Transaction Type: 900
4 Enter Values for Make the following entries and choose Simulate: The Enter Asset Transaction: Legacy Data-Transfer Open
Legacy AUC Asset Ledger: <ledger> Items screen is displayed.
Transfer Date: <transfer date; defaulted per data Confirm the respective dates and amount posted.
takeover date> The system displays the Posting will take place in an earlier
Document Date: <document date; defaulted per data fiscal year message. Bypass this warning.
takeover date> If any errors are RED coded, these must be corrected before
posting.
Posting Date: <posting date; defaulted per data
takeover date>
Asset Value Date: <asset value date; defaulted per
data takeover date>
Amount Posted: For example, 3600.00
5 Post Legacy AUC As- Choose Post. Make a note of the document number for each accounting
set Transaction Choose Continue. principle:
DEAP ______________________
IFRS ____________________
Purpose
Some test procedures in this script are based on AuCs managed by line item. Asset class 4000 is identified in Customizing as managed by line item for this
purpose.
1. Create an asset master record in asset class 4000.
2. Post an acquisition to this asset under construction.
3. Create an asset master record in asset class 2000 (Machinery).
The settlement profile can include both FXA (Asset) and CTR (Cost Center).
Note In the Test Procedure section, steps are included to offer support in asset master data creation and acquisition posting.
Purpose
To use the Create Supplier Invoice - Advanced (MIRO) app (or the Create Supplier Invoice (F0859) app) to post to assets in the Post Acquisition (Integrated
AP) WIthout Purchase Order procedure step, you must first activate direct posting to assets.
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: Sourcing and Procurement
Sub Application Area: Invoice Processing
6. For the row with Item Name of Incoming Invoice, choose Details (>).
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Activate Direct Posting Select the Dir. posting to asset = active checkbox.
This scope item consists of several process steps provided in the following tables.
Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for per-
forming 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.
Table 2: Asset Acquisition for Constructed Assets (External Procurement)
Create Assets [page ] 16 Asset Ac- See the Create Asset (BNI) master data script. You created two master records:
countant 1. An Asset Under Construction
2. An Asset Master (for final settlement)
Post Acquisition (Integrated AP) Without Purchase Order Asset Ac- Post Acquisition (Integrated AP) - Without Pur- You posted the acquisition from purchase with
[page ] 17 countant chase Order (F-90) vendor.
Define Distribution Rules for Assets Under Construction (Pe- Asset Ac- Define Distribution Rules - For AuC (AIAB) You defined the distribution rules for assets under
riodic Processing) [page ] 19 countant construction.
Execute Settlement for Assets Under Construction (Periodic Asset Ac- Execute Settlement - For AuC (AIBU) Assets under Construction are settled according to
Processing) [page ] 22 countant their settlement rules.
This section describes test procedures for each process step that belongs to this scope item.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this step you create an asset under construction (AuC) and an asset master record for the final settlement.
Prerequisite
For an asset for final settlement, use an asset that meets the following criteria:
Table 4: Asset for Final Settlement - Details
Field Value
Procedure
To execute this activity, run the processes described in the Create Asset (BNI) master data script. Use the data mentioned above to run the processes.
Note You can also use another cost center, but you must ensure that you use a consistent combination of cost center and profit center (see the Overview
of Assignments table in the Master Data and Organizational Data section).
Result
You created two asset master records, one AuC and one for the final settlement.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this step, you post the acquisition from purchase with a vendor.
An external asset acquisition is a business transaction that results from the acquisition of an asset from a business partner (in contrast to an in-house acquisi-
tion). You can post the acquisition of an external asset in the following ways:
● In Asset Accounting (FI-AA) integrated with Accounts Payable (FI-AP)
● In Asset Accounting without integration with Accounts Payable (posting to a clearing account - with or without clearing).
There are two scenarios:
● The asset acquisition comes before the receipt of the invoice. The offsetting entry is posted automatically.
● The asset acquisition is posted after the receipt of the invoice. The invoice was posted as an open item to a clearing account. This scenario isn’t described
further here. For more information, see Accounts Payable Accounting.
In this activity, the asset acquisition is posted integrated with Accounts Payable (FI-AP).
Note A new app ( Create Supplier Invoice (F0859)) to complete this procedure is available in the Appendix. You can use App Finder to search for it. You
can use the app below or the one in the Appendix to complete the procedure.
Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
2 Access the SAP Fiori Open Create Supplier Invoice - Advanced (MIRO).
app
3 Navigation If the system prompts you, make the following entries and choose
Continue:
Company Code: 1010
4 Basic Data On the Basic Data tab, enter the following data:
Invoice Date: <Your document date, for example, today>
Posting Date: <Your document date, for example, today>
Reference: any
Amount: 1000
Currency: EUR
Calculate tax : Selected
Tax code: V0
Tax Country/Region: <Tax country/region>
7 Enter Asset Details In the Asset section, make the following entries and press Enter: All required entries are made.
Asset: <Your asset number>
Asset subnumber: <Your asset subnumber>
A mount : 1000
8 Post Document Choose Post. The Address and Bank Data dialog box is dis-
played.
4.1.3 Define Distribution Rules for Assets Under Construction (Periodic Processing)
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this process step, you maintain the settlement rules for the asset under construction created in the previous steps.
Prerequisites
You executed all the previous steps related to assets under construction.
Procedure
2 Access the Open Define Distribution Rules - For AuC (AIAB). The view displays.
SAP Fiori
App
3 Maintain Make the following entries and choose Settlement AuC: Initial screenExecute: The Settlement AuC: Line item listSettleme view displays.
Settlement Company Code: 1010
Rule
Asset: <No. of asset> For example, from asset class 4000
Note The asset number is the asset created in the previous step.
Note If you enter a ledger value (for example, 0L or 2L), distribution rules
should be defined for both ledgers. If you only have distribution rules de-
fined for 0L, enter 0L. If you only have distribution rules defined for 2L, enter
2L.
3.1 Enter Dis- Select the line items you posted and choose DistrRule. The Maintain Settlement Rule: Overview view displays.
tribution
Rules
Note Each ledger has separate line items. Ensure that you select all.
4 Enter Dis- To maintain the distribution rule for the local ledger, select the line for ledger 0L
tribution and depreciation area 01. Select the document displayed and choose Enter Dis-
Rules tribution Rule.
Note To maintain the distribution rule for the second ledgers, select a line
item for ledger 2L and depreciation area 32, or the line for ledger 3L and de-
preciation area 34.
6 Save Set- Choose Back. You maintained the rules for the settlement. The system dis-
tlement Choose Save. plays the Distribution rules saved notification. The execu-
Rule tion of the settlement is part of the periodic processing.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
With the execution of this step, assets under construction are settled according to their settlement rules.
Prerequisite
You must have maintained the settlement rules for the Asset under Construction you want to settle.
Note Under certain conditions, you may need to capitalize an asset under construction before all suppliers have presented their closing invoices. This can
cause a few difficulties, especially if the closing invoice can’t be posted until the fiscal year following the capitalization of the asset under construction,
and down payments were already posted to the asset under construction.
Initially, you post the down payment normally. If you need to capitalize the asset under construction at the end of the fiscal year, but before the closing in-
voice is received, you post reserves for the total amount of the expected invoice. You post these reserves directly to the capitalized asset (external acquisi-
tion with vendor, transaction type 100). If you plan to distribute the values from the asset under construction to several final assets, it makes sense to post
the reserve to the asset under construction first, and then capitalize it. Whichever method you use, you must reverse the down payment on the asset under
construction, because the down payment isn’t allowed to appear in the account for down payments to fixed assets. Instead, it must appear in the account for
completed assets.
To settle the asset under construction, down payments must be cleared with an invoice or forecasted invoice (reserve). The asset under construction can
only be settled after this clearing.
2 Access the Open Execute Settlement - For AuC (AIBU). The AuC Settlement: Ini-
SAP Fiori app. tial Screen view displays.
3 Execute AUC Make the following entries and choose Simulate: The Settlement AuC: Line
settlement Company Code: 1010 Item List view displays.
Note If you enter a ledger value (for example, 0L or 2L), distribution rules should be defined for both ledgers.
If you only have distribution rules defined for 0L, enter 0L. If you only have distribution rules defined for 2L,
enter 2L.
4 Execute AUC Select the line for ledger and depreciation area for which settlement should be executed. Choose Save. The relevant line items
settlement are displayed.
Test Administration
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this activity, you enter a supplier invoice for asset acquisition without reference to a purchase order.
Note The Create Supplier Invoice (F0859) app is only complementary to the Post Acquisition (Integrated AP) Without Purchase Order topic in the Test
Procedures. For other steps that use Create Supplier Invoice - Advanced (MIRO), do not use the Create Supplier Invoice (F0859) app.
Note If you have activated Registration for Indirect Taxation Abroad (RITA) in your system, a Tax Country/Region field is visible in the app.
If you have not activated RITA, the field is not visible in the app. In the latter case, you can disregard the Tax Country/Region field in the Procedure table
below.
For more information on activating RITA, see #unique_20.
Procedure
2 Access the SAP Fiori App Open Create Supplier Invoice (F0859). The New Supplier Invoice(F0859) view is dis-
If the Data from Previous Invoice Entry Exist dialog box displays, played.
choose No.
3 General Information In the Basic Data section, enter the following data:
Transaction: Invoice
Company Code: 1010
Gross Invoice Amount: 119.00
Currency: For example, EUR
4 Enter Asset Details In the Asset Items area, select Add and enter your Asset details:
Asset <Your asset Number>
Asset sub number <Your asset Sub Number>
Amount: 1000
Quantity: 1
5 Simulate Supplier Invoice After entering all required details choose Simulate . The supplier Invoice is complete to post.
and Check Messages If there are no differences, the supplier invoice is complete to post.
Verify the Gross Invoice Amount against the items plus the tax
amount.
If the tax code is an exempt tax code, you don't have any tax
amount.
6 Post Invoice Choose Post. The Invoice is posted. The system displays the
message Invoice xxx has been posted.
Example Words or characters quoted from the screen. These include field names, screen titles, pushbut-
tons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
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, F 2 or E N T E R . © 2024 SAP SE or an SAP affiliate company. All rights re-
served.
No part of this publication may be reproduced or transmitted
in any form or for any purpose without the express permis-
sion of SAP SE or an SAP affiliate company. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distribu-
tors contain proprietary software components of other soft-
ware vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate
company for informational purposes only, without representa-
tion or warranty of any kind, and SAP or its affiliated compa-
nies 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 warranty statements accompanying such prod-
ucts 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 Ger-
many and other countries. All other product and service
names mentioned are the trademarks of their respective
companies.