PUBLIC

Documentation for SAP Note 3117942

ATCUD for Contract Accounting: Preliminary Customizing
Documentation
INTRODUCTION

This document contains customizing documentation and F1 help documentation that has been created or
updated for using the ATCUD code for Contract Accounts Receivable and Payable (FI-CA). The final
documentation will be provided in the next Support Package.

For more information, see SAP Note 3117942.

View: V_FKKPT_NUM_RULE
Define ODN and SAF-T Invoice Number Structure

Use

In this customizing activity, you define the number structure (number range objects, subobjects, and number range
intervals) to be used for documents created in your company codes in different fiscal years. This requires the
following activities:

• Specify whether official document numbering only is required, or whether official document numbering
and digital signature are required (and consequently SAF-T reporting).

• Enter the prefix for the official document number and the prefix (internal code and series ID) for the SAF-T
Invoice Number.

• Enter the series starting with K. Do this to request the validation code from the tax authority for printing the
ATCUD and the QR code (which also contains the ATCUD) on these documents.

• Request the validation code from the tax authorities for each relevant number range. The ATCUD
comprises of a validation code and document number, separated by a minus sign. For this request, the
VAT Registration Number of the company code, the Series ID and the SAF-T Document Type are
required.

• Use transaction code GLO_PT_SVC - Manage Series Validation Code for entering the validation code.

• Specify the invoice type (for example: invoice, credit note, debit note).

Only number range intervals registered in this customizing activity are processed at event 1190 (see also the
FKK_EVENT_1190_PT_2 function module) and are called at event 1191.

Activities

1. Enter the number range object and number range number. If required, enter the number range
subobject and the To Fiscal Year of the number range object.
2. Define whether digital signatures are required for documents using the specified number range. If so,
define whether the documents are reported in the SAF-T file.
You have the following options:

o Eligible for ODN and Digital Signature (documents using this number range are reported in the
SAF-T file)

o Eligible for ODN (documents using this number range are not reported in the SAF-T file)

3. Specify the company code and year for which the number range is relevant.

2
 4. Define the prefix for the official document numbers. To guarantee the uniqueness of official document
numbers, you have to enter different ODN prefixes for each entry.
5. Define the following parameters for SAF-T reporting (only relevant if you selected Eligible for ODN and
Digital Signature in step 2):

o Internal Code: It is recommended that you enter either FT, ND or NC as the internal code.

o Series ID: To be able to request the validation code for ATCUD, the series must start with K and
you must format the series according to certain rules. The series must be unique within the
company code. After assigning this validation code in Manage Series Validation Code (TC
GLO_PT_SVC), the series should not be adjusted. For more information, see Naming
Conventions of Series IDs (ATCUD)

o Internal Code and Series: Both make up the prefix for the SAF-T invoice number. For information
about the relevance of the Internal Code for Utilities (IS-U), see the F1 help documentation of the
Internal Code field in the Dependencies section.

o Invoice Type: This setting allows you to differentiate between FT for invoices, NC for credit
memos, and ND for debit memos in the SAF-T file by defining separate number ranges for each
document type. The invoice type is required for the request of the validation code from the tax
authority. After assigning this validation code in Manage Series Validation Code, Invoice Type
should no longer be adjusted in customizing.

Naming Conventions for Series IDs (ATCUD)

To be able to request the validation code from the tax authorities for the number range series, you must format the
series according to the following rules:

• Use the following for the first character of the series ID, depending on the application area:

Application area Series ID

FI-CA K

• Adhere to the minimum and maximum field lengths:

Application area Required characters

FI-CA 12

• For the remaining characters, only use [A-Z], [0-9], and [._-].

• Don't use separators at the beginning or end of the series ID.

• Don't use 2 or more consecutive separators.

Example

• K2123 with 21 for NR, 23 for Year 2023

3
www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.