SAP S/4HANA for Subscription Billing, Sales and Distribution Option

USER GUIDE | PUBLIC

Document Version: 1.0 – 2017-11-17

SAP S/4HANA for Subscription Billing, Sales and

Distribution Option

Release 1.0

THE BEST RUN

Content

1 SAP S/4HANA for Subscription Billing, Sales and Distribution Option....................3

1.1 Changes and New Features in SAP S/4HANA for Subscription Billing, Sales and Distribution

Option 1.0.................................................................. 4

2 Integration of CI with SD and AP................................................ 5

2.1 Internal Transfer..............................................................5

Process Overview.......................................................... 5

Single Transfer to SD Invoice...................................................7

Mass Transfer to SD Invoices.................................................. 7

Cancellation Process........................................................8

Partner Settlement.........................................................9

2.2 Distributed Transfer...........................................................13

Process Overview for Transfer to SD Invoice.......................................13

Partner Settlement in Distributed Scenario........................................14

2.3 Integration of CI with SD using External Billing Document Request..........................16

Single Transfer to SD Invoice..................................................17

Mass Transfer to SD Invoices..................................................17

Cancellation Process....................................................... 17

3 Payment by Payment Cards................................................... 18

4 Archiving................................................................. 19

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Content

1 SAP S/4HANA for Subscription Billing,

Sales and Distribution Option

Using SAP S/4HANA for subscription billing with the sales and distribution option, you can take consumption

billing data originating from SAP Convergent Invoicing (CI), transfer it to SAP Sales and Distribution (SD), and

then post the revenue in Accounts Receivable (FI-AR).

Product Information

Product SAP S/4HANA for subscription billing, sales and distribution

option

Release 1.0

Based On SAP S/4HANA 1511

Product Assistance Published November 2017

The integrative approach used in Billing in Contract Accounts Receivable and Payable (FI-CA-BI) provides BIT

(billable item) management and pre-billing processes as part of SAP Convergent Invoicing. With the sales and

distribution option for SAP S/4HANA subscription billing, you can make full use of the integrative capabilities of

SAP CI for the creation of billing documents. On the basis of these CI billing documents, you can then create

invoices in SAP Sales and Distribution with accounting in FI-AR. This enables you to implement your business

process starting with the priced consumption of a service, through billing, up to the nal dispatching of invoices

to customers.

Features

● Invoicing for aggregated consumption data using SD Billing in both internal and distributed scenarios.

● Optimization for mass and parallel processing

Before You Start

Before you begin to integrate SD Billing with SAP Convergent Invoicing, additional set-up and conguration

activities are required. For details, please see the Administrator's Guide for SAP S/4HANA for Subscription

Billing, Sales and Distribution Option 1.0.

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

P U B L I C 3

1.1 Changes and New Features in SAP S/4HANA for

Subscription Billing, Sales and Distribution Option 1.0

This section of SAP Library provides an overview of the changes and new features that have been introduced in

SAP S/4HANA for Subscription Billing, Sales and Distribution Option 1.0 and have been made available from

SAP S/4HANA OP 1511 onwards, except the integration of CI with SD using the external billing document

request which is available from SAP S/4HANA OP 1709 onwards only.

Change More Information Relevant Component

You can take billing documents created

in SAP Convergent Invoicing (CI) and

create invoices for them using Ac

counts Receivable (FI-AR) in SAP Sales

and Distribution (SD).

Integration of CI with SD and AP [page

SOLINVE 800 and above

You can transfer single billing docu

ments or large numbers of documents

originating from SAP Convergent In

voicing to SD invoices.

Single Transfer to SD Invoice [page

7]Mass Transfer to SD Invoices [page

SOLINVE 800 and above

You can settle charges with the partner

for the use of its products, services, in

frastructure and so on.

Partner Settlement [page 9] SOLINVE 800 Feature Package 01 and

above

You can enable payments using pay

ment cards for Convergent Invoicing

(CI) transactions invoiced through

Sales and Distribution (SD) billing inter

face

Payment by Payment Cards [page 18] SOLINVE 800 Feature Package 01 and

above

You can transfer CI billing documents

from one or multiple systems to one SD

system to create invoices

Distributed Transfer [page 13] SOLINVE 800 Feature Package 02 and

above

You can choose the integration mode to

specify if the legal invoices are created

directly or external billing document re

quests are created rst.

Integration of CI with SD using External

Billing Document Request [page 16]

SOLINVE 800 Feature Package 02 and

above (can be used only with SAP S/

4HANA OP 1709)

4 P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

2 Integration of CI with SD and AP

The basic process for integrating SAP Convergent Invoicing (CI) with SAP Sales and Distribution (SD) entails

the transfer of CI billing documents into invoices in SD and the performance of additional data mapping and

enrichment.

Starting from SAP S/4HANA 1709, you can create legal invoices directly from a CI billing document or use

Omnichannel Convergent Billing to create external billing document requests rst and then converge the

billing data from SD documents and the CI billing documents into combined customer invoices. For more

details go to the SAP Help portal, navigate to SAP S/4HANA, and choose your relevant version. Go to Product

Assistance Enterprise Business Applications Sales Order and Contract Management Sales Billing

Billing (SD-BIL) Billing Processing Billing Methods Omnichannel Convergent Billing .

For more information on integration using external billing document request, please refer to section Integration

of CI with SD using External Billing Document Request [page 16].

There are two scenarios in which the CI billing documents are transferred:

● Internal: The billing documents issued from SAP Convergent Invoicing (CI) are processed in the same SAP

system

● Distributed: The billing documents issued from SAP Convergent Invoicing (CI) are transferred to SD/AP of

another SAP system.

Related Information

Internal Transfer [page 5]

Distributed Transfer [page 13]

2.1 Internal Transfer

With this feature, it is possible to process CI billing documents in the same SAP system to be processed in

SD/AP.

2.1.1 Process Overview

Prerequisites

Before starting, you must do the following:

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

P U B L I C 5

● Enter master data for business partners, customers, and contract accounts to be invoiced.

● Create provider contracts.

Number Ranges

Note the following number range restrictions that apply when transferring CI billing documents from CI to SD:

● Numbers for SD reference documents are limited to 10 digits.

● Item numbers in SD can have a length of up to 6 digits. This means that an invoice in SD cannot have more

than 999,999 items.

Process Steps

As a prerequisite for starting the invoicing process, invoicing orders must exist. Invoicing orders are created

when a CI billing document is created. They are used for CI billing documents that have not yet been

processed. The related invoicing order is deleted when a CI billing document is invoiced successfully.

The process steps for transferring data from CI to SD are as follows:

1. Data selection

○ When you select the invoicing orders for the invoice integration process, all invoicing orders created

until that point in time are taken into account.

○ CI billing documents are selected from the invoicing orders in CI. These CI billing documents collect

the aggregated consumption data in the component Billing in Contract Accounts Receivable and

Payable (FI-CA-BI). These CI billing documents are source documents for the integration into SD

Billing.

2. Data mapping

○ CI billing document items originating in CI are mapped to the communication structure for the SD

billing interface for external data.

○ Note that due to dierences in basic document structure, if a single CI billing document contains more

than one item, it is mapped as one main item and its corresponding subitems in SD.

3. Creation of invoices in SD Billing

○ Legal invoices in SD Billing are created.

4. Update

○ The system writes the created invoices to the database, deletes invoicing orders, and creates

document ow entries.

You can perform invoice creation in SD for single CI billing documents or for mass data.

Related Information

Single Transfer to SD Invoice [page 7]

Mass Transfer to SD Invoices [page 7]

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

2.1.2 Single Transfer to SD Invoice

Using the transaction /SOIN/CI_SD_SINGLE, you can create an SD invoice for one individual CI billing

document originating from SAP Convergent Invoicing (CI).

Context

You want to transfer a single CI billing document from CI to SD Billing.

Before transferring a CI billing document, you can analyze invoicing orders. To do this, use transaction

FKKINV_MON (Display Invoicing Orders) in the SAP Easy Access screen.

Procedure

1. Use the transaction /SOIN/CI_SD_SINGLE (Single Transfer CI to SD).

2. Enter a CI billing document number.

3. Run the program.

4. An application log is displayed showing all of the messages that occurred during the transfer.

Results

This results directly in a legal invoice in SAP Sales and Distribution.

You can also run the SD invoice creation for a single CI billing document in simulation mode. To do this, select

the Simulation checkbox.

2.1.3 Mass Transfer to SD Invoices

Using the transaction /SOIN/CI_SD_TRANS_MA, you can create SD invoices for mass amounts of CI billing

documents originating from SAP Convergent Invoicing (CI) in a parallel run. Parallel processing is also possible.

The invoice creation run uses the mass activity functionality available in FI-CA to reduce the processing time.

Context

You want to transfer many CI billing documents from CI to SD Billing.

Before you transfer CI billing documents, you can analyze invoicing orders. To do this, use transaction

FKKINV_MON (Display Invoicing Orders) in the SAP Easy Access screen.

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

P U B L I C 7

Procedure

1. Use the transaction /SOIN/CI_SD_TRANS_MA (Mass Activity Transfer from CI to SD).

2. Enter a date and identication. If required, you can maintain a variant in technical settings for

parallelization settings.

3. Select the desired business partners.

4. Run the program.

5. An application log is displayed showing all of the messages that occurred during the transfer.

Results

The invoice creation run creates legal invoices directly in SAP Sales and Distribution.

You can also run the invoice creation for mass transfer of documents in simulation mode. To do this, select the

Simulation checkbox.

For general information, see the documentation about data processing in mass runs in Contract Accounts

Receivable and Payable. You can nd this in the product assistance for SAP S/4HANA on SAP Help Portal at

http://help.sap.com/s4hana under Industries.

2.1.4 Cancellation Process

You can also cancel SD invoices that have been created as part of the integration of SAP Convergent Invoicing

(CI) with SD Billing.

When you cancel invoices or invoice items that originated from CI billing documents, the following steps are

performed:

1. All invoice items related to a single CI billing document are canceled together.

2. New invoicing orders are re-created for the relevant CI billing documents.

The CI billing documents can then be included in the next transfer of data from CI to SD Billing for invoice

creation.

3. The document ow between the CI billing document and the SD billing document is deleted.

The cancellation process described here does not aect the standard reversal process for Billing in SAP

Convergent Invoicing.

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

2.1.5 Partner Settlement

The basic process for integrating SAP Convergent Invoicing (CI) with Accounts Payable (AP) entails the

transfer of pre-billing documents for partner in CI into invoicing and accounting in Accounts Payable and the

performance of additional data mapping and enrichment.

You can view the accounting document in the SAP Easy Access screen, for this, choose Accounting

Financial Accounting Accounts Payable Document Display or use transaction FB03.

 Note

When working in an end-to-end scenario, you must do the following:

● Set up your SAP ERP, SAP CRM, and SAP Convergent Charging systems in such a way that provider

contracts are successfully replicated from your CRM system to your ERP system and to Convergent

Charging.

● Make sure that master data such as products, business partners or customers, and contract accounts

are replicated consistently among all.

Process

As a prerequisite for starting the invoicing process, invoicing orders must exist. Invoicing orders are created

when a billing document is created. They are used for billing documents that have not yet been processed. The

related invoicing order is deleted when a billing document is invoiced successfully.

The billing document must have a partner agreement as the predecessor for the integration of CI with AP to

work.

The process steps for transferring data from CI to AP are as follows:

1. Data Selection

○ When you select the invoicing orders for the invoice integration process, all invoicing orders created

until that point in time are taken into account.

○ Billing documents are selected from the invoicing orders in CI. These billing documents in CI contain

the aggregated rated consumption data in the Billing component in Contract Accounts Receivable and

Payable (FI-CA-BI). These billing documents are source documents for the integration with AP.

○ Only those billing documents which have the related contract category as partner agreement will be

transferred to Accounts Payable

2. Data Mapping

○ Billing document items originating in CI are mapped to the communication structure for the

accounting interface for external data. If the billing documents contain multiple items, the total

amount from the CI billing document items is calculated and the vendor line item is created. There are

multiple G/L line items which correspond to a one to one mapping with the CI billing document items.

The CI billing document and the related AP document created has one to one mapping. The

accounting document type is determined based on the billing process and sub process.

○ The G/L Account is determined based on the Company Code, Billing Process, Subprocess, invoice item

type which can be maintained in Customizing for SAP S/4HANA for Subscription Billing, Sales and

Distribution Option under Sales and Distribution Billing Billing Documents Integration with

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

P U B L I C 9

Convergent Invoicing Assignment of CI Processes to AP Document Types Assign CI Processes at

Item Level for AP

3. Creation of accounting document

Depending upon the accounting document type maintained, the accounting document is created in

Accounts Payable.

4. Update

The system writes the created invoices to the database, deletes invoicing orders, and creates document

ow entries.

5. Navigation to the source CI billing document.

6. You can see the source CI billing document for the AP document using the Original document option.

7. Invoicing History

You can view the corresponding accounting document created for the partner CI billing document in the

Invoicing History tab of partner CI billing document. You can also navigate to the accounting document

displayed in the Invoicing History tab.

You can perform accounting document creation for single CI billing documents and for multiple CI billing

documents using mass activity.

2.1.5.1 Single Transfer to Accounts Payable Document

Using the transaction /SOIN/CI_SD_SINGLE, you can create an Accounts Payable document for one individual

partner Billing Document originating from SAP Convergent Invoicing (CI)

Context

Before transferring a CI billing document, you can analyze invoicing orders. To do this, use transaction

FKKINV_MON (Display Invoicing Orders) in the SAP Easy Access screen.

Procedure

To transfer a single billing document from CI to AP, proceed as follows:

1. Use the transaction /SOIN/CI_SD_SINGLE.

2. Enter a partner CI billing document number.

3. Run the program.

4. An application log is displayed showing all of the messages that occurred during the CI-AP transfer.

For the partner CI billing document entered, a single AP document is created with reference transaction

as/SOIN.

You can also run the SD invoice creation for a single CI billing document in simulation mode. To do this,

choose the Simulation checkbox.

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

2.1.5.2 Mass Transfer to Accounts Payable Document

Using the transaction /SOIN/CI_SD_TRANS_MA, you can create an Accounts Payable document for mass

amounts of partner billing documents originating from SAP Convergent Invoicing (CI) in a parallel run. Parallel

processing is always possible. The AP document creation run uses the mass activity functionality available in

FI-CA to reduce the processing time.

Context

Before transferring a CI billing document, you can analyze invoicing orders. To do this, use transaction

FKKINV_MON (Display Invoicing Orders) in the SAP Easy Access screen.

Procedure

To transfer billing documents from CI to AP, proceed as follows:

1. Use the transaction /SOIN/CI_SD_TRANS_MA.

2. Enter a Date ID and Identication. If required, you can maintain a variant in Technical Settings for

parallelization settings.

3. (Optional) Select the desired Business Partner.

4. If you further wish to lter the CI billing document selection, choose the Custom Selections button and

select the desired Billing Process, Subprocess, Contract, Invoice From. It is not mandatory to choose the

values for these options available.

5. Save the mass run.

6. Run the program.

7. An application log is displayed showing all of the messages that occurred during the transfer.

For each partner CI billing document, a follow up AP document is created.

You can also run the invoice creation for mass transfer of documents in simulation mode. To do this, select

theSimulation run checkbox.

For more general information, see the relevant documentation about data processing in mass runs for

Contract Accounts Payable and Receivable (FI-CA) on SAP Help Portal.

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

P U B L I C 11

2.1.5.3 Accounts Payable Document Reversal

You can reverse Accounts Payable document that has been created as part of the integration of SAP

Convergent Invoicing (CI) with Accounts Payable.

Context

When you reverse AP document that originated from the partner billing document in CI, the following steps are

performed:

1. The whole AP document is reversed and a reverse AP document is also created.

2. New invoicing orders are re-created for the relevant CI billing documents.

The CI billing documents can then be included in the next transfer of data from CI to AP.

3. The document ow between the CI billing document and the AP document is deleted.

 Caution

AP documents with reference transaction /SOIN, which are created using SAP Flexible Solution Billing

cannot be reversed using the standard transaction FB08

Similarly, you cannot reverse the AP Documents created using standard transaction using SAP Flexible

Solution Billing.

Procedure

The cancellation process described here does not aect the standard reversal process for Billing in Convergent

Invoicing

1. Use transaction /SOIN/CI_AP_REVERSE

2. Enter the AP Document Number, Company Code, Fiscal Year, and the reason for reversal.

3. Run the program.

4. An application log is displayed showing all messages that occurred during the reversal.

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

2.2 Distributed Transfer

With this feature, it is possible to transfer CI billing documents from single or multiple CI systems into one SD

system to create SD invoice.

2.2.1 Process Overview for Transfer to SD Invoice

The process for distributed scenario is similar to that of internal scenario.

Prerequisites

Before starting, you must do the following:

● Enter master data for business partners, customers, vendors, and contract accounts to be invoiced.

● Create provider contracts.

Number Ranges

Note the following number range restrictions that apply when transferring CI billing documents from CI to SD:

● Numbers for SD reference documents are limited to 10 digits.

● Item numbers in SD can have a length of up to 6 digits. This means that an invoice in SD cannot have more

than 999,999 items.

● In case of multiple CI systems, the number range for CI billing documents must be dierent in dierent

systems

Process Steps

As a prerequisite for starting the invoicing process, invoicing orders must exist. Invoicing orders are created

when a CI billing document is created. They are used for CI billing documents that have not yet been

processed. The related invoicing order is deleted when a CI billing document is invoiced successfully.

The process steps for transferring data from CI to SD are as follows:

1. Data selection

○ When you select the invoicing orders for the invoice integration process, all invoicing orders created

until that point in time are taken into account.

○ CI billing documents are selected from the invoicing orders in CI. These CI billing documents collect

the aggregated consumption data in the component Billing in Contract Accounts Receivable and

Payable (FI-CA-BI). These CI billing documents are source documents for the integration into SD

Billing.

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

P U B L I C 13

2. Data Mapping

○ CI billing document items originating in CI are mapped to Communication structures and doc ow will

be passed to AIF interface in SD system using interface /SOIN/CISD.

○ Note that due to dierences in basic document structure, if a single CI billing document contains more

than one item, it is mapped as one main item and its corresponding subitems in SD.

3. Update in CI system

○ Create partial doc ow and delete invoicing orders.

4. Processing in AIF in SD system

○ Enrich the data in communication structure with SD relevant data mapping.

○ Validate data in communication structure.

5. Creation of invoices in SD Billing

○ Legal invoices in SD Billing are created.

○ AIF log is updated.

6. Update in SD

○ The system writes the created invoices to the database and creates document ow entries.

○ Trigger AIF interface /SOIN/SDCI in CI system to update doc ow in CI system.

7. You can perform invoice creation in SD for single CI billing documents or for mass data.

 Note

In distributed scenario, the process of single or mass transfer to SD invoice and cancellation is similar

to that in the internal scenario. For further details refer to Internal Transfer [page 5].

Related Information

Single Transfer to SD Invoice [page 7]

Mass Transfer to SD Invoices [page 7]

Cancellation Process [page 8]

2.2.2 Partner Settlement in Distributed Scenario

In distributed scenario, CI data can be transferred from multiple CI systems to one AP system. AIF is used as

interface to transfer data between CI and AP systems.

The basic process for integrating SAP Convergent Invoicing (CI) with Accounts Payable (AP) in distributed

scenario is similar to internal scenario. Please refer to section Internal Transfer [page 5] for basic process.

Process

As a prerequisite for starting the invoicing process, invoicing orders must exist. Invoicing orders are created

when a billing document is created. They are used for billing documents that have not yet been processed. The

related invoicing order is deleted when a billing document is invoiced successfully.

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

The billing document must have a partner agreement as the predecessor for the integration of CI with AP to

work.

The process steps for transferring data from CI to AP are as follows:

1. Data Selection

○ When you select the invoicing orders for the invoice integration process, all invoicing orders created

until that point in time are taken into account.

○ Billing documents are selected from the invoicing orders in CI. These billing documents in CI contain

the aggregated rated consumption data in the Billing component in Contract Accounts Receivable and

Payable (FI-CA-BI). These billing documents are source documents for the integration with AP.

○ Only those billing documents which have the related contract category as partner agreement will be

transferred to Accounts Payable

2. Data Mapping

○ Billing document items originating in CI are mapped to the communication structure for the

accounting interface for external data.

○ Communication structure and doc ow structures passed to AP system through AIF interface /SOIN/

CIAP.

○ If the billing documents contain multiple items, the total amount from the CI billing document items is

calculated and the vendor line item is created. There are multiple G/L line items which correspond to a

one to one mapping with the CI billing document items. The CI billing document and the related AP

document created has one to one mapping.

○ The accounting document type is determined based on the billing process and sub process.

○ The G/L Account is determined based on the Company Code, Billing Process, Subprocess, invoice item

type which can be maintained in Customizing for SAP S/4HANA for Subscription Billing, Sales and

Distribution Option under

Sales and Distribution Billing Billing Documents Integration with

Convergent Invoicing Settings for Distributed CI and SD/AP Systems Assignment of CI Processes

to AP Document Types Assign CI Processes at Item Level for AP

3. Update in CI system

○ Delete invoicing orders in CI system.

○ Create docow with partial information

4. Data mapping in AIF

○ Enrich the data in communication structure with AP relevant data mapping.

○ Validate data in communication structure

5. Creation of accounting document

Depending upon the accounting document type maintained, the accounting document is created in

Accounts Payable.

6. Update

○ Doc ow is created in AP system.

○ Trigger AIF interface /SOIN/APCI in CI system to update doc ow in CI system.

7. Navigation to the source CI billing document.

8. You can see the source CI billing document for the AP document using the Original document option.

9. Invoicing History

You can view the corresponding accounting document created for the partner CI billing document in the

Invoicing History tab of partner CI billing document. You can also navigate to the accounting document

displayed in the Invoicing History tab.

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

P U B L I C 15

You can perform accounting document creation for single CI billing documents and for multiple CI billing

documents using mass activity.

 Note

The process of single or mass transfer to Accounts Payable and reversal of AP documents is similar to that

in the internal scenario. For more information, refer to section Partner Settlement [page 9]

Related Information

Single Transfer to Accounts Payable Document [page 10]

Mass Transfer to Accounts Payable Document [page 11]

Accounts Payable Document Reversal [page 12]

2.3 Integration of CI with SD using External Billing

Document Request

The external billing document request allows the system to create a billing document request for SD external

business transactions before the legal invoice is created.

Prerequisites

The prerequisites and process steps for normal transfer to SD Billing are also applicable for integration of CI

with SD using external billing document request (EBDR). For more information, see section Internal Transfer

[page 5].

Process Overview

The creation of invoices in SD Billing depends upon the integration mode selected, based on which the legal

invoices are either created directly or external billing document requests are created rst. For this, you must

maintain the relevant settings in Customizing for SAP S/4HANA Subscription Billing under Sales and

Distribution

Billing Billing Documents Integration with Convergent Invoicing Specify Mode for

Integrating CI with SD Billing .

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

2.3.1 Single Transfer to SD Invoice

Using the transaction /SOIN/CI_SD_SINGLE, you can create an SD invoice for one individual CI billing

document originating from SAP Convergent Invoicing (CI).

For more information see Single Transfer to SD Invoice [page 7].

However, now the result is an external billing document request in SAP Sales and Distribution, from which in a

later step you can create a convergent legal invoice in SD Billing.

2.3.2 Mass Transfer to SD Invoices

Using the transaction /SOIN/CI_SD_TRANS_MA, you can create SD billing document requests for mass

amounts of CI billing documents originating from SAP Convergent Invoicing (CI) in a parallel run.

Parallel processing is also possible. The invoice creation run uses the mass activity functionality available in FI-

CA to reduce the processing time. For more information, see Mass Transfer to SD Invoices [page 17].

For each CI billing document one SD billing document request is created.

2.3.3 Cancellation Process

You can also cancel SD invoices that have been created as part of the integration of SAP Convergent Invoicing

(CI) with SD Billing.

When you cancel invoices that contain external billing document requests, these are re-opened to be invoiced

again, and only the document ow between the CI billing document and the SD billing document is updated.

You use transaction /SOIN/CI_EBDR_REJECT to reject external billing document requests that originated

from CI billing documents. The following steps are performed:

1. The external billing document request is rejected, and not open to invoicing in SD Billing any more.

2. New invoicing orders are re-created for the relevant CI billing documents.

The CI billing documents can then be included in the next transfer of data from CI to SD Billing for invoice

creation.

3. The document ow between the CI billing document and the SD billing document is deleted.

The cancellation process described here does not aect the standard reversal process for Billing in SAP

Convergent Invoicing.

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Integration of CI with SD and AP

P U B L I C 17

3 Payment by Payment Cards

Payments using payment cards is enabled for Convergent Invoicing (CI) transactions invoiced through Sales

and Distribution (SD) billing interface.

Payment cards assigned to a business partner can be used to process payments for subscription or

consumption related data coming from Convergent Invoicing being invoiced with SD Billing. In an integrated

scenario with CRM, the payment card can be assigned to the corresponding order or solution quote. During the

invoicing process in ERP, the payment information is assigned to the SD invoice including an authorization

process so that the card data can be taken into account during the settlement process.

For an end to end scenario on payment cards, refer to Extended Payment Cards Functions.

18 P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Payment by Payment Cards

4 Archiving

To reduce the load of your database, you can archive data that you no longer need operatively.

As part of the integration of SAP Convergent Invoicing (CI) with Billing in SAP Sales and Distribution (SD), you

can also archive the document ow between CI billing documents and invoices. Archiving is based on SAP Data

Archiving (CA-ARC).

Archiving takes place using the following archiving objects:

● /SOIN/CISD

Allows you to archive the document ow relating to the integration of CI with SD Billing. Note that as a

prerequisite for archiving, the CI billing document must already be archived and deleted from the database.

● /SOIN/CIAP

Allows you to archive the document ow relating to the integration of CI with AP billing. Note that as a

prerequisite for archiving, the CI billing document must already be archived and deleted from the database.

You archive (and also delete) using the SAP standard tool for archiving, the Archive Development Kit. You can

use archive administration (transaction SARA).

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Archiving

P U B L I C 19

Important Disclaimers and Legal Information

Hyperlinks

Some links are classied by an icon and/or a mouseover text. These links provide additional information.

About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your

agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such

links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this

information.

Beta and Other Experimental Features

Experimental features are not part of the ocially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by

SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use

the experimental features in a live operating environment or with data that has not been suciently backed up.

The purpose of experimental features is to get feedback early on, allowing customers and partners to inuence the future product accordingly. By providing your

feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code

Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax

and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of

example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language

We try not to use gender-specic word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

P U B L I C

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Important Disclaimers and Legal Information

SAP S/4HANA for Subscription Billing, Sales and Distribution Option

Important Disclaimers and Legal Information

P U B L I C 21

www.sap.com/contactsap

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

aliate 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 specications may vary.

These materials are provided by SAP SE or an SAP aliate company for

informational purposes only, without representation or warranty of any

kind, and SAP or its aliated companies shall not be liable for errors or

omissions with respect to the materials. The only warranties for SAP or

SAP aliate 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.

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 aliate company) in Germany and other countries. All

other product and service names mentioned are the trademarks of their

respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN