Hi,

I am passing the CRM product's discount values to the IS-U from CRM, and these values are getting replicated into IS-U at installation facts perfectly via MDT.

Issue:

If we do not pass any value from CRM , even then the node is getting executed and operand is being created with Zero values.

See the screen shot.

How can we stop this node execution from config?

Hi Experts,

We want to merge manual bill with periodic bills always. Our requirement is this if there are only manual bills for a CA then this CA should not be process for invoicing.

Regards,

Ankur

I have a couple of questions related to Credits which I am encountering in our system :

Whenever credits are transferred from another CA (doc type XF), these are not picked up in auto clearing.

Let me explain this with an example & this typically happens in Bankruptcy cases. If a customer files for Bankruptcy , all the payments made after the bankruptcy filing are moved to new account. All the unpaid bills remain on old account. Suppose  .$ 100 credit was  transferred to new account & the customer was subsequently invoiced , the auto-clearing does not clear the credit against the invoice. Also we see this credit going thru' dunning process though we have set in config that dunning should not occur for less than 60. I see this behavior for Security deposit refunds too , where the credit is on doc type IN. They are not cleared in auto clearing & go thru' dunning.

Where should i look in clearing rules to address the first issue ?

For the -ve amount going thru' dunning process ... do i need to look for any enhancement.

I have attached a couple of screenshot of accounts where Security deposit refund were transferred & example 3 is for recently released Security deposit (docs of this type though having credit go thru dunning)

Appreciate your advise.

Our billing transactions are set to main 0100 and we post individual line items based on sub (nothing new here):

For example

- customer charge posts to main/sub 0100/0030 which maps to GL 440001

- energy charge posts to main/sub 0100/0160 which maps to GL 440002

The offsetting balance sheet entry to customer A/R posts to GL 140001

Is it possible to set up a scenario where the billing line items post to different A/R accounts?

For example:

- customer charge posts to P&L account 440001 and to balance sheet A/R account 140001

- energy charge posts to P&L account 440002 and to balance sheet A/R account 140002

If so, how can this be accomplished?

Hi,

I have an RTP interface that uses a single component with the following breakup:

Summer weekday on peak

Summer weekday Off peak

Summer weekend

Winter weekday on peak

Winter weekday off peak

Winter weekend

The calendar is set to differentiate weekdays and weekends

While billing the account for a summer month, only the summer weekend value is calculated. All weekday values are missing.

All the RTP component sections are activated. The RTP analysis of the bill indicates that the input profile is not considered for weekdays.

What could be the issue? Please help.

Hi All,

I am trying to create a correspondence for Check Returns. I have created the Return Lot via FP09 and was posted without any issues, but when i try to generate the return letter correspondence via FPCOPARA , I am being presented with message "Customizing settings missing for company code XXXX, form ID X Message No. FAPM020". I am missing something here? I have configured all the return reasons and forms. Please advise.

Thanks,

-Murthy

Hi Experts,

According to what I think TIBAN table was only used for the migration to SEPA and  suspect it is now used by SAP as a kind of archive, to register false mandates or something like that. In the last 3 months, only 3 new records were added to this list.

Can you confirm if above conslusions are correct? If not correct, what the purpose is of this table?

Thanks in Advance. Looking forward to relevant replies.

Hi Experts,

I have an installation, after opening the installation with transaction ES32, then to Installation facts, then pushing the button “Check” , I am getting two errors (see printscreen)

• Error in Operand 10-PRC(fact group, season):
• Rate determination is inconsistent

Please help me out with this problem.

Thanks and Regards,

Anshuman

Hi experts,

If i change MRU in Installation that time i am getting an error in one case "rate determination is inconsistent"

The value defined is as follows:

Kindly suggest me.

Regards.

Priya

Hi,

I am looking for a solution approach on bellow scenario for payment orders.

1. Customer will made a payment on portal, data will be validate by bank for real time check, and on successful scenario system should create a payment order lot and clear the outstanding debt.
2. On next 2 days will get the real time payment via file, and will post using payment lots to customer account.

Primarily to test this scenario, I am directly creating FP45 payment order lot but system is not allowing to post direct manual pay order lot to BP.

I am aware that Pay order is flexible solution for payment program, to test this manual payment I have done the following config checks.

For FPY1, payment method is marked as “Pay order”, does this cause any issue.

Kindly provide your clarification.

Regards,

Hari

Introduction

Electronic bank statement configuration and usage, in a casual contract accounts scenario, spreads through FI module (importing EBS from file to SAP), FI-CA module (parsing the EBS, recognizing the payments and posting them), and then back to FI module (posting to general ledger accounts via reconciliation key). In the next couple of pages I'll try to make a simple scenario which will cover the stated steps. Main goal of this document is to easier set-up the initial configuration which can then be expanded and modified to suit various business needs.

Prerequisites

Since our main focus is the FI-CA module, I'll asume that the basic configuration for the electronic bank statement in FI module is already set. Nevertheless, I'll point out the main configuration items/tasks that you need to check (or carry out, in case theyre not yet set):

1. In case your country has specific input file parameters (as Croatia has), you will have to deal with this first. Go through notes and see the correct way of implementation your specific case. Usualy, you will have to go through expanding include programs and enabling enhancements in CMOD, which is pretty straight-forward process.
2. IMG - Financial Accounting (new) - Bank Accounting - Business Transactions - Payment Transactions - Electronic bank statement - Make Global Settings for Electronic Bank Statement - this is your first stop. Go through the following sections and check if you have the correct configuration:
   1. Create Account Symbols - you should have at least two accounts here: bank account and temporary or transitional account, although common practice is to use one temporary account for incomming payments and the other one for outgoing payments. For the sake of simplicity, we will use just one.
   2. Assign Accounts to Account Symbols - this is where you link the account symbol you created in the previous step with the real general ledger account. You should have, in your system, defined general ledger account for both (or three of them) account symbols from previous step.
   3. Create Key for Posting Rules - in this section, you need to have at least two keys defined. Preferably, make your own key which will be used to define posting of incomming payments, the ones you will transfer to FI-CA and parse there.
   4. Define Posting Rules - for the already stated Key for Posting rules, check that you have defined posting. Usualy, you will have bank accounting posting defined (posting area 1), where you will post debit to bank account and credit to temorary or transisional account.
   5. Create Transaction Type - you should have at least one transaction type existing. When going in its sublevel (Assign External Transactions), you should have covered the possible transactions that will come from your electronic bank statement file, or the enhancement that will parse it.
   6. Assign Bank Accounts to Transaction Types - make sure that you have defined bank accounts for which you will import electronic bank statement.

Shortened: we have defined bank and transitional accounts, transactions that may occur in the file and the rules that tell the system how to post the items.

Having this set, we should be able to successfully import electronic bank statement file from local computer to SAP system and post it between bank account and transitional account.

FI-CA EBS Setup

Importing electronic bank statement in FI-CA can happen by transfering the already imported EBS file (what we are explaining here) and by importing a multicash file directly to FI-CA (which is subject to another post, and will not be covered here). Going with the first method, we have big part of the process already covered. What we have to do next is: import the items that are classified as incomming payments to FI-CA module, and either post them or leave for clarification.

Let's move to the IMG - Financial Accounting (new) - Contract Accounts Receivable and Payable - Business Transactions - Payments - Processing Incoming and Outgoing Payments - Define Transactions for Electronic Bank Statement Transfer configuration item.

Here we need to state which external transaction (check step 2.e) will we use, and what is it for. We can chose among several options: incomming payments, returns, payment orders and cheques. Again, for the sake of simplicity, we will use only one transaction and we will say its incomming payments (1). With this one line, we have enabled everything that we need for transaction FPB7 to import items from EBS that have this type of transaction.

Note to Payee Interpretation

Important process of the electronic bank statement is note to payee interpretation. These steps analyse the data from the item and, using predefined rules, attempts to determine the document number, contract, contract account and/or business partner to which should the payment be assigned. This process should, in short, work like this: you, as an invoice issuer, will state what payer has to put as payment description when paying your invoice.

The best option is to have the reference to the document number. Its the easiest way to identify which invoice has been paid, and, which document is to be cleared with the payment. There are lots of different ways to achieve this, and it would definetly require a document of its own, but again, for simplicity cause, Ill try to give the simple scenario.

Configuration is here: IMG – Financial Accoutning (New) – Contract Accounts Receivable and Payable – Business Transactions – Payments – Processing Incoming and Outgoing Payments – Define Interpretation Rules for Note to Payee. For this example, we will make the SAP document number. We need to create a new entry which we will parametrize. Once done, go to Structure sublevel and enter parameters (field lenght is the lenght of your document number, character set defines wether there are only number or other characters, minimum and maximum values can help you make sure you have the right number out of all the numbers you can get in the electronic bank statement item, and partial transfer can make a beginning or ending offset). Under Assigned Selection Categories make an entry with the Document as selection category. With setup like this, you will be able to identify the exact invoice which is paid and displayed on bank statement.

Another important part is clearing. Once the note to payee interpretation does its magic, and based on the clearing setup, the clearing process is triggered and the documents, again: based on the rules, get cleared. However, clearing process is process of its own, and is already elaborated in SAP documents, and will not be explained here.

Usage

First, let's import the electronic bank statement file from the local computer in the SAP system. Assuming all above written is set, we need to start transaction FF_5. Depending on your case, you need to select the correct electronic bank stamement format. It might be SWIFT MT940 with field 86 structured, XML, Multicash or any other supported format (note: check step 1 for country-specific formats).

Now we have our bank statement imported in FI, and we can check that with transaction FEBA. For incomming payments, we should only have one posting (D: bank - C: transitional account).

Then, we can move to the next step: transaction FPB7. This transaction will check the imported file and pull all items with transaction that represents incomming payments (see above: FI-CA EBS Setup) into payment lot. Depending on the options you set, it will create, create and close, or create, close and post payment lot. Since we want one lot to hold only payments from the one EBS, we should use at least "close lot" option.

Once the lot is created, you can check its parameters and items via transaction FP05. If you havent stated otherwise (in posting area 1005), payment lot name is generated from bank short key, year and bank statement number.

Third step (for this simple scenario) is clarificication. Either through "Postprocess" button in FP05 or transaction FPCPL, we should assign payments to documents, contracts, contract accounts or business partners. Items that appear here are the ones that could not be "understood" by the Note to Payee recognition process.

Finaly, we need to transfer the postings to general ledger. The process, much like the clearing, is out of this scope and I will just point out how its done. Once you post the payment lot, reconciliation key is closed and is ready for transfer to general ledger. You do that via transaction FPG1.

Additional information

There are several articles on SCN regarding different scenarios of electronic bank statement. Some of them are these:

- Lockbox and then FPB7

- Automaticly start FPB7

- Electronic Bank Statements in FICA

- EBS Configuration in FICA

- FI-CA import MT940 file to Multicash

Conclusion

This document describes the simple process of importing electronic bank statement file in SAP, pulling items to FI-CA, interpreting them and finaly transfer postings to general ledger. I hope it will be useful for consultants to set and test the process and give them a quick start in this area.

Hi everyone.

Im struggling with the Note to Payee configuration in FI-CA but it doesnt give any results so far. I would like to ask you if you have some configuration guide or at least some guidelines that I could follow to successfully set it up.

Our client wants the note to payee to consist of 3 numbers: bill number - contract account - month_year (for example: 10006722-2024472-314) as the regulations in our country allow only numbers and dashes to be in that field. Total field length is 22 characters (again, only numbers and dashes).

Thanks a lot in advance for any suggestions or materials.

Marko

Hi everyone.

I have configured the Interpretation rules for Note to Payee. It works for the simple scenario where a subset of the whole line is one parameter that I need (for example: I can extract contract number from the note to payee, when its written in a form similar to this: contract_number-date-check_digit).

Our client wants the Note to Payee to consist of 3 numbers: contract number - contract account - month_year (for example: 10006722-2024472-314) as the regulations in our country allow only numbers and dashes to be in that field. Total field length is 22 characters (again, only numbers and dashes).

As I need to get both the contract number and the contract account number, I tried to set that up using options in Interpretation rules, but so far I havent been able to get it working. Does anyone has similar requirement or has an idea of how this could be achieved?

My config is as follows:

- Selection field: 1 Contract Account

- - Keywords: not used

- - Structure: Defined one structure line, with field length and partial transfer, with limited range (min and max value)

- - Assigned Selection Categories: contract account

What I tried is:

- adding new selection field (2 - Contract)

- adding new line in Structure section (second line with options like above, but for the contract number)

I would appreciate any help or ideas on this issue. Thanks in advance!

Marko

We have cloud enabled Live Activity application integrated with ERP IS Utilities. In this blog we have highlighted some of the functionalities of C4C - ISU Live Activity application.

Solution Scenario - Agent receives call from customers requesting for a service. Service can be request for move-in, move-out, cancel move-in, cancel move-out, edit move-in, edit move-out, transfer, create or edit meter reading, create or edit contract account, request for locks and blocks on contract accounts and contracts, financial transactional activities, so on and so forth. Not just these, the solution provides a comprehensive overview of a utilities customer that an agent can use along with the multi-channel platform to offer the best services to a customer.

The functionality thus offers a promising cloud solution for utility cloud services.  In this space, we will post a series of collaterals on the functionality of the Live Activity Application with ERP IS-U.

Also subscribe to our new exclusive youtube channel . --> SAP C4C Utilities - YouTube

1. How to create invoice - SAP C4C Utilities Create Invoice - YouTube

2. How to create, edit contract account - SAP C4C Utilities Contract Account - YouTube

This blog is work in progress, so please bear with us. These are not official content, they are only how to videos with intend to help the end users.

I have a couple of questions related to Credits which I am encountering in our system :

Whenever credits are transferred from another CA (doc type XF), these are partially cleared up in auto clearing:

In the example below you will observe that the transferred credit has cleared only part of the invoice. Highlighted entries shows the partial clearing.

I observe similar behavior with Security deposit refunds

The clearing variant 001 set in open item management is as under:

Appreciate any advise in analyzing & resolving  this issue.

PS: Amlan / Will : Apologies for incorrect  details of this issue in my earlier thread. Part of the credits seem to be cleared.

In our system we have set the amount limits for dunning procedure at $60.

But we are observing credits going thru' dunning process. We see this behavior for Security deposit refunds (doc type IN) & transferred credits (doc type XF).

Example of credit through transfer going thru' dunning :

Example of Security deposit refund going thru' dunning

Is the total balance on CA considered during dunning or amount at document level ? In the 2nd  example, we have a debit balance of the account.

Our billing transactions are set to main 0100 and we post individual line items based on sub (nothing new here):

For example

- customer charge posts to main/sub 0100/0030 which maps to GL 440001

- energy charge posts to main/sub 0100/0160 which maps to GL 440002

The offsetting balance sheet entry to customer A/R posts to GL 140001

Is it possible to set up a scenario where the billing line items post to different A/R accounts?

For example:

- customer charge posts to P&L account 440001 and to balance sheet A/R account 140001

- energy charge posts to P&L account 440002 and to balance sheet A/R account 140002

If so, how can this be accomplished?

Recently I was in a need of encoding several information into small amount of data: something that would allow system, if correctly entered, to easily identify the paid invoice, and, at the same time, allow user to get more data from the simple sequence. Among other possible solutions, I chose Classification Key implementation due to several reasons: its easy to implement, it is visible on document header and it can be used in note to payee interpretation rules.

Enabling enhancement

Start point is enabling prepared enhancement. Go to IMG - Financial Accounting (New) - Contract Accounts Receivable and Payable - Program Enhancements - Prepared Enhancements - Classification Key and run the program. As always, first time run it with checked option "Only Check Enhancement" which will check wether this enhancement is already enabled/created.

After that, run the program without checked option "Only Check Enhancement" and wait for it to finish. The program will create everything needed in the system.

Note: If you are running SyBase, the database index will not be created automaticaly. The program will show that everything exists, but the index will not be created in the system. To do so, you should create the index in the database manualy: create the database index DFKKKO-Z01 in a customer package and activate the index which will create the index in the database system.

Changes on the documents

If everything was done correct (both by you and the SAP system), you have the enhancement enabled. You can check that by runing the stated program again, checking the table TFKENH or by going to transaction FPE2 (for example), choosing an existing document and checking the document header. At this point, the field Classification Key (OPORD) will exist, but it will not be populated.

Deciding about the Classification Key contents

Classification Key contents are up to you. The field is up to 35 characters long. I decided to put contract account, date and control number in it. It would fit the lenght, give me enough data and be usable for payment transactions.

Filling Classification Key field

I wanted the classification key to be filled during invoicing. Luckily, an event exists exactly for that purpose. Event R429. If youre not familiar with the FQEVENTS transaction, I would recommend this article: How to use FQEVENTS. It will give you great start and you will be able to use the events in no time.

What you need to do here is create your own function module with the ABAP code you will use.

I will give a short example of what could be the content of your custom functional module:

function ZISU_SAMPLE_R429.
DATA: contract_account TYPE VKONT_KK,             date TYPE FAEDN_KK,            output TYPE OPORD_KK,            control_number TYPE n
contract_account = X_FKKVKP-VKONT.
date = X_ERDK-BLDAT.
control_number = 1.
CONCATENATE contract_account '-' date '-' control_numberr INTO output.
Y_OPORD = output.
endfunction.

Depending on your need, you can implement control number generation (for example, you could use something similar to FMCA_CREATE_DIGIT_MODULO11). Displayed code will always put "1" as control number, for demonstration purposes.

Interpreting Note to payee

Assuming you printed classification key on your invoice, as a payment reference number, next step is interpreting it, once it comes on electronic bank statement or is entered manualy in payment lot.

First, add open item selection category in IMG - Financial Accounting(new) - Contract Accounts Receivable and Payable - Basic Functions - Open Item Management - Specify Selection Categories. Define a new selection category and link it to field OPORD.

Then, define interpretation rule (IMG - Financial Accoutning (New) - Contract Accounts Receivable and Payable - Business Transactions - Payments - Processing Incoming and Outgoing Payments - Define Interpretation Rules for Note to Payee). Here, you should define the length (under Structure) and selection category (under Assigned Selection Category).

Setting all this will cover the initial idea: being able to automaticaly identify invoice during payments processing and being able to identify the customer and the month just by seeing this number. Dont forget checking your settlement/clearing settings to include classification key in your variants.

Hope this helps in your implementations.

Hi,

I am creating BP using the BAPI.

Passing the address 123, ABC Street, Richland, IA 52585, US

We do not pass the county/district. Its always blank for us in the file feed.

The BAPI fails because the zip code and city is tied to county : "County Unknown". Tax Jurisdiction cannot be determined.

Creating the BP on FPP1 is not a problem.

Any pointers before I raise the message?

Thanks,

Sachin

Is there any documentation available for SAP Best practices on consolidated billing?

What are the typical things to keep in mind while solutioning for consolidated billing