Status
Owner	PERAL-ext, Carlos
Stakeholders	UL HASAN, Selim LAMIA, Gianni
Jira Request ID
Jira Development ID

High- Level Specification

Parameter

Value

Application System

S/4Hana ROW, S/4Hana CUI

Business Process Reference

09.06.02.04. Manage Centralized Outgoing Payments on Behalf of Subsidiaries

09.06.02.05. Manage Centralized Incoming Payments on Behalf of Subsidiaries

Functional Overview

Its needed to enable a monitor that is able so display the invoices selected in the IHB and the ones that not in case its needed to take action.

This will require a FIORI app to access by business.

Scope and Objectives

The project involves the implementation of a factoring solution within In-House Bank (IHB) using the S/4 Hana FI/IHB module. This system is designed to handle transfer of AP/AR items that are relevant for factoring, to the IHB center for further collection/payable management.

This enhancement covers the monitor to review the integrated items and bring the capacity to integrate new ones.

Process Flow Diagram

09.06.02.04. Manage Centralized Outgoing Payments on Behalf of Subsidiaries

SyWay Project > ERP-962 IHB Factoring - Report Monitor > image-2026-1-27_10-51-7.png

09.06.02.05. Manage Centralized Incoming Payments on Behalf of Subsidiaries

SyWay Project > ERP-962 IHB Factoring - Report Monitor > image-2026-1-27_10-53-24.png

Step	Description	Comment
1	Open the Fiori application to access the report
2	Select the parameters from the selection screen	The report should have a selection screen with the following fields .All fields they need to be able to select single value, a range of information or multiple values.
3	Display the output of the report	The Output of the report should be ALV features to add / remove fields , sort , sum/semisum, sort, filter, …
4	Select / Deselect invoices for Factoring	When I display the information, I should be able to select and deselect the relevant invoices for Factoring (selection flag with multiple selection or all should be available and a button to execute the action).

Assumptions

N/A

Dependencies

Finance Invoice settings

APM / In House Bank Settings

Enhancements relating to performing factoring of the open invoices (AP/AR) from affiliate to IHB from 953 to 959 and 963

Security, Integrity and Controls

Follow program authorization checks

Configuration Requirements

Finance Invoice settings

APM / In House Bank Settings

Language Requirements

No specific language requirement

Special Requirements

NA

If the enhancement interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.

Design Rationale

Functional Requirements

Factoring Monitor Report configuration and usage must adhere to SAP S/4HANA standard reporting principles and enterprise value policies. Access to the report and related invoice actions is to be governed strictly by role-based security authorization profiles.

Report selection screen parameters must allow input of single, range or multiple values for all key fields (company code, posting date, fiscal year, document type, and invoice document number) based on standard SAP selection method protocols.

Any invoice flagged or de-flagged for factoring must trigger real-time updates to Payment Block Key, House Bank and Account ID fields .

ALV output grid must comply with usability standards by providing authorized users the ability to sort, filter, sum, add/remove columns, and export data in standard SAP-supported formats; navigation to source FI, MM, or SD document screens (e.g., FB03, VF03, MIR4) must be enabled via configured SAP API services or classic transaction links.

Key functionalities include navigational access from reference document links to underlying FI, SD, or MM invoice transactions, supporting detailed examination and audit trails.

Proposed Technology to Use

Custom program

Data Source Considerations

The main tables to retrieve the information are:

Finance information : ACDOCA (or BSEG, BKPF, FAGLFLEXA,FAGLFLEXT… )
IHB Contract : /PF1/DB_ORDER ( from Clearing area onwards from the previous list )
Payment Information : BNK_BATCH_ITEM / BNK_BATCH_HEADER / REGUHM/REGUT / FEBEP

Data Validation Considerations

NA

Table	Field Name	Comments/Calculation/Field Manipulation

Custom Tables

N/A.

Master Data

NA

Field	Description	Data Type/Length	Validation rule/ Value Help

Configuration Table

NA

Include an overview of the table and what it’s used for

Field	Description	Data Type/Length	Validation rule/ Value Help

Selection Screen Enhancement

The report should have a selection screen with the following fields :

Field Name	Description	Select: Option or Parameter Check box or Radio button Import or Export	Data Type/Length	Selection Logic
BUKRS	Company code	Radio Button	CHAR(4)	Mandatory Field
KUNNR	Customer Number : Customer account number for receivables postings	Radio Button	CHAR(10)
LIFNR	Vendor Number: Account number of vendor or creditor	Radio Button	CHAR(10)
BUDAT	Posting Date: Date when the document was posted to SAP.	Radio Button	DATS (8)	Mandatory Field
GJAHR	Fiscal year	Radio Button	NUMC(4)	Mandatory Field
Document Type (BLART)	Type of accounting document (invoice, payment, etc.)	Radio Button
BELNR for FI, billing document number for SD	Invoice document number

Processing Logic

The main tables to retrieve the information are:

Finance information : ACDOCA (or BSEG, BKPF, FAGLFLEXA,FAGLFLEXT… )
IHB Contract : /PF1/DB_ORDER ( from Clearing area onwards from the previous list )
Payment Information : BNK_BATCH_ITEM / BNK_BATCH_HEADER / REGUHM/REGUT / FEBEP

Its expected to use API to retrieve the information if possible:

Display Document (for FI accounting documents) : API_JOURNALENTRYITEMBASIC_SRV ( BAPI_ACC_DOCUMENT_FIND / BAPI_ACC_DOCUMENT_READ ) / FB03
Display Billing Document (for SD invoices) : API_SUPPLIERINVOICE_PROCESS_SRV ( BAPI_INCOMINGINVOICE_GETDETAIL ) / VF03
Display Invoice Document (for MM vendor invoices) : API_SUPPLIERINVOICE_PROCESS_SRV ( BAPI_INCOMINGINVOICE_GETDETAIL ) / MIR4
...

Display the output of the report :

The Output of the report should be able to share the following information:

Finance Information

Document Number (BELNR): Unique identifier for the accounting document . This field should be possible to navigate to display the FI invoice. It can be use the same logic as FAGLL03 report
Company Code (BUKRS): Company code where the document was posted
Fiscal Year (GJAHR): Fiscal year of the document posting
Document Date (BLDAT): Date on the document
Posting Date (BUDAT): Date when the document was posted to SAP
Document Type (BLART): Type of accounting document (invoice, payment, etc.)
Reference Document (XBLNR): External reference number . This field should be possible to navigate to display the FI invoice. It can be use the same logic as FAGLL03 report
Customer ( KUNNR ) / Vendor (LIFNR ) : Customer / Vendor account number.
Header Text (BKTXT): Descriptive text for the document header
Currency (WAERS): Document currency
Entry Date (CPUDT): Date when document was entered into system
Entered By (USNAM): User who created the document
Amount (WRBTR): Amount in document currency
Cash Discount Amount ( WSKTO ) : Cash discount amount in document currency
Cash discount percentage rate ( SKTOF) : Cash Discount Percentage
Assignment (ZUONR): Assignment field for additional reference
Text: Line item text description
Cost Center (KOSTL): Cost center assignment
Business Area (GSBER): Business area assignment
Profit Center: Profit center assignment
Trading Partner (VBUND): Trading partner information
Sales Order (KDAUF): Sales order reference
Sales Order Item (KDPOS): Sales order line item reference
SD Billing ( AWEKEY ): SD Billing Document
Payment Ref ( KIDNO ) : Payment Reference
Reference Key (XREF1 ) : Relevance information in text field
Reference Key (XREF2 ) : Relevance information in text field
Reference Key (XREF3 ) : Relevance information in text field
House Bank (HBKID): Bank identification key for house bank master data
Account ID (HKTID): Account identifier within the house bank
Payment Block Key (ZLSPR): Field for selected invoices for factoring

IHB Contract

Clearing Area ( CLEARING_AREA): Clearing area identifier for payment processing
Factoring Contract Number (PI_NO) : Unique payment item number
Payment Item Date ( PI_DATE) : Date of the payment item
Technical Status ( TECH_STAT ) : Technical processing status of payment item
Transaction Type (TRANS_TYPE ) : Type of payment transaction
Transaction Amount ( TR_AMOUNT) : Payment transaction amount
Transaction Currency ( TR_CURR ) : Currency code for transaction amount

Payment information:

From the header document in case of payable:

Batch : Unique identifier linking to BNK_BATCH_HEADER from BNK_BATCH_ITEM ( IDBATCH_ID )
Item Number : ( ITEM_NO -BNK_BATCH_ITEM ) Sequential number identifying individual items within batch
Document reference: REFERENCE_DOCBELNR - BNK_BATCH_ITEM
Vendor/Customer ( PARTNER- BNK_BATCH_ITEM ) Business partner number (vendor or customer)
Item Status ( STATUS - BNK_BATCH_ITEM ) Current processing status of the payment item
Payment Method ( PAYMENT_METHOD - BNK_BATCH_ITEM ) Method used for payment execution

In case of receivable from the bank reconciliation:

Reconciled Item : FEBEP- VB2OK = 'X' its reconciled . VB2OK = ' ' means unreconciled. when its reconciled the report should say ACCEPTED if not pending .

It should be available ALV features to add / remove fields , sort , sum/semisum, sort, filter, …

Select / Deselect invoices for Factoring

When I display the information, I should be able to select and deselect the relevant invoices for Factoring (selection flag with multiple selection or all should be available and a button to execute the action). This should happen to be updating the invoice Payment Block Key ( ZLSPR ) and House Bank and Account ID if required). In case of deselect it should be verified that the Factoring contract is created, in case it is Reversal program should be called as well to reverse the factoring contract.

Volumetrics

This volume is estimated to be approx: 10000

Performance Considerations

In case of performance issues due to large number of information to be processed it should be raised the message to restrict the selection parameters and stop the execution.

Error Handling

Error Code	Description	Type Of Error	Resolution

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

ID	Condition	Expected Result
1	Run the Fiori application	Selection Screen should be displayed
2	Execute the Report layout	Report information is shown
3	Select invoice for factor	Invoice integrated in the IHB
4	Deselect invoice for factoring	Invoice reversed from the IHB

Test Considerations/Dependencies

Data set should be created for multiple scenarios:

AP:

Invoice factored and paid
Invoice factored but not paid
Invoice non factored

AR

Invoice factored and paid
Invoice factored but not paid
Invoice non factored

Other Information

Development Details

Package

Package Name	Parent Package

Enhancement Implementation

Enhancement Type	Standard Definition Name	Custom Implementation Name	Design Rationale Reference

Other Development Objects

Object Type	Object Name	Purpose/High Level Logic	Design Rationale Reference

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

ABAP	ZFI	ZMM	ZPS	ZCO	ZSD	ZBC	ZFI	ZCA
TABLES	ZFIT	ZMMT	ZPST	ZCOT	ZSDT	ZBCT	ZFIT	ZCAT