CDD_Perform Banking and Cash Management Activities.doc

StyrolutionCDD_FCR_01.06_Perform Banking & Cash

Management Activities

Configuration Design Document

Scenario/Topic: FCR_01.06_Perform Banking & Cash Management Activities

Version Date Description

Page 1 of 39



Usage Guidelines:

Document flow: The flow of the document is generic. Specific changes to the flow of the presentation will be required to be done by the client team to suit the client context.

Document content: The content explains the process in a generic manner. Specific changes will be required to be done by the client team to meet client requirement.

Section 1: The standard SAP building blocks which are required before proceeding with the given configuration are documented in this section.

Section 2: The client specific configuration steps are documented with the required data / value for configuration. This section can be changed only to add data / value required for configuration.

Page 2 of 39



Document History

ReviewersRole Name Comments Received Date

FI Local Team Member

Kelly Belmans 14/06/2012

SignatureRole Name Comments Received Date

FI Local Team Member

Kelly Belmans 26/06/2012

Revision History

Version No. Date Author Revision Description0.1 12-Nov-13 Dinesh

BhaleraoSet up Cash Journal - Russia (TR SEDK921359)

0.2 17-Dec-13 Markus Kleine

Wave 3 - Updates

0.3 21-Jan-14 Markus Kleine

Adding Cash Journal Customization

Page 3 of 39

Deliverable Name Bank and Cash ManagementAuthor Sameer S GupteOwnerTeam FCRKernel VersionStatus DraftVersion 0.1



0.4 27-Jan-14 Markus Kleine

Minor updates

0.5 04.06.2014 Stefan Ruppe New Map entry Payment Status Management0.6 12.06.2014 Pradeep

LakkavaramDelimiter “;” added to Language PT 1 4 in Table T015Z. Without this delimiter the Payment advice job is getting cancelled in one of a case.TR: SEDK939951 Ticket#: INC0011035

0.6 18.06.2014 Anjan Nanduru

Assignment of Bank Account – Transaction type changed from Company Code 7003 to 5008 – INC0010019TR: SEDK939502

0.6 20.06.2014 Xiaoxi He Change “Note to Payee” from 4 to 20.6 16.07.2014 Pradeep

LakkavaramThe prefix “/ORDERS” need to be removed for Instruction keys from 4 to 8 for Country KRINC0017085TRs: SEDK941663 & SEDK942011

0.6 17.07.2014 Pradeep Lakkavaram

Set-up of Citibank account for KOREA in SEPINC0017959TR: SEDK941954


Set up of New House Bank for Company Code 5007 – Ticket No INC0015495TR : SEDK941102


DME structure changed for Tree YFI_CNAB240_BOLETO – Ticket:INC0018413TR: SEDK942712


Add New Currency CHF for the Bank Determination for Company Code 1020 – Ticket INC0017229TR: SEDK942200

0.6 21.10.2014 Pradeep Lakkavaram

DMEE change in format YFI_CGI_XML_CT. Convert INSTRPRTY to technical node and set URGP under the node SVCLVLIncident: INC0022767 TR: SEDK948757

0.6 01.12.2014 Xiaoxi He Maintain GL account 284020 for House bank CINL2 CC7005


Added Country AT to the Permitted Destination Countries for DE & CH - TR : SEDK951213 & SEDK951245CHG0030493

0.6 16/01/2015 Anjan Nanduru

Have added Entry in table TBE31 for Country Key TR – EHP7 upgrade issue

Page 4 of 39



Transport : SEDK952745CHG0030663

0.6 19/01/2015 Pradeep Lakkavaram

FBZP-Bank determination for Company code 5001 Payment method “L” and Account id “USD01”- Currency INR added and Ranking order added for House bank “CISG1”Transport: SEDK952737Ticket: CHG0030658

0.6 06/02/2015 Anjan Nanduru

Changing of account ranking order EUR payments of Company Code :7003Transport: SEDK953431Ticket: CHG0030702

0.6 04/03/2015 Ramakrishna Battula

Payment Configuration changed for Company Code :7005Transport: SEDK954620Ticket: CHG0030858

Other Related Documents<Please mention related Documents names / reference (issues, data entities, etc.).>

Related Document CommentFCR_06_Perform_Banking__Cash_Management_Activities.doc

Business process document for banking and cash management

Page 5 of 39



Table of content

1 Sign-off Checklist...................................................................................................................62 Configuration Steps:.........................................................................................7

2.1 STEP 1: Set Country-Specific Checks.............................................................................72.1.1 Information.............................................................................................................72.1.2 Global / Local impact..............................................................................................72.1.3 Cross process / Cross function impact....................................................................72.1.4 Set Country-Specific Checks...................................................................................7

2.2 STEP 2: Define House Banks..........................................................................................82.2.1 Information.............................................................................................................82.2.2 Global / Local impact..............................................................................................82.2.3 Cross process / Cross function impact....................................................................82.2.4 Define House Banks...............................................................................................8

2.3 STEP 3: Global Settings for Electronic Bank Statement..................................................92.3.1 Information.............................................................................................................92.3.2 Global / Local impact............................................................................................102.3.3 Cross process / Cross function impact..................................................................102.3.4 Global Settings for Electronic Bank Statement.....................................................10

2.4 STEP 4: Manual Bank Statement – Create and Assign Business Transactions..............112.4.1 Information...........................................................................................................112.4.2 Global / Local impact............................................................................................112.4.3 Cross process / Cross function impact..................................................................122.4.4 Manual Bank Statement – Create and Assign Business Transactions...................12

2.5 STEP 5: Define Variants for Manual Bank Statement...................................................122.5.1 Information...........................................................................................................122.5.2 Global / Local impact............................................................................................132.5.3 Cross process / Cross function impact..................................................................132.5.4 Define Variants for Manual Bank Statement.........................................................13

2.6 STEP 6: Define Cash Journal.........................................................................................142.6.1 Information...........................................................................................................142.6.2 Global / Local impact............................................................................................142.6.3 Cross process / Cross function impact..................................................................142.6.4 Maintain View for Cash Journals...........................................................................142.6.5 Define Numbering Groups....................................................................................152.6.6 Create, Change, Delete Business Transactions....................................................162.6.7 Create, Change, Delete Business Transactions....................................................16

2.7 STEP 7: Define Approval Rules for outgoing payments................................................182.7.1 Information...........................................................................................................182.7.2 Global / Local impact............................................................................................182.7.3 Cross process / Cross function impact..................................................................182.7.4 Rule Maintenance.................................................................................................182.7.5 Additional Criteria for payment grouping.............................................................202.7.6 Mark rules for automatic payments......................................................................202.7.7 Assign role to Release Steps................................................................................212.7.8 Define Release Procedure....................................................................................23

Page 6 of 39



1 Sign-off ChecklistUse the following checklist to guide your completion of the Functional Design Document.

Standards and Consistency Has the correct template been used and all sections been completed as required? Are the correct details (Business Owner for sign-off, status etc) displayed on the front page? Has the document history been continuously updated? Are all linked / related documents listed in the document?

Integration and Dependencies Have all referenced documents been listed (other business process designs, sub process

designs, spreadsheets, information papers, etc.)?

Global / Local impact Is mentioned if the change has local or global impact? Is mentioned for which company codes / Countries / Plants the setting is needed? Is the transport impact analyzed? Is the transport planned ?

Usability – From the user perspective Has the setting attempted to maximize the efficiency of the user

(i.e. simple to use, intuitive, quick to use)? Are any manual steps clearly defined and carefully comunicated?

Page 7 of 39



Flexibility – From a business perspective Do all steps have been clearly identified ?

Additional Information Has security been considered (e.g. authority checking considered, target group of users who should be given access to

the report etc)? Are the test conditions sufficiently detailed to enable a full test of all required functionality?

Page 8 of 39



2 Configuration Steps:

2.1 STEP 1: Set Country-Specific Checks

2.1.1 InformationHere we maintain the country level settings for bank data, postal data and control data.

In standard SAP all entries are maintained as per ISO standard. SAP recommends that the entries as per ISO standard are used.

However, for some countries like Singapore while SAP mandates bank account number to be maximum 10-digits, certain bank accounts in Singapore are of 12/14 digits. We therefore need to change the bank account number specification to allow 14-digits bank account number.

2.1.2 Global / Local impact<Please mention the global impact on the setting, and for which country which setting was done.etc).>Global

2.1.3 Cross process / Cross function impact<Please mention cross processes or cross function impact of the customizing (issues, data entities, etc.).>

2.1.4 Set Country-Specific Checks

The bank account number field for Singapore would be changed to ‘14’.

Page 9 of 39

SAP Module FI

Customizing Path IMG - SAP NetWeaver - General settings - Set Countries - Set Country-Specific Checks

IMG Transaction OY17Related Tables T 005Customizing Pre-requisitesChange Request(s) Id.Transport Id.



2.2 STEP 2: Define House Banks

2.2.1 InformationEvery financial institution that an organization uses to interact with its business partners needs to be set up as a house bank in SAP. The house bank is represented by a bank ID in SAP. Every account at a house bank is represented by an account ID.

SAP recommends that for domestic banks we should enter the bank number in the “bank key” field and for foreign banks we should enter the SWIFT code in this field.

Due to a global approach banks are always stored with their bank number as bank key and contain the SWIFT code in the corresponding field of the banks master data.

2.2.2 Global / Local impact<Please mention the global impact on the setting, and for which country which setting was done.etc).>Global

2.2.3 Cross process / Cross function impact<Please mention cross processes or cross function impact of the customizing (issues, data entities, etc.).>Processing of incoming bank statement as well as outgoing payment processing

2.2.4 Define House Banks

Page 10 of 39



Styrolution would be using the codification for the house bank ID (field length 5): Position 1 to 2 in the house bank key will be used to identify the bank

o Examples: For Citibank the 2 digit code would be CI For Commerzbank the 2 digit code would be CO For HSBC the 2 digit code would be HS

Position 3 to 4 in the house bank key will be used to identify the country of the banko Examples:

Citibank in Great Britain house bank key would be CIGB Commerzank in Germany house bank key would be CODE HSBC in Germany house bank key would be HSDE

Position 5 in the house bank key will be used as a counter for the bank institution in a countryo Examples:

First Citibank in Great Britain house bank key would CIGB1 Second Citibank in Great Britain house bank key would CIGB2 Third Citibank in Great Britain house bank key would CIGB3

The following codification will be used for the house bank account ID (field length 5): To represent the currency the account is setup against we will use the 3 digit ISO key for the currency and

add a 2 digit numbering to make use of all 5 available possitions.o Examples:

House bank CIGB1 in company code 1001: the first EUR bank account ID would be EUR01

House bank CIGB1 in company code 1001: the second EUR bank account ID would be EUR02

House bank CIGB1 in company code 1001: the first USD bank account ID would be USD01

Styrolution would be using the house banks as detailed in the attached Excel file.

2.3 STEP 3: Global Settings for Electronic Bank Statement

2.3.1 Information

Page 11 of 39

SAP Module FI

Customizing Path IMG - Financial Accounting (New) - Bank Accounting - Bank Accounts - Define House Banks

IMG Transaction FI12Related Tables T012Customizing Pre-requisitesChange Request(s) Id.Transport Id.



Here we make the global settings for electronic bank statement. The main steps to be carried out are:a) Create account symbols – the account symbols (for e.g. BANK, CHECK) required for

defining the posting specifications are defined here.b) Assign accounts to account symbols – the GL accounts (viz. bank, cash receipt, etc.) to

which postings would be made from the electronic bank statement are assigned to the respective account symbols.

c) Create keys for posting rules – keys for posting rules (business transactions from SAP system like incoming checks, credit memo, etc.) are defined here. SAP provides several standard posting rules, which should be used as much as possible.

d) Define posting rules – here we create the posting specifications for each posting rule. We use the posting specifications to specify how a business transaction is to be posted. Posting specifications consist of either 1 or 2 posting records depending upon whether the business transaction affects only bank accounting or also affects sub-ledger accounting.

e) Create transaction types – here we create the names and descriptions of the various transaction types as per our requirements. House banks that use identical lists of business transaction codes (external transactions) can be assigned to the same transaction type later.

f) Assign external transaction codes to posting rules – here we assign the external business transaction codes to an internal posting rule. This allows us to use the same posting specifications for different business transaction codes.

g) Assign bank accounts to transaction types – here we assign each of our bank accounts to a transaction type.

2.3.2 Global / Local impactGlobal

2.3.3 Cross process / Cross function impact

2.3.4 Global Settings for Electronic Bank Statement

Page 12 of 39

SAP Module FI

Customizing PathSPRO - Financial Accounting (New) - Bank Accounting - Business Transactions - Payment Transactions - Electronic Bank Statement - Make Global Settings for Electronic Bank Statement

IMG Transaction FI_BL_EBS_VC_T028 (IMG object)Related Tables T033ICustomizing Pre-requisitesChange Request(s) Id.Transport Id.



The electronic bank statement would be configured for Styrolution as per the attached Excel file “Electronic Bank Statement.xls”

The already existing posting rules ‘ZA0*’ would be changed so that the non-existing document type ‘ZR’ would be replaced with the existing document type ‘SA’:

Comments:

For the codification of Styrolution posting rules, letter “Z” has been used as first digit to be able to clearly differentiate them from SAP pre-delivered keys. To facilitate interpretation, 2 ranges are used:

Z100 – Z199: Incoming payments (and related reversals) Z200 – Z299: Outgoing payments (and related reversals)

External transaction type “NBOE” for transaction type “MT940” is not yet linked to any posting rule since Bills of Exchange are excluded from the Styrolution template. Yet, external transaction type is already foreseen since it is part of MT940 list of transaction codes and to allow linking to Styrolution posting rule when required at a later stage.

External transaction type "0006" is set to GL account Z100 to enable postings for single boleto items provided by an additional boleto return file from the bank. Original bulked entries on the electronic bank statements are redirected to the non-existing GL account '0' to prevent double bookings.

2.4 STEP 4: Manual Bank Statement – Create and Assign Business Transactions

2.4.1 Information

The business transactions determine how and to which accounts the system posts the payments. We create an indicator for each business transaction (for e.g. incoming checks) and allocate a posting rule to each business transaction.

We can use the account modification field to direct postings to different accounts depending on the business transaction. For e.g. account modifier ‘foreign checks’ can be used to direct postings for the business transaction ‘incoming checks – foreign’ to a account different than the general account for incoming checks.


Page 13 of 39




2.4.4 Manual Bank Statement – Create and Assign Business Transactions

Styrolution would be using new business transaction that start with the letter ‘Z’ as per the attached excel “Manual Bank Statement - Business Transactions.xls”. The business transactions would be having the same nomenclature as that used for the posting rules created for the electronic bank statement configuration. The business transactions would be assigned to postings rules in a 1-1 relationship.

The already existing business transactions (see attached excel “Manual Bank Statement – SAP Business Transactions.xls” would be deleted in order to avoid prevent their use by mistake.

2.5 STEP 5: Define Variants for Manual Bank Statement

2.5.1 Information

Here we define the account assignment variants for the manual bank statement in order to adapt the arrangement and/or the selection of the account assignment fields as per our requirements.

The variants are used while posting the manual bank statement (transaction FF67).

Page 14 of 39

SAP Module FI

Customizing PathSPRO - Financial Accounting (New) - Bank Accounting - Business Transactions - Payment Transactions - Manual Bank Statement - Create and Assign Business Transactions

IMG Transaction OT52Related Tables T028HCustomizing Pre-requisitesChange Request(s) Id.Transport Id.





2.5.4 Define Variants for Manual Bank Statement

Manual bank statement processing would require the use of an interpretation algorithm in order to automatically clear the sub-ledger accounts. The standard interpretation algorithms make use of the bank reference field in order to select and clear the correct sub-ledger items. However, in the standard SAP variant SAP01, the bank reference field is ‘suppressed’.

In order to overcome this, the standard SAP variant SAP01 would be copied as variant ZSAP1. The ZSAP1 variant would be modified in order to make the field ‘bank reference’ ready for input. This would help to automatically post the clearing in the sub-ledger accounts.

Page 15 of 39

SAP Module FI

Customizing PathSPRO - Financial Accounting (New) - Bank Accounting - Business Transactions - Payment Transactions - Manual Bank Statement - Define Variants for Manual Bank Statement

IMG Transaction OT43Related Tables T021FCustomizing Pre-requisitesChange Request(s) Id.Transport Id.



2.6 STEP 6: Define Cash Journal

2.6.1 InformationThis transaction allows managing incoming and outgoing cash flow. It enables the user to post to GL accounts, vendors and customers according to the needs of calculating and keeping track of balances and turnover amounts.



2.6.4 Maintain View for Cash Journals

Page 16 of 39

SAP Module FI

Customizing Path SPRO - Financial Accounting (New) - Bank Accounting - Business Transactions - Cash Journal - Set Up Cash Journal

IMG Transaction FBCJC0Related Tables V_TCJ_C_JOURNALSCustomizing Pre-requisitesChange Request(s) Id.Transport Id.



Accordingly to business needs will be configured cash journal in order to post only in Roubles for CC1016. The cash journal serves as a basis for entries in the general ledger and thereby represents the "Cash" G/L account. Moreover it is necessary to define document types used to post FI documents and numbering groups for the incoming and outgoing cash payments. In addition names of the Chef Accountant (Шкуренкова Елена Юрьевна) and the CEO (Ушачева Алла Васильевна) have to be entered in related fields. To get these fields the table should be scrolled to the right side. Mentioned activities could be done in Customizing for FI, by choosing.

Company Code 1016Cash Journal Number RUB1G/L Account Number 288000Currency Key RUBCash Journal Document Type: G/L Account Posting SACash Journal Document Type: Payment to Vendor KZCash Journal Document Type: Payment from Vendor KZCash Journal Document: Payment from Customer DZCash Journal Document Type: Payment to Customer DZNumbering Group for Payments OUTCPNumbering Group for Receipts INCPSplit Indicator for Totals Document for Split Presentation No Split of Line Items of Totals DocumentCash Journal Name PETTY CASH (RUSSIA)Cash Journal: Person 1 Шкуренкова Елена ЮрьевнаCash Journal: Person 2 Ушачева Алла ВасильевнаAdditional Field for Cash Journal Генеральный директор

The cash book must have a name in English (PETTY CASH (RUSSIA)) and in Russian (Кассовая книга) as well.

2.6.5 Define Numbering Groups

To be

able to number vouchers for incoming and outgoing cash payments separately, as required by law, numbering groups for the incoming and outgoing cash payments have to be defined as is shown below.

Page 17 of 39

SAP Module FI

Customizing Path SPRO - Financial Accounting (New) - Bank Accounting - Business Transactions - Cash Journal - Define Numbering Groups

IMG TransactionRelated Tables V_TCJ_NUMB_GROUPCustomizing Pre-requisitesChange Request(s) Id.Transport Id.



2.6.6 Create, Change, Delete Business Transactions

The number ranges for the cash document numbering groups that have been created should be defined. Note that 01 must be used as the number range interval for the number range sub objects of the object CAJO_DOC3.

2.6.7 Create, Change, Delete Business Transactions

Page 18 of 39

SAP Module FI

Customizing PathSPRO - Financial Accounting (New) - Bank Accounting - Business Transactions - Cash Journal - Define Numbering Range Intervals for Cash Journal Groups

IMG Transaction FBVJC6Related Tables INRDPCustomizing Pre-requisitesChange Request(s) Id.Transport Id.

SAP Module FI

Customizing PathSPRO - Financial Accounting (New) - Bank Accounting - Business Transactions - Cash Journal - Create, Change, Delete Business Transactions

IMG TransactionRelated Tables V_TCJ_TRANSACTCustomizing Pre-requisitesChange Request(s) Id.Transport Id.



The below listed Business Transactions have been identified as relevant for Russian Cash Journal usage.

Transaction types used are: Expense (E) Revenue (R) Cash transfer cash journal to bank (B) Cash transfer bank to cash journal (C) Customer incoming/outgoing payment (D) Vendor outgoing/incoming payment (K)

Russian texts have to be maintained for each entry:Business transaction number

Business transaction name in English

Business transaction long name in English

Business transaction name in Russian

Business transaction long name in Russian

2 OUTCSHPAY.EMPLOYEEADVANCE

OUTCSHPAY.EMPLOYEEADVANCE ВЫДАЧА ДС ПОД ОТЧЕТ Выдача денежных

средств под отчет

3 OUTCSHPAY.REIMBURSEMENT.

OUTCSHPAY.REIMBURSEMENT.

ВЫПЛАТА ПЕРЕРАСХ ПО АО

Выплата перерасхода по АО

4 INCASHPAY.RTUNEXCESSPAYM.

INCASHPAY.RTUNEXCESSPAYM.

ВОЗВРАТ НЕИСПОЛ ДС ПО АО

Возврат неиспользованных сумм

5 OUTCSHPAY.STUFFSALARYPAYM

OUTCSHPAY.STUFFSALARYPAYM

ВЫПЛАТА ЗП, ПРЕМИЙ, ПОСОБИЙ

Выплата зп, премий, пособий и пр.

6 OUTCSHPAY. TO SUPPLIER OUTCSHPAY. TO SUPPLIER ВЫПЛАТА ПОСТАВЩИКУ Оплата поставщику

7 OUTCSHPAY. TO CLIENT OUTCSHPAY. TO CLIENT ВЫПЛАТА КЛИЕНТУВозврат денежных средств покупателю

8 INCASHPAY. FROM CLIENT INCASHPAY. FROM CLIENT ПОСТУПЛ ДС ОТ КЛИЕНТА Поступление денег от покупателя

9 INCASHPAY.EMPLOYEELOAN INCASHPAY.EMPLOYEELOAN ВОЗВР.ЗАЙМОВ,ВОЗМ.УЩЕРБА

Возврат займов, возмещение расходов

10 INCASHPAY. FROM BANK INCASHPAY. FROM BANK КОММЕРЦБАНК. СО СЧЕТА Поступление денег

Page 19 of 39



ACC. ACC. из банка

11 OUTCASHPAY. ON BANK ACC. OUTCASHPAY. ON BANK ACC. КОММЕРЦБАНК. НА СЧЕТВнесено в кассу банка (на расчетный счет)

12 OUTCSHPAY.EMPLOYEEADVANC

OUTCSHPAY.EMPLOYEEADVANC ВЫПЛАТА АВАНСОВ ПО ЗП Выплата авансов

по зп

13 INCASHPAY. ESTAB. INIT. B INCASHPAY. ESTABLISH INITIAL BALANCE

ЗАГРУЗКА НАЧАЛЬНОГО ОСТАТ

Ввод начального остатка по кассе

2.7 STEP 7: Define Approval Rules for outgoing payments

2.7.1 Information

To keep control over automatic payment transactions, e.g. SEPA Credit Transfer or Direct Debits initiated out of SAP, two separate approval steps are configured to prevent misuse and increase the level of security.



2.7.4 Rule Maintenance

Rules can be defined to group payments together and allow assignments of specific persons per rule and approval step.

The rules are configured to group by country or region (also special rules for foreign currencies exist) because payment approvals have to handled locally for most of the entities.

Page 20 of 39

SAP Module FI

Customizing Path SPRO - Financial Supply Chain Management - Bank Communication Management - Rule Maintenance

IMG Transaction SPRORelated Tables V_BNK_RULE_MAINTCustomizing Pre-requisites Payment Methods, Company Code

Change Request(s) Id.Transport Id.



2.7.5 Additional Criteria for payment grouping

Page 21 of 39

SAP Module FI

Customizing Path SPRO - Financial Supply Chain Management - Bank Communication Management - Additional Criteria for payment grouping

IMG Transaction SPRORelated Tables V_TBNK_GRP_ADDCRCustomizing Pre-requisites Payment Grouping rules




In addition to the basic grouping conditions SAP allows to further differentiate on house bank configuration. Since Styrolution is using different banks for the direct communication via SWIFT and each payment grouped by SAP results in one file to the banks an additional separation on house bank ID was assigned.

2.7.6 Mark rules for automatic payments

Since only outgoing payments require to be passed on to the approver, rules can be marked to be automatically released.

Styrolution will make use of two different rules for incoming payments- direct debits and issued boletos (brazil).

Page 22 of 39

SAP Module FI

Customizing Path SPRO - Financial Supply Chain Management - Bank Communication Management - Mark rules for automatic payments

IMG Transaction SPRORelated Tables V_TBNK_AUT_PAYMCustomizing Pre-requisites Payment Grouping rules




Rules can also be marked for a mandatory drill-down. If the approver would not check the content of a batch it could not be rejected, released or resubmitted.

2.7.7 Assign role to Release Steps

Before users can be assigned for approval rules, an approval object hast to be created. Therefore the BNK_INI as initializing object is chosen. Since Styrolution requires a two-step approval process the release strategy is set to '01' (dual control) and the 1st release step is assigned.

Page 23 of 39

SAP Module FI

Customizing Path SPRO - Financial Supply Chain Management - Bank Communication Management - Change and Release - Assign role to Release Steps

IMG Transaction SPRORelated Tables V_TBCA_REL_RULECustomizing Pre-requisites Payment Grouping rules




In addition a rule needs to be created to assign specific users to the according payment grouping rules/responsibilities (also needs to be assigned to the rule first)

No user groups are available and each user/agent needs to be assigned separately and for each rule it is applicable.

Page 24 of 39



2.7.8 Define Release Procedure

A

second release object needs to be created to assign a second set of users for the second approval step. One user can be assigned for both sets and apply for the same rules, but setting the release procedure to '01' (dual control) will not allow to execute both approval steps by one single user. User ID of step 1 and 2 are required to be different.

Page 25 of 39

SAP Module FI

Customizing PathSPRO - Financial Supply Chain Management - Bank Communication Management - Additional Release Steps - Define Release Procedure

IMG Transaction BNK_BNK_COM_REL01Related Tables BCA_REL_LOG_DCustomizing Pre-requisites Payment Grouping rules




After enabling the additional approval step, the same customizing as of the previous chapter 2.7.7 is required within path SPRO - Financial Supply Chain Management - Bank Communication Management - Additional Release Steps - Assign Role to Release Steps.

It is important to create a release object of type BNK_COM for the second step since the release procedure was already initialized in the first step.

2.8 STEP 8: Payment Request

2.8.1 InformationPayment requests enable to create payments without involving customer or vendor items. Payment requests can be generated automatically when payments that are due are posted. They are subsequently settled individually or collectively using the Treasury payment program


Page 26 of 39




2.8.4 Define Number Ranges for Payment Requests

Page 27 of 39

SAP Module FI

Customizing PathSPRO - Financial Accounting (New) - Bank Transactions - Payment Transactions - Payment Request - Define Number Ranges for Payment Requests

IMG Transaction SPRORelated Tables INRDPCustomizing Pre-requisites none




2.8.5 Define Number Ranges for Payment Requests

Like vendor and customer payments, payment requests need reconciliation accounts to post on. Payment requests are only used for the Russian Styrolution entity, therefore only one entry needs to be maintained

CoCd 1016 - 489000 (Other payables)

2.9 General bank communication setting

2.9.1 Payment status management

Page 28 of 39

SAP Module FI

Customizing PathSPRO - Financial Accounting (New) - Bank Transactions - Payment Transactions - Payment Request - Define Clearing Accounts for Cross-Country Bank Account Transfers

IMG Transaction SPRORelated Tables V_ATPRA_FICustomizing Pre-requisites none

Change Request(s) Id.Transport Id. SEDK930979

SAP Module FI

Customizing PathSPRO - Financial Supply Chain Management – Bank Communication Management – Payment Status Management – Map external Status to internal Status

IMG Transaction SPRORelated Tables V_TBNK_XST_2_ISTCustomizing Pre-requisites yes




Ticket #: INC0011035 (Payment advice job cancelled due to missing delimter)TR: SEDK939951Changes done: Added delimiter “;” to the Field “Number in words” as below:

Ticket #: INC0017085TRs: SEDK941663 & SEDK942011The prefix “/ORDERS” need to be removed for Instruction keys from 4 to 8 for Country KR

Current setup:

Page 29 of 39



Changes done as below:

Page 30 of 39



Ticket No # INC0018413 : Boleto not workingTRs: SEDK942712

Changes to the DME structure done – Constant value maintained as ‘1’

Page 31 of 39



Ticket No # INC0017229 - Incident/SAP/KhamaP/Transaction F110 payment payment proposal 1020PTRs: SEDK942200

Page 32 of 39



Ticket No # INC0022867 : CHF payments rejected by BankTRs: SEDK948757

Changed the node Instrprty to Technical node.

CHG0030493 : Eng/Request/SAP/SchutA/Payment Method "J" (SEPA Credit Transfer) are not process

Page 33 of 39



Page 34 of 39



CHG0030663 - SEQ and SEP are not allowed to have IBAN for Turkey.

CHG0030658 – FBZP Bank determination for Company code 5001: Currency INR added for combination of House bank “CISG1” Payment method “L” & Account id “USD01”. Ranking order also added

Page 35 of 39



CHG0030702 - Changing of account ranking order EUR payments of cc7003

Page 36 of 39



CHG0030858 – Payment Configuration set up changed for Company Code 7005

House Bank set up

Page 37 of 39



Ranking Order

Bank Accounts

Page 38 of 39



Available Amounts

Page 39 of 39

Date post:	13-Jul-2016
Category:	Documents
Upload:	prabhakar-vanam
View:	84 times
Download:	2 times