Jan 3, 2019

S/4 HANA Banking configuration / Bank Account creation

Now in S/4 HANA there has been a whole change in the way Banking configuration needs to be done in the system. 
House Banks are not created anymore within Transaction FI12 or accessible through the Payment Program config (FBZP). FI12 has been deprecated. Now you need to use Tcode FI12_HBANK. This can still be transported.

But you can no longer create the Bannk Account IDs or Bank Account numbers through the Payment Program anymore. In S/4 HANA you need to create the Account IDs through "Manage Bank Accounts" with the SAP Netweaver Business Client.
For this, you will need to have assigned in your configuration client to your user the SAP standard role SAP_SFIN_CASH_MANAGER. This will give you access to Bank Account Management.
Once assigned you will trigger it with Tcode NWBC.

*NWBC services might not be active in your environment. For this Basis needs to activate the service in SICF.




You will click in "Manage Bank Accounts"



Then you will click in "New Bank Account" 
Fill in all the required information (*). Same as before S/4 the Bank Key needs to have been previously created in FI01 with all the branch address and data.




Here we put the Co.Code, Name of the Account Holder, Bank country, Bank Key (transit created previously), Account #, account description and account type.
<Save as Active>
<Edit>
<Connectivity Path>
<Add>


CAD is the Account ID that we have assigned to the Account that we are creating.
Also we need to assign the MAIN BANK GL ACCOUNT (The one that normally finishes with 00).



<Save as active>



Then we will see the newly created account in the list of Accounts.

This step needs to be done in your Config Client (Ex DEV-200), but it is not a transportable step. So it needs to be redone in every single environment. For that SAP has an EXPORT process that will generate an XML file with the list of Bank Accounts IDs created that will have to be imported in DEV-210 and in the future in QA and PROD.

It is important to keep that XML file and do not modify it internally. If necessary the XML can be generated again going back to the DEV-200 and repeating the EXPORT process that is coming in the next steps.


Here we will EXPORT and generate the XML file that contains the accounts.



Import Bank Accounts in DEV-210 (also applicable for QA and PROD once we will do that)

Log in DEV-210 and Execute NWBC (make sure you close the other NWBC Explorer window as you can easily get confused between the two environments). Remember that you will need to have assigned in your configuration client to your user the SAP standard role SAP_SFIN_CASH_MANAGER in DEV-210.

You will <Select File> and always play safe by doing "Import with Test Run". This way it will not import but it will check the data and tell you if there are any errors.

If you do not have errors within your newly created Bank Accounts, then import with the “overwrite” option activated. There might be some errors within other accounts that come standard, ignore those errors.


Then you will get results like this after the IMPORT.


Once you have finished your XML IMPORT, your Bank Account ID will be created. To verify this you can check the newly created entries in Table T012K.

** Remember that this XML Import process need to be repeated in every client and environment, therefore you should include this as part of your cut-over / client preparation manual activities.


If your Company and/or Project needs to implement this, or any of the functionalities described in my Blog, or advise about them, do not hesitate to reach out to me and I will be happy to provide you my services.

Jan 23, 2012

How to reverse an Accrual Journal Entry in a different date than the original one


Tcode: FBS1 – Enter Accrual / Deferral Journal Entry

FBS1


Enter the data corresponding to your Accrual Journal Entry with a “Reversal Reason” (always 05 for Reversal Journal Entries) and provide a “Reversal Date”. This date should be the date that you intend to reverse your entry; normally for accruals you will put 1st day of your next accounting period. In this case February 1st 2012.

Then complete all the other lines concerning your debits and credits on your entry and save the document.

Now, for any particular reason; you realized that your accrual is not correct and you need to reverse it. Trust me this happens really often at Month End.

To reverse a document you would use FB08 or F.81 to reverse Accrual documents in Mass. But since your Entry is not correct you do not want to reverse it in the actual expected date of reversal that you entered (in my example 2012-02-01); instead you what to reverse it in today’s date.

How would you do that ? Here is a simply trick that not everybody knows .

You should NOT solve this error by creating another Accrual document that offsets your original document.

Go to FB02 to modify the Document that you created.

FB02 Toolbar

Hat

Click on the "Hat" and you will get to the Document Header. There in the lower right part of the window you have a field “Reversal Date” that has the original date that you entered when you created your Reversal Journal Entry. Change that date for today’s date and once you execute FB08 or F.81 your Reversal will be done as of today.

Document Header

Reversal Date

Then you can go ahead and create your new Reversal Entry with the proper information.


If your Company and/or Project needs to implement this, or any of the functionalities described in my Blog, or advise about them, do not hesitate to reach out to me and I will be happy to provide you my services.

Feb 26, 2011

Transport Chart of Accounts and Company Code Chart of Accounts dependent Data

If you want to transport the Chart of Accounts, there are 2 parts that you need to keep in mind in order to transport it.

First part, you transport the Chart of Account itself with Tcode OBY9. In this transaction you transport only the General part of the Chart of Account as account numbers, descriptions, type of account and other general data.

As soon as you open the transaction it will ask you to provide a transport request for your activity.

Select Transport Request
After selecting the transport, you need to specify the Chart of Accounts number / Code that you wish to transport.
Select Chart of Accounts Code / Number
Then you will access to OBY9 main screen where you can select different options.
OBY9 - Main Screen - Transport Chart of Accounts
Here select "Accounts in Chart of Accounts" and also "name in all languages", so if you have more than one language in your system it will transfer the descriptions in all the languages that you have maintained.

As part of this transaction you can also have the chance to include in your transport request other FICO account determinations such as, FI account determination, AM account determination, CO account determination, MM, HR and SD.

By doing this you only transport the General part of the Chart of Accounts but you do not include the Company Code dependent settings of your individual accounts. If you have only 1 Company code, that is not a mayor problem. But ... if you have several company codes that uses the same chart of accounts that can be a real maintenance problem to create or maintain that in each individual environment. 

As part of my experience, I've been working in an implementation where the customer had 43 Company Codes. Yes, I am not mistaken, they had 43 and all in the same country and province. So in this case we needed something quicker in order to maintain and transport the Chart of Accounts for that huge amount of Companies.

As I mentioned before, I was talking about 2 parts for this process...

The second part of this process is to Transport the Company Code dependent data. For this there is no official transaction (as far as I know) and you need to get yourself inside of the transport management to do a couple of things manually.

Assuming that you already have a transport request created, you will use Tcode: SE09 - Transport Organizer; and select the "Display" button.
SE09 - Transport Organizer
SE09 - Display Transports

You will get the list of all your transports. Then select the transport that you will use to include this activity. Ex. like this transport that I created. Do a double-click in your sub-activity / transport task.

Transport Request selection.



In your "Objects" tab where you have the details of the information that you have in that transport, modify your transport by clicking in "Pencil icon" to edit your transport. Add a line like this 
TABU Object Type and Object name SKB1
 Include R3TR (Object) as Program ID, TABU Object Type (which means "Table of Contents") and then in Object Name SKB1 which is the table that has the Company Code Dependent data for the Chart of Accounts.

Once you add the line, do a double click to indicate which are the keys of the table that you want to transport.

SKB1 Keys
As you can see in this example, "200" represents the Golden client where I am transporting from, "1000" the Company Code data that I want to transport and "*" for all records in that key.

Also in this example you can see that I included Company Codes 2000 and 3010.

You can include here as many entries or Company Codes that you want following this concatenated logic.


If your Company and/or Project needs to implement this, or any of the functionalities described in my Blog, or advise about them, do not hesitate to reach out to me and I will be happy to provide you my services.