SAP Note

3293759 - SAP S/4HANA Cloud 2308: Release Restriction Note

Component: XX-SER-REL (Business Suite Release Information), Version: 9, Released On: 09.11.2023

Symptom
You are using SAP S/4HANA Cloud 2308. This note informs you about any restrictions in this release. This SAP Note is
subject to change, please check it for regular updates.

Other Terms

Reason and Prerequisites

Solution
General:
General Release Information Note for SAP S/4HANA Cloud 23082 can be seen here: SAP Note 3293789
For a Change Overview for SAP S/4HANA Cloud regarding Identity and Access Management (IAM): SAP Note
2975653.
Restrictions valid for SAP Fiori visual theme for classic applications are described in the SAP Note 2428021.
For restrictions relevant to Enterprise Search functionality, please see SAP Note: SAP Note 2768916.
For deprecated Scope Items in R&D/ Engineering, please see SAP Note 2792363.
For restrictions relevant for RITA (Registration for Indirect Taxation Abroad) in SAP S/4HANA, please see SAP
Note 2907372.
For restrictions relevant for Integration with SAP Launchpad Service – Restrictions, please see SAP Note 3075639.
For restrictions relevant for SAP S/4HANA Cloud, Test Data Refresh, please see SAP Note 3070606.
The Test Data Indicator flag is not supported in Product SOAP Services. For more information refer SAP Note:
3112356. This feature is not supported by the Product SOAP Services for SAP S/4HANA Cloud 2111, and upwards.
For restrictions relevant for SAP S/4HANA Cloud 2302 in a 3-system landscape, please see SAP Note 3340933.
Restriction Note for "List of Output forms to supporting International address version please see SAP
Note 3211782
Restriction Note for "Unable to Restrict Business Partners Using Data Controller in SAP S/4HANA Asset
Management", please see SAP Note 3345547.

Configuration:
Configuration is done via configuration activities and pre-approved expert configurations (templates).
Maintenance of scope (scope items, languages) needs to be done before content activation and other configuration
happen. Scope extensions can be done after initial activation.
Adjustment of pre-configured organizational data in the "Manage Your Solution" app needs to be done prior to
content activation. Extension of organizational structure after content activation will be still possible.
If you need to adapt the IDs of SAP Best Practice G/L accounts (Operative Chart of Accounts (YCOA), Group Chart
of Accounts (YGR1) and Local Chart of Accounts), use the "Renumber G/L Account" configuration step in the
Manage Your Solution app and the “Convert Renumbered G/L Accounts” app after activation of the SAP S/4HANA
Cloud quality system (ideally in Realize phase). Renumbering of a G/L Account needs to be executed before the
first posting is entered for that G/L account in the production system. To keep the SAP standard CoA, confirm the
Chart of Accounts settings in the "Renumber G/L Accounts" configuration activity in the Manage Your Solution
app.
Deletion of SAP-owned/ shipped entries in configuration activities is not allowed. Customer entries can only be
deleted in certain enabled configuration activities.
Currently, only one change of a project is allowed at a time.
Currently, only one country solution can be changed at a time across the entire customer project. Simultaneous
changes to different countries are not allowed, even if conducted by different users.
Configure Your Solution app:
While using the configuration activity "Set Up Payment Methods per Country for Payment Transactions" (ID:
101972), please consider that only 9 new payment method IDs can be created. The following IDs are
specifically reserved for customers: 6, 7, 8, 9, U, V, W, Y and Z. If 5 alphabetic IDs: U, V, W, Y, Z are not yet in
use in the system, an incident need to be raised to make them technically available.
There are 5 payment method IDs marked as automatic payment (no approval) in the Bank Communication
Management app. Currently, the approval process is not supported for these 5 payment methods and there is
 also no configuration activity available to change it.
If need to create new entries with Configuration activities Define Withholding Tax Type for Invoice Posting
(ID 104225) and Define Withholding Tax Type for Payment Posting (ID 104226) only create new entries in Z*
namespace except Z1, Z2, Z8, Z9 and ZN to avoid potential issues with SAP content.
If need to create new entries with configuration activity Define Withholding Tax Codes (ID 104227) only
create new entries in Z* namespace to avoid potential issues with SAP content.
Create Code Template Button to be disabled in the BRF+ Function UI within Simplified Workbench App
In the Manage Upgrade Tests application, the default execution variant can be empty if there is no execution
scope created in the previous cycle. This can be the case when the application loads initially.
Integration of the Information Retrieve Framework(IRF) is unavailable for the SAP S4HANA
document management.
SAP S4HANA Document management deals with unstructured content ( as an attachment to the SAP S4HANA
business object ), so document management is unsure of the content and whether personal data exist.
It is necessary to retrieve attachments ( managed by the DMS ) by the IRF.
Data Migration
Using Model your Migration Objects app, customer is only allowed to enhance specific Migration Objects
delivered by SAP. This applies to all Migration Objects explicitly listed / referenced in note 2999428. The
enhancements are restricted to the structures and fields explicitly listed in the referenced notes that are specific for
each Migration Object.
Enterprise Asset Management
Process control codes for maintenance orders:
1. Authorizations to set and reset process control codes are not supported.
2. Process control code doesn't block time confirmations. Process phase control codes effectively blocks only the
release of order. After release of the maintenance order, it blocks the transition between phases, but doesn't
prevent the time confirmations of the maintenance order.
Determination of Phases and Subphases of maintenance notifications and orders:
1. Phase and Subphase for a notification are not calculated when the system status is AIRQ (Additional Information Required) is set or unset.

2. Phase and Subphase for a notification is not displayed on the Fiori Uis
 onfiguration activity Define Prioritisation Profiles: User cannot modify SAP delivered Event Prioritization Profile
C
and delete/change pre-delivered Plant + Notification type mapping. Instead a new plant needs to be created.
Unable to navigate to Change Measuring Point (IK02) using “Create Measuring Point" (SAPGUI for HTML) App,
please use "Change Measuring Point" WebDynpro application to Change the Measuring Point.
Unable to navigate to Create Maintenance Plan(IP41) using “Schedule Maintenance Plan” (SAPGUI for HTML)
App (IP10): Note 3040235, please use "Create Maintenance Plan" WebDynpro application to create Maintenance
Plan
The application objects Maintenance Job Package (MAINTENANCE_JOB_PACKAGE) and Maintenance
Notification (MAINTENANCE_NOTIFICATION) in the Output Parameter Determination are created for future
releases. The conditions in the decision tables of the application OPD Maintenance Job
(OPD_EAM_MAINT_JOB_PACKAGE) and OPD Maintenance Notification
(OPD_EAM_MAINT_NOTIFICATION) will undergo changes.
There is high possibility that SAP may change the parameters of this decision tables and it may result in loss of your
conditions or corrupt the transactional data. You should not configure this application object and implement the
same. Till advised, do not use this application object for output control.
In the WebDynpro applications Create Maintenance Order and Change Maintenance order (W0017), you can select
materials or services from an OCI-based catalog.
When items have been checked out from the catalog, they are currently not displayed automatically in the order. You can update the
order with the selected items by pressing the Refresh button in the order.
When you select a catalog and the URL of that catalog has not been maintained correctly, an internal error is triggered and all unsaved
data in the order is lost. We recommend saving the maintenance order before starting a catalog session.

Maintenance confirmations using Find Maintenance Order and Operation App: Post-processing errors
related to goods issue and financial controlling do not appear for individual or mass confirmation of time.
Maintenance confirmation will be posted directly. Confirmataion posting for the already confirmed maintenance
order operation does not get posted and also there is no warning or error messages shown to the user. Mass upload
of maitenance order opertaion confirmation using Excel can handle maximum 100 records in a single upload. Post
processing errors due to actual cost postings are getting captured and shown in the apps.
Perform Maintenance Jobs app does not allow the user to delete malfunction details such as Damage Details,
Cause, and Activity in the malfunction section on the details page.
Mainenance Tasklist: Updating pricing data for adlready added non-stock components/lean service associated to
an operation is not possible in Maintenance Tasklist.
Coping lean service and non-stock material data from reference maintenance order to a maintenance Task list is not
supported.
With the Fiori apps Manage Maintenance Plans (F5325) and Manage Maintenance Items (F5356), you
cannot view, create, or edit maintenance plans or maintenance items of the category Service Order.
Fiori app Manage Maintenance Plans (F5325)
In the tile for the Fiori app (F5325), the key performance indicator (KPI) count may not match the count in the
list report if you are using SAP S/4HANA service orders in your business because:
The count in the tile includes the SAP S/4HANA service orders and maintenance orders whereas the list
report includes only the SAP S/4HANA maintenance orders.
The KPI tile count does not include the maintenance plans that are in Own Draft status but, the list report
count includes the draft records.
Only 15 digits can be entered in the field ‘Cycle Length’. So, the value in this field must be less than or equal to
15 digits.
The option of assigning Class to the maintenance plan is not available, use the Web Dynpro app Change
Maintenance Plan (W0009) app to assign class to the maintenance plan.
The option to filter maintenance plans by characteristics value within a class is not available. You can only filter
maintenance plans by class, use the Web Dynpro app Change Maintenance Plan (W0009) app to filter the
maintenance plan based upon characteristic values.
The option to upload or delete GOS document is restricted, and it is highly recommended not to do the below
changes through the “SSCUI- Activate HDM for Attachment Object Type configuration”
For object type ‘MainennacePlan’ under ‘Activate Document Frameworks’ do not delete the entry of
Document Management System attachment framework
For object type ‘MainennacePlan’ under ‘Maintain Default and Restricted Document Types’ do not change
from restricted to unrestricted for the GOS attachment framework"
While creating a maintenance plan using the Fiori app Manage Maintenance Plans (F5325), you cannot assign
an existing maintenance item to the maintenance plan. Create an Maintenance Item Directly from plan and
then Assign an Existing Item, Delete the first created Item
In the object page of the Fiori app Manage Maintenance Plans (F5325), you cannot assign an existing
maintenance item to the maintenance plan of maintenance plan type ‘Multiple Counter’. Press the Edit Button
on the Object Page and then assign an Maintenance Item to Multiple Counter Plan.
In the tab ‘Unassigned Items’ of the Fiori app Manage Maintenance Items (F5356), you cannot assign a
maintenance item to a multiple counter plan. To assign a maintenance item to a multiple counter plan, use the
Fiori app Manage Maintenance Plans (F5325). To assign a maintenance item to a multiple counter plan, use the
Fiori app Manage Maintenance Plans (F5325).
In the object page of the Fiori apps Manage Maintenance Plans (F5325), you can access the quick views for
measuring point counters of a maintenance plan only for the maintenance plan type ‘Multiple Counter’ and will
not be available for Strategy and single cycle plan.
You cannot use a maintenance plan as a copy template. You cannot create a maintenance plan by copying an
existing maintenance plan.
OCI Catalog:
If the shopping cart from catalog contains any inconsistend data compared to S4 HANA the system doens´t
allow you to add the shopping basket to the maintenance order. The shopping cart in the catalog will become
empty.
Auto Refresh of the maintenance order in Web Dynpro Application (App ID: W0017):
If a Web-Dispatcher is integrated in your system environment it might be that the auto refresh of the
maintenance order is not working as expected while punching back from a OCI Catalog.
The order has to be refreshed manually by clicking the "Refresh" button inside the Web Dynpro Application
Source of Supply Determination:
If you have implemented the BAdI SOS_... the source of supply determination won´t be triggered for enhanced limit
items in the maintenance order.
The long text can have only 1333 characters in Create Maintenance Request (F1511A) and Screen
Maintenance Requests (F4072).
Technical Object Value Help in Create Maintenance Request (F1511A) and Screen Maintenance Requests
app only shows maximum number 100 records of technical object hierarchy. Its not possible to sort, expand and
collapse technical object hierarchy.
You are using Minor Work as Notification Processing Context and you have updated Malfunction Details from My
Maintenance Requests then Malfunction details (Object Part, Damage, Cause and Activity)are not editable once its
saved. This is because My Maintenance Requests app display only app.
Handover of Documents from Maintenance Order to Purchase Documents: The Handover of documents
for maintenance order is only supported for purchase requisition. Documents cannot be copied to the purchase
order.
In Change Measurement Documents (IK18) app which is a SAP GUI for HTML transaction, business graphics are
not supported.
In the Find Technical Object app (F2072), you cannot add a subordinate equipment to a functional location.
Subordinate equipment can only be added to an equipment.
In the Manage Material serial Numbers app (F6879), you cannot update the description of the serialized
equipment. By default, the description of the material is considered as the description of the serialized equipment.
Phase model related notifications and orders have to be proccessed within the boundary of their own scope item, i.e.
you should not create a proactive maintenance order against a reactive maintenance notification, otherwise the
subphases of those business objects are determined incorrectly.
Any actual cost for which a maintenance order is the account assignment object, this actual cost is persisted in
database table ACDOCA. This table has been enhanced to include plant maintenance related information such as
equipment, functional location and work center. Not all line items representing actual cost will be enriched to
include the plant maintenance related information. This plant maintenance related information can be used in the
analytical list page "Maintenance Order Costs" to perform a query such as "Show me all cost related to a certain
technical object". The above query depends on the plant maintenance related information persisted in each line item
of database table ACDOCA so that only those line items will be selected for which the plant maintenance related
information has been persisted.
The plant maintenance related information is persisted in the following scenarios: Posting a goods issue for a stock
component, triggering a time confirmation against an operation, Supporting the procurement process with regards
to external operations, non-stock materials and lean services.
The plant maintenance related information is not persisted for direct FI postings.
Predictive Commitments Management has been partially introduced for account assignment object maintenance
order. The plant maintenance related commitments are not shown in Analytical List Page “Maintenance Order
Costs” or “Change/Display Maintenance Order”. Commitments related to maintenance orders are shown in reports
provided by SAP Enterprise Portfolio and Project Management (EPPM). In addition, no budget control has been
introduced for the maintenance order.
A new version of the migration object for the maintenance order has been introduced. The second version supports
phase control codes against maintenance operations, this was missing in the first version. The second version of the
migration object does not include any reference to task lists. Hence, each operation of an maintenance order has to
be defined individually. In your legacy system, you might have planned a maintenance order via the assignment to a
maintenance task list. When exploding the task list operation into a maintenance order, you can restrict the
operations copied into the maintenance order and you might have overwritten the defaulted work center for those
copied operations. Those decisions cannot be easily replicated in the migration object so that you need to define the
maintenance order operations without any assignment to a task list.
Looking at the reactive maintenance process, a maintenance order can only transition once through the approval
phase. Once the approval for a maintenance order has been issued, the planning of a maintenance order might
continue leading to a much higher planned cost compared to the baseline cost, but the higher cost has no influence
on the approval being issued. In this scenario, the maintenance planner will not be able to trigger “Submit Order for
Approval” and the original approver of this maintenance order will not be automatically informed that the planned
cost exceeds the baseline cost.
As a maintenance planner, I am able to trigger “Main Work Completed” or “Technical Completed” against a
maintenance order header to indicate that all MAIN operations or all operations in general have been completed.
The activation of those system status will determine new subphases on operations. The activation of those system
status will not influence the checkbox “Has open main work”. As of now, this checkbox is only updated when all
MAIN operations have system status “Planned Work Finished”.
The following restriction only applies to you if the following conditions are met: Your maintenance order has an
internal operation including a lean service and the control key of this operation has the confirmation setting
“Confirmation possible but not necessary”. This control key setting is only available in your system when you have
updated the SAP delivered control key YBM1 or introduced your own control key. If those conditions are fulfilled,
the value of the checkbox “Has open main work” will be different across “Change/Display Maintenance Order” and
“Find Maintenance Order” applications. The checkbox in “Change/Display Maintenance Order” application will
show the correct value and the checkbox will be incorrect in “Find Maintenance Order” application.
In the Web Dynpro apps Create Task List and Change Task List (W0021), change number is not supported.
With Migration Cockpit, you cannot migrate lean services, non-stock materials, and production resource tools
(PRTs) for an Task List operation.
In the Manage Maintenance Items app (F5356), you cannot assign an unassigned maintenance item to a
multiple counter plan. To assign unassigned maintenance item to a multiple counter plan, go to the Manage
Maintenance Plans app (F5325).
In the Web Dynpro apps Create Task List, Change Task List, and Display Task List (W0021), the tabs Service
Package and Limits are not applicable. These tabs will be hidden in an upcoming release.
In the object page of the Manage Maintenance Items app (F5356), go to the Account Assignment section.The fields
for asset and asset sub number are not relevant and will be hidden in an upcoming release.
In the Web Dynpro apps Create Task List and Change Task List (W0021), you cannot add a service for a
suboperation.
In the Find Maintenance Task List app (F2660), the following fields are irrelevant and will be removed in an
upcoming release:
• Safety Relevance
• Inspection Point
• Reference Element
• External Numbering
In the Web Dynpro app Change Task List (W0021), choose the Add Safety Instructions button. When you search for
safety instructions to add them to the task list, you can view only 500 safety instructions at a time. Please refine your
search criteria accordingly.
If you have set deletion flag to Maintenance request then it will not appear / display in My Maintenance Requests
and Screen Maintenance Requests Fiori applications.
Maintenance request is in Action required status with system status AIRQ OSNO. You have set deletion flag and
status of the request is AIRQ DLFL NOCO. This request is not available now to view it in My Maintenance Request
 and Screen Maintenance Requests Fiori applications.
Now if you reset the deletion flag then this request will be in AIRQ NOPR status and its available in Action required
tab of My Maintenance Requests app but you can not edit if you go to object page since NOPR status is set and
OSNO status is not possible. You need to close this request and open new one to process further.
Time Zone in Maintenance Notification;
--Date and time in long text of maintenance request will be displayed in system time and not in user or browser time.
--Completion date and time will be stored in user time zone.
-If you are using Maintenance Notification API then time zone conversion will not happened and data will be stored
in user time zone.
-In below application, date time fields will be as per Fiori launchpad time zone.
F1511A - Create Maintenance Request,
F4072 - Screen Maintenance Requests,
F4513 - My Maintenance Requests,
F2072 - Find Maintenance Notifications,
F5797 - Display Maintenance Notifications,
F2048 - Technical Object Breakdown Analysis
Change Maintenance Notification WDA app
If you are using Postpone or Put in process again action for maintenance request then phase and subphase are not
updating correctly. We do not support postpone or put in process again business transactions in new phase model.
Maintenance Technician will be able to upload all the supported documents with the Order header/ order operation.
Currently it is not possible to restrict a document type only for Read purpose in Perform Maintenance Jobs app.
Usage of Billable Order in EAM:
Web Dynpro Application W0017 Create/Change Maintenance order is not designed to handle billable orders.
SAP Enterprise Asset Management (SAP EAM) has not yet adopted the new Business Partner Data Controller
feature and hence it will not block access to any Business Partners based on the Data Controller.
Extensibility:
Custom analytical queries as well as the preview functionality for custom CDS views are not enabled for read access
logging.
Data protection (Developer Extensibility): You are responsible for ensuring that the data persisted in own
tables is managed in accordance with any applicable legal requirements or business needs, such as data protection
legislation or data life cycle requirements. Note that Developer Extensibility is currently not integrated in the
privacy-by-default functionality of SAP S/4HANA. In particular, there is no integration with ILM (Information
Lifecycle Management) and IRF (Information Retrieval Framework) yet. Therefore, Developer Extensibility should
not be used for the processing of personal data if this processing falls under any applicable data protection
legislation.
Extensibility Cockpit supports English only, irrespective of logon language.
Released ABAP Artifacts support the logon language for Technical Content of ABAP artifacts. In case content is not
available in the logon language, this content will be displayed in the language it was created.
Due to possible changes in the underlying Virtual Data Model content, you might have to adapt your Custom CDS
content after the upgrade. For further information see SAP Note 2540701.
A custom CDS view inherits its protection exclusively from its primary data source. For further information, see SAP
Note 2540696.
Financial-specific:
If you want to create an E-Balance sheet for Germany:
1. Upload the taxonomy into the system
2. Enter the mapping of the accounts to the taxonomy positions
3. You can now either:
download and install the ERP standalone client for E-Balance and enter the data into this excel sheet
manually, validate and send off to the authority or
transfer the mapped data to your tax consultant
Advanced Payment Management: Interest rates for account settlement can only be defined as fixed rates.
Reference interest rates are not editable.
Taxes:
Currently, it is not yet possible to restrict the auditor's access by time frame across all reports. In this case,
auditors can access all tax-relevant data, regardless of date.
Tax calculation in the US:
The internal US tax calculation in SAP S/4HANA Cloud and any reporting based on this calculation may not
comply with all reporting requirements in your jurisdiction due to the specifics of the tax law system in the
United States. You must check with your accounting or tax experts to make sure that the results generated by
this report are fully compliant with your relevant jurisdictions’ specific sales and use tax reporting
requirements. For further information on these restrictions, please refer to the SAP Note 2440096.
While using the SSCUI "Set Up Payment Methods per Country for Payment Transactions" (ID: 101972), please
consider that only 9 new payment method IDs can be created. The following IDs are specifically reserved for
customers: 6, 7, 8, 9, U, V, W, Y and Z.
Asset Accounting (US): Luxury Automobile Limitations and 100% Bonus Depreciation: SAP S/4HANA Cloud
provides a MANUAL default Depreciation Key (MANU) for the US Tax Books in asset class 3100 (Vehicles). Please
enter depreciation for the affected vehicle assets for each individual year. This may be done by selecting the Fiori
app "Post Depreciation Manually", entering asset and affected depreciation areas. The transaction type is 610 for a
current year asset or 600 for a prior year asset. The affected US Tax Books are:
90 ACRS/MACRS Federal Tax
91 ALT MIN Alternative Minimum Tax
92 ACE Adjusted Current Earnings
It is only possible to do validation & substitution on journal entries for the fields, which are delivered under
Validation & Substitution Cloud BADIs.
Asset Accounting - 'Post Asset Acquisition' app (F6488):
If you select or remove a ledger from the selection in the ‚Posting Information‘ screen area, the system determines
the corresponding depreciation areas and displays them. (The system proceeds accordingly if you select
depreciation areas.) Due to technical restrictions, the user interface does not always update (synchronize) the
display of the determined ledgers or depreciation areas.
Account Determination app:
It is not allowed to change the posting keys or rules for a transaction key
It is not allowed to delete any existing records
Single Reconciliation Account for Bank Account
Currently a migration of an existing bank account to use the Single Reconciliation Account for Bank Accounts
is not offered.
The following functions are not available for GL accounts of type "Cash Account":
• Foreign Currency Valuation job template
• Perform Foreign Currency Valuation app
If you migrate to use the Advanced Valuation you can valuate G/L accounts of type "Cash Account".
Data Aging: with the following apps, you cannot select journal entries that have been moved to the historical part
of the database:
Display G/L Account Balances
Display Line Items in General Ledger
Display Line Item Entry
Electronic Invoice (Italy)
New Document types requested by tax agency for electronic invoice and Esterometro declaration will be
available. Italian law consider new document types as optional use for 2021. For 2021 SAP recommends to use
current solution based on old document types. In January 2022 Esterometro will be definitely abolished and
new Document types will become mandatory and ready to use. If you need to manage the new document types
already in 2021 you should use the BADI “EDOC_IT_XML_FILE”.
Revenue Recognition (Event-based) – Sales Order: only standard Sales Order-based Sell from Stock
processes and Delivery-based Billings will trigger Revenue Recognition postings (Sales Document Item Category
TAN). Variants of Sell from Stock processes such as the following will not trigger any Revenue Recognition
postings:
1. Advanced/Accelerated Returns
2. intercompany sales
3. third-party sales
For restrictions relevant for "Product Costing: Real-Time Work in Process", please refer to the SAP Note 2737228.
Management Accounting and Margin Analysis - Predictive Accounting:
Predictive Accounting for Sales Processes
Predictive accounting does not support sales orders that have a WBS element as the account assignment.
Projects do not use standard price routines and costs or revenues will be incurred at a later point in time.
When a billing document is created, the DIP profile determines the expense items and the related price
information. As a result, a billing request is created, from which the billing document is generated. This
means that, for example, the following business processes are not supported:
Customer project management
Project-based services
Intercompany sales processes are not supported.
For the “third-party direct shipment” business process (including drop shipments), predictions for the
goods issues are not supported.
Predictive accounting only processes the following SD document categories:
C - Order
H - Returns
I - Order Without Charge
K - Credit Memo Request
L - Debit Memo Request
Split valuation with batches of sales order items can only be simulated if the batch or at least the
valuation type is entered in the sales order. The valuation type then provides an approximation for the
material valuation.
Predictive accounting doesn’t support changes to items in a sales order after a corresponding partial
delivery or partial billing. Such a change prompts predictive accounting to fully simulate the sales order
again, without considering the partial delivery or billing.
Exception: For sales orders with a billing plan, only open billing documents are simulated after a partial
delivery or partial billing.
 When you make supported changes to sales orders, predictive accounting adjusts the corresponding
information in the prediction ledger accordingly. However, when you change the price of a material in its
master data and the material is included in a sales order for which predictive journal entries are already
available in the prediction ledger, predictive accounting does not adjust the information in the prediction
ledger.
Predictive accounting doesn’t support Maintenance Centric Service/Repair Orders or Corrective
Maintenance Services. Therefore, Service Debit Memo Requests with reference to a service order or
service contract aren’t supported. (DP90/DP91).
Predictive accounting reduces simulated invoices only if the actual invoice contains no more than one
receivables line. Multiple receivables may occur, for example, when you create sales orders with payment
terms for holdback/retainage or installments.
Predictive accounting doesn’t support material substitution.
For example, material substitution isn’t supported when:
• An alternative material is used automatically when the originally ordered material is out of stock.
• When you replace a discontinued material with a new one to avoid selling discontinued materials to
customers.
Predictive Accounting with Service Contracts
The cancellation of an invoice that originates from the billing plan of a service contract has no impact on
the predictive revenue recognition. After an invoice is created, the corresponding predictive journal
entries are reduced. If this invoice is later canceled, this reduction is not reversed.
Predictive accounting does not support the following change processes for a service contract after a
billing document request and the corresponding invoice for the service contract have been created in the
system:
Change sold-to-party
Contract renewal for entire contract
Predictive Accounting: Predictive Commitments Management:
Only projects (WBS elements) and cost centers are supported as account assignment types.
No manual commitments are supported.
No commitment carry forward is supported.
Only purchase orders and purchase requisitions are supported.
No separate commitments for freight costs are possible.
A GR/IR account must be configured: A new commitment is posted like a predictive goods receipt, even when
the purchase order is marked as "GR non-valuated" (meaning you expect actual costs with the invoice receipt
only).
Purchase orders or purchase requisitions using a G/L account of cost element category 90 (on tab/subscreen
“account assignment”) is not supported, because the G/L account type is "Balance Sheet Account". Therefore,
the account assignment wbs-element in combination with asset is not supported.
The posting (and reduction) of commitment line items is triggered with the respective transaction currency.
All values in other currencies are calculated during each posting according to the current currency conversion
rules configured in the ledger settings. This means that after the lifetime of a purchase order or purchase
requisition, a balance of 0 can only be expected for the transaction currency. All other currencies could deviate
from 0, because of rounding differences or different currency conversion rules.
Commitments from down payments are not supported.
Commitment overhead calculation is not supported.
Planned commitment cannot be reported. Only the "current" commitment can be reported.
At the end of the lifetime of a purchasing document, you can expect a balance of 0 for the involved account
assignments only. The predictive commitment postings ignore changes to non-account assignments.
Potentially related entities like profit center, functional area, etc. will not be balanced to 0. For example, in
case the account assignment is changed, the functional area or profit center might be derived new. The
offsetting posting of such a change will only consider the change of the account assignment. It will not
consider the related profit center or the functional area.
Predictive Accounting: Universal Parallel Accounting: Predictive accounting creates predictive journal
entries in all available prediction ledgers. However, only the material master data information from the leading
ledger is used for these predictive postings. For this reason, different material prices in non-leading ledgers are not
reflected in predictive journal entries. See SAP Note 3033604.
Migrate Financial Statement Versions to Global Hierarchies: When you migrate financial statement version (FSV)
structures for alternative charts of accounts (COAs) to global hierarchies using the Migrate FSVs to Global
Hierarchies app, you need to switch to the following apps to perform these tasks: • Create new accounts for an
alternative COA and assign them to relevant operating G/L accounts: Use the Manage G/L Account Master Data
app • Assign these new accounts to a FSV hierarchy: Use the Manage Global Hierarchies app You need to switch to
these apps instead of using the Manage Chart of Accounts app. The Manage Chart of Accounts app does not
support FSV structures that are created as global hierarchies. The Manage Chart of Accounts app only supports
FSV structures that were created using the Manage Financial Statement Versions (OB58) app. This restriction only
applies to alternative COAs. For your operating COA, use the Manage Operating Chart of Accounts app. It supports
both types of FSV structures.
General Ledger Accounting:
 Cost allocations between funds and grants not possible for internal occupancy of integration objects from
intelligient real estate.
The following use case isn´t supported by Post B/S Reclassification job template:
Investment reporting.
Functional Currency:
Information for new company codes:
When you create a new company code, you must carefully decide which currency type you want to use as
functional currency. Once you´ve started to use the company code and you have posted to it, you can no
longer change the functional currency.
When you create a new company code and you don´t enter a functional currency, the functional currency is
automatically set to 10 by default.
Credit-Risk-Based Impairment:
If you use the Post Credit-Risk-Based Impairment job template in the Schedule General Ledger Jobs app,
please consider that there is no posting and reporting of utilization of loss-allowances.
Dynamic Reclassification:
• Dynamic reclassification can only be introduced and used in the Manage Global Hierarchies app. It cannot
be introduced using the Manage Financial Statement Versions app.

Valuations
The following valuations are not available for G/L accounts of type "Cash Account":
• Foreign Currency Valuation job template
• Provisions for Doubtful Receivables job template
• Perform Foreign Currency Valuation app
• Perform Further Valuations app
The following valuations are not available when you use exended open item management on GR/IR
accounts:
• Foreign Currency Valuation job template
• Advanced Foreign Currency Valuation job template
• Perform Further Valuations app
General Ledger, Asset Accounting, Contract and Lease Management, Single ledger/ Parallel ledger:
Ledger bundles are possible for four following options only:
1. Local ledger only
2. Local ledger + IFRS (free choice of which should be leading)
3. Local ledger + US GAAP (free choice of which should be leading)
4. Local ledger + IFRS + US GAAP (free choice of which should be leading)
Group Reporting:
Restrictions and additional information on Consolidation of Investments (activity-based): are collected in the
SAP Note 2812499.
Restrictions valid for Fiscal Year Variant in Group Reporting are described in the SAP Note 2844616.
Interunit Reconciliation – Group View app is not supported for customers with the initial release SAP
S/4HANA Cloud 1902 or higher. Please use the Intercompany Matching and Reconciliation (ICMR) solution
instead.
Intercompany Matching and Reconciliation (ICMR): it is possible to use a data source that has the accounting
document data stored as data entry view (in the BKPF and BSEG tables). If there are discrepancies for
matched documents, currently you can’t trigger automatic document posting back to the BKPF and BSEG
tables of the accounting side. Please enter the values manually.
The deletion of versions is currently not supported.
In the reports available in the tile Group Reports, which are based on the old queries for consolidated data (<
SAP S/4HANA Cloud 1902 release), the drill-through to the consolidation reports shows a technical document
generated by the integration task and not the document of origin.
Only one unit of measure can be assigned to a breakdown category. Data cannot be reported with a different
unit of measure for the FS (Financial Statement) items using this breakdown category.
When using old reporting logic, ledgers are assigned to consolidtion groups. It is not possible to assign
different ledgers to different consolidation groups within one single version. When multiple group currencies
are required for consolidation groups, the corresponding ledgers must be assigned to consolidation groups in
different versions.
In Currency translation, the currency translation key 6 (No retranslation of existing group currency value)
considers reported group currency values (currency translation indicator 0) or translated group currency
values (currency translation indicator 1,4) calculated by a prior execution of currency translation. As a
consequence, if a translation was already executed using a currency translation key different than 6 (and data
records are created with C/T indicators 1 & 4), the result of this translation is considered as existing group
values when executing again the translation using currency translation key 6.
In the reclassification log, the value of additional fields for the Triggering Item is initialized. This results in the
aggregation of the amounts in the Triggering Item. The additional fields are displayed only in the Journal
Entry lines.
 The maximum length of the sub item field is 10 characters. When a sender field defined for the sub item
category has a greater length, the value is truncated.
Group Reporting Analytics: It is not possible to add filters on currency keys (GC key, LC key, TC
key)while using API Views A_CnsldtnTransactionData, A_CnsldtnTransactionData_2,
A_CnsldtnTransDataRptgRules to extract data from the released analytical cubes. Please see SAP Note
3075037
Extensibility: From accounting, only custom fields with the business context "Accounting: Coding Block"
can be included in Group Reporting.
In the current release the Preparation for Consolidation Group Changes (PCC) supports consolidation method
changes (from Equity to Purchase, from Purchase to Equity) only if the following criteria are met:
- the method change occurs only once for one consolidation unit in the same fiscal year,
- this consolidation unit is not first consolidated or divested in the same fiscal year.
The field Project is not available in the new API API_CNSLDTNGRPJRNLITEM due to a technical restriction.
Also, the texts are available only the following dimensions:
•FS Item - CnsldtnFSItemText
•Cons Unit - ConsolidationUnitText
•Partner Unit - PartnerConsolidationUnitText
•subitem category - CnsldtnSubitemCategoryText
•Document Type - ConsolidationDocumentTypeText
•Segment - SegmentName
•Controlling Area - ControllingAreaName
•Cons Version - ConsolidationVersionText
•Cons Group - ConsolidationGroupText
While using the SSCUI "Set Up Payment Methods per Country for Payment Transactions" (ID: 101972),
please avoid changing any pre-delivered settings for payment method L External Payment, M Direct Debit
Customer Payments, and N Credit Card Customer Payments. The three payment mehtods are exclusively used for
Digital Payments and Customer Payments ( Scope items 1S0, 1S2, 2M0 and 2LZ). Making changes to the payment
methods will cause consistency issues.
Please note that the SAP pre-delivered payment method IDs may be renamed to different IDs in the systems if
customers occupy these IDs. It is not recommended that customers use these three IDs.
Product Cost Controlling:
Restrictions for solution Period-End Closing - Plant (‫‏‬BEI‫ )‏‬in S/4HANA Cloud:
1. Scrap variance is not supported.
2. Work in process and variance values are calculated in company code currency and group currency only.
Values in the third currency are converted during settlement run which may lead to differences in the G/L
account.
For restrictions relevant to Universal Parallel Accounting, please see SAP Note 3033604.
For restrictions relevant to Alternative Fiscal Year Variant, please see SAP Note: 3169537
For restrictions relevant for "Product Costing: Event-Based Variance", please refer to the SAP Note 2910083.
For restrictions relevant for "Product Costing: Parallel Accounting", please refer to the SAP Note 3042082.
If the SSCUI “Assign Accounting Principles to Ledgers and Company Codes” is used to change the
predelivered assignment of ledger to accounting principle, it automatically rearranges dependent asset depreciation
areas per ledger in the background upon saving your changes. However, the description of a depreciation area is
only correctly reassigned in the logon language but not in all other language. As a consequence an end user may
face confusing texts if he is logged in with a different language than during the setup. This product restriction only
comprises the area description as such, but it does not affect any business related logic. Recommendation:
execute the SSCUI in the language which is mostly appropriate in the desired company code.
SAP S4HANA Cloud Release Restriction Note for Engineer-to-Order in Finance: SAP Note 3218415
With the Fiori app Process Free Form Payments (F2564), you can't maintain the Additional Info field when
creating and processing QR-bill payments. Despite this restriction, QR-bill payments (QRR - QR reference with
QR-IBAN, SCOR - Creditor Reference ISO 11649 or NON - without reference with normal IBAN) can still be posted
and are processed by banks.
Data Controller Assignment to Business Partners: The financial transactions in Treasury and Risk
Management are Business-to-Business (B2B) transactions between your company and banks, financial
institutions, brokers, or similar institutions. Likewise, the master data required for the processes in Treasury and
Risk Management relate to companies and financial institutions. In Treasury and Risk Management, checks are
implemented that do not allow the use of business partners who are natural persons. Since the business partners in
Treasury and Risk Management are organizations, it is not necessary to assign a data controller to them. Therefore,
if you are using Treasury and Risk Management, you must not activate the data controller functions in the business
partner in the configuration activity 'Activate Data Controller for Business Partners'.
Human Resources:
The master data replication between SAP S/4HANA Cloud and SAP SuccessFactors using the SAP Cloud Platform
Master Data Integration is only released for pilot customers. If you would like to use this process please register to
the Early Adopter Care Program in SAP Customer Influence Portal.
Integration between SAP SuccessFactors Employee Central and SAP S/4HANA Cloud 2008 does not support
employees with multiple employments (Concurrent Employment, Global Assignment) and employees going
 through an inter-company transfer.
Employee central time-off API is restricted and does not support delta handling (when called with lastModified). It
is recommended to replicate no more than 120 days at a time during initial load. This can be done by setting the
parameters RETRO_PERIOD and FIXED_NO_OF_DAYS to give a sum of no more than 120 (e.g. RETO_PERIOD
= 60 (90), FIXED_NO_OF_DAYS = 60 (30). In addition, the Employee Central time-off API does not support the
replication of Availability data of contingent workers being hired as regular employees.
Contingent Worker Replication: "Change start date of work order & extend end date of work order" scenario is
possible within SAP SuccessFactors Employee Central, but replication is not supported.
Handling of freelancers is not supported, also creation through import employee/ public API and Success Factors
Employee Central has been disabled. Please use the role Service Performer instead.
Any HR-related data must go via source HR system only and not via a direct modification in Business Partner
Maintenance transaction.
It’s currently not possible to enable the external number range (PERNR) in SAP S/4HANA Cloud as described in
scope item JB1. Only new SAP S/4HANA Cloud customers who are using the assignment ID in SAP SuccessFactors
can request enablement of the feature by reporting an incident on component CA-WFD-INT.
Integration
The following interfaces between SAP Ariba Guided Buying capability and SAP S/4HANA Cloud (scope items 2NV,
3EN) are currently not supported. The solution is planned to be delivered in the upcoming releases. A Guided
Buying Requisition can be edited only until it is approved in SAP Ariba Guided Buying. The following are yet to be
supported:
Editing a PR (Purchase Requisition) and in the process adding a new line item.
Editing a PR and in the process deleting an existing line item.
Changes made to field values on purchase orders in SAP S/4HANA Cloud are not synced with the
corresponding fields on requests in Guided Buying.
The transfer of attachments added at the header level of requisitions in Guided Buying is not supported.
Supplier collaboration and request for proposals are not supported for lean services items.
Notifications on the dashboard do not include status information for requests that include lean services items.
Users can view status information about a request only by viewing the History record of the request.
Attachments once added to a line item cannot be edited. Users must first delete the attachment and then add
the updated attachment again.
Multiple copies of the same file can be sent to SAP S/4HANA Cloud. Neither the buying solution nor SAP
S/4HANA Cloud flags errors or warnings for duplicate file attachments.
The following interfaces between SAP Ariba Guided Buying capability for Central Procurement with SAP S/4HANA
Cloud (scope items 3EN) are currently not supported. The solution is planned to be delivered in the upcoming
releases. A Guided Buying Requisition can be edited only until it is approved in SAP Ariba Guided Buying. The
following are yet to be supported:
Only SAP standard purchasing requisition document types NB and NBS are supported for purchase
requisitions replicated from Guided Buying.
The restrictions mentioned in the Central Requisitioning (1XI) scope item are also applicable for the Guided
Buying for Central Procurement with SAP Ariba Buying (3EN) scope item.
For the current release, if the company codes across the (more than one) connected back-end systems are not
unique when the master data from those (more than one) connected back-end systems converge into one
Guided Buying with SAP Ariba Buying system, then custom configurations are needed to ensure that the
master data can be identified with the correct back-end system. To configure these prerequisites in Guided
Buying, have your Designated Support Contact log a service request. An SAP Ariba Support representative will
follow up to complete the request.
The following features between SAP Ariba Contracts and SAP S/4HANA Cloud (scope item 4AZ and 4B0) are
currently not supported. The solution is planned to be delivered in the upcoming releases.
Use the new Fiori app for sales order creation.
Create a milestone billing plan in a sales order with VA01. E.g. by using the order type OR and item category
CTAD.
Create a scheduling agreement with VA31.
Create a contract (value or quantity) with VA41.
Create a project (scope item J11 and J14).
Use Official Document Numbering.
Use Tax-Abroad. Tax information from BSET is not read and printed on the bill.
Use EDOC-Framework. With release to accounting a message to the government authority cannot be created.
Use Extensibility. The extensibility flow from billing item to journal entry item is not supported.
Use some special logisitic processes in delivery. BOM, Batch and Variant Configuration are not supported.
Use some special processes in Professional Service. E.g. Account-Payment and RevRec are not supported.
 The following restriction applies to the integration of SAP Subscription Billing with SAP S/4HANA Cloud (Scope
Items 57Z and 5IK):
A maximum of 25,000 subscriptions per hour can be created/changed and replicated to SAP S/4HANA Cloud
via events. In addition, the general technical constraints of the SAP Event Mesh default plan apply. If you use
this integration and want to migrate data or run any other process that result in mass changes to
subscriptions, please contact SAP beforehand by creating an incident on the component CEC-SAL-SB.
Subscription cancellations cannot be backdated. They are limited to the same day or later (the resulting
expiration date is the current date or later).
Subscription changes cannot be backdated. They can only be effective as of the same day or later.
Pending subscriptions are not replicated to a provider contract. Once replicated (after transition from pending
to complete, or if the subscription was created as active to begin with), subscriptions cannot be deleted.
The expected term of a subscription is not updated by any automatic process such as subscription renewal. If
you want to defer revenues beyond the expected term in Revenue and Cost Accounting, you need to shift the
expected term end in SAP Subscription Billing manually or using APIs based on the renewal term end.
Otherwise, revenue is recognized based on the billed amounts from SAP Subscription Billing.
A migration scenario together with contract-based revenue recognition is currently not supported. This means
that if you create a backdated subscription that has been invoiced in a legacy system, this deferred balance
position cannot be reflected in your revenue scenarios. As a result, the revenue contract in contract-based
revenue recognition will be missing these postings and cannot be completed.
For SAP Subscription Billing, a legal entity (on which basis the data residence and retention periods are
defined) corresponds to a SAP BTP subaccount. As there can only be one subaccount for a SAP Subscription
Billing tenant, the tenant is restricted to one legal entity. Accordingly, if different markets in SAP Subscription
Billing map to SAP S/4HANA Cloud sales areas for which the sales organizations belong to different legal
entities, this cannot be reflected in the data protection functionality for SAP Subscription Billing.
While you can restrict the access of business users in the SAP Subscription Billing UI based on markets, the
Data Retention Manager and Personal Data Manager provide access to all data of all markets. The use of data
protection functionality for SAP Subscription Billing therefore assumes that the data of only one data
controller is being processed within the tenant.
PO Quantity Tolerance "Unlimited Overdelivery for material items only supported for Advance Shipping
Notification
Workflow for Supplier Order Confirmation not supported.
Integration with Procurement Solutions:
Automation of Order-to-Invoice with Ariba Network (4‫‏‬A1‫)‏‬
Service Procurement with Ariba Network and SAP Fieldglass (4R2)
Automation of Source-to-Pay with Ariba Network (42‫‏‬K‫)‏‬
Subcontracting Integration with Ariba Network (5I2)
Central Procurement with SAP Ariba Sourcing (4‫‏‬QN‫)‏‬
Automation of Central Procurement Quotes with Ariba Network (5JT)
Sourcing with SAP Ariba Sourcing (4‫‏‬BL‫)‏‬
Contract Management with SAP Ariba Contracts (4AZ)
Contract for Central Procurement with SAP Ariba Contracts (4B0)
SAP S/4HANA Cloud: Restrictions for Guided Buying for Central Procurement with SAP Ariba Buying (3EN)
SAP S/4HANA Cloud: Restrictions for Guided Buying Capability with SAP Ariba Buying (2NV)
Integration of Sales with External Buyers: The SAP Note 2907674 contains information about attachment
feature that is currently not supported in the context of Integration of Sales with External Buyers (Scope Item 2EL).
Integration with Microsoft Teams
The application SAP S/4HANA for Microsoft Teams supports English only, irrespective of the logon language.
Localization:
3346137 - SAP S/4HANA Cloud 2308, Local Versions: Release Restriction Note
3346091 - SAP Document and Reporting Compliance S/4HANA Cloud 2308, Local Versions: Release Restriction
Note

Master Data:
SAP note 2690843 contains information about the searches that are currently not supported for the CDS based
search connector “Products”.
Business Partner SOAP Service: The two fields County & Township are not supported for S/4HANA Cloud.
Mass Maintenance/Mass Processing/Consolidation of Business Partner Relationships
All relationship categories using a differentiation type cannot be loaded or updated. Known relationships categories
are "FI0200", "FI0210", "FI0300", "UKM001", and "UKMSB0".
Show changed field values in Mass Maintenance/Mass Processing/Consolidation
The FIORI applications for consolidation, mass processing and mass maintenance usually show changes on field
values. This functionality is disabled due to performance reasons if more than 100000 records are to be processed.
Classification in Mass Maintenance/Mass Processing/Consolidation for Products
When using classification in consolidation, mass processing and mass maintenance for Products, theres is no
support for object dependencies. This means, that the dependencies are not considered in checks. In addition, in
 search helps for characteristic values not all special features for classification values are supported (e.g. overwrite
values).
Classification in Mass Maintenance/Mass Processing/Consolidation for Customer/Supplier
When using classification in consolidation, mass processing and mass maintenance for customer or supplier not all
generic classification features are supported. Review SAP note 2479869 for further information about the Lean
Classification.
Consolidation of active data for Business Partner Relationships
Consolidation processes of active data for business partner relationships are not supported.
Consolidation of Master Data
There is a finetuning UI to configure the matching step for consolidation of master data (Product and Business
Partner). You cannot change all parameters and settings of an existing match configuration. In case of such a
change, you will get an error message and you have to copy the old configuration into a new one. The new one can
be saved with the required changes. The following tables cannot be used to define fields which are relevant for the
matching: KSSK, AUSP, Longtext tables: *STXH and *STXL, AEOI,DRAD, MAPR
Material ledger data in Mass Maintenance/Mass Processing for Products
With the Fiori apps Manage Mass Maintenance - Products (F2505) and Manage Mass Processes - Products
(F1686A), you cannot make a mass change for material ledger prices and prices units. This could lead to
inconsistencies.
With the Fiori apps for Mass Processing (F1686A) and Mass Maintenance (F2505), the mass change of the
material type (MARA-MTART) is not supported. The field cannot be used as scope field, but file upload would
allow the change. When executing a change in these apps, there is no check, if the material type is allowed to be
changed, which could lead to inconsistencies.
Procurement:
Procurement Overview Page: List Apps are not sorted and filtered in the same way as the cards. When navigating
from the card headers, the corresponding app might be filtered and sorted in a different way than the card is
filtered and sorted in the Overview Page. This restriction only applies to the transactional cards "Monitor Purchase
Order Items" and "Monitor RFQs".
Currently, customer and vendor consignment processes and consignment stocks with a border crossing are not
supported. Only domestic consignment processes are supported.
The value “empty” is not supported by the Define Conditions tab in the value help dialog of the filters; when
applying a filter in the table settings. This restriction is applicable for the following apps:
Mass Changes to Purchase Orders
Mass Changes to Purchase Contracts
Mass Changes to Purchase Scheduling Agreements
Mass Changes to Purchasing Info Records
Mass Changes to Central Purchase Contracts
Restrictions for Create Purchase Order of Awarded Supplier Quotation: The following restriction
applies to 4RD - Direct Material Sourcing scenario process in the hub system：
As a Sourcing Manager, you access the app Manage Supplier Quotations - Sourcing Projects to create purchase
order based on awarded quotations. On Create Purchase Order screen, relevant information is pre-populated based
on the item information that is taken over from the awarded supplier quotation. If you work with the items of the
type Invest Item, the value in the field Purchasing Group is currently neither pre-filled, nor is it selectable from the
value help. To enable editing of this information, Sourcing Manager has to create purchase order by clicking Order
in status “Held”. In the connected system, purchaser responsible can then edit the created purchase order and set
the required purchasing group to finish the purchase order release procedure.
Manage Supplier Confirmations:
The following restrictions apply:

Only documents of type NB (standard purchase order) or direct copies with the same settings as NB are
supported.
Only the item categories Standard (blank) and E (Enhanced Limit) or direct copies with the same settings can be
selected.
The Manage Supplier Confirmations app cannot be used for the intercompany stock transfer process.
It is currently not supported to set up your configuration so that the Confirmation Control for Order
Acknowledgements is maintained as GR-Relevant or GR-Assignment.
For restrictions relevant for Advanced Intercompany Stock Transfer, see SAP Note 3192546.
Product Sourcing: The SourcingProject and SourcingProjectQuotation APIs contain entities and operations
related to commodity business feature handling, which is, however, not enabled in SAP S/4HANA Cloud.
Consequently, commodity-related nodes cannot be used.
Produce:
Backorder processing (BOP):
Stock transfer requisitions are not supported for selection in BOP segments. Use stock transport orders as
BOP-relevant requirements instead.
 It is not possible to use characteristic ATPRELEVANTDOCUMENTCATEGORY to differentiate document
types when defining BOP Segment anymore.
ATP:
Although the new app Configure Alternative Determination is delivered with CE2202, allowing the user to get
insights to the SAP pre-delivered alternative determinations, the initial creation of those three alternative
determinations is done when using Configure Substitution Strategy. In this app the alternative determinations
are actually used do define how a best alternative shall be determined.
Only BAdIs with a full upper case FilterImplementationName with a maximum length of 30 characters will be
considered, when creating Alternative Determinations.
When working with Availability Change Log in Advanced Available-to-Promise Processing (Scope item 1JW),
document changes in context of Production Planning and Control are not logged on material-plant level.
Hence, a BOP Run using 'Availability Change Log Filter' will not consider material-plant combinations where
only Production Planning and Control changes have occured.
Product Lifecycle Management (PLM):
Restrictions for Advanced Variant Configuration SAP S/4HANA 2302 - SAP Note 3329592.
Fiori UI for Structures:
You can only include individual elements or sub-structures between projects of the same profile (e.g.
Enterprise Project - Internal).
It is possible to upload files no larger than 100MB from SAP Fiori for SAP S/4HANA applications.
The integration scenario SAP_COM_0932 and scope item 6W9 which includes this integration scenario are
delivered and can be used with 2308.
SAP will offer the Business Technology Platform Application SAP Advanced Solution Bundling for this integration
scenario and scope item. Further information are available in note 3330113.
Professional Services:
Material determination configuration within the DIP (Dynamic Item Processor), which is used by the deprecated
Release Billing Proposal app, is not possible. Therefore, additional materials/activity types should not be created in
this scenario. Alternatively, the new Project Billing solution and its flexible material determination as described in
scope item 4E9 can be used.
Project Forecast Month in Customer Project uses the universal time zone. The project forecast in the Customer
Project Review application is set to the correct month only if a Project manager waits until the local time and the
universal time fall on the same month.
It is not possible to assign a central purchasing organization to a service organization, while purchasing itself is
possible. Please create a local purchasing organization to assign it to service organizations.
If a Purchase Order with Account Assignment Category P (Project) or U (Unknown) is used for Service
Procurement, the note field is restricted to 40 characters, the blocking functionality on work package level and the
Billing Control Category Non-billable is not supported.
Concurrent employments are not supported during maintenance of project roles that are not delivered by default.
The first valid employment of a Business Partner gets forwarded to the Sales Order.
The deprecated Release Billing Proposal app is considering the CET time zone only for billing preparation.
In Billing Proposal Item Details page, the “Address” sub section of the "Contact Details" section of "Performed by
Employee" is removed.
Customer Projects & Internal Projects: Currently, the time-dependent validity records maintained for
Activity types are not supported by customer and internal projects in the professional service context. I.e. only one
master data record should exists for an activity type,if it is used in the Customer and Internal projects.
The following capabilities are not supported for the down payment process in Professional Services:
Installment payments, output items with status “In Process” or “To be Output” of preliminary billing documents
with status “In Progress” and for which a billing document is in place do not include information on down
payments, merging down payment requests with documents of processes other than Professional Services, manual
financial postings that are conducted outside of billing.
The note section of the Prepare Billing screen of the Release Billing Proposal and Debit Memo Request application
reads only up to 40 (forty) characters of text from the billing plan item in case of fixed price billing proposals.
The Billing Info for Customer section that is maintained in the Manage Sales Order application, will be directly
available in Debit Memo Request (DMR). It will not be available in the Release Billing Proposals application.
Project Billing (scope item 4E9) does not support the usage of scale rates.
Project Billing (scope item 4E9) does not support the usage of scale rates or group conditions.
Manage Project Billing app only supports Standard and B (Price date) as the values of Pricing Date in the
customization of condition types in Manage Your Solution app. To view the relevant condition type, navigate to
Sales->Price Management->Set Condition Types for Pricing. If you use other values, you may need to do repricing
on BDR creation and the net rates may not be as expected.
If you maintain any pricing condition other than PC01 and set the configuration as Transfer Costs Only, when a
single expense posting with multiple line items is made, you must execute the repricing job to get the correct To Bill
amount for each line item.
If the 'Down Payment Requested' field includes a BDR corresponding to down payment item usage, and if there is
no permanent PBR created (permanent PBR was not there for down payment request BDRs, before 2111 release),
the entry in the corresponding dialog box will not have the PBR and it's related information.
In the Manage Project Billing app, if you click the relevant value (non zero) under the Billing in Process column,
one pop up window appears. It displays the PBR number and status. When more than one BDR is created for a
 single PBR, the status of the PBR might be incorrect.
If a cost posting is reversed and the cost posting is not part of any of the billing document requests, then the cost
posting and its reverse posting will be marked for cancellation. Further, if there is any price change, the price
change will not be applied to these cancelled postings.
The assignment-based access can be applied to control user access to the project billing elements.
To allow user access only to assigned project billing elements and the editing and creation of project billing
requests for these elements, in the business catalog SAP_PS_BC_PROJ_BLNG_PC for the Project Billing Element
Authorization (authorization object C_PRJBLGEL) option B (only assigned project billing elements) should be set
in the Write, Read, Value Help tab.
Please note that the value of Project Billing Element Authorization can be set in Write, Read, Value Help and Read,
Value Help permission. Whichever value set under both sections is set, the more liberal authorization applies.
Resource Related Intercompany Billing:
With the New Resource Related Intercompany Billing process(Feature toggle FTGL_500717- New Resource
Related Intercompany Billing is activated) only one Intercompany Sales Document is supported as input.
You cannot use the New Resource Related Intercompany Billing process(Feature toggle FTGL_500717- New
Resource Related Intercompany Billing is activated) when the ordering company or the delivering company is
in Brazil.
Scope Item 4E9 is a mandatory prerequisite for Intercompany billing. You have to activate 4E9 first. If you
started using S/4HANA cloud before the release S/4HANA cloud 2108, 4E9 was not a standard scope item
and it would not be activated in your system by default. Therefore please ensure the activation of this scope
item.
Project System / Enterprise Portfolio and Project Management:
Note text related to Billing Items (Fixed Price, Time and Expense Items) of your Project:
Fixed Price Items: if the note text is changed via the "Plan Customer Project" app, this change will presently
not be reflected in the corresponding billing proposal item entry in the "Release Billing Proposals" app.
Time and Expense Items: if the note text for an actual cost posting in the "Release Billing Proposals" app is
modified by a project manager, a modification in "My Timesheet" app by an employee will overwrite the note
text that the project manager previously created. Upon finding a different note text in the "Release Billing
Proposals" app, the project manager can manually edit/ update the note text before releasing the billing
proposal item(s).
Restrictions of SAP CoPilot while using "Release Billing Proposals" app: it is not possible to navigate to a
screenshot of Billing Proposal Item Details through collection using SAP CoPilot in a new session of the SAP
Fiori Launchpad. You will be navigated to the screen containing the list of billing proposals instead. "Go to
Linked Screen" navigates to the last saved URL of the current browser user session. Project manager can
access the "Release Billing Proposals" app, select the relevant billing proposal(s) and manually navigate to the
billing proposal items screen, if needed.
Grouped billing proposal items: when you perform a defer after date function, please expand all the grouped
entries to make sure that billing proposal items display the correct total amount and correct quantities for each
individual group.
Internal procurement/ production processes are currently not supported for Project Stock.
Editing the Planned Independent Requirement data created via Project Demand "Preliminary Procurement" does
not sync back to the data in Project Demand.
The Applications- Plan customer project, Plan Internal project, Review Customer project - does not show the
blocked employee’s master data ( ie name of the employees in project roles and Staffing, Employee Search ) even
with the additional authorization of an External Auditor role.
Project Cost Report (F2513 and F2538) shows the production order planned and actual costs in a hierarchical
format along with the project structure in Engineer to Order scenario. However the report currently does not show
the costs accurately in case the production order settles to WBS Element instead of material.
If the Supplier Invoice amount deviates from the Goods Receipt amount, then the deviation is a separate posting
listed in Prepare Billing screen of Manage Project Billing app. As this posting is not excluded from billing
automatically, this posting needs to be written-off manually to avoid billing the same.
For the Business Catalog SAP_BR_PROJ_BILLG_SPCLST Write, Read, Value Help restrictions maintained for
fields Cost Center, Profit Center, Controlling Area only will be applied in New Project Billing solution. Restrictions
maintained for any other field will not be applied.
Intercompany Concur postings created before CE 1805 will not be considered during the Intercompany billing with
the new solution of Generate Intercompany Billing Request (Feature toggle : FTGL_500717 is active).
Public Sector Management (PSM):
Financial statement version is currently not reflecting the format of US Public Sector organizations. The
functionality to support public sector-specific versions and layouts shall be achieved in the implementation project.
Leasing integration with PSM (restrictions when modified accrual accounting valuation rule used):
Depreciation calculated in Contract and Lease Management (CLM) shall not be reconciled with depreciation
posted in Asset Accounting for modified accrual valuation rule
Principal and interest expenses should belong to same group, if availability controlled (AVC)

Currency revaluation not possible when modified accrual accounting valuation rule is used.
Postings to a cost center or WBS element not possible on a non-valuated CLM contract against a Real Estate
Object.
 WBS element account assignment would not be available in the cost distribution of a worker in S4 HANA Public
Cloud for Public Sector. If an employee is created with WBS cost assignment in SuccessFactors Employee Central,
replication to S/4HANA PC for PS would have all account assignments with the exception of WBS element.
Cost allocations between funds and grants not possible for internal occupancy of integration objects from
intelligent real estate.
The integration of Treasury and Risk Management with Public Sector Management is released for money
market transactions and securities.
In addition, the following functions are currently not supported:
Instalment payments with multiple account assignment.
Cash management integration of financial transactions on fund and grant level is not supported for all
transactions yet.
Universal allocations: Only actual allocations of allocation context “Cost Centers” and allocation types
“Overhead Allocation” and “Distributions” are integrated with Public Sector Management. Other allocations
contexts (e.g. “Profit Center”) or allocation types (e.g. “Intercompany Allocations”) and plan allocations are
currently not supported.
Grants Management resource related billing of sponsors is currently only supported for projects with
profile “Project with Revenue”. The profiles “Investment Project”, “Overhead Project” and “Statistical Project” are
not (yet) supported.
User must have SAP_BR_RECM_SPECIALIST and SAP_BR_RECM_VALSPECIALIST roles inorder for the public
sector account assignments to be derived from the cost object of the valuation parameter and to persist them in
organizational assignment.
'Repost Line Items - Cost Accounting' app (F5549) is not supported for Public Sector Management.
WBS Element account assignment is not supported in automatic generation and consumption of earmarked funds
for RE-FX contract and lease management (CLM) contracts.
In order for the earmarked funds document to be updated, a change to the CO account assignment in the valuation
parameter of a RE-FX contract and lease management (CLM) contracts has be coincided with change to the posting
parameter - organizational account assignment i.e. without a change to the posting parameter, valuation parameter
account assignment changes won't be updated in the earmarked funds document.
A link (approval tab with earmarked funds information) is not available in the RE-FX contract.
Responsibility Management:
You, as data controller, are responsible for ensuring that the data used in responsibility definitions in teams is
managed in accordance with any applicable legal requirements or business needs, such as data protection
legislation or data life cycle requirements. Responsibility definitions in the Fiori app "Manage Teams and
Responsibilities" are currently not integrated in privacy by default functionality. Therefore, the responsibility
definitions in teams should not be used for the processing of personal data if this processing falls under any
applicable data protection legislation.
Sales:
Controls used in the apps "Business Process Activities" and "Aggregated Business Process Activities for Order-to-
Cash Process Performance Monitoring" cannot currently display backwards connections. So, some information
referring to previous process steps will not be reflected on the diagrams.
Batch split: freight costs entered in the delivery cannot be billed for delivery items with batch splits. The batch split
main item has zero quantity, weight and volume, but is relevant for billing. The quantities, weight and volume are
distributed among the batch split sub-items which are not relevant for pricing and billing. See also note 1921287.
Sales Billing:
When using the process ‘Quantity contract-based down payments’ (scope item I9I), rounding differences with
regards to the deducted down payments may occur in the partial and final invoices. Even though, the
complete invoice amount is covered by available down payments, a small amount e.g. 1 cent may appear as
open for payment. In FI the postings for the down payment settlement would nevertheless appear correct.
In some cases the clearing status is not set correctly in the billing document. An example would be billing
documents with installment payment terms.
Potential output issues resulting from complex billing documents with too many items
In general, SAP strongly recommends that you do not output billing documents with more than 1000 items to
output channels PRINT or EMAIL, as this can cause technical issues when Adobe Document Services renders the
PDF.
However, even a lower number of items may cause issues when compounded with the following factors:
o High complexity of the billing document itself (for example, due to an excessive amount of printable price
elements or partner details on item level)
o High complexity of the output form template (for example, due to complex loops or other business logic
scripting)
o High complexity of an accompanying BAdI implementation. While it’s preferable to embed business logic
via BAdI rather than in the form template, inefficient BAdI implementations should be avoided
All of these factors affect performance and could potentially lead to time-outs. In extreme cases, Adobe Document
Services may be overwhelmed and unable to create the PDF.
To avoid time-out issues, you can dispatch output using the Schedule Billing Output app.
Existing Smart KPI apps: Check Open Sales, Profit Margin, Credit Memo, Confirmed as Requested, Backorders and
Demand Fulfillment Smart Business apps show an additional dimension „By Product Hierarchy“, which is not
 related to any values. Unfortunately, it can´t be removed, please ignore it.
In the Read Access Logging of app "Create Sales Orders - Automatic Extraction", currently it's not possible to log
the read access of the PDF attachment. Therefore please do not select the field UPLOADFILECONTENTBINARY
when you configure the Read Access Logging for OData C_SLSORDREQFRMEXTSOURCE_SD
The Create Sales Orders – Automatic Extraction app only supports purchase order files in English or
German for now.
Restrictions for "Multiple Address Handling in SD Documents Using SAP Business Partner" are described in SAP
Note 3119621.
For restrictions relevant for Advanced Intercompany Sales, see SAP Note 3192584.
For restrictions relevant for Sell from Stock with Valuated Stock in Transit, see SAP Note 3192576.
For restrictions relevant for customers using SAP Variant Configuration and Pricing, see SAP Note 2894167.
For restrictions for Setting up Sales Order Automation (73P), see note 3389633.
In scope item 31Q (Sales Order Processing for Sales Kits), we deliver bill-of-material (BOM) variants specified by
the item category groups CPFH (Structure/Price abov) and DISH (Display - PA Header). These item category
groups cannot be used for intercompany processes.
For restrictions for CDS Views in Sales please see SAP Note 3277828.
Trade Compliance checks in S/4HANA for international trade and in SAP Global Trade Services are executed for
both main and sub item in the sales BOM.
As a consequence, for some items, quantities and values are missing and therefore license depreciation within legal
control might not be possible.
Customer Consignment processes will not trigger any Revenue Recognition postings.
SAP Analytics Cloud (SAC):
SAP Analytics Cloud does not support right to left languages at the moment.
SAP S/4HANA Cloud for invoice processing by OpenText:
This solution supports a subset of all countries supported by SAP S/4HANA Cloud. Please check the Customer Set-
Up Guide for scope item "Invoice Processing by OpenText" (1LE) for further details.
Service Management:
Extension fields defined for service contracts are not available to be selected as filter fields in the Service Contracts
Analysis app.
You are not allowed to batch release or batch cancel service contracts when the credit management is enabled for
service contracts.
Concurrent employment is not supported in S/4HANA Service process (which includes Field Service process, In-
House Repair process, Recurring Service). Service Process is working with Business Partner with Employee Role
There is equipment category P available from 2111CE and Maintenance Planner can create PRT as equipment but it
cannot be used in any maintenance processes yet. PRT as Equipment is only supported in Manufacturing
Processes.
Restrictions in this release regarding possible runtime performance issue in the Maintenance Plan Scheduling
Function Import if the parameter “MaintPlnSchedgCallObjUpToDte” is passed to Start or Restart maintenance
plan schedule OData Function Import. The performace impact is directly propotional to the number of call object
(which depends upon the lenght of the cycle) that are derived as an result of parameter
"MaintPlnSchedgCallObjUpToDte", hence for the most optimal performace please set this parameter after careful
consideration Please see SAP Note 3103155 - Restriction - Maintenance Plan Scheduling OData Function Import
Event Base Revenue Recognition is not supported with Service Order item with Ad-Hoc billing plan.
Transportation Management:
For restrictions in Transportation Management, see: 3332309 - SAP S/4HANA Cloud, Public Edition - Restrictions
for the Transportation Management processes - SAP for Me
Two Tier:
For Two Tier-relevant restrictions please see SAP Note 3219412.

Manual Activities

This document refers to

SAP Component Title
Note/KBA

2907674 SD-SLS-EDI Attachments in Sales Order (Customer Return) EDI SOAP messages - SAP S/4HANA Cloud

2748775 LO-MD-MM Productive Cloud system delivered with unwanted Products already created

1921287 LE-SHP-GF Pricing with scale conditions in delivery with batch split

921287 SCM-APO-INT- Underdelivery tolerance is not saved into Live Cache

SLS

3389633 SD-ANA-2CL Restrictions for Setting up Sales Order Automation (73P)

3346137

3346091 CA-GTF-CSC- SAP Document and Reporting Compliance S/4HANA Cloud 2308, Local Versions: Release
DRC Restriction Note

3345547 PM Unable to Restrict Business Partners Using Data Controller in SAP S/4HANA Asset Management

3340933 XX-SER-REL SAP S/4HANA Cloud 2308 in a 3-system landscape: Release Restriction Note

3332309 TM-2CL SAP S/4HANA Cloud, Public Edition - Restrictions for the Transportation Management processes

3329592 LO-VCH Restrictions for Advanced Variant Configuration SAP S/4HANA 2308 CE

3277828 SD-SLS SAP S/4HANA Cloud for Sales: Restrictions for CDS Views

3232739 FI-GL-GL-F Restriction Note for Currency Translation for Country/Region for S/4HANA Cloud

3222253 XX-SER-REL SAP S/4HANA Cloud 2302: Release Information Note

3219412

3218415 CO-PC-OBJ SAP S/4HANA Cloud: Release Restriction Note for Engineer-to-Order in Finance

3213556 MM-FIO-PUR- Difference in Behavior of Net Price Calculation in SAP Fiori Apps for Purchase Contracts,
SQ-SCH Purchase Scheduling Agreements, and Central Contracts (SAP S/4HANA Cloud 2208)

3202464 MM-PUR-GF-EDI SAP S/4HANA Cloud: Restrictions for Automation of Source-to-Pay with SAP Business Network
(42‫‏‬K‫)‏‬

3194703 BNS-INT-ARI SAP S/4HANA Cloud: Restrictions for Automation of Order-to-Invoice with SAP Business
Network (4A1)

3192584 XX-SER-REL SAP S/4HANA Cloud: Restrictions and General Information for Advanced Intercompany Sales

3192576

3192546 XX-SER-REL SAP S/4HANA Cloud: Restrictions and General Information for Advanced Intercompany Stock
Transfer

3182922

3169537 FI-GL SAP S/4HANA Cloud: Release Restriction Note for the Alternative Fiscal Year Variant

3119621 XX-SER-REL SAP S/4HANA Cloud: Restriction Note for "Multiple Address Handling in SD Documents Using
SAP Business Partner"

3112356 LO-MD-MM TestDataIndicator flag not supported in Product SOAP services

3103155 PM-PRM-MP Restriction - Maintenance Plan Scheduling OData Function Import

3075639 CA-RT-AM AM 4.0: Reuse Fiori Library - Column position sort fix Manage Store Area and Capacity

3075037 FIN-CS-EA FIN Group Reporting: Restriction on API and Custom CDS Views

3070606 CA-DT-TDR SAP S/4HANA Cloud, Test Data Refresh (TDR) - Information Note

3042082 CO-PC-OBJ-2CL SAP S/4HANA Cloud: Parallel Accounting for Event-Based Production Accounting (3F0)

3040235 PM-PRM-MP Unable to navigate to Create Maintenance Plan(IP41) using “Schedule Maintenance Plan”
(SAPGUI for HTML) App (IP10)

3036785

3033604 XX-SER-REL SAP S/4HANA Cloud: Release Restriction Note for Parallel Accounting

2999428 CA-LT-MC Collective Note for extensions via Model Your Migration Objects - Migration Object Modeler App
in SAP S/4HANA Cloud, public edition (Migrate Data Using Staging Tables)

2991264 CO-OM-OPA-D Predictive Commitment: Error F5 727, Limit of Account Assignments

2989459 FIN-FSCM-BNK CPON BCM: Processing Incomplete Pain.002 with BAdI

2975653 CA-GTF-IAM Identity and Access Management (IAM): Change Overview for SAP S/4HANA Cloud

2910083 CO-PC-OBJ-2CL SAP S/4HANA Cloud: Event-Based Variance Posting for Product Cost by Order

2907372 FI-GL-GL-F UPDATE: Restriction Note for RITA in SAP S/4HANA CE2005 and further Releases: 'Registration
for Indirect Taxation Abroad: Not supported Apps, Countries and Processes.'

2894167 LOD-CPS Differences between Pricing service and ERP’s sales pricing

2844616 FIN-CS Fiscal year variant: Informations and restrictions

2812499 FIN-CS-COR FAQ Activity-based consolidation of investments in SAP S/4HANA Cloud for group reporting

2792363
2768916 CA-GTF-HSB Potential unauthorized access to data when peforming search in the Fiori Launchpad Search UI

2737228 CO-PC-OBJ-2CL SAP S/4HANA Cloud: Event-Based Work in Process (WIP) Posting for Product Cost by Order

2690843 LO-MD-MM CDS based search connector "Products"

2540701 BC-SRV-APS-GKE Custom CDS Views – Necessary Adoptions after Upgrade

2540696 BC-SRV-APS-GKE Custom CDS Views – Content Rules

2440096 XX-SER-REL SAP S/4HANA Cloud 1705 (and all later releases) Restrictions Internal US Tax Calculation

2428021 XX-SER-REL S/4HANA Cloud 1711 (and later releases): Restrictions on WebGUI/HTML GUI

This document is referenced by

SAP Note/KBA Component Title