ER Minor Release

Technical Specification RFO

Customer Statement - India

 Version: 5.0
Technical Specification Report/Function/Object

1 Technical Design
1.1 Document Information
Business Process IP Code: O-150
FIRE-ID O-150-2512
Team OTC
Complexity: COMPLEX

1.2 Document History

1.2.1 Change Log

Author Date Version Reference Number Summary of Changes

Marirose Beth L 06/09/2016 V1 ER 942600 Initial Document

Dilag
Marirose Beth L. 20/01/2016 V2 ER 1142074 Add ALV display
Dilag
Joseph Ryan 08/08/2023 V5 ER 2514065 Add new program logic for the Consolidation of sum-up of the
Lopez Fire-ID 8010 rebate-related credit/debit notes and credit/debit note
cancellations/reversals value transactions with “RV”, “DG”, “DR” and
NC 261279 “DA” doc. Types and add column Document type for Excel Format.
To add a new Document Header Text column in the report and in the
form output.

[If this FS is updated later on due to a new RICEFW# or SysAid ER# touching the same FIRE-ID, to
clearly relate them to version number here, but also along the rest of the document. The latest
version of this file should always contain the whole history of changes for this FIRE-ID]

1.2.2 Approval Log

Reference
Name Role Date
Number

Bacardi Functional Approver <SysAid ER# or

Partner Functional Approver RICEFW ID>

Bacardi Functional Approver <SysAid ER# or

Partner Functional Approver RICEFW ID>

Modified: 6/6/2024 8:45 PM 2 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

Contents
1 TECHNICAL DESIGN.......................................................................................................................... 2
1.1 DOCUMENT INFORMATION................................................................................................................ 2
1.2 DOCUMENT HISTORY....................................................................................................................... 2
3 TECHNICAL REQUIREMENTS........................................................................................................... 4
3.1 REQUIREMENT SUMMARY................................................................................................................. 4
3.2 DEVELOPMENT DIRECTLY RELATED OBJECTS.....................................................................................4
3.3 AFFECTED OBJECTS OR TRANSACTIONS........................................................................................... 5
3.4 USED OBJECTS OR TRANSACTIONS.................................................................................................. 5
3.5 HARDCODING STRATEGY.................................................................................................................. 5
3.6 EXECUTION MODEL......................................................................................................................... 9
3.7 DEPENDENCIES / CONSTRAINTS / LIMITATIONS................................................................................10
3.8 ASSUMPTIONS............................................................................................................................... 10
3.9 PROCESS FLOW DIAGRAM............................................................................................................. 11
3.10 PROCESS FLOW DESCRIPTION........................................................................................................ 11
3.11 SELECTION CRITERIA..................................................................................................................... 12
3.12 LAYOUT........................................................................................................................................ 13
3.13 FIELDS.......................................................................................................................................... 15
3.14 ERROR MESSAGES........................................................................................................................ 17
3.15 TRANSPORT NUMBER(S)................................................................................................................ 17
3.16 SECURITY AND AUTHORIZATION..................................................................................................... 18
4 TESTING REQUIREMENTS.............................................................................................................. 19
4.1 KEY BUSINESS TEST SCENARIOS................................................................................................... 19
4.2 TESTING CONSIDERATIONS/DEPENDENCIES....................................................................................19
5 APPENDIX......................................................................................................................................... 20
5.1 GLOSSARY OF TERMS.................................................................................................................... 20
5.2 ADDITIONAL SUPPORTING / REFERENCE DOCUMENTATION................................................................20

Modified: 6/6/2024 8:45 PM 3 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

3 Technical requirements
3.1 Requirement summary
India needs to issue customer statement as necessary when customers request a statement or when
Bacardi needs to remind the customers of their payables to the company. This statement contains the same
information available in the Standard SAP transaction FBL5N – Customer Line item. This report has the
option to output in PDF file.

SAP standard transaction will not address India’s requirement due to the following reasons:
 Option to output the report in PDF file format.
 Display detail of the Customer grouping code that is represented by a customer hierarchy node.
 Display beginning balance of customer receivable
 Ability to print out all statements for the selected States (SAP Customer Region)

ER 2514065
 To update the Customer Statement Report (ZR422) to display the consolidated
sum-up of the rebate-related credit/debit notes and credit/debit note
cancellations/reversals value transactions with “RV”, “DG”, “DR” and “DA” doc.
types.
DOC TYPE DESCRIPTION RELATED TO
DA Customer Document Customer Debit Memo
DG Customer Credit Memo Customer Credit Memo
DR Customer Invoice Customer Debit Memo
Billing Doc. Transfer
RV Invoicing
(Invoice)

3.1.1 [V2]
[If this FS is updated later on with new specification details due to a new RICEFW# or SysAid ER# touching
the same FIRE-ID, to clearly relate them to version number in the change log section ]

3.2 Development directly related objects

Object type Object name Package Default message class
Report ZRO_RFKORD11_IN ZRLTRTR FB
Include ZRO_RFKORD11_IN_TOP ZRLTRTR
Include ZRO_RFKORD11_IN_SEL ZRLTRTR
Include ZRO_RFKORD11_IN_F01 ZRLTRTR
Tcode ZR422 ZRLTRTR
ZR_CAS_IN

Smartform ZR_CAS_IN_ZR422 ZRLTRTR

ZR_CAS_IN
Smartform style ZRLTRTR

Modified: 6/6/2024 8:45 PM 4 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

3.3 Affected Objects or Transactions

[Please provide a list of SAP objects or transactions which will be affected by the development}
Standard/Custom Object type Object name Purpose of this object
Contains Smartform name
Filter for Hierarchy Type (KNVH-HITYP)
Filter for Hier Assignment (KNA1-HZUOR)
Filter for Document types (BSEG-BLART & BSAK-
Custom Table ZUTIL_COMB_VAL
BLART)
Replacement of Accounting Text
(T003t-LTEXT)
Accounting doc type for aggregation (BSAD-BLART)
Custom Table ZUTIL_LOGO_TEXT Contains Standard Text names used in smartform

3.4 Used Objects or Transactions

[Detail any programming, error handling and archiving methods, standard or custom, which will be used in
development of the object.]
Standard/Custom Object type Object name Purpose of this object

Standard Table KNB1 Get customer for Company code entered on selection screen.
Standard Table KNA1 Customer details
Standard Table ADRC Customer address details
Standard Table KNVH Customer Hierarchy details
Standard Table BSID Open items for customer
Standard Table BSAD Cleared items for customer
Standard Table BSAK Cleared items for vendors
Standard Table BSEG All accounting document items
Standard Table BKPF Accounting document header
Standard Table VBRK Sales Order header
Standard Table TVFKT SD Document Type Description
Standard Table T003T FI Document Type Description
Item lines for the customer statement for india that will be used
ZOCSILINES_ALV_IN_
Custom Structure in the alv and excel output with the new field document header
ZR422
text
Item lines for the customer statement for india that will be used
Custom Structure ZRCSILINES_IN_ZR422 in the alv, excel, and form output with the new field document
header text
ZRCSILINES_IN_TAB_
Custom Table Type Table Type for smartform ZR_CAS_IN
ZR422

3.5 Hardcoding strategy

[Detail any hardcoding strategy used in development, always based under the premise of the 2
Table
Hardoding set ID Values Purpose
(storeval/combval)

ZSEC 1
FIELDVALUE1 4751
COMBVAL ZRO_RFKORD11_IN FIELDVASSIGN ZR_CAS_IN Smartform name
ACTIVE_FLAG X
DESCRIP SMARTFORM FOR CUSTOMER STATEMENT
ZSEC 2
FIELDVALUE1 KNVH
FIELDVALUE2 HITYP
COMBVAL ZRO_RFKORD11_IN Filter for KNVH
FIELDVASSIGN A
ACTIVE_FLAG X
DESCRIP CUSTOMER HIERARCHY TYPE
ZSEC 3
FIELDVALUE1 KNA1 Filter for KNA1, Blank
FIELDVALUE2 HZUOR value for now (all
COMBVAL ZRO_RFKORD11_IN
FIELDVASSIGN assignments are
ACTIVE_FLAG X selected)
DESCRIP ASSIGNMENT TO HIERARCHY

Modified: 6/6/2024 8:45 PM 5 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

Table
Hardoding set ID Values Purpose
(storeval/combval)
ZSEC 4
FIELDVALUE1 BSAK
FIELDVALUE2 BLART Vendor Items to be
COMBVAL ZRO_RFKORD11_IN
FIELDVASSIGN RE displayed
ACTIVE_FLAG X
DESCRIP DOCUMENT TYPE INVOICE - GROSS
ZSEC 5
FIELDVALUE1 BSAK
FIELDVALUE2 BLART Vendor Items to be
COMBVAL ZRO_RFKORD11_IN
FIELDVASSIGN SA displayed
ACTIVE_FLAG X
DESCRIP DOCUMENT TYPE G/L ACCOUNT DOCUMENT
ZSEC 6
FIELDVALUE1 BSAK
FIELDVALUE2 BLART Vendor Items to be
COMBVAL ZRO_RFKORD11_IN
FIELDVASSIGN KR displayed
ACTIVE_FLAG X
DESCRIP DOCUMENT TYPE VENDOR INVOICE
ZSEC 7
FIELDVALUE1 BSAD
FIELDVALUE2 BLART Customer Item to be
COMBVAL ZRO_RFKORD11_IN
FIELDVASSIGN AB hidden
ACTIVE_FLAG X
DESCRIP DOCUMENT TYPE
ZSEC 8
FIELDVALUE1 REPLACE
FIELDVALUE2 LTEXT
FIELDVALUE3 E
Replacement
COMBVAL ZRO_RFKORD11_IN FIELDVALUE4 RV
Description
FIELDVASSIGN INVOICES
ACTIVE_FLAG X
DESCRIP REPLACEMENT DESCRIPTION FOR DOCUMENT
TYPE
ZSEC 9
FIELDVALUE1 REPLACE
FIELDVALUE2 LTEXT
FIELDVALUE3 E
Replacement
COMBVAL ZRO_RFKORD11_IN FIELDVALUE4 RE
Description
FIELDVASSIGN CUST. CREDIT NOTE
ACTIVE_FLAG X
DESCRIP REPLACEMENT DESCRIPTION FOR DOCUMENT
TYPE
ZSEC 10
FIELDVALUE1 REPLACE
FIELDVALUE2 LTEXT
FIELDVALUE3 E
Replacement
COMBVAL ZRO_RFKORD11_IN FIELDVALUE4 KR
Description
FIELDVASSIGN CUST. CREDIT NOTE
ACTIVE_FLAG X
DESCRIP REPLACEMENT DESCRIPTION FOR DOCUMENT
TYPE
ZSEC 11
FIELDVALUE1 COLLECT
FIELDVALUE2 BSAD
Aggregate entries for
COMBVAL ZRO_RFKORD11_IN FIELDVALUE3 BLART
this document type
FIELDVASSIGN DZ
ACTIVE_FLAG X
DESCRIP COLLECT TO SINGLE ENTRY IN REPORT

Modified: 6/6/2024 8:45 PM 6 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

Table
Hardoding set ID Values Purpose
(storeval/combval)
ZSEC 16
FIELDVALUE1 4751
FIELDVALUE2 ZR422
Smartform for
FIELDVALUE3
COMBVAL ZRO_RFKORD11_IN customer statement
FIELDVASSIGN ZR_CAS_IN_ZR422 ZR422
ACTIVE_FLAG X
DESCRIP SMARTFORM FOR CUSTOMER STATEMENT
ZR422
ZSET BLART
ZSEC 0001
SIGN I
OPTI EQ Document type for
STORVAL ZRO_RFKORD11_IN
LOW DA consolidation values
HIGH
ACTIVE X
DESCRIP CUSTOMER DOCUMENT
ZSET BLART
ZSEC 0002
SIGN I
OPTI EQ Document type for
STORVAL ZRO_RFKORD11_IN
LOW DG consolidation values
HIGH
ACTIVE X
DESCRIP CUSTOMER CREDIT MEMO
ZSET BLART
ZSEC 0003
SIGN I
OPTI EQ Document type for
STORVAL ZRO_RFKORD11_IN
LOW DG consolidation values
HIGH
ACTIVE X
DESCRIP CUSTOMER INVOICE
ZSET BLART
ZSEC 0004
SIGN I
OPTI EQ Document type for
STORVAL ZRO_RFKORD11_IN
LOW DG consolidation values
HIGH
ACTIVE X
DESCRIP BILLING DOC. TRANSFER (INVOICE
ELEMENT ZCADD
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_CADD_IN
ELEMENT ZCHIER
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_CHIER_IN
ELEMENT ZCNAME
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_CNAME_IN
ELEMENT ZCNUM
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_CNUM_IN
ELEMENT ZCREDIT
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_CREDIT_IN

Modified: 6/6/2024 8:45 PM 7 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

Table
Hardoding set ID Values Purpose
(storeval/combval)

ELEMENT ZDEBIT
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_DEBIT_IN
ELEMENT ZDESC
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_DESC_IN
ELEMENT ZDOCNUM
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_DOCNUM_IN
ELEMENT ZDOCTYPE
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_DOCTYPE_IN
ELEMENT ZDUEDATE
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_DUEDATE_IN
ELEMENT ZEFDATE
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_EFDATE_IN
ELEMENT ZLOGO
KEY_FIELD 1
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN Logo for smartform
OBJECT_TYPE L
OBJECT_NAME ZIN01_BACARDI_INDIA
ELEMENT ZNETBALL
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_NETBAL_IN
ELEMENT ZNETBAL1
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_NB1_IN

ELEMENT ZNETBAL2
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_NB2_IN

ELEMENT ZNETBAL3
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_NB3_IN
ELEMENT ZOPEN
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_OPEN_IN
ELEMENT ZOPEN1
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_OPEN1_IN
ELEMENT ZOPEN2
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_OPEN2_IN

Modified: 6/6/2024 8:45 PM 8 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

Table
Hardoding set ID Values Purpose
(storeval/combval)

ELEMENT ZOPEN3
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_OPEN3_IN
ELEMENT ZREF
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_REF_IN

ELEMENT ZREMARKS
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_REMARKS_IN

ELEMENT ZTITLE
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_TITLE_IN
ELEMENT ZTOTAL
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_TOTAL_IN
ELEMENT ZBKTXT
KEY_FIELD 1 Standard text for
ZUTIL_LOGO_TEXT ZRO_RFKORD11_IN
OBJECT_TYPE S smartform
OBJECT_NAME ZO_CS_FT_BKTXT_IN

3.6 Execution Model

Object created using ABAP Editor & Smartforms

Initiating Process Transaction ZR422

Transaction Volume The expected number of records to be displayed on this Form is between 1
and 50 for each customer. Customer statements are generated manually.
There is going to be a high volume of data to be collected since all items
from BSID and BSAD will be added to the balance.
Report can be executed for all the customers in a State. There are
approximately 500 customers per state.
highlight any performance considerations that should be considered during
Performance
the design, such as restrictions to expected execution time

Frequency and Timing Ad hoc

Output Type Print / Email

Processing Type Real time

Batch Requirements N/A

Modified: 6/6/2024 8:45 PM 9 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

3.7 Dependencies / Constraints / Limitations

Report Exclusion

Select document type AB shall and exclude from the program selection and form part of the report.
Except those that originates from a Trade-vendor transaction with document type RE, SA and KR
with reference to vendor/customer transaction (offset). Individual line item from Trade vendor A/C
with doc. Type RE, SA and KR to be picked for statement purpose.

Select from BSAD table the combination of AUGBL (clearing document) and ZUONR (assignment)
and include both documents related to each other with reference to the BELNR for each combination
(AUGBL/ZUONR).

Opening Balance – should include documents with document type UE (migration-data transfer)

3.8 Assumptions
[Describe any assumptions that have been made in the process of completing this design. What functionality
is expected of configuration or other developments that pass information to this development and/or retrieve
the information processed by it (performance, triggers, exceptions, etc.)?]

Modified: 6/6/2024 8:45 PM 10 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

3.9 Process Flow Diagram

Modified: 6/6/2024 8:45 PM 11 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

3.10 Process flow description

[Indicate if the criteria are optional or mandatory and if any data restrictions should apply]

3.11 Selection Criteria

[Please attach sample layout if applicable.]<TBD>

Name Table field / Check Select-Option(S) Comments Default

Box / Radio Button or Parameter(P) Value
Company Code Field P Remove none
multiple input
State Field S - none
Account Field S Mandatory None
Document Type Field S Mandatory None
Posting Date Field S Mandatory None
ER 1142074
Print PDF Check box P - checked
Print PFF Radio Button P Mandatory ticked
Excel Radio Button P Mandatory Blank
Aggregation of Rebate Check box P - No check
Email Check box P - No check
Default Email Field P - None
Output To Printer Field P - None
Print Immediately Check box P - No check

ER 1142074

Modified: 6/6/2024 8:45 PM 12 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object
ER 2514065

3.12 Layout

Modified: 6/6/2024 8:45 PM 13 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

ER 1142074
ALV Output

ER 2514065
ALV Output

Excel Output

Modified: 6/6/2024 8:45 PM 14 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object
Form Output

3.12.1 Totalling
Display the following information:
Opening Balance
Total Debit
Total Credit
Net Balance

3.12.2 Sorting
Sort by Date and Document Number Ascending

3.12.3 Interactive Capabilities

Aggregate by doc type DZ – can be configured in ZUTIL_COMB_VAL
Replace

3.13 Fields
[Please provide the fields and their descriptions in the report layout]
Label SAP SAP Field Print Max Output Calculations/Rules/Notes
Table Name Cntl* Length
CUSTOMER NUMBER BSAD/BSID KUNNR H Like BSAD-KUNNR N/A
CUSTOMER NAME KNA1 NAME1 H Like KNA1-NAME1 Select NAME1 from KNA1 where KUNNR
CUSTOMER KNVH HKUNNR H Like KNVH- Select HKUNNR from KNVH where
HIERARCHY NUMBER HKUNNR HITYP eq ‘A’ and
KUNNR eq (s_kunnr (parameter input) and
VKORG eq s_bukrs(parameter input)
CUSTOMER KNA1 NAME1 H Like KNA1-NAME1 Select NAME1 from KNA1
HIERARCHY NAME
OPENING BALANCE BSAD/BSID DMBTR H Like BSAD-DMBTR Sum up the value of DMBTR for all the items in BSAD
and BSID where
BUKRS eq Selection screen: Company code and
KUNNR eq KUNNR identified in the above step and
BUDAT-from eq blank
BUDAT-to eq Selection screen: (Posting date-from -1)
POSTING DATE BSAD/BSID BUDAT S Like BSAD-BUDAT N/A
DOCUMENT NO. BSAD/BSID XBLNR or S Like BSAD-XBLNR If Document type (BSAD-BLART or BSID-BLART) is ’RV’
VBELN append VBELN. Else XBLNR
For Consolidation of sum-up values per Document Type
and Document Header Text leave it as BLANK
DESCRIPTION T003 LTEXT S Like T003- LTEXT Select LTEXT from T003 where BLART eq (BSAD-

Modified: 6/6/2024 8:45 PM 15 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object
BLART or BSID-BLART).
If BLART eq ‘RV’ select (BSAD-VBELN or BSID-VBELN).
Select FKART from VBRK where VBELN eq (BSAD-
VBELN or BSID-VBELN)
Select from VTEXT from TVFK where FKART eq VBRK-
FKART
REFERENCE DOC. NO BSAD/BSID XBLNR S Like BSAD-XBLNR N/A
For Consolidation of sum-up values per Document Type
and Document Header Text
DOCUMENT HEADER BKPF BKTXT Like BKPF-BKTXT This field should reflect the Document Header Text field
TEXT value of the invoices.

For Consolidation of sum-up values per Document Type

and Document Header Text, Document Header Text
should still be reflected for aggregated line items.
DEBIT BSAD/BSID DMBTR S Like BSAD-DMBTR DMBTR with Debit/Credit value eq ‘S’ and Clearing Doc
is not initial will be listed in this column.
CREDIT BSAD/BSID DMBTR S Like BSAD-DMBTR DMBTR with Debit/Credit value eq ‘H’ and Clearing Doc
is not initial will be listed in this column.
OPEN AMOUNT BSAD/BSID DMBTR S Like BSAD-DMBTR DMBTR with Clearing Doc is initial. If Debit/Credit value
eq ‘H’ multiply Amount in LC with -1.
REMARKS BSAD/BSID SGTEXT S Like BSAD- N/A
SGTEXT
TOTAL BSAD/BSID DMBTR F Like BSAD-DMBTR Summation for Debit and Credit column
NET BALANCE BSAD/BSID DMBTR F Like BSAD-DMBTR Total of Opening Balance + Total Debit – Total Credit

Usage Notes:

*Print Control Codes:

 H =Header (Field that is in the header)
 F =Footer (Field in the footer)
 P =Page Continuation (Line Item data on which no page break should occur)
 S =Start new page (Field on which a page break takes place. Typical fields for page breaks are
'plant, product group, GL account)
 B =Beginning of data group (Sometimes a sort on a field in a report is performed in order to group
information logically although we do not necessarily do a page break on that sort field.

o Example: We could do a page break on plant and then sort material data by product group.
The report would have sections of data in which product group would be a sub header and
material line items would be written under that sub header.)

 E =End of data group (Often there is something that identifies the end of a logical grouping. Most
often this is a total or subtotal.)

Modified: 6/6/2024 8:45 PM 16 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object
ER 1142074
ALV Fields
Label SAP SAP Field Print Max Output Calculations/Rules/Notes
Table Name Cntl* Length
CUSTOMER NUMBER BSAD/BSID KUNNR H Like BSAD-KUNNR N/A
CUSTOMER NAME KNA1 NAME1 H Like KNA1-NAME1 Select NAME1 from KNA1 where KUNNR
CUSTOMER KNVH HKUNNR H Like KNVH- Select HKUNNR from KNVH where
HIERARCHY NUMBER HKUNNR HITYP eq ‘A’ and
KUNNR eq (s_kunnr (parameter input) and
VKORG eq s_bukrs(parameter input)
OPENING BALANCE BSAD/BSID DMBTR H Like BSAD-DMBTR Sum up the value of DMBTR for all the items in BSAD
and BSID where
BUKRS eq Selection screen: Company code and
KUNNR eq KUNNR identified in the above step and
BUDAT-from eq blank
BUDAT-to eq Selection screen: (Posting date-from -1)
POSTING DATE BSAD/BSID BUDAT S Like BSAD-BUDAT N/A
DOCUMENT NO. BSAD/BSID XBLNR or S Like BSAD-XBLNR If Document type (BSAD-BLART or BSID-BLART) is ’RV’
VBELN append VBELN. Else XBLNR
DESCRIPTION T003 LTEXT S Like T003- LTEXT Select LTEXT from T003 where BLART eq (BSAD-
BLART or BSID-BLART).
If BLART eq ‘RV’ select (BSAD-VBELN or BSID-VBELN).
Select FKART from VBRK where VBELN eq (BSAD-
VBELN or BSID-VBELN)
Select from VTEXT from TVFK where FKART eq VBRK-
FKART
REFERENCE DOC. NO BSAD/BSID XBLNR S Like BSAD-XBLNR N/A
DEBIT BSAD/BSID DMBTR S Like BSAD-DMBTR DMBTR with Debit/Credit value eq ‘S’ and Clearing Doc
is not initial will be listed in this column.
CREDIT BSAD/BSID DMBTR S Like BSAD-DMBTR DMBTR with Debit/Credit value eq ‘H’ and Clearing Doc
is not initial will be listed in this column.
OPEN AMOUNT BSAD/BSID DMBTR S Like BSAD-DMBTR DMBTR with Clearing Doc is initial. If Debit/Credit value
eq ‘H’ multiply Amount in LC with -1.
REMARKS BSAD/BSID SGTEXT S Like BSAD- N/A
SGTEXT

3.14 Error Messages

[Please include all error messages to be used within this development object.]
Error type
Error Number Error Message Corrective Action
(E/W/I/A)

<TBD> <TBD> <TBD>

ER 2514065
 When this program ZR422 and no posted accounts been made the system will prompt an error
message “No records were found”.

 When the program run and the required field is not populated, the system will prompt an error “Fill
the required field.”

3.15 Transport Number(s)

CTS Request Number CTS Task Number
D00K977605 D00K977606

Modified: 6/6/2024 8:45 PM 17 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object
D00K977325 D00K977326
D00K977213 D00K977214
D00K977211 D00K977212
D00K976689 D00K976690
D00K976633 D00K976757
D00K976634
ER 1142074
D00K981924 D00K982299
D00K981925
ER 2514065
Workbench
D00K9A1EKQ D00K9A1EKR
D00K9A1J2G D00K9A1J2H

Customizing
D00K9A1FBT D00K9A1FBT
D00K9A1KBL D00K9A1KBM

3.16 Security and Authorization

[List all Security / Authorization checks that should be included for the Report.]

Tcode ZR422

Authority check <Indicate the organizational value which will be used to retrict the access>
(for programs)
FI Company Code Sales Organization
Plant Purchasing Organization
Others: ____________________________

Authorization
group (for table
<Indicate the authorization group which will be assigned to the transaction in SU24>
display /
maintenance)

Complex
<If needed, describe the complex security requirement>
requirement

Role Mapping Function: ____________________________

<To be filled by
Bacardi Security
Sensitive Non Sensitive
SPOC team
member>

Modified: 6/6/2024 8:45 PM 18 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

4 Testing Requirements
4.1 Key Business Test Scenarios
[Please indicate the business level test scenarios that should be used to verify successful operations of the
Report, both positive and negative cases]

I Test Test Conditions Positive Expected results

D Scenario /
Negative
Testing
Positive Company Code: 4751 Positive Opening Balance : 2569969.37
1 Run Account: 10187897 Debit: 997910.00
Posting date: 01.08.2015 to Credit: 0.00
31.08.2015 Net balance: 3567879.37
Print Preview : checked
FBL5n check, amounts should be the
same
2 Ticked Aggregation of Rebate box Positive The report will consolidate the values
with “RV”, “DG”, “DR”, and “DA” same
document type and document header
text
3 Column Document Type display on Positive The document type column has been
excel format displayed in excel format
4 The report displays in PDF, Excel, Positive The report works fine with all formats
and email format
5 Un-ticked Aggregation of Rebate Positive The report works fine with all formats
box

<Name of <Conditions 1>

2 the Test <Conditions 2>
Scenario_2 <Conditions 3>
>

4.2 Testing Considerations/Dependencies

[List any considerations that are essential for application test planning (e.g. test this before ___ along with
___ separate from ____ ). If the development encompasses a user interface, explain how it should be tested
as well as list any insights as to how this component could be tested the most efficiently.]

Modified: 6/6/2024 8:45 PM 19 Last modified by: Rafael Llabres Perez

 Version: 5.0
Technical Specification Report/Function/Object

5 Appendix
5.1 Glossary of Terms
Term Definition

5.2 Additional supporting / reference documentation

ER 2514065
BRD link below
BRD

Modified: 6/6/2024 8:45 PM 20 Last modified by: Rafael Llabres Perez